...

• Walter Kozlowski (Telstra)
• Suresh Krishnan (Kaloom)
• Karine Sevilla (Orange)
• Tom Van Pelt(GSMA)
• Tomas Fredberg (Ericsson)
• Sukhdev Kapur (Juniper)
• Pankaj Goyal (AT&T)
• Per Andersson  (Kaloom)
• Saad Sheikh (STC)
• Toshiyasu Wakayama (KDDI)

Special Notes:

• Weekly RM meetings are intended to
  
  • Plan RM and Network related work
  • Identify owners for new Issues/PRs
  • Track open Issues/PRs
  • Address technical issues that cannot be resolved online (i.e. resolve stalls)

...

• Linux Foundation Anti-Trust Policy Not
• GSMA Anti-Trust Policy Notice
• Recording Policies:
  • https://zoom.us/rec/play/uMAuIuyoqG43EtWS4QSDAf4oW9XsKP2s1CQW-fYNzxu3VSIGN1L3Z7YSNOX-H7MYUyogBuINABoVavXq?autoplay=true&startTime=1589371628000

• Meeting Recording:

  • Topic: RM Core weekly meeting
    Start Time : Sep 23, 2020 05:59

    Meeting Recording:
    https://zoom.us/rec/share/97Cw4HEpp4zyXYUy2dNuMNPEgwJpckFDV4KNkqgzM8MAc_1vKzaG8O1qjqExfDsu.lCN-WE4neBJmRI76

• Agenda bashing
  • 13 - 15 October 2020 LFN virtual F2F meetings.  Topics to be submitted before September 25th at 2020 October Virtual Technical Event Topic Proposals#2020OctoberVirtualTechnicalEventTopicProposals-OPNFV/CNTTTopics
  • Proposed: what are RM topics in the next release?  Proposals and discussions.
  • Proposed: Networking in view if evolved RM (in the container context)
  • Proposed: service mesh
  Please start forming teams and adding topic to 2020 October Virtual Technical Event Topic Proposals#2020OctoberVirtualTechnicalEventTopicProposals-OPNFV/CNTTTopics
• Agenda 
  1. Baraque :
     • Status update and readiness plan for Baraque release
     • Plan for  handover  to GSMA
  2. Telemetry requirements and guidelines for VNF/NFVI (added by Sukhdev)
• CNTT Marketing is asking us for some talking points about Reference Model in the Baraque release, which they need to promote this release.  I gave him some points (see below). 
  • In Baraque release we focus on making RM technology agnostic to cover both VM-based virtualisation as well as containerisation of network functions.
  • We augmented the model to allow co-existence of different Cloud Infrastructure deployments in line with the evolving technology.
  • To enable the co-existence, a new important element was added to RM: Hardware Infrastructure Manager (HIM) which can allow different virtual infrastructure implementations simultaneously using the same share hardware infrastructure.  CNTT started a collaboration with ODIM on the definition of HIM   (possibly using RedFish).
  • We expanded network and storage discussion within RM, clarifying distinction between the virtual and hardware layers within networking and storage.
  • Baraque version of RM will be handed over to GSMA Networking Group (NG), where it is planned to be published as a GSMA NG PRD (Permanent Reference Document). 
  • The on-going maintenance of this PRD and hence  the collaboration with the CNTT RM will be a responsibility of a newly formed subgroup under GSMA NG called OITF (Open Infrastructure Task Force). In the course of this collaboration, several CNTT RM contributors registered as the members of OITF.
• Please feel free to add your views here:
  • TBD
  • TBD
Post Baraque:
• 1. release:
     1. Baraque - RM released, thank to the whole Team! https://cntt.readthedocs.io/en/stable-baraque/

     2. Release of RM to GSMA: version aligned, plan to review in OITF (next week - TBC)
  2. Next release (Elbrus) M3 - 15 January 2021:
     1. Start planning; identify main topics: CNTT Elbrus Release Cycle
     2. Some already identified:
        1. Outstanding "backlog" issues
Status of LCM sections review/cleanup
• 1. 1. 2. Need to add specific requirements for Assurance in a table format, Sec 9.3 - need to create a separate issue and PRs
, most likely post Baraque/handover
• 1. 1. 2. Discussion point: how much of "Virtual network specifications" we need to add to RM
, after Baraque
• 1. 1. 2. Telemetry / Observability , Close loop automation, Infra + workloads
        3. Addressing gaps
- post Baraque
• 1. 1. 1. 
           
        2. Storage
        3. LCM (Infrastructure) - Automation, Upgradeability, 
        4. Security (check with ONAP)
        5. Gaps (as per sec 10)
        6. Networking - next level of details, secondary networks , equality of networks? orchestrate secondary networks?
        7. Macro level topic suggestion: Model for an Enterprise Cloud that comprises multi/hybrid cloud and encompasses from Data Center to Edge
        8. Hardware Infra Mgmt API to Virtual Infra Mgmt (to Orchestration as well?)
        9. Acceleration 

Actions:

1. Zlatko and Sukhdev to start discussion on observability, based on DT/Juniper contribution
2. All: identify topics for the next release RM in CNTT Elbrus Release Cycle
   
3. Walter to clean up the list of topics and propose an owner, to be finalised next Wed, we will prioritise

Minutes:

LikeBe the first to like this