Defining one deploys nothing by itself: a VCF Operations HCX service mesh has to use it. It lists the network profiles, the cluster and datastore where appliances are placed, the service clusters (source VMs to be moved, or eligible targets at the destination) and which HCX services are switched on.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains Compute profile in context, with comparison tables and the common traps.
Terms in this definition
- VCF Operations HCX
Add-on licensed for moving workloads inside and between VCF private clouds and linking those environments, offering bulk or live migration plus network extension so IP addresses can stay the same.
- Service mesh
In HCX, the object that links a source compute profile to a destination one (together with their network profiles) and deploys paired service appliances, such as Interconnect and Network Extension, at both sites. Moving where appliances sit requires a resync, and adding further meshes scales out migration capacity.
- Datastore
A named pointer in the workspace to Blob, Azure Files or ADLS Gen2 storage that keeps the connection details, so code never needs to carry storage keys itself.
- WHERE
Limits a SELECT, UPDATE or DELETE to just the rows meeting a condition. Omit it, and the statement hits every row.
- Virtual machines
Infrastructure-as-a-service compute giving complete control of the operating system, making it a fit for lift-and-shift moves and for software relying on OS-level pieces like COM.
Related terms
- Deployment Cluster
Part of a VCF Operations HCX compute profile, naming where the Service Mesh appliances run: a cluster or resource pool and a datastore. Hosts there need a path to the vMotion and management or replication VMkernel networks of the Service Clusters, and the extended broadcast domains must be present on the distributed switch.
- Service Cluster
A VCF Operations HCX Compute Profile lists these: at the source they contain VMs awaiting migration, and at the destination they are where VMs land. Make sure the Deployment Cluster can get to the vMotion and Management/Replication VMkernel networks of each.