2011: When cloud computing shook the data center

In a year of surging private cloud activity and major build-outs in public cloud capacity, the cloud's promised simplification remains elusive

By , InfoWorld |  Cloud Computing, OpenStack

As InfoWorld's Matt Prigge observed in his post "How I learned to stop worrying and love the private cloud," pervasive server virtualization has created a crying need for software to manage pooled resources. So-called private cloud software addresses that need with many moving parts, including virtualization management, metering and chargeback systems, automated configuration, identity management, self-service provisioning, application management, and more.

Though far from complete, the OpenStack private cloud solution is compelling in part because it follows a Linux-like open source model. Today, under an Apache license, the OpenStack "kernel" has three components: Compute (for managing large networks of virtual machines), Object Storage (for massive storage clusters), and Image Service (for managing virtual disk images). Around that kernel -- as with Linux distros -- vendors add value. The leading commercialized version of OpenStack is Project Olympus from Citrix; startup vendors Internap, Nebula, and Piston Cloud Computing also use the OpenStack core.

Between its debut in October 2010 and today, OpenStack has already undergone four revisions. The fifth, code-named Essex and scheduled for release in spring 2012, will include two new components: Identity, for authentication and authorization, and Dashboard, a UI for managing OpenStack services.

But OpenStack is hardly the only game in town. Its best-known competitor is Eucalyptus, a private cloud implementation of Amazon Web Services that enables you to move workloads back and forth between Amazon EC2 and Eucalyptus (which also comes in an open source version). Then there's Puppet, a wildly popular configuration management framework designed to automate almost any repeatable task in the data center. Puppet can create fresh installs and monitor existing nodes; push out system images, as well as update and reconfigure them; and restart your services -- all unattended.


Originally published on InfoWorld |  Click here to read the original story.
Join us:
Facebook

Twitter

Pinterest

Tumblr

LinkedIn

Google+

Ask a Question
randomness