/
Success Criteria for HPA Enablement

Success Criteria for HPA Enablement

Owned by Alex Vul (Deactivated)
Last updated: Feb 12, 2019
1 min read



This pages defines the success criteria for implementation of the HPA Functional Requirement. The implementation is deemed to be completed when all the requirements below are satisfied.

  1. Vendor neutrality status:Default 

  2. Consistency of hardware platform capability and/or capability requirements specification

    1. The specification is use case neutral status:Default

    2. The specification follows the format defined by the ETSI NFV Hardware Platform Capability Registry status:Default

    3. For TOSCA described VNFs, the specification is compliant with the ETSI NFV SOL SOL001 data model specification status:Default

    4. There is full equivalence between manual, declarative and imperative means of specification status:UNKNOWN

  3. Consistency of VNF orchestration outcomes (based on HPA requirement based constraints)

    1. The outcome of VNF instantiation is consistent regardless of how a given VNF was instantiated status:UNKNOWN

    2. The outcome of VNF scaling is consistent regardless of how a given VNF was scaled status:Default

    3. The outcome of VNF change management actions is consistent regardless of how VNF change management was performed status:Default

  4. Extensibility/Pluggability

    1. New hardware platform capabilities can be introduced without incurring changes to ONAP components status:Unknown

    2. Specification of existing platform capabilities can be modified or extended without incurring changes to ONAP components status:UNKNOWN

    3. Hardware platform capabilities can be removed without incurring changes to ONAP components status:UNKNOWN

    4. OOF homing and placement constraints, based on hardware platform capability requirements, can be added, modified or removed without incurring changes to ONAP components status:UNKNOWN