VCAP6-CMA Deploy – Objective 1.5: Create Fabric Groups utilizing Reservations and Reservation Policies

Objective Overview

Objective 1.5: Create fabric groups utilizing reservations and reservation policies

  • Configure fabric group(s) for specific tenants
  • Allocate resources to a fabric group
  • Assign users the necessary permissions to provision reservations
  • Configure reservations for Business Groups
  • Configure reservation policies for all resource types

Objective Prerequisites

The following prerequisites are assumed for this Objective:

  1. A full deployed vRealize Automation 6.x solution (minimal or distributed).

Objective Breakdown

Configure Fabric Group(s) for specific Tenants

A Fabric Group consists of multiple Endpoints and is a way of grouping similar Compute Resources together.  An example maybe a Production vCenter Server with multiple VMware Clusters.  Each Cluster is considered a separate Compute Resource but they can be grouped into one or more Fabric Groups.  Also Fabric Groups can contain Compute Resources from multiple Endpoints.

The creation of a Fabric Group is the responsibility of the Infrastructure Administrator role.  The Fabric Group can be created within either the Default Tenant or in a specific Customer Tenants.  As part of the creation of a Fabric Group, the Fabric Administrator role is assigned and it is there job to manage the Compute Resources in a Fabric.

Navigate to the vRealize Automation Tenant Portal (https://vra.fqdn/vcac/org/<tenant>)

Log in using an account that has been assigned the Infrastructure Administrator role.

Click Infrastructure.

Click Groups > Fabric Groups.

Click New Fabric Group.

Enter a Name for the Fabric Group into the Name textbox and then click OK.

Note: Don’t worry we’ll be adding resources and Fabric admins over the next two sections of this Objective.

Allocate resources to a Fabric Group

OK so in the previous section we create an empty Fabric Group, now it’s time to configure the Fabric Group with some resources!

Note: You would normally add resources and Fabric Admins to the Fabric Group during its creation, but i’m just trying to cover the sections of this objective, hence i have split this up into three sections!

The following steps assumes you can navigate back to the Fabric Group page within the vRealize Automation Portal (if you can’t remember how to do this, see the section above).

Click on the Fabric Group we need to change.

Underneath Compute Resources,  check the checkbox next to the Compute Resources you want to include in this fabric group.

Click OK.

Assign users the necessary permissions to provision Reservations

The following steps assumes you can navigate back to the Fabric Group page within the vRealize Automation Portal (if you can’t remember how to do this, see the section at the beginning of this post).

Click on the Fabric Group we need to change.

Under Fabric Administrators, type the relevant user account information and click Search to locate the users/groups.

Click OK.

Configure Reservations for Business Groups

The creation of Reservations within a Fabric Group is the responsibility of the Fabric Administrator.  The Fabric Administrator is a System-Wide Role.  In this section i’m going to cover the creation of a vSphere Reservation, however the similar steps can be used for any type of Reservation against a Fabric Group with the right Compute Resources.

In vRealize Automation, a Reservation is the allocation and division of Compute Resources from a Fabric Group into smaller chunks.  However, unlike a vSphere Reservation, the Compute Resources (storage, network and memory) are not physically allocated to a Reservation.  it is just a indication of the maximum number of resources that could be consumed.  It is possible (but not recommended) to over provision resources using vRealize Automation Reservations.

Navigate to the vRealize Automation Tenant Portal (https://vra.fqdn/vcac/org/<tenant>)

Log in as a user with the Fabric Administrator role assigned.

Click Infrastructure.

Click Reservations > Reservations.

Click New Reservation > Virtual > vSphere (vCenter)

Select the Compute Resource from the dropdown and (if required) amend the auto-populated name within the Name textbox.

Note: we have not yet defined any Reservation Policies so we cannot choose one yet.  

Enter a numerical value into the Priority text box to indicate the relative priority of this Reservation against others.

Click the Resources Tab

Under Memory, enter a numerical value for the Reservation and under Storage, select one or more Datastore(s) or DataStore Cluster(s) to allocate to the Reservation and assign a relative priority.

Click the Network Tab

Under Network, check the Network Path checkbox next to each network you want to include in the Reservation.

Note: Ideally you would select a Network profile, but as we have not created any yet, we’ll leave the Network Profile dropdown empty for now.

Click Alerts.

Under Capacity Alerts option, select On.

Note: for this tutorial, we’ll leave the thresholds as their default values

Click OK.

Configure Reservation Policies for all resource types

A Reservation Policy is a way of restricting the deployment of a Blueprint to a subset of Reservations.  A Reservation Policy can include multiple different Reservations and the nature of the Blueprint will determine which Reservations are displayed during request time.  There are two main types of Reservation Policy, Compute and Storage.

Log in as a user with the Fabric Administrator role assigned.

Click Infrastructure.

Click Reservations > Reservation Policies.

Click New Reservation Policy.

Enter the name of the Reservation Policy into the Name text field, (optionally) enter a description into the Description text field and then click the Save icon.

Click New Storage Reservation Policy.

Enter the name of the Storage Reservation Policy into the Name text field, (optionally) enter a description into the Description text field and then click the Save icon.

Create additional Compute and Storage Reservation Policies as required.

Assigning a “Compute” Reservation Policy

Reservation Policy is assigned within a Reservation.  Therefore you can go back and update any Reservation you may have to include a Reservation Policy.

Assigning a Storage Reservation Policy

A Storage Reservation Policy is assigned to a Datastore or Datastore Cluster within the Compute Resources rather than a Reservation.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.