OpenStack Mitaka Design Summit

We have some common cross project concerns that fall by the wayside when we don't pull the whole community together to focus attention on them. Things like functional testing, upgrades, interaction with DefCore, recruiting more core reviewers, and application of the logging guidelines. Let's sit down together and pick one or two "themes" for this cycle for all projects to be considering as background for their project-specific goals.

Moderator: Doug Hellmann
Etherpad: https://etherpad.openstack.org/p/mitaka-crossproject-themes

At the ops midcycle dhellmann talked with Chris Hoge about some of the issues the DefCore team is encountering with establishing the correct versions of APIs, with changes to APIs, and with the tests for our APIs. This led to the mailing list discussion about the Glance project priorities for Mitaka. A design summit session would be a chance to identify problem areas and work on solutions to ensure that all projects fully understand how they can and should be making changes while maintaining compatibility testing.

We should also work on improving communication between the contributor community and the DefCore committee. dhellmann also spoke with zehicle, and he's planning to be present at the session to help with that so when DefCore identifies potential issues, they can feed back into the project teams and vice versa.

Moderator: Doug Hellmann
Etherpad: https://etherpad.openstack.org/p/mitaka-crossproject-defcore

Recently the TC approved a "follows standard deprecation" tag which tried to reasonably capture what projects were doing. That coincided with the removal of v1 cinder API from devstack, which didn't really go so well, and had to be reverted.

This session will be a bit of a post mortem on what went wrong there, and how we do this less wrong in the future. The expected output is a plan for how cinder (and other projects) can reasonably remove their very old APIs, what's expected there, and what additional guidance we should provide in our standard-deprecation tag.

Also we will be talking about libraries and clients and their deprecation story.

Moderator: Sean Dague
Etherpad: https://etherpad.openstack.org/p/mitaka-cross-project-standard-deprecation-policy

We need to all get together and figure out and understand what the issues with DLM are, what lock management features have been replicated by many various projects and what something like zab (zookeeper), raft (consul, etc.d, ...), paxos (?), or other variant can offer to openstack and its diverse set of projects.

Connected to: https://review.openstack.org/#/c/209661/

Related to:

- https://etherpad.openstack.org/p/servicegroup-refactoring
- http://lists.openstack.org/pipermail/openstack-dev/2015-September/075267.html
- http://lists.openstack.org/pipermail/openstack-dev/2015-July/070683.html
- (and many others)

Why: without understanding the problem, and what the solutions are, what the various offerings provide... we have no hope in fixing it, so let's work on that.

Expected result: understanding what a DLM is, what some of the common patterns they offer are, and in my happy world/vision agreeing that a DLM solution (ideally one, not many) will help openstack(s) future (in terms of long-term health, operability, features, and so-on); reduce common code that is replicated similar features and possibly bring world peace.

Moderator: Mike Perez
Etherpad: https://etherpad.openstack.org/p/mitaka-cross-project-dlm

http://mitakadesignsummit.sched.org/event/85609778fc07e1000b3284ca21b14688 (continued)

We need to all get together and figure out and understand what the issues with DLM are, what lock management features have been replicated by many various projects and what something like zab (zookeeper), raft (consul, etc.d, ...), paxos (?), or other variant can offer to openstack and its diverse set of projects.

Connected to: https://review.openstack.org/#/c/209661/

Related to:

- https://etherpad.openstack.org/p/servicegroup-refactoring
- http://lists.openstack.org/pipermail/openstack-dev/2015-September/075267.html
- http://lists.openstack.org/pipermail/openstack-dev/2015-July/070683.html
- (and many others)

Why: without understanding the problem, and what the solutions are, what the various offerings provide... we have no hope in fixing it, so let's work on that.

Expected result: understanding what a DLM is, what some of the common patterns they offer are, and in my happy world/vision agreeing that a DLM solution (ideally one, not many) will help openstack(s) future (in terms of long-term health, operability, features, and so-on); reduce common code that is replicated similar features and possibly bring world peace.

