Like many other enterprise IT shops, Rackspace IT is turning to service providers to help us design, provision and support enterprise-class systems. Our goal is to more efficiently and effectively serve our internal customers. We want to take advantage of efficiencies and scale that the open cloud can provide and we need help to do it. With this in mind, we’ve kicked off a program called “Rackspace IT: Drive to the Open Cloud.” The focus of the program is for Rackspace IT to become an enterprise customer of Rackspace, leveraging the same solutions Rackspace offers our many external customers and driving as many of our enterprise applications as possible to the Rackspace open cloud.
The words “run like Rackspace” are something we hear from customers and prospects all the time. Everyone from enterprise CIOs to ISV development leads want to build private clouds that look, feel and operate like our open public cloud. They want the same software, the same configuration and the same operations that power our public cloud, but they want it all to themselves, most often in their own data centers.
With constantly increasing demand in compute power, data center space can fill up very fast. The problem with compute is that new servers require significantly more power than older facilities can provide. Thus, power demand limits rack density.
One of the most difficult aspects of migrating existing IT applications to the cloud is setting up appropriate storage for those applications. In fact, one of the questions I am frequently asked by our customers is how to set up Rackspace Private Cloud Software to enable their business take advantage of enterprise storage. This dilemma historically has not been easy to solve, since current cloud storage solutions require either re-writing applications to use object storage or using new technologies like NoSQL databases.
A few months ago, Gartner Vice President Lydia Leong created quite a stir when she authored a report that questioned the altruism, or lack thereof, associated with the OpenStack movement. Personally, I can’t see why anyone in the OpenStack community was surprised or offended. It may have hurt some to hear, but Leong made a great point: open source does not necessarily mean open.