14:01:05 <apuimedo> #startmeeting kuryr
14:01:06 <openstack> Meeting started Mon May 23 14:01:05 2016 UTC and is due to finish in 60 minutes.  The chair is apuimedo. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:07 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:10 <openstack> The meeting name has been set to 'kuryr'
14:01:28 <apuimedo> Hello! Welcome to yet another kuryr weekly meeting
14:01:33 <irenab> apuimedo: hi
14:01:34 <apuimedo> who's here for the show?
14:02:11 <apuimedo> banix: ping
14:03:16 <apuimedo> it seems only Irena and I got here with the meeting time change
14:03:18 <irenab> probably banix is not aware of the meeting time change
14:03:32 <apuimedo> I'll go update the meeting and send an email
14:03:33 <banix> hi
14:03:41 <apuimedo> banix: :-)
14:03:44 <apuimedo> nice to see you
14:04:10 <banix> :)
14:04:16 <apuimedo> so, do we hold it now, or we hold it later in #openstack-kuryr?
14:04:44 <irenab> I cannot do it later
14:05:05 <irenab> but you can do it without me
14:05:17 <apuimedo> let's do it now then
14:05:28 <apuimedo> #topic repository split
14:05:56 <apuimedo> #info kuryr libnetwork and kubernetes integrations have been split to kuryr-libnetwork and kuryr-kubernetes
14:06:17 <apuimedo> The first patches have landed to both of them to put the skeleton in place
14:06:49 <banix> apuimedo: great. links?
14:06:52 <apuimedo> sure
14:07:14 <apuimedo> #link https://review.openstack.org/#/c/317988/
14:07:18 <irenab> apuimedo: any common repo for shared code?
14:07:18 <apuimedo> https://review.openstack.org/#/c/317984/
14:07:21 <apuimedo> #link https://review.openstack.org/#/c/317984/
14:07:42 <banix> @irenab yes good question
14:07:55 <apuimedo> #info the common code (like binding) will remain in the `kury` repository
14:08:23 <irenab> apuimedo: maybe need to update the devs documentation as well
14:08:34 <apuimedo> I'm thinking of making kuryr-libnetwork and kuryr-kubernetes use the python setuptools namespace feature
14:08:39 <apuimedo> #link http://pythonhosted.org/setuptools/setuptools.html#namespace-packages
14:09:28 <apuimedo> #info using the namespace-packages could use kuryr.libnetwork and kuryr.cni, etc
14:09:42 <apuimedo> irenab: yes, we need to update a whole bunch of stuff
14:09:58 <apuimedo> #action move libnetwork specific patches to kuryr-libnetwork
14:09:59 <irenab> apuimedo: do you trace this work somehow at launchpad?
14:10:18 <apuimedo> irenab: I don't. I'm not sure how to. A blueprint?
14:10:40 <irenab> I think its the best way to have all related links at one place
14:10:51 <apuimedo> I'd like to push the commits from the beginning of time as if they were new commits from the same authors
14:12:00 <irenab> I think it will just requre change in the commit message for still unmerged patches
14:12:27 <apuimedo> let's hope it is as easy as possible
14:12:59 <banix> the lbaas people should know what to do as they went through similar process
14:13:21 <apuimedo> banix: anybody in particular we can ask?
14:13:25 <banix> dougwig: I believe would be a good [erspn to ask question from
14:13:36 <apuimedo> thanks dougwig
14:14:11 <irenab> or anyone who did neutron vendor split stuff
14:14:20 <apuimedo> good
14:14:22 <apuimedo> I'll check
14:15:07 <apuimedo> #action apuimedo to check how to push the relevant subsets of the kuryr code that belong to kuryr-libnetwork
14:15:37 <apuimedo> #topic open discussion
14:15:49 <apuimedo> Yes, that's right, I don't have anything more for today
14:15:59 <apuimedo> banix: irenab: any other topic?
14:16:05 <irenab> I wanted to suggest have some sort of the meeting format with usual sections, i.e bugs, rfes
14:16:07 <apuimedo> or discussion
14:16:22 <apuimedo> irenab: that's a good proposal
14:16:45 <irenab> I do not spend enough time at bugs review, so maybe peopel can link the bigs/patches so we can take a look
14:16:50 <apuimedo> #action irenab to update https://wiki.openstack.org/wiki/Meetings/Kuryr with standard sessions
14:16:55 <apuimedo> *seccions
14:17:11 <irenab> you will get it right eventually
14:17:14 <irenab> :-)
14:17:14 <banix> i would like to add a script to start kuryr with uwsgi; is there a easy way to pass options (say the config fuie name)? i will look into it myself but in case it is easy to do
14:17:16 <apuimedo> g*df*ck*ng d*ammit
14:17:21 <apuimedo> sections!!!
14:17:46 <apuimedo> banix: you mean like I do in the container via command line?
14:17:52 <banix> yeah
14:18:07 <banix> but i dont see  how the config file name is passed
14:18:07 <apuimedo> well, yeah, you can pass a config file
14:18:15 <apuimedo> let me see if I find it
14:18:20 <apuimedo> I have it somewhere
14:18:21 <banix> i see you creating the config file
14:18:50 <irenab> banix: apuimedo I am not following your discussion, will appreciate a pointer
14:18:53 <apuimedo> banix: --ini
14:18:57 <apuimedo> and you pass an ini file
14:19:12 <apuimedo> irenab: start-kuryr is only for development mode
14:19:15 <banix> ok will look into it
14:19:35 <apuimedo> it is only for flask's development server and is not multithreaded/multi-cored
14:19:45 <apuimedo> so in the container I made I put uwsgi in front of it
14:19:49 <banix> @irenab like to start kuryrs in a multi-threaded way
14:19:56 <apuimedo> but passing things via command line
14:20:04 <irenab> banix: good idea
14:20:10 <apuimedo> banix wants to generalize it into a production start script
14:20:19 <irenab> this is great
14:20:36 <apuimedo> ;-)
14:20:48 <irenab> banix: planning some operational guide as follow up?
14:20:58 * apuimedo is lazy and wanted to leave that as a practice exercise for packagers :P
14:21:01 <banix> irenab: of course :)
14:21:35 <banix> another issue worth mentioning is perhaps supporting router extension
14:21:41 <apuimedo> #action banix to make an INI file using uwsgi start script
14:21:49 <apuimedo> right, right
14:21:53 <apuimedo> banix: how is that going?
14:21:59 <banix> neutronclient supports tags only for networks
14:22:05 <irenab> I wanted to discuss a bit on labels/options for the docker to push into kuryr
14:22:14 <apuimedo> any chance we can get it for routers?
14:22:22 <apuimedo> (and load balancers)
14:22:23 <irenab> banix: I saw this too, but I think we should extend it
14:22:29 <banix> so to do this correctly it’s best to use tags for routers
14:22:44 <banix> so yes we need to extend neutronclient for this
14:22:52 <irenab> we better add them for ports, routers and load balancer pools
14:23:14 <apuimedo> banix: neutronclient or also DB?
14:23:16 <irenab> I think some small change is required in neutron server too
14:23:51 <banix> hmmm my understanding was only neutron client part is missing but i may be wrong
14:24:03 <irenab> banix: do you hafve any link on what you plan for router extension?
14:24:28 <banix> irenab: no
14:24:45 <irenab> https://github.com/openstack/neutron/blob/master/neutron/services/tag/tag_plugin.py#L34
14:24:47 <banix> there is a rfe bug
14:24:56 <irenab> I think supported resources should be listed here
14:25:42 <banix> so it is more invloved thatn changing neutronclient
14:26:12 <irenab> I am not sure why its limited for networks
14:27:03 <apuimedo> irenab: do you have time to check this?
14:27:07 <banix> let me reachout to the author of that patch
14:27:19 <banix> or irenab can do this
14:27:20 <apuimedo> oh, you volunteer banix ?
14:27:46 <apuimedo> #action banix and irenab to check what's missing for having tags for routers, ports, etc
14:27:49 <banix> sure i can at least figure out what is needed
14:28:29 <irenab> banix: let me know if you need any help here
14:28:43 <banix> @irenab sure. thanks.
14:29:10 <apuimedo> anything else?
14:29:16 <irenab> not from me
14:29:35 <banix> im good
14:30:29 <apuimedo> very well!!!
14:30:37 <apuimedo> thank you both for joining!
14:30:47 <apuimedo> next week in the alternate time!
14:30:49 <apuimedo> #endmeeting