If you’ve gone through the steps in my previous HCX+ posts, you should be at a point where you can test a VM migration. There is a three-tier app running in Site A (Sofia in this example), with VMs whose names all start with “dist”. These VMs are all on NSX-backed segments that have been …
Assuming you enabled the Network Extension Service when you created the Site Pair, you should now be able to extend one or more networks. This will allow you to migrate VMs from one site to another without worrying about having to change their network configuration or manually configuring any new networking infrastructure at the destination …
Now that multiple Sites are configured, a Site Pair can be created to link them to each other. Navigate to Infrastructure > Site Pairs. Click the Create a Site Pair button. Choose appropriate sites to add to the pair and provide meaningful name for the Mobility Mesh (the name shown here is the default, which was fine for me). I …
With our sites onboarded, we can move on to configuring each site so that it can be used for HCX+ migrations. Click the Configure Site link under the Site to be configured (Sofia in this example). After a short time, you will see a page similar to the following: This site only has the one …
In my previous post, HCX+ Site Manager Deployment, we walked through through the process of downloading and deploying the Connector and Cloud OVA files that would become the HSM Connector and Cloud VMs. In this post, we’ll complete the process of onboarding these HSMs to HCX+. Back at https://hcxplus.vmware.com, you should have been left at the Onboard Site page …
Obtain the Connector and Cloud OVA files (and complete initial HCX+ onboarding) HCX+ provides central management of multiple local HCX+ Site Managers (HSMs). These HSMs are the equivalent of traditional HCX manager appliances. You can obtain the OVA files needed to deploy the HSMs during the very initial steps for onboarding a site in HCX+. …
You can use the vSphere UI to get a high-level view of events in your Tanzu Kubernetes clusters, and you can use the CLI to see very detailed information. Neither of these is both comprehensive and easy though. If you have onboarded your vSphere 8 with Tanzu installation to Tanzu Mission Control (TMC) (see my …
How to integrate vSphere 8 with Tanzu clusters with Aria Operations for Applications Read More »
If you ever have a need to move a deployed TKG cluster from one datastore to another, the process is not too difficult. The process results in new nodes being created (realized as new virtual machines on the new datastore). If you have a single worker node, or single-pod deployments, this will be a disruptive …
How to migrate a vSphere 8 with Tanzu TKG cluster from one datastore to another Read More »
In my previous post, Registering a vSphere 8 with Tanzu Supervisor Cluster with Tanzu Mission Control, I detailed the steps needed to register a vSphere 8 with Tanzu supervisor cluster with Tanzu Mission Control (TMC). Once this step is done, you can use TMC to manage existing Tanzu Kubernetes clusters (TKCs) created under the supervisor …
Managing a vSphere 8 with Tanzu Workload Cluster in Tanzu Mission Control Read More »
I did a walkthrough of this process for vSphere 7 with Tanzu in my earlier post, Attaching a vSphere 7.0 with Tanzu supervisor cluster to Tanzu Mission Control and creating new Tanzu Kubernetes clusters, and the process is largely the same for vSphere 8 with Tanzu. Once you have your supervisor cluster registered as a …
Registering a vSphere 8 with Tanzu Supervisor Cluster with Tanzu Mission Control Read More »
