{"id":4318,"date":"2013-06-07T17:39:19","date_gmt":"2013-06-07T22:39:19","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=4318"},"modified":"2013-06-07T17:39:19","modified_gmt":"2013-06-07T22:39:19","slug":"openstack-community-weekly-newsletter-may-31-june-7","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/openstack-community-weekly-newsletter-may-31-june-7\/","title":{"rendered":"OpenStack Community Weekly Newsletter (May 31 – June 7)"},"content":{"rendered":"

OpenStack 2013.1.2 released<\/a><\/h3>\n

The OpenStack Stable Maintenance team is happy to announce the release of the 2013.1.2 stable Grizzly release. We have been busy reviewing and accepting backported bugfixes to the stable\/grizzly branches. A total of 80 bugs have been fixed across all core projects.<\/p>\n

OpenStack “I” <\/b>release<\/b><\/strong> <\/b>naming<\/b><\/strong><\/a><\/h3>\n

The next release cycle for OpenStack, starting in November 2013 after we conclude the current release<\/strong> cycle (“Havana”) will be called Icehouse.<\/a><\/p>\n

Open Source Sysadmin: Reorganization of the OpenStack Infrastructure Docs<\/a><\/h3>\n

The OpenStack Infrastructure team is constantly evolving its documentation to make it easier for new contributors to join the team. Last week documentation for the OpenStack Project Infrastructure<\/a> was reorganised \u201cto re-orient the documentation as an introduction for new contributors and a reference for all contributors.\u201d All of the CI tools are open source, the puppet and other configurations are all hosted in public revision control<\/a> and any changes submitted are made by the same process all other changes in OpenStack are made<\/a>. They go through automated tests in Jenkins to test applicable syntax and other formatting and the code changes submitted are reviewed by peers and approved by members of the infrastructure team. This has made it super easy it is for the team to collaborate on changes and offer suggestions (much better than endless pastebins or sharing a screen session with a fellow sysadmin!), plus with all changes in revision control it\u2019s easy to track down where things went wrong and revert as necessary.<\/p>\n

Enter OpenStack\u2019s T-shirt Design Contest!<\/a><\/h3>\n

Show us your creative talent & submit an original design for our 2013 OpenStack T-shirt Design Contest! Winning design will be announced the last week in August 2013. <\/strong>Details on <\/strong>OpenStack blog<\/a>.<\/strong><\/p>\n

Async I\/O and Python<\/a><\/h3>\n

When you\u2019re working on OpenStack, you\u2019ll probably hear a lot of references to \u2018async I\/O\u2019 and how eventlet is the library we use for this in OpenStack. But, well \u2026 what exactly is this mysterious \u2018asynchronous I\/O\u2019 thing? Read it from Mark McLoughlin<\/a>.<\/p>\n

Ceph integration in OpenStack: Grizzly update and roadmap for Havana<\/a><\/h3>\n

S\u00e9bastien Han<\/a> wrote a summary of the sessions about Ceph integration with OpenStack. His post contains details about upcoming features and a roadmap.<\/p>\n

OpenStack-Docker: How to manage your Linux Containers with Nova<\/a><\/h3>\n

A new approach to manage Linux Containers (LXC) within OpenStack Compute. The Docker project released a driver to deploy LXC with Docker, with multiple advantages over the \u201cnormal\u201d virtual machines usually deployed by Nova. Those advantages are speed, efficiency, and portability. Details and links to the code on How to manage your Linux Containers with Nova<\/a>.<\/p>\n

Tips ‘n Tricks<\/h2>\n