Versions Compared

Key

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

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. 

Terminology Introduced

TermDefinition
Hardware Platform Awareness (HPA)The means by which the underlying NFV-I hardware platform capabilities are exposed to the network service orchestration and management functionality, for the purpose of fulfilling VNF instantiation-time hardware platform requirements.
HPA EnablementThe implementation of HPA awareness in ONAP.


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

Child pages (Children Display)
alltrue

HPA JIRA

Jira Legacy
serverSystem Jira
columnskey,summary,status,resolution
maximumIssues1000
jqlQueryfilter = HPA_Filter ORDER BY project ASC
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

Projects That Enables HPA


ProjectPTLCommitted for R2MVPHPA EpicsNotes
1

VNFSDK

(impact)

Status
colourGreen

Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVNFSDK-152

Creating JIRA stories
2

SDC

(impact)

Status
colourGreen

Yes

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-985

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-986

Conditional commitment, based on 2 Intel resources
3SO

Status
colourGreen

Yes

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-390

Conditional commitment, based on 2 Intel resources
4AAI
(impact) 

Status
colourGreen

Yes

Pending - Will add an Epic more specific than

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-466


5Multi-Cloud

Status
colourGreen

Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMULTICLOUD-157


6Policy

Status
colourGreen

Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-399


7OOF

Status
colourGreen

Depends on availability of HPA requirement (VNFD) and HPA capability (AAI) information.

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOPTFRA-33


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


Project

PTL

Committed for R2

MVPHPA EpicsNotes
1VNFRQTS

Status
colourGreen

Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVNFRQTS-159


`Projects that make use of HPA


Project

PTL

Notes
1APP-CThere is no direct impact on APP-C, given that all instantiation actions are "outsourced" to the SO/OOF.
2VF-CChanges to VF-C will be required in order to incorporate use of HPA into instantiation and operation.
3DCAE

Legend:

  • Status
    titleN/A
  • Status
    colourGreen
    titleCommiTTED
  • Status
    colourYellow
    titleIn Progress
  • Status
    colourRed
    titleTBD