Versions Compared

Key

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

...

Purpose:

Introduction

HPA feature (using OOF) ensures that the VNF instances are placed in cloud regions that have platform capabilities as expected by VNF workloads. For example, if a VNF workload requires XYZ vendor SRIOV-NIC and ABC vendor crypto accelerator,  HPA feature of ONAP will ensure that the VNF is placed in a cloud region that have compute nodes with XYZ SRIOV-NIC card and ABC vendor Crypto accelerator card.

History:

Beijing release:

  • Policy based HPA was introduced. 

Casablanca release:

  • Model driven HPA was introduced (TOSCA based).  With this, both SO and VFC based use cases can leverage HPA based placement feature.
  • Use cases:
    • vFW with HPA
    • vCPE-TOSCA with HPA

Dublin release:

Main focus is to harden HPA feature, make it easily deployable, create literature and create easy-to-replicate demos.

Also, fix any gaps and bugs that are discovered during hardening and testing.

Our aspiration is also to make existing use cases always leverage HPA functionality as part of integration testing. 

Stretch goal: is to support multiple choices in specifying a feature requirement in policies.

Owner :  Alex Vul

Participating Companies: Intel, VMware

Use Case Name

Showcase VNF

Test Environment

Integration Team Liaison

vFW, vDNSIntel/Windriver Lab, VMware Lab (TBD)
vCPE with TOSCAChina Mobile Lab


Dublin focus

  • Ready with right setup  Intel/WR lab
    • Have few compute nodes with right HW
    • Ensure to have SRIOV-NIC cards
    • Ensure to have crypto accelerator cards (QAT)
  • Usage of CLI only - Work with the teams to avoid any curl commands, update of DB entries, kubectl exec & configuration files.
  • Work on some of the gaps identified in Casablanca (Issues listed here: HPA Hardening Issues)
  • New vIPSEC sample VNF : Create a new sample VNF (IPSEC VNF) for them to leverage crypto accelerator cards.
    • Start with traditional Ubuntu with QAT driver installed.
  • Create new test cases with various HPA features assigned to VNFs.  Few example:
    • vFW with dedicated cores, SRIOV-NIC VF, Huge pages
    • vIPSEC with QAT
    • vIPSEC with AES-NI
  • Work with Integration team to add the test cases in integration project.
  • Work with demo repository owners to introduce new sample VNFs and add new HEAT/ENV files for existing use cases

HPA Automation JIRA Issues 

PROJECTJIRA EPIC/ USER STORIES/ BUGS
CLI

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-130

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-131

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-132

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-133

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-134

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-135

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

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-137

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-138

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-139

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-140

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-141

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-142

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-143

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-144

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-145

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-148

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-149

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-150

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-151

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

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-153

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-154

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-156

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLI-158

Optimization Framework

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

Integration

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-792

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-794

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-795

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-904

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-905

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-793