From c4e56c0c15a2788702c4345b6afd52e3cb77eb93 Mon Sep 17 00:00:00 2001
From: Steven Dake <stdake@cisco.com>
Date: Fri, 20 Feb 2015 15:00:55 -0700
Subject: [PATCH] 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
---
 specs/containerize-openstack.rst | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)

diff --git a/specs/containerize-openstack.rst b/specs/containerize-openstack.rst
index daf2f73b82..ef57f89f15 100644
--- a/specs/containerize-openstack.rst
+++ b/specs/containerize-openstack.rst
@@ -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