Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=kilo-eol 2015-05-06T20:54:04+00:00 2015-05-06T20:54:04+00:00 Steven Dake stdake@cisco.com 2015-05-02T16:14:01+00:00 urn:sha1:747f80e9281ca777dd5ab3de8d3aaf7f33f022c9 In Kilo, nova no longer reads the config files automatically. They must be specified in the command line to run the nova-* tools. Change-Id: Ifbdf4fd3f952f7bb65e9937b46cf9b96e262c3b0 Paritally-Impleents: blueprint port-kilo 2015-04-27T05:26:37+00:00 Chen Zhiwei zhiwchen@cn.ibm.com 2015-04-27T03:59:55+00:00 urn:sha1:76c1fe63717492fbe84b86c7f5c87b1b042cf446 Unify the shell to bash in all Kolla scripts. Change-Id: Ib9591b2f8f344eb88455c5e9b7ecf2164fb5960a Implements: blueprint use-bash-shell 2015-04-13T17:17:52+00:00 Daneyon Hansen danehans@cisco.com 2015-04-10T06:16:46+00:00 urn:sha1:882a859ff5c7b699887b4b46c804faa02e8ac720 Previously, check_required_vars was requiring log file variables to be set in openstack.env. This would cause an error when starting nova/neutron containers that used default (blank) log file settings. Since the log files are not required for the services to start, the default log files are left blank (without a value in the K/V pair). This patch removes the log_file variable for check_required_vars in each nova/neutron script. Change-Id: I169baab28f63a0e0ae06c8aef21b5e8d3155bdda 2015-04-07T19:13:29+00:00 Daneyon Hansen danehans@cisco.com 2015-04-01T18:38:46+00:00 urn:sha1:0b671ad58d31dc3c3704a35a9ef0c17af0834e72 Previously, logging was hard coded into the nova and neutron containers. This patch creates two common params for logging: DEBUG_LOGGING VERBOSE_LOGGING and sets default values of verbose=true and debug=false. This patch implements logging for Nova and Neutron. Add'l OS service config scripts and images will need to be updated to use the logging params. Change-Id: I03d48005d5b4789aa3c519879a20d963ef1cbaa3 2015-04-01T07:39:44+00:00 Martin André martin.andre@kvhasia.com 2015-03-30T01:14:03+00:00 urn:sha1:34872c1c2f68f4a410c423ed8b615822a29ff94a In order for the `check_for_*` functions to be consumed by `wait_for`, they should notify of their success but not exit. As a consequence, the previous behavior is restored by the fail_unless_* companion functions. With this change, it is now possible to do: wait_for 30 1 check_for_os_service_running keystone Change-Id: I16ddf8913027030c3ccb5487713d172904508fd6 2015-01-21T00:34:01+00:00 Martin André martin.andre@kvhasia.com 2015-01-19T06:06:28+00:00 urn:sha1:f4b7ae95ac24f395e8d7ddd36cba362659fd29b4 When nova-api start and the nova database hasn't yet been created, it would create it itself, preventing the migration in nova-conductor to run and making it unable to start. This commit ensures that nova-api container will not try to steal nova-conductor's job of creating the nova database. Nova-scheduler reacts differently to the missing database and simply exits with a backtrace. This commit also prevents nova-scheduler to start when the nova database cannot be found. Change-Id: Ib6f7521151815faa7a26ec1d170df5a1cdb7fd63 Related-Bug: #1335804 2014-10-17T19:46:49+00:00 Lars Kellogg-Stedman lars@redhat.com 2014-10-17T19:46:49+00:00 urn:sha1:89534f43a1a9b29707d8ac62a23e3c28226f9cf5 Change-Id: Ia0b9057887bf34423546ca36346d9253ef4c90b9 2014-10-16T18:40:26+00:00 Steven Dake sdake@redhat.com 2014-10-16T18:39:47+00:00 urn:sha1:6a5c1d8f50fd13330030095f8a0048fb462af405 Without +x, docker will not run the shell scripts and the containers exit immediately. Change-Id: I03ca231d6e46131a58c01fae0f9b65e0a3722d36 2014-10-16T15:51:59+00:00 Lars Kellogg-Stedman lars@redhat.com 2014-10-16T15:48:40+00:00 urn:sha1:b4560bd0e3e8905bba544cbb95a9dab11f1a8a15 Change-Id: I56156ed59b6678180bcb5d1bdd00233d8f339643 2014-10-07T14:59:07+00:00 Ryan Hallisey rhalllise@redhat.com 2014-10-06T14:13:16+00:00 urn:sha1:9e420ba27eac22847870553c15b92ff499eef3aa Partial-blueprint: kube-nova-container Change-Id: Ib48e6318ae458bf03510725a220332d1920cbeae