Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

« Previous Version 58 Next »

Project Name:

  • Proposed name for the project: VNF SDK & tooling
  • Proposed name for the repository: vnfsdk

Project description:

    • VNF onboarding is a challenge across the industry because of the lack of a standard format for VNFs.
    • This project will build an ecosystem for ONAP compatible VNFs by:
      • developing tools for vendor CI/CD toolchains
      • developing validation and testing tools

    • It will deliver automation tools for VNF product specification, packaging, publication and ingestion
    • This project will also deliver a tool for: 
      • package validation,
      • lifecycle test (framework)
      • functional test (framework)
      • Reference Repository for VNFs to enable CI/CD without dependency on service provider ingestion [Note: business model out of scope]
    • The functionality supplied by this project is intended for use by NFV operators, VNF product developers and VNF product DevOps teams.


Scope:



yellow dotted lines = VNF SDK scope

green dotted lines = VNF Requirements project [out of scope for VNF SDK]

blue dotted lines = ONAP VNF Validation project  [validation project out of scope; tools will be informed by validation requirements]


  • NFV operator tools and SDK for ingestion (download) of VNF products 
  • VNF Supplier DevOps tools and SDK for automated packaging and publication of VNF product releases
  • A Network Function Repository (NF-RP) for publication, upload and download of VNF products and offerings
  • APIs for external interactions with VNF providers 
  • Tooling necessary to support VNF coherence, environment and dependency checking during packaging, upload and download

Note: This project will be the result of merging all relevant tools from the Open-O VNF SDK, ICE and SDC, and of course further development of the merged entity. 

Architecture Alignment:

  • How does this project fit into the rest of the ONAP Architecture?
    • VNF SDK is one of the functional blocks in the ONAP Architecture supporting VNF packaging
  • What other ONAP projects does this project depend on?
    • This project depends on SDC, SO, Modeling, DCAE, VNF Validation Program, and VNF Requirements
  • How does this align with external standards/specifications?
    • This project aligns with TOSCA and ETSI NFV VNF models
    • HEAT will follow OpenStack specification
  • Are there dependencies with other open source projects?
    • OPEN-O (Mercury release)
    • Robot
    • ARIA (parser)
    • OpenStack

Resources:

Other Information:

  • link to seed code (if applicable)
    • VNF SDK is included in the OPEN-O Mercury release
  • Vendor Neutral
    • This project is vendor neutral and open-sourced under the Apache license from the OPEN-O project
  • Meets Board policy (including IPR)
    • yes

Use the above information to create a key project facts section on your project page

Key Project Facts

Project Name:

  • JIRA project name: vnfsdk
  • JIRA project prefix: vnfsdk

Repo name:

  • org.onap.vnfsdk/guidelines
  • org.onap.vnfsdk/model
  • org.onap.vnfsdk/pkgtools
  • org.onap.vnfsdk/validation
  • org.onap.vnfsdk/lctest
  • org.onap.vnfsdk/functest
  • org.onap.vnfsdk/refrepo
  • org.onap.vnfsdk/compliance

Lifecycle State: incubation
Primary Contact: Chris Donley
Project Lead: Chris Donley
mailing list tag [vnfsdk] 
Committers:




*Link to TSC approval: 
Link to approval of additional submitters: 


  • No labels