Versions Compared

Old Version 1

changes.mady.by.user Chris Donley

Saved on

compared with

New Version 2

changes.mady.by.user Chris Donley

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This is a potential draft of a project proposal template.  It is not final or to be used until the TSC approves it.

Project Name:

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

Project description:

  • Provide high level description of intended project and intended use case(s) and benefit, if needed.

Scope:


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

...