[kuryr] Meeting at PTG - follow up
On Fri, 2019-11-08 at 06:53 +0100, MichaÅ? Dulko wrote:
> Thank you all for a constructive discussion at the Shanghai PTG. First
> of all I want to clarify that the Neutron improvements in bulk port
> creation code I talked about were only merged in Stein and are not
> available in Queens. Sorry about that, my mistake.
> Below I want to list some highlights from the discussion.
> * There seemed no pushback on switching to independent release model,
> so I'll follow up on that soon.
> * We discussed using RPC instead of API polling to detect when port
> becomes ACTIVE in Neutron (https://review.opendev.org/#/c/669642/).
> I commented on the review with a follow up that came from discussion
> with Neutron team. Apparently there are 2 better ways of doing this.
> Let's continue that discussion on the review.
> * We know that we don't support running as a second CNI plugin on
> Multus because of eth0 being hardcoded as interface name and kuryr-
> controller handling pods that do not had CNI requests. This is
> something to solve.
> * Apparently we all suffer the same problems with Neutron performance
> when starting a bigger workload on Kuryr-configured K8s cluster
> (think big Helm chart, multiple operators or simultaneous test
> suite). This all comes to reducing the number of calls to Neutron.
> We still don't see a feasible solution to solve this problem, but it
> seems to be a priority for both Samsung and Red Hat at the moment.
> Let's see if we'll meet again in Vancouver!
I forgot to add link to raw etherpad with notes: