Lwood-20151227

December 28, 2015 at 20:11 · Filed under Lwood, OpenStack

Introduction

Welcome to Last week on OpenStack Dev (“Lwood”) for the week ending 27th December 2015. For more background on Lwood, please refer here.

Basic Stats for week 21st to 27th December 2015 :

  • ~307 Messages (down almost 50% relative to last week)
  • ~121 Unique threads (down about 34% relative to last week)

If nothing else we can perhaps conclude from the drop in traffic that OpenStack developers know when to take a break, may well be I need to learn something from them :)

Notable Discussions

IRC meetings warning: two “odd” weeks coming up (!)

Many of the IRC meetings within the OpenStack community are scheduled on a bi-weekly basis according to ISO week number.

Thierry Carrez points out that this will cause some quirks as there are two odd numbered weeks one after the other (Wk53 immediately precedes Wk1).

Due to a bug in the way they’re generated, the automatically generated iCals will be out of sync until they regenerate on Week 1.

Note that many projects are not running regular meetings until early January in any case – there is an at least partial list of the projects affected in the “General Events” section below.

Survey/feedback sought on network software verification research

Arseniy Zaostrovnykh posts that he is doing some research on the verification of network applications as part of the EPFL PhD program.  The team he’s involved with are keen to maximize the utility of what they’re working on and so are conducting a small survey.  

While there’s not a lot more detail in the post itself joining some dots based on the questions asked leads me to think it could be quite an interesting project… :)

Upcoming OpenStack Events

A summary of OpenStack related events that cropped up on the mailing list this past week that seemed worth calling out.  Don’t forget the OpenStack Foundation’s excellent Events Page for a comprehensive list!

General Events

Once again a reminder that many projects and working groups are cancelling or altering the schedule of their regular IRC meetings for the period spanning the last week of December 2015 into early January 2016.

Those I’m aware of are listed below, but worth double checking any that you usually attend to save that unnecessary early morning start or late night :)

  • A (possibly incomplete) list for this week: Nova, CloudKitty, Telemetry, Neutron, Ironic, Cross Project Meeting, Vitrage, Puppet, Watcher, Cinder and Sahara
  • For reference the (also possibly incomplete) list from last week’s Lwood: NFV, TelcoWG, Neutron, DVR, Searchlight, Horizon, Glance, Fuel, QA, Performance, Nova, Tacker, Stable, Freezer, Lbaas and Octavia

Midcycles

People and Projects

Further Reading & Miscellanea

Don’t forget these excellent sources of OpenStack news – all three are currently on vacation by the looks so links are to the most recent edition :)

 

This edition of Lwood brought to you by Tal Wilkenfeld (Transformation), Miles Davis (Amandla, Birth of The Cool), Peter Gabriel (Shaking The Tree) amongst other excellent tunes.

In closing the last Lwood of 2015, I extend to you the wish that 2016 will bring you all that you need and a fun amount of what you want :)

Comments

Lwood-20151220

December 21, 2015 at 17:41 · Filed under Lwood, OpenStack

Introduction

Welcome to Last week on OpenStack Dev (“Lwood”) for the week ending 20th December 2015. For more background on Lwood, please refer here.

Basic Stats for week 14th to 20th December 2015 :

  • ~610 Messages (down about 4% relative to last week)
  • ~184 Threads (down about 8% relative to last week)

All getting a little quieter as we near the end of year, a shorter Lwood as a result to the point where I’m worrying I’ve missed something!

Notable Discussions

Two new Open Stack Security Notices (OSSN 0061, 0062)

Glance image signature uses an insecure hash algorithm (MD5) (OSSN 0061)

From the summary “During the Liberty release the Glance project added a feature that supports verifying images by their signature. There is a flaw in the implementation that degrades verification by using the weak MD5 algorithm.” More discussion in the original post or OSSN 0061

Potential reuse of revoked Identity tokens (OSSN 0062)

From the summary “An authorization token issued by the Identity service can be revoked, which is designed to immediately make that token invalid for future use. When the PKI or PKIZ token providers are used, it is possible for an attacker to manipulate the token contents of a revoked token such that the token will still be considered to be valid.  This can allow unauthorized access to cloud resources if a revoked token is intercepted by an attacker.  More in the original post or OSSN 0062

Gerrit Upgrade to 2.11 Complete

