This post has already been read 4353 times!
So, you’ve got your VMware cloud all running perfectly internally, you have AppD (VMware Application Director) hooked in and also vCO (VMware vCenter Orchestrator) running smoothly. All is looking well, you are now ready to spread your wings and start to push some of your workload into the cloud. You have a number of options around this, but as you know vCAC supports Amazon you decide to start with that.
Navigate to Endpoints and try to add Amazon as a provider and boom, it not there. Can’t understand why, you have bought the vCloud Enterprise Suite, everything should be included right? Well, unfortunately no.
Hopefully the following article should clear up any issues you may have around the VMware vCAC Licensing model and why you don’t have the option to scale out into a Hybrid Cloud model right now.
vCloud Automation Center (vCAC) is available as stand alone product or as part of the vCloud Suite. The stand alone model supports Per VM Licensing (25 machines per license) and the vCloud Suite License supports Per Cpu Licensing. The 3 different types of vCAC products are:
NOTE: vCAC Standard is not available as stand alone product, only Advanced or Enterprise.
If you’re using the product as part of the vCloud Suite then the version of vCAC that will be available is directly related tot he version of the vCloud Suite that you bought.
Sounds simple right? I want the all-singing, all-dancing VMware Cloud option, I will get the vCloud Suite Enterprise option and “grow” into the features as we scale out. Well, there is a “small print” line at the bottom of the vCAC licensing and product options page (http://www.vmware.com/products/vcloud-automation-center/compare.html)
What this basically means is that if you buy vCloud Suite Licenses and not stand alone vCAC licenses you will only ever be able to manage internal Private Cloud resources hosted on vSphere! Not great right.
You may think that you have somehow “got around” this limitation as you can still see the end point connectors. Unfortunately in version 5.2 of vCAC the end points were displayed but from a licensing perspective you were not allowed to connect to them. In version 6 they have tweaked this display to only display the options you are licensed for.
The strange thing is you can’t even connect to VMware’s vCloud Hybrid Service with a vCloud Suite License? You still need a stand alone license for that!
Hopefully this has answered the question “Why are external cloud end points not appearing in my vCAC console”