OpenStack Mitaka Design Summit

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

https://etherpad.openstack.org/p/TYO-ops-networking

Note: This is an interactive discussion, no presentations will be given.

It must be easier to add VIF driver support for all the various Neutron subsystems.
OS VIF library tries to tackle this issue, starting with a focus on the libvirt driver.

More info:
https://etherpad.openstack.org/p/mitaka-nova-os-vif-lib

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

The first networking solution for Magnum used a simple flannel overlay network with our Kubernetes bay. Since then, Magnum and Neutron contributors ahve been working together to design Kuryr, which acts as a libnetwork driver for Docker that connects docker containers to your Neutron networks. This way it can work with your existing SDN. Magnum Also has a new networking specification for that is designed to work with exising Bay types, as well as new ones that are not based on Docker containers. In this session we will outline Magnums goals and non-goals for networking, and explain our point-of-view for how OpenStack cloud resources, including Magnum bays, should be able to share common networks easily.

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

The Neutron contributors meetup is a informal gathering of the project contributors, with an open agenda.

Click here for details on the meetup agenda.

The Neutron contributors meetup is a informal gathering of the project contributors, with an open agenda.

Click here for details on the meetup agenda.