Why building private clouds is tougher than you think

As reported by Information Week’s Charles Babcock: “…with private clouds IT professionals face a dilemma between two competing goals: They want to build private clouds that are open to other clouds but also can run existing in-house systems and applications. Private clouds must be as open and standard as possible so, if necessary, you can shift workloads out to public clouds at times of peak demand (known as cloudbursting).”

“But IT also wants its private cloud architecture to work with what it already owns.”

Reality check: You can’t have it all.  The dilemma IT faces is that they can use the shiny new open private and hybrid cloud computing technology, understanding that there will be a great deal of work required to localize that technology within the existing application infrastructure, not to mention the existing approaches to management and virtualization.  Or, they can look to their existing technology providers, such as Microsoft and VMware, to somehow get them there in the near future.

The easy answer is that it comes down to architecture and requirements.  Understand what the business needs moving forward and back in the right technology for the job.  While sometimes this cloud technology may be in-house, in many cases this technology needs to be piloted, tested, and the applications and infrastructure changed around it.