vRealize Automation 7.0 (GA) is LIVE!

Well, here it is folks…the wait is over for one of the most anticipated releases from VMware’s Cloud Management BU — vRealize Automation 7.0 is officially GA as of this writing!!

vRealize Automation is the centerpiece of vRealize Suite, VMware’s Cloud Management Platform (CMP). With the release of vRA 7.0, VMware clearly demonstrates it’s leadership in the CMP market by delivering a platform loaded with several enhancements, killer features and industry-first innovations. vRA 7 also redefines the user experience by following through on the commitment to take the complexity out of hybrid cloud management without “dumbing down” the product.

I’ve had the privilege to work very closely with several teams within the cloud management BU while gearing up for this launch, most notably my friends and peers in the go-to-market team. In my 6 years at VMware, I can honestly say I have never seen so many smart people work so closely together on a common goal — deliver a solid product, set the standard. Needless to say, I’m incredibly proud and honored to be a part of this release.

Let’s get to the goodies.

I foolishly set a goal to have a full library of vRA 7 content completed by GA.…

vRealize Automation 7 – Part 5, Identity Management

Moving right along with the next spotlight feature in vRealize Automation 7 — a totally revamped access control and authentication system brought to you by VMware Identity Manager (vIDM). What may appear as an insignificant move from 6.x’s standalone Identity Appliance (IDVA aka vCenter SSO/PSC) is actually one of the most important additions to the new platform. Allow me to elaborate…

vIDM is the result of VMware’s acquisition of TriCipher about 5 years ago (August 2010), which has gone through several iterations and has become — or will become — the de facto policy-based identity platform across VMware broader portfolio (beyond vCenter, of course). Today, it is most notably leveraged by the Horizon suite and, more recently, as a stand-alone Identity Management solution available as an on-prem or SaaS offering. Out of the gate, vIDM brings scalability, performance, and policy-based management and access controls to whichever solution it is natively integrated with. This is especially true (re: performance/scaleability) when access into said solution is extended to the entire enterprise. And with that, it was almost a no-brainer that VMware’s Cloud Management BU has chosen vIDM as it’s standard for the next-gen CMP solution, starting with vRA 7.0.

The Identity Problem

To get a better understanding of why this was a critical move for vRA, we need to understand some of current limitations and restrictions brought on by the IDVA.…

vRealize Automation 7 – Part 4, Initial Config as-a-service

We’ve discussed VMware’s focus on the UX and Time-to-Value (TTV) with vRA 7’s much-improved Deployment Architecture and the new Deployment Wizard, which automates the end-to-end deployment for for monolithic or distributed vRA implementations. This alone will drastically change the perceived complexity of installing the solution. But now that we’ve got that out of the way, why not take it one step further?

Once vRA is installed, there is still a significant amount of initial configuration and logic building to be done. While this allows customers to build a tailored solution based on their requirements and desired logic, it wasn’t very POC or quick-start friendly. It can take an experienced vRA admin another hour or so of configuration before being able to log in and request/deploy the first IaaS machine. For the inexperienced POC’er, this can be a brutal process no matter how well VMware attempts to document each step. In the spirit of automating automation and improving the quality of life for the average vRA admin, VMware has delivered a clever way to quickly tackle this. It’s called XaaS (aka anything-as-a-service, previously referred to as the Advanced Service Designer). In short, it’s an XaaS form and a set of vRO workflows that help vRA deliver itself as a service.…

vRealize Automation 7 – Part 3.1, Deployment Wizard Video

In part 3 of this series I provided an overview of vRA 7’s new deployment wizard – an addition that will significantly increase the time-to-value (TTV) by aiming to quickly deploy vRA regardless if it’s for a minimal (monolithic) or enterprise (distributed) implementation.  I cannot emphasize enough how critical the deployment wizard (along with the new deployment architecture) will be for removing the perceived complexity of getting vRA stood up.  Competitively, this sets a new standard for how to implement any enterprise solution and will certainly allow vRA to shine above the rest (but enough about that).

Below is a video of the deployment wizard walking through a minimal implementation.  It is important to note that vRA 7 has yet to GA, so some of the automation options and the UI itself can be tweaked between the current beta code and eventual GA builds.

(The screen capture is sped up 2.5X and some long wait periods have been clipped)

vRA 7 Deployment Wizard – FAST from @virtualjad on Vimeo.

The wizard will provide a choice of a minimal (POC, small) or enterprise (HA, distributed) deployment then, based on the desired deployment type, walks the admin through a series of configuration details needed for the various working parts of vRA, including all the windows-based IaaS components and dependencies.…

vRealize Automation 7 – Part 3, The Deployment Wizard

Remember that time you downloaded vRA (or vCAC) and tried to install it on your own? After some frustration and head-scratching, you turn to documentation, blogs, events, and a variety of guides provided by the community. Eventually everything starts looking good as you’re able to get passed the install and into initial configuration. vRA 6.x’s implementation involves a series of appliance deployments, VAMI configurations, prerequisite headaches, and installation of several IaaS components on windows hosts. Taking that to a distributed, highly-available configuration was a whole different story with the added complexities of deploying several additional systems, clustering configurations, external dependencies, and a whole other set of prerequisites. Of course none of this is unique to vRA — many enterprise solutions will take weeks or months to deploy in a production-ready state. There are many complexities expected of a cloud management platform that is nested at the center of an enterprise ecosystem. While the end-to-end implementation of vRA has come a long way, there was still a lot to be desired. Fortunately, that desire was understood…and a solution was brewing.

Continuing with the theme of redefining the user experience, vRA 7’s new deployment wizard takes time-to-value to a whole new level.…

vRealize Automation 7 – Part 2, Deployment Architectures

VMware has been tackling several customer pain points when it comes to deploying and configuring vRA (6.x). But let’s get this out of the way — the ratio of level of effort vs. product capabilities make the time investment quite worth it at the end of the day (at least i think so!).  In the overview post (Part 1), I mentioned the massive focus on overall UX improvements in vRA 7. While the new deployment wizard absolutely changes the perception of complexity and takes all the work out of the admin’s hands, the reduced deployment footprint is equally important and will drastically reduce operational overhead and time to implementation. That is especially the case for distributed architectures that can grow upwards of 20+ machines. Let’s change that, shall we?…

vRA 6.x Deployment Architecture

In addition to several external dependancies, vRA 6.x requires various internal/embedded services to be taken externally for high availability. The services embedded in the virtual appliance include vRealize Orchestrator, the vPostgres DB, and the vRA framework services themselves. An external Identity Appliance (SSO) is required for authentication (vCenter SSO also an option). And, finally, the optional App Services VA for app authoring.

For distributed architectures, the components include at least 2 load-balanced vRA VA’s, an external pair of clustered vPostgres DB’s, external clustered vRO pair, a pair of [vCenter] SSO’s (the Identity Appliance does not support an HA configuration), and a single ill-fated App Services VA, which also does not support an HA setup.…

vRealize Automation 7 – Part 1, What’s New – Spotlight Features

This was a big week in Barcelona — not just because VMworld EMEA broke attendance records, but also thanks to the announcement of one of the most anticipated updates to the VMware vRealize family, vRealize Automation 7.0 (vRA 7).  I had the opportunity to hosts and co-host several vRA sessions throughout the week, including a couple exclusive ad-hoc deep dive workshops for vExperts.  Now it’s finally time to share with all of you the cloud management goodness that’s been brewing at VMware.  This is the first of many in a series that will cover all the new innovations and features of vRealize Automation 7.0 and dig deep into several advanced use cases.  So let’s get started…

Spotlight #1 – Deployment and Initial Configuration

vRA 7 focuses a lot on the user experience (UX), starting with one of the most critical — Deploying the solution — then the second most critical, configuring it.  Following through with the promise of a more streamlined deployment experience, we made a huge splash at VMworld Barcelona with the debut of the wizard-driven and completely automated installation of the entire platform and automated initial configuration.  And all of this in a significantly reduced deployment architecture.

Deployment Architecture – The overall footprint of vRA 7 has been drastically reduced.  …

A Quick Lesson on vRA Entitlements

vRealize Automation provides a ton of granularity for roles and permissions, service availability, lifecycle management (e.g. day-2 operations). It essentially boils down to a set of logic that defines who can see and do any given task on any given resource. This can be as simple as a handful of configurations, or get as complex as you want it to be.

vRA’s Entitlements feature is just one of many ways to add governance and additional controls to your environment. Entitlements allow admins to create a set of policies that determine which services any given consumer can deploy and how they can [lifecycle] manage their services post-provisioning. The following entitlement options are available per Business Group User or Group.

  • IaaS Blueprints
  • PaaS / AppServices Blueprints
  • XaaS Services
  • Actions / Custom Actions (Day 2 Operations)
  • Service Catalogs
  • Approval Policies

Entitlements are created and managed under Catalog Management (Administration tab -> Catalog Management -> Entitlements) for all available services. It is important to note that entitlements are a REQUIRED function for service delivery (e.g. all services must be entitled at some level before they are available for consumption). Since this isn’t a HOW-TO post (see the vRA Live Install and Config videos and/or the vRA 6.0 POC Guide for a detailed how-to), here’s a summary of how to get from here to there…

 

 

 

 

 

 

 

 

 

 

Once an Entitlement is created, there are several options that will help you fine-tune exactly what gets entitled, who this entitlement effects, which actions are available, and whether or not component-level approval policies are in the mix.…