Introduction

Welcome to Last week on OpenStack Dev (“Lwood”) for the week just past. For more background on Lwood, please refer here.

Basic Stats for week 16 May to 22 May 2016 for openstack-dev:

~584 Messages (down about 27% relative to last week)

~194 Unique threads (down about 17% relative to last week)

After last week’s busiest week in Lwood history, a return to average traffic levels this week. This week is the first where I’m actively keeping an eye on the rather quieter openstack-operators and openstack-community lists, not sure if this will be a long term change, we’ll see :)

Notable Discussions – openstack-dev

New API guidelines for review

Mike McCune writes that there are two new API guidelines ready for review by interested parties;

Request for Volunteer Trainers at PyCon Portland OR

David Flanders notes that the OpenStack Foundation has been given the opportunity to run a 90 minute training session for Application Developers at upcoming PyCon in Portland, OR. As he rightly points “This is a great opportunity to road test the SDKs with our main user audience: application developers.” If you’re interested in helping out, please contact David ASAP :)

A refresher on the global requirements process

Dims Srinivas provides a nice concise primer/reminder on how to work with the global requirements process as it currently stands and also notes there is a new team being formed to further streamline the process.

Languages vs. Scope of OpenStack (was The Monster Thread :)

In his initial post and a subsequent reply to the thread Thierry Carrez seeks to summarise the core issues brought to light by the recent thread on bringing golang in as a supported language for developing core OpenStack projects/code. At the time of writing the thread is actually pretty short so you may want to read the various well thought through contributions yourself, but in essence;

Some projects in OpenStack are more low-level than others and require the sort of optimisation that can only be achieved in languages other than python. It’s possibly helpful to think of language choice in these terms rather than the specific language itself.

A key question is where does OpenStack stop and the wider Open Source community start – it’s suggested that there’s a couple of ways to think of this;

The first way is community-centric: “anything produced by our community is OpenStack”

The other way is product-centric which leads to the idea that “lower-level pieces are OpenStack dependencies, rather than OpenStack itself”

Thierry posits that OpenStack dependencies can and should be developed in whatever language best suits the task at hand and so doing is relatively less costly from an OpenStack community standpoint. Chris Dent notes that a similar way to make this distinction is whether the tool is useful and usable outside OpenStack.

Welcome Keystone to the World of Python 3

Morgan Fainberg notes with thanks to all involved that Keystone is now Python 3.4 compatible. Nice work :)

Austin OpenStack Summit Wrapup – Part IV

No new posts with specific Summit wrap-ups in them but as mentioned last week I’ve now pulled together an as concise as I could make it summary of those posts in a blog post here. If there are further updates I’ll edit the post accordingly.

Notable Discussions – other OpenStack lists

As noted above, as of this week I’m trialing watching what’s happening on the openstack-operators and openstack-community lists as well…

Defining ‘users’, planning ops mid-cycles and related meetings

Over on the openstack-operators mailing list, Chris Morgan wrote a summary of one of the discussions at the Ops Meetup Team IRC meeting (!) Of note and worth a quick read is the thoughtful definition of ‘users’ for the purposes of working out who should attend Operator Mid-Cycles.

In short the preference is for people involved in large scale public and private clouds to attend, more so than vendors of said clouds. However individuals who work for large scale cloud vendors are encouraged to attend if they feel they can contribute, but are asked to wear their user rather than “promotional” hat (I paraphrase this latter).

In a related thread on openstack-operators Tom Fifield announces the meeting in question here and provides a neat summary a few days later in this post. The regular IRC meetings will occur every second Tyesday 1400h UTC in the #openstack-operators channel.

Update on Non-ATC Recognition

An email from Edgar Magana prompted the ever efficient Shamail Tahir to give a quick summary of where this process is up to.

I defer to Shamail’s email for the details but the desire to have a way to recognise contributors to OpenStack that don’t quite fit the Active Technical Contributor (ATC) definition has led to defining an Active User Contributor (AUC). This process is ongoing but will provide a defined way of identifying folk that fit this mold and so their contribution to OpenStack more generally.