SuccessBot Says

• dhellmann: [1] is live with release history and upcoming release schedules.
• ttx:  Governance changes are now announced in #openstack-dev, to increase general awareness about them!
• jklare: Just merged the first batch of opentack-chef cookbook patches for the Mitaka cycle! 4.229 lines of code refactored and 18.678 lines removed!
• johnthetubaguy: Nova subteams starting to look after themselves, and effectively reporting their progress to the wider community
• All: https://wiki.openstack.org/wiki/Successes

Dropping KEYSTONE_CATALOG_BACKEND – Plus Update Your Devstack Plugins

• Devstack has some half baked support for Keystone templated service catalog.
• In an effort to clean up parts of Devstack, we’re dropping that [2].
• This breaks everyone’s Devstack plugin that references the KEYSTONE_CATALOG_BACKEND variable.
• This variable will be kept around until Newton development opens up.
• Full thread: http://lists.openstack.org/pipermail/openstack-dev/2016-February/086272.html

All Hail the New Per-region PyPI, wheel and APT Mirrors

• We have new AFS-based consistent per-region mirrors of PyPI and API repositories, with additional wheel repositories containing pre-built wheels for all the modules in global-requirements.
• You should not notice a difference, except jobs should be a bit faster and more reliable.
• Full thread: http://lists.openstack.org/pipermail/openstack-dev/2016-February/086295.html

Release countdown for week R-7, Feb 15-19

• Focus: Project teams should be focusing on wrapping up new feature work in all libraries.
• Release Actions:
  • We will be strictly enforcing the library release freeze before Mitaka-3 in 2 weeks.
  • Review client libraries, integration libraries, and any other libraries managed by your team, and ensure recent changes have been released.
  • Ensure global-requirements and constraints lists are up to date, with accurate minimum versions, and exclusions.
  • Projects using cycle-with-intermediary release model need to produce intermediate releases. See Thierry’s emails for details [3].
  • Review stable/liberty branches and submit patches to openstack/releases if you want them.
• Important Dates
  • Final release for  non-client libraries: Feb 24
  • Final release for client libraries: Mar 2
  • Mitaka 3: Feb 29-Mar 4 (includes feature freeze and soft string freeze)
• Full thread: http://lists.openstack.org/pipermail/openstack-dev/2016-February/086362.html

Why WADL When You Can Swagger

• Continuing from previous update [4].
• Every build of the api-site is now running fairy-slipper to migrate from WADL to Swagger.
  • Those migrated Swagger files are copied to [5].
• Not all files migrate smoothly. We’d love to get teams looking at these migrated files. Thank you to those who have already submitted fixes!
  • If you see a problem in the original WADL when viewing [5], log it [7].
  • If you see a problem with the migration tool, log it [8].
• The Infra team is reviewing a specification [6] so that we can serve API information from developer.openstack.org.
• You can hop onto #openstack-doc or #openstack-sdks to ask nick annegentle
• Full thread: http://lists.openstack.org/pipermail/openstack-dev/2016-February/086467.html

Tenant VS. Project

• Sean Dague brings up that OpenStack’s use of tenant vs. project. Which are we transitioning to?
• Keystone is working towards allowing project_id in the service catalog [9].
• Neutron is transitioning to project_id now.
• The current Ansible OpenStack modules are using project [10].
• OSLO Logging/Context are using project.
• Full thread: http://lists.openstack.org/pipermail/openstack-dev/2016-February/086396.html

Proposal: Separate Design Summits From OpenStack Conferences

• The OpenStack design summits originally started out as working events.
• The OpenStack summits growing more marketing and sales focus, the contributors attending are often unfocused.
• Some contributors submit talks for the conference, because their company says it’s the only way for them to attend the conference. Part of the reason for this is the cost of attending.
• Thierry Carrez (who helps organize the design summit) explains that he has been working a solution for separation of the summit and the conference himself, and the Foundation is finalizing a strawman proposal that will be pushed to the community for comments soon.
• Full thread: http://lists.openstack.org/pipermail/openstack-dev/2016-February/086007.html

