Wednesday, October 30, 2019
Attendees:
Please add your name in here:
- Mark Shostak* (AT&T)
- Kelvin Edmison (Nokia)
* - Lead
Special Notes:
- 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
Methodology update
- Drive document through concise, actionable Issues
- Identify MVP items/content
- Enumerate MVP items into high-level content
- Translate high-level content to open Issues (detailed level)
- Weekly RM meetings will
- Identify owners for new Issues
- Track open Issues
- Address technical issues that cannot be resolved online (i.e. resolve stalls)
- Address open questions
- RM Core (status) (Mark S.)
- Status
- Need Issue and volunteer: Determine which caps to eliminate from RMCH-4
- New Content - Container support
- New Content - VNF Design Guidelines - Need Issue and volunteer to own initial content
- RM Ops (status) (Ahmed)
- Status
- OA&M - New MVP Content
- FM
- Logging
- Provisioning/State (CM)
- LCM - New MVP Content
- LCM scope / areas covered
- Generic installer model
- Scope/function/state
- Node prototypes and creation by installer
- Open questions
- Should CNTT specify hardware? If so, to what level?
- How to accommodate both homogeneous and heterogeneous server farms?
- Do we need to add a constraints category? (e.g., maximum number of cores you can allocate to a single VNF)
- For example: | e.nfvi.res.cap.001 | #vCPU | number | Min, Max number of vCPU that can be assigned to a single VNFC | -- Are these Capabilities or Constraints?
- Does the VIM really need its own category of PMs and Caps? (e.g., e.vim.cap.xxx)
Actions:
Minutes:
