...
ONAP Meeting Session name: <insert onap module name>
Need Identification:
Identified Need | Description | Driver | Dependencies | Project fit |
| interface with MSO | ||||
| interface with A&AI | ||||
| interface down to SVNFM | ||||
| interface to APP-C?? | Further discussion required, what's relationship with EM | |||
| interface to Infra-C | Capture relationship with Multi-VIM | |||
| Full LCM for network service | ?? | SO dependency, split between them | ||
| alignment with APPC regarding orchestration outcome, vnf guidelines | ||||
| flexibility to VNFM being part of VF-C?? | ||||
| interface with DCAE | ||||
| sfc should be supported in VF-C or controller?? | consider to alignment with using controller/orchestration framework as much as make sense | |||
| dependency on design time (including vnf sdk) | ||||
Should this be a sperated project or within APP-C evolution?
Have a single project to promote integration.
developers talk each other
speaking as NFVO code contributor, he think that VF-C project is not counterpart of ecomp ,should be a seperate project.
Project proposals.
[repeat for each project. Note: This is not a complete project proposal skeleton, only sufficient enough for this discussion]
Project 1: VF-C
Project Name:
- Provide a brief project name.
...
- Provide a high level description of the project
Scope:
- Quickly identify scope, consider: documentation, APIs, models, testing, integration, functionalityNFVO/VNFM.
- Note of any particular deliverables to highlightInterfaces.
- If anything is out of scope, not it downTesting
- documentation (alignment)
-
Other:
- Identify baseline code (if any)
...