Khai writes to confirm the planned upgrade to v2.11 for the main openstack Gerrit instance was completed successfully. The changes were flagged in an earlier post covered in Lwood-20151018

Smaug – a new Application Data Protection project

Eran Gampel announced a new OpenStack project “Smaug” that is aiming tp provide Disaster Recovery for all OpenStack resources.  The post includes an encouraging sounding mission statement for the project, an invitation to join in the bi-weekly meetings and review the proposed Smaug API v1.0

Naming polls for N and O are open

Monty Taylor noted early in the week that polls are open for the OpenStack “N” and “O” names.  Polls close at the end of December 22 (UTC) – a less than 24h from now.

Clarifying “elusive unicorns” – Rolling Upgrades for Cinder

Michael Dulko provided a nicely put together summary of the conversations around rolling upgrades for Cinder (including the reference to “elusive unicorns”) – well worth a read.

Upcoming OpenStack Events

A summary of OpenStack related events that cropped up on the mailing list this past week that seemed worth calling out. Don’t forget the OpenStack Foundation’s excellent Events Page for a comprehensive list though!

General Events

  • A reminder that many projects and working groups are cancelling regular IRC meetings over the last couple of weeks of December 2015 and early January 2016 – worth double checking any that you usually attend to save that unnecessary early morning start or late night :)
    • A (possibly incomplete) list: NFV, TelcoWG, Neutron, DVR, Searchlight, Horizon, Glance, Fuel, QA, Performance, Nova, Tacker, Stable, Freezer, Lbaas and Octavia

Midcycles

  • [kosmos] Midcycle 20-22 January, Seattle, WA, USA – Graham Hayes
  • [designate] Midcycle – 8-10 February, Galway, Ireland – Graham Hayes
  • [tacker] Surveying dates for midcycle – End January, San Jose, CA, USA – Sridhar Ramaswarmy
  • [ansible] Midcycle Partially co-located with Ops Midcycle 15-17 February, UK  – Jesse Pretorious

People and Projects

Further Reading

Don’t forget these excellent sources of OpenStack news :)

Miscellanea

This is the last Lwood before Christmas and so I take this opportunity to wish you and yours the very best for Christmas or your preferred observance at this time of year! :)

This edition of Lwood brought to you by Marillion (A Singles Collection, Clutching At Straws), Queen (Greatest Hits I & II), Richard Clapton (The Best Years of our Lives), Rush (Hold Your Fire) amongst other excellent tunes.

Comments

Lwood-20151213

December 15, 2015 at 00:43 · Filed under Lwood, OpenStack

Introduction

Welcome to Last week on OpenStack Dev (“Lwood”) for the week ending 13th December 2015. For more background on Lwood, please refer here.

Basic Stats for week 7th to 13th December 2015 :

  • ~635  Messages (down about 20% relative to last week)
  • ~201 Threads (down about 13% relative to last week)

Traffic and threads have dropped back to pre- R1 milestone rush levels…

Notable Discussions

Private Links in Launchpad

Roman Prykhodchenko pens a timely reminder about ensuring that when posting links into launchpad or other OpenStack sites, that we only reference things that are public.

He alludes to some specific examples from fuel where he’s marked bugs incomplete for this very reason, but I’d venture it’s something that crops from time to time up across most FOSS projects.

Release Schedules and Project Deadlines delivered direct to your calendar ?

Flavio Percoco writes to float the idea of creating .ics generated automagically for OpenStack Release Schedule and Project Deadline information.  A flurry of replies all variations on the theme of “that sounds great” and a few messages later a post from Louis Taylor with a proposed implementation.

Neato!

Changes to automated behaviour when patches merge

Doug Hellmann’s post follows one from late November and notes that as part of the process of deprecating the use of launchpad for tracking completed work there have been changes to the default behaviour when patches merge.

From herein by default behavior is that when a patch with “Fixes-Bug” in the commit message merges the bug will move to “Fix Released” (a closed state) instead of “Fix Committed” (a “still open” state).  Thierry Carrez later notes that this default behaviour can be changed on a per project basis if required.

New Release of the Gabbi HTTP API tester

Chris Dent posted midweek to announce a new version of Gabbi – a testing library that uses YAML format to declare HTTP API requests and their expected responses and so allow functional testing of OpenStack (and other HTTP request based) APIs.

Chris goes on to note that Gabbi is being used by Ceilometer, Gnocchi and AODH for some functional tests of their APIs and he’s happy to assist other projects in making use of it – reach out to him on IRC if you get stuck.

