vRealize Automation 8 – A first look at vRA8 Migration Assessment Tool: Part 2 of 2

In Part 1 of this two-part series on the vRealize Automation Migration Assessment Tool, we looked at the vRA8 migration tool to see how it might help you plan your migration from vRA7 to vRA8.  In this article, we are going to look at what it will take to migrate your custom workflows from vRA7 to vRA8.  To start, we will explore what a custom workflow looks like to day in vRA7.

SIGN UP FOR THE VRA8 BLOG SERIES & WEBINAR

vRA7 Workflow Components

In vRA7, there are a number of components that come together to make the magic happen.  Each component plays a vital role in how you design, build, and invoke your customizations.

Event Broker

The event broker was introduced in vRA7 to make it easier to trigger the workflow stubs that existed within the IaaS server.  These stubs were always there, but only a handful were accessible and they were not easy to configure. The Event Broker also introduced a more granular way to decide when a workflow should or should not be executed.  Although the event broker has dozens of events you could subscribe to the following were the most commonly used:

  • Machine Requested
  • Building Machine
  • Machine Provisioned
  • Machine Activated
  • Machine Destroyed

Many of these states included a pre and a post execution allowing you to decide if you wanted to execute your workflow before of after vRA’s execution of that state.  These states that are the core of vRA7 extensibility no longer exist in vRA8. vRA8 is a completely new platform, written from the ground up, and no longer includes the IaaS host that controlled all of these states in vRA7.

Read the full article here

A VMware Admin’s First Impressions of vRealize Automation 8 (vRA8) — Part 2 of 2

Article by Mike Bombard

Welcome to Part 2 of 2 of our “First Impressions” of vRA8 article. In Part 1, we discussed what’s new, good, not so good, and really good about Documentation and Tagging in vRA8. Below, we discuss ABX and policies, which are both very new and very different in vRA8.

Action Based Extensibility (ABX), vRealize Orchestrator and Extensibility

ABX is the new extensibility offering packaged with vRA8 (in addition to vRealize Orchestrator) that uses a FaaS provider (AWS, Azure and On Prem offered today) to provide extensibility for the new platform. As someone who has spent countless hours working with vRO, ABX is probably one of the more intriguing announcements surrounding vRA8. 

One of the things that I am impressed with right out of the gate is that the ABX action runs show you the code that was used as well as the payload that was passed for use in the action. In fact, both Orchestrator and ABX runs can be monitored directly from the Cloud Assembly UI. No more having to log in to a separate interface to see what is happening with your extensibility. This methodology makes troubleshooting much more accessible.

A VMware Admin’s First Impressions of vRealize Automation 8 (vRA8) 1

Read the full article here

vRealize Automation 8 – A First Look at the vRA8 Migration Assessment Tool — Part 1 of 2

vRealize Automation veterans may still remember the migrations from vRA 5.x to 6.x and 6.x to 7.x. However, for many enterprises utilizing vRealize Automation, the migration from vRA 7.x to vRA 8.x will be your first major vRA migration. In an ideal world these migrations would only take a few clicks of the mouse.  Migrating from vRA7.x to vRA8.x is going to be a lot like switching banks. Trying to figure out all the services that have your bank card on file for automatic billing and moving over automatic bill payments is tedious and time consuming. Which payments are monthly, quarterly, annually, and for how much? Wouldn’t it be nice if there were a simple tool to identify and update all the services that you have on auto-pay?

SIGN UP FOR THE VRA8 BLOG SERIES & WEBINAR

vRealize Automation is a lot like that.  Whether it’s frequently deployed common workloads, special purpose blueprints that are used a few times a month, quarterly, or a handful or fewer times a year, or software customizations specific to vRA, you have to identify everything that will require hand-holding when you begin the migration from vRA7 to vRA8. The good news is that, unlike your bank, VMware does offer a migration assessment tool to help you determine if your blueprints are ready to be migrated from vRA7 to vRA8. As of this writing, we have not yet learned if the migration assessment tool will determine if your customizations and workloads are ready for migration.

Read the full article here.

Request vRealize Automation Blueprints with Ansible Tower

Integrating Red Hat Ansible Tower with VMware vRealize Automation is a very popular enterprise automation solution. SovLabs has several excellent integrations that can help you accomplish and scale your integration of these two powerful cloud automation tools. This article is the first in a series of four articles covering the integration of Red Hat Ansible Tower with VMware vRealize Automation, based primarily on the content and discussion from our webinar with Red Hat Ansible on May 22.

  1. Requesting a vRealize Automation deployment from Ansible.  How, and why you would want to do it.
  2. The SovLabs Ansible Tower Module for vRealize Automation with Static Inventory
  3. The SovLabs Ansible Tower Module for vRealize Automation with Dynamic Inventory
  4. The SovLabs Ansible Tower Plug-in for vRealize Automation CM Framework

Requesting a vRealize Automation deployment from Ansible

