Atom feed of this document
 

 Nova Metadata Server Support

To use Nova metadata service, metadata_ip and metadata_port in the L3 agent configuration file need to be configured. Accessing from VMs to Nova metadata service is forwarded to an external network through Quantum L3 router. Nova metadata service must be reachable from the external network. As the Limitations section says, note that Quantum overlapping IPs support and Nova metadata service cannot be used together.

Allowing VMs to reach the metadata service is a big point of confusion with Quantum. We need to make sure instructions for how to set this up are displayed more prominently than they already are, and that there are instructions for how to validate and troubleshoot in this scenario.

Example validation includes:

VALIDATION STEP #1

- on network node(l3_agent running) ping to metadata_ip that specified by l3_agent.py

if you are not using namespace, just run:

  ping <metadata_ip>

for example, if the metadata server IP is 172.16.10.5, run:

$ping 172.16.10.5 

if you using namespaces, identify the UUID of the router and run:

ip netns exec qrouter-<router uuid> ping <metadata_ip>

for example, if the router uuid is d7e9ec57-77c2-4046-aebf-d978ed4a4f83 and the metadata server IP is 172.16.10.5, run:

$ ip netns exec qrouter-d7e9ec57-77c2-4046-aebf-d978ed4a4f83 ping 172.16.10.5

VALIDATION STEP #2

- on metadata server(nova_api server) check connection to vm's subnets using an un-NATed IP address of the VM, such as 10.0.0.2:

$ping 10.0.0.2

NOTE

OpenStack does not manage this routing for you, so you need to make sure that your host running the metadata service always has a route to reach each private network's subnet via the external network IP of that subnet's quantum router. To do this, you can either run quantum without namespaces, and run the quantum-l3-agent on the same host as nova-api. Otherwise, you can identify an IP prefix that includes all private network subnet's (e.g., 10.0.0.0/8) and then make sure that your metadata server has a route for that prefix with the quantum router's external IP address as the next hop.



loading table of contents...