...
Please add your name in here:
- Walter Kozlowski (Telstra)
- Tomas Fredberg (Ericsson)
- Suresh Krishnan (Kaloom)
- Karine Sevilla (Orange)
- Per Andersson (Kaloom)
- Ulrich Kleber (Huawei)
- Pankaj Goyal (AT&T)
- Toshiyasu Wakayama (KDDI)
- Ahmed El Sawaf(stc)
- Petar Torre (Intel)
- Sukhdev Kapur (Juniper)
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:
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 High Agreed Primary & secondary networking
Tomas, Suresh, Gergely Medium Probably 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, Pankaj High Agreed Life-cycle Management (infrastructure)
Walter, Karine, Pankaj, Per Medium Upgradeability, migration Automation (closed loop automation) Walter, Tomas Medium Need to plan Observability/telemetry
Sukhdev, Zlatko Medium vF2F session in planning Acceleration Hardware acceleration abstraction
Petar, Pankaj, Tomas, Per, Walter High Decide on subtopics Compute node acceleration (incl smartNICs, GPU, etc) TBA smartNICs Petar, 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, Sukhdev Medium Mutual discovery (workloads/infrastructure)
Sukhdev, Tomas Medium Service function chaining
Suresh, Sukhdev Medium Model for Enterprise Cloud Walter, Pankaj, Ahmed Medium 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:
Alignment with ONAP Investigate topics other than security Petar Petar to present to RM meeting
Actions:
- All: start creating Issues and PRs for the topics identified
- Question: do we need a special RM chapter for Requirements?
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