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.

More Information (Intel-specific)...

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.

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.

Participating Companies

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

Terminology Introduced

Term	Definition
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 Enablement	The implementation of HPA awareness in ONAP.

Discussion Pages

Child pages (Children Display)

all	true

Projects that enable HPA

	Project	PTL
1	VNFSDK (impact)	Chris Donley Lianhao Lu (Deactivated)
2	SDC (impact)	Michael Lando
3	SO (impact)	Seshu Kumar Mudiganti
4	AAI (impact)	James Forsyth
5	Multi-Cloud	Former user (Deleted)
6	Policy	Pamela Dragosh
7	OOF	Sarat Puthenpura

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 container based VNF placement is not supported.
5	Specification of capability requirements is bounded by the set of capabilities discovered in #2.
6	Implementation of southbound (Multi-Cloud) facing SO workflows is limited to HEAT only.
7	Use of TOSCA based resource orchestration is a stretch goal.
8	There is no dynamic discozzzvery of HPA capabilities.
9	HPA capabilities are not under monitoring.

Projects that make use of HPA

	Project	PTL	Notes
1	APP-C	Randa Maher	There is no direct impact on APP-C, given that all instantiation actions are "outsourced" to the SO/OOF.
2	VF-C	Yan Yang	Changes to VF-C will be required in order to incorporate use of HPA into instantiation and operation.
3	DCAE	Lusheng Ji

Internal HPA Documentation

	Project	PTL
1	VNFRQTS	Steven wright

External HPA Documentation

	Organization	Contact
1	ETSI NFV SOL	Alex Vul, Intel Thinh, Nokia Bruno Chartras, Orange

Gliffy

border	true

size	1200
name	HPA Enablement Flow Diagram
pagePin	3

Enabled HPA Functionality

Functionality

MVP

Projects Involved

ONAP
ReleaseAvailability

Status

1

Modeling of VNF hardware platform requirements and dependencies as part of the VNFD information model and TOSCA data models.

Yes

Modeling Subcommittee

R2R3

Status


colour	RedGreen
title	R3
title	Delayed

Status

Committed

2

Specification and validation of VNF hardware platform requirements and dependencies as part of the VNF package (TOSCA).

Yes

VNFSDK

R2R3

Status


colour	RedGreen
title	Delayed

Status

title	R3Committed

3

Use of VNFD supplied hardware platform requirements (VNFD) at on-boarding time to verify that infrastructure is capable of supporting VNF instantiation and operation.

No

SDC

R3

Status


colour	RedYellow
title	Delayedstretch

Status


title	R3

4

Translation of VNFD supplied VNF hardware platform requirements (VNFD) into HPA related OOF homing and placement policies.

Yes

SDC, Policy

R2R3

Status


colour	RedGreen
title	R3
title	Delayed

Status

committed

5

Manual specification of HPA related OOF homing and placement policies based on hardware platform requirements (Policy Portal).

Yes

Policy

R2

Status


colour	Green
title	Done

6

Use of VNF hardware platform requirements as constraints constraint policies for optimized homing and resource placement of VNF components during VNF instantiation.

Yes

OOF, SO, Policy

R2

Status


colour	Green
title	Done

7

Use of hardware platform health information telemetry in determination of the VNF instance health.

No

AAI, DCAE

R4

Status


title	scheduled

8

Use of hardware platform telemetry to enhance OOF homing and placement decisions.

No

Multi-Cloud, AAI, OOF

R3

Status


colour	Green
title	R3committed

8

9

Use of VNF hardware platform dependencies as constraints for operation and remediation of running VNF instances.

No

VF-C, APP-C

R3

Status


colour	Red
title	delayed

Status


title	R3r4

9

10

Use of VNF hardware platform dependencies as constraints for VNF autoscaling.

No

Scaling FR

R3

Status


colour	Red
title	delayed

Status


title	R3r4

10

11

Use of VNF hardware platform dependencies as constraints for VNF change management.

No

Change Management FR

R3

Status


colour	Red
title	delayed

Status


title	R3r4

11

12

Discovery of hardware platform capabilities exposed by different VIMs.

Yes