Moderator: Mike Perez
Etherpad: https://etherpad.openstack.org/p/mitaka-cross-project-dlm

The process around cross-project specs is lengthy and painful. The cross-project meeting doesn't work that well. We should brainstorm how to improve those for the Mitaka cycle.

Moderators: Thierry Carrez / Mike Perez
Etherpad: https://etherpad.openstack.org/p/mitaka-crossproject-comms

The keystone has been implementing federation support for a few releases now. We are at the stage where other projects, such as: horizon, chef, puppet, ansible, and the CLIs have begun to support it as well. Furthermore, the topic of using services from different clouds (mix and match federation) have begun to arise, in this scenario a user could create a VM from one cloud, while getting images and volumes from a service provider cloud. 


Moderator: Steve Martinelli
Etherpad: https://etherpad.openstack.org/p/mitaka-cross-project-keystone-federation-next-step

At the close of Liberty, we had a number of items which slipped into the Mitaka release.
We'll use this session to go over those items and decide which ones should be fast-tracked
back into the Mitaka release. We'll also try to evaluate if any are no longer relevant or require
significant re-thinking to align with the current plan of record.

This is part of the Neutron 'Core' track series.

Who is this session for:

This is a track of Neutron sessions for OpenStack/Neutron developers. If you are not a developer
you'll find these sessions incredibly boring or hard to decipher. Having said that, if you are a
relatively new contributor and intend to be more involved with the community, you are more than
welcome to attend so that we can grow the Neutron developer team. Save the usability issues
and long term picture project discussions for the other two tracks below.

Relevant tracks:
'Next' track
'Labs' track

Core track theme:
Topics are 'boring' day-to-day activities that need to happen for moving the project forward,
and do not have a direct impact to users or operators. Processes, testing, integration with other
projects are typically what we talk about. Topics are non-controversial stuff that must happen
one way or another, the objective of the session is to go home with an idea of how big a task
is, and who does what. Typically these activities are a single-person effort. They span all the
neutron core projects: neutron, and neutron-*-aas.

etherpad

Chair: mestery

A year ago we embarked upon a journey to evolve the project and how we test it:
we got tests closer to the codebase, we split the project in sub-projects, and we
extended our ability to test according to different strategies (functional vs api vs fullstack).
At the same time we delegated more and more to 3rd party testing to ensure
quality of sub-projects. The road is far from over: in this session we'll talk about
what is ahead of us and how we are going to finish what we started.

This is part of the Neutron 'Core' track series.

Who is this session for:

This is a track of Neutron sessions for OpenStack/Neutron developers. If you are not a developer
you'll find these sessions incredibly boring or hard to decipher. Having said that, if you are a
relatively new contributor and intend to be more involved with the community, you are more than
welcome to attend so that we can grow the Neutron developer team. Save the usability issues
and long term picture project discussions for the other two tracks below.

Relevant tracks:
'Next' track
'Labs' track

Core track theme:
Topics are 'boring' day-to-day activities that need to happen for moving the project forward,
and do not have a direct impact to users or operators. Processes, testing, integration with other
projects are typically what we talk about. Topics are non-controversial stuff that must happen
one way or another, the objective of the session is to go home with an idea of how big a task
is, and who does what. Typically these activities are a single-person effort. They span all the
neutron core projects: neutron, and neutron-*-aas.

etherpad

Chair: amuller

Moderator: John Griffith
Every company these days wants to provide a SDS with plugins, sure sounds a lot like Cinder! The complaint is that Cinder doesn't offer enough and doesn't work outside of OpenStack, maybe we can/should change that?

Moderators: Michal Dulko, Duncan Thomas
Change of behavior in Nova (started passing AZ when creating a volume) uncovered misunderstaning in the community about how Cinder should treat AZs. We should ask operators how they see AZs and how we can improve them in Cinder to make their life easier.

