Thiago,
My current ml2_conf.ini looks like your example. My environment also
continues to work if I omit the entire [security_group] section. However,
it stops working if I omit the [securitygroup] section.
Matt
On Mon, Apr 7, 2014 at 5:36 PM, Martinx - ジェームズ
wrote:
> Hi!
>
> I faced this prob
Hi!
I faced this problem this weekend, look:
https://bugs.launchpad.net/bugs/1303517
Currently, my ml2_conf.ini contains:
---
[security_group]
enable_security_group = True
[securitygroup]
firewall_driver =
neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
---
Best!
Thiago
Hi Matt,
Thanks for raising this. Both should be the same section.
[securitygroup] section exists in Havana and previous releases and
it is the right section name.
When we introduced enable_security_group option, we seem to have added
a new section
accidentally. We don't intended to introduce a n
I'm writing the ML2 configuration sections for the installation guide and
found a potential location conflict for the 'enable_security_group' key in
ml2_conf.ini. In the patch associated with this feature, the example
configuration file has this key under [security_group].
https://review.openstack
