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

Compare with Current View Page History

« Previous Version 3 Next »

Project Name:

  • Proposed name for the project: VNF Guidelines and SDK
  • Proposed name for the repository: vnfsdk

Project description:


  • This project will deliver a set of VNF guidelines and automation tools for VNF product specification, packaging, publication and ingestion
  • This project will also deliver a portal and tool for parameter validation, function test, and marketplace for VNF
  • The functionality supplied by this project is intended for use by NFV operators, VNF product developers and VNF product DevOps teams.



Scope:

  • Unified set of VNF Guidelines incorporating those from OPEN-O and ECOMP
  • Data model for VNFs
  • NFV operator tools and SDK for ingestion (download) of VNF products from the VNF marketplace
  • VNF Supplier DevOps tools and SDK for automated packaging and publication of VNF product releases
  • A Network Function Marketplace (NF-MP) for publication, upload and download of VNF products and offerings
  • Tooling necessary to support VNF coherence, environment and dependency checking during packaging, upload and download

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