This reverts commit 684bb51cbdc253d5ac20fdf892b1badee1fcbd19.
Maintenance is completely, bump max servers back to 1 to see how things
are doing now.
Change-Id: Ie33155c32bedd8cb94de952d8e8823a5e9dc19a2
Bluebox is performing maintenance soon. It would be friendliest
if nodepool wasn't asking for vms on their cloud whilst they
do their maintenance. This patch sets bluebox max_servers to 0.
Change-Id: I6e147b3e142dc185b2752f25007fca8c26d03e2d
simple-init (i.e. glean) has some unreleased changes that are required
for enabling the network correctly on F23. Install from source before
we cut a release so we can test things out.
Change-Id: Icffcede14853a7cdc988c3358c660416b30138ae
On OVH and Bluebox, the memory layout is such that there is still
significant (~900M) memory above the 8192M address. Increase the
limit to encompass that, which will bring these providers up to
approximately 8G, while increasing hpcloud (which is the actual
target of this restriction) to about 8.5G.
Change-Id: I5c121be55cadad13ad5807968f33b492f9b1e215
This reverts commit e474929518a11337a87432a67abd5f0144833551.
Approve once https://bitbucket.org/hpk42/tox/issues/294 is fixed in
a new tox release.
Change-Id: I73846af205efb49e14c41793e0327b54a9f2f7f9
Until the regression in tox 2.3.0 is resolved through a new release,
only update nodepool images on Tuesdays so we don't need to delete
them every day (hopefully it will be fixed by Tuesday!).
https://bitbucket.org/hpk42/tox/issues/294
Change-Id: I300857d50c1dc010dba569c5978e45e76a90162c
The non ha job has been tested on F22 and
F21 is going EOL. Also change the number of
F21 and F22 nodes appropriately.
Depends-On: I7835ec90d8bcbf1183b4217b9bc6d7714833d243
Change-Id: Ib42dbfc8e8ae1cf5e85159562bd6c112bc0d3220
When running disk image builder use the build specific checkout of
system-config to install puppet and puppet modules. This allows for easy
local testing of changes to those scripts. Without it master is always
used.
Change-Id: Ifc86d77f702633d630adc1ee619f58607cb56c82
We now have no more jobs using CentOS6, so disable them in nodepool.
-1 is magic value for: Do not even build new images.
Change-Id: I573a2709389c66780a822325b882609e853b8b84
Since https://review.openstack.org/#/c/196252/ merged, nodepool
injects a sync;sleep 5 after running the scripts, so having it in the
scripts is a double sleep.
Change-Id: Ie7a9315e6de67625eca15b45f1662e4c63f8bc10
We have something like 57 floating ips now, but 316 vcpus, so
increase servers to 316/8 = 39 instances.
Change-Id: I915af243dc399070202d17292aa5e31976a01c2c
The release has happened, the migration worked, all's right with the
world.
This reverts commit 04eb36588d80dd77a9c692f53470b7d727567604.
Change-Id: I28a3e9cf3b420a6ccca20c52c4e67adc3f5710c5
After I3de17c2d670d8cb0f28ffb5e1541751bc7f4d73e there are no more F22
based jobs; min-ready was turned to zero with
Ifa6367488165df6cad18725a9191b426a41c08bf
Remove them from the config
Change-Id: I6ff6d684e17b0581ae6fbb310af29dd1be0e54d7
The prior change (Ifa6367488165df6cad18725a9191b426a41c08bf) has
disabled F22 nodes.
This adds F23 nodes (just one for inital testing) and modifies the
fedora-22 based jobs to use the new nodes.
(note the depends-on, required for building f23 fedora-minimal, is
available in dib 1.4.0, so this is ready to go)
Depends-On: I1a6e45d04755515286b3d49f8280c16b527e2f48
Change-Id: I3de17c2d670d8cb0f28ffb5e1541751bc7f4d73e
This commit adds a temporary version cap on subunit2sql to be < 1.0.0.
The 1.0.0 release includes a very large database migration which will
be slow to execute. The python DB api from >=v1.0.0 will not work with
a database that doesn't have the updated schema. So while the migration
is running let's cap the version we install to prevent everything from
breaking while the migration is running. (which might take days)
Change-Id: Iab89beb5c7aba8b744a62f5063e513b72cab0ec2