03:01:30 #startmeeting Kuryr 03:01:31 Meeting started Tue Mar 8 03:01:30 2016 UTC and is due to finish in 60 minutes. The chair is tfukushima. Information about MeetBot at http://wiki.debian.org/MeetBot. 03:01:32 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 03:01:34 The meeting name has been set to 'kuryr' 03:02:08 Who's up for Kuryr IRC meeting today? 03:02:16 morning&evening, everyone~ 03:02:22 hi tfukushima 03:02:22 o/ 03:02:24 evening 03:02:31 o/ 03:03:02 #info baohua, banix, fawadkhaliq and tfukushima are present 03:03:36 #link Today's agenda https://wiki.openstack.org/wiki/Meetings/Kuryr#Meeting_March_8.2C_2016 03:04:01 Ok, let's get started. 03:04:29 #topic Kubernetes Integration 03:04:49 #link Spec proposal by irenab https://review.openstack.org/#/c/281132/ 03:06:07 #action Everyone reviews irenab's spec proposal 03:06:34 tfukushima: thanks, will do. I did a quick review early on, Will do again on the latest patch 03:06:53 +1, will do it 03:07:18 Yeah, it seems to be updated recently and it'd be again, I guess. 03:07:31 sure will do too 03:08:30 It has the descriptions about the API watcher and the CNI driver. 03:08:50 tfukushima: taku i hear you have a prototupe working 03:09:02 is it along the lines being described in the spec? 03:09:33 I think I have to write the devref rather than the higher level spec. 03:10:16 I'm playing with the apiserver of K8s. 03:10:46 cool 03:11:27 The API allows you to get a line of JSON data when you call GET against the certain endpoint with the query string, i.e., /api/v1/pods?watch=true 03:12:02 You can see what's happening with curl. 03:12:16 tfukushima is your prototype a multi-node env? 03:12:44 At this point one master and two worker nodes. Small cluster. 03:13:04 sounds multi-node to me :) 03:13:04 thanks 03:13:31 And I'm doing the api watcher-ish stuff, so only the master is my concern so far. 03:14:08 I'll push back to Kuryr updatream when it gets some shape. 03:14:40 Oh, I have a question about that. 03:14:51 great thanks. Mike Spreitzer who dont seem to be around now is also working on a prototype 03:15:45 Nice. We might need to coordinate our tasks not to be conflicted. 03:16:26 i think he is doing the OTHER approach discussed for a quick short term solution but should leave it to him to describe what he has 03:16:41 any of you going to KubeCon? 03:16:45 in Europe? 03:16:51 London I believe 03:17:47 banix possible not for me, will u go? 03:17:53 I hope I could. We'd love to see that proposal but yes, it's up to him. 03:18:45 I am not going. Mike is going. Should let us know how things are in our next meeting hopefully 03:19:24 yes, that will be a nice sharing 03:20:02 Anyways, here's my question: To get a line of JSON data, I'd like to use asyncio, the async I/O library introduced in Python 3.4 not to be blocked for the next event propagation. Does it make sense to drop Python 2.6 support for that? 03:21:16 2.7 you mean? 03:21:28 to support curl-based api querying? 03:21:30 Yes. Python 2.x. 03:22:09 To support better async I/O mechanisms and more features introduced only in Python 3.x. 03:22:30 curl is blocking actually, I believe. 03:23:29 i understand what you are saying. is the rest of kuryr ok with 3.4? 03:23:54 There's Trollius for the equivalent but it's saying it's deprecated and recommending to move Python 3.x. 03:24:00 http://trollius.readthedocs.org/deprecated.html 03:24:02 i know we test at gate but beyond that 03:24:45 a little worried not full tested yet. 03:25:25 Maybe we can separate the API watcher from the rest but it'd be a bit bothering. 03:26:45 Anyways, I'll submit the patch or something and propose this in another way as well but I wanted to know how you would feel about that. 03:27:29 #link Python3 support in OpenStack https://wiki.openstack.org/wiki/Python3 03:28:15 Sorry, I took time. Let's move on to the next topic. 03:28:31 #topic Nested Containers and Magnum Integration 03:28:52 fawadkhaliq: Any update? 03:29:44 tfukushima: yes, the spec is in good shape 03:29:52 have several +1s and a +2 03:30:01 I am hoping we merge it soon 03:30:23 And in parallel, we are planning to kick off the discussion on Kuryr Agent 03:30:28 there is a separate spec for that 03:30:38 that's the current update and plan moving forward. 03:30:45 Nice. I seriously should look at the spec! It's my shame. 03:31:05 tfukushima: thanks 03:31:48 fawadkhaliq: BTW, have you tried Magnum? 03:32:09 tfukushima: yes, I have in general usage sense 03:32:20 are you referring to some specific? 03:32:28 s/some/something/ 03:32:50 fawadkhaliq: My friend tried it but he told me he got stuck in the middle of creating a bay. 03:33:18 tfukushima: okay, maybe he can drop an email 03:33:54 Yeah, he'd but I was just wondering how stable Magnum is now. 03:34:29 tfukushima: its reasonable, the base infra has to be perfect to make it work 03:34:55 tfukushima: sine Heat is invovled and sometimes Heat stacks are just stuck forever 03:35:12 and thats normally tied to the base infra 03:35:46 fawadkhaliq: I see. That makes sense. Thanks. 03:35:55 tfukushima: npp 03:36:05 so thats all on the nested container topic for today 03:36:14 #action Everyone review fawadkhaliq's spec again. 03:36:28 Good. 03:36:30 thanks, hoping to get it merged soon. 03:37:09 #topic Existing Networks 03:37:36 banix: You might want to share something about that. 03:37:46 yes sure 03:37:59 so the Neutron tags got merged for neutron networks 03:38:24 Yay! 03:38:30 in that light, we can get rid of the use of neutron network names 03:38:30 Finally. 03:38:34 yes 03:38:52 so i have a patchset to do that. Will update it based on the comments 03:38:58 I heard you tried it and it worked? 03:39:08 this will just change the kuryr to use tags 03:39:19 yes it works 03:39:39 Then I am going to update your existing network spec Taku 03:39:54 I had made changes based on our stop-gap planning 03:40:01 banix: Yes, please. I left it forever. :-( 03:40:07 but now, I can uodate it to use tags 03:40:24 That's sweet. 03:40:34 tfukushima: no worries. Gal and Toni mentioned you are busy 03:41:06 So that will get rid of the using name ugliness and add the support for existing networks in a clean way 03:41:41 That’s all for me unless there are questions 03:42:19 Cool. 03:43:01 Ok, we shall go to the next topic. 03:43:14 #topic Packaging 03:43:50 Actually I have no idea about the situation of the packaging. 03:44:24 We shall leave this for next week then :) We need Toni to get the status 03:44:57 Yeah, he should know better and I saw hi submitted a few patches. 03:45:16 #topic Fullstack and Rally integration 03:45:48 baohua: Would you like to share something? 03:45:53 yes 03:46:01 two patches under review, welcome anyone's comments, thanks! 03:46:03 https://review.openstack.org/#/c/265105/ 03:46:08 https://review.openstack.org/#/c/286531/ 03:46:17 that's it :) 03:47:13 tfukushima, pls go ahead :) 03:47:23 baohua: Thanks. I have to review them. 03:47:30 #action Everyone reviews haohua's Rally tests. 03:48:16 baohua: The patch looks well documented and I like it. 03:48:25 thanks :) 03:49:02 Ok, let's wrap up the meeting. 03:49:09 #topic Open Discussion 03:49:29 Does anyone have anything else to discuss? 03:50:04 banix; Oh, I submitted a patch. https://review.openstack.org/#/c/289147/ 03:50:32 I'm sadly a OSX user and I wanted to run unit tests. :-p 03:50:44 cool 03:51:20 will have a look 03:51:53 Good. I think we can finish today's meeting. 03:51:58 nothing else from my side 03:52:07 yay! we save 9 min :-) 03:52:09 :P 03:52:14 thanks taku 03:52:18 great! thanks everyone~ 03:52:21 and everybody :) 03:52:37 Thanks for attending, guys. 03:52:42 :) 03:52:44 thankjs 03:52:46 bye 03:52:50 bye 03:52:56 #endmeeting