Upcoming OpenStack Events

This section was previously called “Midcycle dates and locations”, new name reflects the observation that there were other OpenStack related events that crop up on the mailing list that were worth calling out.  Don’t forget the OpenStack Foundation’s excellent Events Page for a comprehensive list though!

General Events

  • Open Cloud Symposium at linux.conf.au 31 January – 5 February in Geelong, Victoria, Australia – Josh Hesketh
    • Yes this is a repeat, but LCA is near and dear to me so a little extra publicity :)

Midcycles

People and Projects

Further Reading & Miscellanea

Don’t forget these excellent sources of OpenStack news :)

This edition of Lwood brought to you by Black Country Communion (Afterglow), Yngwie Malmsteen (“Far Beyond the Sun” Live), Magnum (On a Storyteller’s Night) and Rock of Ages (Original Cast Recording) amongst other excellent tunes.

Comments

Lwood-20151206

December 7, 2015 at 23:22 · Filed under Lwood, OpenStack

Introduction

Welcome to Last week on OpenStack Dev (“Lwood”) for the week ending 6th December 2015. For more background on Lwood, please refer here.

Basic Stats for week 30th November to 6th December 2015 :

  • ~793 Messages (up about 28% relative to last week)
  • ~232 Threads (up about 26% relative to last week)

Traffic and threads up markedly this week – R1 milestone traffic and some long technical threads at least part of the trend.

Notable Discussions

Semi automated static code analysis of OpenStack modules

Péter Hegedűs writes of work underway at the University of Szeged in conjunction with Ericsson Hungary that seeks to harden the codebase and so improve the overall quality of OpenStack.  

They are using an interesting combination of automated code analysis and manual review to find things like long/complex methods, duplicated code and so forth.  Worth checking out the information in the original thread or on the Wiki page they’ve put together.

Improving the effectiveness of Cross-project specs

Mike Perez puts forward an excellent suggestion for improving the effectiveness of Cross-Project specifications.  The essence of the idea is that projects nominate a cross-project liaison person who can take some of the load off the PTL by explicitly keeping an eye on things that come in to the project from the cross-project repo and ensure they get the attention required.

A neat (and well received) solution – please take a moment to acquaint yourself with the proposal particularly if if you’re a PTL or Core :)

Should DefCore explicitly require running Linux as a compute capability ?

Chris Hodge posts a request for comment on whether Defcore should explicitly require running Linux as as a compute capability.  This is an offshoot of an earlier conversation (reported in Lwood-20151122) kicked off by Egle Sigler which raised the more general question of what should and shouldn’t be OS specific.

It’s a pretty nuanced matter (and isn’t as simple as should we always be able to “run Linux”) – the summary document is worth a skim if DefCore is up your alley :)

New Mitaka Release Schedule Page

Thierry Carrez notes that “As part of the effort to move reference information off the wiki to a more peer-reviewable area, the Mitaka release schedule page was moved…” it’s new home is http://docs.openstack.org/releases/schedules/mitaka.html.

In the post he goes on to explain that projects can now propose their own deadlines through a page in the git repository and asks that projects add their information to same – the aim being to make the page a one stop shop for release information across OpenStack as a whole.

Desperately seeking the Java mirror person

Well perhaps not desperately, but Michael Krotscheck tells of a conversation some months ago on #openstack-infra where someone asked for a maven repository mirror for java builds.  He’s not been able to find trace of the person or conversation and would like to follow up with them :)

He also invites anyone else curious about the topic to help review the spec and/or patches.

OpenStack Health Dashboard

Matthew Treinish announces a rather neat test results dashboard that provides information from the gate.  Rather cool, rather useful!

Privacy issues with some OpenStack documentation ?

Thomas Goirand kicked off a couple of threads (1st here,  2nd here) late in the week both flagging concerns about the use of Google Analytics, generic CDN and other external links within OpenStack documentation.

While the tone of the the posts are a little emotive in places the technical merit of what he puts forward are valid enough and some solutions have already been put forward but the community to address them.

Upcoming OpenStack Events

This section was previously called “Midcycle dates and locations”, new name reflects the observation that there were other OpenStack related events that crop up on the mailing list that were worth calling out.  Don’t forget the OpenStack Foundation’s excellent Events Page for a comprehensive list though!

General Events

Midcycles

People and Projects

Further Reading & Miscellanea

