Ask Your Question
1

working with external dhcp and enable metadata server

asked 2016-06-30 14:37:39 -0600

Uzi gravatar image

updated 2016-06-30 14:38:15 -0600

Hi All

i am working in a network that requires not openstack related network DHCP because the Organization DHCP add additional information to the Instance .

however i also need the cloud-init when instantiating the instance ,so i need its routing rule that enable access to metadata server at the controller in the first place

what can i do in-order to have both "worlds" ?, is there a way for open stack to intercept incoming DHCP packets and add the meta data routing rule to them ?

thanks for your help

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-07-03 15:00:23 -0600

james-denton gravatar image

An instance can reach metadata via:

An instance will reach 169.254.169.254 via:

  • default route (pointing to Neutron router)
  • static route (pointing to Neutron DHCP namespace)

As long as your org's DHCP server is sending a default route pointing to the Neutron router, I would think you'd be good. Otherwise, you may be limited to using config-drive instead, since it doesn't rely on DHCP.

You can also add DHCP options to Neutron ports that you attach to instances if you'd rather Neutron handled the entire stack rather than using org's DHCP server.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-06-30 14:37:39 -0600

Seen: 517 times

Last updated: Jul 03 '16