I recently ran into a problem where new vSphere-hosted virtual machines that are cloned from existing VMs have the same IP address. I assumed the clone process took care of these issues but apparently not. To fix this, I found the following solution:
Remove machine-id with sudo rm -rf /etc/machine-id
Run dbus-uuidgen --ensure=/etc/machine-id
After a reboot, the cloned VM has a new IP address!
In Part 1, we built the hardware build of materials and determined the utilization of a basic VMware Cloud Foundation (VCF) management domain deployment. But we need to put the “cloud” in by adding automation and self-service capabilities provided by vRealize Suite. To accomplish that, we can use SDDC Manager to deploy all the components of the vRealize Suite: Operations, Automation, and Log Insight into the SDDC. In this post, we’ll explore the compute and storage requirements for these components like we did in the previous post. This is going to explore the components required for a single region SDDC. There are a few more steps and components needed for setting up Cross-Region support.
When talking with customers about deploying a standard VMware Cloud Foundation (VCF) architecture, the topic of the hardware requirements and details for the management domain are usually glossed over. There’s a basic understanding that it will consist of 4 hosts with sufficient resources to run the SDDC components for the workload domains that it manages. When it comes time for purchasing though, what is the actual hardware that will run the management domain and does VMware have recommended specs for hardware for the management domain?