Don’t forget these excellent sources of OpenStack news :)

This edition of Lwood brought to you by Harunobu Okubo and friends (performing ELP), Vanessa Rodrigues (Soul Project), Liquid Tension Experiment (2) amongst other excellent tunes.

 

Comments

Lwood-20151129

November 30, 2015 at 23:59 · Filed under Lwood, OpenStack

Introduction

Welcome to Last week on OpenStack Dev (“Lwood”) for the week ending 29th November 2015. For more background on Lwood, please refer here.

Basic Stats for week 23rd to 29th November 2015 :

  • ~618 Messages (down about 2% relative to last week)
  • ~184 Threads (down about 3% relative to last week)

Traffic and threads steady despite holidays in some parts of the OpenStack world…

Notable Discussions

Work in progress: Grafana Dashboard for Bugs

Lwood-20151115 mentioned the recently launched http://grafana.openstack.org website and this week there’s a post and proof of concept mockup from Markus Zoeller outlining some work he’s doing towards a bug dashboard for OpenStack projects.  He’s actively soliciting feedback on the proposal and assistance – check it out and pitch in if you can :)

Encouraging first time contributors through special bug tags

Shamail Tahir kicks off an interesting thread about using bug tags to encourage first time contributors.  In essence the idea is to have a specific bug tag (probably a new one) that flags bugs as being suitable for first time contributors.  Some review logic could be added that would reject or at least -1 patch-sets that weren’t from a first time contributor.

A good bit of discussion followed including the suggestion that projects may wish to adopt this and take the idea a little further by having certain bugs defined this way that would also have additional comments in them to help the newcomer know where to go solution wise.

Tweaking the IRC Meeting Infrastructure

Tony Breeds puts forward a very cogent case for making some tweaks to the IRC channels used for OpenStack related meetings.  In short he proposes adding #openstack-meeting-5 and renaming #openstack-meeting-alt to #openstack-meeting-2 (which is what it effectively is anyways)

The proposal was well received it looks like the changes will proceed over the next week or two.

Mitaka 1 Milestone week November 30th – December 4th

Doug Hellmann reminds us that week R-18 (that’s this week) is the Mitaka 1 milestone deadline and provides a hand list of things that projects should be doing in light of this.

Moving to a trusting model ?

Morgan Fainberg puts forward a proposal to subtly alter the social policy that is applied to the permitted relationship between who writes code, who reviews code and who reviews/approves code for inclusion into OpenStack.

As it stands most projects prevent each of these three people being from the same company/organisation – the default is, in a sense, “distrust”.  In his post Adam Young provides a little further context around why the policy was worded the way it was – interestingly it’s as much about protecting employee developers from management pressure as anything else.

Morgan’s proposal is essentially that it be made “ok” for all three kinds of involvement (write code, review code, approve code) to be done by people from the same organisation/company with the acknowledgment that if it is felt this trust is broken, the changes can be reverted and the core status of those involved be reviewed.  a “trust” rather than “distrust” model.

While it’s a longish thread (27 messages at the time of writing) I’d commend it to all involved in OpenStack development and, equally people who manage folk that undertake this work.

Changes to the DocImpact flag

Lana Brindley writes of changes to the DocImpact flag – a flag used by developers to notify the Documentation team when a patch might cause a change in the docs.  

To quote Lana: “TL;DR: In the future, you will need to add a description whenever you add a DocImpact flag in your commit message.”  

The rationale is eminently sensible – providing a description will save the Docs folks having to dig quite so deeply to understand what the actually impact on the documentation will be.

More detail can be found in the original post or the spec.  Significantly, a Jenkins job will test for this and the job will fail if there is no description – so please bear this in mind for future patches.

Process change for closing bugs when patches merge

Doug Hellman advises of some changes to automated behaviours when patches containing “Closes-Bug” are merged.  Such patches will no longer automatically make the patch status update to “Fix Committed” as it’s seemingly been a bit of a wonky part of the release process.

Implications of this likely apply to all OpenStack developers, so if that’s you, please take a few minutes to read Doug’s post…

Releases vs Development Cycle explained in a single post

Succinctly put by Thierry Carrez in this email – worth a quick read but, frankly, tricky to summarise in Lwood in less than several paragraphs by which point you might as well have read his email :)

Midcycle dates and locations

A few more midcycle announcements and one poll this past week

People and Projects

Further Reading & Miscellanea

