OpenStack Weekly Community Newsletter (Nov. 28 – Dec. 4)

Individual Member Director nominations are now open

The deadline for Individual Member Director nominations is next Friday, December 11, 2015

How to manage medical and health data with OpenStack, a wearable sensor and smart apps

“Our hope is to inspire you to look into open source, to think of ways to solve the data problems that you might have already,” says Anne Gentle of Rackspace.

Why no data center should be full of islands

OpenStack connects developers with new tools while leveraging a common foundation, says Foundation COO Mark Collier.

Powering one billion page views and 170 million unique visitors per month with OpenStack

NTT Resonant operates goo, one of Japan’s leading web portals and Internet search engines

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].

Reports from Previous Events 

CFP and Election Deadlines

OpenStack Developer Mailing List Digest November 28 to December 4

Tips ‘n Tricks 

Upcoming Events 

Other News

OpenStack Developer Mailing List Digest November 28 to December 4

Success Bot Says

  • dims: cross-project, technical-debt-reduction effort pays dividends, no code left in oslo-incubator repo anymore.
  • dhellmann: horizn, searchlight, python-openstackclient, ironic-introspec, manila, barbican, aodh, and sahara tagged for mitaka-1 milestone!
  • odyssey4me: OpenStack-Ansible for Kilo and Liberty have been released.
  • ttx: Nova mitaka-1 (13.0.0.0b1) published!
  • flaper87: Glance m-1 is out
  • AJaegar: The Networking Guide has been translated into Japanese, read it [1].
  • stevemar: Got reno in all keystone projects.
  • Tell us yours via IRC with a message “#success [insert success]”.

Cross-Project Specs Close to Merging

  • Backwards compatibility for clients and libraries [2].
  • Deprecate Individual CLIs in favor of OpenStack Client [3].
  • Chronicles of Distributed Lock Manager [4].

Release Countdown For Week R-17, Dec 7-11

  • A list of all projects with tags [5].
  • There’s a known bug in Reno for release notes not appearing after merge [6].
  • Teams should have retrospectives to consider how the cycle is going so far.
  • Each project has a patch that removes the version field from setup.cfg file. Please review that as quickly as possible.
  • Mitaka 2 Release: Jan 19-21
  • Mitaka release schedule [7].

The Lock Files Saga (and Where We Can Go From Here)

  • Josh Harlow writes, different projects use file locks to ensure that no application on the same machine can manipulate a given resource.
  • Stale lock file bug happens [8] and there is no easy way to determine when a lock file can be deleted manually.
  • Proposed creative solutions [9][10].
  • Josh proposes having offset locks. Create a single file X size to store locks, instead of having a bunch of files representing locks.
    • Clint says this just makes the directory of lock files look clean, but still leaves each offset stale and has to cleaned anyway.
      • Idea: having a cron job which deletes lock files within a set reasonable time.
  • Ben Nemec feels this is largely cosmetic complaints about not cleaning up old files. The amount of trouble we’ve had with interprocess locking in the past, he has never felt that a cosmetic issue was sufficient reason to relook at the issue.
  • Clint feels what’s missing is metadata for cleaning up stale locks. That can be done with:
    • fcntl locks – You have the kernel telling you for sure if the locking process is still alive when you want to clean up and take the lock.
    • Creation locks – You need to write that information into the locks, and remove it, and then have a way to make sure the process is alive and know it has the lock, which isn’t simple.

Recording Milestones For Unmanaged Projects

  • Projects with non-release:managed tag should:
    • Prepare a patch to the deliverable file in openstack/releases repository recording the existing beta tag for your release. Include in the commit message that you are recording an existing milestone tag.
    • Prepare a patch to the project repository removing the version line from setup.cfg. This patch should depend on the release patch with the topic “remove-version-from-setup”.
    • Add a comment to the milestone tag request linking to the review from step 2.

Cross-Project Spec Liaisons

  • Mike Perez writes about problems we have with cross-project specs today:
    • Authors of specs can’t progress forward with specs because of lack of attention. Eventually getting frustrated and giving up.
    • Some projects could miss a cross-project spec being approved by the TC.
  • A proposal was given on the list and discussed at the cross-project meeting [11] to have cross-project spec liaisons from each project with the following responsibilities:
    • Watching the cross-project spec repo [12].
      • Comment on specs that involve your project. +1 to carry forward for TC approval.
        • If you’re not able to provide technical guidance on certain specs for your project, it’s up to you to get the right people involved.
        • Assuming you get someone else involved, it’s up to you to make sure they keep up with communication.
  • Communicate back to your project’s meeting on certain cross-project specs when necessary. This is also good for the previous bullet point of sourcing who would have technical knowledge for certain specs.
  • Attend the cross-project meeting when it’s called for [13].

