Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=version-m2 2014-11-17T17:47:40+00:00 2014-11-17T17:47:40+00:00 Daneyon Hansen danehans@cisco.com 2014-10-25T03:53:36+00:00 urn:sha1:05f352a12556e08ecf10155399b29360c491b76e Previously, the nova-network service was not fully functional. This patch adds multi-interface support to the nova-network container. The eth0 configuration is moved to a bridge (br100 per nova defaults), and configures eth0 and eth1 as bridged interfaces. eth0 is used for the nova-flat network and eth1 for foating-ip's. This model is identical to typical bare-metal nova-network deployments. The patch depends on the following patch to kube-heat template that provides multiple interfaces per minion: https://github.com/larsks/heat-kubernetes/pull/8 Rebased. Fixed merge conflict with k8s/pod/nova-compute-pod.yaml Change-Id: Ieb59f397981a226555ce55ca621ef578b987e3c6 2014-10-22T15:11:31+00:00 Lars Kellogg-Stedman lars@redhat.com 2014-10-22T14:57:13+00:00 urn:sha1:277f2448e8fde089cfed0a3dfe2e74dc265af447 Remove individual MAINTAINER information from Dockerfiles. Change-Id: I777df5cde049599dc786176e1d5b4b9597f0b334 2014-10-21T20:05:36+00:00 Lars Kellogg-Stedman lars@redhat.com 2014-10-21T19:56:42+00:00 urn:sha1:d41b9dc5ac6b3a41a88baef9b83e9ccf4779ac2a this patch creates a dummy interface ("flat0") and uses that for flat_interface. This prevents nova from breaking container networking when it adds the container eth0 to the nova bridge (br100). Change-Id: I93c696a8476228d6bbca678748170c2a11d5af11 2014-10-21T18:29:32+00:00 Lars Kellogg-Stedman lars@redhat.com 2014-10-21T18:29:32+00:00 urn:sha1:914dcfae88012cd762de1f5cc6183077a9dd359c global script is called "kolla-common.sh" not "config-common.sh". Change-Id: I0303d33c786d575ac4b061b4060f626213bc583b 2014-10-21T16:57:25+00:00 Steven Dake sdake@redhat.com 2014-10-21T16:55:16+00:00 urn:sha1:f34e65ab1fc67210c688e0560bfe8a09b00cbbac Not all nova services need a bridge. Remove bridge creation from nova-base config and place in nova-network specifically. Change-Id: Ia78c65a4661cd95112dca7ffdc1e839d4f648d52 2014-10-21T16:57:24+00:00 Steven Dake sdake@redhat.com 2014-10-21T16:56:01+00:00 urn:sha1:51643d2fea52fc37ae71ebb012b5425278326db3 libvirt-start.sh was missing from nova-compute/nova-compute. Add it so libvirt is started from a fresh checkout of the repository. Change-Id: I8b40819629b16e4a63102eb353b3c8682791cf9d 2014-10-20T21:05:03+00:00 Steven Dake sdake@redhat.com 2014-10-17T20:20:17+00:00 urn:sha1:0c8080296d1d391dcfade14e08e655c094e42745 Neutron is not yet ready, so use flat nova networking instead. Change-Id: I4905f2a54af2c0c06cc8cf95d21f5831b02fbe5e 2014-10-17T19:19:51+00:00 Lars Kellogg-Stedman lars@redhat.com 2014-10-17T18:53:27+00:00 urn:sha1:a5f6222da89b2515f63531597d7143bb54957ee9 This moves nova-ctr-base one level up and renames it nova-base, so that we can share the same basic config between compute and controller pods. Change-Id: I325f70c278744a1e1fe99b891e05c59c4248c55f 2014-10-17T06:02:56+00:00 Steven Dake sdake@redhat.com 2014-10-17T05:59:45+00:00 urn:sha1:a14b8048c273f12aa4b941c0ff923997ad7524d6 The nova-compute POD now starts and produces nearly correct output. It may be that the libvirt container needs additional attention as it is spitting out errors related to the firewall toolchain on the container. Change-Id: I5bcd21c59f341494206a09e882631185ce66f336 2014-10-17T06:02:53+00:00 Steven Dake sdake@redhat.com 2014-10-16T22:58:35+00:00 urn:sha1:518e72484599defe3fa6d0d749558137c47543c1 Libvirt imports from fedora-rdo-base rather then nova-base, so no need in generating an extra image. Change-Id: I3ddd3aca54900686e3351de3dc11896347b14b6e