Migration of old metadata solution to new Edge Cluster solution

Products

• VMware NSX

Issue/Introduction

Edge Cluster is logical object driving vCloud Director placement decision of Org VDC Edge Gateways nodes (VMs). It consists of a compute resource pool and a storage policy. The Edge Cluster is created by the Provider and then assigned to Org VDC by assigning the Edge Cluster as a primary or secondary (for High Availability) to the Org VDC Network Profile. This means that an Edge Cluster can host Edge Gateways from different Tenant Organization VDCs.

Resolution

In order to migrate the old metadata solution to the new edge cluster solution follow,

1. Remove the existing resource pool that was specified in the metadata from the PVDC and remove the metadata from the PVDC.
2. Create the Edge Cluster.

NOTE: In the metadata solution, a child resource pool would get created under the resource pool specified in the metadata when deploying edges (System VDC…). If you want full zero downtime, then you should use that child resource pool id for the Edge Cluster. Otherwise you can use the main resource pool id and when you redeploy the Edge Gateway it will move to that main resource pool (recommended). 

3. Assign the Edge Cluster to the Org VDC by updating the VDC Network Profile.
4. Redeploy the Edges if necessary.