Announcing a new cloud provider for OpenStack’s CI system: OVH

The OpenStack Project Infrastructure Team has added OpenStack Compute instances from OVH to the project’s continuous integration system.

There are a lot of ways to participate in an Open Source community like the OpenStack project and OVH is doing so in a way that best matches their strengths: contributing cloud resources to the project to drive our test and automation systems — resources which are critical to ongoing development.

OpenStack runs up to 30,000 automated jobs each day to test proposed changes and build documentation and software artifacts. The system responsible for this is itself a large multi-cloud application. It utilizes OpenStack Compute instances from Rackspace, HP Cloud, and now OVH to provide this service to developers. Each of those instances runs a single job and is then deleted in order to ensure the next job starts with a clean slate. This puts an extraordinarily high demand on our providers.

We are very excited by the addition of OVH, not only because it will help us scale to meet the needs of a growing project, but also because it demonstrates one of OpenStack’s key features: cross-cloud compatibility. When a developer uploads a proposed change to an OpenStack project, available instances from any of our contributing cloud providers will be used interchangeably to test it.

We are able to do this with the help of a number of OpenStack projects. First, we create a base image to use on all of our providers using Diskimage-builder. This ensures that all of our tests operate in an identical environment. Our test resource manager, Nodepool, uses the shade library to upload each of these images to our providers using the OpenStack Image service. Each of our providers is configured slightly differently, but shade handles the details so that Nodepool can focus on the business logic. Nodepool then identifies demand from our automation system, Zuul, to create OpenStack Compute instances as needed.

The Infrastructure Team thanks OVH for their contribution as well as our existing cloud providers, and we are excited about sharing our experience using this very demanding OpenStack application with all of them.

Technical Committee Highlights November 27, 2015

Welcome back from Tokyo. While there, I did not realize a three-dimensional subway map exists for Tokyo, but I sure loved traveling on the subway.

Welcoming the latest projects to OpenStack

Speaking of amazing cities and their subway maps, we should mention the growing list of OpenStack projects. We welcome these projects to OpenStack governance since the OpenStack Summit.

    • Monitoring – both OpenStack and its resources: monasca
    • Backups for file systems using OpenStack: freezer
    • Deployment for OpenStack: fuel
    • Cluster management service for Compute and Orchestration: senlin
    • Integrate Hyper-V, Windows and related components into OpenStack: winstackers

During these last weeks, the TC also had other project reviews requests that were put on hold for later once those projects and/or teams are more mature and ready to join the Big Tent.

Reports from TC Working Groups

Project Team Guide

The Project Team Guide team held a session back in Tokyo to discuss the next steps for this project. As a result of that session, more content will be created (or moved from the wiki): add community best practices, detail the benefits and trade-offs of the various release models, introduce deliverables and tags (as maintained in the governance repo’s projects.yaml), detail what common infrastructure projects can build on, and so on.

Communications Group

The communications working group (the one that brings these blog posts to you) will continue to operate under the same model. Announcements, summaries and communications will be sent out as they have been during the last cycle. Remember that feedback is always welcome and the group is looking for ways to improve. Talk back to us, we’re listening!

Project Tags

These are the latest new project tags created by the Technical Committee.

    • team:single-vendor: A new tag was added to communicate when a project team is currently driven by a single organization. We had some discussion about using the term “vendor” or “organization” but this intent is to show the opposite of a diversity in the team’s makeup.
    • assert:supports-upgrade: A new tag has been added to communicate when a project supports upgrades. Teams should apply this tag to their project if they assert they intend to support ongoing upgrades.
    • assert:supports-rolling-upgrade: A new tag has been added to communicate when a project supports rolling upgrades. Team should apply this tag to their project if they assert that operators can expect to perform rolling upgrades of their project, where the service can remain running while the upgrade is performed.

OpenStack Developer Mailing List Digest November 21-27

