...
- Cloud Affinity
- Location of cloud-regions (same as above)
- [Ethan] If it’s the same as above, this do not fall into the scope of MultiCloud.
- [Bin] The location information is coming along with complex which is populated by robot script in In Release 1. ESR might be able to help since complex belongs to external system information logically.
- HPA capabilities, indirectly, through AAI
- CPU Pinning, NUMA as key value pairs
Example: cloud-region-id: {CPU Pinning: True, NUMA: False, Large Pages: True}
- required for evaluating HPA constraints
- Is this provided by MultiCloud during VIM registration
- [Ethan] Yes, When a new VIM was registered through ESR portal, ESR will call MultiCloud to update VIM informations like networks or images in A&AI, we could populate HPA during register in R2 release. What kind of HPA features that might need in R2?
- [Shankar] The exact HPA attributes relevant in R2 is still being determined. That said, it is most likely to be a list of attributes that are associated with a cloud-instance in AAI. Does that sound a reasonable way to capture capabilities ?
- [Ethan] About HPA, using a list [hpa1, hpa2] sounds not good to me since it will make filtering harder, I would prefer a map {hpa1: true, hpa2: false}.
- [Shankar] A map works just fine from an OOF perspective. However, I wonder when a HPA:false check will need to be performed
- Min-guarantee capability, indirectly through AAI
- Boolean (Yes/No) for a given cloud instance.
- This can be treated similar to other capabilities (as a key value pair)
- Example: cloud-region: {min-guarantee: True}
- [Ethan] Does software configuration attribute exist in A&AI schema now?
- [Shankar] This is very similar to the HPA attributes except that these are more general attributes (as compared to hardware specific attributes).
- Available Capacity, directly, through MultiCloud
- CPU, Mem, Network, Disk, etc
...