1. Enhanced Platform Awareness (EPA) Alex Vul Intel Corporation
Date , 2017

2. What is EPA?
Provides awareness of underlying compute hardware platform capabilities to software running on the hardware platform
Provides means platform capability discovery, data collection and consumption
Used to optimize, accelerate or otherwise augment platform software execution

3. Why EPA?
Attract a largest possible ecosystem of commercial VNF suppliers to ONAP, including those who use HW platform features to accelerate and to optimize the performance and throughput of their VNFs
Enable EPA in existing ONAP use cases and all future use cases…
Support S3P
Supporting Companies – AT&T, Intel, Cloudify

4. Use within ONAP
In ONAP, EPA is used to optimize and accelerate virtual network function performance and throughput…
Performance
Get to end-to-end line rate throughput and low latency
Deterministic workload performance
Security
Place workloads on security-enabled HW (e.g. TXT)
Optimal security performance (e.g. SSL de/encrypt)
Service Assurance
Telemetry integration to determine post-deployment workload performance
To be utilized by 5G, vCPE and VoLTE use cases
Addresses S3P needs and enables future use cases (5G)
Scope – for use by VNFs only, other uses not supported

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

6. EPA Related ONAP Projects
Closed-loop Automation
Multi-VIM Abstraction Layer
OpenStack
WindRiver
VMware VIO
Azure
Kubernetes
AA&I (Inventory) DB
OOF
APPC (Controller)
POLICY (Policy Framework)
CLAMP (CL Policy Editor)
SO (Service Orchestration)
DCAE
(Monitoring)
Catalog
(Service Catalog)
SDC (Service Designer)
VNF Suppliers
Contain hardware platform requirements
VNF Packages (CSAR Files)
EPA-centric policies for VNF placement and operation
VNF packages are ingested and on-boarded
EPA driven optimization of compute and storage resource allocation
Discovery of hardware platform capabilities
Discovered hardware capabilities are stored in the inventory DB PE
Policy
Enforcement

7. ONAP Component Impact Summary
POLICY
Definition of EPA centric constraint policies as they apply to VNF instantiation, VNF resource optimization and VNF instance operation.
Multi-VIM
Dynamic discovery of hardware platform capabilities during VIM on-boafding and operation.
SDC
Infrastructure validation during VNF on-boarding, based on ingested VNF hardware dependencies. Propagation of ingested VNF hardware platform dependencies.
AAI
Modeling and persistence of hardware platform capabilities as part of the inventory information.
VNFSDK
Specification of VNF hardware platform requirements and dependencies as part of the VNF descriptor.
OOF
Use of hardware platform requirements as constraints for VNF component homing and resource placement.
APP-C
Use of hardware platform requirements as constraints for VNF instance operation and remediation.
VF-C SO
Use of hardware platform requirements as input into the resource homing and optimization process.
DCAE
Use of hardware platform telemetry in determination of network service and VNF instance health.