True story… I spend a lot of my daytime hours working with VMware Fusion Pro for BAU and local lab tasks. Fusion has been a mainstay for me since switching to a Macbook Pro for my main workhorse a number of years ago. I test a lot of beta software, build & break stuff for training. Fusion has always had me covered.
I’ve also gotten used to working with a variety of interfaces when testing various cloud platforms, but recently most of my time has been spent in vCloud Air (obvz). So when I fired up Fusion 8 Pro this morning and found the <VMWARE VCLOUD AIR> header in my navigation pane, I was understandably excited.
A simple click onto the header reveals login fields and a couple of contextual links to vCloud Air (bonus points to the product team for adding <Remember Password> checkbox).
I enter my login credentials and *BAAM*. Within a couple of seconds, full access to all of my Subscriptions and VPC OnDemand. I will admit that I was surprised by how rapidly Fusion was able to display and allow interaction with my full vCA inventory across multiple SID’s / VDC’s.
I’m hoping to see a more advanced federated ID type service integrated into Fusion in the near future, but this will do for now.
VM Remote Console (VMRC)
Hands down one the best features of this Fusion release is VMRC access to vCA workloads. No messing with firewall and NAT rules. Just plain VMRC…
The result is Operations can continue to administer the vCA platform and assign access to VDC’s based on login. Developers (or users) who have no delegated administrative control in vCA can login via Fusion and get access to the resources the need. No additional URL’s to send out. No training users on the multiple interfaces. They just continue to use Fusion in the same way they always have…
Transport to vCA
As for workload transport, we can still export to OVF/OVA and upload to our Private Catalogue in vCA…
…but why would we when we can now drag ‘n drop our local VM’s into vCloud Air! Select the VM, drag to our VDC of choice, rename if required and click <Upload> to confirm. Simple.
Note: One small gotcha (why is there always a gotcha…). In order to use this method of migration we need to update Fusion tools to the latest version, and then downgrade the hardware version to a maximum of v10.
The VM can be upgraded again post migration which is a small hassle (edit:when supported), but in general this method rocks!
And that’s it… A ~5GB VM took just under 10 minutes to move from Fusion to vCA (AU South). Of course the network still needs to be setup on the vCA side to support intra-VDC and external network communication, but if the VM is standalone then nothing else is required.
More detail to come in the near future. Happy Fusion’ing 😉