With Ansible Tower quickly growing in popularity, many developers and system administrators want to be able to utilize Ansible Tower to deploy infrastructure.  This type of deployment is the subject of many debates within enterprise organizations, especially those with cloud teams trying to develop standards while enforcing policy and governance across organizations.

The good news is that organizations no longer have to choose between solutions. If you want to use Ansible to develop standards while enforcing policy and governance across organizations, now you can.  Using the solution below you can request workloads from Ansible facilitated by vRA to enforce the desired standards and governance policies. Let’s take a look at how it works.

Continue reading “Request vRealize Automation Blueprints with Ansible Tower”

How to Create vRealize Automation Global Properties with the SovLabs Property Toolkit

If you have not yet read my recent series Harness the Power of vRealize Automation (vRA) with the SovLabs Property Toolkit and Template Engine, I would encourage you to do so. This 3-part series will provide you with some interesting ways to get more out of vRealize Automation using the software solutions provided by SovLabs. In this article I will be coveringa topic closely related to my previous articles and showcasing even more value when you use the SovLabs Property Toolkit.

Global Properties

If I had a dollar for every time someone asked me, “Is there a place to define global properties in vRA?” throughout my career, I probably could have retired by now.  The unfortunate answer to this question has always been “it does not”, but there is a way to apply properties to every request. Keep reading.

The Old Way

The old way to define global properties in vRA was to add the properties you wanted applied globally to each and every endpoint you had configured in vRA.  So, if you had 25 endpoints and 20 properties you ended up have to enter 500 properties and 500 values. This method leads to inevitable typos, finger fatigue, and management overhead every time you need to update a value for any one of those properties or add a new property.

To see the new more efficient way read the rest of the article on the SovLabs blog site here.

SovLabs Plugin Release 2019.8.0 Now Available

SovLabs has released it’s latest version of it’s vRealize Automation plugin version 2019.8.0. Among other key updated it is Certified for vRealize Automation 7.6 as well as ServiceNow Madrid. Below is the full list of updates available in this release:

What’s New?

  • Certified for vRA 7.6!
  • SovLabs Licenses
    • A new SovLabs 2019.x license key is needed in order to use the SovLabs 2019.x Plug-in
    • A 2019.x license key is needed in order to use the SovLabs ServiceNow Connector 2019.8.0
  • SovLabs EULA has been updated!
    • During install of the SovLabs Plug-in and running SovLabs Configuration, the EULA now refers to https://sovlabs.com/eula
  • SovLabs Template Engine
    • Added new tags, filters and improvements!
      • Tags: decrement, ifchanged, increment
      • Filters: abs, at_least, at_most, ceil, compact, concat, floor, lstrip, newline_to_br, reverse, round, rstrip, slice, sort_natural, strip, uniq, url_decode and url_encode
      • Improvements
        • Allow “.” in variables
        • Enhanced parser error messages
        • Allow Unicode forward and backward “fancy” quotes
  • Puppet Enterprise
    • Added “2018.1” and “2019.1” into the Version dropdown list.  Previously verified on 2018.3.4 and 2019.2.0
  • ServiceNow CMDB
    • Added “Madrid” into the Version dropdown list.  Previously verified on 2019.2.0
  • Backup as a Service for Veeam
    • Support for Veeam 9.5, Update 4
    • Performance improvement for Backup Jobs with a large number of VMs
  • Backup as a Service for Cohesity
    • New Day2 Feature: Ability to Recover Virtual Disk that allows recovering an entire virtual disk – either by overwriting the existing disk or recovering to a new (unmounted) device

ServiceNow Connector 2019.8.0

What’s New?

  • A 2019.x license key is needed in order to use the SovLabs ServiceNow Connector 2019.8.0
  • Supports Madrid
  • Added ability to enable the vRA Business Group to be selected at request time by the end-user in ServiceNow when ordering the Catalog request

Import Catalog Item / Modify Catalog Item Mapping Page Enhancements

  • New field for “Override vRA Business Group?”
  • Updated “Constant” label to “Template”

Improvements/Resolved Issues

  • Error logs in ServiceNow and ServiceNow Mid Server
  • ServiceNow request to show useful error when the request is unable to be generated in vRA
  • Hid unnecessary fields during Import/Modify for a vRA Blueprint

Resolved Issues

  • Ansible Tower
    • Fixed issue for Static Inventory failing when no dynamic groups are defined.
  • Ansible Tower for CM Framework
    • Fixed error reporting to report back correct error when an IP address is not defined
    • Fixed the error similar to the following: “[WARNING]: * Failed to parse /tmp/awx_inventory_rNDKxh/tmpqWOvv0 with script plugin: Inventory script”
    • Fixed error when accidentally appending trailing “/” to vRO Hostname when creating the Ansible Tower Endpoint
  • Snapshot Management
    • Fixed issue for missing ID(s) from incomplete vRA CAFE/IaaS data that prevented successful mapping to managed VMs in vCenter.  Added checking and additional logging.
  • IPAM Framework
    • Fixed Release IP to release the IP address correctly

