The Monasca Log Transformer takes raw, unstandardised logs from one
Kafka topic, standardises them with whatever rules the operator wants
to use, and then writes them to a standardised logs topic in Kafka. It
is currently implemented as a Logstash config file.

Since Kolla does a fairly good job of standardising logs, this service
does very little processing. However, when other sources of logs
are used, it may be useful to add rules to the Transformer, particularly
if it's not possible to standardise the logs at source.

Ingesting the logs from this service with Fluentd will be covered under
a different commit.

Change-Id: I31cbb7e9a40a848391f517a56a67e3fd5bc12529
Partially-Implements: blueprint monasca-roles

Kolla Ironic reference point out enable booting via iPXE by setting
"enable_ironic_ipxe" to "true" in "/etc/kolla/globals.yml", but there
is no enable_ironic_ipxe option exists in globals.yml.

Change-Id: I5794fc5a7d236f7f486011f53366a5b3f4c59731

Change-Id: I8b8631e1c215580dd7711a0c0b3683b06ddc47d3

Other lists of servers have the postfix _servers. To be consistent
this change uses the same format for Kafka.

Change-Id: Ia595f2ab485904e76fb76211f6715a7c019886ea
Partially-Implements: blueprint monasca-roles

Change-Id: I751c3901b831aaed03b88d36184cd9cc5df1789b
Closes-Bug: #1779110

the zun is need kuryr to be enabled[0], add it into
prechecks is a good idea.

[0]: https://docs.openstack.org/zun/latest/install/compute-install-ubuntu.html#install-and-configure-components

Change-Id: I4f46907c9b47b9108a9aa7bfbd668b833db420af

It is not always convenient to use the the given
admin project and admin user; especially when some clouds
use different user and project for there keystone 'admin'

This allows setting the variables for these users to something
else, and defaults them to there current values of 'admin'.

Change-Id: I22b79a30f01c90a92ecc0974886edf3791518f2f

By default, kolla configure docker to use an insecure connection
with the private registry. If we want to use SSL verification we need
to add an option.

Change-Id: Id1805c9cfeb499da9bb56c70028f14c6f8bb20b6

To destroy a kolla-ansible environment a confirmation string should be passed
along with kolla-ansible command: kolla-ansible destroy -i ~/multinode \
--yes-i-really-really-mean-it
However, this string is not evaluated right and just putting --y starts destroy
process: ./kolla-ansible destroy -i ~/multinode --y

Change-Id: I5983f9c7fd3859d60741dfd23ad10dfd91872eeb
Closes-Bug: #1701313

In this way, keyring caps is updatable.

Change-Id: Idf7f222645b5073e2c72d59eecf3d47b3f1dc6ba

Change-Id: I1b0e1df0e91b7a4abc408ee4b0852e1278e441ef

the zun-wsproxy image is exists in kolla[0], but kolla-ansible
missing, this ps to add it.

[0]: https://github.com/openstack/kolla/tree/master/docker/zun/zun-wsproxy


Co-Authored-By: ZhijunWei <wzj334965317@outlook.com>

Change-Id: I89ef3463dfa5df8cf2d963ff0f0c7ddc382fc79b
Closes-Bug: #1765728

Change-Id: I0e3c098db9d1f0a8fda383910c05ed5efc929994

As reported in the bug, these can grow to 10s to 100s of GB
in a month. To reduce the chance of filling the disk and
bringing down the control plane this change defines
an expiry time.

Closes-Bug: 1720113
Change-Id: I508aad1f515d5108a3d08c90318b70d0a918908c