Metadata service on provider's network

asked 2017-09-06 10:04:53 -0600

nuriel77 gravatar image

Hi, I am using Ocata (via TripleO), and was following this tutorial on how to allow metadata accessibility from provider network: how-to-use-meta-data-service-for-vm-with-provider-network

Two different things between my setup and the one from the link above is that my provider's network is 10.10.0.0/24 and the physical router is at 10.10.0.1 (in the link above it is at 10.0.0.254...)

The problem I am having is with the host routes when creating the subnet:

neutron subnet-create ext_net \
  --name infra-access \
  --gateway=10.10.0.254 
  --allocation-pool start=10.10.0.51,end=10.10.0.199 \
  --host-route destination=0.0.0.0/0,nexthop=10.10.0.1 \
  --host-route destination=169.254.169.254/32,nexthop=10.10.0.254 \
  --dns-nameserver 10.10.0.223 \
  --dns-nameserver 10.10.0.225 \
  10.10.0.0/24

Subnet creates fine, I can see the two host-route definitions when I run neutron subnet-show infra-access:

| host_routes       | {"destination": "0.0.0.0/0", "nexthop": "10.10.0.1"}            |
|                   | {"destination": "169.254.169.254/32", "nexthop": "10.10.0.254"} |

However, when I check the file created for dhcp I see this:

# cat /var/lib/neutron/dhcp/b92236fd-3c8d-4566-b833-fe5d4e6a6631/opts
tag:tag0,option:dns-server,10.10.0.223,10.10.0.225
tag:tag0,option:classless-static-route,169.254.169.254/32,10.10.0.254,0.0.0.0/0,10.10.0.254
tag:tag0,249,169.254.169.254/32,10.10.0.254,0.0.0.0/0,10.10.0.254
tag:tag0,option:router,10.10.0.254

As you can see the route for 0.0.0.0/0 is 10.10.0.254 and not 10.10.0.1 as I'd expect and as I've defined when creating the subnet.

Any ideas? Thanks

edit retag flag offensive close merge delete

Comments

By the way, it just looks like it defaults to the gw address for any static routes specified for 0.0.0.0/0. I am going to try my luck with config_drive=true to supply vm's with metadata.

nuriel77 gravatar imagenuriel77 ( 2017-09-06 12:36:31 -0600 )edit