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-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-07T14:50:47+00:00 Jenkins jenkins@review.openstack.org 2015-04-07T14:50:47+00:00 urn:sha1:7a29958949f04269956172817ca9ed39d1fb3802 2015-04-06T18:09:19+00:00 Steven Dake stdake@cisco.com 2015-04-01T21:03:14+00:00 urn:sha1:1a530dca4c7593d8d6ea7f1b70491b43145d5b2c the libvirtd package "Provides" wwas removed from the libvirt packaging. To workaround this problem just install libvirt-daemon in CentOS 7.1 or Fedora 20+. WIthout this change, an install of libvirtd does not actually install libvirtd. The yum tool will not fail if libvirtd is specified so we weren't catching this in the build. Change-Id: I81e64f6f659aa0466369dad4b0574ebb24c99555 2015-04-01T13:35:34+00:00 Sam Yaple sam@yaple.net 2015-03-31T15:45:57+00:00 urn:sha1:2f0f37f97b575fe7b863d086b00f8f5c470d362a Loads ebtable_nat, ip6_tables, ip_tables, and the appropriate kvm module if the cpu supports it. Change-Id: I69995b06da6da4169a2f0d207608543820d8a89e 2015-03-31T00:12:42+00:00 Steven Dake stdake@cisco.com 2015-03-27T20:38:10+00:00 urn:sha1:93e164d97317bb4ca56bc734d95764777c838e68 In a native QEMU environment there is no /dev/kvm. Change-Id: I4d0eb32fd6fad3a4c9c15c7c2b12430b2e4db154 2015-03-30T13:57:03+00:00 Steven Dake stdake@cisco.com 2015-03-27T20:35:42+00:00 urn:sha1:fe380064bfe8fa5d6e43f277c3e3e2f7e5077d84 libvirt is compiled with lxc support. On Ubuntu hosts, without this file libvirt is nonusable. The container exits immediately. Change-Id: Ifbc2d75defe082cbe3b80b1821799f1f965c2a85 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-22T15:54:53+00:00 Steven Dake stdake@cisco.com 2015-03-21T22:13:32+00:00 urn:sha1:f4fd47dc2cdb5eee6ac366788c25c2a6a21ca362 A data volume container is far superior to bind mounting the host's shared directories. It preserves the idempotency, immutability and declarative properties of the containers. The way this works in practice is that a data volume container is created. Then when the containers start they use LVM to access the filesystem where /var/lib/docker is contained. Then the container startup logic bindmounts the data volume stored on the host filesystem in /var/lib/docker/vfs/dir/ID. This prevents people with access to the host operating system from damaging the contents of the data container. It does mean that now we must use tools/stop to stop our containers rather than tools/cleanup-containers -f. This is a containers best practice. For more details see: https://docs.docker.com/userguide/dockervolumes/ Big credit goes to Danyeon Hansen for seeding this idea in the mariadb containers. Note occasionally docker-compose start/stop seems to not want to stop a container. This bug needs to be addressed upstream separately from our utilization of this best practice. Change-Id: Iaa1419f606e1b1b7a7560a095c49e79d643164f1 2015-03-20T22:00:54+00:00 Daneyon Hansen danehans@cisco.com 2015-03-20T22:00:54+00:00 urn:sha1:c49613ad0a4ec1793819c8f6c4780fbaa224ad4f Previously, the nwfilter daemon/conf pkgs would need to be installed on the host. Compose would then mount the host DIR to the compute containers. A more efficient approach is to simply install the nwfilter config/daemon in the libvirt container. Both appoaches address the following error when booting an instance: 'no-mac-spoofing' is missing Change-Id: I81b446d198920473bf99b97ef5eac6ef5ee85024