This week sees the second Everything Open conference being held in Gladstone, Queensland. Alas I’m not there :/

I’ve had the good fortune to attend CALU-99 as well as something like 20+ years of linux.conf.au events that followed as well as last years Everything Open. I very much saw EO as a sensible evolution of LCA and worthy of being considered such.

I’d hoped to attend the Gladstone event, but then had some (very routine) medical stuff scheduled at the same time, so I resigned myself to not attending. Somewhat ironically the aforementioned appointments got moved, by which time a work commitment had come up during the same week. This latter is quite special too as I get to spend time with many of my Grafana colleagues – in a fully distributed/post geographical company this is quite a special thing.

So I very much wish all involved in/at EO 2024 the best. I’m sure it’ll be a great week, some fantastic talks, hallway tracks, keynotes and everything else, I’m just a little sad that I’ll only be there in spirit.

I guess a bit of melancholy too as it means an end the unbroken run I had of attending the CALU/LCA/EO series of events over the years!

Happy hacking all :)

Introduction

Welcome to Last week on OpenStack Dev (“Lwood”) for the week ending 7 February 2016. For more background on Lwood, please refer here.

Basic Stats for week 1 to 7 February 2016:

• ~585 Messages (down about 6% relative to last week)
• ~185 Unique threads (up about 4% relative to last week)

Steady as it goes this week pretty much.

Notable Discussions

Review requested for Rolling Upgrades and Updates user story

Kenny Johnston writes on behalf of the Product Working Group seeking feedback/additional reviews on a user story that discusses Rolling Updates and Upgrades.  If you’re working on or interested in improving upgrades please comment whether you’re a user or developer or both.  Given the importance of upgrades/updates for the OpenStack community (users and developers alike) this is a conversation worth joining :)

What makes it “Open” enough for OpenStack ?

Thierry Carrez kicked off a long but interesting thread where he opines “…If you need proprietary software or a commercial entity to fully use the functionality of a project or getting serious about it, then it should not be accepted in OpenStack as an official project…”  Thierry’s post and the discourse that follows is an intriguing and (generally!) well thought out discussion around this knotty topic.

Doug Hellman notes early in the thread that there is a more concrete case being considered at present in the form of the Poppy Project – a project that provides an Open Source front end/API to otherwise commercial services.

Well worth a read, particularly if you work for commercial entity that provides OpenStack related services and contribute resources to same.

The Trouble With Names

Sean Dague posted a thought provoking piece on the difficulty with names in OpenStack.  This in the context of project names (e.g. “nova”), common/generic names (e.g. “compute”) as well as namespaces in code repositories and elsewhere.

A lengthy discussion ensued with a general agreement that there was a need to do better, slightly less consensus on how that might achieved.

My impression and certainly my own experience is that many newcomers to OpenStack struggle with the “in joke” nature of some names in the early days and so it becomes part of the barrier to entry during that crucial period.  Please take a read of the thread and throw your views into the mix if you’re so inclined :)

Time to separate Design Summits from OpenStack conferences ?

In what looks like it will become a busy thread this week, Jay Pipes posits that perhaps the time has come to separate the OpenStack Design Summits from the more commercially oriented aspects of the Conference.

An interesting dialog follows with folk speaking for and against, but invariably constructively about the idea. James Bottomley is one of a number of folk who contributed to the discussion – he gives an interesting perspective from the experiences of the Linux Foundation and broader Linux community.

New API Guidelines for cross project review

From Michael McCune one new API guideline up for cross project review – “Must not return server-side tracebacks”

OpenStack Mentoring

Mike Perez followed up last weeks post with more details about the OpenStack Mentoring program and the importance of same to growing the OpenStack community.  if you’re interested in helping out, or finding a mentor yourself, Mike’s post has the details.

Further DocImpact Changes

Lana Brindley gave an update on changes to the behaviour of the DocImpact script.  The result of this most recent set of changes is to revert the earlier tweaks and in so doing shift the responsibility for triage of incoming DocImpact changes into the project teams themselves.  More details in Lana’s post or here.

Upcoming OpenStack Events

Some of the OpenStack related events that cropped up on the mailing list this past week.  Don’t forget the OpenStack Foundation’s comprehensive Events Page for a comprehensive list!

Midcycles & Sprints

• [glance] – Virtual Mid-Cycle meeting next week​ (Feb 11 & 12) – Flavio Percoco
• [storyboard] – Midcycle Meetup – Zara Zalmeche

People and Projects

• [Magnum] New Core reviewers proposed (Tom Ngo and Egor Guz) – Adrian Otto
• [Solum] Nominating Vijendar Komalla for Solum core – Devdatta Kulkarni
• [Manila] Nominate Rodrigo Barbieri for core reviewer team​ – Ben Swartzlander
• [telemetry][aodh] Announcing Liusheng as new Aodh liaison​ – Gordon Chung
• [lbaas] [octavia] Proposing Stephen Balukoff as Octavia Core​ – Michael Johnson

Further Reading & Miscellanea

Don’t forget these excellent sources of OpenStack news

• Technical Committee Highlights by Anne Gentle
• What’s Up, Doc? by Lana Brindley
• OpenStack Developer Mailing List Digest by Mike Perez
• OpenStack Foundation Blog

This edition of Lwood brought to you by Joe Walsh (Funk 49-50) and Booker T Jones (Live, The Road from Memphis, Potato Hole) amongst other tunes.