[1] – http://releases.openstack.org
[2] – https://review.openstack.org/#/c/278333
[3] – http://lists.openstack.org/pipermail/openstack-dev/2016-February/086152.html
[4] – http://www.openstack.org/blog/2016/01/openstack-developer-mailing-list-digest-january-9-15/
[5] – http://developer.openstack.org/draft/swagger
[6] – https://review.openstack.org/#/c/276484/
[7] – https://bugs.launchpad.net/openstack-api-site
[8] – https://bugs.launchpad.net/openstack-doc-tools
[9] – https://review.openstack.org/#/c/279576/
[10] – http://docs.ansible.com/ansible/list_of_cloud_modules.html#openstack

SuccessBot Says

• odyssey4me: OpenStack Ansible Liberty 12.0.5 released.
• stevemar: Devstack now defaults to v3 for Keystone.
• boris-42: osprofiler functional job passed [1].
• odyssey4me: OpenStack Ansible Kilo 11.2.9 released [2].
• odyssey4me: OpenStack Ansible Liberty 12.0.6 released [3].
• All: https://wiki.openstack.org/wiki/Successes

Cross-Project Specs

• A common policy scenario across all projects [4].
• Query config from web UI [5]

API Guidelines

• Must not return service-side tracebacks [6].

Service Type vs. Project Name For Use In Headers

• There’s a question of whether we should be using service type or project names in headers. Some reviews involving this [7][8][9][10].
• We should be selecting things that better serve the API consumers and according to Dean Troyer the API working group is going in the right direction.
• The service type as the primary identifier for endpoints and API services is well established, and is how the service catalog has and will always work. Service types therefore should be the way to go.
• Full thread: http://lists.openstack.org/pipermail/openstack-dev/2016-January/085145.html

OpenStack Ansible Without Containers

• Gyorgy annouces a new installer for OpenStack under GPLv3 using Ansible, but without containers.
  • Reasons for another installer since we already have the OpenStack Ansible project and Kolla:
    • Containers adding unnecessary complexity.
    • Packages: avoid mixing pip and distributor packages. Distributor packages includes things like init scripts, proper system users, upgrade possibilities, etc.
      • Kevin Carter mentions that these benefits are actually also included with the OpenStack Ansible project.
• Without containers, upgrading a single controller can be tricky and disruptive since you have to upgrade every service at the same time. Rollbacks are also easier.
• OpenStack Ansible project can already today do deployment without containers using the is_metal=true variable.
• Full thread: http://lists.openstack.org/pipermail/openstack-dev/2016-January/084963.html

Release Countdown for Week R-8, Feb 8-12

• Focus:
  • 2 more weeks before final releases for non-client libraries for this cycle.
  • 3 more weeks before the final releases for client libraries.
  • Projects should focus on wrapping up feature work in all libraries.
• Release Actions:
  • The release team will be strictly enforcing library release freeze before M3 in 3 weeks.
• Important Dates:
  • Final release for  non-client libraries: Feb 24
  • Final release for client libraries: Mar 2
  • Mitaka 3: Feb 29-Mar 4 (includes feature freeze and soft string freeze)
• Full thread: http://lists.openstack.org/pipermail/openstack-dev/2016-February/085705.html

“No Open Core” in 2016

• Before OpenStack had a name, the “four opens” principles were created to define how we operate as a community.
• In 2010 when OpenStack started, it was different from other open source cloud platforms (Eucalyptus) which followed open core strategy of producing a crippled community edition and an “enterprise version”.
• Today we have a non-profit independent foundation, which cannot do an “enterprise edition”.
  • Today member companies build “enterprise products” on top of the apache licensed upstream project. Some are drivers that expose functionality in proprietary components.
• What does it mean to “not do open core” in 2016? What is acceptable and what’s not?
• Thierry Carrez believes it’s time to refresh this of what is an acceptable official project in OpenStack.
  • It should have a fully-functional production grade open source implementation
  • If you need proprietary software of commercial entity to fully use the project, then it should not be accepted in OpenStack as an official project.
    • These projects can still be non-official projects and still be hosted by OpenStack infrastructure.