More info: https://review.openstack.org/#/c/220971/

This session is aimed at discussing issues that cross outside any neutron project.
It can involve interactions with other projects, or coordination that needs to happen
between the Neutron stadium teams.

This is part of the Neutron 'Core' track series.

Who is this session for:

This is a track of Neutron sessions for OpenStack/Neutron developers. If you are not a developer
you'll find these sessions incredibly boring or hard to decipher. Having said that, if you are a
relatively new contributor and intend to be more involved with the community, you are more than
welcome to attend so that we can grow the Neutron developer team. Save the usability issues
and long term picture project discussions for the other two tracks below.

Relevant tracks:
'Next' track
'Labs' track

Core track theme:
Topics are 'boring' day-to-day activities that need to happen for moving the project forward,
and do not have a direct impact to users or operators. Processes, testing, integration with other
projects are typically what we talk about. Topics are non-controversial stuff that must happen
one way or another, the objective of the session is to go home with an idea of how big a task
is, and who does what. Typically these activities are a single-person effort. They span all the
neutron core projects: neutron, and neutron-*-aas.

etherpad

Chair: dougwig

We have "decomposed" non-reference code out of the neutron tree. Are we providing
external projects with the support they need to integrate with Neutron? What are the pain
points? Can we agree on a prioritized list of improvements to aid pluggability? What is
the roadmap for neutron-lib and API micro-versioning? These are some of the topics
we will discuss in this session.

This is part of the Neutron 'Core' track series.

Who is this session for:

This is a track of Neutron sessions for OpenStack/Neutron developers. If you are not a developer
you'll find these sessions incredibly boring or hard to decipher. Having said that, if you are a
relatively new contributor and intend to be more involved with the community, you are more than
welcome to attend so that we can grow the Neutron developer team. Save the usability issues
and long term picture project discussions for the other two tracks below.

Relevant tracks:
'Next' track
'Labs' track

Core track theme:
Topics are 'boring' day-to-day activities that need to happen for moving the project forward,
and do not have a direct impact to users or operators. Processes, testing, integration with other
projects are typically what we talk about. Topics are non-controversial stuff that must happen
one way or another, the objective of the session is to go home with an idea of how big a task
is, and who does what. Typically these activities are a single-person effort. They span all the
neutron core projects: neutron, and neutron-*-aas.

etherpad

Chair: HenryG

The session is expected to raise awareness about existing server-to-agent
extension mechanisms, their deficiencies, and to come up with a plan on
where we can make the most reasonable progress during the next two cycles.
Additionally, we would like to define the scope of work for the modular L2 agent
discussions that frequently come up since there are many interpretations about
what level of abstraction that implies for agent extensions.

This is part of the Neutron 'Core' track series.

Who is this session for:

This is a track of Neutron sessions for OpenStack/Neutron developers. If you are not a developer
you'll find these sessions incredibly boring or hard to decipher. Having said that, if you are a
relatively new contributor and intend to be more involved with the community, you are more than
welcome to attend so that we can grow the Neutron developer team. Save the usability issues
and long term picture project discussions for the other two tracks below.

Relevant tracks:
'Next' track
'Labs' track

Core track theme:
Topics are 'boring' day-to-day activities that need to happen for moving the project forward,
and do not have a direct impact to users or operators. Processes, testing, integration with other
projects are typically what we talk about. Topics are non-controversial stuff that must happen
one way or another, the objective of the session is to go home with an idea of how big a task
is, and who does what. Typically these activities are a single-person effort. They span all the
neutron core projects: neutron, and neutron-*-aas.

etherpad

Chair: kevinbenton/iharchys

Moderators: Patrick East, Scott D'Angelo
Do we need them? Do we want them? How should we implement them?

https://etherpad.openstack.org/p/cinder-experimental-api-info
Draft spec for microversions - https://review.openstack.org/#/c/223803/ and code - https://review.openstack.org/#/c/224910/ )

