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

Compare with Current View Page History

« Previous Version 11 Next »

Refer wiki page: https://wiki.onap.org/display/DW/Policy+Specification+and+Retrieval+for+OOF

Policy

Attributes

hpaFeature

Openstack Mapping

AAI representation (Eg:)

HPA CPU Topology Policy Example

numCpuSockets

numCpuCores

numCpuThreads

cpuTopology

hw:cpu_sockets, hw:cpu_cores, hw:cpu_threads,

hpaCapabiltyId="a369fd3d-0b15-44e1-81b2-6210efc6dff8",

hpaFeature=”cpuTopology”,

hardwareArchitecture=”generic",

version=”v1”,

HPAAttributeKey

HPAAttributeValue

numCpuSockets

{value:4}

numCpuCores

{value:4}

numCpuThreads

{value:8}

HPA Basic Capabilities Policy Example

numVirtualCpu

virtualMemSize

basicCapabilities

vcpus,

ram

hpaCapabiltyId="b369fd3d-0b15-44e1-81b2-6210efc6dff9",

hpaFeature=”basicCapabilities”,

hardwareArchitecture=”generic",

version=”v1”,

HPAAttributeKey

HPAAttributeValue

numVirtualCpu

{value:4}

virtualMemSize

{value:4, unit:”GB”}

HPA OVS DPDK Policy Example

dataProcessingAccelerationLibrary

ovsDpdk


hpaCapabiltyId="b369fd3d-0b15-44e1-81b2-6210efc6dffa",

hpaFeature=”ovsDpdk”,

hardwareArchitecture=”Inte64",

version=”v1”,

HPAAttributeKey

HPAAttributeValue

dataProcessingAccelerationLibrary

{value:”v12.1”}

“HPA CPU Pinning Policy Example

logicalCpuThreadPinningPolicy

logicalCpuPinningPolicy

cpuPinning

hw:cpu_thread_policy

hw:cpu_policy

hpaCapabiltyId="c369fd3d-0b15-44e1-81b2-6210efc6dffa",

hpaFeature=”cpuPinning”,

hardwareArchitecture=”generic",

version=”v1”,

HPAAttributeKey

HPAAttributeValue

logicalCpuThreadPinningPolicy

{value:”prefer”}

logicalCpuPinningPolicy

{value:”dedicated”}

HPA NUMA Policy Example

numaNodes

numaCpu-N

numaMem-N

numa

hw:numa_nodes

hw:numa_cpus:N

hw:numa_mem:N

hpaCapabiltyId="c369fd3d-0b15-44e1-81b2-6210efc6dffa",

hpaFeature=”numa”,

hardwareArchitecture=”generic",

version=”v1”,

HPAAttributeKey

HPAAttributeValue

numaNodes

{value:2}

numaCpu-0

{value:[0,1]}

numaCpu-1

{value:[2,3,4,5]}

numaMem-0

{value:2, unit:”GB”}

numaMem-1

{value:4, unit:”GB”}






HPA PCIe Passthrough Policy Example

pciCount

pciVendorId

pciDeviceId

pciePassthrough

pci_passthrough:alias=ALIAS:COUNT

Openstack administrator is expected to create ALIAS as

<name>-<PCIe vendor ID in Hex>-<PCIe device ID>

QuickAssist example: "mycrypto-8086-0443"


In case of SRIOV-NIC:

aggregate_instance_extra_specs:sriov-device-<name>="<Vendor ID>-<Device ID>"

It is expected that Openstack administrator creates host aggregate and metadata 'sriov-device-<name>' .

Example: Assume that there are two SRIOV-NIC cards supported by a region, Intel and Mellanox.

Examples:

sriov-device-intel=8086-1563

sriov-device-mellanox=15B3-1003



hpaCapabiltyId="f453fd3d-0b15-11w4-81b2-6210efc6dff9",

hpaFeature=”pciePassthrough”,

hardwareArchitecture=”intel64",

version=”v1”,

HPAAttributeKey

HPAAttributeValue

pciCount

{value: 1}

pciVendorId

{value: "8086"}

pciDeviceId{value: "0443"}


hpaCapabiltyId="q236fd3d-0b15-11w4-81b2-6210efc6dff9",

hpaFeature=”pciePassthrough”,

hardwareArchitecture=”{hw_arch}",

version=”v1”,

HPAAttributeKey

HPAAttributeValue

pciCount

{value: 1}

pciVendorId

{value: "15B3"}

pciDeviceId{value: "1003"}


HPA Local Storage Policy Example

diskSize

ephemeralDiskSize

swapMemSize

localStorage

disk

swap


hpaCapabiltyId="u456fd3d-0b15-90r4-81b2-6210efc6dff9",

hpaFeature=”localStorage”,

hardwareArchitecture=”generic",

version=”v1”,

HPAAttributeKey

HPAAttributeValue

diskSize

{value:4096, unit:”GB”}

ephemeralDiskSize

{value:160, unit:”GB”}

swapMemSize{value:8192, unit:”MB”}


HPA CPU Instruction Set Extensions Policy Example

instructionSetExtensions

instructionSetExtensions

hw:capabilities:cpu_info:features

hpaCapabiltyId="c369fd3d-0b15-44e1-81b2-6210efc6dffa",

hpaFeature=”instructionSetExtensions”,

hardwareArchitecture=”Intel64",

version=”v1”,

HPAAttributeKey

HPAAttributeValue

instructionSetExtensions

{value:["AAA", "BBB"]}

HPA Huge Pages Policy Example

memoryPageSize

hugePages

hw:mem_page_size

values can be ANY, 4KB, 2MB, 1GB

How to handle large, small, any from openstack?

if the hw:mem_page_size is an integer it is assumed the unit is in KB

hpaCapabiltyId="e769fd3d-0b15-77b3-81b2-6210efc6dffa",

hpaFeature=”hugePages”,

hardwareArchitecture=”generic",

version=”v1”,

HPAAttributeKey

HPAAttributeValue

memoryPageSize

{value:2, unit:”MB”}

  • No labels