Attendees:
Please add your name in here:
- Walter.kozlowski (Telstra)
- Sukhdev Kapur (Juniper)
- Tomas Fredberg [Ericsson] (Ericsson)
- Rabi Abdel (Vodafone)
- Ian Gardner (Vodafone)
- Ed Horwath (AT&T)
- Saad Ullah Sheikh (STC)
- Pankaj.Goyal (AT&T)
- Trevor Cooper (Intel)
- Ahmed El Sawaf (STC)
- Toshi Wakayama (KDDI)
- Sabine Demel (Deutsche Telekom)
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
- 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:
- Some thoughts about addressing ths (proposed by Sukhdev):
- AOB
Minutes & Actions:
Minutes
- Agreement: after updates (currently being done by Tomas, Ahmed and Walter) reflecting currently open comments from Mark and Uli the contents is ready for merging into RM, see AI # 1
- Clarification: physical networking is included in the scope of Cloud Infrastructure
Action Items
| Description | Due Date | Assignee | Status | Task In | |
|---|---|---|---|---|---|
| 1 | Request merging approval from Kelvin and Rabi to PR#1325 into the Master RM; proposal is to include in RM Chapter 3. Proposed section 3.5 or 4.3 to be agreed at RM meeting. PR will be needed after approval. | 29 April 2020 | Walter | Open | email/RM meeting |
| 2 | Need to distinguish between VIM and Cloud Infrastructure Manager, and reflecting different levels of infrastructure management. Topic for TSC. | 29 April 2020 | Rabi | Open | agenda for TSC |
| 3 | Write up an email proposal regarding short term position on SDN (needed for RC) and long term position on SDN APIs (Neutron extension) for an offline discussion | 29 April 2020 | Sukhdev | Open | |
| 4 | |||||
| 5 | |||||
| 6 | |||||
| 7 | |||||
| 8 | |||||
| 9 | |||||
| 10 | |||||
| 11 |