Update the group_vars and globals docuementation as well.
Change-Id: I3ffd49b8d99667425596a2753845767a62e05bf1
Partially-Implements: blueprint kolla-docker-module
This intentionally leaves out rabbitmq from this patchset. It will
require additional work to remove its data container
UpgradeImpact
Partially-Implements: blueprint docker-named-volumes
Change-Id: Id68b8e43a3c077ef4f4f4d67ea34d0692e66eef7
Add `nova` user to nova-libvirt container.
And change libvirt-socket group to nova.
Change-Id: I183c83f4be8b1d7c75d4ac204df7b7e059626aa2
Closes-Bug: #1525583
- See instructions in doc/nova-fake-driver.rst
Implements: blueprint nova-fake-driver
Change-Id: I553a40c2df39bdcc391eb1b8b2b8fd5f4ed48c33
Signed-off-by: Hui Kang <kangh@us.ibm.com>
Signed-off-by: Marcio D. Silva <marcios@us.ibm.com>
The upstream docker module in control of Ansible has proven to be a
major breaking point for Kolla. It is the reason we have a cap on
Docker of 1.8.2. They have stated no support for the Docker registry
v1 moving forward. We have to wait for a patch to land and then
upgrade to the latest Ansible version to take advantage of a new
Docker feature. Doing that is slow and it is not always possible to
upgrade if there are other breaking changes (aka ansible 2.0).
For these reasons we can build our own Docker module.
Partially-Implements: blueprint kolla-docker-module
Change-Id: I2ca57010c45710635cfe80ff23a2a5e2edabee57
Master version was still set to 1.0.0. This became alot more obvious
in a recent patch when we started pulling that version number for the
tag...
TrivialFix
Change-Id: Ie9c95a4dc606d0527c44fcd624b4473e45f7f3cf
Throughout the project overtime some of these file permissions have
changed to have an executable bit. They should not have this bit set.
TrivialFix
Change-Id: I1748b5bde813a0fcac36aeecdfd83245b8ee5be3
The CMD command for data causes docker to launch it with /bin/sh which
is ugly when viewing the containers statuses. Additionally for
kolla_ansible we were not specifying the CMD at all, forcing us to use
the 'command' param to set the sleep command.
This patch brings the kolla_ansible launch inline with the rest of the
project.
TrivialFix
Change-Id: Ic87a89921674802c15596756526e07f52a782f32
During the bootstrap we no longer need to pass in this info
TrivialFix
Related-Bug: #1526251
Related-Id: Ieee215b9de1618b3d31f3d1a766a9d0ebafdee4d
Change-Id: I82460cf11dea4692c0469bf2b9afddd794a30ec1
By ignoring the appropriate tests that pep8 does we can properly run
*most* of the pep8 tests on all of our modules allowing for a more
consistent coding style.
Closes-Bug: #1528431
Change-Id: I33f27a250d06d4f044267aa3ad189e092789b8df
Convert config creation from a playbook to an action_plugin. This
reduces the complexity and confusion while retaining the same augment
structure and flexibility.
This allows us to remove the 0-byte files as requirements. They will
still be used if they are present (this means we require additional
documentation around them).
DocImpact
Closes-Bug: #1528430
Change-Id: I2c789f6be9f195c7771ca093a6d59499564b4740
In heterogeneous environment, api_interfaces are different each other.
So we should specify it from hostvars.
Implements: bp configure-network-interface
Change-Id: Id15d70bfb9ebb62a64a3847a6b77407efb171dbe
Create the admin project, user, role and keystone service info by
using ansible task rather than shell script
Closes-Bug: #1526251
Change-Id: Ieee215b9de1618b3d31f3d1a766a9d0ebafdee4d
This changes default behaviour of build.py to instad of putting latest
tag on it, it puts current kolla version as found in setup.cfg
Change-Id: I4d6e9a0159c6a5598abd58072594df4204427308
Partially-Implements: blueprint upgrade-nova
Partially-Implements: blueprint record-version
As part of upgrade process we need new services to detect what is the oldest
version running on compute nodes.
Change-Id: Id65f2bc765828054bf5d5562de27255031254821
Partially-Implements: blueprint upgrade-nova
Without this the haproxy role doesn't have the facts it needs to
render it's template, resulting in the following error:
TASK: [haproxy | Copying over config(s)]
************************************** fatal: [control01] => {'msg':
"AnsibleUndefinedVariable: One or more undefined variables: 'dict
object' has no attribute u'ansible_eno1'", 'failed': True}
This is similar to the fix applied previously for other services in
I99b7dbebd5a6193e192ee258ddf576d18db90ed7.
Change-Id: Idb7fa8763cff64ad761c5b8a1a3bf92a27f4f501
Closes-Bug: 1524738