-
Epic
-
Resolution: Done
-
Major
-
None
-
Kuryr: General scalability improvements
-
Improvement
-
False
-
False
-
Done
-
OCPPLAN-6500 - OpenStack Kuryr SDN Improvements
-
Impediment
-
0% To Do, 0% In Progress, 100% Done
The amount of Neutron Ports created in a cluster with Kuryr has direct impact on the Pod and possibly Namespace readiness or cluster clean up.
During Pods creation, Kuryr relies on a Ports pool functionality that makes Neutron Ports ready to be used by the Pods. When a population happens Kuryr has to create Neutron Ports in a bulk request, tag them all and attach them to the Trunk. If there is a considerable amount of Pods in different Namespaces and multiple Nodes, multiple frequent population will happen, which directly impacts Neutron performance. Besides that, when a Namespace is deleted or a cluster is destroyed, the Ports clean up will take really long as they are done sequentially.
We have also seen cases when the Subnets and Networks become leftovers upon Namespace creation or deletion.
As part of this epic we should provide a better management of Ports/Networks/Subnets in Kuryr for the scenarios described above to improve general response time.