Make quantum namespace proxy transparent

[mouadino]

The namespace proxy should be transparent for all request and response that are passing throw, this way we can avoid to change it, (or forgetting doing it :) LP#1092311 ) when the metadata service change.

[Mark McClain (markmcclain)]

I'm wondering if this belongs as a blueprint rather than a bug.

[mouadino (mouadino)]

The way i see it, is that this is a behavior bug, because the intended behavior for which this proxy was created didn't include changing metadata HTTP response which can miss-lead cloud-init clients and lead to wrong behavior, and apparently the current code assumed that the metadata service will never change ( but apparently that was wrong, bug #1092311), that's why the response status that are currently supported by the metadata service are **hardcoded** the way they are now.

And please correct me if i am wrong.

[Nachi Ueno (nati-ueno)]

Hi Mouadino

IMO, this needs bp, because the bug is gap between spec(bp) and implementation.
so if there is no bp says namespace proxy should be transparent proxy, we should add new one.

[mouadino (mouadino)]

Hi Nachi,

Is this the link for the original blueprint (https://blueprints.launchpad.net/neutron/+spec/metadata-overlapping-networks) ?

I just want to have an idea of what was the first bp specs and how can i write the new ones.

Thanks :)

[Launchpad Janitor (janitor)]

[Expired for neutron because there has been no activity for 60 days.]