Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 64 Next »

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

HPA JIRA

key summary status resolution
Loading...
Refresh

Projects That Enables HPA


ProjectPTLCommitted for R2MVPHPA EpicsNotes
1

VNFSDK

(impact)

GREEN

Yes

VNFSDK-152 - Getting issue details... STATUS

Creating JIRA stories
2

SDC

(impact)

GREEN

Yes

SDC-985 - Getting issue details... STATUS

SDC-986 - Getting issue details... STATUS

Conditional commitment, based on 2 Intel resources
3SO

GREEN

Yes

SO-390 - Getting issue details... STATUS

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

GREEN

Yes

Pending - Will add an Epic more specific than AAI-466 - Getting issue details... STATUS


5Multi-Cloud

GREEN

Yes

MULTICLOUD-157 - Getting issue details... STATUS


6Policy

GREEN

Yes

POLICY-399 - Getting issue details... STATUS


7OOF

GREEN

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

OPTFRA-33 - Getting issue details... STATUS


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


Project

PTL

Committed for R2

MVPHPA EpicsNotes
1VNFRQTS

GREEN

Yes

VNFRQTS-159 - Getting issue details... STATUS


`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:

  • N/A
  • COMMITTED
  • IN PROGRESS
  • TBD


  • No labels