14:08:36 #startmeeting Kuryr 14:08:36 Meeting started Mon Jun 10 14:08:36 2019 UTC and is due to finish in 60 minutes. The chair is dulek. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:08:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:08:40 The meeting name has been set to 'kuryr' 14:08:58 Hi anyone! ;) 14:09:18 I'm tempted to switch that to "office hours" model. I don't really have much update today. 14:09:34 But well, let's seeā€¦ 14:10:30 There are probably 4 bigger things that got merged. 14:10:37 (or are close to get merged) 14:10:52 1. NP stuff, next bugfixes landed. 14:11:17 2. I proposed updating Python 3 containers to Fedora 30. Seems like it's a smooth transition. 14:11:22 https://review.opendev.org/#/c/663073/ 14:12:03 3. aperevalov proposed https://review.opendev.org/#/c/660152/ and it got merged. The default kuryr-daemon listening port is now 5036. 14:12:25 o/ 14:12:38 4. And last but not least - I rewrote kuryr-cni to golang: https://review.opendev.org/#/c/663084/. It's just the plugin part, not kuryr-daemon! 14:12:49 The rationale is in the commit message. 14:14:24 I could ping alisanhaji, as this will unblock Kuryr in Magnum, but seems he's offline 14:14:38 Sooo that's all that happened over last week, I think. 14:14:47 ltomasbo, maysams: Anything to add? 14:15:50 there is not much from my side, besides that the NP bug fixes and the last NP with named port ps got merged 14:19:10 dulek, I was simply looking at the gates 14:19:17 and trying to make services work in general 14:19:30 both on openshift and none openshift gates, and on the ones with pooling 14:19:52 found out a problem with FIPs and OVN, as well as with the threading approach to check the services 14:20:14 seems to have more normal failures now on: https://review.opendev.org/#/c/663356/ 14:20:25 but still need to investigate further 14:20:33 ltomasbo: Though still failures? ;) 14:20:58 dulek, yes! but seems to be reduced to a fewer number 14:21:08 like the one with the pod and overlay taht you hitted 14:21:21 the crio is related to the devstack-pluging configuration 14:21:43 and there are others related to unexpected responses... 14:21:52 ltomasbo: Yes, crio isn't working for a while now. I tried to fix it a long while ago, but without success. :( 14:22:01 so, not great, but looking a bit better 14:22:10 ltomasbo: Okay, good! 14:23:59 I'll work on gate failures during following weeks. 14:24:24 So I guess we can finish the meeting and just stay in #openstack-kuryr in case anyone has some question/comment/issue. 14:24:31 #endmeeting