Discussion around any integration issues. Start identifying and shortcomings or other things we need to work on to make things better.

https://etherpad.openstack.org/p/NovaCinderMitakaSession

Some topics to be covered include:
* Multi-attach
* OS-Brick
* Cinder-Nova API changes
* Extending attached volumes
* Bugs

This is one session of two (back-to-back) sessions that start on Thursday 11am.
The first one is about Load Balancing: we will discuss the road map for Octavia
and LBaaS in M – in particular how Active-Active load balancing can be achieved
with Octavia and how Octavia can leverage containers for load balancing functions.

The second one is about firewall: we will discuss the road map for FWaaS in M and
how the service can be rebooted and work better together with Security Groups.
Additional topics include logging and East-West firewall in DVR scenarios.

This is part of the Neutron 'Next' track series.

Who is this session for:

This is a Neutron session for OpenStack/Neutron users, if you are not running/using
OpenStack Neutron on a daily basis, you'll find these sessions interesting, but nothing
deciced here has an impact on you. However, if you have just started getting your hands
dirty, a fresh perspective like yours is welcome to the discussion. Save the long-term
aspects for the track below.

Relevant tracks:
'Labs' track

Next track theme:
Topics are well-known pain-points, or short-term areas of improvement that must be addressed
in the next cycle to improve usability and make users/operators are happier. New tangential features
or minor incremental improvement to existing features that require some design discussion or
more elaborated scoping are typically things we talk about during these sessions.
The objective of the session is to go home with an idea of the working group that is going to
drive the feature to completion and an idea of which direction they want to go down to.
Typically these activities are more elaborated effort that require more than a couple of folks
to get it to a meaningful momentum.

etherpad

Chair: dougwig/sc68cal/xgerman

This is one session of two (back-to-back) sessions that start on Thursday 11am.
The first one is about Load Balancing: we will discuss the road map for Octavia
and LBaaS in M – in particular how Active-Active load balancing can be achieved
with Octavia and how Octavia can leverage containers for load balancing functions.

The second one is about firewall: we will discuss the road map for FWaaS in M and
how the service can be rebooted and work better together with Security Groups.
Additional topics include logging and East-West firewall in DVR scenarios.

This is part of the Neutron 'Next' track series.

Who is this session for:

This is a Neutron session for OpenStack/Neutron users, if you are not running/using
OpenStack Neutron on a daily basis, you'll find these sessions interesting, but nothing
deciced here has an impact on you. However, if you have just started getting your hands
dirty, a fresh perspective like yours is welcome to the discussion. Save the long-term
aspects for the track below.

Relevant tracks:
'Labs' track

Next track theme:
Topics are well-known pain-points, or short-term areas of improvement that must be addressed
in the next cycle to improve usability and make users/operators are happier. New tangential features
or minor incremental improvement to existing features that require some design discussion or
more elaborated scoping are typically things we talk about during these sessions.
The objective of the session is to go home with an idea of the working group that is going to
drive the feature to completion and an idea of which direction they want to go down to.
Typically these activities are more elaborated effort that require more than a couple of folks
to get it to a meaningful momentum.

etherpad

Chair: dougwig/sc68cal/xgerman

In this session we will identify pain points in the Neutron Liberty release.
Focus on short-term areas of improvement that must be addressed in the
next cycle to improve usability and make users/operators are happier.
The objective of the session is to go home with an idea of the working group
that is going to drive the feature to completion and an idea of which direction
in which they want to proceed. Some larger topics may come up and be noted
on the etherpad but discussion for those should probably start on the mailing list,
a Neutron team meeting, or some other venue.

This is part of the Neutron 'Next' track series.

Who is this session for:

This is a Neutron session for OpenStack/Neutron users, if you are not running/using
OpenStack Neutron on a daily basis, you'll find these sessions interesting, but nothing
deciced here has an impact on you. However, if you have just started getting your hands
dirty, a fresh perspective like yours is welcome to the discussion. Save the long-term
aspects for the track below.

