Currently we omit the os_distro property when uploading the
cirros image to glance. Nova assumes it to need vfat disk
incase the image is Windows.
This change sets the property to "linux" causing ext4 to be
used instead.
TrivialFix
Change-Id: I3fdb71f5be7702a2dc223946fae82131c6c46154
Signed-off-by: Dave Walker (Daviey) <email@daviey.com>
Add a new subcommand 'check' to kolla-ansible, used to run the
smoke/sanity checks.
Add stub files to all services that don't currently have checks.
Change-Id: I9f661c5fc51fd5b9b266f23f6c524884613dee48
Partially-implements: blueprint sanity-check-container
Run playbooks in serial are unnecessary and may cause some issue. This
patch disables serial.
This patch also removes the serial for MariaDB playbook. MariaDB handle
this internally.
Partial-Bug: #1668185
Change-Id: I3b4216dd82607475e9bd9b44590b631be4abdbdd
The newest version of ARA, 0.11, deprecated "ara generate" in favor
of "ara generate html". "ara generate" will be removed sometime in
the future so let's adjust it right away.
Change-Id: I31bff0a7e130c329da44b46506f5b12fa8d6deb8
Closes-Bug: #1665746
There is inconsistent use of either `/usr/bin/python` or
`/usr/bin/env python`. This makes for unexpected results when a
user might be using a virtualenv.
Change-Id: Ibb030f920a8869f9113ade70b66a921cc815060d
Currently it is not possible to use kolla-ansible when it has been
installed in a virtualenv. Virtualenv-based installation may be
desirable when a suitable system package (e.g. RPM, .deb) is not
available, as it allows the user to install kolla-ansible and its
dependencies without affecting the system-wide packages.
This change checks for the presence of the $VIRTUAL_ENV environment
variable to determine whether we are running in an virtualenv. Since
kolla-ansible is not a python script, this comes with the caveat that we
must source the virtualenv activation script ($VIRTUAL_ENV/bin/activate)
before executing kolla-ansible.
Change-Id: I19efb96605bee3b16df3a0b78cd681e5f15499f6
Closes-Bug: #1530319
In commit 177fbea79a1babdcd4e8230341380d373eef6df4 the project
was renamed to kolla-ansible, and this broke the BASEDIR
in the kolla-ansible wrapper.
Closes-bug: #1665262
Change-Id: I89fe15e5723f39f453a8173f7ced3f623a8bccc5
Ansible use jinja2 < 2.9, but requirements/upper-constraints.txt
requires jinja2===2.9.5. Installing ansible shouldn't use upper
constraints provides by OpenStack.
Change-Id: Ib37e8d06373a61959b41b8737085d5f001650e42
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
- This change introduces a new tool for configuring
host interfaces for use with ovs and dpdk.
- The ovs-dpdkctl tool will be executed via systemd
when a system first boots to bind interfaces to
dpdk compaible drivers.
- The ovs-dpdkctl tool will be injected into the
ovsdb container to allow external configuration of
ovs bridges and ports for use with dpdk.
Change-Id: Ie8f32d097f0a6816c2ddd03ade926c00837da322
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
