14:00:49 <apuimedo> #startmeeting kuryr
14:00:50 <openstack> Meeting started Mon Dec 12 14:00:49 2016 UTC and is due to finish in 60 minutes.  The chair is apuimedo. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:51 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:53 <openstack> The meeting name has been set to 'kuryr'
14:01:09 <apuimedo> Hello and welcome to another kuryr IRC weekly meeting
14:01:12 <apuimedo> who's here?
14:01:23 <ivc_> o/
14:01:29 <limao> o/
14:01:31 <garyloug> o/
14:01:52 <janonymous> o/
14:02:03 <irenab> hi
14:02:58 <apuimedo> alright, let's get started!
14:03:21 <apuimedo> #topic kuryr-libnetwork
14:04:26 <apuimedo> I think we are very close to getting the nested support with the reworked patch from lmdaly, mchiappero and ltomasbo https://review.openstack.org/#/c/400365/
14:04:27 <mchiappero> o/
14:04:31 <mchiappero> sorry I'm late
14:04:44 <apuimedo> if it passed the UTs it would be merged already :-)
14:04:45 <ltomasbo> o/
14:04:50 <mchiappero> yes, I have a couple of other fixes I haven't pushed yet
14:04:59 <hongbin> o/
14:05:17 <mchiappero> the unit tests are almost done, but I have a few questions on those, maybe gerrit is a better place
14:05:28 <ltomasbo> after that is merged I will rework my patch too on top of that one, as a new vlan.py driver
14:05:32 <mchiappero> later I'l push some more code
14:05:40 <apuimedo> irenab: we have a couple of easy merges https://review.openstack.org/#/c/396519/ https://review.openstack.org/#/c/408501/
14:05:50 <irenab> apuimedo: will check
14:06:04 <apuimedo> ltomasbo: the code shouldn't change, so if you have time, maybe you can start the rework ;-)
14:06:22 <apuimedo> mchiappero: okay, otherwise we can just discuss in #openstack-kuryr
14:06:28 <ltomasbo> good, I'll do that later today
14:06:31 <mchiappero> ok, thank you
14:06:51 <mchiappero> but my goal is to push all by tomorro morning, possibly earlier
14:07:06 <janonymous> mock conversion is completed for test cases. just base.py few functions removal which does not affect anything
14:07:09 <apuimedo> mchiappero: good! Remember to sleep
14:07:23 <apuimedo> janonymous: great!
14:07:25 <mchiappero> I know, I'm also travelling today...
14:07:32 <apuimedo> sorry I didn't get back to you earlier?
14:07:34 <mchiappero> thank you all for your reviews
14:07:37 <apuimedo> s/?//
14:07:44 <apuimedo> janonymous:
14:07:57 <apuimedo> mchiappero: thank you for the base patch
14:08:08 <apuimedo> anything else on kuryr-libnetwork?
14:08:25 <apuimedo> there's a patch from vikas on the neutron feature checks that needs rework
14:08:26 <janonymous> apuimedo: we can discuss it in kuryr channel later :)
14:08:35 <apuimedo> janonymous: please do
14:08:37 <apuimedo> :-)
14:09:24 <apuimedo> and then I'm not entirely sure if we didn't break uwsgi multithreaded support by moving around those checks, which it seems to me are only done on __main__ now, which IIRC uswgi does not run
14:10:09 <apuimedo> #action apuimedo to check if we broke uwsgi and if, file a bug so that we cover it with fullstack testing
14:10:18 <apuimedo> #topic kuryr-lib
14:10:51 <apuimedo> I don't think we have anything on kuryr-lib, but if anybody disagrees, please go ahead and bring some topic
14:12:20 <apuimedo> alright, moving on
14:12:25 <apuimedo> #topic fuxi
14:12:35 <hongbin> hi
14:12:40 <apuimedo> #chair hongbin
14:12:41 <openstack> Current chairs: apuimedo hongbin
14:12:47 <apuimedo> hongbin: some update?
14:12:53 <hongbin> so, last week, i tried to setup the CI
14:13:10 <hongbin> There is a patch to project-config and apuimedo already voted a +1
14:13:14 <hongbin> #link https://review.openstack.org/#/c/408330/
14:13:28 <hongbin> The review required us to un-wip the depended patch
14:13:36 <hongbin> #link https://review.openstack.org/#/c/408329/
14:13:42 <vikasc> o/
14:13:47 <hongbin> however, this patch has no wip at all :)
14:14:03 <hongbin> but it is better to fast merge above patch to get the gate working
14:14:18 <apuimedo> hongbin: agreed
14:14:33 <hongbin> besides that, the devstack plugin is merged, thanks apuimedo for reviews
14:14:38 <apuimedo> irenab: vikasc: please, try to find some time review those patches
14:14:48 <irenab> apuimedo: ok
14:14:49 * apuimedo too, of course
14:15:00 <hongbin> then, there are several patches that setup the fullstack tests
14:15:01 <vikasc> apuimedo, sure
14:15:16 <hongbin> #link https://review.openstack.org/#/c/403931/
14:15:24 <apuimedo> hongbin: yes. It is very important we get the fullstack related patches in asap
14:15:26 <hongbin> #link https://review.openstack.org/#/c/403941/
14:15:33 <hongbin> apuimedo: yes
14:15:41 <hongbin> that is for last week
14:15:50 <apuimedo> thanks hongbin!
14:16:05 <hongbin> apuimedo: after the CI was setup, i think we need to think what is next in the future (i.e. the roadmap)
14:16:13 <apuimedo> hongbin: agreed
14:16:22 <apuimedo> We depend on people bringing up use cases
14:16:32 <hongbin> yes
14:16:37 <irenab> hongbin: any agenda you want to propose?
14:16:50 <apuimedo> I personally don't have anything in mind, but I'm looking forward to hear about them
14:16:56 <hongbin> irenab: no, i would like to work with the community to figure out the agenda
14:17:34 <apuimedo> hongbin: it is important to talk with the users. I think you have some internal ones, I wonder if there are others
14:18:00 <hongbin> apuimedo: i will try to figure out if there are others :)
14:18:06 <apuimedo> thanks hongbin!
14:18:08 <apuimedo> #topic kuryr-kubernetes
14:19:50 <apuimedo> #info ivc_ posted final looking versions of services devstack and handler patches (though the latter needs splitting) https://review.openstack.org/#/c/407244/ and https://review.openstack.org/#/c/376045/
14:19:57 <apuimedo> please, review the latter
14:20:04 <apuimedo> ivc_: I have some issue on the former
14:20:19 <ivc_> apuimedo what issue?
14:21:15 <apuimedo> http://paste.openstack.org/show/592114/
14:21:28 <apuimedo> I was just running it now pre-merge
14:21:35 <apuimedo> maybe I missed some config
14:21:45 <apuimedo> I'll check later
14:22:23 <ivc_> there was an issue in an earlier version, but i've updated the patch recently
14:22:29 <apuimedo> apart from this two patches, we need to work on porting the nested port drivers from kuryr-libnetwork
14:22:48 <vikasc> i am trying to launch a pod with current kuryr-k8s but observing some errors. Trying to understand.
14:22:50 <apuimedo> I think vikasc started looking at it, maybe ltomasbo and mchiappero will want to as well
14:22:52 <irenab> apuimedo: to k8s or to lib?
14:23:20 <apuimedo> irenab: in this case, it will be kuryr-libnetwork -> kuryr-kubernetes -> kuryr-lib, then removing it from the former two
14:23:38 <apuimedo> enable fullstack tests just like fuxi is doing
14:23:59 <ivc_> vikasc, ping me on #openstack-kuryr if you have some issues
14:24:11 <irenab> apuimedo:  so port drivers ported to k8s should work for libnetworks too, right?
14:24:17 <vikasc> ivc_, sure
14:24:19 <apuimedo> and saving binding info in /run files for cleanups
14:24:42 <apuimedo> irenab: well, how I think it will go will be
14:24:55 <ivc_> apuimedo we have 'slightly' different driver models in libnetwork and k8s
14:24:56 <apuimedo> the move to k8s will consist in making it stevedore based
14:25:10 <apuimedo> then we'll have to refactor kuryr-lib for 1.0.0 to be stevedore based too
14:25:13 <apuimedo> and kuryr-libnetwork as well
14:25:27 <apuimedo> and we move the drivers to kuryr-lib
14:25:33 <apuimedo> ivc_: exactly
14:25:53 <apuimedo> we want to end up standardizing on a model almost like what we have in k8s
14:26:37 <irenab> apuimedo: I would like to suggest to register bp for this wrok
14:26:47 <irenab> work
14:26:48 <apuimedo> irenab: agreed
14:26:52 <ivc_> irenab +1
14:27:17 <ivc_> i think we'll cover that on wed meeting
14:27:20 <vikasc> first kuryr-k8s, then kuryr-libnetwork and then finally to kuryr-lib
14:27:21 <apuimedo> #action apuimedo to register a blueprint for the nested driver porting to the new stevedore driver arch
14:27:30 <vikasc> wed meeting?
14:27:51 <irenab> vikasc: we want to sync on improvments to existing k8sPoC
14:27:55 <apuimedo> vikasc: there will be an extraordinary videoconf meeting, it came on on irc earlier today
14:28:10 <apuimedo> as usual, everybody feel free to ping irenab to join :-)
14:28:12 <vikasc> irenab, apuimedo nice!
14:28:15 <apuimedo> since she has the invite
14:28:25 <vikasc> irenab, please consider me
14:28:41 <irenab> I can post a hangout link, so anyone can join without special invitation
14:28:50 <mchiappero> want to join!
14:29:01 <apuimedo> irenab: good idea
14:29:08 <apuimedo> post it here with #link
14:29:20 <irenab> #link  https://plus.google.com/hangouts/_/calendar/aXJlbmFiLmRldkBnbWFpbC5jb20.2kstghq4tavlmnhkfpnrjqd3j4?authuser=1
14:29:25 <apuimedo> thanks irenab!
14:29:34 <irenab> np
14:29:46 <apuimedo> irenab: what about we send the agenda to the mailing list
14:29:52 <apuimedo> so people can prepare?
14:30:15 <irenab> apuimedo: I thouht its going to be just sync on short term improvments so we can merge devref
14:30:35 <apuimedo> yes, it is
14:30:53 <apuimedo> irenab: I'll try to itemize it and send an email
14:31:08 <apuimedo> irenab: ivc_: I'll ping you later about it
14:31:14 <ivc_> apuimedo sure
14:31:20 <apuimedo> anything else on kuryr-kubernetes?
14:31:39 <irenab> apuimedo: ok
14:31:43 <ivc_> apuimedo we can also try to decide on the more long-term roadmap
14:32:02 <apuimedo> ivc_: if time allows :-)
14:32:05 <irenab> apuimedo: ivc_ shall we have 2 meetings then?
14:32:06 <ivc_> since we'll have many ppl joining
14:32:26 <apuimedo> irenab: let's plan 45 minutes
14:33:03 <apuimedo> ivc_: irenab: let's have an etherpad
14:33:09 <apuimedo> and split it in short term and long term
14:33:10 <irenab> please anyone who plans to join, go through the devref patch and preferably code
14:33:12 <ivc_> good idea
14:33:32 <irenab> apuimedo: +1
14:33:59 <irenab> apuimedo: I can start the etherpad
14:34:05 <apuimedo> #link https://etherpad.openstack.org/p/kuryr-kubernetes-dec14-syncup
14:34:11 <apuimedo> irenab: I already created it
14:34:14 <apuimedo> feel free to add to it
14:34:16 <apuimedo> :-)
14:34:21 <irenab> cool
14:34:52 <vikasc> time?
14:35:01 <irenab> Wed 11UTC
14:35:21 <irenab> apuimedo: Will you be sending the email or want me to send it?
14:35:38 <apuimedo> irenab: I can ;-)
14:35:57 <apuimedo> #action apuimedo to send the email to the list about the meeting
14:36:03 <apuimedo> anything else?
14:36:30 <janonymous> i have a point to mention, as kuryr has now many projects under it ..i would like to propose inclusion of a new project: kuryr-specs to maintain all the specs docs for kuryr-* projects,many projects have it like nova,qa etc what is the community viewpoint on it?
14:36:46 <apuimedo> #topic general
14:36:54 <janonymous> ops!
14:37:53 <ivc_> i think we went through this once before and decided to keep specs under 'kuryr' and blueprints/devrefs under specific projects
14:38:08 <apuimedo> #startvote Have openstack/kuryr-specs and move specs there? Yes, No, needs_discussion
14:38:09 <openstack> Begin voting on: Have openstack/kuryr-specs and move specs there? Valid vote options are Yes, No, needs_discussion.
14:38:10 <openstack> Vote using '#vote OPTION'. Only your last vote counts.
14:38:31 <apuimedo> ivc_: that is indeed the last decision we took
14:38:31 <ivc_> #vote Yes
14:38:56 <irenab> #vote:Yes
14:38:57 <openstack> irenab: :Yes is not a valid option. Valid options are Yes, No, needs_discussion.
14:39:01 <vikasc> #vote Yes
14:39:05 <apuimedo> vikasc: mchiappero limao irenab ltomasbo cast your votes :-)
14:39:17 <apuimedo> #vote Yes
14:39:22 <irenab> #vote Yes
14:39:22 <ltomasbo> #vote Yes
14:39:26 <limao> #vote Yes
14:39:34 <vikasc> full majority yes :)
14:39:37 <hongbin> if the specs repo is created, fuxi would like to leverage it as well :)
14:39:45 <apuimedo> hongbin: gladly!
14:39:46 <janonymous> :) great!
14:39:51 <apuimedo> #endvote
14:39:52 <openstack> Voted on "Have openstack/kuryr-specs and move specs there?" Results are
14:39:53 <openstack> Yes (6): ltomasbo, ivc_, vikasc, irenab, limao, apuimedo
14:40:06 <apuimedo> very well
14:40:42 <apuimedo> #action apuimedo to do the administrative work of setting up the new repo
14:40:57 <apuimedo> hongbin: I'm counting on you to move the fuxi specs
14:41:05 <hongbin> apuimedo: ack
14:41:11 <apuimedo> and the others for the rest :-)
14:41:34 <irenab> sorry, need to go. Thanks for the meeting
14:41:43 <apuimedo> if everybody is okay with it, devrefs will still be on their closest repo
14:41:47 <apuimedo> thanks to you irenab!
14:42:03 <apuimedo> ivc_: vikasc: hongbin: ltomasbo: mchiappero: ^^
14:42:26 <hongbin> i am ok with that
14:42:34 <ivc_> +1
14:42:35 <ltomasbo> ok
14:42:40 <vikasc> +1
14:42:49 <apuimedo> very well, as always, we can revisit later
14:42:51 <apuimedo> :-)
14:43:11 <apuimedo> #info devrefs will evolve in the same repo as the code
14:43:25 <apuimedo> Anything else?
14:44:30 <apuimedo> very well then!
14:44:36 <apuimedo> #endmeeting