{"id":1188,"date":"2011-07-20T11:20:52","date_gmt":"2011-07-20T16:20:52","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=1188"},"modified":"2011-07-20T14:23:24","modified_gmt":"2011-07-20T19:23:24","slug":"openstack-celebrates-a-successful-first-year","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/openstack-celebrates-a-successful-first-year\/","title":{"rendered":"OpenStack Celebrates a Successful First Year"},"content":{"rendered":"

\"\"<\/a>A year into the life of OpenStack, it seems like its success should have been more obvious.\u00a0 The market lacked an open platform designed specifically for building and managing a cloud.\u00a0 We knew that fact at Rackspace because we had been forced to build our own solution.\u00a0 For five years we looked for off the shelf technologies that could power our public cloud but never found an acceptable solution.\u00a0 So we kept building our own proprietary technology.\u00a0 But that wasn’t the right answer.\u00a0 As a company, we had always relied on standardized technologies to power our offers.\u00a0 Technologies that our customers were also running in their own data centers.\u00a0 But in cloud, such standards did not exist and were nowhere in sight.\u00a0 Certainly, the ones that were emerging were not completely open.\u00a0 And by building our own solution \u2014 one not available to anyone else \u2014 we weren’t actually helping to solve the problem.\u00a0 So we decided to open source our technology, and make it available for use by our competitors and customers alike.\u00a0 What we didn’t know was whether anyone else saw the world as we did.<\/p>\n

A year later, its obvious we weren’t alone.\u00a0 Consider these stats:<\/p>\n