Just a little reminder about the configuration of vRA
Tenant creation (System administrator privilege required for this operation)
- Create local users and assign Tenant Admin permission
Tenant configuration (Tenant administrator privilege required for this action)
- Add a directory to bind an AD domain
- To enable HA, add a Identity Provider using this time the second vRA node as a connector and the VIP of the vRA node as the new hostname.
- Create custom groups (System or tenant administrator privilege required for this action)
- Assign IaaS All needed rights (including tenant admin, IaaS archi, at least)
- Provide IaaS administrator privilege to the newly created custom group
- If needed, plan access policies (to set network range to allow authentication etc…)
Create endpoint (tenant administrator privilege required for this action)
- name must match with the agent name installed on IaaS server
- Restart vcac vCenter agent to force an inventory of vCenter resources
- Compute resource must be available once data have been collected
Make sure that no error appears in IaaS logs :
- On the server in c:\program files (x86)\vmware\vcac\server\logs\error.log
- On the portal, as a IaaS admin, you can go to Infrastructure > Monitoring > Log
Tips : If cluster storage does not appear, you can think about an issue with MSDTC between SQL and IaaS |
- Create a Fabric Group (IaaS administrator privilege required for this action)
- Select Fabric group administrators
- Create a Machine Prefix (Fabric Group administrator privilege required for this action)
- Create a business group (Tenant administrator privilege required for this action)
- Create a reservation for the business group (Fabric Group administrator privilege required for this action)
- Make sure this new reservation is enabled (it is by default)
- Provide a machine quota, RAM, Storage, Network
Blueprint creation (IaaS Architecte privilege required for this action)
- Publish it to make it visible as a catalog item
Catalog creation (Tenant administrator privilege required for this action)
-
- Create a catalog service
- Make sure it is active (by default)
- Add a catalog item
- Select a blueprint to make it available to link it to the proper service
- Entitle users for the new catalog
- Make sure the status is active (draft by default)
- Select a business group (revert no permitted on this setting once the entitlement has been saved)
- Select group and users
- Select service, catalog items and allowed actions on them
Test and enjoy 🙂
November 17th, 2017 by axel