Don’t forget these excellent sources of OpenStack news :)

This edition of Lwood brought to you by Jeff Beck (Guitar Shop, There and Back, Wired) Jordan Rudess (Rhythm of Time), Herbie Hancock (Cantaloupe Island) amongst other excellent tunes.

Comments

Lwood-20151122

November 23, 2015 at 23:48 · Filed under Lwood, OpenStack

Introduction

Welcome to Last week on OpenStack Dev (“Lwood”) for the week ending 15th November 2015. For more background on Lwood, please refer here.

Basic Stats for week 16th to 22nd November 2015 :

  • ~628 Messages (down about 8% relative to last week)
  • ~189 Threads (same as last week)

Traffic and threads steady…

Notable Discussions

Nova / Trusted Computing Pools related security notice (OSSN 0059)

Summary from the original security notice: “A trusted VM that has been launched earlier on a trusted host can still be powered on from the same host even after the trusted host is compromised.  More in the original post or the OSSN itself.

A reminder to projects about new “assert” tags

Over the last few months the TC defined a number of “assert” tags – a standardised way for projects to make certain assertions about their projects.  In his email Thierry Carrez reminds all concerned (basically PTLs and Project Cores) that the time is upon them to see if these tags should apply and if so to start using them.

In time this information will be added to that already displayed in the OpenStack Foundation’s Project Navigator hence the desire to get projects using these tags as soon as possible.  For operators and other non-developers, the use of these tags and endeavours like the Project Navigator promise to make the process of evaluating an OpenStack projects maturity a little simpler.

Vitrage – a Root Cause Analysis engine for OpenStack

Announced at the Mitaka Summit, a post to the list provided some more information on the Vitrage project – part of the broader Telemetry umbrella project for OpenStack,  The Vitrage developers would “like it to be the Openstack RCA (Root Cause Analysis) Engine for organizing, analyzing and expanding OpenStack alarms & events, yielding insights regarding the root cause of problems and deducing the existence of problems before they are directly detected.”

Noble goals and early days but a worthwhile and much needed set of functionality

What should the openstack-announce mailing list be ?

Tom Fifield kicked off a thread discussing what the best use of the mailing list is from herein.  Originally conceived as a low traffic read-only list he makes the point that with the addition of more (arguably) developer oriented content it’s become rather high traffic.  The concern being this appears to have put some folk off with them either filtering the list or unsubscribing – and so possibly missing the urgent content such as security notifications.

While there has been a little discussion since his first post on Friday input from a broad range of readers would be welcome.

Is booting a Linux VM important for certified OpenStack interoperability ?

On behalf of the DefCore Committee Egle Sigler asks for feedback on whether the ability to boot a Linux VM should be required for certified OpenStack interoperability.  A quick glance at the comments in the review cited suggests this is anything but a simple topic particularly once you consider containers and bare metal clouds in an environment…

Autoscaling both clusters and containers

Ryan Rossiter kicked off an interesting thread about autoscaling both containers and clusters. Essentially have the ability for a cluster to expand when the concentration of containers gets too high. Evidently there was some discussion about this in Tokyo with at least one demo being given using Senlin interfacing to Magnum to autoscale.

Developer Mailing List Digest

Originally a section within the OpenStack Community Newsletter, Mike Perez’ excellent openstack-dev digest is now available as a digest sent to the openstack-dev mailing list as well as being posted on the OpenStack Foundation’s blog.  I commend it to you if you’re after a deeper and/or more technical analysis than Lwood or other sources provide.  Here are the links to the Digest for November 7-13 and 14-20.

Discounted documentation changes

While the sprint in question is alas over at the time of writing, this post from Joshua Harlow about the Oslo projects virtual documentation sprint is too well written not to note :)

Midcycle dates and locations

A few more midcycle discussions this past week

  • [ironic] The Midcycle discussions from last week kicked off by Lucas Alvares seem to have settled on the idea of a virtual midcycle as proposed by Jim Rollenhagen
  • [manila] A survey for midcycle attendees/interested persons – Ben Swartzlander
  • [cinder] Mitaka Midcycle Sprint is on 26-29 January in North Carolina, USA – Sean McGinnis

Post Mitaka Summit Summaries and Priorities

A few more Summaries and Priority lists rolled in from the Mitaka Summit

People and Projects

Further Reading & Miscellanea

Don’t forget these excellent sources of OpenStack news :)

