With contributions from: Massimo Re Ferre, Eric Fulton, Tomas Fojta, Ray Budavari, Jesse Schachter, Kyle Smith, Francois Misiak, Benham Chia, Ranga Maddipudi, Trevor Gerdes and Ben Byer
We hope you enjoy this month’s vCloud Suite Digest. This is where we take some questions that we get and disseminate the answers in the hopes that it will help someone else who might have a similar question. This month, we have some great tidbits on guest OS clustering, elastic VDCs, and networking among other things. Enjoy!
This was a question I received this morning on how to programmatically identify which products have been installed from the VMware vCloud Suite in a given environment. There are a variety of use cases where this information can come in handy such as software audits, information for third party application/integrators or documentation to just name a few. This information is provided through vCenter Server and the vSphere API using the ExtensionManager which is responsible for both VMware and third party solutions.
In case you haven’t read the post here already, there’s a great screencast available that demonstrates how to use the vCloud metadata policy descriptors and mechanisms to trigger the enforcement of policies in a cloud environment.
This screencast highlights several products included in the vCloud Suite, such as vCloud Director (vCD), VMware vCloud Networking and Security, and VMware vCenter Orchestrator (vCO). Additionally, it also demonstrates how someone can leverage VMware vCloud Automation Center (vCAC) to provide more governance around policies within cloud environments.
Overall, this is a great example of how you can leverage several of the components contained within the vCloud Suite in your environment. If your interested in finding out more about the products shown in this screencast, or any of the other products that are contained within the vCloud Suite, you can visit the vCloud Suite page on VMware.com.
A new version of the vSphere vCenter Server has been released to address some of the issues encountered with various scenarios of deploying and operating the 5.1.0 version. This release is a full version and you can upgrade from 4.0-5.1GA to 5.1.0A
I’ve listed some information specific to the issues resolved however do check out the full release notes for install instructions and a list of known issues with workarounds.