VCP6-CMA Section 5: Allocate and Manage vRealize Automation Resources

Contents:

Objective 5.1: Create and Manage Fabric Groups

Add and configure endpoints for vSphere and vRealize Automation

  •  IaaS Administrators can create endpoints
  • A vSphere proxy agent must be installed
  • The endpoint name given to the vSphere proxy agent  must match the name given to the vSphere proxy agent during installation
  • Create the appropriate credentials
  • To create vSphere endpoint:
    • Log in as an IaaS Administrator
    • Select Infrastructure > Endpoints > Endpoints
    • Select New Endpoint > Virtual > vSphere
    • Enter a Name
      • This must match the name provided to the proxy agent during installation
    • Enter a description
    • Enter the vCenter SDK url
      • https://vcenter.company.local/sdk
    • Select the correct credentials for the proxy agent
    • If required, select Specify manager for network and security
      • This is out of the scope of this objective, but has been noted in previous sections
    • Add any custom properties
    • Click OK

Map compute resources to endpoints

  • Typically you would map a compute resource to an endpoint by installing the appropriate agent, then configuring the endpoint with the appropriate credentials in vRA
  • Once the initial data collection task completes you should be able to see the compute resource and assign it to a fabric group

Assign correct permissions to manage fabric groups

  • IaaS Administrators can create fabric groups and assign compute resources
  • They also can assign Fabric Group Administrators
  • Fabric Group Administrators are also responsible for creating reservations on the compute resources in their groups to allocate resource to business groups
  • To assign users as Fabric Group Administrators
    • Log in as an IaaS Administrator
    • Select Infrastructure > Groups > Fabric Group
    • Select Infrastructure > Groups > Fabric Group
    • Select a Fabric Group
    • Enter users and/or groups in the Fabric Administrators text box
    • Click OK

Collect compute resource data

  • You collect compute resource data by running Data Collections
  • Data collection occurs automatically at regular intervals
  • IaaS Administrators can manually initiate data collection for infrastructure source endpoints and fabric administrators can manually initiate data collection for compute resources.
  • Data Collection Types include:
    • Infrastructure Source Endpoint Data Collection
      • Updates information about hosts, templates and ISO images for virtualization environments
      • Updates regions and machines provisioned on them for Amazon
      • Updates installed memory and CPU count for physical machines
    • Inventory Data Collection
      • Updates the record of the VMs tied to a compute resource
      • Also records missing machines
    • Performance Data Collection (vSphere compute resource only)
      • Avg CPU, storage, memory and network usage for each VM discovered through inventory data collection
    • vCNS Inventory data collection (vSphere compute resources only)
      • Updates information related to vCNS and NSX
      • Security groups and load balancing
    • WMI data collection (Windows compute resrouces only)
      • Management data for each windows machines
      • WMI agent must be installed on the Manager Service Host
    • Cost data collection (Compute resources managed by vRealize Business Standard Only)
      • CPU, memory and storage costs for each compute resrouce managed by vRealize Business Standard Edition

Monitor resources

  • Fabric Administrators manage the resource usage of the compute resources and reservations they own
  • Tenant Administrators and Business Group Managers manage the resource usage of the business group they own
  • Resource Terminology
    • Physical
      • Indicates the actual memory or storage capacity of a compute resource
    • Reserved
      • Indicates the machine quota, memory and storage set aside for a reservation
      • For physical machines, this term indicates machines that are reserved for a reservation but not yet provisioned
    • Managed
      • For physical machines this indicates that the machine is provisioned and under vRA management
    • Allocated
      • Indicates the machine quota, memory, or storage resources actively being consumed by provisioned machines
    • Used
      • For virtual provisioning this indicates the amount of storage in use by provisioned machines
      • When standard storage is used, storage used and allocated are the same
      • When space efficient storage technology is used, storage used is less than storage allocated
      • This is because the machines consume only the amount of space they require!
    • Free
      • For virtual provisioning, this is the unused physical capacity on a storage path
Resource Monitoring Scenario Privileges Required Location
  • Monitor consumed physical storage and memory and determine free resource
  • Monitor the number of reserved and allocated machines provisioned on each compute resource
Fabric Administrator Infrastructure > Compute Resources > Compute Resources
  • Monitor physical machines that are reserved for use by not yet provisioned
Fabric Administrator Infrastructure > Machines > Reserved Machines
  • Monitor machines that are currently provisioned and managed by vRA
Fabric Administrator Infrastructure > Machines > Managed Machines
  • Monitor allocated storage, memory and machine quota and determine the available capacity
Fabric Administrator Infrastructure > Reservations > Reservations
  • Monitor consumed storage, memory and machine quota for business groups and determine the remainingcapacity
  • Tenant Administrator
    • Monitor resource usage for all groups in the tenant
  • Business Group Manager
    • Monitor resource usage for groups that you manage
Infrastructure > Groups > Business Groups

Objective 5.2: Create and Manage Reservation

Create and manage reservations

  • Fabric Administrators allocate resources to business group members by creating reservations
  • To create a reservation for virtual platforms, log in to the vRA console
    • Select Infrastructure > Reservations > Reservations
    • Select New Reservation > Virtual
    • Select the compute resource to which you want to associate with
    • Fill in the appropriate information
  • Cloud Reservations depend on the appropriate endpoint being configured
  • To create a reservation for cloud platforms, log in to the vRA console
    • Select Infrastructure > Reservations > Reservations
    • Select New Reservation > Cloud
    • Select the compute resource to which you want to associate with
  • Both reservation types can be managed from the vRA console
    • Select Infrastructure > Reservations > Reservations
    • Select the reservation you want to manage
  • You can also view machines associated to this reservation by hovering over the reservation and selecting View Virtual Machines

Specify reservation information

  • Select a reservation from the Copy from existing reservation to import settings
    • You can amend the settings as required for the new reservation
  • Or you can configure manually
    • Select a Compute Resource
      • Only templates located on the cluster you select are available for cloning
    • Enter a reservation name
      • This will be auto generated, but can be changed
    • Select a Tenant
    • Select a Business Group
    • If required, select a Reservation Policy
    • If required, enter a machine quota
      • Only powered on machines count towards the quota
      • Leave blank for unlimited
    • Enter a priority
    • Ensure that Enable this reservation is selected
    • Add any custom properties
    • You will now need to configure memory, storage and networking from the Resources Tab
    • For storage, you can use SDRS storage or individual datastores
      • Select a FlexClone endpoint if required
        • The endpoint is visible only if a NetApp ONTAP endpoint exists
      • Enter the amount of allocated storage in to This Reservation Reserved
    • For networking, select a path for machines provisioned on this reservation
      • If required, select a network profile
        • Network profiles must be configured in order to use this
      • More than one network path can be selected on a reservation but only one is used when provisioning
    • If required, configure alerts

Select a reservation for a cloud based virtual machine

  • Reservation must be select from the reservations that belong to the business group
  • The reservation must satisfy the following criteria
    • Must be of the same platform type
    • Must be enabled
    • Must have enough capacity remaining in it’s quota
    • Must have the security groups specified in the request
    • Must be associated with a region that has the machine image specified in the blueprint
    • AWS – reservation must match the network type (VPC or non-VPC)
    • If the provider supports network selection and the blueprint has specific network settings, the reservation must have the same networks
    • If the blueprint specifies a reservation policy, the reservation must belong to that reservation policy
    • If no reservation exists that meets all of the selection criteria, the request fill fail
    • If multiple reservations meet the criteria, the following logic applies
      • Reservations with higher priority are selected over reservations with lower priority
      • If multiple reservations have the same priority, the reservation with the lowest percentage of its quota allocated is selected
      • If multiple reservations have the same priority, machines are distributed amongst them in a round robin fashion

Determine where reservations have been over allocated

Troubleshoot reservation over-allocation

 

Objective 5.3: Create and Manage Reservation Policies

Create, configure and assign one or more reservations to a reservation policy

  • Create and configure the reservation policy as per the steps in objective 5.2
  • Reservation policies provide a way of controlling how reservation requests are processed
  • Often used to collect resources in to groups or service levels
  • Some uses include
    • Ensure virtual machines are provisioned on storage that supports NetApp FlexClone
    • Restrict Provisioning of cloud machines to a specific region
  • You can add multiple reservations to a reservation policy but a reservation can only belong to one policy
  • A reservation policy can include reservations of different types but only reservations that match the blueprint are considered when selecting a reservation for a request.
  • Fabric Administrators can create Reservation policies
  • To create a reservation policy
    • Select Infrastructure > Reservations > Reservation Policies
    • Click New Reservation
    • Enter a name
    • Click the save icon
  • To assign a reservation policy to a reservation
    • Select Infrastructure > Reservations > Reservations
    • Point to a reservation and click edit
    • Select the reservation to assign from the reservation policy drop-down menu
    • Click OK

Create, configure and assign a reservation policy to one or more blueprints

  • You can assign a single reservation policy to more than one blueprint
  • A blueprint can only have one reservation policy
  • Tenant Administrators and Business Group Managers can assign reservation Policies to a blueprint
    • Select Infrastructure > Blueprints > Blueprints
    • Select a blueprint and click edit
    • Select a Reservation Policy from the Reservation policy drop-down menu
    • Click OK

Create and assign a storage reservation policy

  • Fabric Administrators create storage reservation policies to allow Tenant Administrators and Business Group Managers to assign the volumes of virtual machines to different datastores
  • To create a storage reservation policy, login as a Fabric Administrator
    • Select Infrastructure > Reservations > Reservation Policies
    • Click New Storage Reservation Policy
    • Enter a name and description
    • Click Save
  • After the reservation policy is created, you must populate it with datastores
  • A datastore can belong to only one storage reservation policy
  • Add multiple datastores to create a group of datastores for use with a blueprint
  • To assign a storage reservation policy
    • Select Infrastructure > Compute Resources > Compute Resources
    • Point to a compute resource and click edit
    • Click the configuration tab
    • Click edit net to the datastore that will be added to the policy
    • Select your storage reservation from the storage reservation policy column drop-down
    • Click Save
    • Click OK