NOTE: This poll closes on Thu March 8th, 2018
...
Examples of the above attributes can be found at https://wiki.onap.org/pages/viewpageattachments.action?pageId=24051740&metadataLink=true, or if you have ETSI account, NFVIFA(18)000162 contribution.
...
| Panel |
|---|
|
Please put your @name in one of the option column for each attribute (or the "ALL" for simplicity) and provide any comments you might have. | Attribute | Option 1 | Option 2 | Option 3 | Comments |
|---|
| "ALL" | | Xu Yang Lingli Deng |
| All the listed attributes (for simplicity). | | vduCpuRequirements | |
|
| Xu Yang: Possible redundant attributes: numVirtualCpu, virtualCpuClock, logicalCpuPinningPolicy, logicalCpuThreadPinningPolicy, computeRequirements Alex Vul: the computeRequirements attribute is not HPA related. Alex Vul: These are not redundant. If I remember right, they are complementary... | | vduMemRequirements | |
| |
| | vduStorageRequirements | |
|
|
| | logicalNode |
|
|
| Xu Yang: Question: In the example document, the logical node requirements are categorized into compute, memory and network categories. But in IFA011, only one logicalNode attribute is defined, what's the mapping here? Alex Vul: There is a single k/v array holding attributes from three registries... We will optimize this, when registries are created. | | nicIoRequirements |
|
|
| Xu Yang: Question: related to the above comment, if the network logical node requirements are specific, should this be a dedicated data type instead of a reference? Alex Vul: Hmm... Need to think about it. As I review both the NFV Profile based spec and the SOL spec, I am finding some oddities.. We may have a mistake or two in how things got modeled.. | | networkInterfaceRequirements | |
|
|
| | logicalNodeData |
|
|
|
|
|