Vro on The IT Hollow

Execute vRO Workflow from AWS Lambda

Tue, 26 Jul 2016 14:00:15 +0000

The use cases here are open for debate, but you can setup a serverless call to vRealize Orchestrator to execute your custom orchestration tasks. Maybe you’re integrating this with an Amazon IoT button, or you want voice deployments with Amazon Echo, or maybe you’re just trying to provide access to your workflows based on a CloudWatch event in Amazon. In any case, it is possible to setup an Amazon Lambda call to execute a vRO workflow. In this post, we’ll actually build a Lambda function that executes a vRO workflow that deploys a CentOS virtual machine in vRealize Automation, but the workflow could really be anything you want.

Add Custom Items to vRealize Automation

Tue, 05 Jul 2016 14:14:41 +0000

vRealize Automation lets us publish vRealize Orchestrator workflows to the service catalog, but to get more functionality out of these XaaS blueprints, we can add the provisioned resources to the items list. This allows us to manage the lifecycle of these items and even perform secondary “Day 2 Operations” on these items later.

For the example in this post, we’ll be provisioning an AWS Security group in an existing VPC. For now, just remember that AWS Security groups are not managed by vRA, but with some custom work, this is all about to change.

vRealize Automation 7 - Deploy NSX Blueprints

Wed, 09 Mar 2016 15:10:20 +0000

In the previous post we went over how to get the basics configured for NSX and vRealize Automation integration. In this post we’ll build a blueprint and deploy it! Let’s jump right in and get started.

Blueprint Designer

Login to your vRA tenant and click on the Design Tab. Create a new blueprint just like we have done in the past posts. This time when you are creating your blueprint, click the NSX Settings tab and select the Transport zone. I’ve also added a reservation policy that can help define with reservations are available for this blueprint.

vRealize Automation 7 - NSX Initial Setup

Mon, 07 Mar 2016 15:01:03 +0000

Its time to think about deploying our networks through vRA. Deploying servers are cool, but deploying three tiered applications in different networks is cooler. So lets add VMware NSX to our cloud portal and get cracking.

The first step is to have NSX up and running in your vSphere environment. Once this simple task is complete, a Distributed Logical Router should be deployed with an Uplink interface configured. The diagram below explains what needs to be setup in vSphere prior to doing any configurations in vRealize Automation. A Distributed Logical Router with a single uplink to an Edge Services Gateway should be configured first, then any new networks will be built through the vRealize Automation integration. While the section of the diagram that is manual, will remain roughly the same throughout, the section handled by vRealize Automation will change often, based on the workloads that are deployed. Note: be sure to setup some routing between your Provider Edge and the DLR so that you can reach the new networks that vRA creates.

vRealize Automation 7 – XaaS Blueprints

Mon, 29 Feb 2016 15:03:07 +0000

XaaS isn’t a made up term, well maybe it is, but it supposed to stand for “Anything as a Service.” vRealize Automation will allow you to publish vRO workflows in the service catalog. This means that you can publish just about any thing you can think of, and not just server blueprints. If you have a workflow that can order your coffee and have it delivered to you, then you can publish it in your vRA service catalog. Side note, if you have that workflow, please share it with the rest of us.

vRealize Automation 7 - Load Balancer Rules

Wed, 24 Feb 2016 15:15:32 +0000

In a previous post we went over installing an Enterprise Install of vRealize Automation behind a load balancer. This install required us to setup a Load Balancer with three VIPs but also required that we only had one active member in each VIP. A load balancer with a single member doesn’t really balance much load does it?

After the installation is done, some modifications need to be made on the Load Balancer. The instructions on this can be found in the official vRealize Automation Load Balancing Configuration Guide if you want to learn more. There are several examples on how to setup load balancing on an F5 load balancer and NSX for example. This post will focus on a KEMP load balancer which is free for vExperts and it will all be shown through with GUI examples.

vRealize Automation 7 – Enterprise Install

Mon, 22 Feb 2016 15:09:48 +0000

OK, You’ve done a vRealize Automation 7 simple install and have the basics down. Now it’s time to put your grown up pants on, and get an enterprise install done. This is a pretty long process, so be ready, but trust me, this is much better in version 7 than in the past.

Load Balancer

To start with, you will want to configure your load balancer. An enterprise install means that you’ll want at least two of each type of service so that you can protect yourself from a failure. There are three Virtual IPs (VIPs) that should be created prior to starting your install. The table below lists an example list of VIPs with their associated members and ports.

vRealize Automation 7 – Custom Actions

Mon, 15 Feb 2016 15:31:16 +0000

We’ve deployed a virtual machine from a vRA blueprint, but we still have to manage that machine. One of the cool things we can do with vRealize Automation 7 is to add a custom action. This takes the virtual machine object and runs a vRealize Orchestration blueprint against that input. We call these actions “Day 2 Operations” since they happen post provisioning.

To create a new custom resource action go to the Design Tab –> Design –> Resource Actions. Click the “New” button to add a new action.

vRealize Automation 7 - Custom Properties

Wed, 10 Feb 2016 15:09:39 +0000

Custom Properties are used to control aspects of machines that users are able to provision. For example, memory and CPU are required information that are necessary for users to deploy a VM from a blueprint. Custom properties can be assigned to a blueprint or reservation to control how memory and CPU should be configured.

Custom properties are really powerful attributes that can vastly change how a machine behaves. I like to think of custom properties as the “Windows Registry” of vRealize Automation. Changing one property can have a huge effect on deployments.

vRealize Automation 7 – Subscriptions

Mon, 08 Feb 2016 15:05:14 +0000

In vRealize Automation 7 a new concept was introduced called a “Subscription.” A subscription is a way to allow you to execute a vRealize Orchestrator workflow based on some sort of event that has taken place in vRA. Simple idea huh? Well some of you might be thinking to yourself, “Yeah, this is called a stub, Duh!” The truth is that stubs are still available in vRealize Automation 7 but are clearly being phased out and we should stop using them soon because they are likely to not be around in future versions. The idea of an event subscription is a lot like a stub when in the context of machine provisioning, but there are a lot more events that can be triggered than the stubs that have been around in previous versions. Let’s take a look.

vRealize Automation 7 – Manage Catalog Items

Tue, 02 Feb 2016 15:05:37 +0000

You’ve created your blueprints and entitled users to use them. How do we get them to show up in our service catalog? How do we make them look pretty and organized? For that, we need to look at managing catalog items.

Log in as a tenant administrator and go to the Administration Tab –> Catalog Management –> Catalog Items. From here, we’ll need to look for the blueprint that we’ve previously published. Click on the blueprint.

vRealize Automation 7 – Entitlements

Mon, 01 Feb 2016 15:01:13 +0000

An entitlement is how we assign users a set of catalog items. Each of these entitlements can be managed by the business group manager or a tenant administrator can manage entitlements for all business groups in their tenant.

To create a new entitlement go to Administration tab –> Catalog Management –> Entitlements. Click the “New” button to add a new entitlement.

Under the General tab, enter a name for the entitlement and a description. Change the status to “Active” and select a Business Group. Note: If only a single business group has been created, this will not be selectable since it will default to the only available group. Then select the users who will be part of this entitlement.

vRealize Automation 7 – Blueprints

Thu, 28 Jan 2016 15:10:13 +0000

Blueprints are arguably the thing you’ll spend most of your operational time dealing with in vRealize Automation. We’ve finally gotten most of the setup done so that we can publish our vSphere templates in vRA.

To create a blueprint in vRealize Automation 7 go to the “Design” tab. Note: If you’re missing this tab, be sure you added yourself to the custom group with permissions like we did in a previous post, and that you’ve logged back into the portal after doing so.

vRealize Automation 7 – Custom Groups

Thu, 28 Jan 2016 15:05:40 +0000

If you’ve been reading the whole series of posts on vRealize Automation 7, then you’ll know that we’ve already been setting up roles in our cloud portal, but we’re not done yet. If you need any permissions besides just requesting a blueprint, you’ll need to be added to a custom group first.

To create a custom group, login as a tenant administrator and go to the Administration Tab –> Users and Groups –> Custom Groups. From there click the “New” button to add a new custom group.

vRealize Automation 7 – Services

Tue, 26 Jan 2016 15:05:21 +0000

Services might be a poor name for this feature of vRealize Automation 7. When I think of a service, I think of some sort of activity that is being provided but in the case of vRA a service is little more than a category or type. For example, I could have a service called “Private Cloud” and put all of my vSphere blueprints in it and another one called “Public Cloud” and put all of my AWS blueprints in it. In the screenshot below you can see the services in a catalog. If you highlight the “All Services” service, it will show you all blueprints regardless of their service category. Otherwise, selecting a specific service will show you only the blueprints in that category.

vRealize Automation 7 – Reservations

Mon, 25 Jan 2016 15:16:53 +0000

vRealize Automation 7 uses the concept of reservations to grant a percentage of fabric group resources to a business group. To add a reservation go to Infrastructure –> Reservations. Click the “New” button to add a reservation and then select the type of reservation to be added. Since I’m using a vSphere Cluster, I selected Virtual –> vCenter. Depending on what kind of reservations you’ve selected, the next few screens may be different, but I’m assuming many people will use vSphere so I’ve chosen this for my example.

vRealize Automation 7 – Business Groups

Thu, 21 Jan 2016 15:15:27 +0000

