If you have existing vCloud organizations, and you want the client to use a specific org, you can assign them to an org using client assignments (mapping).  This allows you to not only assign an org, but also external networks, org vDC’s, and Edge Gateways.

Mapping organizations

To map an organization to a client, click on “My Services” select your vCloud Automator, and click on ”Client Management”.  Select which Provider vDC should be used in order to display the relevant organizations.

You will now see a list of all organizations within the provider vDC. Each org will also display the number of org vDCs, vApps, Edge Gateways, VMs, clients are assigned to that org.  Unassigned means no client is currently assigned to the org.

Assign a client to an org by clicking on the person icon located under Actions. This will open the associate account screen.

There will be a list of all available clients that have not been assigned to an org. Select a client and then click submit.

Within a few seconds, the client will be assigned to that org.  You can verify if the client mapped correctly by looking under the company name column.

Now you can map Solutions to the client. Click on the plug icon to open the map existing services window.  Make sure that the Org vDC you want to map is within the solution’s resources range or capacity, and is using the supported storage policy.

For example, there is an Allocation vDC Solution with a CPU range of 1GHz – 10GHz, RAM 1GB – 10GB, and a Tier 2 Policy 10GB – 1000GB. Only Org vDCs that fall within that range can be associated to that solution. All 3 specs must be within the range.

Select which solution type you want to map - Allocation, Pay-As-You-Go, Reservation, or Edge Gateway. Once selected, choose a solution.  If the org vDC matches the solution type and is within the solution’s ranges, your org vDC will appear.

You can select any or all org vDC’s to map. If you select multiple org vDCs, they will all use the same solution.

Once completed, click “Save”.

Mapping external network

After mapping your solutions, you can map external networks to the client. Click on “External Networks” to see a list of all external networks from the provider vDC you selected.

Click on the  icon and select which clients will use this external network. Clients can use multiple external networks.

Mapping NSX edge gateway

If the org vDC you mapped also has an Edge, you must also map it to the client or they will not be able to use it. Mapping an Edge Gateway is very similar to mapping org vDCs.

You will need an Edge Solution that has the correct size to map to an Edge. For example, if the Edge you’re mapping is a Compact size, the Solution must have Compact as one of its choices.

Your client will now be able to access the org you assigned to them including all Oog vDCs that have a solution, vApps, VMs, org networks, and catalogs associated to the org vDC, along with any Edges belonging to the org vDC.

Unmap solutions

If you no longer want a client to use a certain org vDC or Edge, or you want to remove the client altogether, they can be unmapped.

Begin by clicking the no plug icon.  This will open the Unmap Existing Services window.

Select the solution type to unmap, then select the Org vDC you want to unmap from. Finally, select the Org vDCs to unmap.

Click unmap once you’re satisfied with your selections.

Once you unmap an org vDC, the client will no longer have access to it, or be able to see it.  Note that this will not remove the org vDC from your vCloud.