OpenStack Nova · Aggregate scheduling · Caracal

Aggregate routing — who lands where?

Pick a filter below. Green solid = the boot is allowed there; red dashed = blocked. The matrix gives the exact reason per cell.

Flavor A has extra_spec special-hw=true Image 2 license=linux Flavor B (no extra_spec) Aggregate A special-hw=true hA1 · hA2 Aggregate B (no metadata · allow-all) hB1 · hB2
Flavor ↔ host
Image ↔ host
Project ↔ host
Flavor / Image (traits)
boot ↓   target →Aggregate A (reserved)Aggregate B (allow-all)
Subject A
Subject C
Subject B
allowed (lands here) blocked (rejected) A = subject with the property/trait/tenant   B = without