Go to start of metadata

• Attendees:
• Agenda:
• Minutes & Actions:

Attendees:

Please add your name in here:

• Walter Kozlowski (Telstra)

Agenda:

• Agenda Bashing

• Antitrust Policy: https://r.lfnetworking.org/Antitrust%20Slide.pdf

• Current status of the contents move from PR #1325 [RM-Networking] Networking Scope, Principles and H/L Model https://github.com/cntt-n/CNTT/pull/1325 into Master
• Planning next updates
• Action item from RA1 for NFG: How to handle custom APIs? Get upstream (OSTK)/another project to define common (useful) SDN API extensions.  What should be the CNTT position?  Wait for CNTT Network FG to define position. 
  • Some thoughts about addressing ths (proposed by Sukhdev): 
    • SDN Controllers have plugins in Neutron - All common Neutron APIs are directly supported by the controllers - Additional APIs are needed for advanced networking features, so, either we: 
      • 1) Upstream these additional APIs into Neutron (very hard and non-scalable)
      • 2) Come with an extension model in Neutron so that additional APIs are invoked through this extension
      • 3) Most automated production deployments use Heat templates to manage Neutron and SDN controllers - we specify a common model to define the Heat template/resources - may be the easiest way to address this
• AOB

Minutes & Actions:

Minutes

Action Items