> The instance firewall should be configured to only allow DHCP > responses from the IP it believes to be the correct DHCP server. > Perhaps it has the wrong idea?
Ah yes - it probably does because of my unusual network "subrange" config. It seems I'm not "missing something", so I've proposed a init script for contrib that can apply the configuration from a config_drive. It solved my problem, and it avoids all of the DHCP/cloud-init complexity without needing direct injection. Still very much a version 1 though: https://review.openstack.org/#change,4498 _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp