master
stable/victoria
stable/yoga
stable/wallaby
stable/xena
stable/zed
stable/2023.1
stable/train
stable/ussuri
27.1.0
26.2.0
25.2.0
26.1.1
25.1.1
xena-em
24.2.1
27.0.0
27.0.0.0rc1
26.1.0
25.1.0
24.2.0
stein-eol
rocky-eol
queens-eol
wallaby-em
23.2.2
26.0.0
26.0.0.0rc2
26.0.0.0rc1
pike-eol
24.1.1
23.2.1
25.0.1
victoria-em
25.0.0
25.0.0.0rc1
24.1.0
23.2.0
22.4.0
ussuri-em
21.2.4
21.2.3
23.1.0
22.3.0
24.0.0
24.0.0.0rc2
24.0.0.0rc1
21.2.2
22.2.2
23.0.2
ocata-eol
train-em
20.6.1
22.2.1
23.0.1
21.2.1
23.0.0
23.0.0.0rc2
23.0.0.0rc1
20.6.0
22.2.0
21.2.0
21.1.2
22.1.0
20.5.0
stein-em
22.0.1
20.4.1
19.3.2
21.1.1
22.0.0
22.0.0.0rc1
19.3.1
20.4.0
21.1.0
19.3.0
20.3.0
21.0.0
21.0.0.0rc2
19.2.0
21.0.0.0rc1
20.2.0
rocky-em
18.3.0
20.1.1
19.1.0
20.1.0
20.0.1
queens-em
17.0.13
20.0.0
18.2.3
20.0.0.0rc2
19.0.3
20.0.0.0rc1
17.0.12
18.2.2
19.0.2
17.0.11
18.2.1
19.0.1
pike-em
16.1.8
19.0.0
19.0.0.0rc2
18.2.0
17.0.10
19.0.0.0rc1
17.0.9
16.1.7
17.0.8
18.1.0
18.0.3
ocata-em
17.0.7
15.1.5
16.1.6
18.0.2
15.1.4
18.0.1
17.0.6
16.1.5
18.0.0
18.0.0.0rc3
18.0.0.0rc2
18.0.0.0rc1
18.0.0.0b3
15.1.3
18.0.0.0b2
16.1.4
17.0.5
15.1.2
16.1.3
17.0.4
15.1.1
17.0.3
16.1.2
18.0.0.0b1
16.1.1
17.0.2
17.0.1
17.0.0
17.0.0.0rc3
2011.1
2010.1
17.0.0.0rc2
16.1.0
17.0.0.0rc1
newton-eol
17.0.0.0b3
14.1.0
15.1.0
16.0.4
17.0.0.0b2
14.0.10
16.0.3
15.0.8
14.0.9
16.0.2
17.0.0.0b1
16.0.1
16.0.0
14.0.8
16.0.0.0rc2
15.0.7
16.0.0.0rc1
16.0.0.0b3
mitaka-eol
15.0.6
16.0.0.0b2
14.0.7
15.0.5
14.0.6
15.0.4
16.0.0.0b1
15.0.3
15.0.2
14.0.5
13.1.4
15.0.1
13.1.3
14.0.4
15.0.0
15.0.0.0rc2
15.0.0.0rc1
15.0.0.0b3
14.0.3
15.0.0.0b2
liberty-eol
12.0.6
15.0.0.0b1
14.0.2
14.0.1
13.1.2
14.0.0
12.0.5
14.0.0.0rc2
14.0.0.0rc1
14.0.0.0b3
13.1.1
14.0.0.0b2
13.1.0
12.0.4
14.0.0.0b1
kilo-eol
2015.1.4
12.0.3
13.0.0
13.0.0.0rc3
13.0.0.0rc2
13.0.0.0rc1
12.0.2
13.0.0.0b3
2015.1.3
13.0.0.0b2
12.0.1
juno-eol
13.0.0.0b1
2014.2.4
12.0.0
12.0.0.0rc3
2015.1.2
12.0.0.0rc2
12.0.0.0rc1
12.0.0.0b3
2015.1.1
12.0.0.0b2
icehouse-eol
12.0.0.0b1
2014.1.5
12.0.0a0
2015.1.0
2015.1.0rc3
2015.1.0rc2
2015.1.0rc1
2014.2.3
2015.1.0b3
2014.1.4
2015.1.0b2
2014.2.2
2015.1.0b1
2014.2.1
2014.2
2014.2.rc2
2014.1.3
2014.2.rc1
havana-eol
2013.2.4
2014.2.b3
2014.1.2
2014.2.b2
2014.2.b1
2014.1.1
2014.1
2014.1.rc2
2013.2.3
2014.1.rc1
grizzly-eol
2013.1.5
2014.1.b3
2013.2.2
2014.1.b2
2013.2.1
2014.1.b1
folsom-eol
2013.1.4
2013.2
2013.2.rc2
2013.2.rc1
2013.2.b3
2013.1.3
2013.2.b2
2013.1.2
2013.2.b1
2013.1.1
essex-eol
diablo-eol
2012.2.4
2013.1
2013.1.rc2
2013.1.rc1
2013.1.g3
2012.2.3
grizzly-2
2012.2.2
2012.2.1
grizzly-1
2012.1.3
2012.2
folsom-rc3
folsom-rc2
folsom-rc1
folsom-3
2012.1.2
folsom-2
2012.1.1
folsom-1
2012.1
essex-rc4
essex-rc3
essex-rc2
essex-rc1
0.9.0
2011.1rc1
2011.2
2011.2gamma1
2011.2rc1
2011.3
2011.3.1
diablo-1
diablo-2
diablo-3
diablo-4
essex-1
essex-2
essex-3
essex-4
${ noResults }
2 Commits (master)
Author | SHA1 | Message | Date |
---|---|---|---|
![]() |
e66443770d |
Per aggregate scheduling weight
This spec proposes to add ability to allow users to use ``Aggregate``'s ``metadata`` to override the global config options for weights to achieve more fine-grained control over resource weights. blueprint: per-aggregate-scheduling-weight Change-Id: I6e15c6507d037ffe263a460441858ed454b02504 |
4 years ago |
![]() |
ec74cc688e |
Add PCIWeigher
Take three hosts, one with a single PCI device, one with many PCI devices, and one with no PCI devices. Nova should prioritise these differently based on the demands of the instance. If the instance requests a single PCI device, then the first of the hosts should be preferred. Similarly, if the instance requests multiple PCI devices, then the second of these hosts would be preferred. Finally, if the instance does not request a PCI device, then the last of these hosts should be preferred. While the first and second of these cases is already somewhat handled by the NUMA topology filter (which will ensure the correct number and type of PCI devices are available on the hosts), there is nothing to stop a instance that *does not* require PCI devices from occupying space on one of the few hosts that *does* have free PCI devices. The PCIWeigher is designed to keep hosts with PCI device(s) as free as possible, to best ensure they can satisfy requests from instances with PCI requirements when called upon. This change ensures (a) an instance with PCI requirements has the best possible chance of scheduling successfully and (b) an instance without these requirements won't clog up hosts that have these valuable resources. Change-Id: I04bf7e6b8324dcac6c93b0cb69c38c30fb05be56 Partially Implements: blueprint reserve-numa-with-pci |
6 years ago |