In the most recent ‘Getting started with Oracle Cloud VMware Solution (OVCS)’ post; Getting Started With Oracle Cloud VMware Solution (OCVS) – Deploying The SDDC With HCX we deployed ourselves a VMware vSphere Software-Defined Data Center (SDDC) along with VMware HCX into Oracle Cloud.
Posts in this series:
In this post, I’m going to do a high-level review of the SDDC deployment which includes the VMware vSphere components (vCenter, ESXi Hosts), NSX-T Manager, and VMware HCX. Subsequent posts will dive deeper into the configuration.
We are now presented with the SDDC information. This page contains all of the important URLs, IP Addresses, Usernames, Passwords that you’ll need to access and manage your environment.
Scroll down to the ESXi Hosts section of the screen (bottom of the page), here we can see the three ESXi Hosts that have been deployed. This is also where we would add additional ESXi Hosts to our SDDC if required. Additional information about the ESXi Hosts can be found when we view our Compute Instances.
Something else to note here is the Fault Domain column. You’ll notice that each of our ESXi Hosts is deployed into a different Fault Domain within our Availability Domain. So for those of you who love to believe that rack failures happen, this should make you happy.
Each Oracle Cloud Region has at least one Availability Domain (all Regions with have 3 AD’s within a year of it becoming available). An Availability Domain is a physical data center within a geographical region. Availability Domains within the same region are connected to each other by a low latency, high bandwidth network. Each Availability Domain contains three Fault Domains. A Fault Domain is a grouping of hardware and infrastructure. Fault Domains provide anti-affinity, allowing the distribution of instances across Fault domains so that the instances are not on the same physical hardware within a single Availability Domain.
The diagram below illustrates our current SDDC deployment within the US East (Ashburn) Oracle Cloud Region. Here you can see, we are only using AD-1 and our ESXi Hosts are distributed across all three Fault Domains.
With the SDDC fully deployed, let’s make sure we can log into vCenter, NSX-T, and HCX.
NOTE: It’s worth noting here that you are logging in with the Administrator account. After the deployment of the environment, Oracle removes its own access and gives the customer FULL ACCESS to the whole vSphere environment. Oracle has ZERO ACCESS to SDDC after initial deployment. It’s completely private.
As part of the SDDC deployment, we opted to include the deployment of VMware HCX. HCX will be used to migrate workloads from our on-premises environment into our new SDDC.
NSX-T is used at the core of the SDDC for virtual networking. We’ll cover the networking configuration in-depth in a future blog post. For the moment, let’s get logged in.
Now that we have completed the overview of our OCVS SDDC, let’s move to the next blog post in this series; Getting Started With Oracle Cloud VMware Solution (OCVS) – Networking Configuration
Another VMworld is upon us!!! Sadly, it's only virtual again this year. However, that does…
As part of my recent move to Google, I'm working on quickly getting up to…
I am delighted to announce the next chapter in my career. Today is my first…
In episode thirteen of The VCDX Podcast, I am joined by two special guests who…
In my recent ‘Getting started with Oracle Cloud VMware Solution (OVCS)’ post; Getting Started With…
In my recent ‘Getting started with Oracle Cloud VMware Solution (OVCS)’ post; Getting Started With…