Comment 12 for bug 1905115

Hi
Recently, I thought of this RFE when my colleague consult me that the network issue about ironic deploy. The ironic's workflows have a inspection step, this step is mainly completed by two services: ironic-inspector and ironic-python-agent(IPA), the IPA need to post data to ironic-inspector. But, the ironic-inspector listen on the controller node's management network, the IPA work on ironic's inspection network (a neutron provider network, it's type is vlan). So, in short, my colleague require that a openstack tenant network can access openstack management network, so I immediately thought of the neutron-metadata-agent, then thought of this RFE. I mean that we can simplify the network topology when deploy openstack ironic by this RFE.
By the way, the trove and octavia's deployment also have similar network issue. For trove, the trove database instance need to post log information to swift.

[1] https://docs.openstack.org/ironic-python-agent/latest/admin/how_it_works.html
[2] https://docs.openstack.org/ironic-inspector/latest/user/workflow.html