The job of a business group is to associate a set of resources with a set of users. Think of it this way, your development team and your production managers likely need to deploy machines to different sets of servers. I should mention that a business group doesn’t do this by itself. Instead it is combined with a reservation which we’ll discuss in the next post. But before we can build those out, lets setup our business groups as well as machine prefixes.

vRealize Automation 7 – Fabric Groups

Tue, 19 Jan 2016 15:09:39 +0000

In the last post we setup an vCenter endpoint that defines how our vRealize Automation solution will talk to our vSphere environment. Now we must create a fabric group. Fabric Groups are a way of segmenting our endpoints into different types of resources or to separate them by intent. These groups are mandatory before you can build anything so don’t think that since you don’t need to segment your resources, that you can get away with not creating one.

vRealize Automation 7 – Endpoints

Mon, 18 Jan 2016 15:06:46 +0000

Now that we’ve setup our new tenant, lets login as an infrastructure admin and start assigning some resources that we can use. To do this we need to start by adding an endpoint. An endpoint is anything that vRA uses to complete it’s provisioning processes. This could be a public cloud resource such as Amazon Web Services, an external orchestrator appliance, or a private cloud hosted by Hyper-V or vSphere.

vRealize Automation 7 – Create Tenants

Thu, 14 Jan 2016 16:10:08 +0000

Now it’s time to create a new tenant in our vRealize Automation portal. Let’s login to the portal as the system administrator account as we have before. Click the Tenants tab and then click the “New” button.

Give the new tenant a name and a description. Then enter a URL name. This name will be appended to this string: https://[vraappliance.domain.name]/vcac/org/ and will be the URL that users will login to. In my example the url is https://vra7.hollow.local/vcac/org/labtenant. Click “Submit and Next”.

vRealize Automation 7 - Authentication

Wed, 13 Jan 2016 15:03:15 +0000

In order to setup Active Directory Integrated Authentication, we must login to our default tenant again but this time as our “Tenant Administrator” (we setup in the previous post) instead of the system administrator account that is created during initial setup.

Once you’re logged in, click the Administration tab –> Directories Management –> Directories and then click the “Add Directory” button. Give the directory a descriptive name like the name of the ad domain for example. Then select the type of directory. I’ve chosen the “Active Directory (Integrated Windows Authentication)” option. This will add the vRA appliance to the AD Domain and use the computer account for authentication. Note: you must setup Active Directory in the default (vsphere.local) tenant before it can be used in the subtenants.

vRealize Automation 7 - Base Setup

Tue, 12 Jan 2016 15:07:46 +0000

We’ve got vRA installed and thats a good start. Our next step is to login to the portal and start doing some configuration. Go to https://vra-appliance-name-orIP and enter the administrator login that you specified during your install. Unlike prior versions of vRealize Automation, no domain vsphere.local domain suffix is required to login.

To start, Lets add some local users to our vSphere.local tenant. Click on the vsphere.local tenant.

Click on the “Local users” tab and then click the “New” button to add a local account. I’ve created a vraadmin account that will be a local account only used to manage the default tenant configurations.

vRealize Automation 7 Guide

Mon, 11 Jan 2016 15:45:35 +0000

If following the posts in order, this guide should help you setup vRealize Automation 7 from start to finish. This is a getting started guide that will hopefully get you on the right path, answer any questions you might have, and give you tips on deploying your own cloud management portal.

Part 1 - Simple Installation

Part 2 -Base Setup

Part 3 - Authentication

Part 4 - Tenants

Part 5 - Endpoints

Part 6 - Fabric Groups

Part 7 - Business Groups

Part 8 - Reservations

Part 9 - Services

Part 10 - Custom Groups

Part 11 - Blueprints

Part 12 - Entitlements

Part 13 - Manage Catalog Items

Part 14 - Event Subscriptions

Part 15 - Custom Properties

Part 16 - XaaS Blueprints

Part 17 - Resource Actions

Part 18 - Enterprise Install

Part 19 - Load Balancer Settings

Part 20 - NSX Initial Setup

Part 21 - NSX Blueprints

Part 22 - Code Stream and Jenkins Setup

Part 23 - Code Stream and Artifactory Setup

Part 24 - Add Custom Items to vRA7

Part 25 - Upgrade vRA from 7.1 to 7.2

Part 26 - Adding an Azure Endpoint

Part 27 - Installing vRealize Code Stream for IT DevOps

Part 28 - Configuring Endpoints for vRealize Code Stream for IT DevOps

Part 29 - Using vRealize Code Stream for IT DevOps

Part 30 - Unit Testing with vRealize Code Stream for IT DevOps

Part 31 - Containers on vRealize Automation

Part 32 - vRA 7.3 Component Profiles

Part 33 - vRA 7.5 Upgrade

