Posted on

vRealize Automation 7–vRA7–Announced – Get a look at what’s to come!

Many of you have already heard the news about vRA7.  Now that it has been officially announced I can start to share some useful information regarding this transformative release of vRealize Automation.  I want to start by stating I cannot discuss anything related to GA release date so don’t expect to find anything related to when this will be released.  This article is aimed to give you an overview of some of the great new features coming in version 7 and as the starting point for a  series of vRA7 walk-through articles.

vRealize Automation 7 Installation

I think you are all going to be very pleased with the new installation wizard.  It takes 98% of the pain out of deploying vRA, and let’s face it, it wasn’t that difficult in the 6.x release.  To start much like the vRA 6.x installation process you will need a Windows Server available, but you no longer have to make sure you have all the pre-requisites completed.  The only pre-requisite you will need is to install a simple installation agent on server and that’s it.  The installation will not only check for the pre-requisites, but it will allow you to resolve them if they are not met.

The installation also now let’s you choose between a simple installation and a fully distributed installation.  This is huge.  If you have ever done a distributed installation this is where most of the pain was felt.  VMware has truly raised the bar and done a fantastic job with the installer.

 

image image image image image  image

 

Identity Management

Not a fan of the SSO solution in previous releases of vRA?  Then you are in luck.  vRA7 no longer uses the Identity Appliance and VMware SSO.  It leverage VMware Identity Manager.  There are so many great aspects to this welcomed change starting with one less virtual appliance to deploy.  That’s correct Identity Management is built in to the vRA virtual appliance.  Besides simplifying the installation it will also simplify integrations giving you the ability to authenticate a user via an external source and pass that token to vRA preventing the need for the user to login yet again.  Look for some more in-depth articles coming on this soon.

image

 

Unified Blueprints

Blueprint creation just got a whole lot easier and a whole lot more feature rich.  For those of you who have been using vRA 6.x you are going to really appreciate the new Blueprint designer.  Drag and drop templates, networks, applications, XaaS workflows on the canvas and build your blueprint visually.  This is just the start.  Remember the 6.x NSX integration?  Remember how it only worked with multi-machine blueprints?  Guess what?  That is no longer the case.  Add one machine add ten is doesn’t matter.  Use existing networks, create new ones, assign securty tags, security groups, load balancers, and more.  It’s like those old Prego commercials…..”It’s in there”.  Are you an application services user?  Remember having to pull in the single machine vRA blueprints to use with App Services and then publish them to the vRA catalog?  Guess what?  You guessed it.  If you want to deploy an application to a template on your cancase, you just drop the application on to the template.  Look for a lot of great articles to come on this.

image

 

Blueprints as Code

Ever wish you could export and import blueprints?  Wish no more!  vRA7 features the ability to export you blueprints as code.  Once exported you can manipulate the file is needed and import into another vRA7 or the same vRA7 instance.  Imagine exporting your bleuprints checking it into GIT for version control and running those bleuprints builds through Jenkins to facilitate new “builds” and then importing it back into vRA7.  Well no need to image because it’s all possible.  Another feature to help with the transformation to DevOps.

Enhanced Extensibility

Just when you thought it couldn’t get any better, it does.  The new event broker system in vRA completely transforms how you will integrate to 3rd party systems in vRA7.  Some of the features here include dynamically assigning workflows to builds based on filters.  Remember how complicated it could be get the right workflows to run based on custom properties?  Well this if the possibilities, trigger a workflow based on the requestor, the machine name, the blueprint, and more…..and this is just one of the cool features of event broker.  Use event topics such as Post Approval, Pre Approval, Blueprint configuration, resource reclamation, Business Group Configuration, XaaS, Machine LIfecycle, and Machine Provisioning.    Look for a whole ton of articles on this as well as new releases of workflows based on this new event broker.

 

image

 

These are just some of the great new features in vRA7, I can’t wait to start posting new articles on how to works with the awesome new features.

Posted on

vRealize Automation – vRA 6.2.1 is now available!!!!!

Today VMware released vRealize Automation (vRA) formerly known as vCloud Automation Center (vCAC) version 6.2.1.  In the release there is several bug fixes and one enhancement.  The enhancement however is one that you may be very interested in.

Remote Console is back! – Remote Console Capabilities for Machines Provisioned with vSphere: Secure remote console capabilities for machines provisioned with vSphere are implemented in this release by means of WebMKS (HTML 5 console) through a console proxy.

To get the latest bits and check it out go to:

vRealize Automation 6.2: https://my.vmware.com/web/vmware/info/slug/infrastructure_operations_management/vmware_vrealize_automation/6_2

Posted on

