...
Hardware Platform Capability Requirements
HPA Hardware platform capabiity requirements describe VNF component-specific dependencies on the underlying hardware platform capabilities. HPA Capability requirements are specified as part of the VNF descriptor (VNFD) templates, created during VNF packaging and containing all information needed for initial instantiation and subsequent operation of a given VNF. HPA Capability requirements are expressed as arrays of tuples, where each tuple fully defines a single HPA requirement.
Each requirement tuple has the following format:
(<version-spec>, <hardware-architecture>, <capability-name>, <capability-value>, <need-level>)where the tuple elements are defined as follows:
<version>A unique quote delimited string identifier representing the version of the tuple format. | string | The tuple schema version | ||
<hardware-architecture>A unique quote delimited string identifier representing the | string | The hardware platform architecture identifier associated with the a given capability. A value of "*" (star) indicates that the given capability is hardware vendor agnostic.<requirementindicated a normative capability applicable to all hardware platforms. | ||
<capability-name> | A unique quote delimited string identifier representing the name of the capability. | <requirementstring | The capability name. | |
<capability-value> | A unique quote delimited string identifier representing the value/settings of the capabiity. | <need-level> | A quote delimited string constant stating whether the string | The capability value. May be a single value. |
<requirement-level> | enum | Indicates whether a given capability is mandatory or optional. Has one of two possible values - "mandatory" or "optional". |
...
Hardware Platform Capabilities
HPA Hardware platform capabilities describe the underlying compute, storage and network hardware platform capabilities. HPA Platform capabilities are obtained from each on-boarded VIM and are persisted as part of the AAI inventory database. HPA Platform capabilities are expressed as arrays of tuples, where each tuple fully defines a single HPA capability.
Each requirement tuple has the following format:
(<version-spec>, <hardware-architecture>, <capability-name>, <capability-value>)where the tuple elements are defined as follows:
<version> |
| string | The tuple schema version. |
<hardware-architecture> |
| string | The hardware platform architecture identifier associated with |
| a given capability. A value of "*" |
| indicated a normative capability applicable to all hardware platforms. |
<capability-name> |
| string | The capability name. |
<capability-value> |
| string | The capability value. |
Requirement/Capability Matchmaking
...