Page History

...

• 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:

...

• support NS and VNF lifecycle management based on the ONAP tosca and yang data model and workflow
• support integration with multi VNFMs via drivers, which include vendors VNFM and generic VNFM
• support integration with multi VNFs via generic VNFM, which does not provide VNFM function
• support integration with multi VIMS via Multi-VIM, which include the opensource and commercial VIMs
• support microservice architecture and model driven resource orchestration and management

Scope:

     The project scope provides the full intended scope of the

...

VF-C; not just what is intended for the

...

first release.

• 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,
• interface to DCAE and Policy
• interface to A&AI
• interface to SO
• interface to Portal/VID
• interface to Vendor 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

• 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

...