Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=master 2016-11-16T04:34:17+00:00 2016-11-16T04:34:17+00:00 Steven Dake stdake@cisco.com 2016-11-16T02:01:25+00:00 urn:sha1:3fcef82946f7053affcfb0b1b3ef4292beb9fa95 Change-Id: I5396e4b9927d3e65b6aa4185238a43a4765a996b 2016-05-13T12:12:25+00:00 Waldemar Znoinski waldemar.znoinski@intel.com 2016-05-06T14:51:55+00:00 urn:sha1:a2c2eba34fb7077346d651918dfb22a53a63cb00 This change makes each step of the kolla deployment aware of the port database was configured to listen on. It defaults mariadb_port to database_port. Change-Id: I8e85d5732015afc0a5481cb33e0b629fdfa84a1b Closes-Bug: #1576151 DocImpact 2016-02-05T15:04:37+00:00 Jenkins jenkins@review.openstack.org 2016-02-05T15:04:37+00:00 urn:sha1:b891afd64c7bcd351cde324591dc4d915f550a51 2016-02-02T18:12:15+00:00 SamYaple sam@yaple.net 2016-01-29T16:40:54+00:00 urn:sha1:80b7266ed1b10fb302a507d250d28a964ce14e49 This change is needed for clarity. We have a kolla-ansible script. We have a kolla-mesos repo. We plan to have a kolla-ansible repo. Already we have had far too much confusion about whether we are talking about the container or the project. Naming this kolla-toolbox eliminates all of that confusion and its probably a bit more accurate of a name too. Closes-Bug: #1541053 Change-Id: I8fd1f49d5a22b36ede5b10f46b9fe02ddda9007e 2016-02-02T07:03:08+00:00 Allen Gao wanlong.gao@easystack.cn 2016-02-02T07:03:08+00:00 urn:sha1:54aa896735a9efc9a24eeb30732f91ec5b971d6d Change-Id: Iffb12c8e22724ba779e4ce80204710513875e725 Partially-Implements: blueprint upgrade-kolla Implements: blueprint upgrade-murano 2016-01-28T20:26:41+00:00 SamYaple sam@yaple.net 2016-01-28T02:04:02+00:00 urn:sha1:6d8959a962c038269653b00ba7ddb491c597e49a Add bootstrap label to all bootstrap containers to ensure that when the a new container is launched a difference is seen between it and the bootstrap container since we cannot rely on ENV variables for this. This only affects mariadb at this stage, but it is needed to ensure rabbitmq works when we switch to named volumes. Change-Id: Ia022af26212d2e5445c06149848831037a508407 Closes-Bug: #1538136 2015-12-31T16:38:56+00:00 SamYaple sam@yaple.net 2015-12-26T00:37:02+00:00 urn:sha1:2f03fc81ec613c396cdff45697edbbe7814d632c Change-Id: I7be9c91cb31eca5dfc15e8ff0a6ab8f42c5af8dc Partially-Implements: blueprint kolla-docker-module 2015-11-23T17:24:22+00:00 Sam Yaple sam@yaple.net 2015-11-05T12:15:49+00:00 urn:sha1:970617b80af8532a454ff1c92d1714048e584703 Additionally remove tty from the container cleanup docker section. It was added in a sed in a previous patchset by serves no purpose. Change-Id: Ib617870616bca687f72ffaa44b2e9a3a11ef1011 Partially-Implements: blueprint cleanup-playbooks 2015-11-23T17:09:36+00:00 Hui Kang kangh@us.ibm.com 2015-11-07T20:11:40+00:00 urn:sha1:790bf336d5e082c5c079bfb681f9509188eae72f The bootstrap tasks could be started on any node listed in the site.yml The issue is that all the tasks must run on the same node, and the only node that all the tasks can run on is the 'api' node due to needing to start the bootstrap container which binds in the configs. delegate_to is required to ensure that the proper node gets the task. Co-Authored-By: Sam Yaple <sam@yaple.net> Change-Id: Ica04ab366777a571a92212ac22c482f1881d4ecd Closes-Bug: #1513598 Related-Bug: #1513439 2015-11-09T10:47:15+00:00 Sam Yaple sam@yaple.net 2015-11-07T16:40:17+00:00 urn:sha1:6b283430173caf0d0ecabce55dfa62abfe68787a database_user_create was not correctly referenced when parsing the variable names. This could never actually lead to a situation that reported a false change, but it could break an operation if you were using the --step option with ansible and skipped the database create task. TrivialFix Backport: Liberty Change-Id: Idf69fffcc3814f509448ccea11b7d175f074ccf1