add options to configure dnsmasq options in neutron. fixes #709#108
add options to configure dnsmasq options in neutron. fixes #709#108JCallicoat wants to merge 1 commit intorcbops-cookbooks:masterfrom JCallicoat:issue_709
Conversation
|
Running GATE test(s): http://build.monkeypuppetlabs.com:8080/job/GIT-Pull-Request/1151/console |
|
Gate: Submodule Tailor (non-voting): SKIPPED |
|
Gate: Submodule syntax: SUCCESS |
|
Gate: Submodule Foodcritic: SUCCESS |
|
Gate: Nova AIO (jenkins-precise-v2): SUCCESS |
|
Gate: Nova AIO (jenkins-centos-v3): SUCCESS |
|
Not automatically merged : JCallicoat is not an approved committer. Please leave pull request open for review and manual merge by a core team member. |
|
@JCallicoat it appears that this will set the MTU for instances via DHCP for all network types and not just the ones that are using GRE? I spoke to @Apsu and we were wondering if you tried allowing ingress ICMP to the instance and allowing pMTUD to set the MTU correctly for the tunneled interface? |
|
@rackerjoe Yeah, setting a dnsmasq config file is at the agent level, so all networks would be effected. I didn't see a way to apply the config per network. I'm not sure if MTU discovery is an option as I don't know the requirements around allowing ICMP. I would think that in at least some cases ICMP would be disallowed by policy. @odyssey4me what do you think? We could make the dhcp-option value a default-nil attribute instead of hard coding it. |
|
@rackerjoe @JCallicoat @Apsu Ingress ICMP should already be allowed by default I think as the DHCP service will sit on the same subnet as the instance and the default policies have a blanket allowance for same subnet traffic. |
This adds attributes for neutron dnsmasq options, adds a dnsmasq-nova.conf template with
dhcp-option=26,1454, and also allowsdhcp-scriptto be set via attribute.