You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

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 resourced 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.
  • Specify any interface/API specification proposed,
    • interface to DCAE and Policy
    • interface to A&AI
    • interface to SO
    • interface to VNFM
  • Identity a list of features and functionality will be developed.
  • Identify what is in or out of scope. During the development phase, it helps reduce discussion.

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?
  • How does this align with external standards/specifications?
    • APIs/Interfaces
    • Information/data models
  • Are there dependencies with other open source projects?
    • APIs/Interfaces
    • Integration Testing
    • etc.

Resources:

  • Primary Contact Person
  • Names, gerrit IDs, and company affiliations of the committers
  • Names and affiliations of any other contributors
  • Project Roles (include RACI chart, if applicable)

Other Information:

  • link to seed code (if applicable)
  • 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: 

  • No labels