Comment 1 for bug 1631371

I either don't understand your proposal or I think you already have all you need in the trunk_details extension. Neutron is not involved in how metadata is exposed to the guest, and it should not be. I suspect there is nothing to do on the Neutron side, but please elaborate in case I am missing something.

When you fetch a parent port [1], what information is missing that you need to get hold of?

[1] https://review.openstack.org/#/c/353131/10/api-ref/source/v2/samples/trunks/trunk-details-show-response.json