• Doug Hellmann brings up Poppy [11] which is applying to be an official OpenStack project.
  • A wrapper to content delivery networks, but there is no open source solution.
  • Is this something that can be an official project, or is open core?
• Full thread: http://lists.openstack.org/pipermail/openstack-dev/2016-February/085855.html

The Trouble with Names

• A few issues have crept up recently with the service catalog, API headers, API end points, and even similarly named resources in different resources (e.g. backup), that are all circling around a key problem. Distributed teams and naming collision.
• Each project has a unique name that is ensured by their git repository in the OpenStack namespace.
• There’s a desire to replace project names with generic names like nova/compute in:
  • service catalog
  • api headers
• Options we have are:
  • Use the code names we already have: nova, glance, swift, etc.
    • Upside: collision problem solved.
    • Downside: You need a secret decoder ring to know what a project does.
  • Have a registry of common names.
    • Upside: we can safely use common names everywhere and not fear collision down the road.
    • Downside: yet another contention point.
• Approvals by the various people in the community to have a registry of the common names. Maybe in the governance projects.yaml file [12]?
  • This list does include only the official projects by the technical committee, therefore only those projects can reserve the common names.
• OpenStack Client has already encoded some of these common names to projects [13].
• Full thread: http://lists.openstack.org/pipermail/openstack-dev/2016-February/085748.html

Announcing Ekko – Scalable Block-Based Backup for OpenStack

• The goal of Ekko is to provide incremental block-level backup and restore of Nova instances.
• Two place with overlapping goals:
  • Cinder volume without having the incremental backups be dependent.
  • Nova instances
    • OpenStack Freezer today leverages Nova’s snapshot feature.
    • Ekko would leverage live incremental block-level backup of a nova instance.
• Jay Pipes begins the discussion on the two projects (Freezer and Ekko) working together to make sure their REST API endpoints are not overlapping. Having two APIs for performing backups that are virtually identical is not good.
• The creator of Ekko sees the reason for another backup project because of “actual implementation and end results are wildly different” even if they are the same API call.
• Jay doesn’t like that today all the following endpoints exist:
  • Freezer’s /backups
  • Cinder’s /{tenant_id}/backups
• Having these endpoints make for bad user experience and is just confusing.
• The current governance model does not prevent competition of projects. So if two projects overlap in API endpoints, there should be an attempt in collaboration.
• Full thread: http://lists.openstack.org/pipermail/openstack-dev/2016-January/084739.html

Success Bot Says

• mriedem: nova liberty 12.0.1 released [1].
• OpenStack Ansible Kilo 11.2.7 has been released.
• OpenStack-Ansible Liberty 12.0.4 has been released.
• Tell us yours via IRC with a message “#success [insert success]”.
• All: https://wiki.openstack.org/wiki/Successes

Governance

• License requirement clarification for big tent projects [2].
• Make constraints opt in at the test level [3].
• OSprofiler is now an official OpenStack project [4].

Cross-Project

• TC approved:
  • Deprecate individual CLIs in favor of OpenStack client [5].
  • clouds.yaml support in clients [6].
• Current open specs: https://review.openstack.org/#/q/status:open+project:openstack/openstack-specs

Release Count Down For Week R-10, Jan 25-29

• Focus: with the second milestone behind us, project teams should be focusing on wrapping up new feature work and stabilizing recent additions.
• Release actions:
  • Strictly enforcing library release freeze before M3 (5 weeks).
  • Review client/integration libraries and whatever other libraries managed by your team.
  • Ensure global requirements and constraints lists are up to date with accurate minimum versions and exclusions.
  • Quite a few projects with unreleased changes on stable/liberty branch. Check for your project [7].
• Important dates:
  • Final release for non client libraries: February 24th
  • Final release for client libraries: March 2nd
  • Mitaka-3: Feb 29 through March 4 (includes feature freeze and soft string freeze).
  • Mitaka release schedule [8].
• Full thread: http://lists.openstack.org/pipermail/openstack-dev/2016-January/084678.html

Stabilization Cycles: Elaborating on the Idea To Move It Forward

