openstack/kolla.git/docker/mariadb/extend_start.sh, branch train-eol

Support customising MariaDB log directory

2019-08-08T16:17:02+00:00

This retains the default, but allows the directory to be customised if required. This is useful, for example, when using Kolla Ansible to deploy multiple instances of MariaDB. Partially Implements: blueprint support-nova-cells Change-Id: I042fbe140ee84f2ed72e27635be247cb145aac5f

MariaDB upgrade: specify host and port

2019-03-23T10:16:19+00:00

While mysql_upgrade seems to work on CentOS images without specifying a host and port, it fails on Ubuntu without these. Change-Id: Ie140de57c4fe2f2e4db6a90c18e3535d9cc71ff2 Related-Bug: #1820325

Fix MariaDB 10.3 upgrade

2019-03-18T19:42:36+00:00

There are a couple of issues with the mariadb image currently. 1. it doesn't include mysql_upgrade on CentOS/RHEL. It is necessary to run this after an upgrade of MariaDB. This is fixed by installing mariadb-server-utils. 2. it inherits the standard dumb-init entrypoint from the base image, which includes a --single-child argument. That causes signals to be forwarded only to the process executed by dumb-init, which in the case of kolla-ansible is mysqld_safe, however mysqld_safe ignores SIGTERM. After a timeout, Docker then forcibly kills the container. Executing dumb-init without --single-child ensures the TERM signal is sent to mysqld, allowing it to shutdown gracefully. Change-Id: I1a450736721863b91be1ea3d3c8948990de9fdeb Closes-Bug: #1820325

Add --wsrep-new-cluster option back in the bootstrap_db function

2018-01-22T09:36:22+00:00

Ia2acb09e877a586243fc1acb49d8d140cf27d7b5 removed the "--wsrep-new-cluster" option and left "--wsrep-on=OFF". But it seems "--wsrep-on=OFF" won't work with mariadb 10.0. and In Ubuntu, we are still using mariadb 10.0. Try to add --wsrep-new-cluster back Change-Id: I4d382d1b9c83def62dc85a773580c8c6b2500f68

Fix MariaDB bootstrap for 10.1 version

2018-01-04T01:31:22+00:00

Option "wsrep_on" behaves differently between 10.0 and 10.1 [1]: "Before MariaDB 10.1, even though this variable is ON by default, its value get automatically adjusted based on whether mandatory configurations to turn on Galera replication have been specified. Since MariaDB 10.1, it is set to OFF by default and must be turned on to enable Galera replication." So on MariaDB 10.0 although wsrep_on set to OFF, its value will automatically adjusted to ON because wsrep mandatory configurations are set. Whereas on MariaDB 10.1, it will failed at galera provider 'wsrep_ready' checking because wsrep_on is set to OFF. We can set wsrep_on to ON to handle both 10.0 and 10.1. But, the point is that the cluster bits, which are creating a cluster and wsrep_ready checking, are no need at bootstrap stage. At bootstrap stage it mainly do two things: Creating required system DBs (by mysql_install_db) and securing the mariadb (by bootstrap_db). After the bootstrap stage, it will create a cluster when starting the first node. [1] https://mariadb.com/kb/en/library/galera-cluster-status-variables/#wsrep_ready Partial-Bug: 1740060 Co-Authored-By: Steven Dake Change-Id: Ia2acb09e877a586243fc1acb49d8d140cf27d7b5

Fixing mariadb bootstrap failure in kolla-kubernetes

2017-07-16T19:15:47+00:00

With latest master, mariadb is failing to bootstrap in kolla-kubernetes cluster. The issue is with the name of mysql pid file. When it is not forced in the command line, in kolla kubernetes it gets created in the form of mariadb-init-element-xqg4b.pid where mariadb-init-element-xqg3b is pod name, but bootstrap scripts explicitely checks for mysql.pid. Change-Id: Ic0ee577d73d196ef40354efa51ca3ba60bf4e125 Closes-Bug: #1704671

Remove sudo operations that are no longer necessary

2017-05-27T04:40:31+00:00

set_configs.py has logic to handle chown of directories. Simplify the codebase by removing these unnessary chowns. Further the chowns cause some forms of NFS backed storage to not work properly. Change-Id: I8df95d06b1010778deb3e2a3065aaab26ed2eb6a Closes-Bug: #1693973

check mariadb galera status in every loop.

2017-03-27T09:04:17+00:00

in extend_start.sh, if Mariadb galera is not ready at first time, it will sleep 60s and then exit 1. we should check it`s status every time in the loop. Change-Id: I89174969687eecbf467ca3cad9aad1bfbfb8c4fe Closes-Bug: #1676316

Disable networking during bootstrapping

2016-12-31T21:17:16+00:00

There is no reason to have networking active while bootstrapping the initial mysql folder structure. It is an additional attack vector that serves no purpose. Change-Id: Ia636ba9f563dbfb969dbfb613198c98748ee8a3c

Wait the wsrep_ready to be ON in mariadb

2016-11-07T15:30:35+00:00

Mariadb galera will be ready only when wsrep_ready to be ON, rather then wsrep_cluster_status is equal to Primary. Closes-Bug: #1639838 Change-Id: I9ef60a39a195057eeee0404a39b174cc8feed793