Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=kilo-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-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-03-27T23:52:48+00:00 Sam Yaple sam@yaple.net 2015-03-27T23:48:49+00:00 urn:sha1:986edf4a97d9c98cd784067275c426f03df52f77 When using ';' this can allow the previous command to fail and while the docker build proceeds without realizing a command failed. Switching to '&&' allows the exit code to make it to the docker build command and the build to fail appropriately. Change-Id: Idd0991ed4549542bb10d27da1a0a025d0503b6c1 2015-03-02T05:08:06+00:00 Martin André martin.andre@kvhasia.com 2015-02-26T06:00:42+00:00 urn:sha1:0764fd7dea3f56627bb42e285cfb818cce08229e By changing the PREFIX variable in the .buildconf one is now able to build docker images from different bases. For example, add the following line to your .buildconf file to build CentOS based images: PREFIX=centos-rdo- Default base image is Fedora. For now only RH family is supported. Additionally, changing the namespace either with the NAMESPACE variable in .buildconf or via --namespace commandline option now changes the source namespace as well from the default kollaglue one. Implements: blueprint multi-baseos Co-Authored-By: Steven Dake <stdake@cisco.com> Change-Id: I3964cd2292789ea883a1f2d2738a5731a4fff49b 2014-11-25T22:23:42+00:00 Pradeep Kilambi pkilambi@cisco.com 2014-11-25T22:23:08+00:00 urn:sha1:6bd1f5a3a70b00d69806314812376257980ed0b4 For some reason forking the mongod process seems to cause issues when the container comes up. If i remove this and run the images with detach and publishall flags i can connect to mongo instance. Change-Id: I0b7193e6369084e3aeec857607dda9c3f235770d 2014-11-14T18:06:37+00:00 Pradeep Kilambi pkilambi@cisco.com 2014-11-14T16:16:29+00:00 urn:sha1:904b5c425698ab4a32d5928a78c1a6f525856ed6 Implements: blueprint kube-mongodb-container Change-Id: If76f6c0be90c3025933795d262304a10bf1a880d