diff options
| author | Steven Dake <sdake@redhat.com> | 2014-10-19 13:26:27 -0700 |
|---|---|---|
| committer | Steven Dake <sdake@redhat.com> | 2014-10-20 10:18:47 -0700 |
| commit | f2c3719506e6ec0174fe7671ae5610faccedbcb9 (patch) | |
| tree | 74a2254e110c2d150b4d13c187fc15dba8957173 /k8s | |
| parent | 3ae22f65ea0f04b0a49a81f81af96e5a9646d46f (diff) | |
| download | kolla-f2c3719506e6ec0174fe7671ae5610faccedbcb9.tar.gz kolla-f2c3719506e6ec0174fe7671ae5610faccedbcb9.zip | |
Use hostPort to lock 1 nova-compute/nova-network per node
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
Diffstat (limited to 'k8s')
| -rw-r--r-- | k8s/replication/nova-compute-replication.yaml | 10 |
1 files changed, 7 insertions, 3 deletions
diff --git a/k8s/replication/nova-compute-replication.yaml b/k8s/replication/nova-compute-replication.yaml index 4c3060c63..a690fca49 100644 --- a/k8s/replication/nova-compute-replication.yaml +++ b/k8s/replication/nova-compute-replication.yaml @@ -6,6 +6,9 @@ desiredState: containers: - name: nova-compute image: kollaglue/fedora-rdo-nova-compute + ports: + - containerPort: 12000 + hostPort: 12000 env: - name: DB_ROOT_PASSWORD value: password @@ -14,9 +17,10 @@ desiredState: - name: KEYSTONE_ADMIN_TOKEN value: ADMINTOKEN - name: nova-libvirt - image: kollaglue/fedora-rdo-nova-libvirt + image: kollaglue/fedora-rdo-nova-network ports: - - containerPort: 16509 + - containerPort: 12001 + hostPort: 12001 env: - name: DB_ROOT_PASSWORD value: password @@ -30,7 +34,7 @@ desiredState: name: nova-compute replicaSelector: name: nova-compute - replicas: 1 + replicas: 6 id: nova-compute-controller kind: ReplicationController labels: |