Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 5 Next »

Scratch pad for Beijing planning.  Add unprioritized backlog items and user stories here. We will discuss collectively during VNFSDK team meetings.

User Stories

integrate ice tools

standalone validation tool

Backlog Items

Non functional & stability items:

  • Security – authentication/authorization
  • Quary APIs not working, query framework needs to be enhanced
  • DB operates without transactions
  • Enhance error handling, introduce error codes to rest services.
  • Enable swagger
  • Validate csar content using ‘aria’ or configuration instead of the current static way

Functional items:

  • Csar packages are stored on local disk – may be lost – perhaps use volume or DB
  • Enable the ‘life cycle test’ project which currently does nothing
  • Interface with SDC

Carrier Grade Requirements

Security?

VNF Package Basic security Requirements as specified in ETSI GS NFV-SOL004 (a User Story to be created for Beijing)

The VNF package must include a Manifest file (already included in Amsterdam release) with basic security features (artifacts integrity and VNF authenticity) as specified in  ETSI GS NFV-SOL004 containing

  • VNF package meta-data
  • A  list of all artifacts (internal and external) entry’s including

    • Respected path/URI,

    • An algorithm to calculate a digest,

    • A digest result calculated on the content of each artifacts

  • A CMS Signature (using VNF Provider certificate with embedded VNF Provider public key) calculated on all the contents of the Manifest file.




  • No labels