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 4 Next »

Some VNF suppliers make use of the underlying hardware platform capabilities in order to accelerate performance and optimize throughput of their VNF products. In order to ensure proper instantiation and operation of such VNFs, the VNF descriptor (VNFD) is used to describe VNF-specific hardware platform (HPA) capability requirements that will be matched against the capabilities of the underlying hardware infrastructure resources, in order to ensure that appropriate resources are used for instantiation.

Requirement Format

HPA capability requirements are specified using a set of kev/value pair arrays within the VNFD. There are five types of HPA capability requirements that can be specified using the VNFD - CPU, memory, storage, network and NUMA. Each requirement type is specified using a separate key-value pair array. Each entry in the array fully defines a single HPA capability.

The "key" portion of each array entry contains a string specifying a particular HPA capability name. The "value" portion of each array entry is a structured field containing information used to interpret the requested capability configuration.

Array EntryValues
<key>A string specifying the name of a given HPA capability.
<value>A list of key-value pairs describing the configuration value of a given capability, where the key-value pairs are defined as follows

keytypevalue
schema-versionstringA string describing the version the schema to be used for validation and interpretation of the <configuration-value>.
schema-locationstringA URL formatted string describing the location of the schema.
platform-idstringA string describing what hardware platform associated with a given HPA capability. For vendor-neutral HPA capabilities, a value of "generic" is used.
mandatorybooleanA boolean value specifying whether the requested capability is mandatory for for proper operation of the VNF. The value of "true" indicated that a given HPA capability must be present. The value of "false" indicates that the VNF can function with or without the capability.
configuration-valuestringA string describing the configuration value of a given capability, as defined by the schema.


CPU & Memory Requirements


Storage Requirements


NIC Requirements


NUMA Requirements

NUMA HPA requirements are specified using the logical_node property of the tosca.capabilities.nfv.VirtualCompute capability.


  • No labels