<div dir="ltr"><div>Folks,</div><div><br></div><div>I have had discussions with some folks individually about this but I would like bring this to a broader audience.</div><div><br></div><div>I have been playing with security groups and I see the notion of 'default' security group seems to create some nuisance/issues.</div><div><br></div><div>There are list of things I have noticed so far:</div><div><ul><li>Tenant for OpenStack services (normally named service/services) also ends up having default security group. </li><li>Port create operation ends up ensuring default security groups for all the tenants as this completely seems out of the context of the tenant the port operation takes place. (bug?) </li><li>Race conditions where if system is stressed and Neutron tries to ensure the first default security group and in parallel another call comes, Neutron ends up trying to create multiple default security groups as the checks for duplicate groups are invalidated as soon as the call make past a certain point in code.<br></li><li>API performance where orchestration chooses to spawn 1000 tenants and we see unnecessary overhead.<br></li><li>For plugins that use RESTful proxy backends require the backend systems to be up at the time neutron starts. [Minor, but affects some packaging solutions]</li></ul></div><div><br></div><div>To summarize, is there a way to disable default security groups? Expected answer is no; can we introduce a way to disable it? If that does not make sense, should we go ahead and fix the issues around it? </div><div><br></div><div>I am sure some of you must have seen some of these issues and solved them already. Please do share how do tackle these issues?</div><div><br></div>Thanks,<br clear="all"><div><div dir="ltr">Fawad Khaliq<div><br></div></div></div>
</div>