Jump to: navigation, search

Meetings/Neutron-L3-Subteam

< Meetings
Revision as of 19:45, 22 February 2014 by Carl (talk | contribs)

L3 Subteam

The L3 Neutron sub-team exists to help members on the Neutron community reach consensus on various L3 subjects. This does not automatically include every L3 subject, especially those that are progressing well and mature on their own. Initially, this team's charter will include ...

Relevant blueprints:

Meetings

  • Weekly on Thursday at 1500 UTC
  • IRC channel: #openstack-meeting-3
  • Chair: Carl Baldwin (carl_baldwin)

Distributed-Virtual-Router meetings are still on-going. It deals with a specific use case under this sub team.

Agendas for 2014

The agenda is light for now as we establish a regular cadence of meetings. We will gradually add more topics.

  • dvr
  • l3-high-availability
  • l3-agent-consolidation
  • dynamic-routing-discussion

Meeting Logs and Minutes

Meetings, with their notes and logs, will be found under http://eavesdrop.openstack.org/meetings/neutron_l3

Monday, February 17th, 2014

  • Team meeting
    • For now, attend the DVR meeting
    • Wednesdays at 1600 UTC ? Thursdays at 1500 UTC ?
  • DVR
    • F2F was very productive.
      • DVR Team updated the OpenStack Community on what has changed from the earlier proposal.
        • No kernel Module
        • Use existing namespaces
        • Split L3, Floating IP and default External Access.
        • Provide migration Path
        • Supporting both East-West and North-South.
      • Got a clear direction from the PTL that we don’t need to address the distributed SNAT at this point of time and focus on the centralized solution that we proposed.
      • The DVR Agent design (both L2 and L3) should be discussed with the respective teams before we proceed. Probably a separate document or blueprint that discusses the flows.
      • No support for Dynamic routing protocols.
      • Discussed both active blueprints.(
      • Community suggested that we need to consider or check if the OVS ARP responder can be utilized.
      • HA for the Centralized Service Node (l3-high-availability)
  • L3 Agent consolidation
  • HA Routers
    • All patches are submitted, the agent patch has to be reworked a bit to leverage the changes made in the keepalived patch and the conntrackd patch written by Assaf Muller. I think Assaf's patch should also be reworked since I have introduced some new features to the external_process package. I already have a new version of the agent which uses the keepalived changes but I didn't submit yet. I'm currently on vacation, and I'll be back in 2 weeks. Regards,

-Sylvain