Host route to metadata server is not propagated to VM with Big Switch/Floodlight plugin

[Sumit Naiksatam]

The reason seems to be that the update to the subnet (with the host route information) is not being picked up by the dhcp agent.

[Salvatore Orlando (salvatore-orlando)]

Sumit, are you trying to inject a metadata host route via the Quantum API?

Something like:
dest 169.254.169.254/32
nexthop <ip of dhcp agent>

In that case the dhcp agent now has 'native' support for this via the 'enable_isolated_metadata' option.
Also the dhcp agent also allows for routed access to the metadata server even without the l3 agent.

Would that solve your problem?

[Sumit Naiksatam (snaiksat)]

Thanks Salvatore, yes I wanted to inject that route. I did try setting 'enable_isolated_metadata' to True, however the opts file does not get this route. Let me know if you have any other suggestions on the configuration.

[Sumit Naiksatam (snaiksat)]

It seems that the 'enable_isolated_metadata' is effective only when the gateway IP for the subnet is not set. In this case I want the host route to point to <ip of dhcp agent> regardless. I am pushing a patch to do this.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/23248

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/23248
Committed: http://github.com/openstack/quantum/commit/f1efd89131f4773514089ab48424c91b795eac83
Submitter: Jenkins
Branch: master

commit f1efd89131f4773514089ab48424c91b795eac83
Author: Sumit Naiksatam <email address hidden>
Date: Thu Feb 28 22:00:32 2013 -0800

    Host route to metadata server with Bigswitch/Floodlight Plugin

    Host route to metadata server was not getting propagated
    to VM when using the Big Switch/Floodlight plugin. The
    reason being the update to the subnet (with the host
    route information) was not being picked up by the dhcp
    agent. This is being fixed here by sending a notification
    to the dhcp agent when the host route is added to the subnet.

    Fixes: Bug #1134043

    Change-Id: If040f51946bcb734da319249df17d03e68aa5588