Remove devstack-check label and increase centos/py3k values

Both of these measures are intended to make allocation more fair in
the currently constrained environment.  The check jobs have an advantage
in being able to run on two node types, and nodepool may be favoring
them due to that.  Remove the check label for now.

Set the min-ready for centos and py3k to values that are closer (50%)
of the precise nodes.  Reducing the spread should make the allocator
distribute nodes more closely according to current demand.

These are untested suppositions, but I don't think they will hurt.
They may help.

Change-Id: Id228c7e0f3422a7432af84b3f3bd1817b3b9b139
This commit is contained in:
James E. Blair 2014-04-11 15:39:09 -04:00
parent 065b0f181a
commit 9d9f3ff881

View File

@ -26,11 +26,6 @@ labels:
- name: rax-dfw - name: rax-dfw
- name: rax-ord - name: rax-ord
- name: rax-iad - name: rax-iad
- name: devstack-precise-check
image: devstack-precise-check
min-ready: 7
providers:
- name: rax-iad
- name: bare-precise - name: bare-precise
image: bare-precise image: bare-precise
min-ready: 42 min-ready: 42
@ -40,14 +35,14 @@ labels:
- name: rax-iad - name: rax-iad
- name: bare-centos6 - name: bare-centos6
image: bare-centos6 image: bare-centos6
min-ready: 14 min-ready: 21
providers: providers:
- name: rax-dfw - name: rax-dfw
- name: rax-ord - name: rax-ord
- name: rax-iad - name: rax-iad
- name: py3k-precise - name: py3k-precise
image: py3k-precise image: py3k-precise
min-ready: 7 min-ready: 21
providers: providers:
- name: rax-dfw - name: rax-dfw
- name: rax-ord - name: rax-ord