Versions Compared

Old Version 8

changes.mady.by.user Alexander Vul

Saved on

compared with

New Version 9

changes.mady.by.user Alexander Vul

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
borderColorRed

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.

AttributeOption 1Option 2Option 3Comments
"ALL"

Alexander Vul

Andy Mayer



All the listed attributes (for simplicity).
vduCpuRequirements

Alexander Vul




Xu Yang: Possible redundant attributes: numVirtualCpu, virtualCpuClock, logicalCpuPinningPolicy, logicalCpuThreadPinningPolicy, computeRequirements

Alexander Vul: the computeRequirements attribute is not HPA related.

Alexander Vul: These are not redundant. If I remember right, they are complementary...

vduMemRequirements

Alexander Vul





vduStorageRequirements

Alexander Vul




logicalNodeAlexander Vul

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?

Alexander Vul: There is a single k/v array holding attributes from three registries... We will optimize this, when registries are created.

nicIoRequirementsAlexander Vul

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?

Alexander 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..

networkInterfaceRequirementsAlexander Vul


logicalNodeDataAlexander Vul