Virtualization Technology News and Information
VMware vCAT 3.0 Implementation Examples Changes

Now that vCAT 3.0 has been released, it is worthwhile to discuss the obvious as well as the more subtle changes that are a part of this release and specifically the Implementation Examples document. One of the key guidelines that we adhered to while writing vCAT was to be careful not to operate in a bubble. In other words, the authors tried to always be cognizant of why they were writing these documents. One of the primary reasons behind writing these documents is simply to make the jobs of cloud architects and engineers a little easier. In order to do this we listened to feedback from the field that would ultimately be consuming these documents.

Three pieces of feedback based on previous versions of vCAT that were directly incorporated into the Implementation Examples document were:

  1. The document has a lot of information and readers are not always sure where to go for a specific task they need to accomplish.
  2. The document is a large monolithic representation of one very specific design example, which reduces its value to those without the same exact business requirements or constraints.
  3. While the document has very specific guidance and information about vCloud Director, what about other complimentary products in what is now the VMware vCloud Suite. Readers wanted more information on the integration and coexistence of VMware products such as vCenter Chargeback Manager, vCenter Operations Management Suite, vCenter Orchestrator or vFabric Application Director with Cloud.

To learn more and to read the entire article at its source, please refer to the following page, vCloud Architecture Toolkit Blog: vCAT 3.0 Implementation Examples Changes- VMware Blogs


Published Thursday, September 13, 2012 7:06 AM by David Marshall
Filed under:
There are no comments for this post.
To post a comment, you must be a registered user. Registration is free and easy! Sign up now!
<September 2012>