If you’re looking for a getting started video, check out this P luralsight course for a quick leg up on vRA 7.

vRealize Automation 7 Simple Installation

Mon, 11 Jan 2016 15:00:21 +0000

This is our first stop in our journey to install vRealize Automation 7 and all of it’s new features. This post starts with the setup of the environment and assumes that you’ve deployed a vRealize Automation appliance from an OVA and that you’ve also got a Windows Server deployed so that we can install the IAAS components on it.

After you’ve deployed the vRA7 OVA, login to the appliance with the root login and password supplied during your OVA deployment.

Veeam Package for vRealize Orchestrator

Mon, 07 Dec 2015 15:00:10 +0000

Veeam is a popular backup product for virtualized environments but who wants to spend their days adding and removing machines to backup jobs?

Now available on github is a Veeam package for vRealize Orchestrator. This is my gift to you, just in time for the Hollow-days.

Available Features

The following features are available with the plugin for it’s initial release.

Add a VM to an existing backup job
Remove a VM from a backup job
Start a backup job immediately
Add a Build Profile to vRealize Automation
Add a VM to a backup job from vRA
Remove a VM from a backup job from vRA

Some additional functionality could easily be added to your environment using the existing worfklows such as start a backup as a Day 2 operation in vRA, or change backup jobs etc. The world is your oyster.

Create a Day 2 Operations Wrapper

Mon, 16 Nov 2015 15:08:30 +0000

Just deploying virtual machines in an automated fashion is probably the most important piece of a cloud management platform, but you still need to be able to manage the machines after they’ve been deployed. In order to add more functionality to the portal, we can create post deployment “actions” that act on our virtual machine. For instance an action that snapshots a virtual machine would be a good one. We refer to these actions that take place after the provisioning process a “Day 2 Operation”, probably because it’s likely to happen on the second day or later. Clever huh?

Assign a VM to a Rubrik slaDomain

Mon, 14 Sep 2015 14:00:16 +0000

This last post in the series shows you how Nick Colyer and I to tie everything together. If you want to just download the plugins and get started, please visit Github.com and import the plugins into your own vRealize Orchestrator environment.

Download the Plugin from Github

NOTE: The first version of this code has been refactored and migrated to Github in Rubrik’s Repository since the time of this initial writing

To recap where we’ve been, we:

Get Rubrik VM through vRealize Orchestrator

Thu, 10 Sep 2015 14:07:51 +0000

Part four of this series will show you how to lookup a VM in the Rubrik Hybrid Cloud appliance through the REST API by using vRealize Orchestrator. If you’d rather just download the plugin and get using it, check out the link to Github to get the plugin and don’t forget to check out Nick Colyer’s post over at systemsgame.com about how to use it.

Download the Plugin from Github

NOTE: The first version of this code has been refactored and migrated to Github in Rubrik’s Repository since the time of this initial writing

Rubrik API Logins through vRealize Orchestrator

Tue, 08 Sep 2015 14:00:17 +0000

Part three of this series focuses on how Nick Colyer and I built the authentication piece of the plugin so that we could then pass commands to the Rubrik appliance. An API requires a login just like any other portal would. Since this is a a REST API, we actually need to do a “POST” on the login resource to get ourselves an authentication token.

Download the Plugin from Github

NOTE: The first version of this code has been refactored and migrated to Github in Rubrik’s Repository since the time of this initial writing

vRealize Orchestrator REST Hosts and Operations for Rubrik

Thu, 27 Aug 2015 14:30:30 +0000

In part one of this series, we went over some basics about what REST is and the methods involved in it. In this post, we’ll add a REST host and show you how to add some REST Operations. To begin, we need to add a REST host. In plain terms, this is simply a host that will be accepting an API call. In this case, we’re adding the Rubrik Hybrid Cloud Appliance as our REST host.

Getting Started with vRealize Orchestrator and Rubrik's REST API

Tue, 25 Aug 2015 14:00:02 +0000

What’s this REST thing everyone keeps talking about?

“Oh, don’t worry, we have a REST API.”

“It’s just a simple REST call.”

At one point I was hearing these phrases and would get very frustrated. If REST is so commonplace or so simple to use, then why did I not know how to do it? If this sounds like you, then keep reading. I work for a company called “Ahead” as a consultant and they recently got a Rubrik Hybrid Cloud Appliance in their lab but my colleague Nick Colyer and I noticed that they didn’t have any vRealize Orchestrator Plugins for it. We decided to build these on our own, with the help of Chris Wahl and publish them for the community to use.

Getting Started with vRealize Orchestrator and Rubrik's REST API

Tue, 25 Aug 2015 14:00:02 +0000

What’s this REST thing everyone keeps talking about?

“Oh, don’t worry, we have a REST API.”

“It’s just a simple REST call.”