Success Bot Says

  • vkmc: We got 7 new interns for the Outreachy program December-March 2015 round.
  • bauzas: Reno in place for Nova release notes.
  • AJaeger: We now have Japanese Install Guides published for Liberty [1].
  • robcresswell: Horizon had a bug day! We made good progress on categorizing new bugs and removing old ones, with many members of the community stepping up to help.
  • AJaeger: The OpenStack Architecture Design Guide has been converted to RST [2].
  • AJaeger: The Virtual Machine Image guide has been converted to RST [3].
  • Ajaeger: Japanese Networking Guide is published as draft [4].
  • Tell us yours via IRC with a message “#success [insert success]”.

Release countdown for week R-18, Nov 30 – Dec 4

  • All projects following the cycle-with-milestones release model should be preparing for the milestone tag.
  • Release Actions:
    • All deliverables must have Reno configured before adding a Mitaka-1 milestone tag.
    • Use openstack/releases repository to manage the Mitaka-1 milestone tags.
    • One time change, we will be simplifying how we specify the versions for projects by moving to only using tags instead of the version entry for setup.cfg.
  • Stable release actions: Review stable/liberty branches for patches that have landed since the last release and determine if your deliverables need new tags.
  • Important dates:
    • Deadline for requesting a Mitaka-1 milestone tag: December 3rd
    • Mitaka-2: Jan 19-21
    • Mitaka release schedule [5]

Common OpenStack ‘Third-Party’ CI Solution – DONE!

  • Ramy Asselin who has been spearheading the work for a common third-party CI solution announces things being done!
    • This solution uses the same tools and scripts as the upstream Jenkins CI solution.
    • The documentation for setting up a 3rd party ci system on 2 VMs (1 private that runs the CI jobs, and 1 public that hosts the log files) is now available here [6] or [7].
    • There a number of companies today using this solution for their third party CI needs.

Process Change For Closing Bugs When Patches Merge

  • Today when a patch merges with ‘Closes-Bug’ in the commit message, that marks the associated bug as ‘Fix Committed’ to indicated fixed, but not in the release yet.
  • The release team uses automated tools to mark bugs from ‘Fix Committed’ to ‘Fix Released’, but they’re not reliable due to Launchpad issues.
  • Proposal for automated tools to improve reliability: Patches with ‘Closes-Bug’ in the commit message to have the bug status mark the associated bug as ‘Fix Released’ instead of ‘Fix Committed’.
  • Doug would like to have this be in effect next week.

Move From Active Distrusting Model to Trusting Model

  • Morgan Fainberg writes most projects have a distrusting policy that prevents the following scenario:
    • Employee from Company A writes code
    • Other Employee from Company A reviews code
    • Third Employee from Company A reviews and approves code.
  • Proposal for a trusting model:
    • Code reviews still need 2x Core Reviewers (no change)
    • Code can be developed by a member of the same company as both core reviewers (and approvers).
    • If the trust that is being given via this new policy is violated, the code can [if needed], be reverted (we are using git here) and the actors in question can lose core status (PTL discretion) and the policy can be changed back to the “distrustful” model described above.
  • Dolph Mathews provides scenarios where the “distrusting” model either did or would have helped:
    • Employee is reprimanded by management for not positively reviewing & approving a coworkers patch.
    • A team of employees is pressured to land a feature with as fast as possible. Minimal community involvement means a faster path to “merged,” right?
    • A large group of reviewers from the author’s organization repeatedly throwing *many* careless +1s at a single patch. (These happened to not be cores, but it’s a related organizational behavior taken to an extreme.)

Stable Team PTL Nominations Are Open

  • As discussed [8][9] of setting up a standalone stable maintenance team, we’ll be organizing PTL elections over the coming weeks.
  • Stable team’s mission:
    • Define and enforce the common stable branch policy
    • Educate and accompany projects as they use stable branches
    • Keep CI working on stable branches
    • Mentoring/growing the stable maintenance team
    • Create and improve stable tooling/automation
  • Anyone who successfully contributed to a stable branch back port over the last year can vote in the stable PTL election.
  • If interested, reply to thread with your self-nomination.
  • Deadline is 23:59 UTC Monday, November 30.
  • Election will be the week after.
  • Current candidates:
    • Matt Riedmann [10]
    • Erno Kuvaja [11]

Using Reno For Libraries

  • Libraries have two audiences for release notes:
    • Developers consuming the library.
    • Deployers pushing out new versions of the libraries.
  • To separate the notes from the two audiences and avoid doing manually something that we have been doing automatically, we can use Reno for just deployer release notes.
  • Library repositories that need Reno should have it configured like service projects, with separate jobs and a publishing location different from their developer documentation [12]

