[Openstack-operators] [Metadata in Neutron]

Nam Nguyễn Hoài namptit307 at gmail.com
Wed May 13 04:28:52 UTC 2015

Thanks for your answer.
I want to combine two usecases that are "Per-tenant router with private
networks architecture" and  "Single flat network". Metadata is supplied via
DHCP_agent (I solved metadata with your guide) and "Single flat network"
supply IP external network for instance but instance can not connect
external network. Can you guide me config this case.


2015-05-12 15:48 GMT+07:00 Miguel Ángel Ajo <majopela at redhat.com>:

> The metadata on DHCP agent is only provided when you have isolated
> networks, that means
> “networks with no router attached”.
> And it’s only enabled if you set True enable_isolated_metadata in
> /etc/neutron/dhcp_agent.ini
> Let me know if that works for you.
> Best regards,
> Miguel Ángel.
> Miguel Ángel Ajo
> On Tuesday, 12 de May de 2015 at 10:16, Nam Nguyễn Hoài wrote:
> Hi everyone. Neutron uses two ways to supply metadata via DHCP_agent or
> L3_agent. So what situation do we use metadata via dhcp_agent or L3_agent?
> Can you guide me how config to supply metadata via DHCP_agent?
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150513/72aa907f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot_6.png
Type: image/png
Size: 11656 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150513/72aa907f/attachment.png>

More information about the OpenStack-operators mailing list