Project Name:
- Proposed name for the project: VF-C
- Proposed name for the repository: vfc
Project description:
- As part of the integration between OpenECOMP and OPEN-O, this proposed project VF-C leverages ETSI NFV MANO architecture and information model as a reference, and implements full life cycle management and FCAPS of VNF and NS.
Scope:
- Describe the functionality to be provided by the project. Please provide the full intended scope of the project; not just what is intended for the project's first release.
- NFV-O Component,
- compliant with ETSI NFV MANO architecture and information model,
- providing resource orchestration and full life cycle management and FCAPS for NS,
- providing standard south bound interface to VNFMs,
- providing north bound interface to SO, to take part in fulfilling the orchestraion and operation of end2end service,
- providing interface and work with DCAE and Policy for Close Loop Automation.
- VNFM Component,
- compliant with ETSI NFV MANO architecture and information model
- providing full life cycle management and FCAPS for VNFs,
- providing interface and work with NFV-O component, to take part in fulfiiling the LCM and FCAPS management of NS,
- providing interface and work with DCAE and Policy for Close Loop Automation.
- NFV-O Component,
- Specify any interface/API specification proposed,
- interface to DCAE and Policy
- interface to A&AI
- interface to SO
- interface to VNFM
- interface to Multi-VIM
- Identity a list of features and functionality will be developed.
- features
- compliant with ETSI NFV MANO architecture and information model
- providing standard south bound interface to VNFMs
- take part in end2end service orchestration by working with SO
- take part in close loop automation by working with DCAE and Policy
- functionalities
- resource orchestration and full life cycle management and FCAPS for NS
- full life cycle management and FCAPS for VNFs
- Identify what is in or out of scope. During the development phase, it helps reduce discussion.
- end2end service orchestration is out of scope for VF-C
Architecture Alignment:
- How does this project fit into the rest of the ONAP Architecture?
- Please Include architecture diagram if possible
- What other ONAP projects does this project depend on?
- SDC, A&AI, DCAE, Policy, Common Service, Modeling.
- How does this align with external standards/specifications?
VF-C takes the following specifications as a reference.- APIs/Interfaces: ETSI NFV IFA 007, ETSI NFV IFA 008, ETSI NFV SOL 005
- Information/data models: ETSI NFV IFA 015, ETSI NFV SOL 001, ETSI NFV SOL 004
- Are there dependencies with other open source projects?
- WSO2: BPMN workflow engine.
Resources:
- Primary Contact Person
Lingli Deng (denglingli@chinamobile.com) Names, gerrit IDs, and company affiliations of the committers
Lingli Deng
China Mobile
Beijing, China. UTC +8
Shitao Li
Huawei
Nanjing, China. UTC+8
Maopeng Zhang
ZTE
Nanjing, China. UTC +8
Kanagaraj Manickam
Huawei
India. UTC +5:30
Shen Tao
China Mobile
Beijing, China. UTC +8
Jinhua Fu
ZTE
Nanjing, China. UTC +8
Chengli Wang
China Mobile
Beijing, China. UTC +8
Guangmin Liu
Huawei
Shenzhen, China. UTC +8
Nanjing, China. UTC +8
Yuanxing Feng
ZTE
Nanjing, China. UTC +8
Yan Yang
China Mobile
Beijing, China. UTC +8
Tianqi Liu
Huawei
Shenzhen, China. UTC +8
Victor Gao
Huawei
Shenzhen, China. UTC +8
Anatoly Andrianov
Nokia
Chicago, U.S. CST
Nagesha Subramanya
Nokia
Bangalore, India. IST
- Names and affiliations of any other contributors
- Project Roles (include RACI chart, if applicable)
Other Information:
- link to seed code (if applicable)
git clone https://gerrit.open-o.org/r/nfvo - Vendor Neutral
- if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
- Meets Board policy (including IPR)
Use the above information to create a key project facts section on your project page
Key Project Facts
Project Name:
- JIRA project name:
- JIRA project prefix:
Repo name: Lifecycle State: Primary Contact: Project Lead: mailing list tag [Should match Jira Project Prefix] Committers: foo@bar.com baz@qux.com *Link to TSC approval:
Link to approval of additional submitters: