According to Python 3 Porting guide
http://docs.pythonsprints.com/python3_porting/py-porting.html
Exceptions were changed in a few ways for Python 3. First, strings
are no longer usable as exceptions. Additionally, the raise syntax no
longer accepts comma-separated arguments, instead working with exception
instances. Perhaps the largest difference in Python 3 is that exception
objects are only available via the as keyword, which was introduced in
2.6.
Change-Id: Ide665ecc4b7f14bd58bafab47e05a86a4cf2d141
Closes-Bug: #1490526
Nova-compute is curerntly generating a backtrace when trying to nova
boot a VM. The backtrace is described in the bug log. Bind-mounting
/sys/fs/cgroup:/sys/fs/cgroup in the libvirt container resolves the
problem.
Change-Id: I5a56b61fd260728fb76e19bcbdf403b80a4ec5a6
Closes-Bug: #1490326
Initially it did not use this client due to the fact that the client
didn't seem to want to work in the containers. Now it works fine and
it should be used instead of the deprecated keystone client
Change-Id: Ib0e172c677e200e5df01c478b7ea257b30c0df0b
Closes-Bug: #1490126
This changes bootstrapping of the Heat container to bootstrap
the Heat container with a heat domain user. This requires some
work from bootstrap.yml to pass in several environment variables
needed by the heat domain setup script.
Co-Authored-By: Sam Yaple <sam@yaple.net>
Change-Id: Iab05983754fa514835cb5ff54d775faa18773110
Partially-implements: blueprint ansible-heat
We no longer have CONFIG_INTERNAL and moving forward CONFIG_STRATEGY
infront of COPY_ALWAYS or COPY_ONCE will just lead to confusion.
Change-Id: Ie0d71637e25cbd79d46e1cdca62df714c10b85d2
Implements: blueprint update-configs
This currently deploys the core services for a working Swift which are
account/container/object/proxy.
I've included some basic docs in docs/swift-related.rst, which gives
usage instructions and more context on this patch. These are really to
give an overview of the state of Swift in Kolla as of now, so unless
there's some major inaccuracy there please don't nitpick it.
Change-Id: Id0c54be3e24c46459c40b16b7020f05bddbe1b19
Implements: blueprint ansible-swift
nova.conf was not using the proper port value for glance and would
only work with the default port in that situation.
Additionally, the state_path defaults to the python directory rather
that the expected /var/lib/nova/ directory.
Paritially-Implements: blueprint update-configs
Change-Id: I9cc2117c1d786fc1b81c53848e543d27afaf8979
Use cinder-volumes as name of LVM volume group expected on the host
instead of the nonsense that was there before.
Change-Id: I35221ac0ad3464581f9ba95c3127832e0af7ad64
Closes-Bug: #1487800
Note, this is not in the inventories/site.yml as it will be a
transparent dependency of Swift.
Change-Id: Ic8c80072596594e646ece74ac0ce74c7000398ff
Partitially-Implements: blueprint ansible-swift
In MariaDB we adjust the dependecies of what we install there as well
adding only what is appropriate for the install.
In Ansible we adjust some templates to all work around differences
between the different Linux families.
Change-Id: Ibc26e2f4d4a732630632d3ed27fb595b6fe019d2
Partially-Implements: blueprint install-from-ubuntu
Currently we write configs to /opt/kolla/config on the destination
node. This does not mesh with LSB so we adjust it to /etc/kolla
Change-Id: I4b6683b3b707ebb25b064ba5162533ea5a35d977
Partially-Implements: blueprint update-configs
In rabbitmq we removed the requirement for hostname since that is
already installed.
Change-Id: Ia2355e332d53763db630d19663c2ddc8bf3aa425
Paritially-Implements: blueprint install-from-ubuntu
The register operation was registering user_database which is a global
variable in group_vars/all.yml. This results in glance not being deployable
because user_database is overwrriten at keystone task registration time.
The result of this is the playbooks fail to deploy.
Change-Id: Ic69725fb09aa0a368ec5b0d8f47bfc768c29c70c
Closes-Bug: #1486876
If ip_vs is not loaded keepalived will enter a restart loop. To fix that
load ip_vs module every time we start the container.
Change-Id: I6b39d8654cc6a6da7a9162e5c3efab073746b246
Closes-Bug: #1486276
Due to the differences between Ubuntu and Centos around Apache2 I have
had to copy both start.sh and config-external.sh to be unique files
for Ubuntu so as not to affect Centos either. This can be removed when
we change the way config-external works.
Change-Id: I14dc11e7bb6284b897259a53acc914ae8f254d3c
Partially-Implements: blueprint install-from-ubuntu
Rabbitmq containers mount /var/lib/rabbitmq from 'data'
containers with 'root:root' permissions because
ansible does not wait for rabbitmq bootstrap container -
the latter corrects access rights but sometimes gets
killed just after start.
Change-Id: I5cd1ce9810a1fd457dd34a1283e448204964c17d
Closes-Bug: #1487422
Bootstrap task runs bootstrap container on one host but
waits for its exit on all machines in inventory. This
gives error about non-existing container id.
Change-Id: Ie06c4da470c2e109d13b029fa674373b255653f3
Closes-Bug: #1487387
The previous method of using the API image for a data container
worked, but resulted in more data being bindmounted and copied
into the system. This patch resolves that by essentially using
a distro-type as a FROM in a Dockerfile to generate
distro-type-data. Further all of the data containers used
throughout ansible are modified to use this new data container.
Change-Id: I8846573d4f2d4b98d4f46c770bfefc6d4c5cd0b5
Partially-Implements: blueprint one-data-container
This moves the remaining global.yml options into the all.yml file
Change-Id: I9795b924e3e1882d20ba8f16ef3c5fe5c0193ef3
Partially-Implements: blueprint update-configs
The purpose for having defaults.yml on the command line was originally
for variable inheritance. Over the past month we have slowly changed
how things are inherited (like ports) allowing us to place these
'defaults' into the group_vars/all.yml location as they should be
values that go unchanged (but can be overridden).
Change-Id: I2becec66bf431bfc9d88fc825b5380c1e173ca70
Partially-Implements: blueprint update-configs
