There are lots of reasons to want to export and import blueprints from one vRA instance to another. My current motives are to move blueprints from my vRA 7.2 environment to my newly deployed vRA 7.3 environment. In vRA 7.3 their is a great new free feature available, the Code Stream Management Pack for IT Devops that is free. However if you are running a pre vRA 7.3 environment you may want to get that content from that environment backed up so you can use it in another instance. Cloud Client is a great option.
vRealize CloudClient 4.3
- Support for the vRealize Automation 7.2 capability to assign all users of a business group to an entitlement or to delete an inactive entitlement.
- The new vra catalogitem service unassign command enables you to remove a service from a catalog item.
- CloudClient’s truststore password can now be set by the user. As a result of this update, users may be prompted to accept certificates that were previously accepted in earlier versions of CloudClient.
- CloudClient 4.3 runs on Java version 1.8. Java 1.7 is no longer supported.
For additional details about this release, please refer to the Release Notes (links below).
While I was away on vacation last week it seems VMware had another exciting round of releasing starting with the Release of vRA 7.2. Probably the most anticipated feature is the new Azure Endpoint. Although this is a very exciting feature there are some other very exciting enhancements as well. Enhancements to the API, container support, installation API, and one of my personal favorites Scale out/scale in.
GA date: 22 November 2016
The vRealize Automation 7.2 release includes resolved issues and the following changes:
Still running vRA 6.x, then you will be happy to hear vRA 6.2.5 is now GA and boast some great performance improvements. See blow for more details.
Many of you may have already seen the news, but I like to create a roll up to make it easy to see what’s been newly released. Yesterday Tuesday August 23rd 2016 VMware released a number of much awaited Management product updates. See below for a breakdown of the updates per product.
vRealize Automation 7.1
vRealize Automation 7.1 is optimized for growing clouds thanks to significant improvements in the automated installation experience.
vRealize Automation 7.1 continue simplifying the primarily and secondary setup process by adding ability to automate the setup process among similar deployments leveraging the new Silent Installer. Cloud Admins are now able to scale out existing vRealize deployment by adding more vRA components and manage them automatically though the new Command Line(CLI) interface.
vRA 7.1 release is also equipped with a brand new Migration tool which allows you to perform safe and sound side by side upgrade (migration) existing vRealize Automation systems 6.2.X to the latest and greatest release. During the migration process the source production environment remains intact which guarantees a minimum downtime of the production environment.
Over the weekend Roman, Grant, John and I released a significant update to the platypus project, which is essentially a very simple and elegant way to provide a Swagger based documentation of several VMware Products. This project started out by providing a quick way to consume the vRealize Automation 7 API, but it has grown a healthy set of legs.
One of the goals of the project was to take publicly available specifications and make them consumable and adaptable by the larger community.
So, what’s new? Everything.
- Flexibility: When you run the docker container, there is the option to provide variables for Product Name and Product Version.
- Product Support: The updated platypus project now includes vRealize Operations 6.2, vRealize Orchestrator 7.0, and NSX 6.2.
- Host Config: The host variable now provides the ability to input the hostname of an instance of the VMware Product in question (preferably a test/dev instance) and issue the REST API calls.
To get your hands dirty with the NSX version of Platypus, just issue the following command:
docker run –name platypus –rm -p 80:8080 -e PRODUCT=”nsx” -e VERSION=”6.2″ vmware/platypus
Interested in checking the platypus project out? Find out more at https://github.com/vmware/platypus. If you are interested in contributing to the project, simply issue a PR.
Please leave your feedback or comments below, I’d love to hear from you.
vRA has a great UI for provisioning VM’s, but with developers needing infrastructure on demand and wanting to have the ability for continuous integration. With the new and updated vRA API’s you can now easily code your own deployment scripts or recipes and integrate with your own run books and still get the the governance and lifecycle management that vRA has to offer. Continue reading “VMware vRealize Automation – vRA7 – Infrastructure as Code (IaC)”
vRA 7 introduced a number of new and very useful features such as unified blueprints, software components, event broker, and others. The event broker however has proven itself to be one of the most power new features we have seen in some time. How so you ask? Well if you have been working with vRA for any period of time you will remember the old way of triggering external workflow executions such as those run by vRO. If you have been using vRA for a really long time you will remember back before vRO when vRA wasn’t even vRA and run nothing but .Net workflows, but we won’t go back that far.
Looking to prepare a Windows template for use with vRA7? Want to utilize the vRA Guest Agent as well as Software Components? Great! The very talented Gary Coburn has built a package that will it all for you. If you have ever prepped an image for use with vRA 6 or even vRA 7 you know it’s sort of a pain especially if you are like me and don’t like to read the documentation line by line. The first time I prepared a guest I figured ah this is simple I’ll just go and do it. Well that didn’t turn out to well. I had anticipated putting together an article on how to do it when a co-working on my team at VMware Gary Coburn built an awesome script that just does it all for you.
OK not too much on this one. If you wan to upgrade vRA to 7.0.1 and you want to use the plug-in in vRO 7.0 or 7.0.1 you will need this. That’s basically it. Just don’t forget you need this if you are upgrading and if you are doing a fresh install and are using a non embedded vRO server.