docker-py 2.0.0 is released with renaming docker.Client to
docker.APIClient. and with a new python package name "docker" rather
than "docker-py".
This patch support docker and docker-py packages.
Change-Id: Ib4400a4d2ce803191ee6215c5b28f0052970332c
Closes-Bug: #1668346
Adding -e REGISTRY_PROXY_REMOTEURL=https://registry-1.docker.io to the
docker run command in the start-registry script configures the local
registry as a pull through cache. However, pushing of images to the
local registry fails.
Pushing to a registry configured as a pull-through cache is unsupported.
For more information, reference the proxy section in Docker
Documentation (https://docs.docker.com/registry/configuration/)
The start_registry script has been updated in the patch set
https://review.openstack.org/#/c/426338/
Change-Id: If62b40d8316af7c3593523493cad8a904d35dceb
This builds the deployment guide that will be published to
https://docs.openstack.org/project-deploy-guide/newton/.
In this approach, all existing documents in kolla-ansible/doc directory
will remain. The kolla-ansible/deploy-guide directory will simply
include all documents that exist in the kolla-ansible/doc directory.
All new changes will be made to the documents in the docs directory
which will be imported to the deployment-guide. However, I believe we
will also have to build the deployment-guide every time a change is
merged to the docs in the doc directory.
Change-Id: I98db4ec45403cf48086381b45bf5a12bbf998911
The check whether 'already' presents in mongodb output
should belong to changed_when.
Change-Id: I829c8906f0f7b61d3f6e0211319899d126e6850c
Closes-Bug: #1668216
Fix the example by suggesting the creation of the directory
and customizing nova properly.
Change-Id: Ie5cd9b7f309416745dce60211b5a800e8c5273f7
Co-Authored-By: ampopp04@gmail.com
add environment parameter to handlers restart etcd container as
there are env parameters in default
Closes-Bug: #1669089
Change-Id: I99266e7a367cb54c77b3d3da35ba5055acd98f62
While deploying/genconfig designate, raise an error due
a missing .key in the item iteration
designate_rndc_key var is already used and replaced by the register
Changed register to other name.
Bind9 container should be started before other designate services.
Change-Id: Ia6aa89af1cf2317fa8f006b8d35d3760e7fb9980
heat-api kept redirecting clients to use http:// instead of https://
when communicating with our https:// only loadbalancer
Please examine the logic for enabling it carefully, it's hard to know
if it should be enabled or not, potenitially it could be a security
risk.
Based on openstack-ansible-os_heat:
commit 4033a0f854cba6719c61812ef5b553e932a6c6c2
Author: Kyle L. Henderson <kyleh@us.ibm.com>
Enable oslo_middleware proxy header parsing
"Heat has moved to using oslo_middleware for the http proxy header
parsing, however the default is to not parse the headers. When
the external protocol differs from the internal protocol this
parsing is required in order for heat to work properly since it
will return 302 redirects to the client during some operations
(such as delete stack).
An example of this is when using haproxy with https configured
for the external protocol and http for the internal protocol.
If the oslo_middleware does not parse the headers, then any
302 redirects would specify a url with http rather than
correctly specifying https and the heat client would fail to
connect on the redirect url."
Change-Id: I38661a0bc2163a7f72febd98b7ae6f51c5d45ad5
We explicitly gather facts for all nodes up front in the playbook, so
setup tasks for all other plays are unnecessary noise.
Change-Id: I4bc152288752da780b5cb447b4ad3f7d49390dee
* Remove references to all-in-one, kolla Swift now works correctly in both
all-in-one and multinode contexts
* Fixup commands used for generating rings
* General readability improvements
Change-Id: I3ec87068a98ba5397bb6f2feb707bc685181e747
The check whether 'already' presents in mongodb output
should belong to changed_when.
Change-Id: Ib982a59820d53ccf5439f59df50c1b1938650967
Closes-Bug: #1641113
The wrapper keystone_bootstrap.sh expects to parse output from the
keystone-manage command. Somewhere along the line this command stopped
logging to stderr resulting in it not being able to report it's changed
status correctly.
Closes-Bug: #1668220
Change-Id: I895ebe11b88fd239fa8cb6e1a2fed779743e4139
