...
- This is the inaugural meeting for the RM, under aligned to the post-Antwerp structure
- The focus of the first meeting will be on alignment regarding direction and logistics
- Each of the three RM sections will get 20 minutes
- Given the limited time available, we will focus on identifying issues/actions/next steps, but not solving them right now
Agenda:
- Linux Foundation Anti-Trust Policy Notice
- GSMA Anti-Trust Policy Notice
- Agenda bashing
- PR #388 / Issue #385
- Identifier schema review
- Identify PMs to remove
- Identify external and internal PMs to replace measurements relocated to RMCH-8 // Action from last week's mtg
- Align on definitions for capabilities/
metrics/constraints vs. resources/capabilities, then normalize chapter - Clarify language around Sect. 4.1.1 (int vs. ext)
Actions:
- TBD
...
- Master Meeting Logistics (bridge, time, slack, IRC, Github, etc.)
- New Issue creation
- Required for all changes/enhancements
- Must include -
- Concise title
- What: Actionable description
- Why: Justification for inclusion
- RM Core (status) (Mark S.)
- Status
- Enhancing usability (consistency, completeness, major issues and upgrades)
- New Content - Container support
- New Content - VNF Guidelines
- Major Issue - HW Profiles and performance
- Is a substream meeting required? If so, when?
- RM Ops (status) (Ahmed)
- Status
- New Content - OA&M
- FM
- Logging
- Capacity
- Provisioning/State (CM)
- New Content - LCM
- NFVI areas covered
- Generic installer model
- Scope/function/state
- Node prototypes and creation by installer
- Is a substream meeting required? If so, when?
- RM Comp (status) (Victor)
- Status
- Alignment w/ RC on division of responsibility
- Identification and migration of content to RC
- New Content - Certification and Badging Requirements
- Is a substream meeting required? If so, when?
- New Business
Actions:
- Core
- TBD
- Ops
- TBD
- Comp
- TBD
Minutes:
- Core
- TBD
- Ops
- TBD
- Comp
- TBD