• At the Tokyo summit, the OpenStack Development Theme session, in which people discuss overall focus in shared efforts, having cycles to stabilize projects was brought up.
• A project could decide to spend some percentage of time of the cycle on focusing on bug fixing, review backlog, refactoring, instead of entirely on new features.
• Projects are already empowered to do this, however, maybe the TC could work on formalizing this process so that teams have a reference when they want to.
• Some contributors from the summit feel they need the Technical Committee to take leadership on this, so that they can sell it back to their companies.
• Another side of discussion, healthy projects should naturally come up with bursts of feature additions and burst of repaying technical debt continuously.
  • Imposing specific periods of stabilization prevents reaching that ideal state.
• Full thread: http://lists.openstack.org/pipermail/openstack-dev/2016-January/084564.html

Success Bot Says

• stevemar: Latest python-neutronclient use keystoneauth, yay!
• devkulkarni: Devstack plugin for Solum finally working as expected.
• dulek: Initial tests show that our rolling upgrades stuff is working fine – I’m able to use Mitaka’s Cinder API service with Liberty’s cinder-scheduler and c-volume services.
• Tell us yours via IRC with a message “#success [insert success]”.

Cross-Project Specs & API Guidelines

• Add clouds.yaml support specification [1]
• Deprecate individual CLIs in favor of OSC [2]
• Add description of pagination parameters [3].

Release Models To Be Frozen Around Mitaka-2

• Deadline: Mitaka-2, January 21st
• Example, your release model is release:independent, and you want to switch to cycle-oriented models (e.g. release:cycle-with-intermediary or release:cycle-with-milestones). [4]
• To change your project, propose an openstack/governance change in reference/projects.yaml file [5].

Vision and Changes For OpenStack API Guides

• New tool: fairy-slipper [6]
  • Migrate files from WADL to Swagger.
  • Serve up reference info.
• New build jobs to build API guides from project repos to developer.openstack.org
• It was discussed in the last cross-project meeting [7] to answer questions.
• There are a variety of specs [8][9] to go over this work.
• See what’s happening this month [10].

“Upstream Development” Track At the Austin OpenStack Summit

• Call for speakers [11] at the OpenStack conference in Austin will have a new track targeted towards upstream OpenStack developers.
  • Learn about new development processes
  • Tools that the infrastructure team gives us
  • New OSLO library features (or elsewhere)
  • Best practices
• Probably Monday before the design summit tracks start.
• Have a topic that fits this audience? Submit it! [12]

You Almost Never Need to Change Every Repository

• There have been a lot of patches that tweak the same thing across many, many repositories.
• Standardizations are great, but if you’re making the same change to more than a few repositories, we should be looking at another way to have that change applied.
• If you find yourself making the same change over and over in a lot of projects, start a conversation on the dev mailing list first.

Release Countdown For Week R-11, Jan 18-22

• Focus:
  • Next week is the second milestone for the Mitaka cycle.
  • Major feature work should be making good process, or be re-evaluated to see it really needs to land this cycle.
• Release Actions:
  • Liaisons should submit tag requests to the openstack/releases repository for projects following the cycle-with-milestone before the end of the day on Jan 21.
  • Release liaison responsibility update should be reviewed [13].
• Important Dates:
  • Mitaka 2: January 19-21
  • Deadline for Mitaka 2 tag: Jan 21
  • Release models to be frozen: Jan 21

SuccessBot Says

• russellb: Ported OVS to Python 3.
• notmyname: Removed the beta tag on the swift erasure code docs.
• AJaeger: OpenStack configuration reference has been migrated from DocBook XML to RST [1].
• notmyname: This season’s Outreachy intern had her first patch merged.
• odyssey4me: OpenStack-Ansible 12.0.3 tagged.
• jordanP: My 3rd party CI correctly warned me that a patch would break my driver.
• asselin: OpenStack Third Party CI documentation published [2].

Slightly Longer Delays for Gate CI Testing

• When: January 31, 2016
• Why:
  • Due to the sunsetting of a public cloud [3] used by the OpenStack Infra team, we will have less resources available.
  • Jeremy Stanley says that the Infra team is working on bringing in new providers to absorb the impact.

Release Countdown For Week R-12, Jan 11-25

• Focus:
  • Second milestone is coming up. Finish up major features or reevaluate if it really needs to land in this cycle.
• Actions:
  • Identify work that needs to be completed before the M-2 tag.
  • Release liaisons responsibilities are being updated. Provide comments for questions or concerns [4].
• Important Dates:
  • Mitaka 2: Jan 19-21
  • Release schedule [5].

Re-introduce Twisted to global-requirements

• A change in global-requirements introduces mimic, an http server that can mock various APIs.
• Mimic depends on twisted, which in the past was removed in favor of Eventlet to avoid developers having to know multiple frameworks [5].
• Jim Rollenhagen explains Ironic’s need for Mimic:
  • To do functional tests, not unit tests which they could do with requests-mock.
  • To bring up a less expensive Ironic environment for doing these tests.
• Jay Pipes notes:
  • This is another way to introduce a larger surface area of bugs to creep in since you have keep Mimic up-to-date with the real interfaces.
  • There’s not a clear value in the advantage  of functional tests of a client that calls a fake HTTP API versus unit tests of a client that simply uses requests-mock.

Running an OpenStack cloud? Come to the first European Mid-Cycle Operators meetup

The meetup, held February 15 – 16, 2016 in Manchester, is a chance for operators to share best practices and give feedback.

The keys to OpenStack startup success: Platform9 Systems

Platform9 Systems opens its startup playbook, highlighting ecosystem challenges and tips for fellow startups including how they differentiate their product from competitors with simplicity, choice and interoperability.

OpenStack operators connecting together

To make meetups more productive and useful, Edgar Magana at Workday proposes smaller, operator-focused gatherings.

The Road to Austin

• The Call for Speakers is now OPEN for the April OpenStack Summit in Austin! Hurry – the deadline to submit a talk is February 1 at 11:59pm PST. 
  • NEW: Speakers are limited to a maximum of THREE submissions. 
• Other Summit items now available:
  • Attendee Registration – Price increase in early March
  • Call for Sponsors – March 8 deadline
  • Hotel Discount Room Blocks
    *The Design Summit will be held at the Hilton Austin. Workshops and the Certified OpenStack Administrator exams will be held at the JW Marriott.
  • Visa Invitation Request
  • Travel Support Program Application – February 9 deadline

Community feedback

OpenStack is always interested in feedback and community contributions, if you would like to see a new section in the OpenStack Weekly Community Newsletter or have ideas on how to present content please get in touch: [email protected].

CFP Deadlines

• Call for papers:
  • PyCon 2016 deadline: Jan 3, 2016
  • USENIX Annual Technical Conference 2016 deadline: February 1, 2016

OpenStack Developer Mailing List Digest December 12-18

Tips ‘n Tricks 

• By Alena Holanova: Swift deployment with OpenStack Keystone authentication
• By Nicole Martinelli: How to take your OpenStack contributions to the next level
• By Lana Brindley, Brian Moss, Darren Chan, Joseph Robinson: Getting started with OpenStack Documentation

Upcoming Events 

• Dec 26, 2015 OSS OpenStack Upstream Training VN Ha Noi, VN
• Dec 27, 2015 Riding a Baby Unicorn | MIT Forum Event (No RSVP) Tel Aviv-Yafo, IL
• Dec 31, 2015 Project Kuryr – Bringing Container Networking to Neutron Tel Aviv, IL

Other News

• China’s First OpenStack-based Cloud Provider UnitedStack Announced the Completion of Series C Round of Financing
• Mirantis and Palo Alto Networks Integrate Production-Grade OpenStack with Next-Generation
  
• Bright Computing Provides Van Andel Institute with Integrated Management Solution for HPC and OpenStack

Success Bot Says

• jroll: Ironic is using the devstack plugin.
• Tell us yours via IRC with a message “#success [insert success]”.

Cross-Project Specs

• Approved by the Technical Committee:
  • Chronicles Of A DLM [1].
    • OpenStack will adopt Tooz as an abstract layer to distributed lock managements solutions. This will allow projects to provide all the options Tooz provides for their distributed lock management needs.
    • Reference implementation is currently ZooKeeper for testing.
