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.
The constant battle a web site administrator must fight is the resource requirements of their site in contrast with the resource requirements of the configuration it is run on. In the end, this will almost always dictate how many user requests can be handled at any point in time. A common tool in the arsenal to fight this battle is to find clever ways to off load these common, or static, requests, off the server and allow it to spend as much time as possible delivering dynamic content as quickly as it can handle. This allows a server to not handle more request than before, but leaves it free to address more than previously it would have.
Rackspace and NASA founded OpenStack in 2010, and since then the cloud operating system has seen explosive growth in several key areas. With the mission of becoming the ubiquitous cloud computing platform, OpenStack Foundation has attracted over 5,600 individual members from 87 countries and 850 different organizations.
At OpenStack Summit San Diego, Troy Toman, Rackspace Senior Director of Engineering for Cloud Compute, took the keynote stage to showcase how Rackspace built the world’s largest open cloud. In the presentation, Toman touched upon Rackspace’s journey to OpenStack, how Rackspace uses OpenStack today and how OpenStack needs to evolve in the future.
Here at Rackspace we view OpenStack as the operating system of the cloud. We believe that the openness and large community that has developed around OpenStack provides value for consumers by empowering them with flexibility and optimization options. Consumers can use OpenStack to power an on premise cloud or a cloud hosted by a provider.