Releases VS Development Cycle

  • Thierry writes that as more projects enter the Big Tent, there have recently been questions about release models and development cycle.
  • Some projects want to be independent of the common release cycle and dates, but still keep some adherence to the development cycle. Examples:
    • Gnocchi wants to be completely independent of the common development cycle, but still maintain stable branches.
    • Fuel traditionally makes their releases a few months behind the OpenStack release to integration all the functionality there.
  • All projects above should current be release:independent, until they are able to (and willing) to coordinate their own releases with the projects following the common release cycle.
  • The release team currently supports 3 models:
    • release:cycle-with-milestones is the traditional Nova model with one release at the end of a 6-month dev cycle and a stable branch derived from that.
    • release:cycle-with-intermediary is the traditional Swift model, with releases as-needed during the 6-month development cycle, and a stable branch created from the last release in the cycle.
    • release:independent, for projects that don’t follow the release cycle at all.
      • Can make a release supporting the Mitaka release (including stable updates).
        • Can call the branch stable/mitaka even after the Mitaka release cycle, as long as the branch is stable and not development.
      • Should clearly document that their release is *compatible with* the OpenStack Mitaka release, rather than *part of* the Mitaka release.

OpenStack Developer Mailing List Digest November 14-20

Time to Make Some Assertions About Your Projects

  • The technical committee defined a number of “assert” tags which allows a project team to to make assertions about their own deliverables:
    • assert:follows-standard-deprecation
    • assert:supports-upgrade
    • assert:supports-rolling-upgrade
  • Read more on their definitions [1]
  • Update the project.yaml [2] of which tags apply to your project already.
  • The OpenStack foundation will use “assert”tags very soon in the project navigator [3].

Making Stable Maintenance Its Own OpenStack Project Team (Cont)

  • Continuing discussion from last week [4]…
  • Negatives:
    • Not enough work to warrant a designated “team”.
    • The change is unlikely to bring a meaning full improvement to the situation, sudden new resources.
  • Positives:
    • * An empowered team could tackle new coordination tasks, like engaging more directly in converging stable branch rules across teams, or producing tools.
    • Release management doesn’t overlap anymore with stable branch, so having them under that PTL is limiting and inefficient
    • Reinforcing the branding (by giving it its own team) may encourage more organizations to affect new resources to it
  • Matt Riedemann offers to lead the team.

Release Countdown For Week R-19, November 23-27

  • Mitaka-1 milestone scheduled for December 1-3.
  • Teams should be…
    • Wrapping up incomplete work left over from the end of the Liberty cycle .
    • Finalizing and announcing plans from the summit.
    • Completing specs and blueprints.
  • The openstack/release repository will be used to manage Mitaka 1 milestone tags.
  • Reno [5] will be used instead of Launchpad for tracking completed work. Make sure any release notes done for this cycle are committed to your master branchless before proposing the milestone tag.

New API Guidelines Read for Cross Project Review

  • The following will be merged soon:
    • Adding introduction to API micro version guideline [6].
    • Add description of pagination parameters [7].
    • A guideline for errors [8].
  • These will be brought up in the next cross project meeting [9].

OpenStack Weekly Community Newsletter (Nov. 14 – 20)

A primer on Magnum, OpenStack containers-as-a-service

Adrian Otto, project team lead, on how Magnum works and what problems it can solve for you.

OpenStack Mitaka release: what’s next for Ansible, Oslo and Designate

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

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].

Reports from Previous Events 

Deadlines and Contributors Notifications

Security Advisories and Notices 

  • None this week

Tips ‘n Tricks 

Upcoming Events 

OpenStack Weekly Community Newsletter (Nov., 7-13)

Kilowatts for Humanity harnesses the wind and sun to electrify rural communities

OpenStack-powered DreamCompute cloud computing helps keep rural microgrids up and running

OpenStack and Network Function Virtualization, the backstory

Jonathan Bryce, OpenStack executive director, gave a keynote at the OPNFV Summit where he talked about the two communities.

Fighting cloud vendor lock-in, manga style

To celebrate the OpenStack community and Liberty release, the Cloudbase Solutions team created a one-of-a-kind printed comic packed with OpenStack puns and references to manga and kaiju literature.

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].

Reports from Previous Events 

Deadlines and Contributors Notifications

Security Advisories and Notices 

  • None this week

Tips ‘n Tricks 

