openstack/kolla-ansible
Code Issues Proposed changes

Use hostPort to lock 1 nova-compute/nova-network per node

Browse Source 
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
This commit is contained in:
Steven Dake 2014-10-19 13:26:27 -07:00
parent 3ae22f65ea
commit f2c3719506
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
k8s/replication/nova-compute-replication.yaml
View File

@ -6,6 +6,9 @@ desiredState:
containers: containers:
- name: nova-compute - name: nova-compute
image: kollaglue/fedora-rdo-nova-compute image: kollaglue/fedora-rdo-nova-compute
ports:
- containerPort: 12000
hostPort: 12000
env: env:
- name: DB_ROOT_PASSWORD - name: DB_ROOT_PASSWORD
value: password value: password
@ -14,9 +17,10 @@ desiredState:
- name: KEYSTONE_ADMIN_TOKEN - name: KEYSTONE_ADMIN_TOKEN
value: ADMINTOKEN value: ADMINTOKEN
- name: nova-libvirt - name: nova-libvirt
image: kollaglue/fedora-rdo-nova-libvirt image: kollaglue/fedora-rdo-nova-network
ports: ports:
- containerPort: 16509 - containerPort: 12001
hostPort: 12001
env: env:
- name: DB_ROOT_PASSWORD - name: DB_ROOT_PASSWORD
value: password value: password
@ -30,7 +34,7 @@ desiredState:
name: nova-compute name: nova-compute
replicaSelector: replicaSelector:
name: nova-compute name: nova-compute
replicas: 1 replicas: 6
id: nova-compute-controller id: nova-compute-controller
kind: ReplicationController kind: ReplicationController
labels: labels: