Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=kilo-eol 2015-05-14T18:39:55+00:00 2015-05-14T18:39:55+00:00 Daneyon Hansen danehans@cisco.com 2015-05-12T19:11:40+00:00 urn:sha1:a171f7a9177a8602221a2854e1e1ade4adabdd75 Previously, vnc was not completely working properly because nova.conf config flags were not properly implemented in t he correct containers. This patch moves the nova.conf config flags for vnc to the proper containers. Additionally, the patch modifies the proxy client ip param to be consistent with the param within nova.conf and adds all the novnc params to docs. Change-Id: I1944baca64ccd113bbca582784b08f90dc0eff69 (cherry picked from commit fa51eb4b5377e4725c0438fbfe85cdacdab8b3fe) 2015-05-07T16:18:34+00:00 Daneyon Hansen danehans@cisco.com 2015-05-07T16:18:34+00:00 urn:sha1:8b6d7b44b8a5adb6078ab3ffa1ddec67968e5699 Previously these services would not start because the start script requires the associated log file to exist. The default settings for these 2 log files are blank causing the failure. Since the log files are not required for the services to start, this patch removes the parameter requirement from both start scripts. Change-Id: I84d3d128728075e52282b49d9df229917a34a7b5 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-05-06T20:32:38+00:00 Harm Weites harm@weites.com 2015-05-04T22:37:23+00:00 urn:sha1:5ffc66cd69e1cda087056da25ab25548dacb1d32 All VNC-specific configuration bits are moved from nova-api-base to nova-compute and the new nova-novncproxy and nova-consoleauth containers. The compose specification has been updated to reflect this. A future patch will make the desired backend configurable (spice/vnc). Change-Id: I8b64abf125fd1ecd7d3463515e3717dd9bd60420 Blueprint: novnc-container 2015-05-06T16:58:43+00:00 Steven Dake stdake@cisco.com 2015-05-05T00:26:30+00:00 urn: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 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-07T03:25:18+00:00 Steven Dake stdake@cisco.com 2015-03-28T15:11:34+00:00 urn:sha1:a87980e5c21b17a60ba46cb53208140143ed8b15 The EXPOSE options will create a local docker-proxy. This is unnecessary with --net=host mode. The docker-proxy adds about 20 microseconds of latency. Add documentation to the specification to indicate where to find the ports that are exposed by the services in case someone were to desire to add EXPOSE back to the Dockerfiles. Change-Id: I398e922fe096d6022a2d5985bb92498f89a5ea31 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