summaryrefslogtreecommitdiff
path: root/k8s/replication
AgeCommit message (Collapse)AuthorFilesLines
2014-10-20Change to using flat nova networking from neutronSteven Dake1-1/+3
Neutron is not yet ready, so use flat nova networking instead. Change-Id: I4905f2a54af2c0c06cc8cf95d21f5831b02fbe5e
2014-10-20Use hostPort to lock 1 nova-compute/nova-network per nodeSteven Dake1-3/+7
Kubernetes does not have a horizontal scaling feature that works per node. A workaround is to use hostPort to cause the scheduler not to schedule several replicationController replicas to each node. By doing so, only one nova-compute is launched per node up to a total of 6 nodes which is the most we can generate in testing. Change-Id: I1621f15cf1ec502418b454300645b46bc796dc8b
2014-10-16Make nova-compute work properly with libvirtSteven Dake1-1/+1
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-14Convert nova-compute-replication to yamlSteven Dake2-66/+37
Yaml is the future - json is the past \o/ Change-Id: I36a9cbf8db034d1e8deba040a22e556d791c65ed
2014-10-08Add a replicationController for nova-compute so it runs on each minionSteven Dake1-0/+66
We want the nova-compute controller to run on each minion Change-Id: If0355034927e195d1dd5482dab1026418185e9c6