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

Compare with Current View Page History

« Previous Version 2 Next »

Overview

This page is intended to capture discussions and work relating to the longer term strategy and direction of testing within the LFN programs.

Testing Scopes

Note, the following is a work in progress.

VNF Testing

  • Compliance:

    • Conformance to HEAT or TOSCA Templates, as defined by ONAP Requirements.

    • Conformance to ONAP VNFRqmts documentation which will integrate other SDO requirements (ie, 5G, BBF, ETSI,...)
    • Documentation of VNF is available.

  • Validation:

    • On-boarding: Validate the VNF Artifact(s) is able to be "consumed" by an ONAP instance.

      • Open questions: 1) What are the requirements defined for "On-boarding?" What is the requirement for the "ONAP instance?" 3) Is there a requirement for backwards compatibility? 4) Besides ONAP are there other organizations defining this?

    • Instantiation: Validate the VNF can be "launched" by an ONAP instance on top of an NFVI.

      • Open questions: 1) What is the requirements for ONAP Instance? 2) What is the requirements for the NFVI? 3) What are the requirements for the "VNF launch?"

    • Validate various life-cycle operations are possible with the VNF running on the ONAP Instance.

      • Open questions: 1) What the required "life-cycle operations?" 2) What the requirements for each "operation?" 3) What are the requirements for the "ONAP instance?"

      • Life Cycle Operations my version of FCAPS:
        • Fault Management
        • Capacity Management
        • Billing/Accounting Management
        • Performance Management
        • Security Management 
  • Performance:

    • Capacity:

    • Stability:

  • Security:

    • Open question: Where do these requirements come from? Who is responsible for the test cases?

NFVI Testing

  • Compliance:

  • Validation:

  • Performance:

Related Attachments and Presentations

No files shared here yet.

  • No labels