Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=juno-eol 2015-05-06T16:58:43+00:00 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-05-06T12:33:55+00:00 Steven Dake stdake@cisco.com 2015-05-02T16:26:58+00:00 urn:sha1:61cc479e90d321f7eac71749ebe3fe96081c1e05 Rather then upgrading to a specific version of OpenStack, just upgrade to Head. This works for both juno and kilo. Change-Id: I6305218eabd7de0878e24c8fdae968ac6d612175 Partially-implements: 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-15T01:55:48+00:00 Steven Dake stdake@cisco.com 2015-04-15T00:44:02+00:00 urn:sha1:095fbd7d7c07984141bda1d31779a3b046c6be90 The nova-config.sh script was exiting because of incorrect shell syntax. The correct syntax for a regex search is [[ haystack =~ needle ]]. The .*needle.* is unnecessary. I think this shell script exited because a period was missing. Change-Id: I3aca5e0729eb5fedbe9ecb4d75ed85d5a1c7815a 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-13T07:34:12+00:00 Daneyon Hansen danehans@cisco.com 2015-04-07T19:34:40+00:00 urn:sha1:ed107a5e26f35351a178c12eed5cd38c086409db Previously, the agents ran in seperate containers. Since some of the agents create and use network namespaces, runnning them in seperate containers has become a challenge. This patch adds neutron agent support in a single container. Partially Implements: blueprint compute-operation-neutron Change-Id: If4f893abd50d90b58e8435ec2659870dce36951c 2015-04-10T03:11:23+00:00 Daneyon Hansen danehans@cisco.com 2015-03-26T19:47:56+00:00 urn:sha1:2f2bb366e0aa856803c0d21a7a541802d814d180 Adds neutron-server components of the neutron container set. Partially Implements: blueprint compute-operation-neutron Change-Id: I63525ae85f4ead4e010cdb9b6bc8059bb9d252e7 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