Versions Compared

Old Version 13

changes.mady.by.user Alexander Vul

Saved on

compared with

New Version 14

changes.mady.by.user Alexander Vul

Saved on

Key

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

Table of Contents

This is page is being used to track the realization of the Hardware Platform Awareness (HPA) functional requirement defined in support of VoLTE, vCPE and 5G use cases. The requirement calls for enablement of hardware platform feature awareness (HPA) inside the ONAP management platform, or means by which knowledge about underlying compute hardware platform capabilities is exposed to VNFs running on top of the platform  in order to optimize, accelerate and/or otherwise augment their execution. In ONAP, HPA enablement focuses on discovery, health monitoring and configuration of hardware platform capabilities within the NFV infrastructure, and their consumption by the virtual network functions and network services deployed on top of the infrastructure.

Business Requirements

This functionality is required in support of commercial VNF implementations that are used as part of vCPE, VoLTE and 5G use cases.

Participating Companies

  • AT&T, Intel, Cloudify, China Mobile, Orange, ARM

Scope

The scope of this initiative is to enable consumption of hardware platform capabilities for the purpose of VNF performance acceleration and optimization. Other uses of HPA are not in scope. 

Provided Functionality

  1. Modeling of VNF hardware platform requirements and dependencies as part of the VNFD information model.
  2. Specification of VNF hardware platform requirements and dependencies as part of the VNF template (TOSCA).
  3. Use of VNF hardware platform dependencies at on-boarding time to verify that infrastructure is capable of supporting VNF instantiation and operation.
  4. Use of VNF hardware platform dependencies as constraints for optimized homing and resource placement of VNF components during VNF instantiation.
  5. Use of hardware platform health information in determination of the VNF instance health.
  6. Use of VNF hardware platform dependencies as constraints for operation and remediation of running VNF instances.
  7. Discovery of hardware platform capabilities exposed by different VIMs.
  8. Modeling and persistence of discovered platform capabilities in the AA&I database.

Discussion Pages

Children Display