Split OpenStack controller and OpenStack API

Permit different levels of horizontal scalability for API vs engine or
conductor processes.  Typically API may need different levels of scale
compared to the engine processes.
.

Change-Id: I2916fed7745bd9b0f67fda0abbb6d148315e5e00
This commit is contained in:
Steven Dake 2015-02-20 15:00:55 -07:00
parent 91bea4c72b
commit c4e56c0c15
1 changed files with 9 additions and 5 deletions

View File

@ -93,6 +93,7 @@ The top level container sets are composed of:
* database control
* messaging control
* high availability control
* OpenStack interface
* OpenStack control
* Openstack compute operation
* OpenStack storage operation
@ -113,17 +114,22 @@ The various container sets are composed in more detail as follows:
* HAProxy
* OpenStack control
* OpenStack interface
* keystone
* glance-api
* nova-api
* ceilometer-api
* heat-api
* OpenStack control
* glance-controller
* glance-api
* glance-registry
* nova-controller
* nova-api
* nova-conductor
* nova-scheduler
@ -138,7 +144,6 @@ The various container sets are composed in more detail as follows:
* ceiloemter-controller
* ceilometer-alarm
* ceilometer-api
* ceilometer-base
* ceilometer-central
* ceilometer-collector
@ -146,7 +151,6 @@ The various container sets are composed in more detail as follows:
* heat-controller
* heat-api
* heat-engine
* Openstack compute operation