Closing on a lighter note – this edition of Lwood brought to you by Booker T Jones (Potato Hole & The Road From Memphis), Vinnie Moore (Aerial Visions), The String Contingent (Talk, TSC II), Steve Ray Vaughan (In Step), Tommy Emmanuel (Determination) amongst other excellent tunes.

 

Comments

Lwood-20151115

November 16, 2015 at 22:44 · Filed under Lwood, OpenStack

Introduction

Welcome to Last week on OpenStack Dev (“Lwood”) for the week ending 15th November 2015. For more background on Lwood, please refer here.

Basic Stats for week 9th to 15th November 2015 :

  • ~683 Messages (basically flat relative to last week)
  • ~189 Threads (down 7% from last week)

Traffic and threads settling after the Mitaka lull then rush of the last few weeks!

Notable Discussions

Making Stable Maintenance it’s own OpenStack project team

This quite lengthy thread starts on Monday here and neatly summarised in a post on Friday makes the case for making stable maintenance its own discreet OpenStack project team.

Reasons in favour include the ability for a suitably empowered team to tackle new coordination tasks (across projects) and reinforcing branding – making stable more visible to organisations that may in turn be more inclined to commit resources.

To me the upsides of this far outweigh the minor downsides – as OpenStack continues to mature so will the expectation around stable releases and longer term support.

New API guidelines for review

There are three new API guidelines ready for review that will be merged on November 20th in the absence of any further feedback.  They are;

Telemetry and Ceilometer explained

Gord Chung wrote a nice summary explaining the newly introduced [telemetry] tag and accompanying project and how it relates to Ceilometer.  In short telemetry is a project that encapsulates various smaller projects, including Ceilometer that provide monitoring, alarming, data collection and resource storage style services.

OSprofiler is dead, long live OSprofiler

A tongue in cheek subject for a significant thread from Boris Pavlovic in which he outlines his work to write a new OSprofiler.  For the uninitiated this tool allows quite fine grained analysis of where time is spent doing various OpenStack requests.  Boris provides a link to a demo trace of a CLI command (nova boot) as an example.

While he acknowledges there is some work to be done there already appears to be quite widespread support for seeing this work integrated across the Mitaka release.

Nominations open for N and O names of OpenStack

Monty Taylor wrote to advise that nominations for the N and O releases of OpenStack were open – they are alas now closed at the time of writing this edition.

Fear not, you can still vote when the names are put forward for Community voting on 30th November.  If you’re curious the geographc regions in questions are “Texas Hill County” for the “N” release and “Catalonia” for “O” – both lovely places :)

Shout out for Nova API documentation contributions

Understand a bit about Nova ?  Able to explain it to others ?  Please consider contributing to the very important work to refresh the Nova API documentation as Alex Xu writes here.  There is also a virtual Sprint planned.

Cool graphs!

What’s better than OpenStack ?  Graphs of OpenStack of course! :)

Jokes aside, Paul Belanger noted the existence of a new site http://grafana.openstack.org which will, as it develops, allow various dashboards to be created.  Suggestions for what the community would like to see are sought, for now there is an example dashboard of Zuul data.

High Availability topic for openstack-dev

Adam Spiers noted that there is now a formal topic tag [HA] for High Availability related posts to the mailing list.  If you’re posting on HA related topics please use this tag to assist server-side and client-side maili filters in doing their thing.

Last sync from oslo-incubator

A good news thread with a practical bent this one – Dims noting that most of the code in oslo-incubator has now moved into oslo.* libraries (as intended) followed up by a post from Thierry pointing out it was three years to the day that oslo-incubator was first created.  Props for all involved in getting Oslo to where it is today.

Not keeping Juno around longer after all

Following up on the thread mentioned in last week’s Lwood, Tony Breeds summed up a fairly full couple of weeks discussion in this message noting that “… Juno is no more long live Kilo!”

Introducing Lwood

A colleague suggested I should flag a post about Lwood from within Lwood to see if the resulting recursion would collapse the Internet.  Silliness aside, as Thierry suggested I’ve added the blog version of Lwood to Planet Openstack.

Other Reading

Don’t forget these excellent sources of OpenStack news :)

Post Mitaka Summit Summaries and Priorities

A few more Summaries and Priority lists rolled in from the Mitaka Summit

Midcycle dates and locations

A couple of midcycles (or lack thereof) were announced;

