Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=master 2015-05-15T06:32:22+00:00 2015-05-15T06:32:22+00:00 Sam Yaple sam@yaple.net 2015-05-13T11:46:24+00:00 urn:sha1:13062e23e86b5d86020949754540460cb5b0b4fe As a restructure, nothing is changed from the original behaviour and naming despite the file structure changing. The symlinks to build had to be updated generating lots of "deleted" and "new_file". The new structure is: docker/${base_distro}/${type}/${container} base_distro == centos, ubuntu, fedora, etc type == source, binary, rdo type rdo is a symlink to binary for backwards compatibility Two new flags are added to the build-all script to support the ability to support different base distros and a flag to support binary or source containers. There are several added folders that are empty to hold the directory structure for future containers of these types. To use a prefix other than centos-rdo- you can set PREFIX in the toplevel directory .buildconf file Change-Id: Ifc7bac0d827470f506c8b5c004a833da9ce13b90 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-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-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 2015-03-06T00:44:02+00:00 Jenkins jenkins@review.openstack.org 2015-03-06T00:44:02+00:00 urn:sha1:c3114b961086be034c6674a916361e2033c87986 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 2015-02-28T04:23:20+00:00 Steven Dake stdake@cisco.com 2015-02-24T07:32:03+00:00 urn:sha1:7eca70b1a6dfe58288dcdeae12c99dfab69f890c This imports sdakes' nova-docker codebase to show that atomic upgrades work atleast with nova networking. This has many corrections. For more details read: http://sdake.io/2015/01/28/an-atomic-upgrade-process-for-openstack-compute-nodes/ Implements-blueprint: blueprint libvirt-container Partially-implements; blueprint container-set-compute-operation-nova Change-Id: I858ea113c5656b6da5d2fd13502fecdbd085c8da