Skip to end of metadata
Go to start of metadata

Zoom link:


Please add your name in here:


    • Agenda 
      • New time for RM meetings: Wednesdays, 8:00pm UTC, 9:00pm CET, 12:00 pm California, 7:00 am (Thursday) Melbourne
      • Anuket/Meld: Interim TSC update: Anuket Interim TSC
      • Next vF2F conference in February 2021: topics are required: Feb vF2F Feb 1-4: 2021 February LFN Developer & Testing Forum. Proposals due 15 January 2021. Potential topics and presenters (TBC):
        • Hybrid, multi-cloud model: DC to Edge (Pankaj, Walter)
        • Acceleration Abstraction (Petar, Tomas, Per)
        • Beyond IaaS/CaaS for Cloud Infrastructure in RM (Petar, Pankaj, Walter)
        • Telemetry, monitoring, observability (Sukhdev, Petar, Zlatko)
      • Walter→create placeholders in 2021 February LFN Developer & Testing Forum. All→ please add topics if you want to present other topics
      • Next release (Elbrus) M3 - 15 January 2021: Update on Elbrus Issues and PRs progress/actions and PRIORITIZATION

      • MVP: means that we should have an almost ready contents by 20 December 2020

        Network/Hardware Management

        Hardware Infrastructure Management: function and APIs

        Tomas, Walter




        Issue 2050

        Requirements for  NBI from HIM: work in progress

        Contents will be available during the week of 14th December

        Primary & secondary networking

        Tomas, Suresh, Gergely



        Probably RA-2 topic, discuss with Tom K. Gergely, Georg Kunz,  whether RM can help (prob general guidance and requirements)

        Issue 2085: work in progress

        Contents will be available during the week of 14th December


        Security (workloads and infrastructure) - alignment with ONAP

        Karine, Amy, Pankaj



        Done from Elbrus MVP perspective

        Karine reviewing FS.31 and FS.40 from GSMA FASG from the possible alignment perspective for post Elbrus

        Operations and Life-cycle Management 



        Action: Issue 2086; identify gaps in Chapter 9 - open fort comments

        Proposed new structure of Chapter 9

        9.1 Introduction (Walter, PR#2114 for review, further updates)

        9.2 Configuration and Lifecycle Management (includes closed loop automation, Change Control)

        9.3 Assurance

           9.3.3 Assurance Overview (as is now)

           9.3.2 Observability (Sukhdev)

           9.3.3 Telemetry (Sukhdev) 

        9.4 Capacity Management (as is now)

        9.5 Automation Work in Progress. All → use RM Automation Content for adding contents, remarks, next meeting on Automation scheduled for Monday 14 Dec at 12pm UTC, please contact Pankaj Goyal or Walter Kozlowski if you want to join.

           9.5.1 Infrastructure LCM Automation ( including Platform Software and CI/CD)  (Saad) - End-2-End understanding of what type of automation ought to be done on what layers and includes

        • hardware configuration CI/CD
        • networking automation
        • software development CI/CD
        • software deployment CI/CD (operator environment)
        • Identify "Closed Loop Automation" as a Gap in Ch10

           9.5.2  Application LCM Automation Workload onboarding automation (including CI/CD)  (Saad) includes

        • workload onboarding automation - the scope for RM is to describe support only but leave the details to RA/RI;
        • RM will state the requirements including for CI/CD for ensuring software security scans, image integrity checks, OS version checks, etc. prior to deployment -
        • the tenant processes for application LCM (such as updates) are out of scope

           9.5.3 Tenant creation automation

        • requirements for enterprise processes prior to tenant creation on the platform
        • networking automation

        Security Automation => Chapter 7, Security; but compare with Observability/Telemetry 

        Networking Automation => Section 4.3 Networking; but cloud level automation networking aspects may be in Chapter 9

        Automation (closed loop automation)

        Should be in part in LCM (Chapter 9) - Issue  2087

        Proposed to include into Chapter 9 (see above)

        Walter → write up a PR defining the Gap


        Sukhdev, Zlatko, Petar



        Issue 2052 contains a link to a google document:

        All → please add comments there 


        Hardware acceleration abstraction

        Petar, Tomas, Per, Walter



        Issue 2051; open for comments 

        PR# 2115 to create a structure

        Initial text work in progress, plan to share within the week of 14th of Dec 2020

        Compute node acceleration (incl smartNICs, GPU, etc)


        Programmable fabric


        Network acceleration

        Karine, Petar


        Needed a structure

        Further details needed (all classes of storage)

        Issue 2056: Need contributors and expertise it has a link to the June PTG notes

        Action: Beth → provide a structure (PTG etherpad can be used)

        Special use cases

        Load balancing

        Per, SukhdevMediumIssue 2095: Per to provide concept description for comments

        Mutual discovery (workloads/infrastructure)

        Sukhdev, Tomas
        MediumIssue 2088; Sukhdev to add the concept description for comments

        Service function chaining

        Suresh, Sukhdev



        Issue 2089; text in Issue 

        Action: All → review and comments from the Team

        Model for Enterprise Cloud

        and Edge

        Walter, Pankaj, Ahmed



        Issue 2049: Multi/hybrid cloud  from Data Centre to Edge;

        PR#2118 for review

        Action: All → review PR#2118

        Alignment with ONAPInvestigate topics other than securityPetarLowPetar to present to RM meeting
        Alignment with GSMA OPGInvestigate alignment pointsWalterLowDepends on outcomes of joint OITF and OPG meetings
        Alignment with ORAN?Influence ORAN regarding telco cloud

        Tomas raised this question as he participates in WG 6. Karine to find out how we could discuss possible  dependencies, alignments, cloud principles....
        Alignment  with ODIM
        Bring to this meeting the actions, comments from previous sessions and vF2F 
        Granularity of RM profiles

        Issue 2068

        Ricardo as the new RA-2 leader has joined RM meetings

        REview of RM Chapter 2
        Issues 2067, 2067


        • Karine → inform the RM Team about O-RAN (WG 6) collaboration ver 2 of  the design document (Cloud Platform) will be finalised by the end of November (reference conformance for K8s)
        • All→ please add vF2F topics if you want to present other topics
        • All → use RM Automation Content for adding contents, remarks; next meeting on Automation scheduled for Monday 14 Dec at 12pm UTC, please contact Pankaj Goyal or Walter Kozlowski if you want to join.
        • Walter → write up a PR defining the Gap

        • All → please add comments for Issue 2052 which contains a link to a google document:
        •  Beth → provide a structure for Storage (PTG etherpad can be used)
        • All → review Issue 2089 'Service Function Chaining', text in Issue
        • All → review PR#2118 on Multi-cloud, Hybrid model


        1.  GSMA non-members who want to participate in OITF please contact Tom Van Pelt ,  Those who are interested in GSMA PRD FS.31 - it is available at
        2. Akraino meetings on Dec 17th: (CNTT Edge presented by Beth and Ahmed)
        3. Cloud Native Network Functions (CNF) Working Group:
  • No labels