To see previous feature releases please visit the SovLabs support website here.

Harness the Power of vRA with the SovLabs Property Toolkit and Template Engine – Part 1

Ever wish you were able to set more than one value from a single vRealize Automation (vRA) request input?  Have you ever wished you could make some aspects of vRA more dynamic and flexible? Wish you could simplify the vRA request form?  In this article I’m going to let the genie out of the bottle. All your wishes are about to come true. But before we summon our genie, let’s first dive into what it is that we are going to be wishing for.  My wish is to have a simple vRA request page with only three inputs that can drive the outcome of every aspect of my request. Sounds too good to be true doesn’t it? We will find out soon enough.

Finished Result
Harness the Power of vRA with the SovLabs Property Toolkit and Template Engine 1
Determine the needed Inputs

Determining what our inputs are going to be.  For my scenario I need to the following three inputs:

  1. The Environment (Production, Development, or Test)
  2. The Application (WordPress or Microsoft SQL)
  3. Compliance Needs (SOX or Non-SOX)

In my example, these are the only three items I need to know from the requester to build a server in my environment.  The remaining info I can gather from the business group they belong to, what resources the workload is placed on, etc. I know every environment is different and many will require more than three inputs.  Once you have read this entire 3-Part series, you will realize the number of inputs doesn’t matter. It’s how we use them that’s key.

Determine the outcome

What outcomes do we need to drive based on these inputs?  Or, how will these help determine the outcome of the overall deployment?  Will they influence items such as the machine hostname, Active Directory OU placement, vCenter Folder placement, vSphere tagging, application installation, etc?

Harness the Power of vRA with the SovLabs Property Toolkit and Template Engine 2

To read the full article please visit the SovLabs blog located here.

Infoblox, Custom Naming, and the Cost of Free Software

About the Free Custom Hostname Extension for vRealize Automation

Here at SovLabs we are always helping our audience make the decision to either “build” or “buy”, when it comes to VMware automation solutions. Recently, we have been involved in some discussions about the free Infoblox plugin for vRealize Automation. Specifically,these discussions are around how the free Infoblox plugin for vRealize Automation handles custom host naming. That discussion prompted us to consider all such customizations and the support required when when they are integrated with vRealize Automation.

Integrate with vRA
Custom Automation Considerations

There are a few issues at play here, including:

  • How do the different components of your solution work together?  
  • Was it designed wholistically or were pieces added on as you needed them?   
  • Did one source develop all of the components, or are they pulled piecemeal from multiple places?
  • If one source did all of the development – are they still available?  
  • Who is supporting the development work going forward?

Read the entire article written by Josh Andrews here on the SovLabs Blog.

Bedtime story – A tale of two vRA admins

My six-year-old asked me to tell him a bedtime story and it went something like this.

Jimmy and Tommy are both vRA admins.  Jimmy works for a large financial company and Tommy works for a large company that makes really cool stuff.  Both Jimmy and Tommy made great decisions to use vRA to automate their private clouds.  Jimmy decided his organization was going to build all their own integrations.  Tommy  decided to use the SovLabs plugin for all his organizations needs.

Four weeks after Tommy’s vRA deployment his company was using vRA to deploy 75% of their virtual deployments. Meanwhile after four weeks Jimmy is just getting started designing the first of many needed integrations.  Fast forward a year and Tommy’s organization is now deploying 100% of their workloads.  They have reduced management overhead by 45%, and are able to deploy new server requests in under an hour.

A year later Jimmy’s company is still working out bugs with their custom code.  Their administrative overhead is up 55% and it still takes over two-weeks for new server requests to be fulfilled.  Jimmy is working 80+ hours a week and perpetually stressed.  Tommy on the other hand is working 30 hours a week, but don’t tell his boss.  He is enjoying his job and has next to no stress.

I then ask my six-year-old who he would rather be Jimmy or Tommy?  He responded neither daddy I would rather be you.  I asked him why he said he wanted to be me.  He responded, because daddy you helped Tommy only have to work 30 hours a week.

Road to Automation with VMware vRA – vRA Design Part 1

GSS has decided on a number of design considerations for their vRA implementation.  GSS is currently using a consumption based model for their resource allocation.  They don’t pre-reserve any amount of resources for specific groups within the organization.  GSS feels their current consumption model allows them to more efficiently manage their resources.  It also prevents them from having pockets of idol resources that may never get used.  Based on this utilization model GSS will be implementing the following elements within vRA.

GSS  considered having a business group for each environment (Dev, Test, Stage, and Production).  To evaluate how they would like to proceed they asked to have 5 initial tenants created.  One for each of their environments and one to evaluate a collapsed model of all environments in one group.

Business Groups

  •  Development – All Developers across all groups within GSS
  • Test – All QA engineers within GSS
  • Stage – All production teams
  • Production – All Production teams
  • Gregarious – All Dev, QA, and Production teams

Continue reading “Road to Automation with VMware vRA – vRA Design Part 1”