...
- Describe the functionality proposed.
- 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 which do not require a vendor VNFM,
- 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 Provide interfaces to DCAE and Policy
- interface to A&AI
- interface to Provide interfaces to SO
- interface Provide interfaces to Portal/VID
- interface Provide interfaces to Vendor VNFM
- Use vendor VNFM interfaces
- Use interface to Multi-VIM interfaces
- Use A&AI interfaces
- 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
Identify the usecase in the Release 1
- Use Case: VoLTE (vIMS + vEPC)
- VNF onboarding
- Network service deployment automation
- Network service termination automation
- Framework for integration with vendor provided VNFM
...
- What other ONAP projects does this project depend on?
- SDC, A&AI, CLAMP, DCAE, Policy, SO, Common Service, Modeling, and Multi-Vim
Note: - VF-C will be align to the ONAP modeling project defined data model(TOSCA/Yang) and information model
Now the VF-C seed code doesn’t depend on the common controller framework project. In the future, the common controller framework can be analyzed after it puts the seed code on the wiki,
- SDC, A&AI, CLAMP, DCAE, Policy, SO, Common Service, Modeling, and Multi-Vim
- 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 – additional API may be required
- Information/data models: ETSI NFV IFA 015, ETSI NFV SOL 001, ETSI NFV SOL 004 – additional API may be required
- Are there dependencies with other open source projects?
- WSO2: BPMN workflow engine.
- ARIA: TOSCA Parser.
...
- 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
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
Yan Yang
China Mobile
Beijing, China. UTC +8
Victor Gao
Huawei
Shenzhen, China. UTC +8
Anatoly Andrianov
Nokia
Chicago, U.S. CST
Nagesha Subramanya
Nokia
Bangalore, India. IST
Xinhui Li VMware lxinhui@vmware.com Beijing, China. UTC + 8 Guirong Wang Boco wangguirong@boco.com.cn Beijing, China. UTC +8 Xiaodong Ning Boco ningxiaodong2017@boco.com.cn Beijing, China. UTC +8 Yog Vashishth Jio Yog.Vashishth@ril.com India GMT+05:30 Adityakar Jha Jio Adityakar.Jha@ril.com India GMT+05:30 Hu Dong raisecom donghu@raisecom.com Beijing, China. UTC +8 Yannan Han raisecom hanyanan@raisecom.com Beijing, China. UTC +8 Names and affiliations of any other contributors
name company email time zone Yunlong Ying ZTE ying.yunlong@zte.com.cn Nanjing, China. UTC +8 Yuanxing Feng ZTE feng.yuanxing@zte.com.cn Nanjing, China. UTC +8 Shitao Li Huawei lishitao@huawei.com Nanjing, China. UTC+8 Guangmin Liu Huawei liuguangmin@huawei.com Shenzhen, China. UTC +8 Yang Xu Huawei yang.xu3@huawei.com New Jersey, USA UTC -5 Hui Deng Huawei denghui12@huawei.com Beijing, China. UTC +8
- Project Roles (include RACI chart, if applicable)
...
- Maopeng Zhang(ZTE), zhang.maopeng1@zte.com.cn
- Jinhua Fu(ZTE), fu.jinhua@zte.com.cn
- Kanagaraj Manickam(Huawei),kanagaraj.manickam@huawei.com
- Victor Gao(Huawei),victor.gao@huawei.com
- Tao Shen(China Mobile),shentao@chinamobile.com
- Yan Yang(China Mobile),yangyanyj@chinamobile.com
- Anatoly Andrianov(Nokia),anatoly.andrianov@nokia.com
- Nagesha Subramanya(Nokia),nagesha.subramanya@nokia.com
- Xinhui Li(VMware),lxinhui@vmware.com
- Guirong Wang(Boco),wangguirong@boco.com.cn
- Xiaodong Ning(Boco),ningxiaodong2017@boco.com.cn
- Yog Vashishth(Jio),Yog.Vashishth@ril.com
- Adityakar Jha(Jio),Adityakar.Jha@ril.com
- Hu Dong(Raisecom),donghu@raisecom.com
- Yannan Han(Raisecom),hanyanan@raisecom.com
*Link to TSC approval:
Link to approval of additional submitters:
...