- Configure Fabric Groups – vRealize Automation Series Part 9
- Add vCenter Endpoint – vRealize Automation Series Part 8
- Configure vRealize Permissions – vRealize Automation Series Part 7
- Install vRealize Automation IaaS Installation – vRealize Automation Series Part 6
- Install vRealize Automation IaaS SQL 2014 Installation – vRealize Automation Series Part 5
- Install vRealize Automation IaaS Preparation – vRealize Automation Series Part 4
- Configure the vRealize Automation Appliance – vRealize Automation Series Part 3
- Deploy the vRealize Automation Appliance – vRealize Automation Series Part 2
- vSphere SSO or vRA Identity Appliance – vRealize Automation Series Part 1
- Workstation Home Lab Wrap-Up – On to vRealize Automation
Time for Fabric Groups, and no a fabric group is not what Grandma does on Saturday afternoons at the senior center. Fabric groups in the vRealize Automation / vCloud Automation Center world is a collection of resources, this tends to send folks who have been storage focused for a long time down a different path as they start thinking about zoning and switches.
There can be multiple fabric groups with different purposes, for example you may assign clusters to different business groups to ensure performance, or at least that one group does not “hog” all of the resources available (though as we’ll see later there are other ways to control that).
As this is a resource being configured, we again log in with someone that as the Infrastructure admin role, in our case the iaasadmin user :
- Click on the Infrastructure tab >> Groups >> Fabric Groups
- Click on New Fabric Group
- Provide a name for your fabric group, in my case I’ll use vxprt
- Assign a user to as a fabric administrator – remember we may have different groups using different fabrics and you may want to have someone in engineering manage their resources and a separate person in QA to manage the resources in their fabric group. Or you could have a single fabric group that is assigned to various users. The choice is yours. In my case I am going to assign the iaasadmin user as the fabric administrator. Start typing the name in, click the magnifying glass icon then click on the user
- In compute resources, you will see the cluster from the vCenter server you added when you added the vSphere endpoint, had you not followed the last blog post you would have no endpoint, thus no resources – unless you already knew to do that on your own of course! Select your cluster and click the OK button
For fun, click on New Fabric group again – did you think your cluster assigned to your previous admin group would still be available? Logic might suggests that once I assign a cluster to a fabric group I should not be able to reuse it, however fabric groups are not how we control resource consumption, they are used for administration by other users.
That’s it, pretty easy. If you like you can create multiple fabric groups to mimic what you might do in a production environment or play around with adding different clusters if you have those kinds of resources. In my next post we will setup machine prefixes and business groups – which have to be done in that order, you can’t create a business group without a machine prefix (seems out of order to me but hey I’m not a programmer).