With the previous setting of optIn=False, users still get nagged on the
starting page to enable telemetry, let's disable completely instead.
Change-Id: I258006c09edf7e36570f6575db07cce474c2ef8b
The check condition is similar to the previous if and it can be merged
Signed-off-by: Seena Fallah <seenafallah@gmail.com>
Change-Id: I62213d91945de42ffc87ecad1e96fa4fc0760f10
In case of running mariadb role with --limit the group_by module will only include the limited hosts and other hosts that are not limited by ansible will not be included.
Using add_host will add all hosts in mariadb group to their shards group
Signed-off-by: Seena Fallah <seenafallah@gmail.com>
Change-Id: I1331698e313bd714a16fc35f38fb579d75b56370
Closes-Bug: #1947589
This reverts commit 15259002beb6b9f35f8eee6529132c6e1a126902.
Reason for revert: The iptables_firewall produces warnings without it.
Change-Id: Id046a3048436c4c18dd1fd9700ac9971d8c42c57
Implement simple global variables system in docs and add global variables
KOLLA_OPENSTACK_RELEASE, KOLLA_ANSIBLE_MAJOR_VERSION and
KOLLA_BRANCH_NAME.
Closes-Bug: #1844710
Change-Id: I2c131463eaf1c51eb8768f6d90e9697c77a7833b
Signed-off-by: Adrian Andreias <adrian@fleio.com>
We have Debian support for quite a while. While binary target is not
always up-to-date (due to Debian OpenStack team policy of building only
released code, not git snapshots) source images are expected to just
work.
Change-Id: I2ed6061054bcea12d5b38974ee691e9632d32f05
Correct typo in role's playbook in order to be able to deploy
the service with customized policy file.
Change-Id: I252ffaf73dd2a649387ddacc73286b49f36dfdf2
Closes-Bug: #1948835
It seems some cases were missed in reviews and not fixed by
the previous iterations:
Ifc252ae793e6974356fcdca810b373f362d24ba5
I838e526b930d5276d3ce24f5188262af7eb33280
Change-Id: Id57da1c5024e1efc5810baca8fbe18967cf95a68
The copy job for the grafana home dashboard file needs to run
priviliged, otherwise permission denied error occurs.
Closes-Bug: #1947710
Change-Id: Ib15e961e5193af55e45a443305a96667295f3cb7
There seems to be a bug in Galera that causes
TASK [mariadb : Check MariaDB service WSREP sync status]
to fail.
One (in case of 3-node cluster) or more (possible with
more-than-3-node clusters) nodes may "lose the race" and get stuck
in the "initialized" state of WSREP.
This is entirely random as is the case with most race issues.
MariaDB service restart on that node will fix the situation but
it's unwieldy.
The above may happen because Kolla Ansible starts and waits for
all new nodes at once.
This did not bother the old galera (galera 3) which figured out
the ordering for itself and let each node join the cluster properly.
The proposed workaround is to start and wait for nodes serially.
Change-Id: I449d4c2073d4e3953e9f09725577d2e1c9d563c9
Closes-Bug: #1947485
Add file to the reno documentation build to show release notes for
stable/xena.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/xena.
Sem-Ver: feature
Change-Id: I5ec222dde45ed36b70547f4d03612e91fc2ea02e
This change updates documentation, examples and tests to support
Ironic inspection through DHCP-relay. The dnsmasq service should be
configured with more specific format set in the variable
``ironic_dnsmasq_dhcp_range``. See the dnsmasq manual page [1].
[1] https://thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html
Change-Id: I9488a72db588e31289907668f1997596a8ccdec6
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
