Now that vCloud Automation Center 6.1 is generally available (grab it!) we can go more into the details of whats new! I’ve been waiting for this release for quite some time, as it improved some nice things and set a standard for next versions. So are you ready? lets go!
Installation Changes Quick-guide
Some notable installation changes can be seen with this new version. In terms of install steps, they are still the same:
- vCAC SSO (Id Appliance / Windows Install / vCenter Server)
- vCAC VA (Clustered or not)
- vCAC IaaS (Distributed or not)
An important note regarding the identity appliance – Upgrades from 6.0.x will still need the <id appliance FQDN>:7444 format in the host name field, BUT a fresh install will not require the port, only the host FQDN.
On the vCAC appliance side – achieving HA is now a breeze. Simply install 2 vCAC VA Appliances, configure the primary one, and add a secondary to the cluster by clicking an “HA Mode” option. This will configure the Web app, and messaging for HA mode, PostgresSQL will still have to be configured manually.
As for the vCAC IaaS component, the installation of the components is pretty much the same, but a couple of things changed. .Net 4.5.1 is now the new IaaS operating framework, but you will also need Java 1.7 x64 or later to be installed on the db machine as well.
UPDATE: Looks like it might be the Manager server that specifically needs Java rather then the DB, I’ll re-check and update pre-req script soon.
The new pre-req checker will obviously warn you about this, also another tiny thing i’ve noticed – When you download java from Oracle, using a server box (an 2008 R2 for that matter) the Java you will get is an x86 one since IE is a 32 bit application, thus your computer is detected as such. So pay a good attention to which version of Java you download, since x64 is a must here.
The install script below will handle all pre-reqs, as well as attempt to download the Java 1.7 x64 and set JAVA_HOME (which is also required) for you.
After we’re done configuring everything, it’s time to login! At a first glance we can notice the vCAC UI got a nice minor revamp , showing the vCloud Suite colors & theme, and also a bit of a flat design. I like it overall.
Oh and another minor thing, you can now also access vCAC through –
https://vcac-host-fqdn/vcac/org/tenant (no more shell-ui-app, though it will work as a soft link)
A major change that had to go deep into the vCAC 6.x code base was support for the standard i18n language codes, which includes some standard languages such as German, Japanese, Chinese and more. This is actually something coming all the way from Pat Gelsinger for all of the VMware products.
Enhanced NSX Support
This version of vCAC is mostly ‘the NSX version’ it brings some major improvements to the way multi-machine blueprints are deployed with complex networking and supports NSX in order to do so. A good example of this is the support for NSX features like:
- Logical Switches
- Distributed Logical Routers
- Security Groups & policies
- Distributed Firewall Rules
- Load Balancers
Basically all of these improve a lot of the NSX functionality, for instance, the ability to utilize DLR enables us to deploy single-arm edge devices, with an internal link that serves as a gateway, and the external link is served by the ESXi DLR.
Also, vCAC 6.1 comes with a builtin vCO 5.5.2 Server, which contains by default, a new version of the NSX plugin for vCO! This is actually crucial in running some of the logic for vCAC / NSX integration, so if you configure vCAC for an external vCO IaaS endpoint, and plan to use NSX, be sure to install the NSX plugin on that vCO server!
This plugin will also enable you to perform some great day 2 operations on your VMs, like adding a machine to a load balanced configuration, or a security group.
Advanced Service Designer has been around since 6.0.x release, and VMware has extended some of the things it can perform. For example, you can now assign a day 2 operation to a VM on a VM filter basis.
This means that from now on you will be able to decide when does a VM shows its ASD Day 2 operations, according to its properties. For example, show a custom day 2 operation only if a VM is Powered On, since it is only relevant to that state of the VM.
You will also be able to filter-out operations to be displayed based on other parameters as well, kind of like the parameters available with approval policies.
Also, one of the problems with vCAC 6.x was the lack of ability to specify that a certain Day 2 operations is an ‘Un-provision’ operation. You had do delete the item off of vCO’s cache, and get vCAC to refresh its inventory as well. With the 6.1 ASD, you can specify whether a Day 2 operation is a ‘Provisioning’ one like lets say – clone a vCAC VM (and provision a second VM off of it) , or un-provisioning an ‘abstract’ item.
Last thing new and exciting about ASD is the ability to show output to the users from an ASD Day 2 operation! Meaning, you can have the output of the vCO workflow displayed to the user after the day 2 operation is done, if you need to let him know of a specific output. This is a lot nicer then an email in some cases.
As part of the vCAC 6.1 release, VMware’s former ‘App Director’ or now, Application Services , is also released in a new version. This version has better integration to vCAC , allowing for users to deploy fully blown multi tier apps as service catalog items.
Some of the new features include:
- Resuming a failed App deployment
- Multi tenancy support
- Allowing for additional day 2 ops
Users will now be able to own the infrastructure holding the application requested from the ‘Application Services’ provider (unlike in vCAC 6.0.x) so they are easier to manage, from the central vCAC item portal.
Also, the new Application Services platform is more tightly integrated with puppet, to be able to deliver puppet configured platforms, enabling application teardown, scale in / scale out using the puppet nodes.
Infrastructure Bulk Import
vCloud Automation 6.1 now allows you to bulk import your existing infrastructure into vCAC’s management, with the help of CSV files. Although you could also import brownfield environments in 6.0.x using the infrastructure organizer, things would get complicated when you would try to import a lot of machine with multiple owners to multiple business groups. The bulk import tool comes to simplify all of that, and generates a much simpler importing flow for the end user / admin.
vCloud Automation Center CLI
This version of vCAC comes built in with a little tool called vCAC-CLI. It’ll help you do some rest operations on vCAC with ease, and allow you to get well formatted JSON responses when you perform GET operations. This tool is not ‘CloudClient’ as some of you may or may not know, but more of a vCAC cURL tool.
The tool is Java based, so you can use it from any client OS (Mac / Windows / Linux). You can download the vCAC-CLI tool directly from the vCAC Appliance.
Expect some more in-depth posts about this one later on.
vCloud Automation Center API
The fruits of the vCAC 6.0.x API have ripened and the vCloud Automation Center 6.1 exposes a fully blown Rest APIs accessible even without the help of our friend vCO !
XaaS & Dynamic Types Plugin
vCO 5.5.2 Dynamic Types plugin should now be in full sync with vCAC 6.1, allowing for users to create any vCO inventory item (and thus, a vCAC ASD item) off of services equipped with external REST/SOAP APIs … I’ll be fiddling with these capabilities soon, so expect some interesting updates in the posts to come. Meanwhile, you can check out this few guides at vCOTeam.Info to get your game going on new XaaS options and capabilities!