| Age | Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
Remove individual MAINTAINER information from Dockerfiles.
Change-Id: I777df5cde049599dc786176e1d5b4b9597f0b334
|
|
Not all nova services need a bridge. Remove bridge creation from
nova-base config and place in nova-network specifically.
Change-Id: Ia78c65a4661cd95112dca7ffdc1e839d4f648d52
|
|
Neutron is not yet ready, so use flat nova networking instead.
Change-Id: I4905f2a54af2c0c06cc8cf95d21f5831b02fbe5e
|