| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
These are no longer used by kolla ansible, and were not used by any
other deployment tools.
Change-Id: I214b0b7d94717aa9aeae88363d5721396e7b6684
|
|
Currently we use Ansible 2.2 in kolla_toolbox, while lowest supported
version is 2.6 - bumping up to 2.8.
* Use upper constrains in Dockerfile.j2, instead of pinning them in
here - Ansible is pinned to 2.8.*
* Add no_log=True in kolla_keystone_user
* Add endpoint_type as a param in kolla_keystone_service - now
AnsibleModule requires all options to be defined, otherwise it throws
an UnsupportedParameter error
* Add openstack_release variable in kolla/common/config.py which
is used for fetching upper-constraints.txt for desired release
Change-Id: I2cb0ea2fde1b408d48b39bf7a54b898e850d31aa
|
|
Use latest release 1.1.0 and compatible changes w.r.t pep8
Change-Id: Ia3d1166a2746a46591e4e5a04ea91e03ddc28d93
|
|
When using kolla_keystone_service module, if
description attribute is not created(example Keystone).
Service update will fail due missing attribute.
This change adds a None value to description in order to
allow service update when description was not added.
Change-Id: I568db4559428525ac6c5083cfc20cffc20be6342
|
|
The deployment of a service requires the creation of a new service
endpoint into Keystone. To create a new service endpoint the
kolla_keystone_service tests if the service is already registered and
updates the URL if so, or create the new endpoint in other cases. In the
actual implementation, the register test only looks at the service id
and interface which makes the test behaving wrong in multi-regions
context. In multi-regions, we deploy the same service many times, and
thus, actual implementation considers that this is the same service and
updates its endpoint rather than creating a new one. This fix adds a
condition to the test that verifies the region to distinguish two
identical services deployed into two different regions.
Change-Id: Ie7ca8800fe3c5a9585e4b0bbbc38ac628ec753bc
|
|
Make the kolla_keystone_service can update the following fields
* service.name
* service.description
* endpoint.url
TrivialFix
Change-Id: If239a518b0217cfc105388ae5e298a8904ac2af5
|
|
The traceback is logged also and will be helpful when the
library failed. We can get which line is failed from the log.
TrivialFix
Change-Id: Ia417232007e2f34c83d2e7cad6ed08dee49ce836
|
|
bcoca has asked we use head of devel to fix the loader issue
TrivialFix
Change-Id: Ie6f4b6bbdffed9a85c840a4f425d866fc5402f4b
|
|
After our switch to keystone-manage bootstrap Horizon is not happy
due to v3 not being setup correctly. This patch fixes that
This also includes removal of unused variables (transforms them into
endpoint url variables)
TrivialFix
Change-Id: I1e04db8c24049f80e974c063f03068a2ab32a563
|
|
Ansible is pinned to single commit in devel branch to pull in the
latest shade module we need (domain control). It will be available in
ansible 2.1
TrivialFix
Change-Id: I4c21fa1d2cec30d4aeb80e050ef4a62332f9ed45
|
|
This change is needed for clarity. We have a kolla-ansible script.
We have a kolla-mesos repo. We plan to have a kolla-ansible repo.
Already we have had far too much confusion about whether we are
talking about the container or the project. Naming this kolla-toolbox
eliminates all of that confusion and its probably a bit more accurate
of a name too.
Closes-Bug: #1541053
Change-Id: I8fd1f49d5a22b36ede5b10f46b9fe02ddda9007e
|
