Now we have a Fabric Group – basically pulled our cluster and its resources into vRealize Automation. If you know vCloud Director – a Fabric Group effectively is a Provider vDC.
Next we need to carve up the resources. It doesn’t necessarily mean that we want to give users the whole cluster, right.
That is where Reservations come in. Another useful thing to configure – Reservation Policies.
A Reservation Policy can be used to for example link a reservation with a blueprint. Imagine you have different blueprints, Linux and Windows ones – but you want different reservations for different workloads.
So to future proof my environment, I do create a reservation policy first.
You need to be Fabric Admin to do this. As you know I added both, my AD user and the configurationadmin as Fabric Admin.
Navigate to Infrastructure > Reservations > Reservation Policies
The add name and description and click OK
Now navigate to Reservations
Click New > vSphere
Enter a name, select your tenant (again, only got the default tenant myself), business group and reservation policy.
Set a priority if needed.
Move to the tab resources
- Compute Resource (taken from the Fabric Group)
- Machine Quota
- Maximum allowed of virtual machine memory used
- Storage and set maximum amount of storage alowed
Move to the tab Network and select the appropriate network path (port group) and newly created network profile.
Configure alerts if you wish – I don’t have email setup (yet) so I will skip this step
Done .. Easy ey 😀