From abbee7dbcac828840a7f0cca914c8d9a570180d1 Mon Sep 17 00:00:00 2001 From: Michal Stachowski Date: Fri, 19 Jun 2015 16:14:34 +0200 Subject: Galera container This changes are providing support for galera cluster. It's important for project to has got support for database cluster as a one of the steps to providing High Avability(HA) in Kolla project Change-Id: If51bb88ab05972d3b8aa8abbbbd2a5480213a10e Implemented: blueprint galera-container --- docs/integration-guide.md | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'docs') diff --git a/docs/integration-guide.md b/docs/integration-guide.md index 4794508ff..eb7c475b1 100644 --- a/docs/integration-guide.md +++ b/docs/integration-guide.md @@ -56,6 +56,11 @@ all containers. This allows a simple method of ensuring every type of node ADMIN_USER_PASSWORD= - The admin user password ADMIN_TENANT_NAME= - tenant name FLAT_INTERFACE= - nova networking flat interface device name + DB_CLUSTER_BIND_ADDRESS= - Defaults to 0.0.0.0. Listening address for database. + DB_CLUSTER_INIT_DB= - Defaults to false. Configures if Galera should be initialized. + DB_CLUSTER_NAME=. Defaults to kollacluster. Galera cluster name. + DB_CLUSTER_NODES=. Defaults to none. List of nodes in Galera cluster, separated by comma(IP address or hostname). + DB_CLUSTER_WSREP_METHOD= - Defaults to mysqldump. Galera replication method. GLANCE_API_SERVICE_HOST= - address where glance API is running> GLANCE_DB_NAME= - DB name of glance service GLANCE_DB_PASSWORD= - -- cgit v1.2.3