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

Compare with Current View Page History

« Previous Version 4 Next »

  • Brief Project Overview (brief as it should be known)

    • VNFSDK is well known as part of CVC to verify the xNF Package before goes to ONAP or operator system 
      • Compliance Test: such as ETSI compliance check, VNF Requirements compliance check, etc
      • Validation Test: such as the VNF Lifecycle  Management Test , based on different NFVI(e.g. openstack, vmware, k8s)
      • Performance Test
    • VNFSDK also provide the UI(Marketplace) to trigger the test and API to upload/download packages
    • VNFSDK also provide the APIs to trigger the test cases execution
    • VNFSDK aim to deliver  DevOps tools and SDK for automated packaging and publication of VNF product releases for VNF suppliers
    • VNFSDK aim to deliver NFV operator tools and SDK for ingestion (download) of VNF products  for operators

  • New component capabilities for Dublin, i.e. the functional enhancements.

    • No

  • New or modified interfaces

    VNFSDK add more API to enable the external system could get more information from VNFSDK and trigger the corresponding test cases.


  • If they are modified, are the backwards compatible?

    • Yes, Just introducing new interfaces

  • Interface naming (point to an example)

    For example, to get VNFSDK supported testcases:
    /onapapi/vnfsdk-marketplace/v1/vtp/tests
    Download a csar package from marketplace:
    /onapapi/marketplace/v1/csars/{csarId}/files

  • Reference to the interfaces.


  • What are the system limits?

    • Currently, No


  • Involved use cases, architectural capabilities or functional requirements.

    • 5G Usecase 
    • CCVPN Usecase
    • SOL004 (VNF Package Security)



  • No labels