vRealize Automation – vRA (vCAC) 6.2 – vRealize Automation 6.2 released

FIlter vRealize Automation 6.2 has been released.  This release although not a Major Version packs a pretty powerful punch.  It’s loaded with new features and enhancements that you are all going to want.  This release aims to add some features that solve some basic challenges that have been seen by many of you running the product in your production environments.  Here is a breakdown of what is new in this release:

  • vCloud Air EndPoint with support for Proxy Servers with vCloud Air
  • Configurable email tempaltes
  • Calendar of Events
  • Use IaaS custom properties within Application Services (Application Services)
  • Support for CloudFoundry as a deployment target (Application Services)
  • vRealize Operations Integration including health badges in vRA Portal.
  • XenDesktop 7.x Support
  • Support for OpenStack Havana
  • Ability to edit Custom Properties during approval time
  • Scheduler for reconfigure operations
  • Ability to change lease times to indefinite
  • Enhanced Event and Audit Logging
  • Log Bundle tool
  • VM Disk Support for up to 60 disks (Previously 15)
  • Improved Rest API
  • API for Reservation Management
  • Better control for DB log rollover
  • Swap Space Custom Property to account for swap space on disk
  • Filter Catalog by Business Groups
  • Enhanced installation for easier HA deployments
  • UI Performance Improvements

Continue reading “vRealize Automation – vRA (vCAC) 6.2 – vRealize Automation 6.2 released”

Posted on

VRealize Automation – vRA (vCAC) 6.2 – Hardening Guide Released

This is something that has been long sought after by many.  The hardening guide is 38 pages long packed with hardening information for the vRA Appliance, IaaS Server, Identity Appliance, and Application services appliance.  This document takes you through the hardening of the SLES 11, PostgresSQL, Windows Host including SQL Server, IIS, and Microsoft .Net.  The hardening guide also covers the network security and securing communications between the vRA components.

The network security section of the guide includes a complete list of all the vRA components and the ports/protocols that are used by the component.  Even if you are not ready to start creating a fully hardened deployment it’s worth taking a look at the guide and becoming familiar with the the communications between the different components.

Continue reading “VRealize Automation – vRA (vCAC) 6.2 – Hardening Guide Released”

Posted on

vRealize Autoamtion – vCAC 6.x – Identity Appliance vs. vCenter SSO Server

I am frequently get asked “Should we deploy the vRealize Automation Identity Appliance or should we connect vRealize to the vCenter SSO server”?  The answer to this really depends on what is important to you.  There are pro’s and con’s both scenarios.  Let’s look at the vRealize Identity appliance first.

vRealize Identity Appliance

The major benefit to running the vRealize Identiy appliance is that it is released as part of the vRealize Automation code stream.  This is important because if new features are released in vRealize Automation that have dependencies on specific support from the SSO server the Identity Appliance will be updated with the needed support.  This will allow you upgrade when a new version is released without having to worry about external dependencies.

The downside of running the vRealize Identity Appliance is the extra administrative overhead, especially of you are deploying an HA environment.  It’s extra servers to support, backup, and maintain on top of the vRA Appliance, IaasS Server, and any deployed for DEM’s/Agents.  Not a huge deal, but it’s something to consider.

Continue reading “vRealize Autoamtion – vCAC 6.x – Identity Appliance vs. vCenter SSO Server”

Posted on

vRealize Automation – vCAC 6.1 – Ultimate Multi-Machine Blueprint Extension v1.0.2 – Updated

Have you ever needed more control over what custom properties get assigned to specific component machines of a multi-machine blueprint, or want to use the same component blueprints for all component machine of a multi-machine blueprint?  The Ultimate Multi-Machine Blueprint Extension aims to help with that.

The Ultimate Multi-Machine Blueprint Extension allows you to utilize the same source component blueprint for multiple component machines while at the same time controlling which custom propertied get assigned to each of the components.  This allows you customize each of them differently during deployment.

This extension works well with the Custom Hostname and the Custom vCenter Folders extension to round out the use of Multi-Machine Blueprints.

Example Use Cases:

  1. Use a single machine blueprint for all components of a multi-tiered multi-machine blueprint and customize the name of each component.
  2. Use a single machine blueprint for all components of a multi-tiered multi-machine blueprint and customize the guest agent actions of each component machine.
  3. Use a single machine blueprint for all components of a multi-tiered multi-machine blueprint and override the template for each component to deploy from a different source vCenter template for each component.

The goal of this extension is to limit blueprint sprawl and leverage the multi-machine construct to customize the component machines and rely less on customizing the single machine blueprints making them more re-usable.

This extension was designed and built as a collective effort by Tom Bonanno and Sid Smith.  If you have any feedback please let us know.

