2020-05-11 - [CNTT NFG] - Meeting Agenda and Minutes
Attendees:
Please add your name in here:
@Walter.kozlowski (Telstra)
@Tomas Fredberg [Ericsson] (Ericsson)
@Sabine Demel (Deutsche Telekom)
@Ian Gardner (Vodafone)
@Sukhdev Kapur (Juniper)
@Rabi Abdel (Vodafone)
@Kodi (Vodafone)
@Ed Horwath (AT&T)
@Pankaj.Goyal (AT&T)
@Ahmed El Sawaf (STC)
@Toshi Wakayama (KDDI)
@Oya Gilligan (Vodafone)
@Karine Sevilla (Orange)
@Suresh Krishnan (Deactivated) (Kaloom)
@Petar Torre (Deactivated) (Intel)
Agenda:
Agenda Bashing
Antitrust Policy: https://r.lfnetworking.org/Antitrust%20Slide.pdf
Webinar
Review of AIs from the NFG Action Items list
Current status of the contents creation
Move from PR #1325 [RM-Networking] Networking Scope, Principles and H/L Model https://github.com/cntt-n/CNTT/pull/1325 into Master https://github.com/cntt-n/CNTT/blob/master/doc/ref_model/chapters/chapter03.md
Network Overview Diagram: PR #1568 https://github.com/cntt-n/CNTT/pull/1568
Update contents of Sec 3.5 of RM (adding principles): PR #1565 https://github.com/cntt-n/CNTT/pull/1565
Updates to Sec 4.3 of RM
Planning next updates (NFG roadmap items). Proposed High Priority items:
Role of SDN and standardization of SDN integration into Cloud Infrastructure. What are the key integration reference points that are of the highest priority?
Spine-leaf architecture. How much do we (CNTT/NFG) need to be specified, and how much we can leave to implementations?
Programmable fabric. Should we specify P4 as the standard following current ONF work, or should be more generic?
Protocols in underlay and overlay. Should we specify which protocols are allowed or be more generic?
Acceleration (incl SRIOV and DPDK). Workload inter-working aspects.
AOB
Minutes & Actions:
Minutes
Webinar: LFN organized webinars; Networking topic: Network Model, speakers: Walter, Tomas. CNTT Technical Webinar Topics
High priority items:
SDN: currently RA-1 we assume Neutron API compatibility. The issue: either maintain this view or propose beyond this view (e.g. using upstream OpenStack, or use Heat templates, etc.). See AI #8.
Spine-leaf architecture: h/l diagram in RM? is this over-specifying? Does RA-1 needs more information form RM? RA-1 does not need more information: Pankaj. To be continued in the next meeting (parked).
Action Items
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 | Closed | 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 (An email is sent to the team by Sukhdev) | 29 April 2020 | Sukhdev | Closed | |
4 | Draw a network diagram similar to other diagrams in Chapter 3 | 11 May 2020 | Walter and Tomas | Done | |
5 | Create PR to move network concepts, model and deployment examples into 4.3 | 11 May 2020 | Tomas | Open | RM Sec 4.3 |
6 | Present the NFG view on the proposed implementation of Tungsten fabric (see Minutes above) to Rabi and if needed TSC for their approval | 5 May 2020 | Walter | Closed | Email/call |
7 | Plan for the long term CNTT view on SDN controller, to be presented to NFG | 11 May 2020 | Walter | Open | offline call |
8 | Draft a summary of the problem and propose options; Walter to organise this work | 25 May 2020 | Pankaj, Ahmed, Sukhdev,Tomas,Walter (lead), Suresh | Open | RM, RA-1, RA-2(?) |
9 | |||||
10 | |||||
11 |
LikeBe the first to like this