The OpenStack Blog

Category: Communication

OpenStack Community Weekly Newsletter (July 18 – 25)

How to Effectively Contribute to An Open Source Project Such As OpenStack Neutron

As Neutron’s Tech Lead (PTL), Kyle Mestery has been mostly heads down working to ensure the Neutron project has a successful Juno release. Increasingly, and especially near OpenStack Juno milestone deadlines, he’s forced to make hard choices and start turning new features down in order to focus on shipping good quality code for Juno. He sent an email to the openstack-dev mailing list this morning addressing the pressure his team is under. He also wrote a longer blog post to expand upon that email.

OpenStack Failures

Last week the bulk of the brain power of the OpenStack QA and Infra teams were all in one room, in real life. This was a great opportunity to spend a bunch of time diving deep into the current state of the Gate, figure out what’s going on, and how we might make things better. Sean Dague, Jim Blair, wElizabeth K. Joseph and bmwiedemann wrote a summary of the week.

OpenStack plays Tetris : Stacking and Spreading a full private cloud

CERN is running a large scale private cloud which is providing compute resources for physicists analysing the data from the Large Hadron Collider. With 100s of VMs created per day, the OpenStack scheduler has to perform a Tetris like job to assign the different flavors of VMs falling to the specific hypervisors.

Juno Updates – Security, Authentication and other neat things

There is a lot of development work going on in Juno in security related areas. Nathan Kinder wrote up some of the more notable efforts that are under way in Keystone, Barbican, Kite and other projects.

The Road To Paris 2014 – Deadlines and Resources

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 surveyto provide input for the group.

Security Advisories and Notices

Tips ‘n Tricks

Upcoming Events

Other News

Got Answers?

Ask OpenStack is the go-to destination for OpenStack users. Interesting questions waiting for answers:

Welcome New Reviewers and Developers

Mike Smith Roman Vasilets
Mika Ayenson Motohiro Otsuka
Claudiu Nesa David Yuan
Scott Reeve Amey Ghadigaonkar
Pawel Palucki Alexandr Naumchev
Travis McPeak Michele Paolino
Livnat Peer Marcus V R Nascimento
zhangtralon daya kamath
Ryan Brown arkady kanevsky
David Caudill Travis McPeak
FeihuJiang ChingWei Chang
Anusha JJ Asghar
Lee Yarwood Neetu Jain
François Magimel
Ashraf Vazeer

Latest Activity In Projects

Do you want to see at a glance the bugs filed and solved this week? Latest patches submitted for review? Check out the individual project pages on OpenStack Activity Board – Insights.

OpenStack Reactions

wnnng

My reaction when for the first time I had a contribution merged in OpenStack

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment.

OpenStack Community Weekly Newsletter (July 11 – 18)

DefCore Update: Input Request for Havana Capabilities

As part of our community’s commitment to interoperability, the OpenStack Board of Directors has been working to make sure that “downstream” OpenStack-branded commercial products offer the same baseline functionality and include the same upstream, community-developed code. The work to define these required core capabilities and code has been led by the DefCore Committee co-chaired by Rob Hirschfeld (his DefCore blog) and Joshua McKenty (his post). You can read more about the committee history and rationale in Mark Collier’s blog post. The next deadlines are: OSCON on July 21, 11:30 am PDT and the Board Meeting on July 22nd.

And the K cycle will be named… Kilo !

The results of the poll are just in, and the winner proposal is “Kilo”. “k” is the unit symbol for “kilo”, a SI unit prefix (derived from the Greek word χίλιοι which means “thousand”). “Kilo” is often used as a shorthand for “kilogram”, and the kilogram is the last SI base unit to be tied to a reference artifact (stored near Paris in the Pavillon de Breteuil in Sèvres).

Five Days + Twelve Writers + One Book Sprint = One Excellent Book on OpenStack Architecture

A dozen OpenStack experts and writers from companies across the OpenStack ecosystem gathered at VMware’s Palo Alto campus for the OpenStack Architecture Design Guide book sprint. The intent was to deliver a completed book aimed architects and evaluators, on designing OpenStack clouds — in just five days.

