6184dea966
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 |
||
|---|---|---|
| .. | ||
| devstack-with-lbaas-v2.rst | ||
| devstack-with-ldap.rst | ||
| devstack-with-nested-kvm.rst | ||
| lxc.rst | ||
| multinode-lab.rst | ||
| neutron.rst | ||
| nova.rst | ||
| single-machine.rst | ||
| single-vm.rst | ||