Evolving SDNA and Virtual Data Center Concepts
By jasoncatsun on Aug 03, 2009
Cloud computing continues to evolve. We are seeing more and more critical apps deployed onto and managed via cloud infrastructures and platforms. A great example is Rightscale's announcement a few weeks ago that they have kicked off more than 500,000 cloud VMs.
Another aspect of the evolution is moving beyond the VM but to grouping servers and services together and treating them as a virtual data center. Sun's Qlayer acquisition in January provided a unique view and model into how these resources can be grouped and managed together. This shifts the lifecycle to managing many if not all aspects of a deployment versus a box or cluster at a time. Typically during a major upgrade, code changes but so does DB tables, presentation tier components, etc. How do you manage the lifecycle of this change vs a component at a time?
NOTE: SDCs = Service Delivery Controller, See the blog below for more info.)
Using VDCs, services can be deployed within a VDC, and eventually even span multiple data centers. A VDC might implement a single business service, very much like Service Delivery Network Architectures' (SDNA) service module (NOTE PDF) concepts detailed here several years ago. As we continue to evolve and release new technologies -- the focus should be on the lifecycle -- and the first step is to realize every data center service out there is transient and has a "time to live (TTL)."
Look for more "evolution" on the SDNA front at Sun's Blueprints program blog.