Here we configure
- Fabric Groups
- Machine Prefixes
- Business Groups
What are Fabric Groups ?
Let me quote VMware here
An IaaS administrator can organize virtualization compute resources and cloud endpoints into fabric groups by type and intent. One or more fabric administrators manage the resources in each fabric group.
Fabric administrators are responsible for creating reservations on the compute resources in their groups to allocate fabric to specific business groups. Fabric groups are created in a specific tenant, but their resources can be made available to users who belong to business groups in all tenants.
So .. Basically like Provider / Organization vDCs in vCloud all thrown together 😀
We have created a connection to our vCenter using the vSphere agent and the vCenter Endpoint. Now imagine having 10 vCenter, maybe you even connected AWS to your vCAC instance and now you want to assign a customer, or tenant, some resources.
This is what Fabric Groups do. You basically tell vCAC which customer / tenant has access to which resources / vCenter etc.
Let’s get started.
Again as Infrastructure Admin, browse to
Infrastructure > Groups > Fabric Groups
and click New Fabric Group
Give it a name and description and select the cluster of resources you’d like to use.
Note: If you do not see any resources, it can take an hour for the inventory to be updated. You can also just reboot the IaaS Server or restart all services.
Next, Machine Prefixes. In order to even see the option you need to logoff / login again (not even kidding)
This is essentially just this – a prefix for VMs deployed with vCAC. In vCloud Director you can easily see which machines have been created using vCD as they are under a specific vCloud Director Resource Pool.
Here however, you can deploy VMs straight into your root vCenter – looking at the vCenter you wouldn’t even know they have been deployed with vCAC.
With a prefix you make it not just easier to see when looking at the inventory, but you can search easier for vCAC deployed VMs.
Anyway, once logged in again, browse to
Infrastructure > Blueprints > Machine Prefixes
Enter any prefix you like – such as vcac. The number of digits depends a little on how many VMs you’d expect. 3 digits obviously gives you 999 and so on. Next Number is at which number it should start counting.
Three digits, starting at 1 would mean the first starts at vcac001 and so on.
A Business Group is a connection between users and resources. For example one set of resources is given to a Buisness Group Development, or Production etc.
Infrastructure > Groups > Business Groups and click New Business Group
Populate the necessary fields such as name, prefix and email notification. You can find the email setup in my other article HERE.
I don’t have any other users so I am using my newly created user mike. This user will get emails regarding approval and so on.
As you can see, the user does not have any resources yet, so next step
Infrastructure > Reservations > New Reservation >Virtual > vSphere (vCenter)
Select your resources from the dropdown, give it a name (or use the auto-generated one), select your Business Group and give it a priority (1 = only one I got at the moment)
Move over to Resources
Assign RAM and Storage here.
You will only see portgroups which are on a vDS (Virtual Distributed Switch). In this case, the only portgroup on the vDS is my External Network. click OK
When you login with your created user and check the Business Groups you can see the created allocations
vCAC Install Content
1. vCAC Requirements
2. vCAC Install Identity Appliance
3. vCAC Install vCAC Appliance
4. Install vCAC IaaS Components
5. Adding a Tenant
6. Configure Agents & Endpoints
7. Configure Resource Allocations
8. Create Blueprints
9. Create Service Catalogs
10. Create Entitlements & Testing
11. Other vCAC Bits (SMTP etc.)