14:17:08 <ivc_> #startmeeting kuryr
14:17:09 <openstack> Meeting started Mon Feb 20 14:17:08 2017 UTC and is due to finish in 60 minutes.  The chair is ivc_. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:17:10 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:17:12 <openstack> The meeting name has been set to 'kuryr'
14:17:20 <ivc_> hi everyone
14:18:42 <ivc_> #topic kuryr-libnetwork
14:20:05 <ivc_> #chair apuimedo
14:20:06 <openstack> Warning: Nick not in channel: apuimedo
14:20:07 <openstack> Current chairs: apuimedo ivc_
14:21:30 <apuimedo> ivc_: ping
14:21:51 <ivc_> #chair apuimedo
14:21:52 <openstack> Current chairs: apuimedo ivc_
14:21:57 <ivc_> fixed :)
14:22:04 <apuimedo> sorry for the delay. I couldn't find a room in the PTG
14:22:05 <apuimedo> :P
14:22:17 <apuimedo> did we already go over kuryr-kubernetes?
14:22:47 <mchiappero> no
14:22:50 <ivc_> nop. i've changed topic to kuryr-libnetwork and was checking the patches that might need discussion :)
14:23:05 <apuimedo> ah, very well
14:23:32 <apuimedo> well. For kuryr-libnetwork I was expecting people to bother cores last week as the freeze was last wednesday
14:23:41 <apuimedo> since that didn't happen...
14:24:05 <apuimedo> #action apuimedo to go over the outstanding patches and send an email to the mailing list about which to get to the release
14:24:21 <alraddarla> apuimedo: i beg to differ. I believe I bothered you a few times :)
14:24:56 <apuimedo> alraddarla: You are the only one. And I have bad conscience of not having had the time to go over it
14:25:01 <apuimedo> I'll do it after this meeting
14:25:08 <alraddarla> I've heard that before
14:25:11 <apuimedo> now that I'm in Atlanta I have all the day in front of myself
14:25:13 <alraddarla> :P Just kidding
14:25:19 <apuimedo> guilty as charged
14:25:46 <apuimedo> alraddarla: did you get a chance to look at the floating ip apis for kuryr-k8s?
14:26:01 <alraddarla> yes i looked through the docs and some of the patch sets you mentioned
14:26:04 <apuimedo> if anybody has more stuff on kuryr-libnetwork, speak now or forever hold your peace
14:26:08 <apuimedo> or until next week
14:26:21 <apuimedo> alraddarla: cool
14:26:45 <apuimedo> if you have questions on the kuryr-k8s patches ivc_ and I will try to help with that
14:26:53 <apuimedo> #topic fuxi
14:27:02 <apuimedo> hongbin sent me his updates
14:27:55 * apuimedo finding the email
14:28:31 <apuimedo> #info Fuxi is preparing the first release. hongbin was trying to setup the release jobs and release notes for that
14:28:48 <apuimedo> #info The patches to be be taken for the release:
14:28:54 <apuimedo> #link https://review.openstack.org/#/c/435737/
14:29:00 <apuimedo> #link https://review.openstack.org/#/c/435626/
14:29:06 <apuimedo> #link https://review.openstack.org/#/c/435741/
14:29:15 <apuimedo> #link https://review.openstack.org/#/c/435746/
14:29:29 <apuimedo> #link https://review.openstack.org/#/c/399296/
14:29:55 <apuimedo> #action apuimedo: limao: irenab: to get the above merged
14:30:18 <apuimedo> #topic kuryr-kubernetes
14:30:46 <apuimedo> ivc_: or did we cover kuryr-kubernetes already?
14:30:52 <ivc_> no
14:30:57 <alraddarla> https://review.openstack.org/#/c/433250/   Just needs workflow
14:31:17 <ivc_> and i'm waiting for reply on k8s lbaas service patch :)
14:31:20 <ivc_> #link https://review.openstack.org/#/c/433359/
14:31:39 <apuimedo> alraddarla: merged
14:31:40 <apuimedo> :-)
14:32:16 <apuimedo> ivc_: you mean on the discussion with ltomasbo?
14:32:46 <ivc_> apuimedo yes, and your comments too
14:33:10 <apuimedo> ivc_: very well. I'll get to that then after the meeting
14:33:25 <apuimedo> ivc_: I want to make the endpoint code configurable
14:33:39 <ivc_> apuimedo what do you mean?
14:33:57 <apuimedo> whether it should make members for endpoints not in the pods subnet
14:34:27 <ivc_> oh that, i knew it was coming when you tried openshift router :)
14:34:28 <apuimedo> Considering that it may be necessary for "infra" pods like dns
14:34:33 <apuimedo> as well
14:34:44 <apuimedo> the thing is, since we do not run kube-proxy
14:34:51 <ivc_> lets do it in another patch maybe?
14:34:52 <apuimedo> the cluster IPs that we do not define
14:34:56 <apuimedo> as LBs
14:35:00 <apuimedo> are not reachable at all
14:35:26 <apuimedo> I think we should do this (maybe even as deafult) so we can support kuryr pods accessing hostnetwork pods
14:36:03 <ivc_> yes, there's 1 TODO/REVISIT note that has to be addressed before we can use non-ClusterIP (i.e. non-Pod) endpoints
14:36:17 <apuimedo> very well
14:36:46 <apuimedo> ivc_: I suppose work on the third services patch is waiting for closure on the current patch, right?
14:38:12 <ivc_> apuimedo not rly, i've started working on it
14:38:44 * ivc_ does not expect many (if any) changes in driver patch
14:39:10 <apuimedo> ivc_: very well
14:39:27 <apuimedo> ivc_: easy review https://review.openstack.org/#/c/399296/
14:40:08 <ivc_> apuimedo isn't that fuxi?
14:40:25 <apuimedo> ivc_: wrong paste https://review.openstack.org/#/c/435205/
14:40:36 <apuimedo> ivc_: also https://review.openstack.org/#/c/435903/1
14:41:00 <apuimedo> I deleted firefox for some breakage and I'm finding it hard to get used not to have my vimperator shortcute
14:41:03 <apuimedo> *shortcuts
14:41:10 <ivc_> apuimedo last i checked there was -1 from tests.
14:41:31 <ivc_> but its green now. i'll check
14:41:35 <apuimedo> good
14:42:19 <ivc_> i think those logging imports were leftovers from debugging
14:42:58 <apuimedo> #info vikasc ltomasbo and apuimedo worked on a demo of OpenShift with Kuryr https://www.youtube.com/watch?v=UKZryuTH4B0 which is what the earlier discussion about 'infra' pods was about
14:43:06 <apuimedo> ivc_: :-)
14:43:10 <ivc_> apuimedo isn't https://review.openstack.org/#/c/435903/1 conflicting with openstack proposal bot?
14:44:10 <apuimedo> ivc_: that's what I'd suppose. Since you usually can't merge them. But I wonder if they made an exception
14:44:25 <apuimedo> so my position is: Try to merge, if it fails, contact infra
14:44:36 <ivc_> i just merged one earlier today https://review.openstack.org/#/c/433250/
14:44:46 <ivc_> wrong link
14:44:59 <ivc_> https://review.openstack.org/#/c/431967/
14:45:04 <ivc_> #link https://review.openstack.org/#/c/431967/
14:45:51 <ivc_> apuimedo i mean we dont need to manually create patches for things that are managed by openstack proposal bot
14:46:18 <apuimedo> #info slides to the demo before. If anybody wants the diagrams for trunk port or anything else, let me know. I have the svgs http://www.slideshare.net/celebdor/openshift-on-openstack-with-kuryr
14:46:23 <apuimedo> ivc_: I know
14:47:06 <apuimedo> ivc_: I'll check if it is really an exception or we can expect the bot to post this
14:48:34 <ivc_> apuimedo i've rebased that patch and now its just empty :) so i think it should be abandoned
14:50:01 <apuimedo> great
14:50:06 <apuimedo> ivc_: feel free to do so
14:50:09 <apuimedo> you have the power!
14:51:22 * ivc_ feels the powah!
14:51:26 <apuimedo> :D
14:51:31 <apuimedo> #topic general
14:51:53 <apuimedo> #info apuimedo is at the PTG and we'll discuss on wednesday about tripleo kolla helm integration
14:52:09 <apuimedo> for both deployment and also for having kuryr-kubernetes be deployed by those tood
14:52:12 <apuimedo> *tools
14:52:43 <apuimedo> #info the VTG schedule is final and there is people to lead the sessions
14:52:59 <alraddarla> do you have the link for that?
14:53:00 <apuimedo> I'll send the invite to the mailing list with the bluejeans link
14:53:08 <apuimedo> I have to create a meeting
14:53:35 <apuimedo> in bluejeans to get a new url
14:53:42 <apuimedo> I'll post it on the mailing list later
14:53:49 <apuimedo> anything else?
14:56:27 <apuimedo> very well
14:56:32 <apuimedo> Thank you all for joining
14:56:35 <apuimedo> #endmeeting