People and Projects

  • [tacker] Sripriya Seetharam nominated for Tacker core by Sridhar Ramaswamy
  • [oslo][taskflow] Greg Hill proposed for the taskflow-core team by Joshuah Harlow
  • [freezer] Proposal to add Pierre-Arthur Mathieu and Eldar Nugaev to freezer core by Marzi Fausto
  • [kolla] Proposing Michal Rostecki for Core Reviewer by Steve Dake
  • [vpnaas][neutron] Paul Michali advised he is stepping down from VPNaaS work to focus on other areas on Neutron

 

Comments

Lwood-20151108

November 9, 2015 at 22:27 · Filed under Lwood, OpenStack

Introduction

Welcome to Last week on OpenStack Dev (“Lwood”) for the week ending 8th November 2015. For more background on Lwood, please refer here.

The Mitaka Summit induced quiet spell last week was more than compensated for this week :)

Basic Stats for week 2nd to 8th November 2015 :

  • ~686 Messages (up about 155% from last week!)
  • ~204 Threads (up around 80% from last week)

Notable Discussions

Mitaka Release Schedule Published

Doug Hellman posted the Mitaka release schedule noting among other things there are only five weeks between Feature Freeze and Final Release instead of the usual six.

Exposing hypervisor/hardware details to users

Tony Breeds kicked off an interesting discussion about how best to expose hypervisor information to end users.  While seen by a few as a controversial idea there was far more assent than dissent and a way forward for something useable in ‘N’ and quite possibly Mitaka.

The most favoured approach seems to be to provide a capabilities API that abstracts the underlying information in hypervisor (or hardware) independent manner – a bit more heavy lifting to design and implement in the first instance, but a lot more future proof and allows a useful degree of hardware/hypervisor independence (the world isn’t all x86 after all…)

Changes to release process

Doug Hellman penned a few posts about changes to the release process for Mitaka.

The first dealt with communications – in summary the IRC channel for release related discussions has been renamed #openstack-release from it’s old name of #openstack-relmgr-office  Some behind the scenes tinkering should mean that anyone connecting to the old channel will be redirected.  The concept of “office hours” for the channel has now been removed – a recognition that most people have some form of scrollback or bot in use so that they can see messages posted while they weren’t logged in to the channel directly.

The second is more substantial – a move away from treating milestones as strict synchronisation points between projects, instead they are now intended to serve as reminders to the projects to have their own checkpoints.  Thus each project will be responsible for handling milestone tasks during the relevant weeks of the schedule, but at a big tent level there will no longer be an expectation to have all the tags and launchpad updates applied on the same day.

In a third email Doug outlines how similar changes are being made for stable releases and some in a fourth email, and finally in a fifth email some tools that might assist in keeping up.

Distributed lock managers at the Summit

Robert Collins posted a summary of conversations at the summit around adopting a common Distributed Lock Manager (DLM) While DLM is fairly deep developer level voodoo in most cases there are implications for operators as well as OpenStack moves in time to more unified solutions for this.

The plan put forward for now is to use an oslo abstraction layer named tooz – as Robert points out this doesn’t preclude using something else in special cases, but merely that they should be considered the exception not the norm.

It’s a longish thread that follows, but worth a read if DLM is on your radar and at the time of writing, still ongoing…

Oh and while you’re at it, take a moment to read this thread amusingly titled “[all][dlm] Zookeeper and openjdk, mythbusted” for a bit of comfort around the misconception that all of the above might mean you need to run a proprietary JVM…

Keep Juno alive for longer!

Tony Breeds kicked off a second thread worthy of a read – this one presenting a case for keeping the Juno release around for longer on the basis of its wide adoption and, as it would appear, a non-trivial number of customers that who are, for whatever reason, unable to contemplate a move to Kilo anytime soon.  

Post Mitaka Summit Summaries and Priorities

If you only have time to read one summary from the Summit, please consider making it this one by Doug Hellman as he neatly sets the stage for many themes that will be at the fore this cycle.

Beyond that, many projects and individuals posted summaries, recaps or priority lists following the Mitaka Summit and I have sought to link them all below, roughly in chronological order of their appearance on the list;

Midcycle dates and locations

A couple of midcycles (or lack thereof) were announced;

