...
- 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,
- Provide interfaces to DCAE and Policy
- Provide interfaces to SO
- Provide interfaces to Portal/VID
- Provide interfaces to Vendor VNFM
- Use vendor VNFM interfaces
- Use Multi-VIM interfaces
- Use A&AI interfaces
- Use SDC 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
- (obselete)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?
- Projects depend on: SDC, A&AI, CLAMP,DCAE, Policy, SO, Common Common Service, Modeling , and Multi-Vim
- Interfaces provided to: Policy, SO,VID, portal
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 We will collaborate with common controller framework can be analyzed after it puts the seed code on the wiki,to identify the potential denpendency in the future.
- 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
yangyanyjy@chinamobileName Gerrit ID Company Email Time Zone Lingli Deng
lingli China Mobile
Beijing, China. UTC +8
Maopeng Zhang
maopengzhang ZTE
Nanjing, China. UTC +8
Kanagaraj Manickam
mkr1481 Huawei
India. UTC +5:30
Jinhua Fu
fujinhua ZTE
Nanjing, China. UTC +8
Yan Yang
yangyan China Mobile
ShenzhenBeijing, China. UTC +8
Victor Gao
g310497 Huawei
.XiAn, China
, U.S. CST, UTC+8
Anatoly Andrianov
caa028 Nokia
Chicago
Bangalore,, USA, UTC -6
Nagesha Subramanya
hsnagesh Nokia
ISTIndia.
UTC +5:30
Xinhui Li xinhuili VMware lxinhui@vmware.com Beijing, China. UTC + 8 Guirong Wang Wang_Guirong Boco wangguirong@boco.com.cn Beijing, China. UTC +8 Xiaodong Ning ningxiaodong2017 Boco ningxiaodong2017@boco.com.cn Beijing, China. UTC +8 Yog Vashishth yogvashishth Jio Yog.Vashishth@ril.com India GMT+05:30 Adityakar Jha adityakar.jha Jio Adityakar.Jha@ril.com India GMT+05:30 Hu Dong donghu1102 raisecom donghu@raisecom.com Beijing, China. UTC +8 Yannan Han hanyanan raisecom hanyanan@raisecom.com Beijing, China. UTC +8
- Names and affiliations of any other contributors
name | company | 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 |
Tao Shen | China Mobile | shentao@chinamobile.com | Beijing, China. UTC +8 |
Chengli Wang | China Mobile | wangchengli@chinamobile.com | Beijing, China. UTC +8 |
Xin Lu | Huawei | luxin7@huawei.com | XiAn, China, UTC+8 |
Zhong Quan | Huawei | quanzhong@huawei.com | XiAn, China, UTC+8 |
Yaoye Zhang | Huawei | zhangyaoye@huawei.com | Nanjing, China. UTC+8 |
- Project Roles (include RACI chart, if applicable)
...
mailing list tag [vfc]
Committers:
...
Please refer to the table above.
*Link to TSC approval:
Link to approval of additional submitters:
...