Public bug reported:
The "enable_isolated_metadata = True" options tells DHCP agents that for each
network under its care, a neutron-ns-metadata-proxy process should be spawned,
regardless if it's isolated or not.
This is fine for isolated networks (networks with no routers and no default
gateways), but for networks which are connected to a router (for which the L3
agent spawns a separate neutron-ns-metadata-proxy which is attached to the
router's namespace), 2 different metadata proxies are spawned. For these
networks, the static routes which are pushed to each instance, letting it know
where to search for the metadata-proxy, is not pushed and the proxy spawned
from the DHCP agent is left unused.
The DHCP agent should know if the network it handles is isolated or not,
and for non-isolated networks, no neutron-ns-metadata-proxy processes
should spawn.
** Affects: neutron
Importance: Undecided
Assignee: John Schwarz (jschwarz)
Status: In Progress
** Changed in: neutron
Assignee: (unassigned) => John Schwarz (jschwarz)
** Changed in: neutron
Status: New => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1361545
Title:
dhcp agent shouldn't spawn metadata-proxy for non-isolated networks
Status in OpenStack Neutron (virtual network service):
In Progress
Bug description:
The "enable_isolated_metadata = True" options tells DHCP agents that for each
network under its care, a neutron-ns-metadata-proxy process should be spawned,
regardless if it's isolated or not.
This is fine for isolated networks (networks with no routers and no default
gateways), but for networks which are connected to a router (for which the L3
agent spawns a separate neutron-ns-metadata-proxy which is attached to the
router's namespace), 2 different metadata proxies are spawned. For these
networks, the static routes which are pushed to each instance, letting it know
where to search for the metadata-proxy, is not pushed and the proxy spawned
from the DHCP agent is left unused.
The DHCP agent should know if the network it handles is isolated or
not, and for non-isolated networks, no neutron-ns-metadata-proxy
processes should spawn.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1361545/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
