Earlier this month, we updated the Rackspace Private Cloud Software, adding new features and support capabilities that give you the ability to quickly and easily deploy an OpenStack-powered private cloud in your data center.
Rackspace makes it extremely easy to deploy private clouds for companies of all sizes, from large Fortune 100 enterprises to individuals wanting to learn about building massively scalable clouds on OpenStack.
While I was putting together my keynote presentation for OpenStack EMEA, I took a trip down memory lane and uncovered documents, emails and slide decks chronicling the earliest iterations of what would later become OpenStack.
One of our goals at Rackspace is to make it easier for enterprises to deploy and manage private clouds. We’ve made great strides with the launch of Rackspace Private Cloud, powered by OpenStack® (dubbed “Alamo”), which lets our customers go from bare metal to a private cloud in their own data center in less than an hour.
We’ve received a bunch of questions since our launch of Rackspace Private Cloud Software (code-named Alamo) about how we are using open source software. How is Alamo licensed? Are we adding restrictions to the components? What happens to the components if you stop using Alamo? And many more. If you have these same questions, this blog post is for you!
This week, Rackspace opened our latest data center in Australia. You might think this marks our entry into the country, but we have actually been there for some time. Throughout our history we have had a large number of Australian companies serving their customers and markets from our other data centers, and in particular in our Hong Kong facility. In 2009, we setup a permanent team of Rackers in Australia to serve those customers led by the awesome Mark Randall (@racker_randall). With this investment, and the rollout of our cloud portfolio, the demand from the market for us to have a local data center rapidly grew; hence opening the new data center this week.
Deploying a private cloud shouldn’t be so complex and expensive, or require a cloud expert to make it happen. In the two years since we founded OpenStack®, one of our missions has been to create fast and easy ways for our customers to deploy a free OpenStack-based cloud wherever they choose. And to do so not using a proprietary installer or version of OpenStack, but instead using the community bits themselves. In other words, we think it’s critical that the OpenStack community version be usable.