{"id":6328,"date":"2014-07-11T17:10:49","date_gmt":"2014-07-11T22:10:49","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=6328"},"modified":"2014-07-11T17:10:49","modified_gmt":"2014-07-11T22:10:49","slug":"openstack-community-weekly-newsletter-july-4-11","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/openstack-community-weekly-newsletter-july-4-11\/","title":{"rendered":"OpenStack Community Weekly Newsletter (July 4 – 11)"},"content":{"rendered":"

OpenStack Swift 2.0 Released and Storage Policies Have Arrived<\/a><\/span><\/h3>\n

OpenStack Swift 2.0.0. This release includes storage policies \u2013 the culmination of a year of work from many members of the Swift contributor community. <\/span>Storage policies are the biggest thing to happen in Swift since it was open-sourced <\/span>four years ago. Storage policies allow you to tailor your storage infrastructure to exactly match your use case. This release marks a significant milestone in the life of the project that will lead to further adoption and community growth. You can get Swift 2.0 from http:\/\/tarballs.openstack.org\/swift\/swift-2.0.0.tar.gz. As always, you can upgrade to this version without any client downtime<\/a>.<\/span><\/p>\n

Wrapping up the Travel Support Program \u2013 Juno<\/span><\/a><\/h3>\n

The OpenStack Foundation brought 21 people to Atlanta for the Summit in May, thanks to the grants offered by the Travel Support Program, sponsored by VMware. The Travel Support Program is based on the promise of Open Design<\/a> and its aim is to facilitate participation of key contributors to the OpenStack Design Summit. The Travel Support Application for the November Summit in Paris<\/a> is NOW OPEN! You can apply for the Travel Support Program, including costs for travel and accommodation.<\/span><\/p>\n

Missing Building Blocks for Enterprise OpenStack: Part 1 \u2013 High Availability<\/span><\/a><\/h3>\n

In the long term debate of pets vs cattle OpenStack has always been on the side of cattles. <\/span>Dmitriy Novakovskiy<\/a> <\/span>shared his thoughts on why pets are good and how far away OpenStack is from supporting the more ‘legacy’ applications (TL;DR: not too far away).<\/span><\/p>\n

Third Party CI group formation and minutes<\/span><\/h3>\n

At Juno Summit in Atlanta, Kurt Taylor, Anita Kuno, and Jay Pipes agreed to form a group focused on the Third Party experience, including but not limited to continuous integration. Part of the mission of the group is to focus on the quality of Third Party testing for OpenStack through improving documentation, gathering requirements, and easing the deployment of third party testing systems. <\/span>The group has been <\/span>working to improve the consumabi<\/span>li<\/span>ty of the components and documentation. <\/span>They’re inviting all people involved in CI testing to<\/span> join and help make the Third Party experience easier for developers and administrators to understand and deploy. <\/span>The group holds regular weekly m<\/a><\/span>eetings<\/span><\/a>. <\/span>This week they discussed timelines for <\/span>Cinder and Neutron testing, <\/span>r<\/span>equirements <\/span>for <\/span>documentation patches<\/span><\/a>, <\/span>a proposal for s<\/span>ystem terminology <\/span>and helped <\/span>openATTIC <\/span>solve its issues starting up the <\/span>CI system.<\/span><\/p>\n

K<\/span>udos Corner<\/span><\/h3>\n

It’s a great pleasure to highlight good examples of first time contributors to OpenStack getting through their first changeset proposal. Jeegn Chen<\/a>‘s first changeset <\/a>is one of such cases. Kudos to him and the community helping him fixing bug #1327497<\/a>.<\/span><\/p>\n

The Road To Paris 2014 \u2013 Deadlines and Resources<\/h2>\n