14:01:08 <dmellado> #startmeeting kuryr 14:01:08 <openstack> Meeting started Mon Jul 9 14:01:08 2018 UTC and is due to finish in 60 minutes. The chair is dmellado. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:10 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:13 <openstack> The meeting name has been set to 'kuryr' 14:01:26 <dmellado> o/ Hi folks, who's here for today's super-duper-exciting-as-ever kuryr meeting? 14:01:33 <snapiri> o/ 14:01:38 <dmellado> Hi snapiri ;) 14:01:54 <garyloug> o/ 14:01:55 <snapiri> Hi :) 14:02:10 <dulek> o/ 14:02:12 <dmellado> ltomasbo: dulek I know you're around too 14:02:14 <dmellado> \o/ 14:02:26 <dmellado> #chair dulek 14:02:27 <openstack> Current chairs: dmellado dulek 14:02:34 <ltomasbo> ups! sorry! I'm here yes! 14:02:40 <dmellado> #chair ltomasbo 14:02:40 <openstack> Current chairs: dmellado dulek ltomasbo 14:02:45 <dmellado> irenab: you around here as well? 14:03:06 <dmellado> and then maybe.... 14:03:09 <dmellado> and it's not wonderwall 14:03:15 <dmellado> itzikb: juriarte gcheresh ? 14:03:34 <juriarte> o/ 14:03:43 <dmellado> awesome! 14:03:45 <dmellado> so let's start 14:03:49 <dmellado> #topic kuryr-kubernetes 14:04:02 <itzikb> dmellado: here 14:04:14 <dmellado> Just wanted to let you know that after our dreaded fight with the requirements we've gotten the gates to pass 14:04:22 <dmellado> and we'll be adding openshift client as a global-requirement soon 14:04:46 <dmellado> basically, as soon as tonyb wakes up and gives his +2 again after the rebase 14:05:05 <dmellado> Thanks for your help tonyb! ;) 14:05:19 <dmellado> #link https://review.openstack.org/#/c/580093/ 14:05:45 <dulek> Another heads up - Rocky-3 is coming at 26th - https://releases.openstack.org/rocky/schedule.html. 14:05:49 <dmellado> besides this, I've finally gotten time and I'm working again on the NPS patch, I've a WIP one where I would appreciate early comments if you'd like 14:06:05 <dmellado> dulek: I was going to go for that after the patches! ;) 14:06:18 <dmellado> let's wait for the releases and so after we've gone through a roll call ;) 14:06:21 <dulek> dmellado: Whoops, sorry. 14:06:43 <dmellado> how about you folks? any work that you'd like to share with us? 14:07:10 <dmellado> dulek: now you go first :P 14:07:10 * dulek was gone through most of the week. 14:07:19 <ltomasbo> I was completing the network per namespace, with isolation between the namespaces 14:07:34 <ltomasbo> I had most of the patch working, with tempest test included 14:07:42 <ltomasbo> but I'm now trying to get isolation for the services too 14:08:13 <ltomasbo> and getting a little bit block with octavia, need to check how to get the amphora VM port from the loadbalancer creation steps 14:08:14 <snapiri> I have tried to progress with the neutron-* services on the gates. Can't get ovn to work. 14:08:16 <dmellado> ltomasbo: cool, we'll need to sync regarding the SG and so around this week 14:08:28 <dmellado> snapiri: did you get to speak with the ovn folks about this? 14:08:37 <snapiri> it seems like they are working with the legacy services 14:08:39 <ltomasbo> and then I'll also take a look at why the lbaasv2 gate is failing (timing out) for the patch 14:08:48 <ltomasbo> https://review.openstack.org/#/c/579181/12 14:09:12 <dmellado> snapiri: they might've not migrated yet for a reason 14:09:16 <dmellado> you can ping lucasalvaresgomes 14:09:19 <snapiri> I've put that aside for now as I have other tasks on my plate. 14:09:19 <dmellado> or dalvarez 14:09:21 <dmellado> on that 14:09:41 <dmellado> you might want to add a flag on devstack for that until it's sorted out for ovn ;) 14:09:43 <snapiri> dmellado: will try to remember when I get back to working on it 14:09:47 <dmellado> thanks snapiri 14:09:55 <dmellado> snapiri: ack, yw! ping me if you don't 14:10:33 <dmellado> so, who goes next? 14:10:40 <garyloug> I can 14:10:49 <dmellado> garyloug: go for it! 14:11:02 <garyloug> Unit tests and documentation pushed for nested DPDK 14:11:15 <garyloug> I just need to do tempest tests 14:11:31 <garyloug> But I think folks can start reviewing if they get time 14:11:39 <dmellado> garyloug: awesome, after we go through all this, I wanted to speak with you about a session for the topic on Berlin summit 14:11:41 <dmellado> ;) 14:11:47 <dmellado> we'll do, thanks! 14:11:49 <garyloug> cool 14:12:14 <garyloug> also, there's one test failling, to do with requirements, can't figure it 14:12:19 <dmellado> itzikb: do you want to share about your totally needed patches to testing? 14:12:25 <dmellado> garyloug: oh, I can help with that 14:12:27 <dmellado> I'll take a look 14:12:31 <garyloug> cool, thx 14:12:56 <itzikb> dmellado: I think they are ready to be merged. basically adding a job to run tests in serial 14:13:09 <dmellado> itzikb: one of the things I've been concerns it, tbh 14:13:16 <dmellado> is with the order of the patches 14:13:21 <dmellado> could you share it here on order 14:13:27 <dmellado> ? 14:13:39 <dmellado> at least for me to get a whole understanding on what depends on what ;) 14:13:46 <itzikb> dmellado: sec 14:13:51 <dulek> garyloug: Seems like this is a global thing being broken. 14:14:21 <itzikb> dmellado: this is the first https://review.openstack.org/#/c/579808/ 14:14:26 <itzikb> dmellado: sec is https://review.openstack.org/#/c/580222/ 14:14:59 <itzikb> dmellado: and gcheresh's patch https://review.openstack.org/#/c/552498/ whic depends on these two 14:15:01 <dulek> garyloug: You can try rebasing the patch, seems like parent is pretty old. 14:15:20 <dmellado> itzikb: awesome, thanks! 14:15:20 <garyloug> dulek, yea, not familiar with the problem but maybe it's already fixed as dmellado says above. Sure I'll try that! 14:16:19 <dmellado> garyloug: in any case if after rebasing you're still hitting that 14:16:32 <dmellado> you might need to check global-reqs and maybe propose a patch to it 14:16:42 <dmellado> in any case let's check after the rebase if it doesn't fix it ;) 14:16:48 <garyloug> cool, ok 14:17:06 <dmellado> so dulek go ahead, you can now announce the deadlines :P 14:17:59 <dulek> So! Another heads up - Rocky-3 is coming at 26th - https://releases.openstack.org/rocky/schedule.html. 14:18:22 <dulek> Also a week for that is release deadline for any libraries. 14:19:17 <dulek> And then we'll be in RC timeout, so probably no more features unless we're getting some feature freeze exception. 14:19:35 <dulek> I think dmellado will come up with the lightweight process to apply for that. ;) 14:20:14 <dmellado> dulek: yeah, please everyone take that into consideration 14:20:37 <dmellado> if you think you won't be able to make it *but* you'd think you'd be close let me know 14:20:50 <dmellado> I'll be watching over this and send a reminder email in any case 14:21:09 <dmellado> dulek: damn, feels like we're always releasing xD 14:21:43 <dmellado> and yet another heads-up 14:21:57 <dmellado> folks, we're also close to the deadline for Berlin CfP 14:22:08 <dmellado> https://etherpad.openstack.org/p/kuryr-kubernetes-berlin-summit 14:22:13 <dmellado> I've created this etherpad 14:22:21 <dmellado> so we can track possible speakers 14:22:23 <dmellado> sessions and so 14:22:38 <dmellado> so, I would like to get the time to do some roll call on sessions 14:22:43 <dmellado> any ideas so far for Berlin 14:22:47 <dmellado> something you'd like to share? 14:23:16 <dmellado> garyloug: you can add your session there ;) 14:24:10 <dmellado> in any case I'd like to see some discussions there within this week 14:24:13 <dulek> Hm, hm, how about something on making Kuryr a first-class Kubernetes application? 14:24:34 <dmellado> dulek: sounds like something you'd like to write an abstract about there 14:24:57 <dulek> I mean we've did some mistakes with containerization and Kubernetesization (xD?), so might be worth speaking up about those. 14:24:59 <dulek> dmellado: Sure, sure. 14:25:06 <dmellado> topics aren't limited only to dev 14:25:09 <dmellado> bug also to ops 14:25:19 <dmellado> for instance we can get to speak about the path to multinode 14:25:28 <dmellado> make a hands-on-lab 14:25:35 <dmellado> (Even relying on rdocloud xD) 14:26:07 <dmellado> but dulek what you speak about sounds interesting 14:26:25 <dmellado> I'll ping you later (prob tomorrow) to draft an abstract and put something concrete there 14:26:38 <dmellado> I was also thinking about adding topics such as 14:26:47 <dmellado> 'How to create a new handler on Kuryr-K8s' 14:26:49 <dulek> dmellado: Yeah, unlike KubeCon adding "Kubernetes" to abstract for the Summit is seen really okay by people who are deciding. 14:26:50 <dmellado> for the upstream institute 14:27:07 <dmellado> or the onboarding 14:27:26 <dmellado> as there might be people interested on listening for third-party events that we don't care (yet) about 14:28:00 <dulek> dmellado: I'm not sure if we have enough expertise to handle session about OpenStack Cloud Provider? 14:28:11 <dulek> dmellado: Or even if it was talked about before? 14:28:12 <dmellado> that'd be an interesting topic 14:28:23 <dmellado> hmm from the Kuryr part I'm pretty sure it hasn't 14:28:55 <dulek> dmellado: Actually I thought on the Kubernetes Cloud Provider, not exactly Kuryr. 14:29:38 <dmellado> dulek: yeah, but I mean that you could always try to speak about possible kuryr usecases 14:29:47 <dmellado> in any case I'm adding the topic and we can work on the abstract 14:32:42 <dmellado> all right, so this makes it for kuryr-kubernetes unless anyone has anything else to share! 14:36:06 <dmellado> #topic open discussion 14:37:58 <dmellado> so no more discussions, not even open nor closed 14:38:02 <dmellado> I'm calling it a day 14:38:04 <dmellado> thanks folks! 14:38:08 <snapiri> cheers 14:38:12 <dmellado> #endmeeting kuryr