Have you ever tried to build a day 2 operation for use with Multi-Machine applications? Well if you have chances are you hit the same issue one of my colleagues Pontus ran in to when he first attempted. Pontus however didn’t give up when he discovered there is no Object type to tie the action to. Instead he dug deeper and deeper until he found a solution. If you find yourself needing this capability or have found yourself banging your head for hours trying to figure this out you should check out Pontus’s post on virtualviking.net. The post can be found at http://virtualviking.net/2015/11/13/day-two-operations-on-multi-machine-blueprints-in-vrealize-automation-6-2/
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
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.
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.
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:
- Use a single machine blueprint for all components of a multi-tiered multi-machine blueprint and customize the name of each component.
- 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.
- 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.
- 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.
- Fixed bug that caused properties with Multiple periods not to be processed properly.
- 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.