Change-Id: I436711ca17b3d1b4adb90b40521c96eafc3bb823

 keep consistent with other projects

Change-Id: I3eae5efbc148a87dea44ce1fe727f6314a437e98

- rename action and serial to kolla_ansible and kolla_serial
- use become instead of "sudo <command>" in shell
- Remove quota for failed_when and changed_when in rabbitmq tasks

Change-Id: I78cb60168aaa40bb6439198283546b7faf33917c
Implements: blueprint migrate-to-ansible-2-2-0

In trove-taskmanager.conf a typo has been
introduced for nova_proxy_admin_tenant_name
option.

It currently is:
"nova_proxy_admin_tenant_name = services"
But should be:
"nova_proxy_admin_tenant_name = service"

Change-Id: I7b5d0ca4c6c994b6dd3c5de3f0a79637fda88177
Closes-Bug: #1770262

The kolla-ansible certificates command creates a self-signed
certificate and corresponding private key.  This change sets the
file mode on the files that contain the private key so that they
are not world readable.

Change-Id: I7bfba5975af8d230e5d00c2ce801a914fbbf2d4e

Apply Glance database upgrade procedure:

https://docs.openstack.org/glance/latest/admin/zero-downtime-db-upgrade.html

Rolling upgrade in Glance requires that glance-registry is not deployed and run

Depends-On: https://review.openstack.org/532128
Depends-On: https://review.openstack.org/566804

Change-Id: Ia5d0cee2385facefda9d423051b74ab51d075f13
Implements: blueprint apply-service-upgrade-procedure

Since the version of ceph bump to L, the output should
be updated.

Change-Id: I4c05b9b7423369a43dcb5855a2f0ef016ddbe488

By default, the workers for gnocchi_metricd is 5[0], it's too
small for production environment, this PS to make it configurable,
in this way, user can change it according to actual needs.

[0]: https://github.com/openstack/kolla-ansible/blob/master/ansible/group_vars/all.yml#L356

Change-Id: Ibf4dec793f02c407547c77963cc13799d044b90f

This commit adds the --by-service flag in the discover_hosts
command of the nova cell subsystem, using this flag,
hosts are mapped based on the existing nova-compute services instead
of using the compute node reference.

In this way, we can ensure that the host mappings exists
for this new host (and create it if not) preventing the
HostMappingNotFound exception to loop over and over.

Bug: #1768094
Change-Id: I948004031bc3e125f929ed3e6c670aea11e73a31
Signed-off-by: Jorge Niedbalski <jorge.niedbalski@linaro.org>

Following by https://docs.openstack.org/image-guide/obtain-images.html#cirros-test

Change-Id: Ide3508b3af6923a06e63242dc730b2742147ce37

Change I0c1328237d2109b1d1d5dcb40f331fff1ab10257 recently prevented
running kolla deployment CI jobs against changes to some files,
including requirements.txt. This change reinstates testing of changes to
requirements.txt, since this can have an effect on the operation of
kolla ansible.

Change-Id: I3d839de9aed60cddebea7d1140f618d3261cca2a

While fixing test-requirement.txt, I found that
check pipeline can be more optimized in term of selecting
the jobs to run based on file change.
- https://review.openstack.org/#/c/567083/
kolla main jobs are not needed to be run on check
pipeline for test-requirements.txt, releasenotes/* etc.

This commit skip those jobs when only above files
are changed in patch. This is will save time as well
as infra resource also.

Change-Id: I0c1328237d2109b1d1d5dcb40f331fff1ab10257

hacking is not capped in g-r and it is in
blacklist for requirement as hacking new version
can break the gate jobs.

Hacking can break gate jobs because of various
reasons:
- There might be new rule addition in hacking
- Some rules becomes default from non-default
- Updates in pycodestyle etc

That was the main reason it was not added in g-r
auto sync also. Most of the project maintained the
compatible and cap the hacking version in
test-requirements.txt and update to new version when
project is ready. Bumping new version might need code
fix also on project side depends on what new in that
version.

If project does not have cap the hacking version then,
there is possibility of gate failure whenever new hacking
version is released by QA team.

Example of such failure in recent release of hacking 1.1.0
- http://lists.openstack.org/pipermail/openstack-dev/2018-May/130282.html

Change-Id: I05790c5f946a4127fe6c8d9867cc618cb83d67fb

As described in [1], [2], glance-registry was deprecated from Queens and will be
removed in S, so we should disable glance registry in Queens but keep the image
and deploy logic if user need this (but it's low chance due to glance-registry
almost do nothing currently).

This patch only disable glance registry microservice.

[1]: http://specs.openstack.org/openstack/glance-specs/specs/newton/approved/glance/deprecate-registry.html
[2]: https://blueprints.launchpad.net/glance/+spec/deprecate-registry

Change-Id: I6667325711d1c54cf5233ad6973d89ea396a46b5
Closes-bug: #1769837

This patch enforces the removal of the container
network namespace when the environment is destroyed.

Closes-Bug: #1769651

Change-Id: I9b0bbbb5a59e6067a745635c555051ef97b79f9a
Signed-off-by: Jorge Niedbalski <jorge.niedbalski@linaro.org>

Allow to set computes_need_external_bridge to true/false
depending on the desired configuration, for allowing
cases such as disable dvr and enable l3 ha.

Closes-Bug: #1769686

Change-Id: I1565b08dfccb7bec2ddda8c048b7d951c9eb1824
Signed-off-by: Jorge Niedbalski <jorge.niedbalski@linaro.org>

Some variables should be modified too, just like this commit:
https://review.openstack.org/552863

Change-Id: Id43eefb948a05de03d19c46048b6151bf6f5dc0a
Related-Bug: #1769463

Aodh service credential defaults to publicURL.

Aodh should work with the internal interface (v3 API Identity syntax):

.....
[service_credentials]
interface = internal
.....

Change-Id: Ie11290be25291fee1938032ae6294546fb7a98f3

In ansible/roles/etcd/tasks/config.yml, the kolla_docker
compare_container action doesn't check environment.

Once a container is created, it won't get recreated if only the
environment change. This commit add the environment attribute to the
kolla_docker action in etcd role

Change-Id: I8fb71cc945867e06acc67f6d1256bf62f4276206
Closes-Bug: #1765517