14:07:23 #startmeeting kuryr 14:07:23 Meeting started Mon Apr 30 14:07:23 2018 UTC and is due to finish in 60 minutes. The chair is apuimedo. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:07:24 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:07:26 The meeting name has been set to 'kuryr' 14:07:36 Hi everybody and welcome to the weekly kuryr meeting 14:07:44 #topic kuryr-kubernetes 14:08:35 #info today we released 0.4.3 that includes an important bugfix for service deletion when using octavia 14:08:49 yboaron_: I still think that we should catch the exception you proposed 14:09:02 yboaron_: ltomasbo: thoughts on that? 14:09:47 apuimedo, I don't think we need, after we have the cascading delete merged 14:10:29 I don't have a strong opinion there, but catching the exception will not hurt 14:10:34 yboaron_: cause this can't happen with neutron-lbaas, can it?\ 14:10:49 apuimedo, that's correct 14:12:26 apuimedo, it can't happen in LBaaSV2 14:12:47 yboaron_: ok. So it that case, let's abandon it 14:12:53 ok! 14:13:04 #action yboaron_ to abandon the lbaas badrequest exception catching bug 14:13:19 apuimedo, will do it 14:13:42 yboaron_: talk to us a bit about the ingress controller effort 14:14:02 apuimedo, before reaching the ingress controller ,we have another issue with Octavia LB , 14:14:12 #link https://bugs.launchpad.net/kuryr-kubernetes/+bug/1768009 14:14:13 Launchpad bug 1768009 in kuryr-kubernetes "Service edit (scale out number of members) - cause exception" [Undecided,New] 14:14:45 all the Get list + fields are not supported at Octavia 14:15:03 there's an open patch for that in Octavia 14:15:19 #link https://review.openstack.org/#/c/559842/ 14:15:45 nice, new bugs 14:15:48 let's see 14:16:24 so, from Kuryr perspective, all the _find_xx functions in Lbaasv2.py file will cause an exception 14:16:57 yboaron_: I see it is a backport candidate 14:17:06 Yes 14:17:32 I"ll open a bug for that in Octavia and mark that it affects Kuryr 14:17:32 #action yboaron_ to talk to Octavia folks to see whether it is likely to be backported and see how we can help it get in quickly 14:17:55 also, please test that the bug solves it and comment on the patch if it does 14:18:13 OK 14:19:00 now I can elaborate about the Ingress controller .. 14:19:09 :) 14:19:19 so, I have decided to split the work into two phases 14:19:44 1. just add the Ingress controller 14:19:58 2. add the ocp-route and service handlers 14:20:16 I have sent 4 patches that covers phase 1 14:20:49 yboaron_: can you argue about the split 14:20:59 vs just having handlers 14:21:06 loaded as the other handlers are loaded 14:22:02 we"ll still have the handlers (ocp-route and service) loaded using the pluggable feature 14:22:09 but in phase '2' 14:22:43 in first phase, we just have the Ingress controller LB creation and Devstack related stuff 14:22:52 oh, I understand now 14:22:58 phase 1 is dpeloyment 14:23:07 phase 2 happens in the kuryr-controller instead 14:23:09 is that right? 14:23:10 correct 14:23:52 also prt of phase '1', as the LB created manually and controller just need to sync with it 14:24:14 but in general most of phase '1' about deployment 14:24:36 also added two zuul gates for ingress controller in K8S and Openshift 14:24:59 as one of the patches of phase '1' 14:25:02 yboaron_: wouldn't openshift gate be with Routes handler instead? 14:25:48 you mean to enable Ingress controller by default in openshift? 14:26:54 I thought that route handlers should be tested by tempest tests (e.g: create service+route and try to curl the name) 14:27:51 yboaron_: sure 14:30:48 alright, let's move to the next work in progress 14:31:18 ltomasbo: how's the work on the namespace handling for subnet per namespace effort? 14:31:53 apuimedo, it is working and I addressed some of the comments 14:32:02 apuimedo, I need to find some time to add the unittesting 14:32:32 ltomasbo: yboaron_: and I'm expecting tempest tests for the service deletion and for the namespace handlers 14:32:35 :-) 14:32:40 xD 14:32:56 it in my list .. 14:33:01 yes yes, first the unit tests, and then I'll add some tempest too 14:33:27 :-) 14:33:30 and I reply to some of the comments that yossi made, and I have a todo from it! 14:33:41 perfect 14:33:45 thanks 14:33:53 so, probably on thursday I'll spin a new version, but the current ones are testable 14:33:58 does anybody have anything else on kuryr-kubernetes 14:33:59 so, feel free to give it a try! 14:34:06 ltomasbo: let me know when you do so I make sure to review them 14:34:24 I have a few backports, that we may merge or abandon 14:34:29 (probably the second) 14:35:01 apuimedo, https://review.openstack.org/#/c/563079/ 14:35:10 * apuimedo looking 14:35:20 ltomasbo: let's abandon this one 14:35:25 what else? 14:35:41 and similar for these two: https://review.openstack.org/#/c/563078/ https://review.openstack.org/#/c/564113/ 14:37:14 I think we should take the first 14:37:29 check what's wrong with the gates with it 14:37:40 the second as well 14:37:58 ok! 14:38:34 second one passes the gate, it is just a matter if we want to merge it now or later 14:38:51 we're not waiting for any urgent backport 14:38:52 following yossi's comments 14:39:02 I'll check his comment again later 14:39:09 ok! that's all 14:39:12 anything else? 14:39:51 nope 14:39:55 Not from my side 14:41:37 very well 14:41:42 #topic kuryr general 14:41:49 Does anybody have any other topic? 14:43:31 alright. Let's close it early today 14:43:36 Thank you all for joining! 14:43:39 #endmeeting