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-05T02:10:22+00:00 urn:sha1:68594d873f7a1006fab5d360cb7c55bbb7ed421b This represents the Juno release of the images. Partially-implements: blueprint port-kilo Change-Id: I2837ec25a2aa093b7fff7519f3ed608ec93736bf 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-03-28T20:54:43+00:00 Sam Yaple sam@yaple.net 2015-03-27T23:55:00+00:00 urn:sha1:1dcd904d27593e818721fe6dc143cd384eb9a6d9 We have to overlay the /lib/modules folder from the host to properly `modprobe` from within a container. We don't have to give it write permissions however, so the docker-compose volume is mounted in as 'ro' Change-Id: I95101136dad56e9331d8b92cd394495f7bd0576a 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 2015-03-20T17:05:03+00:00 Steven Dake stdake@cisco.com 2015-03-20T02:01:24+00:00 urn:sha1:5bfc3e11f6d36204d88e085d9ed9df6c941f7dd2 Without pid: host, nova-compute and libvirt fail to operate correctly together. I don't understand why, and I wish it weren't so, but it means folks will have to install docker-compose from my personal github account until the pull request is merged upstream. Change-Id: I24e55405139c831f2df246f54c5b6fd39d00656a 2015-03-17T18:45:25+00:00 Steven Dake stdake@cisco.com 2015-03-16T17:58:19+00:00 urn:sha1:2f2d0ef0cc569bc5ce78d71cc9ce2f34e718ab18 The host directory is /etc/libvirt/nwfilter, not /etc/libvirt/nwfilters Change-Id: If7dc4a8028477d938aaa0dba20b79589217ceaf9 2015-03-13T03:51:14+00:00 Ian Main imain@redhat.com 2015-03-12T20:20:13+00:00 urn:sha1:c2bdaadd7cdff5c428b8169f5ffa6da23a4ea072 This one uses the single environment file and has a few changes to mounted directories. Change-Id: I047a92b5ab89aa9b3b75213c19e05eb84d48adf6