• Close to approval:
  • Backwards compatibility for libraries and clients [2].
  • Deprecate individual CLIs in favor of OSC [3].

New Things In Gerrit 2.11 To Enjoy

• New search strings:
  • Patch size
    • delta:<=10
    • show patches with <= 10 lines of change
  • Scoring by group
    • label:Code-Review<=-1,nova-core
    • filter by -1 from nova-core team
  • message:/comment:
    • Queries work with more than one word
• UI Features:
  • is:amergable field
  • Column 3
    • Related changes: all changes in linear patch series.
    • Conflicts with: all open patches in the system that will conflict with this one.
    • Same topic: Grouping reviews.
  • Inline edit an entire patch.
    • Click the ‘edit’ button above the list of files. Once you’re done click ‘save’ and eventually ‘Publish Edit’ on the main page.
    • “Follow up” button: builds an entire follow up patch that you can inline edit to fix something like typos.

Stable Meeting Time Proposal

• Matt Riedmann the stable PTL proposes two meeting dates [4]:
  • Every two weeks (on odd weeks) on Monday at 2100 UTC in #openstack-meeting-4
  • Every two weeks (on even weeks) on Tuesday at 1500 UTC in #openstack-meeting-3
• Thierry has proposed it start January 5th 2016

DocImpact vs. Reno

• Sean notes a new job on all Nova changes that is processing commit messages [5].
• UpgradeImpact got dropped for having an upgrade comment in Reno.
• Instead of DocImpact, SecurityImpact in commit messages, new special sections using Reno will be created that trigger creating bugs and sending out emails like today. The hope is for better quality in these notifications.

Nominations open for the N and O names of OpenStack

• For the N release, where the geographic region is “Texas Hill Country” [6]
• For the O release, where the geographic region is “Catalonia” [7]
• OpenStack foundation individual members should have received a vote link via email. [8]
• Polls end of Dec 22nd UTC.

Travel grants bring global community members to OpenStack Summit

Key contributors from 15 countries attended the recent OpenStack Summit in Tokyo. The program for Austin is growing – find out more about the Travel Support Program.

OpenStack Mitaka release: what’s next for Neutron, Cinder and Ceilometer

Meet the project team leads (PTLs) and find out how to get involved.

Check out this tool library for OpenStack operators

These tools – contributed by and for operators – offer quick solutions to streamline your work

OpenStack design contest T-shirts are now available!

Joline Buscemi won the third edition of the community T-shirt design contest, held annually by the OpenStack Foundation.

Community feedback

OpenStack is always interested in feedback and community contributions, if you would like to see a new section in the OpenStack Weekly Community Newsletter or have ideas on how to present content please get in touch: [email protected].

CFP Deadlines

• Call for papers:
  • PyCon 2016 deadline: Jan 3, 2016
  • USENIX Annual Technical Conference 2016 deadline: February 1, 2016

OpenStack Developer Mailing List Digest December 5-11

Tips ‘n Tricks 

• By Alain Swanson: Provisioning Neutron networks with the NSX-v Plugin

Upcoming Events 

• Dec 12, 2015 meet: Big data and OpenStack sousse, Sousse, TN
• Dec 12, 2015 开源文化与OpenStack Beijing, CN
• Dec 14 – 18, 2015 Okinawa Open Days 2015 Naha, Okinawa, JP
• Dec 15, 2015 Software Defined Storage – What makes Ceph special Guadalajara, MX
• Dec 16, 2015 Openstack Seattle Meetup: A Deep Dive of the OpenStack Security Project
• Dec 16, 2015 OpenStack End of the Year Beer Ljubljana, SI
• Dec 17 – 18, 2015 Ops meetup in Asia Okinawa, JP
• Dec 18, 2015 SFBay OpenStack Hackathon #OSSFO

Other News

• How PayPal Runs the World’s Largest Private OpenStack Cloud
• Thinking outside the box and outside the gate to improve OpenStack and RDO
• Australian company, Aptira, expands global footprint
• Bright Computing Receives Honors in 2015 HPCwire Readers’ and Editors’ Choice Awards