Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I finally found the solution in this forum: http://lists.openstack.org/pipermail/openstack/2013-October/001831.html

When you use flat networking you have two options:

  1. You need to use metadata via dhcp namespace (Source: http://techbackground.blogspot.ie/2013/06/metadata-via-dhcp-namespace.html) I did not test this setup because I cannot change my subnet right now. The logic is not to use default gateway option in subnet, and enter 0.0.0.0/0 route to subnet manually. (Check discussion part of the link)

  2. You need to create a router in network node in Openstack, create port on your instance network for this router and choose an IP different than your real router. This router will be used just for metadata. Install neutron-metadata-agent to network node where you install l3 agent. Configure your nova.conf in compute and controller nodes:

metadata_host=192.168.0.1 service_neutron_metadata_proxy = True neutron_metadata_proxy_shared_secret = x1x1x1x1x

Configure your metadata_agent.ini in network node:

auth_url = http://192.168.0.1:5000/v2.0 auth_region = RegionOne admin_tenant_name = service admin_user = neutron admin_password = xxxxxxx nova_metadata_ip = 192.168.0.1 nova_metadata_port = 8775 metadata_proxy_shared_secret = x1x1x1x1x

I finally found the solution in this forum: http://lists.openstack.org/pipermail/openstack/2013-October/001831.html

When you use flat networking you have two options:

  1. You need to use metadata via dhcp namespace (Source: http://techbackground.blogspot.ie/2013/06/metadata-via-dhcp-namespace.html) I did not test this setup because I cannot change my subnet right now. The logic is not to use default gateway option in subnet, and enter 0.0.0.0/0 route to subnet manually. (Check discussion part of the link)

  2. You need to create a router in network node in Openstack, create port on your instance network for this router and choose an IP different than your real router. This router will be used just for metadata. Install neutron-metadata-agent to network node where you install l3 agent. Configure your nova.conf in compute and controller nodes:

metadata_host=192.168.0.1 service_neutron_metadata_proxy = True neutron_metadata_proxy_shared_secret = x1x1x1x1x

Configure your metadata_agent.ini in network node:

auth_url = http://192.168.0.1:5000/v2.0
auth_region = RegionOne
admin_tenant_name = service
admin_user = neutron
admin_password = xxxxxxx
nova_metadata_ip = 192.168.0.1
nova_metadata_port = 8775
metadata_proxy_shared_secret = x1x1x1x1x

x1x1x1x1x

I finally found the solution in this forum: http://lists.openstack.org/pipermail/openstack/2013-October/001831.html

When you use flat networking you have two options:

  1. You need to use metadata via dhcp namespace (Source: http://techbackground.blogspot.ie/2013/06/metadata-via-dhcp-namespace.html) I did not test this setup because I cannot change my subnet right now. The logic is not to use default gateway option in subnet, and enter 0.0.0.0/0 route to subnet manually. (Check discussion part of the link)

  2. You need to create a router in network node in Openstack, create port on your instance network for this router and choose an IP different than your real router. This router will be used just for metadata. Install neutron-metadata-agent to network node where you install l3 agent. Configure your nova.conf in compute and controller nodes:

    metadata_host=192.168.0.1 metadata_host=192.168.0.1

    service_neutron_metadata_proxy = True True

    neutron_metadata_proxy_shared_secret = x1x1x1x1x

Configure your metadata_agent.ini in network node:

auth_url = http://192.168.0.1:5000/v2.0
auth_region = RegionOne
admin_tenant_name = service
admin_user = neutron
admin_password = xxxxxxx
nova_metadata_ip = 192.168.0.1
nova_metadata_port = 8775
metadata_proxy_shared_secret = x1x1x1x1x