Page Comparison

...

• 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.
• Specify any interface/API specification proposed,
• Provide interfaces to 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

• Use Case: VoLTE (vIMS + vEPC) 
• VNF onboarding
• Network service deployment automation
• Network service termination automation
• Framework for integration with vendor provided VNFM

...

• Primary Contact Person
  Lingli Deng (denglingli@chinamobile.com)

• Names, gerrit IDs, and company affiliations of the committers

  Lingli Deng	China Mobile	denglingli@chinamobile.com	Beijing, China. UTC +8
  Maopeng Zhang	ZTE	zhang.maopeng1@zte.com.cn	Nanjing, China. UTC +8
  Kanagaraj Manickam	Huawei	kanagaraj.manickam@huawei.com	India. UTC +5:30
  Jinhua Fu	ZTE	fu.jinhua@zte.com.cn	Nanjing, China. UTC +8
  Yan   Yang	China Mobile	yangyanyjy@chinamobile.com	Beijing, China. UTC +8
  Victor Gao	Huawei	victor.gao@huawei.com	Shenzhen, China. UTC +8
  Anatoly Andrianov	Nokia	anatoly.andrianov@nokia.com	Chicago, U.S. CST
  Nagesha Subramanya	Nokia	nagesha.subramanya@nokia.com	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

• Project Roles (include RACI chart, if applicable)

...