Last time we laid out the general approach of our automation framework.  Today we will be completing some of the per-requisite technical tasks to enable vROPS to apply a layer of governance and detection to our framework.

The other posts in this series can be found below:

Day Two Automation Self Service Framework – Part 1

Day Two Automation Self Service Framework – Part 2 (this post)

Overview

  1. Create the needed vSphere tag and tag category.
  2. Install the vRO Management Pack and configure the vROPS and VRO interaction.
  3. Connect vRO to the target vCenters.

Create the needed vSphere tag and tag category

We will be using vSphere tags to inform vROPS of which machine our snapshot exception policy should apply to.  Creating a vSphere tag is very straight forward.  After logging into vCenter, navigate to the Menu->Tags & Custom Attributes section

tagsandattributes

We will be creating a new tag category named monitoringException.  Be sure to allow multiple cardinality, which allow a given object to have multiple monitoring exceptions.  I also suggest selecting all object types, as it allows for the most flexibility down the road.

category

Next create our tag, which we will name snapShotLifetime, and we will assign it to the category we just created.

tag

Install the vROPs Management Pack and configure the connection to vRO

The install of the vROPS management pack for vRO is fairly straight forward.  First you will need to download it from the VMware Solution Marketplace.  After you download it you can follow my hack instructions below, or follow the official documentation.

  1. After logging into vROPS as an admin, navigate to: Administration->Repository->Add/Upgrade
  2. Select the pak file you downloaded , click Upload, and then walk through the remainder of the installer.
  3. Configure the Account for vROPS to interact with vRO by navigating to: Administration->Other Accounts->Add Account. 
    1. Select vRealize Orchestrator as the account type.  Fill in the prompt with the appropriate details for your environment.
    2. Click Validate.  If validation is successful, click Add.
  4. Now have to download content from vRO to vROPS. This let’s us set up workflows from vRO as actions in vROPS.
    1. Navigate to Environment-> vRealize Orchestrator-><Cloud Account Name from the previous step>
    2. Select Actions->Configure Package Discovery
    3. Once the task finishes, you will see a package list in the vRO inventory
  5. The last content related step is to import vROPS workflows into vRO. This will add some workflows and actions to vRO to enable a variety of automated actions.
    1. Return to the Actions menu, and select Import vRealize Operations Remediation Package to vRO.

Configure the vRO connection to the target vCenters

There are two ways you can configure, vRO to connect to vCenter, adding a vCenter endpoint in vRO parlance: via the vROPS interface or more traditionally through the vRO interace. We will go over the path of using vROPS to do this today.

  1. Navigate to same menu in vROPS in in the previous section: Environment-> vRealize Orchestrator-><Cloud Account Name from the previous step>
  2. Select the option: Add a vCenter server instance to vRealize Orchestrator
    1. Fill in the details for the vCenter you want to connect to, repeating the process for each vCenter.
  3. Validate that the connection has been established by looking at the recently completed workflows in vRO.

That’s it for today.  We have now established the connection between vRO and VROPS, which enables vROPS to trigger a vRO workflow when an alert is triggered with an automated action enabled for it, and we have also connected vRO to vCenter.

In the next post we will look at the vRO workflows involved in this process.

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.