This is part 4 of my vRealize Automation 6.2 guide. This will focus on Endpoint and Fabric config.
Set up Administrators:
- First we need to log in to our vRA Appliance at https://FQDN/vcac/
- Click vSphere.Local under Tenants this is our default tenant.
- We now want to set up administrators for the various roles in vRA so click on Administrators and then add both a Tenant and Infrastructure Admin. I use a dedicated user for each and add my domain administrator (lab\administrator) to both, then click Apply.
NOTE: You would configure the Email server here also, but I don’t have any SMTP server in my lab so have skipped this step.
Set up Endpoints:
- Log out and then log back in as your Infrastructure Admin (mine is firstname.lastname@example.org) from here you can click the two small arrows in the top left and follow the steps to configure the Fabric.
- First step is to add a license, Click Infrastructure –> Adminstration –> Licensing, Click Add License and enter your license.
- Next step is to add credentials that will be used for our endpoints, click Credentials, then click New Credentials, enter the credentials thenclick the green arrow to save them. I have added 2 credentials one SSO user and one AD user, which should cover us for most endpoints we will use (again I have set up new accounts but you could use the default email@example.com and Domain\Administrator if you prefer).
- Next in My Goals, click Configure Endpoints, then New Endpoint –> Virtual –> vCenter
- Complete the fields and select the credentials we created earlier. Ensure you use the name vCenter here as this must match the vCenter Agent installed earlier and it is case sensitive.
Create Fabric Groups:
- The last step is to create a Fabric Group. Again in My Goals select Create Fabric Groups, enter a name and assign users as Fabric Administrators, I have a role just for this and add my firstname.lastname@example.org role that has access to everything.
- Once the Fabric Group is created log out, then log back in as the Fabric Admin (in my case email@example.com).
- Once logged in we will follow the bouncing ball and configure the fabric using the My Goals (click the two small arrows at the top left), and click Machine Prefixes. You can make up whatever you like here, then click the Green Arrow to save. If you use the same as me your first VM will be vRA001, then vRA002, etc, etc.
Create Reservation and Network Policies:
- Next we create a reservation, again click Create Reservations, then Reservation Policies, then click New Reservation Policy, and New Storage Reservation Policy, As shown below, and give them both a name.
- While we are here we should also create a Network Profile, I am going with an External network, which will connect to my existing network.
- We also need to set up some IP’s for the network profile.
Create a business group:
- Business groups are created by the Tenant Admin, so log in as the Tenant Admin (if you are using my naming convention this will be “firstname.lastname@example.org”). Again we are going to use the My Goals as the navigation is easier, so click the two arrows in the top left to show the My Goals panel:
- Most of the items in the goals for the Tenant Admin are not necessary as we are using the Default Tenant, and so far not setting up for multi tenancy, so we can skip to Create Business Groups.
- Enter a name for your Business Group, select the Default Machine Prefix we created earlier, and add the group manager roles for the business admin (in this case ACME_Admin), also add the Administrator that has access to everything if you have one, then set the user to ACME_User. We do need to set a destination for email here, so you can use anything even if it doesn’t actually work.
Create a Reservation:
Now that we have created our business group we need to create a reservation so the business group can use our resources.
- Log in as the Fabric Admin (email@example.com if following my naming convention)
- Click on Reservations then New Reservation –> Virtual –> vSphere
- We then need to set the Priority, Reservation Policy, and Business Group, but all other values should be populated for you, notice the Business Group, and Reservation Policy we created earlier.
- We now need to allocate both memory and storage resources to the reservation
- Network resources are next, and we allocate the network “external” we created in Part 4
- You can set alerts thresholds on the next tab but I am going to skip this.
Congratulations now everything is configured for your tenants to start working, this will be covered in Part 5.
Please check out the other articles in this series and if you have any feedback please leave a comment.