If you haven’t looked at Code Stream, you may want to now. Code Stream as you may or may not know is VMware’s DevOps product, but what you may not know is that with this management pack it adds some features to your vRA deployment that you may be interested in. Now this isn’t totally new it is in version 2.0 as you can see. The management pack allows you to utilize Code Stream to automate the SDDC lifecycle of templates, blueprints, workflows, dashboards, scripts and more within vRA. This is pretty cool right. If you want to use a blueprint for two tenants your can automate the lifecycle of these blueprints which I think is awesome.
You will soon see the theme in all the releases that have been released today. Earlier I posted that vRA 7.0.1 was released and of course vRA and vRO are tightly tied so it seems obvious they would release an updated vRO as well. vRO 7.0.1 is a patch release. What’s the difference between and maintenance release and a patch release? Yeah I don’t know either. What I do know is it introduces some improvements, bug fixes, and resolved a very important issue that you may have seen with vRO. Issue CVE-2015-7547 “glibc getaddrinfo() stack-based buffer overflow”. For more information see the Resolved Issues.
vRealize Automation 7.0.1 is the first maintenance release for the new vRA 7.x release. The release provides fixes in many areas, however it is primarily focused on vRA lifecycle. Fixes include Installation and Upgrade, Licensing, Enterprise Readiness, Performance and Scale. If you have made the leap to vRA7 or are starting out on vRA7 it is recommend that you install this maintenance release and take advantage of the benefits and fixes it provides. Stay tuned for more details on the fixes and what they will mean to you.
Folks this truly is an amazing leap forward for the vRA platform. Just look at the list of new features below, which is not a complete list of all there is with this release. Keep checking back for informative step-by-step articles as well as updated versions of our workflow packages to be published by the end of this month.
vRealize Automation 7.0 is a cutting edge release which provides an industry lead cloud automation solution to our customers. With the streamlined installation wizard, simplified SSO configuration, integrated graphical infrastructure and application blueprint authoring and deployment capabilities, and many other new enhancements, customers will be able to maximize their return on investment by extremely shortened time to value for cloud service delivery.
Following are some of the new features:
Streamlined and Automated Wizard-based Installation
- Introduces management agent to automate the installation of Windows components and to collect logs
- Automates the deployment of all vRealize Automation components
- Installation wizards based on deployment needs: Minimal (Express) and Enterprise (Distributed) Installations
Simplified Deployment Architecture and High Availability Configuration
- Embedded authentication service by using VMware Identity Manager
- Converged Application Services in vRealize Automation Appliance
- Reduced minimal number of appliances for HA configuration
- Automated embedded PostgreSQL clustering with manual failover
- Automated embedded vRealize Orchestrator clustering
This is for all you MacBook users out there. If you are like me and run a VM to use the VMRC console, well those days are over. VMware Remote Console 7.1 for mac was released yesterday!
Last October, VMware announced the release of the first standalone VMware Remote Console application for Windows. Yesterday, VMware went live with the first-ever VMware Remote Console (VMRC) for Mac OS. Until the end of last year, VMRC has been a plug-in component in the web clients of vSphere, vCloud Director, and vRealize Automation. Until this release of VMRC for Mac, customers on Mac clients were limited to using a basic HTML console and a plugin-based device control.
Google has scheduled the deprecation of the Netscape Plugin API (NPAPI) in Chrome browsers in September 2015, which will stop the legacy VMware Remote Console plug-in in web clients from functioning. VMware will continue to add VMRC support for different platforms so that customers will have plugin-independent access to VM console functionality and operations, as well as client device connections to VMs on remote ESXi hosts.
VMRC can be launched directly from vSphere web client versions 5.5u2b and 6.0, as well as URLs specifying ESXi host and VM information. The application supports Mac OS 10.8 and up.
You can find the VMware Remote Console (VMRC) for Mac Download here.
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
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.