Channels ▼
RSS

Tools

OpenStack Developers Meet To Plan Next Platform Releases


The OpenStack open source cloud project completed its first public Design Summit last week, which attracted more than 250 people from 90 companies and 14 countries. Development teams met to plan the next two releases, which are currently code-named "Bexar" and "Cactus."

This first public meeting was held as a four-day event in San Antonio, Texas, and was hosted by Rackspace Hosting, a founding member of the open source project. The summit featured two separate tracks, one consisting of developer-led sessions to plan the next two code releases and one for interested users and the partner ecosystem to discuss deployment and commercial opportunities.

The Summit also featured what was labeled as an "InstallFest" where attendees were able to test and document the installation process on a live, on-site environment provided by Dell and powered by the company's PowerEdge C server line.

"From development, to documentation and deployment, the OpenStack Design Summit has enabled the OpenStack community to come together to learn and make the key decisions for the next two code releases," said Jim Curry, general manager of OpenStack.

"The themes for the week focused on how to execute on enterprise and service provider deployments and the immense opportunity that exists for the commercial ecosystem," he added.

Dozens of developers are reported to have contributed to the first "Austin" code release in October this year — and a similar number engaged in proposing new features for the next "Bexar" release scheduled for early 2011.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video