Open Stack

Should VMs always have a static route to the 169.254 subnet so they
can access the metadata service?

In my VMs attempting the following request works with a route but just
times out without it,

$ curl http://169.254.169.254/latest/meta-data/instance-id

Works with these routes,

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.52.10.0      0.0.0.0         255.255.255.0   U     0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
0.0.0.0         10.52.10.1      0.0.0.0         UG    0      0        0 eth0

But doesn't work these,

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.52.10.0      0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         10.52.10.1      0.0.0.0         UG    0      0        0 eth0

If we need the route then dhclient should request 121, "Classless
Static Route" right? My VM isn't including this in it's DHCP request
but I guess that's just something I need to configure in dhclient.
However I don't want to do this if the route is unnecessary to start
with (and just points to something else is wrong in my setup).

Adrian