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)
Once your vCAC Application Services appliance is installed and configured, you must set up a Cloud Provider. A Cloud Provider is a system that will provide infrastructure services for the applications you will manage. In this case, we are using vCAC. At the same time, you can create Templates based on the vCAC Blueprints you’d like to consume.
Follow the steps below to create your Cloud Provider and Templates.
Choose a user account and add it to the Group Manager role in a vCAC Business Group with the privilege to deploy the Blueprint you would like to use as a base for your application installation.
Next login to the Application Services appliance, open the Applications menu in the upper right-hand corner, and navigate to Cloud Providers.
Click the green plus sign to add a new Cloud Provider.
Select the appropriate Cloud Provider Type, vCAC in this case.
Fill in the Name and Description for the Cloud Provider. The vCAC Cloud Provider Type also requires you to input the vCAC Infrastructure URL (the Windows machine, NOT the catalog appliance), as well as your chosen User Name and Password. Be sure to click Validate Connection after you’ve completed all required fields.
To add a Template, click the green plus sign next to the Templates heading in the lower section of the page.
Click the check box for the Blueprints you’d like to enable as Templates in Application Services, then click OK. You can also click the ellipsis to show more information about a Blueprint.
If you’d like, you can change the Name and/or Description of the Template(s). When you are finished, click Save.
This Cloud Provider and Template will now be available for Application deployments.
Now that we have installed and configured NSX I think it’s time we connected it to vCAC. In version 6.1 there are some changes to the integration with NSX and vCAC. When I say changes I should say there are some great new changes. The integration now utilizes a vCO Plug-in that handles all the interactions between NSX and vCAC.
Benefits of vCO plug-in for NSX to vCAC integration
The benefits of the vCO plug-in are huge. These workflows that now exist in vCO are there for you to use in your own customization giving you the ability to interact with NSX in a custom way without having to code against it’s api. Personally I await the day for all integrations to be this way.
As most of you know the vCAC appliance has vCO built in and the built in vCO server already has the NSX plug-in installed for. If you want to use an external vCO you will have to deploy the plug-in to that appliance before trying to connect vCAC to NSX.
I have been received a number of questions about the MoaC Lab so I decided to put together an article to cover what the MoaC is. The MoaC or Mother of all Clouds lab is a project Tom Bonanno and myself (Sid Smith) started to help with sharing information. The goal is to build a lab that will allow us to build the use cases that everyone wants to learn about. It’s not about building a lab that has a huge number of resources, but a lab that has a huge number of integrations. Integrations that that we can document and share with the world.
The MoaC Lab consists of two site. Site 1 is located in my basement in Harrisburg, PA and Site 2 is located in Tom’s Basement near Atlantic City, NJ. The two site are currently connected using an IPSec VPN run over NSX.