Open Data Center Alliance, Part 8--Service Catalog

 
 
Cameron Sturdevant Cameron Sturdevant is the executive editor of Enterprise Networking Planet. Prior to ENP, Cameron was technical analyst at PCWeek Labs, starting in 1997. Cameron finished up as the eWEEK Labs Technical Director in 2012. Before his extensive labs tenure Cameron paid his IT dues working in technical support and sales engineering at a software publishing firm . Cameron also spent two years with a database development firm, integrating applications with mainframe legacy programs. Cameron's areas of expertise include virtual and physical IT infrastructure, cloud computing, enterprise networking and mobility. In addition to reviews, Cameron has covered monolithic enterprise management systems throughout their lifecycles, providing the eWEEK reader with all-important history and context. Cameron takes special care in cultivating his IT manager contacts, to ensure that his analysis is grounded in real-world concern. Follow Cameron on Twitter at csturdevant, or reach him by email at cameron.sturdevant@quinstreet.com.
By Cameron Sturdevant  |  Posted 2011-06-23 Email Print this article Print
 
 
 
 
 
 
 

2011-06-23 part 8 service catalog

This ODCA diagram shows the basic interactions between the cloud provider and cloud consumer, "highlighting the key role that the API will have..."

The Open Data Center Alliance Service Catalog usage model is by far the most detailed of the publications issued in the first round of requirements.

In many ways, the Open Data Center Alliance (ODCA) attempts in the Service Catalog (SC) a codification of the real interaction between cloud providers and cloud consumers. Fans of dispelling the hype around cloud computing will delight in this sticky romp through the very practical, "Mary Poppins"-like approach to creating a service catalog. The SC is all about what an API (application programming interface) will provide to large cloud consumers. "...[A] GUI is of relatively low importance to our target Cloud-Subscriber, who may choose not to use it at all for service discovery and selection. Instead, Cloud-Subscribers need a robust and detailed API...to interrogate the Service Catalog." With this gruff introduction, the SC usage model dives into ten pages of what, roughly, would be entailed in this "robust and detailed API."

Besides being a refreshingly sober antidote to the often breezy discussion surrounding cloud computing implementation, the SC is a decent primer about just what cloud computing can offer. In detailing the service catalog requirements, the SC touches on nearly every aspect of cloud operations and talks quite frankly about what role IT can play in ensuring that these services are delivered efficiently.

Table of Contents for the Series:

1. IT Users Band Together: a brief introduction to the ODCA 2. Virtual Machine Interoperability 3. Carbon Footprint 4. Security Monitoring 5. Security Provider Assurance 6. Regulatory Framework 7. Standard Units of Measure for IaaS 8. Service Catalog 9. I/O Controls

 
 
 
 
del.icio.us | digg.com
 
 
 
 
 
 

Submit a Comment

Loading Comments...
 
 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
 
 
Thanks for your registration, follow us on our social networks to keep up-to-date
Rocket Fuel