OpenStack Developer Mailing List Digest November 7-13

Upcoming Events 

OpenStack Developer Mailing List Digest November 7-13

New Management Tools and Processes for stable/liberty and Mitaka

  • For release management, we used a combination of launchpad milestone pages and our wiki to track changes in releases.
  • We used to pull releases notes for stable point releases at the time of releases.
  • Release managers would work with PTLs and release liaisons at each milestone to update launchpad to reflect the work completed.
  • All this requires a lot of work of the stable maintenance and release teams.
  • To address this work with the ever-growing set of project, the release team is introducing Reno for continuously building release notes as files in-tree.
    • The idea is small YAML files, usually one per note or patch to avoid merge conflicts on back ports, which are then compiled to a readable document for readers.
    • ReStructuredText and Sphinx are supported for converting note files to HTML for publication.
    • Documentation for using Reno is available [1].
  • Release liaisons should create and merge a few patches for each project between now and Mitaka-1 milestone:
    • To the master branch, instructions for publishing the notes. An example of Glance [2].
    • Instructions for publishing in stable/liberty of the project. An example with Glance [3].
    • Relevant jobs in project-config. An example with Glance [4].
    • Reno was not ready before the summit, so the wiki was used for release notes for the initial Liberty releases. Liaisons should covert those notes to Reno YAML files in stable/liberty branch.
  • Use the topic ‘add-reno’ for all patches to track adoption.
  • Once liaisons have done this work, launchpad can stop being used for tracking completed work.
  • Launchpad will still be used for tracking bug reports, for now.

Keeping Juno “alive” For Longer

  • Tony Breeds is seeking feedback on the idea of keeping Juno around a little longer.
  • According to the current user survey [5], Icehouse still has the biggest install base in production clouds. Juno is second, which means if we end of life (EOL) Juno this month, ~75% of production clouds will be running a EOL’d release.
  • The problems with doing this however:
    • CI capacity of running the necessary jobs of making sure stable branches still work.
    • Lack of resources of people who care to make sure the stable branch continues to work.
    • Juno is still tied with Python 2.6.
    • Security support is still needed.
    • Tempest is branchless, so it’s running stable compatible jobs.
  • This is acknowledged as a common request. The common answer being “push more resources in fixing existing stable branches and we might consider it”.
  • Matt Riedmann who works in the trenches of stable branches confirms stable/juno is already a goner due to requirements capping issues. You fix one issue to unwedge a project and with global-requirement syncs, we end breaking 2 other projects. The cycle never ends.
  • This same problem does not exist in stable/kilo, because we’ve done a better job of isolating versions in global-requirements with upper-constants.
  • Sean Dague wonders what are the reasons that keep people from doing upgrades to begin with. Tony is unable to give reasons since some are internal to his companies offering.

Oslo Libraries Dropping Python 2.6 compatibility

  • Davanum notes a patch to drop py26 oslo jobs [6].
  • Jeremy Stanley notes that the infrastructure team plans to remove CentOS 6.X job workers which includes all python 2.6 jobs when stable/juno reaches EOL.

Making Stable Maintenance its own OpenStack Project Team

  • Thierry writes that when the Release Cycle Management team was created, it just happen to contain release management, stable branch management, and vulnerability management.
    • Security Team was created and spun out of the release team today.
  • Proposal: spin out the stable branch maintenance as well.
    • Most of the stable team work used to be stable point release management, but as of stable/liberty this is now done by the release management team and triggered by the project-specific stable maintenance teams, so there is no more overlap in tooling used there.
    • Stable team is now focused on stable branch policies [7], not patches.
    • Doug Hellmann leads the release team and does not have the history Thierry had with stable branch policy.
    • Empowering the team to make its own decisions, visibility, recognition in hopes to encourage more resources being dedicated to it.
      • Defining and enforcing stable branch policy.
      • If team expands, it could own stable branch health/gate fixing. The team could then make decisions on support timeframes.
    • Matthew Treinis disagrees that the team separation solves the problem of getting more people to work on gate issues. Thierry has evidence though that making a its own project will result in additional resources. The other option is to kill stable branches, but as we’ve seen from the Keeping Juno Alive thread, there’s still interest in having them.

OpenStack Weekly Community Newsletter (Oct., 31 – Nov., 6)

Superuser TV

