Attendees:

Please add your name in here:

Agenda:

Agenda Bashing
Antitrust Policy: https://r.lfnetworking.org/Antitrust%20Slide.pdf
Feedback from the NFG session (21 April) at the CNTT/OPNFV virtual conference
Current status of PR #1325 [RM-Networking] Networking Scope, Principles and H/L Model https://github.com/cntt-n/CNTT/pull/1325
Agreement to merge the contents of PR #1325 into RM Master as a base of further work
Agreement on next steps: creation of new Issues and PRs to provide new/updated contents in RM and RAs
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