Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=train-eol 2020-12-18T08:45:08+00:00 2020-12-18T08:45:08+00:00 abraden C-Albert.Braden@charter.com 2020-10-15T19:02:43+00:00 urn:sha1:c213921fddbfca13277d88ebaa35f8f34cd4809f backup_full() saves the history name in $BACKUP_DIR/last_full_date. backup_incremental() attempts to read from $BACKUP_DIR/last_full_date into $LAST_FULL_DATE. After the read attempt; if $LAST_FULL_DATE is zero length then $(date +%d-%m-%Y) is used. Change-Id: I4172b814d5d95ae3debbc1cf3feaeee2e2bec9bd Closes-bug: 1897948 (cherry picked from commit ccfe65b5f7fe437141f342421488c176038fddb0) 2020-05-17T13:02:14+00:00 Marcin Juszkiewicz marcin.juszkiewicz@linaro.org 2020-04-20T13:13:31+00:00 urn:sha1:bd21ac14d73e01c97a780ec8c12fb99e0b8c4b10 RDO builds of stable/train for CentOS 8 went into phase when we do not need to use delorean builds. EPEL is disabled like it is in Ussuri (RDO packages may conflict with it). Erlang for RabbitMQ is used from CentOS 8 'rabbitmq-38' repo while RabbitMQ is still 3.7.* from same place as usual. 'python3-pika' is dropped from openstack-base as it is EPEL only package and is not used by any image (dropped in Ussuri in https://review.opendev.org/#/c/710003/ patch) AArch64 is not supported until CentOS 8.2 release. Change-Id: I9d3ed54f4d10ef7ad2d52ed3aeca15f3968cd163 2019-10-25T11:35:18+00:00 Mark Goddard mark@stackhpc.com 2019-10-25T11:33:01+00:00 urn:sha1:88f374c914c4d6709a1edf407a912c8cf566038b Without this, a failure in mariabackup would be ignored due to the pipe to gzip. Change-Id: I84536b302991e8fb04d5fa67ea266bc428437ce1 Related-Bug: #1843043 2019-10-23T14:43:26+00:00 Mark Goddard mark@stackhpc.com 2019-10-23T13:08:35+00:00 urn:sha1:65b27d772be32738a8508ea8e6c07f74f229cdb7 After switching from innobackupex to mariabackup [1] for database backups, the kolla_mariadb_backup.sh script was not modified to account for the difference in arguments between innobackupex and mariabackup. There is a compatibility mode, the documentation [2] for which covers some of the differences. The following have been changed: - Add explicit --backup argument, now required - Remove './' positional argument - not required with --stream - Remove --no-timestamp argument - only supported in innobackupex compatibility mode - Remove --incremental argument - implied by --incremental-history-name - Remove deprecated --compress argument, which requires qpress to be installed (it is not). The stream is now passed through gzip instead [3] [1] https://mariadb.com/kb/en/library/mariabackup-overview/ [2] https://mariadb.com/kb/en/library/mariabackup-options/#-innobackupex [3] https://mariadb.com/kb/en/library/using-encryption-and-compression-tools-with-mariabackup/ Change-Id: I67cff47cbf56570b8eaeb66092dd87c2769fc8a6 Closes-Bug: #1843043 2019-09-12T12:14:08+00:00 Marcin Juszkiewicz marcin.juszkiewicz@linaro.org 2019-09-12T09:48:07+00:00 urn:sha1:016c0f577c535def40dd32ddf41e6cb145a2f9b8 XtraBackup started failing to install on Ubuntu and does not support MariaDB 10.3 version. Related-Bug: #1843043 Change-Id: I9cf62c8e03a02574d85e5349df1d23a51d4c99be 2019-08-31T06:35:43+00:00 Michal Nasiadka mnasiadka@gmail.com 2019-08-29T09:06:46+00:00 urn:sha1:761d58717731dd72ce50f6dbb6cd8e2b5e608060 MariaDB in Ubuntu packages is backlevel (10.1). Devstack gates are tested on MySQL 5.7 which is not compatible with MariaDB 10.1. Neutron recently introduced a db migration that breaks on MariaDB 10.1, but works on MariaDB 10.3 [0]. Bumping up version to 10.3 on Ubuntu to match CentOS (RDO) version. [0]: https://review.opendev.org/#/c/677221/ Closes-Bug: #1841907 Change-Id: I16e4c40208912691e3015bfe2065ea0ce2358edb 2019-08-08T16:17:02+00:00 Doug Szumski doug@stackhpc.com 2019-08-08T14:14:34+00:00 urn:sha1:99de712a2dd49593daba09accac7811bc51b56ad 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 2019-04-03T08:27:45+00:00 Rabi Mishra ramishra@redhat.com 2019-03-29T02:15:19+00:00 urn:sha1:fb4cb9efda5a522ba0d837047385b61275d09150 Usage of dumb-init can also be disabled from cli with `--nouse-dumb-init` when building images. Also moves ENTRYPOINT outside of dumb_init_installation block. Change-Id: Id32d54fc9913b83cf121ede5a5e265e0772062ae Related-Bug: #1821970 2019-03-23T10:16:19+00:00 Mark Goddard mark@stackhpc.com 2019-03-23T10:16:19+00:00 urn:sha1:3c9c72bad0b1ed4b61a5ed02a36c01c1455dc9bf 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 2019-03-18T19:42:36+00:00 Mark Goddard mark@stackhpc.com 2019-03-18T15:14:01+00:00 urn:sha1:3075685d01554447144f37201f241f7f1ff1ad3b 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