Attention: new zoom link
https://zoom.us/j/997256543?pwd=MWptM0F0Y1NpckhFVUgrZnM2TkJ0Zz09
Attendees:
Please add your name in here:
- Walter Kozlowski (Telstra)
- Tomas Fredberg (Ericsson)
- Suresh Krishnan (Kaloom)
- Karine Sevilla (Orange)
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)
Agenda:
- Linux Foundation Anti-Trust Policy Not
- GSMA Anti-Trust Policy Notice
- Recording Policies:
Meeting Recording:
- Agenda bashing
- Agenda
- Next release (Elbrus) M3 - 15 January 2021:
- Start planning; identify main topics: CNTT Next Release starts Sep 25 2020
- Internal plan proposal, for the team discussion:
Area Topic Owner/team (proposal) Priority Comments Network/Hardware Management
Hardware Infrastructure Management: function and APIs
Tomas, Walter Primary & secondary networking
Tomas, Suresh, Gergely Operations
Security (workloads and infrastructure) - alignment with ONAP
Karine, Amy Life-cycle Management (infrastructure)
Walter, Karine, Pankaj Observability/telemetry
Sukhdev, Zlatko Acceleration Hardware acceleration
Petar, Pankaj smartNICs Petar, Per Programmable fabric Per, Suresh Network acceleration Suresh, Per Storage Petar, Karine Further details needed
Special use cases
Load balancing
Per, Sukhdev Mutual discovery (workloads/infrastructure)
Sukhdev, Tomas Service function chaining
Suresh, Sukhdev Model for Enterprise Cloud Walter, Pankaj, Ahmed Multi/hybrid cloud from Data Centre to Edge
- Next release (Elbrus) M3 - 15 January 2021:
Actions:
- Zlatko and Sukhdev to start discussion on observability, based on DT/Juniper contribution
- All: identify topics for the next release RM in CNTT Next Release starts Sep 25 2020
- Walter to clean up the list of topics and propose an owner, to be finalised next Wed, we will prioritise
Minutes:
- Some already identified:
- Outstanding "backlog" issues
- Need to add specific requirements for Assurance in a table format, Sec 9.3 - need to create a separate issue and PRs
- Discussion point: how much of "Virtual network specifications" we need to add to RM
- Telemetry / Observability , Close loop automation, Infra + workloads
- Addressing gaps
- Storage
- LCM (Infrastructure) - Automation, Upgradeability,
- Security (check with ONAP)
- Gaps (as per sec 10)
- Networking - next level of details, secondary networks
, equality of networks? orchestrate secondary networks?
- Macro level topic suggestion: Model for an Enterprise Cloud that comprises multi/hybrid cloud and encompasses from Data Center to Edge
- Hardware Infra Mgmt API to Virtual Infra Mgmt (to Orchestration as well?)
- Acceleration