Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Please add your name in here:

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)

...

    1. Linux Foundation Anti-Trust Policy Not
    2. GSMA Anti-Trust Policy Notice
    3. Recording Policies:
    4. Meeting Recording:


    5. Agenda bashing
    6. Agenda 
      • Next release (Elbrus) M3 - 15 January 2021:
        1. Start planning; identify main topics: CNTT Next Release starts Sep 25 2020
      • Internal plan proposal, for the team discussion:


        AreaTopicOwner/team (proposal)PriorityComments

        Network/Hardware Management

        Hardware Infrastructure Management: function and APIs

        Tomas, WalterHighAgreed

        Primary & secondary networking

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

        Operations

        Security (workloads and infrastructure) - alignment with ONAP

        Karine, Amy, PankajHighAgreed 

        Life-cycle Management  (infrastructure)

        Walter, Karine, Pankaj, PerMediumUpgradeability, migration

        Automation (closed loop automation)Walter, TomasMediumNeed to plan

        Observability/telemetry

        Sukhdev, ZlatkoMediumvF2F session in planning
        Acceleration

        Hardware acceleration abstraction

        Petar, Pankaj, Tomas, Per, WalterHighDecide on subtopics

        Compute node acceleration (incl smartNICs, GPU, etc)

        TBAsmartNICsPetar, Per

        Programmable fabric

        Per, SureshTBA

        Network acceleration

        Suresh, PerTBA
        Storage
        ?, Petar, Karine, ?High

        Needed a structure

        Further details needed (all classes of storage)

        Need contributors and expertise

        Special use cases

        Load balancing

        Per, SukhdevMedium

        Mutual discovery (workloads/infrastructure)

        Sukhdev, Tomas
        Medium

        Service function chaining

        Suresh, SukhdevMedium
        Model for Enterprise Cloud
        Walter, Pankaj, AhmedMedium

        Multi/hybrid cloud  from Data Centre to Edge

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 Next Release starts Sep 25 2020
  3. Walter to clean up the list of topics and propose an owner, to be finalised next Wed, we will prioritise

Minutes:

      • Alignment with ONAPInvestigate topics other than securityPetar
        Petar to present to RM meeting


Actions:

  1. All: start creating Issues and PRs for the topics identified
  2. Question: do we need a special RM chapter for Requirements?


Minutes:

  1.  Some already identified:
  2. Outstanding "backlog" issues
  3. Need to add specific requirements for Assurance in a table format, Sec 9.3 - need to create a separate issue and PRs
  4. Discussion point: how much of "Virtual network specifications" we need to add to RM
  5. Telemetry / Observability , Close loop automation, Infra + workloads
  6. Addressing gaps
  7. Storage
  8. LCM (Infrastructure) - Automation, Upgradeability, 
  9. Security (check with ONAP)
  10. Gaps (as per sec 10)
  11. Networking - next level of details, secondary networks (question), equality of networks? orchestrate secondary networks?
  12. Macro level topic suggestion: Model for an Enterprise Cloud that comprises multi/hybrid cloud and encompasses from Data Center to Edge
  13. Hardware Infra Mgmt API to Virtual Infra Mgmt (to Orchestration as well?)
  14. Acceleration