{"id":6452,"date":"2014-08-29T18:10:37","date_gmt":"2014-08-29T23:10:37","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=6452"},"modified":"2014-08-29T18:10:37","modified_gmt":"2014-08-29T23:10:37","slug":"openstack-community-weekly-newsletter-aug-22-29","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/openstack-community-weekly-newsletter-aug-22-29\/","title":{"rendered":"OpenStack Community Weekly Newsletter (Aug 22 – 29)"},"content":{"rendered":"

The results are in – Manila is an OpenStack incubated project!<\/span><\/a><\/h3>\n

OpenStack <\/span>T<\/span>echnical <\/span>C<\/span>ommittee <\/span>voted <\/span>Manila into official incubation status. <\/span>The TC<\/span> formally accepted the creation of shared file systems program, as well as the incubation of the Manila project.<\/p>\n

OpenStack as Layers<\/span><\/a><\/h3>\n

Sean Dague<\/a> has a good suggestion for representing OpenStack’s pieces and how they stack up together to realize Infrastructure As A Service. His post expands on the timely topic of what should be part of an integrated release.<\/p>\n

Keystone is not an authentication service<\/span><\/a><\/h3>\n

Nathan Kinder<\/a> dives deeper into Keystone. While many would argue that Keystone in OpenStack world has something to do with authentication, Nathan argues that Keystone\u2019s main purpose is authorization within an OpenStack deployment. While it\u2019s true that Keystone can perform authentication itself, Nathan argues that doesn\u2019t mean that it should be used for authentication.<\/p>\n

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

During the Paris Summit there will be a working session for the Women of OpenStack to frame up more defined goals and line out a blueprint for the group moving forward. We encourage all women in the community to complete this very short survey<\/a>to provide input for the group.<\/p>\n