People and Projects

  • [rpm-packing] Alan Pevec and Jakub Ruzick were nominated for RPM packaging core by Haikel Guemar
  • [keystone] Steve Martinelli announced some changes to their cross project liaison personnel
  • [TripleO] Greg Haynes proposed Ian Weinand as core review on diskimage-builder
  • [ceilometer] Gord Chung proposed Rohit Jaiswal to be added to Ceilometer core
  • [networking-onos] Vikram Choudhary proposed Albert Dongfeng and Ramahjaneya Reddy Palleti as new cores for the networking-onos project
  • John Garbutt proposed adding Sylvain Bauza and Alex Xu to nova-core
  • [NFV][telco] Marc Koderer advised he would be stepping down from his TelcoWG core team membership
  • [neutron] After mooting such a move at the summit, Edgar Magana confirmed his decision to step down from Neutron core

Comments

Lwood-20151101

November 2, 2015 at 09:55 · Filed under Lwood, OpenStack

Introduction

Welcome to Last week on OpenStack Dev (“Lwood”) for the week ending 1st November 2015. For more background on Lwood, please refer here.

An even shorter Lwood this week than last – many people were at the Mitaka Summit in Tokyo which has reduced the amount of traffic dramatically.

Basic Stats for week 26th October to 1st November 2015 :

  • ~268 Messages (down about 36% from last week)
  • ~114 Threads (down about 49% from last week)

Notable Discussions

Midcycle dates and locations

There will likely be more of these announced/clarified during the coming week post Mitaka, but for now at least the Nova folk know where to be – Bristol, UK, 26 and 28 January. The announcement is here and a link to registration here.

Certificate Authority for openstack-ansible deployments

This thread, started by Major Hayden has been quietly percolating away and got, I think, some coverage at the summit too. It’s been suggested that the anchor project may have a role to play here as well.  Input is actively being sought from both the Ansible community but also from Openstack crypto folk.

People and Projects

  • Ian Cordasco wrote to say he would be stepping down from his involvement in Bandit, Glance, Ansible and Searchlight effective immediately.  A flurry of emails followed thanking Ian for his sustained and extensive contributions to OpenStack
  • Steve Dake announced that he will be stepping down from his role as a Magnum core reviewer.  He will continue to be involved with Kolla however.  A number of followup emails rightly thanked him for his work on the project
  • Denis Egorenko was proposed to Core for Puppet and with a quorum reached formally added
  • HenryG was added to the Neutron Drivers team

OpenStack-Cinder YouTube channel

Sean McGinnis announced the creation of a YouTube channel for Cinder – it will in time include tutorials and the like, for now will have Summit sessions posted.

Comments

Lwood-20151025

October 25, 2015 at 19:18 · Filed under Lwood, OpenStack

Introduction

Welcome to Last week on OpenStack Dev (“Lwood”) for 25th October 2015. For more background on Lwood, please refer here.

A bit of a shorter Lwood this week as the Mitaka Summit in Tokyo seems to have reduced the amount of Lwood-relevant traffic.

Basic Stats for week 19th to 25th October 2015 :

  • ~499 Messages (down about 19% from last week)
  • ~186 Threads (up about 2% from last week)

Notable Discussions

User Survey Results are out

Tom Fifield writes that the results of the most recent OpenStack user survey are now available here and it is, truly, compelling reading.  No matter what your involvement with OpenStack this is worthy of your time to go through and read.  Your humble correspondent will be taking a second pass at it right after I click send on this Lwood :)

New Stackalytics goodness

Ilya Shakhat notes that Stackalytics 0.9 is now up and running, a mixture of some neat new functionality as well as compatibility with upcoming infra changes (such as working with Gerrit 2.9+) Head over and check it out :)

Release Freeze until after Summit

Doug Hellman made note of the fact that barring anything unforeseen, there will be a freeze on new releases until after tne Summit – November 2nd.

OpenStack-HA IRC Channel

After some discussion with the -infra team, Adam Spiers points out there is now an IRC channel specifically for High Availability related discussions.

A new project – Watcher

Antoine Cabot announced the Watcher project on Wednesday last week – a project that seemingly makes use of data streamed from Ceilometer (and so isn’t, as I understand it querying the database) and allows this information to be used to trigger events with the aim of optimising resource usage.  Seems pretty neat and follows a presentation made at the Vancouver summit.

Release Notifications

A new section for Lwood, will see how useful/practical it proves to be – a wrapup of the weeks release/version bump notifications…

Comments

« Previous Page — « Previous entries « Previous Page · Next Page » Next entries » — Next Page »