When using init-runonce script multiple default
security groups are present and raise error:
More than one security_group exists with the name 'default'.
Add a check to create rules to admin's default sec group.
Change-Id: Iaf93467d70ae41fdbcd2b37d6c5639a32d939394
Pull images from tarballs.openstack.org site[0] when there is no
Depends-On in current commit message.
[0] http://tarballs.openstack.org/kolla/images/
Change-Id: I2e5d4d7ed6418624494121e0a530ec95fd045970
kolla-ansible destroy properly fails if qemu processes
are running in compute nodes.
Manually executing ./cleanup-container won't because
$COMPUTE variable is not defined anywhere.
Change-Id: I304c59ec682a93035e631490bbba7b355b1fcae2
Closes-Bug: #1656864
Move ovs-cleanup step to cleanup-containers,
otherwise bridges will not be removed because neutron_openvswitch_agent
container does not exists after running cleanup-containers.
Add logic to cleanup ovs bridges only when openvswitch_db
is removed and openvswitch-agent is running,
so when removing other container from a parameter at script
invocation ovs-cleanup will not be executed.
Change-Id: Ie5fea40426df0e9e465fc173aba185f61098f676
Closes-Bug: #1640178
With 4.4 kernel we can use the improved overlay2 driver instead of
btrfs for significantly better performance when creating layers.
Change-Id: I0b84a2b34fdb71c07798d94b546d3105a2742321
Related-Id: I3b0dfd6db5298dfb34ec160eed910ca76feeb423
Read EXTRA_OPTS from env make it possible that using arbitrary
ansible-playbook parameters in kolla-ansible script. like
EXTRA_OPTS='--limit control' kolla-ansible deploy
Change-Id: I10e0dafb6138d91facdb66a2f487cdeca4689c28
OpenStack requirements constrains is well tested. Use it in case of
installing upstream broken package.
This also fixes latest requests 2.12.2 break docker-py, which makes
kolla gate red.
Change-Id: I3e4ec4af2a6e1280313733e8f31f2eea7669dbc1
Updates cleanup-containers to disclude lines related to
dom0 qemu processes.
Change-Id: I0b71ed29b9a2f239ebfdaa66b7cbe41eeaf2773c
Partially-Implements: blueprint xen-hypervisor-support
Behavior of stop playbook is very similar to the destroy
playbook. This is meant when you may just want to bring down
the service for some sort of maintenance but not destroy all
the associated data. Also added support for the new playbook
into the kolla-ansible command.
Change-Id: Icf0ca91de71dc8ead3a024de3e5b9e49116560d1
Implements: blueprint ansible-stop-host-playbook
* Build kolla image by using kolla project's code
* bump openstack_release to 4.0.0
* Remove tox deploy related env, it is useless now.
Depends-On: I132ee005bce993cbadf411697817c2e95548dc81
Change-Id: Id899eb39d476b95130fbeb43adf4fd49ef32be32
All json file in Kolla are json.j2 file, it shold be render as jinja
template, then validate by using json.
Change-Id: Ibabbe435116fd255d68347e00407156db76fedfe
Closes-Bug: #1634447
ARA 0.9.2 was released which deprecates the previous callback location
in favor of a new one. The deprecated location still works but let's
move to the new one right away.
Change-Id: I8a10d5855ab6f813e52cc6efce5bcfe91d9c3f92
The next release of ARA (0.10.0) contains a change to the callback
plugin location that /should/ be backwards compatible but let's
control the update to the newer version to be safe and avoid
breaking the gate needlessly.
Change-Id: I32176166e8ebcbfdf0baa8bd7ec30e5ec6d795a5
The gate jobs are using Xenial as the base OS so it seems we should be
using the same non-infra repos as our base image.
TrivialFix
Change-Id: I6e5d27364054c474c16120a3195cae819861c8a1
