OpenStack Kilo release
Pitching the Tent
With corporations like SUSE, Red Hat, Canonical, HP, IBM, and Intel investing time and money in OpenStack, clearly this cloud computing platform is here to stay. On the other hand, OpenStack technological advances do not rank highly with many administrators.
The criticisms are always the same: OpenStack is not mature enough as a project to meet the challenges of the provider's daily grind. Some developers believe the money that comes from corporate funding is not always useful: Precisely because so many stakeholders want a say in OpenStack, the project is finding it difficult to formulate and implement its technological objectives. Therefore, the tension always builds up in the community whenever a new OpenStack version is announced, which typically happens twice a year, as was the case in April. OpenStack 2015 "Kilo" is the successor to OpenStack Juno, but what features does the revised OpenStack offer, and have the developers succeeded in solving some of the major problems?
The Big Tent
Possibly one of the most important innovations in OpenStack has nothing to do with technology: the OpenStack Foundation's Big Tent initiative. The image of a big tent underscores the fact that OpenStack wants to be understood as a catch-all for any project that is related to cloud computing. The implementation of the Big Tent initiative was preceded by lengthy discussions, especially within the OpenStack Foundation itself. Release manager Thierry Carrez describes the problem in an exhaustive but easily understandable paper [1].
Up until Juno, OpenStack comprised one major release, and only the officially integrated OpenStack components were allowed to use the title. Anyone wanting to integrate their component needed to pass through the incubation process and thus survive a number of tests. After finally completing a number of
...Buy this article as PDF
(incl. VAT)