Browse code
Remove n-api-metadata service from compute nodes
Starting up n-api-metadata service on every compute nodes does
not solve the problem of isolated networks (no route to metadata
service). It all depends on how 'enable_isolated_metadata' and
related options (e.g. force_metadata) are set in dhcp agent and
what is configured for the 'nova_metadata_host' option of q-meta
service. Having a global n-api-metadata service in the control
node is sufficient for a mult-node lab setup.
Besides, the n-api-metadata services on compute nodes are not
really working due to https://bugs.launchpad.net/nova/+bug/1815082
Change-Id: Ib8691c3eeee59758fbd98989d9460f1458ea422f
Related-Bug: 1815082
Rui Zang authored on 2020/07/07 15:47:56Showing 1 changed files
| ... | ... |
@@ -169,17 +169,12 @@ machines, create a ``local.conf`` with: |
| 169 | 169 |
MYSQL_HOST=$SERVICE_HOST |
| 170 | 170 |
RABBIT_HOST=$SERVICE_HOST |
| 171 | 171 |
GLANCE_HOSTPORT=$SERVICE_HOST:9292 |
| 172 |
- ENABLED_SERVICES=n-cpu,q-agt,n-api-meta,c-vol,placement-client |
|
| 172 |
+ ENABLED_SERVICES=n-cpu,q-agt,c-vol,placement-client |
|
| 173 | 173 |
NOVA_VNC_ENABLED=True |
| 174 | 174 |
NOVNCPROXY_URL="http://$SERVICE_HOST:6080/vnc_lite.html" |
| 175 | 175 |
VNCSERVER_LISTEN=$HOST_IP |
| 176 | 176 |
VNCSERVER_PROXYCLIENT_ADDRESS=$VNCSERVER_LISTEN |
| 177 | 177 |
|
| 178 |
-**Note:** the ``n-api-meta`` service is a version of the api server |
|
| 179 |
-that only serves the metadata service. It's needed because the |
|
| 180 |
-computes created won't have a routing path to the metadata service on |
|
| 181 |
-the controller. |
|
| 182 |
- |
|
| 183 | 178 |
Fire up OpenStack: |
| 184 | 179 |
|
| 185 | 180 |
:: |