...
Please add your name in here:
- TBD
- Mark Shostak* (AT&T)
- Kelvin Edmison (Nokia)
- Nick Chase (Mirantis)
- Trevor Cooper (Intel)
- Al Morton (AT&T)
- Michael Fix (AT&T)
- Ahmed El Sawaf (STC)
- Karine Sevilla (Orange)
- Ulrich Kleber (Huawei)
- Manik Sidana (VoerEir)
- Pierre Lynch (Keysight)
- Georg Kunz (Ericsson)
...
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
...
- Linux Foundation Anti-Trust Policy Notice
- GSMA Anti-Trust Policy Notice
- Agenda bashing<TBD>
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
- Drive document through concise, actionable Issues
- RM Core (status) (Mark S.)
- StatusEnhancing usability (consistency, completeness, major issues and upgrades)
- Need Issue and volunteer: Determine which caps to eliminate from RMCH-4
- New Content - Container support
- New Content - VNF Design Guidelines Major Issue - HW Profiles and performance- Need Issue and volunteer to own initial content
- RM Ops (status) (Ahmed)
- Status
- New Content - OA&M - New MVP Content
- FM
- LoggingCapacity
- Provisioning/State (CM)
- LCM - New MVP Content -
- LCM
- NFVI scope / areas covered
- Generic installer model
- Scope/function/state
- Node prototypes and creation by installer
...
- RM Comp (status) (Victor)
- Status
- Alignment w/ RC on division of responsibility
- Identification and migration of content to RC
- TBD
- 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)New Content - Certification and Badging Requirements
- New Business
Actions:
- General
- None at this time
- Core
- None at this time
- None at this time
- Kelvin: Sync up w/ internal people WRT VNF Design Guidelines input
- Ops
- Trevor: Sync up w/ Owen (from Intel)
- Comp
- None at this time
Minutes:
- General
- Discussed methodology
- Nick Chase volunteered to assist people w/ technical writingNil
- Core
- Nil
- Discussed VNF Guidelines and other listed Core agenda items
- Ops
- Ahmed presented draft monitoring architecture for feedback (as follows)
- Kelvin: Indicated focus on metrics, rather than architecture (implementation)
- Kelvin: Indicated diagram might be more appropriate for RA
- Karine: Diagram should be more generic for RM
- Nil
- Ahmed presented draft monitoring architecture for feedback (as follows)
- Comp
- Nil