Features

  • Define which component machines to apply custom properties to in a multi-machine blueprint.
  • Utilize a singular blueprint for all component machines in a multi-machine blueprint.

Change Log

v1.0.2

  • Fixed bug that caused properties with Multiple periods not to be processed properly.

v1.0.1

  • Initial Release

Remember we have performed a large amount of testing, but this is a v1.0 extension so please test and let us know if you find any issues.

Continue reading “vRealize Automation – vCAC 6.1 – Ultimate Multi-Machine Blueprint Extension v1.0.2 – Updated”

Posted on

vRealize Automation – vCAC 6.2 – Pre-Req Automation Script

Are you getting ready for the pending release of vRealize Automation 6.2 next week?  If so you’ll want to make your first stop GitHub to download Brian Graf’svCAC62-PreReq-Automation.ps1 script.  If you are not familiar with Brian’s PreREq automation scrip, it is a script that configures all of the needed requirements ion your Windows IaaS server prior to installing vCAC.  Brian did a fantastic job with the creation of this, it is a must have if you are installing vCAC from scratch.

In this version he updated the script to account for vCAC 6.2 Pre-Requisites so head on over to https://github.com/vtagion/Scripts/blob/master/vCAC62-PreReq-Automation.ps1 to download the script and get familiar with it to be prepared for the pendinf release.

Posted on

vRealize Automation – vCAC 6.1 – Custom Property Toolkit for vCO

For those of you who have not seen this yet, it is a must have for anyone writing vCO workflows for vCAC.  VMware’s own Dan Linsey build a set of pre-built workflows to help aid you in your own development efforts.  The toolkit includes workflows for performing Create, Read, Update, & Delete Operations for vCAC custom properties for more than just virtual machine objects.  IT includes support for the following:

 

  • Blueprints
  • Build Profiles
  • Business Groups
  • Endpoints
  • Property Dictionary
  • Virtual Machines
  • and more

Top check out this incredibly useful toolkit head over to the VMware Communities and download it.

Posted on

vRealize Automation – vCAC 6.x – Removing workflow revisions from Design Center

CloudUtil is a vRA(vCAC) repository management tool that is part of the vRA Designer.  It actually is what you are launching when you run the designer.  When run without parameters it launches the GUI Designer.  It however has other functions that can prove useful from time to time.

For starters if you don’t have the Designer Installed you can get it by going to https://FQDNofvCACAppliance:5480 –> IaaS Install –> vCloud Automation Center Designer.  When you install it make sure you put in the IaaS host, NOT the vCAC appliance hostname.

I frequently get asked how can workflow revisions be removed from the designer.  The answer is they can, but you need a Development Kit license to do so with CloudUtil.  Working in the designer you will come to find out that the revisions add up fast and before you know it you could have hundreds.  I’m going to walk you through a way to remove the revisions without a Development License for CloudUtil.

Continue reading “vRealize Automation – vCAC 6.x – Removing workflow revisions from Design Center”

Posted on

vRealize Automation – vCAC 6.1 – Custom vCenter Folder Extension

Overview

vCAC by default will place all provisioned machines into a vCenter folder named VRM.  You can override this using the custom property VMware.VirtualCenter.Folder to tell vCAC where to place the provisioned machine.  While this is great that you can tell vCAC where to place the provisioned machine it isn’t very flexible.  I built the Custom vCenter Folder Extension to fix that and make folder placement as flexible as you need it to be.  VM folder placement is just about organizing virtual machines.  It provides a way to control access to these machines through vCenter as well.  Many organizations control permissions to these environments using these folders and need to be able to place any machine where they need for these purposes.

Multi-Machine blueprints is another area where this extension adds value.  You can control placement of virtual machines by defining the VMware.VirtualCenter.Folder property on a Multi-Machine blueprint folder, but all VM’s for all Multi-Machine apps are placed in the same folder creating confusion as to which VM’s belong to which Multi-Machine application.  Now if you add NSX into the mix and you have Multi-Machine components spread all over the place with no way to easily determine which VM’s as well as NSX Edges go to which application.

When used with Multi-Machine blueprints the Custom vCEnter Folder Extension can place all component Virtual Machines as well as Deployed NSX Edge appliances in a folder named after the Multi-Machine application if you desire making it easy to identify related components of an application.  This also allows you to easily permission vCenter access to the components of the application if necessary.

Features

  • Dynamic Folder Names based on custom naming scheme
  • Multi-Machine folder placement including NSX Edge applince
  • Automatic Multi-Machine folder removal when Multi-Machine app is destroyed

Continue reading “vRealize Automation – vCAC 6.1 – Custom vCenter Folder Extension”