openstack/devstack
Code Issues Proposed changes

fix multinode guide

Browse Source 
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
This commit is contained in:
Sean Dague 2015-08-04 06:23:28 -04:00
parent af68087be3
commit a6db5e30cc
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/source/guides/multinode-lab.rst
View File

@ -178,12 +178,17 @@ machines, create a ``local.conf`` with:
MYSQL_HOST=192.168.42.11 MYSQL_HOST=192.168.42.11
RABBIT_HOST=192.168.42.11 RABBIT_HOST=192.168.42.11
GLANCE_HOSTPORT=192.168.42.11:9292 GLANCE_HOSTPORT=192.168.42.11:9292
ENABLED_SERVICES=n-cpu,n-net,n-api,c-vol ENABLED_SERVICES=n-cpu,n-net,n-api-meta,c-vol
NOVA_VNC_ENABLED=True NOVA_VNC_ENABLED=True
NOVNCPROXY_URL="http://192.168.42.11:6080/vnc_auto.html" NOVNCPROXY_URL="http://192.168.42.11:6080/vnc_auto.html"
VNCSERVER_LISTEN=$HOST_IP VNCSERVER_LISTEN=$HOST_IP
VNCSERVER_PROXYCLIENT_ADDRESS=$VNCSERVER_LISTEN VNCSERVER_PROXYCLIENT_ADDRESS=$VNCSERVER_LISTEN
**Note:** the ``n-api-meta`` service is a version of the api server
that only serves the metadata service. It's needed because the
computes created won't have a routing path to the metadata service on
the controller.
Fire up OpenStack: Fire up OpenStack:
:: ::
@ -263,7 +268,7 @@ Swift
----- -----
Swift, OpenStack Object Storage, requires a significant amount of resources Swift, OpenStack Object Storage, requires a significant amount of resources
and is disabled by default in DevStack. The support in DevStack is geared and is disabled by default in DevStack. The support in DevStack is geared
toward a minimal installation but can be used for testing. To implement a toward a minimal installation but can be used for testing. To implement a
true multi-node test of swift, additional steps will be required. Enabling it is as true multi-node test of swift, additional steps will be required. Enabling it is as
simple as enabling the ``swift`` service in ``local.conf``: simple as enabling the ``swift`` service in ``local.conf``: