Thanks for reporting this bugs, and for proposing a strategy for fixing it.
I'm not really up-to-date on the Quantum-nova integration, but I was wondering why we would need to stop dnsmasq. This might make sense with the VLAN manager, altough I think there is already code in place for destroying resources on the network node, including the dnsmasq instance, when a network is delete.
However, in FlatDHCP mode, if I'm not wrong the same dnsmasq instance is used for all networks (several IP addresses are configured on the bridge).
Hi Isaku!
Thanks for reporting this bugs, and for proposing a strategy for fixing it.
I'm not really up-to-date on the Quantum-nova integration, but I was wondering why we would need to stop dnsmasq. This might make sense with the VLAN manager, altough I think there is already code in place for destroying resources on the network node, including the dnsmasq instance, when a network is delete.
However, in FlatDHCP mode, if I'm not wrong the same dnsmasq instance is used for all networks (several IP addresses are configured on the bridge).