08:00:54 #startmeeting storlets 08:00:55 Meeting started Tue Oct 18 08:00:54 2016 UTC and is due to finish in 60 minutes. The chair is eranrom. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:56 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:58 The meeting name has been set to 'storlets' 08:02:20 hi 08:02:25 hello 08:02:31 Hi 08:02:51 Lets start :-) 08:02:57 #topic Newton branch 08:03:47 I have posted a small patch. Once reviewed, I can cut the branch. 08:04:00 https://review.openstack.org/#/c/385866/ 08:04:39 eranrom: thank you for working about that 08:05:07 sure, anything else on the release3 topic? 08:05:18 eranrom: Can I ask one question about the patch? 08:05:26 takashi: please do. 08:05:56 eranrom: As far as I understand about the patch, you first put a pin about dependency to newton in master blanch 08:06:13 and after cutting of Newton branch, you will revert it on master, right? 08:06:25 right. Hope this makes sense. 08:07:15 I think there are another option to cut of Newton blanch first, and push a patch to put a pin to that stable branch 08:08:04 takashi: does it mean that patch includes the tag? 08:08:19 kota_: Thanks I was just about to ask that :-) 08:08:42 takashi: usually, we are doing the release via land first at the master and make a tag for the commit and push it 08:09:03 (the method is available in the incuvation like swift3) 08:09:29 kota_: ok 08:10:14 let me take 5 minutes to move to my desk. 08:10:20 please continue w/o me 08:10:39 my little concern is that, if we cut newton release by current way, we will merge the pinning dependency and reverting it in master, right? 08:10:40 takashi: kota_: Summarising: We land the patch, tag, create a branch. update master with a new patch to revert dependencies 08:11:00 takashi: right 08:11:48 I just wanted to know if there are any way without merging that non-fastforward (pinning and reverting) change to master, but it seems to be required 08:11:58 based on that explanation 08:13:25 takashi: Well, there might be a better way, only I am not aware of it. 08:13:52 perhaps we can ask the swift community next week. 08:14:05 anyway, we don't have so long time. maybe we can discuss the way for that with tc members, for the next release 08:14:25 Currently I do not have so big objection. will put +2 on the patch soon 08:14:31 takashi: sure. Thanks! 08:14:55 Do we want 2 reviewers for this one? 08:15:18 eranrom: Can you have a look, kota_? 08:15:26 eranrom: maybe that is better 08:15:40 takashi: sure! 08:15:46 next topic? 08:15:49 back 08:15:55 kota_: some background for you. We discussed to have Newton release before Barcelona summit. 08:16:10 takashi: sounds great 08:16:31 does it needs a volunteer to do something? 08:16:45 kota_: to review the patch I guess :-) 08:17:01 which one or two or ??? 08:17:14 lets start with https://review.openstack.org/#/c/385866/ 08:17:33 k, that one. 08:17:41 kota_: Thanks! 08:17:41 kota_: that is the patch for tagging, which adds pin about dependency 08:18:20 eranrom: all from my side about release. I'm ok to move to the next 08:18:23 or if takashi could review it, it's ok with single +2 because it looks just small changes 08:18:40 kota_: ok 08:18:57 ok thanks so moving to the next subject. 08:19:00 tbh, Swift also wants to cut a release in this or the next week in the barcelona because of closing critical bug. 08:19:14 kota_: which you fixed :-) 08:19:15 so i may not have enough time to take a look that, sorry. 08:19:38 ok. will put +2+A later, with some comments based on this irc meeting result 08:20:00 takashi: ok, note that I am putting Swift 2.9.0 as the pinned dep. 08:21:01 Should we update this (on the branch) once Swift has the new release next week? 08:21:05 eranrom: ok. I found we need to consider to install keystone via git, and upgrade ubuntu version in the next release... but they should be addressed to Ocata cycle 08:21:18 takashi: Agree! 08:22:09 eranrom: If that new release is coming as bug fix, we can move the pin 08:22:14 new release of swift 08:22:22 takashi: alright. Thanks 08:22:29 So moving on (take 2 :-)) 08:22:43 #topic Design Summit 08:23:11 I am working on a presentation for the spark part, and thought I would also prepare some slides on the deep dive. 08:23:27 Wanted to ask you what should I cover, or if there are subjects you would like to cover. 08:24:53 this is in the context of the FB and working session 08:26:26 eranrom: Honestly speaking, I didn't think more that just checking etherpad topics, 08:26:47 eranrom: but if we can prepare some, it sounds good, especially for new people 08:27:19 takashi: Fair enough. I was thinking about our initial discussions where we thought os also doing some storlets deep dive in the context of the design session. 08:27:52 don't worry about it. I will send you the presentation for a review 08:28:03 s/os/to 08:28:39 I am even not sure how much time we will have for it. 08:28:45 eranrom: thanks. 08:29:32 allright. This is all I had planned for today. 08:30:49 Any other topics? 08:31:39 not so big updates. I'm still debugging the error in packaging work. I'd like to fix the problem before summit, but currently need to find the time for that... 08:32:14 that's all from my side today. 08:32:31 k, as calling a few minutes before, I've been tighten up to Swift upstream work so no updates in recent. 08:32:37 takashi: sure. Also here is a long holidays period so I do not have much time to do any progress other then getting ready for the summit :-) 08:32:53 kota_: sure. 08:33:07 eranrom, kota_: looking forward to seeing you at Barcelona! 08:33:23 all: enjoy and safe trip! 08:33:23 takashi: kota_: Same here!!! 08:33:42 Thanks! see you in Barcelina 08:33:52 Barcelona :-) 08:34:22 :-) 08:34:35 see you! 08:34:52 #endmeeting