Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=master 2016-01-21T22:59:13+00:00 2016-01-21T22:59:13+00:00 SamYaple sam@yaple.net 2016-01-12T20:52:00+00:00 urn:sha1:6adb5c0aa5a5947bdeeb03b03cba29af30902d2f The existing gate partitioned a disk for use with docker, depending on the gate it would use the swap disk (RAX) or a spare disk (HP). However, with the new gates (Bluebox + OVH) there is neither a spare disk nor a swap disk. This leaves us with one choice: File based loop device. This patch creates a file at /swapfile to ensure we have swap. It creates a file at /docker to ensure we have a loop device for Docker. Right now the /docker file is 10GB and the /swapfile is 4GB due to size limitations in the gate across all servers and types. This has proven to be enough space for all our current tests. Additionally, reduce the number of threads the gate uses to 4 to prevent the lockup and hour timeout we have been seeing as more recently in the gate. The scripts that setup the gate are moved to the tools directory rather than the tests directory to match the structure of the other projects. Partially-Implements: blueprint functional-testing-gate Change-Id: I3e370f2382b6df36103d8b2ceda9b21d9b4229d5 2016-01-03T16:44:44+00:00 SamYaple sam@yaple.net 2015-12-26T02:20:08+00:00 urn:sha1:6ca65aba6cc01ef3e13854c19aaf4c6cbf420331 Docker and docker-py can now be unpinned since Kolla has been converted to using the kolla_docker module and we no longer rely on upstream to unblock us. Change-Id: I6ee2b78c31ef0447da6154b75db381d5cdd55ab6 Partially-Implements: blueprint kolla-docker-module 2015-12-11T06:31:35+00:00 Martin André m.andre@redhat.com 2015-12-11T02:11:05+00:00 urn:sha1:40b8a0243e20d551f2e153759f531749783656be This commit removes the assumption that all gate nodes have a secondary disk, and skip tuning the filesystem if the node doesn't have one. This fixes gate failures on OVH nodes. Closes-Bug: #1525047 Change-Id: Ief22f34b32caf7a8b446df888fc5cc1964ad272e 2015-11-22T18:34:35+00:00 Sam Yaple sam@yaple.net 2015-11-07T15:58:10+00:00 urn:sha1:f9ee96f21695f7eba81c07e257eda3a080108b70 To support multinode we must now distribute our setup to multiple hosts. Instead of making special rules for this, we are going to convert our existing setup to Ansible. This way both setup proceedures take place in the exact same fashion. Partially-Implements: blueprint multinode-gate Change-Id: I43ece298bba994e9b5083403ef3cf6d4245cda6d