Introduced at the Tokyo Summit, Superuser TV offers community and industry insights, plus educational topics to support the OpenStack community. With content ranging from deployments to diversity, from emerging technologies to cloud strategy, Superuser TV is aiming to provide the community with access to a variety of perspectives and knowledge

October 2015 user survey highlights increasing maturity of OpenStack deployments

60 percent of deployments in production and high rates of adoption of OpenStack’s core services are key findings from the report released by the User Committee. The full report can be downloaded here: openstack.org/user-survey

Eliminating “Not-Invented-Here” Syndrome

Why embracing this notion is the key to unlock an open data center infrastructure, according to Boris Renski, the co-founder and CMO of Mirantis.

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].

Reports from Previous Events 

Deadlines and Contributors Notifications

Security Advisories and Notices 

  • None this week

Tips ‘n Tricks 

Upcoming Events 

What you need to know from the developer’s list

  • Success Bot Says

    • calebb: Shade now supports volume snapshots
    • pleia2: Launched code search [1].
    • sdague: grenade-multinode live upgrade tests now running on nova non voting
    • AJaeger: Contributors guide is published [2].
    • Tell us yours via IRC with a message “#success [insert success]”
  • Upgrading Elastic Search Cluster Monday

    • November 9th 1700UTC
    • Requires a cluster restart, in which people won’t be able to do searches during that time.
    • New features from upgrade:
      • Aggregations
      • Rolling upgrades within a major release
      • Should improve performance
  • Release Team Communication Changes

    • IRC channel change from #openstack-relmgr-office to #openstack-release
    • “Office hours” are being dropped.
      • Just drop by the channel or on the dev list with subject containing “[release]” anytime you need something.
  • Deprecation for Untagged Code

    • Ironic tries to keep master backwards compatible. There are deployers doing continuous deployments of Ironic off of master.
    • Based on the deprecation tag policy [3], it only covers released and tagged code, but not unreleased code or features introduced in an intermediate release.
    • A proposal [4] by Jim:
      • Three month deprecation period is needed for features that were never released.
      • A feature that was introduced in a intermediate release needs to be deprecated in the next intermediate release or coordinated release, and supported until the next release and 3 months.
  • Outcome of Distributed Lock Manager Discussion @ the Summit

    • There was a two part session at the summit [5]
    • Previously, there was an unwritten policy that DLMs should be optional, which led to writing poor DLM-like things backed by databases.
    • Continuing our existing pattern of usage like databases and message-queues, we’ll use an oslo abstraction layer: tooz [6].
    • Current OpenStack project requirements that surfaced in discussion for DLMs, it’s likely that Consul, Etcd and Zoo Keeper will be fine to use via Tooz. No project required a fair locking implementation in the DLM.
    • We want to avoid the situation of unmaintained drivers. We adopted a similar requirement from oslo.messaging driver requirements [7]:
      • Two developers responsible for it
      • Gating functional tests that use dsvm
      • Test drivers in-tree need to be clearly referenced as a test driver in the module name.
    • Davanum brings in Devstack ZooKeeper support [8].
    • An etcd driver is in review for Tooz [9].
    • A Consul driver in Tooz is also planned [10].
    • Concerns raised about the default DLM driver being ZooKeeper:
      • It’s a new platform for operators to understand
      • We don’t know how well ZooKeeper will work with openjvm as oppose to Oracle’s JVM.
  • Troubleshooting Cross-Project Communication

    • Evolve the current cross-project meeting to an “as needed” rotation, held at any time on Tuesdays or Wednesdays.
    • Based on feedback [11] it’s difficult to have meetings at different times on Tuesday and Wednesdays.
    • There was consensus that the meeting can be “as needed” on Tuesday, and that most announcements will happen in the mailing list, and sometimes show up in this weekly Dev List Summary.
  • API For Getting Only Status of Resources

    • Projects like Heat,Tempest, Rally, and other projects that work with resources are polling for updates on asynchronous operations.
    • Boris proposes having API’s expose the ability to just get the status by UUID, instead of fetching all data on a resource.
    • Clint suggests instead of optimizing for polling, we should revisit the proposal for a pub/sub model, so users can subscribe to updates for resources.
    • Sean suggests near term work around is to actually use Searchlight, which today monitors the notification bus for Nova.
      • Searchlight is hitting the Nova API more than ideal, but at least it’s one service.
      • Longer term we need a dedicated event service in OpenStack. Everyone wants web sockets, but anticipating 10,000+ open web sockets, this isn’t just a bit of python code, but a highly optimized server underneath.