Yes, that's correct. You would define:
1x Network Profile and 1x Compute Profile for Melbourne. Then create a Service Mesh using the Melbourne Compute Profile.
1x Network Profile and 1x Compute Profile for Sydney. Then create a Service Mesh using the Sydney Compute Profile.
Ensuring that the networks in each profile reflect what is configured in each cluster.
Original Message:
Sent: May 11, 2025 08:34 AM
From: sumit bnd
Subject: HCX Service Mesh
Hi Team,
I have a requirement to migrate VMs from on-prem to Azure VMware Solution (AVS). In our on-prem environment, we have a single vCenter server managing two separate clusters - one located in Melbourne and the other in Sydney. Each cluster is configured with distinct Management and vMotion networks.
Given this setup, I would like to confirm the correct approach for network and service mesh configuration. Based on my understanding, I will need to:
Deploy two separate service meshes (one for each cluster), and
Create two network profiles and two compute profiles accordingly to match the network configurations of Melbourne and Sydney clusters.
Could you please confirm if this approach is correct, or advise if there's a more efficient alternative?