Only developers should file specifications and blueprints

If you try to solve a problem with the wrong tool you’re likely going to have a frustrating experience. OpenStack developers use blueprints define the roadmap for the various projects, the specifications attached to a blueprint are used to discuss the implementation details before code is submitted for review. Operators and users in general don’t need to dive in the details of how OpenStack developers organize their work and definitely should never be asked to use tools designed for and by developers.

Third Party CI group formation and minutes

At this week’s meeting the Third-Party group continues to discuss documentation patches, including a new terminology proposal, as well as CI system naming, logging and test timing. There was also a summary review of the current state of Neutron driver CI rollout. Anyone deploying a third-party test system or interested in easing third-party involvement is welcome to attend the meetings. Minutes of ThirdParty meetings are carefully logged.

The Road To Paris 2014 – Deadlines and Resources

Security Advisories and Notices

Tips ‘n Tricks

Upcoming Events

Other News

Got Answers?

Ask OpenStack is the go-to destination for OpenStack users. Interesting questions waiting for answers:

Welcome New Reviewers and Developers

Will Foster zhangtralon
Walter Heck Gael Chamoulaud
Mithil Arun Fabrizio Fresco
Kieran Forde badveli_vishnuus
JJ Asghar Ryan Lucio
Gilles Dubreuil Martin Falatic
Emily Hugenbruch Bryan Jones
Christian Hofstädtler Tri Hoang Vo
Steven Hillman Ryan Rossiter
Rajesh Tailor Mohit
akash Tushar Katarki
Rajini Ram Pawel Skowron
Pawel Skowron Karthik Natarajan
Abhishek L Ryan Brown
takehirokaneko Keith Basil
Kate Coyne
Ju Lim

Latest Activity In Projects

Do you want to see at a glance the bugs filed and solved this week? Latest patches submitted for review? Check out the individual project pages on OpenStack Activity Board – Insights.

OpenStack Reactions

youwelcome

Trivial fix on a review of someone else while he’s asleep so jenkins can pass

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment

OpenStack Community Weekly Newsletter (July 4 – 11)

OpenStack Swift 2.0 Released and Storage Policies Have Arrived

OpenStack Swift 2.0.0. This release includes storage policies – the culmination of a year of work from many members of the Swift contributor community. Storage policies are the biggest thing to happen in Swift since it was open-sourced 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.

Wrapping up the Travel Support Program – Juno

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 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 is NOW OPEN! You can apply for the Travel Support Program, including costs for travel and accommodation.

Missing Building Blocks for Enterprise OpenStack: Part 1 – High Availability

In the long term debate of pets vs cattle OpenStack has always been on the side of cattles. Dmitriy Novakovskiy 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).

Third Party CI group formation and minutes

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. The group has been working to improve the consumability of the components and documentation. They’re inviting all people involved in CI testing to join and help make the Third Party experience easier for developers and administrators to understand and deploy. The group holds regular weekly meetings. This week they discussed timelines for Cinder and Neutron testing, requirements for documentation patches, a proposal for system terminology and helped openATTIC solve its issues starting up the CI system.

Kudos Corner

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

The Road To Paris 2014 – Deadlines and Resources

Reports from Previous Events

Security Advisories and Notices

Tips ‘n Tricks

Upcoming Events

Other News

Got Answers?

Ask OpenStack is the go-to destination for OpenStack users. Interesting questions waiting for answers:

Welcome New Reviewers and Developers

Matthew Printz Slawomir Gonet
Fabio Massimo Di Nitto Prashanth Prahalad
azher ullah khan takehirokaneko
João Cravo azher ullah khan
Romain Soufflet Wayne
deven Vasiliy Artemev
Julia Kreger Dave Neary
Fabrizio Fresco Arnaldo Hernandez
Anant Patil Amit Kumar Das
Liyi Meng Shivakumar M
Richard Jones Richard Hagarty
Maurice Leeflang Michael Chase-Salerno
sh.huang
jizhilong
Rajesh Tailor
Chris Crownhart
Aleksandr Shaposhnikov
Matjaz Pancur
Alok Kumar Maurya
Jyoti
Andrey Epifanov
Abhishek L
Łukasz Oleś
Victor Chima
FeihuJiang
Mike King