Relevant tracks:
'Labs' track

Next track theme:
Topics are well-known pain-points, or short-term areas of improvement that must be addressed
in the next cycle to improve usability and make users/operators are happier. New tangential features
or minor incremental improvement to existing features that require some design discussion or
more elaborated scoping are typically things we talk about during these sessions.
The objective of the session is to go home with an idea of the working group that is going to
drive the feature to completion and an idea of which direction they want to go down to.
Typically these activities are more elaborated effort that require more than a couple of folks
to get it to a meaningful momentum.

etherpad

Chair: carl_baldwin

In this session, we will discuss modeling changes and protocol support mainly
around Neutron L3. Topics include new L3 models, floating IP's, BGP dynamic
routing, and IPv6.

This is part of the Neutron 'Next' track series.

Who is this session for:

This is a Neutron session for OpenStack/Neutron users, if you are not running/using
OpenStack Neutron on a daily basis, you'll find these sessions interesting, but nothing
deciced here has an impact on you. However, if you have just started getting your hands
dirty, a fresh perspective like yours is welcome to the discussion. Save the long-term
aspects for the track below.

Relevant tracks:
'Labs' track

Next track theme:
Topics are well-known pain-points, or short-term areas of improvement that must be addressed
in the next cycle to improve usability and make users/operators are happier. New tangential features
or minor incremental improvement to existing features that require some design discussion or
more elaborated scoping are typically things we talk about during these sessions.
The objective of the session is to go home with an idea of the working group that is going to
drive the feature to completion and an idea of which direction they want to go down to.
Typically these activities are more elaborated effort that require more than a couple of folks
to get it to a meaningful momentum.

etherpad

Chair: carl_baldwin/tidwellr

This is part of the Neutron 'Labs' track series.

Who is this session for:

This is a Neutron session open to everyone, anyone is welcome to join and express
his/her view on where Neutron should go. For more short-term topic consider the following
tracks.

Relevant tracks:
'Labs' track

Labs track theme:
Areas of innovations that we may want to explore within the context of the Openstack
Big Tent and Neutron Stadium, or contentious topics that would will need two or more
cycles to evolve, mature and formalize. The objective of a session in this track is to get
a sense on how much time and energy the Neutron team should invest in such initiatives
and identify volunteers to spearhead and pave the way for these future advancements.

etherpad

Chair: mestery

This is part of the Neutron 'Labs' track series.

Who is this session for:

This is a Neutron session open to everyone, anyone is welcome to join and express
his/her view on where Neutron should go. For more short-term topic consider the following
tracks.

Relevant tracks:
'Labs' track

Labs track theme:
Areas of innovations that we may want to explore within the context of the Openstack
Big Tent and Neutron Stadium, or contentious topics that would will need two or more
cycles to evolve, mature and formalize. The objective of a session in this track is to get
a sense on how much time and energy the Neutron team should invest in such initiatives
and identify volunteers to spearhead and pave the way for these future advancements.

etherpad

Chair: cathy

This session is about containers networking needs, gaps and integration points with Neutron.
How Neutron fits and integrate with other containers oriented OpenStack projects like Magnum
and Kolla, and integration of Neutron with Containers Orchestration engines like Kubernetes,
Docker Swarm, Mesos.

This is part of the Neutron 'Labs' track series.

Who is this session for:

This is a Neutron session open to everyone, anyone is welcome to join and express
his/her view on where Neutron should go. For more short-term topic consider the following
tracks.

Relevant tracks:
'Labs' track

Labs track theme:
Areas of innovations that we may want to explore within the context of the Openstack
Big Tent and Neutron Stadium, or contentious topics that would will need two or more
cycles to evolve, mature and formalize. The objective of a session in this track is to get
a sense on how much time and energy the Neutron team should invest in such initiatives
and identify volunteers to spearhead and pave the way for these future advancements.

etherpad

Chair: gsagie