14:00:45 #startmeeting kuryr 14:00:45 Meeting started Mon Jul 17 14:00:45 2017 UTC and is due to finish in 60 minutes. The chair is dmellado. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:46 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:49 The meeting name has been set to 'kuryr' 14:00:59 Hi kuryrs, who's here today for the meeting? 14:01:07 :D +1 14:01:23 #chair kzaitsev_ janonymous 14:01:24 Current chairs: dmellado janonymous kzaitsev_ 14:02:04 irenab: ltomasbo around? 14:02:11 hi 14:02:17 o/ 14:02:24 #chairs irenab 14:02:31 #chair irenab 14:02:32 Current chairs: dmellado irenab janonymous kzaitsev_ 14:02:45 o/ 14:02:53 #chair ltomasbo 14:02:53 Current chairs: dmellado irenab janonymous kzaitsev_ ltomasbo 14:03:01 so, let's go over a quick roll 14:03:09 #topic kuryr-kubernetes 14:03:33 I'll go first if noone has anything on here 14:03:47 :D 14:03:47 o/ 14:03:51 I was speaking with apuimedo about how to further improve testing in our CI 14:04:17 sorry i'm afk right now 14:04:52 awesome, my computer turned off 14:04:54 xD 14:05:26 so, I was saying that we were speaking about how to improve FT on our CI 14:05:30 #link https://blueprints.launchpad.net/kuryr-kubernetes/+spec/functional-testing-catch-up 14:05:34 o/ 14:05:44 pls do have a look and feel free to take over/improve something if you'd like to 14:06:00 basically we need to enhance by *lots* the current coverage for this 14:06:18 on our 2nd topic, we're currently lacking nested pod coverage 14:06:28 so I was thinking into creating another gate for this 14:07:02 based on the current document by kzaitsev_ 14:07:06 #link https://github.com/openstack/kuryr-kubernetes/blob/master/doc/source/installation/nested-vlan.rst 14:07:32 and current apuimedo effort on improving the overcloud by heat 14:07:40 ltomasbo: do you have the link around? I had, but had to restart 14:07:59 dmellado: shall we have different gate per distro? 14:08:13 https://review.openstack.org/#/c/472763/ 14:08:32 #link https://review.openstack.org/#/c/472763/ 14:08:45 irenab: well, I think that'd be a nice to but wouldn't get that far yet 14:08:53 that's just my 2 cents 14:09:13 irenab: what would you were thinking about? 14:09:17 how many gates and so? :D 14:09:49 dmellado: this patch assumes positive flow, once something is missing, like referenced image, script fails and not always able to remove the created parts 14:10:31 irenab: I'll take over the patch and have a look at your concerns 14:10:36 about the gates, I think we probably need one for Ubuntu and one for CentOS, but need to start somewhere 14:10:44 in any case the gate would be ephemeral 14:10:50 so that shouldn't matter *that* match for now 14:11:07 I do agree on the ubuntu/centos part but yeah 14:11:15 +1 14:11:50 In any case I've a few concerns about this running on the upstream gate in terms of memory consumption and capacity 14:11:56 but I'll check with the infra folks 14:12:10 dmellado: +1 14:12:20 looks like a great frankenstein, kinda putting together devstack and tripleO 14:12:44 so for now I'll try syncing with apuimedo and putting something together, just wanted to let you know that I'll be trying to coordinate and lead on this effort and 14:12:51 contributions and reviews are welcome! :D 14:12:55 heh 14:13:27 anyone has anything to say related to kuryr-k8s besides this? 14:13:51 yes 14:13:57 go for it garyloug ;) 14:14:25 we are working on CRD for multiple networks. We will update the google doc soon 14:14:29 That's all 14:14:45 thanks garyloug, do you have any link to the current doc? 14:15:56 kzaitsev_ws: this effort is probably related to the Sr-IOV patches you have 14:17:05 all right, so let's go to the next topic for now 14:17:14 #topic kuryr-libnetwork 14:17:25 We will update the TPR vs CRD section of this file with our findings 14:17:25 I don't have nothing on this, does anyone? 14:17:33 https://docs.google.com/document/d/1GNZbmVxE2n5j07YRlkx4zP-XbFSPI9UEcVifX1MRXyY/edit 14:17:39 garyloug: ack, thanks 14:17:46 #link https://docs.google.com/document/d/1GNZbmVxE2n5j07YRlkx4zP-XbFSPI9UEcVifX1MRXyY/edit 14:18:10 hongbin: around, anything on fuxi? 14:18:18 o/ 14:18:23 #chair hongbin 14:18:24 Current chairs: dmellado hongbin irenab janonymous kzaitsev_ ltomasbo 14:18:28 hi all 14:18:32 o/ 14:18:43 last week, the major update is on fuxi-kubernetes 14:18:43 #topic fuxi 14:19:05 zengchen updated revision of a few patches 14:19:30 besides that, the doc migration needs to be done on fuxi and fuxi-kubernetes 14:19:42 that is the tasks for this week 14:19:50 oh, I see, I do recall dhellmann email about that 14:19:59 yes 14:20:11 pls do let me know if you need help on that ;) 14:20:22 dmellado: thx 14:20:29 dmellado: that is all from me 14:20:35 hongbin: awesome, thanks! 14:20:39 #topic open discussion 14:21:02 Anyone has anything to say? otherwise I'll call it a day and go for an early coffee :P 14:22:27 dmellado: what about release cut on kuryr-lib? 14:23:23 irenab: oh, feel free to continue on that 14:23:27 could you summarize it? 14:23:49 I think kzaitsev_ws mentioned it over kuryr channel today 14:24:46 We merged the update of global requirements and if there were any other patches, we should probably have it release on Pike dates 14:24:59 Well, in any case I'd just like to remember everyone that we'll have a FF going in soon 14:25:04 #link https://releases.openstack.org/pike/schedule.html#p-3 14:25:20 and it's also Final release for client libraries 14:25:52 dmellado: lets ask apuimedo to check is some active action is required on kuryr-lib 14:25:59 +1 14:26:12 #action apuimedo to check if there's any action to do for kuryr-lib on Pike3 milestone 14:28:42 so, if noone has anything more to say I'd say I'll call it off for today's meeting 14:28:58 +1 14:29:23 thanks everyone! 14:29:26 #endmeeting