yahoo-eng-team team mailing list archive

[Shih-Hao Li <shihli@xxxxxxxxxx>]

Public bug reported:

Vendors may need additional processing when handling metadata requests.

For example, a metadata request going through a router may not carry
the router_id in the header. If the network_id in the request header is
the routed-to network instead of the original network, metadata agent
can not find the corresponding port via the _get_port function.

This problem can be solved by providing vendor's own _get_port function
that does additional lookups. To achieve this goal, MetadataProxyHandler
class needs to be configurable.

** Affects: neutron
     Importance: Undecided
     Assignee: Shih-Hao Li (shihli)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Shih-Hao Li (shihli)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1518402

Title:
  Make MetadataProxyHandler configurable

Status in neutron:
  New

Bug description:
  Vendors may need additional processing when handling metadata
  requests.

  For example, a metadata request going through a router may not carry
  the router_id in the header. If the network_id in the request header is
  the routed-to network instead of the original network, metadata agent
  can not find the corresponding port via the _get_port function.

  This problem can be solved by providing vendor's own _get_port function
  that does additional lookups. To achieve this goal, MetadataProxyHandler
  class needs to be configurable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1518402/+subscriptions