Metadata via the DHCP namespace

This is a follow-on from the previous post that described how metadata requests go from instances to the Nova metadata service via a namespace proxy in a Quantum router namespace. This post shows how requests can go via a namespace proxy in a DHCP namespace instead.

Metadata via the Quantum router

Grizzy adds support for the Nova metadata service to work with overlapping IP address spaces from Quantum. Now Quantum proxies metadata requests to Nova adding HTTP headers which Nova uses to identify the source instance. Quantum actually uses two proxies to do this: a namespace proxy and a metadata agent. This post shows how a metadata request gets from an instance to the Nova metadata service via a namespace proxy running in a Quantum router. It is also possible to run the namespace proxy in a DHCP namespace, but that is not covered here.