there are some gaps between DM defined in TOSCA and the format used from OOF/Multicloud/AAI/Policy perspective.
the high-level TOSCA DM
...
refers to Supported HPA Capability Requirements(DRAFT)
the OOF/MultiCloud/AAI/Policy refer
...
to HPA Policies
...
the black and strikethrough item could be found/matched the hpa-feature-attributes used in currently OOF/Policy/MultiCloud/AAI.
we need think a way to do an alignment.
TOSCA DM | Capability Name |
|---|---|
VDU CPU Requirements | cpuModelSpecificationBinding simultaneousMultiThreading hypervisorConfiguration computeRas cpuModel directIoAccessToCache accelerator measuredLaunchEnvironment secureEnclave
|
VDU Memory Requirements | attributeReference schemaVersion schemaSelector numberOfPages memoryAllocationPolicy memoryType memorySpeed memoryRas memoryBandwidth processorCacheAllocationType processorCacheAllocationSize |
VDU Storage Requirements | storageIops storageResilencyMechanism |
Logical Node Compute Requirements | numberCpu |
Logical Node Memory Requirements | localNumaMemorySize |
Logical Node i/O Requirements |
pciAddress pciDeviceLocalToNumaNode |
Network Interface Requirements | nicFeature interfaceType vendorSpecificNicFeature |
Hpa-feature-Attributes | hpa-feature(Group) |
|---|---|
numCpuSockets numCpuCores numCpuThreads |
...
cpuTopology | |
virtualMemSize | basicCapabilities |
| ovsDpdk |
| cpuPinning |
numaNodes numaCpu-N numaMem-N | numa |
pciCount
functionType | pciePassthrough |
diskSize ephemeralDiskSize swapMemSize | localStorage |
| instructionSetExtensions |
| hugePages |
...