Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

The challenges of moving to a private cloud

Bill Claybrook | Nov. 16, 2010
In this article, we delve deeper into the technology choices needed for the virtualization, management and automation required for a private cloud.

One alternative to home-grown tools includes building mixed-component cloud stacks by acquiring various third-party components and putting them together. The question then becomes: Who do you call when there is a problem? Another possibility is to lock yourself into a single vendor such as Microsoft or VMware.

Each alternative has its pluses and minuses, so weigh your options carefully. And keep in mind that turning back from any of them once you're underway is expensive and time-consuming.

Open-source tools

What's the most challenging part of implementing a private cloud?

(Check all that apply.)

Software licensing/pricing issues: 44 per cent

Finding tools to help us build our cloud: 44 per cent

Ensuring economies of scale: 44 per cent

Finding tools to help us manage our cloud: 42 per cent

Making it all work together: interoperability: 37 per cent

Dealing with technology obsolescence, protecting our cloud investment: 37 per cent

Lack of standards in the cloud world: 33 per cent

Making the ROI case to upper management: 20 per cent

Source: Computerworld online survey; 54 respondents

Open-source software is a good choice for building private clouds because the software is essentially free, and it does not impede the flexibility gained by virtualization and cloud computing the way that proprietary software licensed on physical CPUs sometimes does. For example, proprietary software licensing can create issues with migrating VMs from host to host.

Abiquo, and Red Hat sell open-source tools for managing clouds.

You do not want to lock yourself into a single vendor's cloud stack. Especially avoid vendors with cloud stacks that perform well when using only their components. Reserve the option to plug in your home-grown or third-party tools.

Integrating multiple toolsets

Jeff Deacon, cloud-computing principal for Verizon Business, says that more sophisticated enterprises are integrating multiple management toolsets -- for instance, Hewlett-Packard's Server Automation Suite and BMC's Patrol Automation Suite. Security, firewall, networking and storage elements can be orchestrated from within both BMC Patrol and HP Server Automation Suite. Companies that do not link multiple toolsets may have to write a lot of their own software to get the necessary automation capabilities.

It is not yet possible to buy one commercial product that will do everything that most IT managers need to do for private clouds. You have to stitch together a number of different products from various vendors and place your own GUI on the front end.

Is single-console management a reality for private clouds? Iams says that not everyone will be able to get by with just one console, but even two or three consoles represent a huge improvement over the dozen that some shops use today.

Deacon thinks that single-console management is in the cards. He says that Verizon Business has built a high-level console management layer that calls APIs from VMware vCenter, HP Network Automation and HP Virtual Connect, among other products.


Previous Page  1  2  3  4  5  6  7  8  Next Page 

Sign up for Computerworld eNewsletters.