VMware vCAC IaaS Optimization Guide

Update 04/22/15: After further investigation around the effectiveness of these optimization tips on a vRA 6.2.1 environment, I am convinced that several of the tweaks do in fact provide some level of perceived IaaS UI performance improvements. I’m very interested in hearing your feedback on these findings (i.e. give it a try and let me know!).


Update 12/10/14: I have been advised that the optimization tweaks highlighted in this article will not provide any added benefits to vCAC/vRA 6.1 or 6.2. This is due to the way the IaaS interface is now presented back to the user (via the vCAC appliance vs. directly to the user session). The good news is VMware dev’s are hard at work at baking optimization right into the products, starting with a significant boost in the recently released vRA 6.2.

VMware’s vCloud Automation Center (vCAC) can transform how an enterprise delivers IT. It’s out-of-the-box functionality will help IT deliver Infrastructure-as-a-Service (IaaS) along with X-as-a-Service (XaaS / Everything-a-a-S) in a matter of clicks. Once extended into the datacenter’s ecosystem with vCAC’s extensibility engine, it will help integrate, orchestrate, and automate native and 3rd-party tools, services, and infrastructure, thrusting the enterprise into a new level of self-serviced IT efficiency.…

Using VSAN Storage Policies in vCloud Automation Center

VMware vCloud Automation Center is the center piece of VMware’s Software-Defined Enterprise vision. It is also the primary user and admin interface for enterprise and application services, and therefore it makes a lot of sense for vCAC to be the core integration point for the SDDC.

Rawlinson Rivera (@PunchingClouds) recently posted a blog post titled “VMware Virtual SAN Interoperability: vCloud Automation Center“, where he highlights the use of vCloud Automation Center (vCAC) 6.0 to deploy applications directly to a VSAN Datastore while also leveraging a VM Storage Policy. In short, the desired storage policy is applied to the template backing the vCAC Blueprint. Once provisioned, the resulting machine adopts the associated storage policy and the rest is glorious, app-centric VSAN storage consumption. I recommend reviewing that post to get a better idea of what we’re doing here.

So now that we have a basic understanding of the interoperability between vCAC and VSAN, let’s dive into some more advanced concepts for a glimpse into the art of the possible by expanding on Rawlinson’s example and using some of vCAC’s extensibility features to deliver greater functionality.The integration between vCAC and VSAN can greatly enhance how applications are provisioned.  Since storage policies can be configured per-application or VM, you can specify varying policies based on the use case, tier, application criticality, SLA, etc…all backed by a common VSAN Datastore.…