Default ulimit value for neutron containers (DHCP, L3 and OVS agents) limits a number of SDN entities in production environment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Slawek Kaplonski |
Bug Description
Bug originally reported by Alex Stupnikov:
Description of problem:
TripleO sets ulimits for different containers since RHOSP 13 [1].
Default value for neutron services and nova-compute is 1024. This
default doesn't work well for nova-compute with huge number of attached
disks, so I have reported bug [2].
Today customer informed me that neutron services are ALSO AFFECTED:
he faced issues with DHCP agents after creating 250 tenant networks
(quite low number) and was able to solve them after increasing default
ulimit value by defining DockerNeutronDH
I have asked neutron developers to provide recommendations for defaults for the following parameters and was told to report the bug:
DockerNeutronDH
DockerNeutronL3
DockerOpenvswit
[1] https:/
[2] https:/
Changed in tripleo: | |
assignee: | nobody → Slawek Kaplonski (slaweq) |
status: | New → In Progress |
Changed in tripleo: | |
importance: | Medium → High |
tags: | added: queens-backport-potential |
tags: | added: edge |
So for the record we lowered it to 1024 because rootwrap didn't like the larger default value. See Bug 1760471 So we to figure out a happy medium between 131072 and 1024