Multi-Cloud

R2

Status


colour	Green
title	Done

12

13

Modeling and persistence of discovered platform capabilities in the AA&I database.

Yes

Multi-Cloud, AAI

R2

Status


colour	Green
title	Done

13

14

SRIOV Discovery.

No

Multi-Cloud

R3

Status


colour	Green
title	R3commited

14

15

SRIOV Day 0 Configuration.

No

TBD

R3

Status


colour	Green
title	R3committed

15

16

VF-C/HPA integration.

No

VF-C

R2/R3

Status


colour	Green
title	R3committed

Test Plan (DRAFT)

Assumptions

VolTE and vCPE use cases will be used to validate the function of HPA end-to-end. The HPA test plans for Casablanca makes make the following assumptions with respect to function of ONAP components affected by HPA enablement functional requirement.

There are no changes to the HPA capability discovery process.
There are no changes to how discovered HPA capabilities are persisted in AAI.
There are no changes to specification of HPA constraint policies used by OOF.
Existing VoLTE and vCPE tests are sufficient to perform the end-to-end HPA testing.

Based on the above assumptions, the scope of the testing effort is limited to the following:

VNF On-Boarding (VNFSDK/SDC)

Test ID

Test Description

Status

101

Format and content of the VNFD, as supplied via the CSAR file are unaffected by VNF on-boarding.

Status

title	To be done

102

HPA requirements are unaffected by VNF on-boarding.

Status

title	To be done

103

On-boarding of VNFs with HPA requirements fails if appropriate ONAP components (e.g. HPA requirement interpreter plugin) are not found.

Status

title	To be done

104

HPA requirement validation errors result in termination of the VNF on-boarding process.

Status

title	To be done

VNF Design (SDC)

Test ID

Test Description

Status

201

VNFs with TOSCA-encoded VNFDs can be used to build network services.

Status

title	To be done

202

VNFD and all of its content, HPA requirements included, remain immutable.

Status

title	To be done

VNF Distribution (SDC/SO/Policy)

Test ID

Test Description

Status

301

Policy and SO components are able to register as SDC distribution clients.

Status

title	To be done

302

VNFD can be distributed through the SDC distribution framework.

Status

title	To be done

303

HPA requirement parsing errors result in termination of the VNF distribution process.

Status

title	To be done

VNF Instantiation (SO/VF-C/OOF)

Test ID

Test Description

Status

401

VNFs with TOSCA-encoded VNFDs can be instantiated using VF-C.

Status

title	To be done

402

VNFs with TOSCA-encoded VNFDs can be instantiated using SO.

Status

title	To be done

403

The same VNF package can be used with all ONAP orchestrators.

Status

title	To be done

404

HPA requirements are consistently interpreted by all orchestrators.

Status

title	To be done

SRIO-V Support

Test ID

Test Description

Status

501

Status

title	To be done

HPA Service Assurance (Platform Telemetry)

Test ID

Test Description

Status

601

Status

title	To be done

Versions Compared

Old Version 96

New Version 97

Key

Business Requirements

Scope

Participating Companies

Terminology Introduced

Discussion Pages

Projects that enable HPA

Limitations

Projects that make use of HPA

External HPA Documentation

Enabled HPA Functionality

Test Plan (DRAFT)

Assumptions

VNF On-Boarding (VNFSDK/SDC)

VNF Design (SDC)

VNF Distribution (SDC/SO/Policy)

VNF Instantiation (SO/VF-C/OOF)

SRIO-V Support

HPA Service Assurance (Platform Telemetry)

Page Comparison

Versions Compared

Old Version 96

New Version 97

Key

Business Requirements

Scope

Participating Companies

Terminology Introduced

Discussion Pages

Projects that enable HPA

Limitations

Projects that make use of HPA

External HPA Documentation

Enabled HPA Functionality

Test Plan (DRAFT)

Assumptions

VNF On-Boarding (VNFSDK/SDC)

VNF Design (SDC)

VNF Distribution (SDC/SO/Policy)

VNF Instantiation (SO/VF-C/OOF)

SRIO-V Support

HPA Service Assurance (Platform Telemetry)