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
