Change-Id: Iba1040e242f015eb32651efd935ccea3514c80bc

All other project names are lowercase.

Change-Id: I7046d3f6b610a46a69504a283c933d83f266a3db

Change-Id: I4d409e052c00d83b451a2a13917f89531a88457f

Two new parameters (migration_interface, migration_interface_address) to make
the use of a dedicated migration network possible.

Change-Id: I723c9bea9cf1881e02ba39d5318c090960c22c47

Closes-bug: #1799348

Change-Id: I4c43076795d28ea36f9e1d165e56abb110c5b544

Change-Id: Iedfad564f834504fa1f4bfd935cd735d1d9ee65f

Change-Id: I114c582181e0c58fc5b3ce5b1735fb54a0fdd93e

Change-Id: I0412c4d15fea97cf466287a5bed62427b43df7ea
Closes-Bug: #1799243

zun-wsproxy group is used in multinode[1], but it missing from
site.yml this PS to fix this.

[1]: https://github.com/openstack/kolla-ansible/blob/master/ansible/inventory/multinode#L676

Change-Id: I3b06f15dba5b6569202b038a28fb1a2728cffd25
Closes-Bug: #1799234

If you build the docs with `tox -edocs` and then run `tox -epep8`,
it will always fail because it checks the build output from the
docs. This change ignores the build folder.

Trivial-Fix
Change-Id: Ie7c53b517b7cfff1d317cad014371c94c6212eac

Fix the path of fernet cron for centos images

Change-Id: Iedf3a8630bc3c25fd05f580980d499023bf974fa

The python-neutronclient is deprecated. We should use openstackclient
and openstacksdk for the equivalent functionality.

Change-Id: Iaf49d6b7942343104e0b40b6db89b78a793b858b

Change-Id: I5631fd12d8cd1815ba0045f3fad272066265e3f5
Closes-Bug: #1798971

Change-Id: I288fa5ea202376d481de6966150e7e050e390f03
Partially-implements: blueprint better-reconfigure
Co-Authored-By: caoyuan <cao.yuan@99cloud.net>
Closes-Bug: #1796219

By adding 'become' element, you can set ceilometer as non root user.

Change-Id: I146f3aec6b1270d40c02f4f7883c169aaa796239
Closes-Bug: #1798035

Alarm service has been moved to Aodh for a long time [1].
Therefore, we should define evaluation_interval in
aodh.conf rather than ceilometer.conf. The interval value
should be configurable as well because we can use a
custom polling config now [2]

[1] https://review.openstack.org/#/c/200593/
[2] https://review.openstack.org/#/c/572013/

Change-Id: I7adeff2dff5d6d6ae4c621e84857347995e9203a

notification_topics was deprecated. Now we use
oslo_messaging_notifications.topics option instead [1]

[1] https://docs.openstack.org/oslo.messaging/latest/configuration/opts.html#oslo-messaging-notifications

Change-Id: I9ed3cca6d25d08494e0933a1fb8a9502b07b9775

Even though Kolla services are configured to log output to file rather than
stdout, some stdout still occurs when for example the container re(starts).
Since the Docker logs are not constrained in size, they can fill up the
docker volumes drive and bring down the host. One example of when this is
particularly problematic is when Fluentd cannot parse a log message. The
warning output is written to the Docker log and in production we have seen
it eat 100GB of disk space in less than a day. We could configure Fluentd
not to do this, but the problem may still occur via another mechanism.

Change-Id: Ia6d3935263a5909c71750b34eb69e72e6e558b7a
Closes-Bug: #1794249