summaryrefslogtreecommitdiff
path: root/docker/nova-base
AgeCommit message (Collapse)AuthorFilesLines
2014-12-03Prefer the use PUBLIC_IP over MY_IPMartin André1-2/+2
PUBLIC_IP is more descriptive that MY_IP, it should be used consistently across Kolla. Change-Id: Iff6ae903e794ec84a40a300b36512422b7a81f71
2014-11-25Adds Neutron Networking SupportDaneyon Hansen1-0/+25
Implements: blueprint kube-neutron-container Previously, only the neutron-server service was functional. This patch adds support the the rest of the neutron services need by Nova instances to function. The linux-bridge agent is used instead of the OVS agent to realize network abstractions. This is because the ovs-agent package will install the kernel module version of OVS instead of the userspace version. Additionally, the OVS userspace code is still very experimental and reduces performance. Requires: https://github.com/larsks/heat-kubernetes/pull/8 Change-Id: I5ef34ddeb48d4954934571a928cc82ae7f3a0f20
2014-11-17Adds support for Functional Nova-NetworkDaneyon Hansen1-18/+0
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-22Update MAINTAINER in Dockerfiles to Kolla ProjectLars Kellogg-Stedman1-1/+1
Remove individual MAINTAINER information from Dockerfiles. Change-Id: I777df5cde049599dc786176e1d5b4b9597f0b334
2014-10-21workarounds for nova networkingversion-m1Lars Kellogg-Stedman1-1/+1
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-21Only create bridge in nova-networkSteven Dake1-3/+1
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-20Change to using flat nova networking from neutronSteven Dake2-7/+22
Neutron is not yet ready, so use flat nova networking instead. Change-Id: I4905f2a54af2c0c06cc8cf95d21f5831b02fbe5e
2014-10-17introduce a common base for compute and controllerLars Kellogg-Stedman3-0/+108
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
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-05 19:01:16 +0000