openstack/kolla.git/docker/nova-compute, branch version-m1Unnamed repository; edit this file 'description' to name the repository.
https://git.platform-os.org/openstack/kolla.git/atom?h=version-m12014-10-21T20:05:36+00:00workarounds for nova networking2014-10-21T20:05:36+00:00Lars Kellogg-Stedmanlars@redhat.com2014-10-21T19:56:42+00:00urn: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
fix typo in nova-network/start.sh2014-10-21T18:29:32+00:00Lars Kellogg-Stedmanlars@redhat.com2014-10-21T18:29:32+00:00urn:sha1:914dcfae88012cd762de1f5cc6183077a9dd359c
global script is called "kolla-common.sh" not "config-common.sh".
Change-Id: I0303d33c786d575ac4b061b4060f626213bc583b
Only create bridge in nova-network2014-10-21T16:57:25+00:00Steven Dakesdake@redhat.com2014-10-21T16:55:16+00:00urn: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
Add missing libvirt-start.sh2014-10-21T16:57:24+00:00Steven Dakesdake@redhat.com2014-10-21T16:56:01+00:00urn: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
Change to using flat nova networking from neutron2014-10-20T21:05:03+00:00Steven Dakesdake@redhat.com2014-10-17T20:20:17+00:00urn:sha1:0c8080296d1d391dcfade14e08e655c094e42745
Neutron is not yet ready, so use flat nova networking instead.
Change-Id: I4905f2a54af2c0c06cc8cf95d21f5831b02fbe5e
introduce a common base for compute and controller2014-10-17T19:19:51+00:00Lars Kellogg-Stedmanlars@redhat.com2014-10-17T18:53:27+00:00urn: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
Make nova-compute work properly with libvirt2014-10-17T06:02:56+00:00Steven Dakesdake@redhat.com2014-10-17T05:59:45+00:00urn: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
Remove nova-base since there is only 1 image for nova-compute2014-10-17T06:02:53+00:00Steven Dakesdake@redhat.com2014-10-16T22:58:35+00:00urn:sha1:518e72484599defe3fa6d0d749558137c47543c1
Libvirt imports from fedora-rdo-base rather then nova-base, so no need
in generating an extra image.
Change-Id: I3ddd3aca54900686e3351de3dc11896347b14b6e
Have qemu uri point to correct place2014-10-14T15:36:41+00:00Steven Dakesdake@redhat.com2014-10-14T15:35:54+00:00urn:sha1:394725f1b1e660c272161e913461c632d6e7c183
Prevoiusly the connection uri was using an undefined variable. Now
it will use NOVA_LIBVIRT_SERVICE.
Change-Id: Ia5ceb3428fa7aeb8dd1dd7b500c63119856977f2
do not perform database or keystone setup in nova-compute2014-10-14T15:13:46+00:00Lars Kellogg-Stedmanlars@redhat.com2014-10-14T15:13:46+00:00urn:sha1:20e88776bc9b85b2a3a0f7a86004f6b04520e9a8
- do not perform database or keystone initialization in nova-compute
image (these should happen in the controller images).
- fix incorrect nova.conf path
- configure keystone_authtoken correct
NB: This still won't result in a working image, because it does not
configure the RPC settings yet. That will be for a subsequent patch.
Change-Id: Icbd66104ef817d360c46003b29fff63f66ace8d2