Latest Activity In Projects

Do you want to see at a glance the bugs filed and solved this week? Latest patches submitted for review? Check out the individual project pages on OpenStack Activity Board – Insights.

OpenStack Reactions

wyfail

Elastic-recheck bot pointing us to which bug we need to recheck to

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment.

Wrapping up the Travel Support Program – Juno

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 and its aim is to facilitate participation of key contributors to the OpenStack Design Summit. The program aims at covering costs for travel and accommodation for key contributors to the OpenStack project to join the community at the Summits.

We had 21 people accepted in the program from 8 countries and all around the world. Five people traveled from India, seven from Europe, three from Africa and the rest were from North America and South-East Asia. Of the selected recipients, two were unable to attend due to VISA timing issues, but we were excited to welcome the 21 attendees who were able to make the trip.

IMG_3139

The Foundation spent a total of $33,376 for flights and $7,751 for flights for a total cost for the Foundation of more than $40,000 USD including the costs of 10 access passes granted to non-ATCs (Active Technical Contributors).

The Travel Support Application for the November Summit in Paris is NOW OPEN! You can apply for the Travel Support Program, including costs for travel and accommodation.

The final deadline to submit applications is August 18th, so apply now!

OpenStack Community Weekly Newsletter (June 27 – July 4)

OpenStack Turns 4 – It’s Time to Celebrate the Community!

OpenStack celebrates its 4th birthday July 19, and we’re celebrating with the entire OpenStack community during July!  User maturity, software maturity and a focus on cloud software operations are rapidly emerging for OpenStack and none of it would be possible without the quickly growing OpenStack community. There are now more than 70 global user groups and 17,000 community members across 139 countries, spanning more than 370 organizations. This calls for a big toast to the OpenStack community members and our users.

OpenStack Technical Committee Update (July 1)

This week the TC held a special meeting entirely focused on clarifying some points around DefCore and providing some responses to the questions DefCore posed to the TC. A must-read.

We need to start uncovering OpenStack’s Hidden Influencers

