A&AI Schema
...
ComputeNode, HPACapacity schema
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
<java-type name="ComputeNodes">
<xml-properties>
<xml-property name="description" value="List of ComputeNodes in a CloudRegion"/>
</xml-properties>
<xml-root-element name="compute-nodes"/>
<java-attributes>
<xml-element container-type="java.util.ArrayList" java-attribute="computeNode" name="compute-node" type="inventory.aai.onap.org.v14.ComputeNode"/>
</java-attributes>
</java-type>
<java-type name="ComputeNode">
<xml-root-element name="compute-node"/>
<java-attributes>
<xml-element java-attribute="nodeName" name="node-name" required="true" type="java.lang.String" xml-key="true">
<xml-properties>
<xml-property name="description" value="UUID to uniquely identify a HPA capability"/>
</xml-properties>
</xml-element>
<xml-element java-attribute="resourceVersion" name="resource-version" type="java.lang.String">
<xml-properties>
<xml-property name="description" value="Used for optimistic concurrency. Must be empty on create, valid on update and delete."/>
</xml-properties>
</xml-element>
<xml-element java-attribute="relationshipList" name="relationship-list" type="inventory.aai.onap.org.v14.RelationshipList"/>
<xml-element container-type="java.util.ArrayList" java-attribute="hpaCapacity" name="hpa-capacity" type="inventory.aai.onap.org.v14.HpaCapacity"/>
</java-attributes>
<xml-properties>
<xml-property name="description" value="Represents a Compute Node with HPA capacity information"/>
<xml-property name="indexedProps" value="node-name"/>
<xml-property name="dependentOn" value="cloud-region"/>
<xml-property name="container" value="compute-nodes"/>
</xml-properties>
</java-type>
<java-type name="HpaCapacity">
<xml-root-element name="hpa-capacity"/>
<java-attributes>
<xml-element java-attribute="hpaCapacityKey" name="hpa-capacity-key" required="true" type="java.lang.String" xml-key="true">
<xml-properties>
<xml-property name="description" value="Composite key formed with hpaFeature and append list of hpaFeatureAttributes needed for capacity check"/>
</xml-properties>
</xml-element>
<xml-element java-attribute="hpaCapacityValue" name="hpa-capacity-value" type="java.lang.String">
<xml-properties>
<xml-property name="description" value="JSON string specifying the capacity (total,free), unit and metadata of the specific HPA attribute"/>
</xml-properties>
</xml-element>
<xml-element java-attribute="resourceVersion" name="resource-version" type="java.lang.String">
<xml-properties>
<xml-property name="description" value="Used for optimistic concurrency. Must be empty on create, valid on update and delete."/>
</xml-properties>
</xml-element>
<xml-element java-attribute="relationshipList" name="relationship-list" type="inventory.aai.onap.org.v14.RelationshipList"/>
</java-attributes>
<xml-properties>
<xml-property name="description" value="HPA Capability Feature attributes"/>
<xml-property name="indexedProps" value="hpa-attribute-key"/>
<xml-property name="dependentOn" value="hpa-capability"/>
</xml-properties>
</java-type> |
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Changes Required in OOF HPA constraint
Match Flavor Function (per vnfc)
...
During HPA discovery process, Multicloud will add the necessary metadata for simplifying capacity check.
Refer wiki page: https://wiki.onap.org/display/DW/Policy+Specification+and+Retrieval+for+OOF
Policy | Attributes | hpa-feature | Openstack Mapping | AAI Flavor HPACapability representation (Eg:) | ||||||||||||||||||||||
HPA Basic Capabilities Policy Example | numVirtualCpu virtualMemSize | basicCapabilities | vcpus, ram | hpa-capability-id="b369fd3d-0b15-44e1-81b2-6210efc6dff9", hpa-feature=”basicCapabilities”, architecture=”generic", version=”v1”,
| ||||||||||||||||||||||
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 | hpa-capability-id="f453fd3d-0b15-11w4-81b2-6210efc6dff9", hpa-feature=”pciePassthrough”, architecture=”intel64", version=”v1”,
hpa-capability-id="q236fd3d-0b15-11w4-81b2-6210efc6dff9", hpa-feature=”pciePassthrough”, architecture=”{hw_arch}", version=”v1”,
| ||||||||||||||||||||||
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 The deafult value for small page is 4k, for large page is 2M or 1G(recommended value 2M), for any page, libvirt will firstly to try to find large pages, if failed then will fall back to small pages. so it's suggest do not support any page in current release version | hpa-capability-id="e769fd3d-0b15-77b3-81b2-6210efc6dffa", hpa-feature=”hugePages”, architecture=”generic", version=”v1”,
|