openstack/kolla.git/compose/mariadb.yml, branch kilo-eolUnnamed repository; edit this file 'description' to name the repository.
https://git.platform-os.org/openstack/kolla.git/atom?h=kilo-eol2015-05-06T20:54:00+00:00Port to Kilo2015-05-06T20:54:00+00:00Steven Dakestdake@cisco.com2015-05-05T02:28:55+00:00urn:sha1:c81b00330925d5e3f0e7ae2c2ae41c6dc8f295c1
Use kilo upstream RPM packages
Partially-implements: blueprint port-kilo
Change-Id: Ia0b4db5dc8e40c01184871e77458dc718c3c46cd
Port to Juno2015-05-06T16:58:43+00:00Steven Dakestdake@cisco.com2015-05-05T02:10:22+00:00urn:sha1:68594d873f7a1006fab5d360cb7c55bbb7ed421b
This represents the Juno release of the images.
Partially-implements: blueprint port-kilo
Change-Id: I2837ec25a2aa093b7fff7519f3ed608ec93736bf
Port to icehouse2015-05-06T16:58:43+00:00Steven Dakestdake@cisco.com2015-05-05T00:26:30+00:00urn:sha1:d30f69bc8327bf37e013c9647c99d9192eec8830
This represents making build-docker-images --release build
with the icehouse tag and causes docker-compsoe to pull from
the icehouse tag.
Partially-implements: blueprint port-kilo
Change-Id: I66b2c39abc55c0f47152dd90e696fc46b9c58f50
Tell mariadb to restart2015-03-28T15:50:23+00:00Steven Dakestdake@cisco.com2015-03-28T15:48:40+00:00urn:sha1:bbad173a0a283676d84e1a2542cbf4b9da6514ca
If a system is rebooted with kolla running, all the services will
continually restart. There appears to be some locking problem in
docker which will result in docker imploding. One problem is a
key dependency, mariadb, is never started on a reboot because it is
missing restart: always. Also restart the mariadb data container
until it returns success.
Change-Id: I599d28548ff041712d54a702c80fe36c321adf7f
Make mariadb use a data container without a bindmount2015-03-22T15:55:24+00:00Steven Dakestdake@cisco.com2015-03-21T23:17:01+00:00urn:sha1:c2b92c5e96857ea88f8b01df8a81b6418087a259
A data container is meant to operate without bindmounts.
Change-Id: I2624a63fd75db7ed8050054c17e19885f8a7ac8a
Co-Authored-By: Daneyon Hansen (danehans@cisco.com)
Implements: blueprint Implement a database container set2015-03-20T16:17:51+00:00Daneyon Hansendanehans@cisco.com2015-02-25T05:49:40+00:00urn:sha1:5547b5fe786b7491d2e33f92c4082535f2bb56cf
Previously, the database container was configured for use with
Kubernetes. This patch removed any k8s dependencies, adds a script
to manage mysql server.cnf settings and splits data and app
containers. Splitting the containers provides additional
portability and operational efficiencies compared to host mounts.
Change-Id: I80656450c02dda5f2959d187eec20d5877dc54a2