The multinode guide erroneously said to enable n-api on the worker
nodes, which is a typo. n-api-meta is the thing that's needed.
Change-Id: I733896681f7f6fe3bea0fdeeb8ffc9033d7fc761
| ... | ... |
@@ -178,12 +178,17 @@ machines, create a ``local.conf`` with: |
| 178 | 178 |
MYSQL_HOST=192.168.42.11 |
| 179 | 179 |
RABBIT_HOST=192.168.42.11 |
| 180 | 180 |
GLANCE_HOSTPORT=192.168.42.11:9292 |
| 181 |
- ENABLED_SERVICES=n-cpu,n-net,n-api,c-vol |
|
| 181 |
+ ENABLED_SERVICES=n-cpu,n-net,n-api-meta,c-vol |
|
| 182 | 182 |
NOVA_VNC_ENABLED=True |
| 183 | 183 |
NOVNCPROXY_URL="http://192.168.42.11:6080/vnc_auto.html" |
| 184 | 184 |
VNCSERVER_LISTEN=$HOST_IP |
| 185 | 185 |
VNCSERVER_PROXYCLIENT_ADDRESS=$VNCSERVER_LISTEN |
| 186 | 186 |
|
| 187 |
+**Note:** the ``n-api-meta`` service is a version of the api server |
|
| 188 |
+that only serves the metadata service. It's needed because the |
|
| 189 |
+computes created won't have a routing path to the metadata service on |
|
| 190 |
+the controller. |
|
| 191 |
+ |
|
| 187 | 192 |
Fire up OpenStack: |
| 188 | 193 |
|
| 189 | 194 |
:: |
| ... | ... |
@@ -263,7 +268,7 @@ Swift |
| 263 | 263 |
----- |
| 264 | 264 |
|
| 265 | 265 |
Swift, OpenStack Object Storage, requires a significant amount of resources |
| 266 |
-and is disabled by default in DevStack. The support in DevStack is geared |
|
| 266 |
+and is disabled by default in DevStack. The support in DevStack is geared |
|
| 267 | 267 |
toward a minimal installation but can be used for testing. To implement a |
| 268 | 268 |
true multi-node test of swift, additional steps will be required. Enabling it is as |
| 269 | 269 |
simple as enabling the ``swift`` service in ``local.conf``: |