From 6184dea966d56f13f15d926dbb09e527ae3ba39e Mon Sep 17 00:00:00 2001 From: Rui Zang Date: Mon, 6 Jul 2020 23:47:56 -0700 Subject: [PATCH] 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 --- doc/source/guides/multinode-lab.rst | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/doc/source/guides/multinode-lab.rst b/doc/source/guides/multinode-lab.rst index 15f02a0e5e..c0b3f58157 100644 --- a/doc/source/guides/multinode-lab.rst +++ b/doc/source/guides/multinode-lab.rst @@ -169,17 +169,12 @@ machines, create a ``local.conf`` with: MYSQL_HOST=$SERVICE_HOST RABBIT_HOST=$SERVICE_HOST GLANCE_HOSTPORT=$SERVICE_HOST:9292 - ENABLED_SERVICES=n-cpu,q-agt,n-api-meta,c-vol,placement-client + ENABLED_SERVICES=n-cpu,q-agt,c-vol,placement-client NOVA_VNC_ENABLED=True NOVNCPROXY_URL="http://$SERVICE_HOST:6080/vnc_lite.html" VNCSERVER_LISTEN=$HOST_IP 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: ::