Hardware Platform Enablement In ONAP

Overview

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 requirement is required in support of commercial VNF implementations, that are used as part of vCPE, VoLTE and 5G use cases, and require hardware assisted acceleration. This requirement is also needed by the ONAP Optimization Framework (OOF) project in order to optimize homing and placement of hardware assisted VNFs.

Participating Companies

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

Scope

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

R2 Limitations

1. Specification of VNF's hardware platform capability requirements is limited to TOSCA based VNFD's.
2. Specification of VNF's hardware platform capability requirements using HEAT is not supported.
3. Supported capabilities are limited to the ones discoverable via OpenStack APIs.
4. Use of infrastructure resources for HPA drive placements is limited to virtual machines only.
5. Use of container based VNF placement is not supported.
6. Specification of capability requirements is bounded by the set of capabilities discovered in #2.
7. Implementation of southbound (Multi-Cloud) facing SO workflows is limited to HEAT only. 
8. Use of TOSCA based resource orchestration is a stretch goal.
9. There is no dynamic discovery of HPA capabilities.
10. HPA capabilities are not under monitoring.

Terminology Introduced

Enabled Functionality

1. Modeling of VNF hardware platform requirements and dependencies as part of the VNFD information model and data models.
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

HPA JIRA

• HPA Func. Requirement Board 

• HPA Epics & Stories

key	summary	status	resolution

Loading...

Refresh

Projects That Enables HPA

Projects that document HPA guidelines, use cases, requirements & test cases

`Projects that make use of HPA

Legend:

• N/A
• COMMITTED
• IN PROGRESS
• TBD