| Gliffy Diagram | ||
|---|---|---|
|
...
Homing Policies and corresponding information required from MultiCloud for Homing in R2:
- HPA capabilities, indirectly, through AAI
- CPU Pinning, NUMA
- required for evaluating HPA constraints
- Min-guarantee capability, indirectly through AAI
- Boolean (Yes/No) for a given cloud instance.
- Aggregate Utilization, directly (through DMaaP
)- CPU, Mem, Network, Disk, etc
- required for evaluating instantaneous/available capacity check constraints
- Aggregate capacity, indirectly (through AAI)
- CPU, Mem, Network, Disk, etc
- Does this fold naturally under the aggregate utilization - when do we actually need aggregate static capacity for decision making ?
...
- Host-level affinity/anti-affinity capability, indirectly through AAIMin-guarantee capability, indirectly through AAI
Open Questions:
- Evaluating constraint combinations:
- Example: consider the following two constraints
- Is there sufficient number of CPUs in the (cloud) cluster ? - (Yes)
- Does the (cloud) cluster support NUMA ? - (Yes)
- But, is there sufficient number of CPUs that support NUMA ? - Maybe not !
- Example: consider the following two constraints
...