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" | | |
| All the listed attributes (for simplicity). Brian Hedstrom: The link provided above for Key-Value Pair Registries.docx, for the HPA Key Value Pairs, is linking to an OLD version of the file. The vduComputeRequirements Registry Example provided in the link above DOES NOT MATCH the vduComputeRequirements Registry Example provided in NFVIFA(18)000162r1. It's not clear to me if we are voting on the attributes only in this attribute table, or also voting on supporting the key value pairs per NFVIFA(18)000162r1. I would suggest the key value pairs be a separate poll/discussion. My vote here is for the attribute table only. Xu Yang: to Brian, the vote is only for the attribute table, not the key value pairs.
maopeng zhang: I agree HPA requirements. - All changes for HPA in R2 should be not effect R1 VoLTE case. It needs the data model compatible, which the VoLTE case already used.
If this can be pre-condition in R2, I agree with add HPA attributes. But how to add, we needs more details.
- please make it clear that add cloumn for OPT2, what attributes to be removed and how to removed(remove from KVP or remove from attributes existed in the clean page)
Depend on the clear and furthur more details, I can decide whether to support the remove option.
| | vduCpuRequirements | |
|
| Xu Yang: Possible redundant attributes: numVirtualCpu, virtualCpuClock, logicalCpuPinningPolicy, logicalCpuThreadPinningPolicy Alex Vul: the computeRequirements attribute is not HPA related. Xu Yang: remove computeRequirements
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. Brian Hedstrom Is logicalNode and logicalNodeDescr the same attribute? I'm finding both in the Wiki. logicalNode is not listed as an attribute for Class: VirtualComputeDesc | | 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.. Brian Hedstrom nicloRequirements is not listed as an attribute (or data type for other attribute) for Class: VirtualNetworkInterfaceRequirements | | networkInterfaceRequirements | |
|
|
| | logicalNodeData |
|
|
| Brian Hedstrom This appears to be a Class, not an attribute. |
|