Blog Post

Rackspace launches OpenStack private cloud

Filling in its OpenStack check list, Rackspace(s rax) is making code for its OpenStack private cloud available on Wednesday. The company launched its OpenStack public cloud infrastructure on July 31.

The availability of both private and public cloud infrastructure will enable customers who want to run some workloads on an internal or private cloud and others on an external cloud to do so using the same basic infrastructure.

There is big interest and probably considerable demand for such hybrid cloud implementations that let companies keep sensitive workloads inside their firewalls but allows easy expansion into a public cloud as needed.

OneID is an example. The company, a Rackspace customer, offers a secure way for users to make payments online. Bobby Beckmann, VP of engineering there, loves the idea of hybrid cloud. In a recent interview said he loves what cloud can do — let you spin up machines for fast, on-demand CPU power.  But …”I wasn’t ready to give up control over our speed of accessing storage.  Even with Amazon(s amzn) EC2, I/O is a bottleneck because you’re competing with other VMs. I also wanted my own real hardware load balancer and firewall. We need to be PCI compliant and to do that we need tight control over devices.”

Jim Curry, GM of Rackspace’s private cloud business, tells us via email:

“We believe that the majority of our customers and cloud users will be running hybrid cloud environments for a long time. Today’s announcement allows businesses to utilize their existing investment in their own data center resources to run an open cloud solution for additional control and customization and also take advantage of Rackspace’s datacenter options.”

OpenStack activity is heating up — earlier this week Red Hat(s rhat) posted a preview to its OpenStack cloud implementation although it will not be generally available until next year.

4 Responses to “Rackspace launches OpenStack private cloud”

    • Bostonmikea

      The software is definitely open. The installer uses the community open stack bits as part of the install. The chef recipes are open sourced. Even the installer is open sourced.

      • Thanks Mike. OpenStack itself is open but, the question is when can I have a control panel that allows me to move my workloads from one provider to another and extend my on premise cloud?

        It’s an open solution but I don’t have portability without a control panel and some interoperability between providers.

        So are you saying the Control Panel itself is an install-able component? If so, that would be incredible indeed.