vCD 9 – Metadata to control Edge Placement

With vCD9 now GA, I can post this!

One of the things our team has been diligently working on is the ability to specify a host cluster to be an edge cluster for edge deployments. This is a recommended design methodology in NSX, especially for providers to control scalability and allow for proper North/South traffic. I had a conversation with one of our SP’s who was beta testing vCD9 and this came up in discussion.

In vCD9, we will have the ability to utilize metadata to force edge placement in a pvDC. Associated KB will be posted shortly.

Summary steps:

  1. In vCenter, create the cluster that will be holding said Edges.
  2. We need to get the resource pool MoRef now. Use the Managed Object Browser or query by running the ‘{url}/api/admin/extension/providervdc/{pvdcId}/resourcePools’ query). You need to discover the name and Managed Object ID of the resource pool. The name will be used to attach the resource pool to the pVDC and the Managed Object ID for the metadata you create.
  3. In vCD, create the provider vDC, then attach another resource pool to it, specifying the name of the resource pool backed by the Edge Cluster you set up in Step 1. New org vDC’s will have access to this RP by default.
  4. Click on the Metadata tab of the Provider vDC to create the following metadata for the resource pool object.
    1. placement.resourcepool.edge = resource-pool-Managed-Object-ID
    2. For example,  placement.resourcepool.edge = respool-12

Done. With this tag in place, new Edges will be automatically created in this resource pool while no other vApps will be placed there. Previous Edges can be redeployed into this RP now also.

Leave a Reply

Your email address will not be published. Required fields are marked *