After the summit (#afterstack), a few people compared notes and found a common theme in an under served but critical part of the OpenStack community. Sean Roberts, Allison Randall, and Rob Hirschfeld are expanding the discussion to the broader community in a series of blog posts.

Call for Speakers now OPEN – November Summit in Paris

The Call for Speakers is OPEN for the November OpenStack Summit in Paris! Submit your talks here: submit your talks now. Don’t wait! The Call for Speakers will close on July 28 at 11:59pm CDT.

Reports from Previous Events

Security Advisories and Notices

Tips ‘n Tricks

Upcoming Events

Other News

Got Answers?

Ask OpenStack is the go-to destination for OpenStack users. Interesting questions waiting for answers:

Welcome New Reviewers and Developers

Jeegn Chen Richard Jones
Ciaran O Tuathail Mateusz Blaszkowski
Amit Prakash Pandey EliQiao
Melissa Wong warewang
Gael Chamoulaud Rakesh H S
François Magimel Maurice Leeflang
Tomáš Nováčik Markus Zoeller
Theron Voran Christopher Dearborn
Suthan Venkataramanaiah joanne
Jason Baker Tardis Xu
Harry Rybacki Rui Zang
Anthony Lee Ivo Vasev
Angela Smith Ian Cordasco
Anastasia Martynova stephen
Rikimaru Honjo
Alexander Maretskiy
Alex Weeks
Tim Hinrichs
Mike Bayer
Julia Kreger

Latest Activity In Projects

Do you want to see at a glance the bugs filed and solved this week? Latest patches submitted for review? Check out the individual project pages on OpenStack Activity Board – Insights.

OpenStack Reactions

nitpicking

Getting nitpicked on code reviews

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment.

OpenStack Community Weekly Newsletter (June 20 – 27)

OpenStack Technical Committee Update (June 25)

The TC is busy discussing OpenStack Glance‘s mission, evolving from cataloging and serving Nova disk images to cataloging and serving other artifacts consumed by other OpenStack services, like for example Heat templates. This scope evolution has been under discussion at the last two meetings. Read the other things that keep the TC busy on OpenStack blog.

A Path Towards Contributing (via Commits) in Open Stack

Matt Fischer set himself a goal to contribute 12 patches to OpenStack during 2014: he reached the goal and shared how he did it.

On bug reporting…

Speaking of contributing, sending bug reports is a good way to contribute to OpenStack (together with doing code reviews). Kashyap Chamarthy has a very good guide on how to file a useful bug report.

Engage in technical discussions keeping in mind the OpenStack promise

There is a conversation about what is Cinder itself and what’s the role of its drivers. It’s a highly technical debate and a very important one, where I think this promise needs to be reminded: There will be no “Enterprise Edition”. John Griffith and Ken Hui have a lot of interesting things to say about this and I suggest you to read their posts and read the conversation on this proposed specification. Then we may want to have a wider conversation about Software Defined Storage (SDS) and Cinder.

Reports from Previous Events

Security Advisories and Notices

Tips ‘n Tricks

Upcoming Events

Other News

Got Answers?

Ask OpenStack is the go-to destination for OpenStack users. Interesting questions waiting for answers:

Welcome New Reviewers and Developers

Constanze Kratel Harry Rybacki
TaoBai David Pineau
Kevin McCarthy Angus Lees
Angus Lees Michael Turek
yalei wang IBM xCAT CI
Craig Bryant Clayton O’Neill
Ben Roble Tomáš Nováčik
pritesh Randy Bertram
Vishal kumar mahajan Kevin Fox
Tomoki Sekiyama Aaron Sahlin
Jyotsna yalei wang
sridhar basam
Tomoki Sekiyama
Matthew J Black
Anthony Lee
Jason Rouault
James Kremer
Craig Bryant

Latest Activity In Projects

Do you want to see at a glance the bugs filed and solved this week? Latest patches submitted for review? Check out the individual project pages on OpenStack Activity Board – Insights.

OpenStack Reactions

When your patch has passed half the tempest tests at the gate, and the other half is still running.

With sound

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment.

OpenStack Technical Committee Update (June 25)

Two weeks ago, Russell Bryant inaugurated a series of blogposts about what the Technical Committee (“TC”) is working on. We will regularly post about the outcomes of the TC meetings, and rotate writers to give all TC members a chance to participate and describe what happens in their own words. This post will focus on what happened during the last two meetings.

The TC has several missions, and the topics we cover in TC meetings generally fall into one of them.

Mission #1: Integrated release contents

One of the missions of the TC is to determine what is part of the OpenStack “integrated release” that we collectively produce every 6 months. We manage the “incubation” process, through which selected projects can become part of the integrated release. We also keep an eye on already-integrated projects in case their scope evolves.

That’s the case currently for Glance, whose mission is evolving from cataloging and serving Nova disk images to cataloging and serving other artifacts consumed by other OpenStack services, like for example Heat templates. This scope evolution has been under discussion at the last two meetings. The principle of expanding Glance’s scope is pretty much accepted at this point, but the precise words to describe the new scope are still under discussion.

In order to set clear base expectations for projects in the incubation/integration process track, last cycle the TC came up with a reference document listing all the requirements for incubation, integration and the first integrated cycle that are consensual across TC members. This document is constantly revisited as we continue to raise the quality and convergence bar between integrated projects.

Last two meetings we have been discussing adding a translation support requirement for projects wishing to graduate from incubation. The main objection to it at this point is the lack of automated testing of the translated strings (which resulted in undetected I18N problems in the past). It looks like when this is addressed, this requirement will probably make it to the reference document.

Raising requirements for new entrants is one thing, but sometimes existing integrated projects do not fill those new requirements. This creates a gap that we need to address. During this cycle we reviewed most existing integrated projects (Heat and Swift are still pending). When a gap was raised, PTLs responded with a proposed “gap coverage plan” to address it.

The last project to go through that exercise was Glance, where a single gap around testing coverage was raised. Mark Washenberger (Glance PTL) created a gap coverage plan to address it and that plan was blessed by the TC at the last meeting.

Having plans is a good thing, but we also need to check that projects meet the deadlines that they set in such plans. Last week, after the juno-1 development milestone, we reviewed the progress on gap coverage plans. Ceilometer plan is on track, still targeting the juno-2 milestone for fully covering the gap. Horizon plan is mostly on track. Neutron has an ambitious gap coverage plan, and work on all gaps has started; gap 4 is a bit late (was planned to be completed by juno-1), but it’s also been determined to just be one API call. Trove plan is on track, and work started on all items.

Finally, having responsibility over the integrated release also means making sure we use terminology across integrated projects consistently. An issue was raised about the use of “certified” terminology to qualify CI testing on some projects. After open discussion on the -dev mailing-list and at the TC meeting, there was agreement that “certified” terminology was too loaded and should be phased out in favor of some variation around “tested”.

Mission #2: Representation of technical contributors

The TC is a directly-elected body representing all the technical contributors to the project. It is the final decision-making entity over technical matters in OpenStack as a whole. Some issues that can’t be solved at a lower level are sometimes escalated to the TC for final resolution, and the TC is also a convenient conduit for other OpenStack governance bodies to ask for general technical input.

Two issues were brought to the TC recently. The first one is about expected election behavior for our technical elections (PTLs and TC members). Our current election procedure doesn’t clearly describe expected behavior, and a proposal was raised to cover that. While everyone agrees on what is acceptable behavior and what is not, there are two ways of addressing issues if they arise. One is to piggy-back on the Community Code of Conduct, which clearly states that you should respect the election process. The other is to call out out-of-line behavior and trust the voters to make their own judgment about it. Both options are and will stay available, but we are still discussing which of those options (if any) we should encourage by making it part of the TC resolution. This discussion is on-going and will continue in a future meeting.

The other issue being brought to the TC were requests from the Foundation Board of Directors “Defcore” subcommittee for technical input to use as part of their work on trademark rules. There are two types of requested inputs. One is to provide for each project “designated sections” of code that you need to run in order to use the “OpenStack” trademark. The other is to give precise scoring for “core capabilities”: for each capability, indicate whether it’s part of the TC future direction or if it’s on its way to be deprecated.

While those inputs are technical (and we even voted on guidelines to help coming up with answers), some TC members expressed clearly their discomfort. Asking the representation of OpenStack contributors to designate parts of OpenStack that may just be replaced by proprietary alternatives (while still being called “OpenStack”) just crosses the line as to what they consider acceptable. Our “technical” answer might be read as an endorsement, or collaboration toward a behavior we don’t really want to encourage.

This tension has been surfacing every time Defcore was discussed at the TC meeting, and it’s difficult to address it between two topics in a one-hour online meeting. We have therefore scheduled a Defcore-specific TC meeting for July 1st (20:00 UTC in #openstack-meeting on Freenode IRC), and will try to clearly list concerns beforehand to ensure meeting clarity.

OpenStack Community Weekly Newsletter (June 13 – 20)

Summer Speaking Sessions and Call for Papers

Summer is in full swing and there are some great industry events coming up on the OpenStack Marketing calendar, as well as Call for Proposals deadlines!

Marconi to AMQP: See you later

In the last couple of weeks, Marconi’s team has been doing lots of research around AMQP and the possibility of supporting traditional queuing systems. Flavio Percoco, believed with others that this capability would be useful. However, after digging more into what’s needed and what supporting traditional brokers means for Marconi, the community changed its mind and now believes supporting such systems doesn’t make much sense anymore. This post explains why.

Tracking multiple OpenStack projects using StoryBoard

StoryBoard is a new task tracking system which is aimed at the systems where projects are closely related, and OpenStack is definitely a good example of that. In inter-related systems like OpenStack, a feature or a bug usually affects more than one project, so it should be tracked simultaneously across those projects. The proof-of-concept was presented in the Havana release cycle by OpenStack release manager Thierry Carrez, and active development started during the Icehouse development cycle. The project is now driven by three major contributor companies: the OpenStack Foundation, Mirantis, and HP.

Breaking news:OpenStack Object Storage ‘Storage policies’ merge today

The series of patches that will eventually lead to Swift 2.0 merged today. Many Swift contributors have been working on storage policies for quite some time now. It’s a huge feature and improvement to Swift that enables a ton of new use cases. Storage policies allow deployers to configure multiple object rings and expose them to end users on a per-container basis. Deployers can create policies based on hardware performance, regions, or other criteria and independently choose different replication factors on them. A policy is set on a Swift container at container creation time and cannot be changed. Full docs and more details about the roadmap in this message by John Dickinson.

Security Advisories and Notices

Tips ‘n Tricks

Upcoming Events

Other News

Got Answers?

Ask OpenStack is the go-to destination for OpenStack users. Interesting questions waiting for answers:

Welcome New Reviewers and Developers

peng fei wang Renjie Sun
Doug Wiegley Vishal kumar mahajan
Stephen Jahl Nikunj Aggarwal
joanne Lennart Regebro
Richard Hagarty João Cravo
Flavio Fernandes Anna Eilering
yingjun Vivek Jain
Tom Cammann Susanne Balle
Julie Gravel Stephen Balukoff
Rikimaru Honjo Shayne Burgess
Diana Whitten Nathan Manville
Max Grishkin
German Eichberger
Dustin Lundquist
Doug Wiegley
Yi Sun
Przemyslaw Czesnowicz
FrazyLee
Ying Zuo
Julie Gravel
Jorge Chai
Bradley Klein

Latest Activity In Projects

Do you want to see at a glance the bugs filed and solved this week? Latest patches submitted for review? Check out the individual project pages on OpenStack Activity Board – Insights.

OpenStack Reactions

its-friday

When I see the OpenStack newsletter in my mailbox

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment.

OpenStack Community Weekly Newsletter (June 6 – 13)

Moving forward as a User Experience Team in the OpenStack Juno release cycle

The OpenStack Juno Summit in Atlanta was a major turning point for User Experience professionals working on OpenStack. There were 3 specific design sessions around UX work and 1 talk on the persona work, all with great attendance, and the whole team committed taking a number of actions to take over the course of the Juno development cycle. Liz Blanchard summarized them quite nicely.

OpenStack Technical Committee Update

The OpenStack Technical Committee (TC) meets weekly and recently decided to publish regular updates about the TC to the OpenStack blog. The first post has news about the graduation process, Glance and Designate.

Calling on Security Engineers / Developers / Architects – Time to share your toys

Lets work together and openly on security review and threat analysis for OpenStack. There are currently scores of security reviews taking place on OpenStack architecture, projects and implementations. Robert Clark sent a call for action to OpenStack developers: “All the big players in OpenStack are conducting their own security reviews, we are all finding things that should be addressed in the community and that we are all missing things that others have found too.” Robert’s call is for all the security people out there in the community to come together and share expertise on Threat Modelling/Analysis in OpenStack.

Reports from Past Events

Tips ‘n Tricks

Security Notes and Advisories

Upcoming Events

Other News

Got Answers?

Ask OpenStack is the go-to destination for OpenStack users. Interesting questions waiting for answers:

Welcome New Reviewers and Developers

Petersingh Anburaj mark collier
Ellen Hui Rey Aram Alcantara
Pierre Rognant Patrick Crews
ajay Angela Smith
Rui Zang Zu Qiang
Rahul Verma Vladimir Eremin
Christoph Arnold Praveen Yalagandula
Amit Prakash Pandey
Ton Ngo
Tom Cammann
Sam Leong
Paul Montgomery
James Chapman
Gal Sagie

Latest Activity In Projects

Do you want to see at a glance the bugs filed and solved this week? Latest patches submitted for review? Check out the individual project pages on OpenStack Activity Board – Insights.

OpenStack Reactions

tumblr_inline_n1h25lbMTa1raprkq

Giving +2 out of fear

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment.

OpenStack Technical Committee Update

The OpenStack Technical Committee (TC) meets weekly. During the meeting on 2014-06-03, one of the topics we discussed was the relatively low turnout for the TC election as compared to the PTL elections. The most productive thing to come out of that discussion was that we needed to do a better job of communicating what the TC is working on and why it is important. As a result, we will be posting regular updates about the TC to the OpenStack blog. This first post will likely be a bit longer as it’s important to set up some of the context for the things we are currently discussing.

How the TC was formed is described in the history of OpenStack open source project governance  by the current chair of the TC, Thierry Carrez.

Openness

Open governance is an important value held by OpenStack and the TC wants to be as open as possible. In addition to these regular updates, you can find the details of everything we do in a few other places. The archives of the openstack-tc mailing list are open. Our weekly IRC meetings are public and logged.

All project governance work is managed in a git repository and changes are reviewed in gerrit in the same way that we review code. Everyone that is interested is invited to comment on proposed governance changes. You can find a list of changes under review here. You can find a list of previously approved changes and the discussions that happened on their reviews here.

Project Incubation and Graduation Requirements

One of the responsibilities of the TC is to manage the set of projects that are included in the OpenStack integrated release. New projects may apply to be incubated. Incubated projects will later be reviewed for graduation from incubation. A graduated project is a part of the integrated release.

As OpenStack has grown, it became clear that we needed to be much more clear around our expectations of projects for incubation and graduation. Over the last year we worked to formalize these expectations in a document in the governance repository. We approved the first version of this document on December 2, 2013. We have been updating it ever since as more issues need to be clarified. You can find the latest version of that document in the Governance git repository.

Toward the end of the Icehouse development cycle, we started a process of going through all projects already in the integrated release and evaluating them against this criteria. For any project that has gaps against these expectations, we require that the PTL present a plan for addressing these gaps during the Juno cycle.

Glance

The latest project review was for Glance, during the TC meeting on 2014-06-10. The only gap found for Glance was around tempest test coverage. Specifically, Tempest does not cover uploading a real binary image to Glance. The Glance PTL will now come up with a plan to address this gap and the TC will review progress against this plan throughout the Juno cycle.

We actually spent quite a bit of this meeting talking about Glance. The most controversial topic is around the proposal to increase its scope. Glance is currently focused on disk images. There is a proposal against the governance repository to expand its scope to cover a more general definition of artifacts. The particular use cases that inspired this direction for Glance is the desire to store things like Heat or Murano templates. In the end, there seems to be broad support for the general direction proposed. We still have some work to do to get the wording of the mission statement in a form that everyone is comfortable with.

Finally, the Glance project brought an important cross-project API consistency question to the TC. Specifically, they have an alternative method for how they would like to expose actions through their API which is different from how Nova does it currently, for example. There was support for the specific proposal. However, it raises the larger question about how we go about best working toward cross project API consistency. We would love to have someone lead an effort to create a cross-project API style guide for OpenStack, but it’s unclear who will do it and exactly who would review and approve the content. I expect this to be an ongoing discussion.

You can find the full mailing list thread that spawned this API discussion in the archives starting in May and continuing in June.

Designate

Another project that has received a lot of attention recently is Designate, which provides DNS as a Service for OpenStack. This is a sorely needed feature for OpenStack deployments so I’m very happy to see the progress made in this area.

The project recently applied for incubation. This is actually the second time that Designate has applied for incubation. The first time was one year ago, in June of 2013. After the first application, the TC concluded that it was a bit too early to incubate the project. There were various concerns, but the primary one was the level of involvement in the project, in terms of individuals and separate companies.

Designate has matured a good bit over the last year and I’m proud to announce that the application has been approved. Designate is now an incubated project!

The earliest Designate will be included in the integrated release would be the K release. Given that we’re already well into the Juno cycle, the L release seems more realistic. This is a topic that the TC would revisit at the end of the Juno development cycle.

Future Updates

We want to make these updates from the TC as useful as possible. If you have any comments or suggestions, please let us know!

Back to top