Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This proposal does not require changes to the ONAP architecture and makes use of the existing ONAP management components. The following diagram identifies the ONAP components affected by this project:

Image AddedImage Added

Image Added

Image Added

Image Added

ONAP Project Dependencies


Project

Dependencies

VNFSDK

Specification of VNF hardware platform requirements and dependencies as part of the VNF descriptor.

SDC

Infrastructure validation during VNF on-boarding, based on ingested VNF hardware dependencies. Propagation of ingested VNF hardware platform dependencies.

POLICY

Definition of HPA centric constraint policies as they apply to VNF instantiation, VNF resource optimization and VNF instance operation.

SO

Use of hardware platform requirements as input into the resource homing and optimization process.

OOF

Use of hardware platform requirements as constraints for VNF component homing and resource placement.

DCAEUse of hardware platform telemetry in determination of network service and VNF instance health.
APP-CUse of hardware platform requirements as constraints for VNF instance operation and remediation.
VF-CUse of hardware platform requirements as constraints for VNF instance operation and remediation.
AAIModeling and persistence of hardware platform capabilities as part of the inventory information.
Multi-VIMDynamic discovery of hardware platform capabilities during VIM on-boafding and operation.

Alignment with external standards and specifications

This project is dependent on use of the folliowing information and data model specifications:

  • ETSI NFV IFA011 v2.3.1 - VNFD Information Model
  • ETSI NFV SOL001  - VNFD TOSCA Data Model
  • OASIS TOSCA SImple YAML Profile v1.2
  • OASIS TOSCA NFV Profile (WD5)

Dependencies on other open source projects

None.