21:00:07 #startmeeting swift 21:00:08 Meeting started Wed Jan 4 21:00:07 2017 UTC and is due to finish in 60 minutes. The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:11 The meeting name has been set to 'swift' 21:00:12 who's here for the swift team meeting? 21:00:19 hi 21:00:24 hi 21:00:25 o/ 21:00:25 hi 21:00:26 hello 21:00:28 Hi 21:01:15 hmm... kinda light today :-) 21:01:31 but to the faithful, welcome ;-) 21:01:36 o/ 21:02:17 this week I was hoping to catch up on what's going on, now that we're all back from holidays 21:02:39 hi, sorry for being late 21:03:11 but first, I wanted to call out donagh in the meeting and thank him for working on swift. he's moving on to other projects at HPE and will no longer be working on swift https://review.openstack.org/#/c/416577/ 21:03:36 so if/when you see him around, tell him thanks and wish him well :-) 21:04:22 ok, so let's talk about what's going on 21:04:56 I'll admit I haven't completely caught up on patches since being off, so if I'm missing something that comes up, please remind me :-) 21:04:57 o/ 21:05:01 hi 21:06:02 in our last meeting, I put forth a list of stuff that's being worked on that are big (either in impact or in effort) 21:06:26 golang object server, global ec, composite rings, policy migration, policy auto tiering, sync to elasticsearch, container sharding, symlinks, increase part power, container sharding 21:06:44 and I know there are other things going on too 21:08:15 here's what I'm working on personally, related to upstream work. I'm getting ready for a conference in two weeks (talk prep) and I'm working on an improved all-in-one environment that shoudl be really easy to consume 21:08:36 i hope to be done with that relatively soon, and it will be a public tool 21:08:56 so what are you working on? who's first? 21:09:05 ...or second, rather 21:09:45 kota_: what's going on with you and in the NTT world? 21:10:07 notmyname: ok, so you know, global ec is my first priority 21:10:17 cool. I'm excited about that :-) 21:10:19 notmyname: and still waiting reviews 21:10:23 how's progress? 21:10:28 ok, blocked by reviews 21:10:32 not so much recently 21:10:35 yes 21:10:45 ok 21:10:46 and the good news in the end of the last year 21:10:48 is 21:11:02 storlets has been openstack official 21:11:11 related project to swift 21:11:17 nice 21:11:23 and i has been working on some stuff on that 21:11:30 cool 21:11:33 congrats to storlets team 21:11:42 the most impressive work has been writing jupyter/ipython extension 21:11:56 https://review.openstack.org/#/c/414883/ 21:12:02 thanks all 21:12:29 now i'm thinking of sort of that could be used for swift too. 21:12:45 fun 21:13:16 pdardeau: you're next. what's up? 21:13:17 e.g. %%swift-upload container object -> upload ipython cell to swift 21:13:36 mmotiani1: and i are working on swift benchmarking 21:13:55 ramping up to 20 storage nodes with 8 HDD each 21:14:19 +1 21:14:27 nice 21:14:36 anything upstream you're needing for that? 21:14:46 not at the moment 21:14:51 ok 21:15:04 bkeller`: what's up with you? frozen in chicago? 21:15:10 pdardeau: did you ever meet Mark Seger (in Bristol maybe?) - he has some nice tools for benchmarking/analysis 21:15:15 * notmyname always imagines chicago as very very cold 21:15:19 it's 10F here today 21:15:42 nothing new for notifications yet though 21:15:45 acoles: yes, i did! thanks for reminding me. i'll look around to see what he has 21:16:08 pdardeau: email me if you want to connect with him, he doesn't hang out in irc 21:16:23 acoles: thx 21:16:38 bkeller`: ok. what do you need from upstream? 21:17:33 nothing yet that i know of 21:17:36 ok 21:17:40 jrichli: you're next 21:17:45 tdasilva, timburke, and I have done some work on symlinks recently 21:17:51 still more to do for sure 21:18:07 timburke left a lot of good feedback 21:18:13 cool 21:18:27 i uploaded a patch for api-ref docs - could use some feedback there 21:18:35 ok. link? 21:18:55 https://review.openstack.org/#/c/415943 21:19:17 clayg had mentioned it would be good for us to focus on hammering the api out before we go through perfecting the impl 21:19:45 yeah, I can see wisdom in that 21:20:00 and you all have prob seen in channel we are planning to have a conference call about keymaster v2 soon 21:20:14 jrichli: do we have a time yet? 21:20:16 great 21:20:36 i guess tomorrow at 14:00 UTC - although, i still have a lot to go over for myself. but i dont want to hold it up. 21:21:59 I'll look forward to hearing what you talk about 21:21:59 i haven't created an invite yet. will today. let me know if you are interested - i already know about tdasilva, mahatic, acoles 21:22:35 well, i call it that, but its about mathiasb current patch - oh, and he will be on the list of course :-) 21:22:39 #info review https://review.openstack.org/#/c/415943 for symlink API 21:22:48 specifically I want to suggest that future keymasters *only* keep config in a separate file (not in proxy-server.conf), and have others tell me I am wrong 21:23:00 https://review.openstack.org/364878/ 21:23:08 #info if interested, talk to jrichli about an invite to the conference call about keymaster v2 happening this week 21:24:12 jrichli: anything else? 21:24:27 that's all i have been up to lately 21:24:57 sgundur_: you're up. what are you working on this week? 21:25:54 notmyname : Happy new year 21:26:04 was on vacation , got back this week 21:26:24 been learning about EC from Nadeem 21:26:25 hint: "mark all as read" is a *great* way to deal with email ;-) 21:26:36 lol 21:26:54 cool on the EC learning 21:27:07 I am inclined to do some meaningful reviews on EC and hopefully more in furture in EC work 21:27:38 sgundur_: great. it would be helpful for you to look at kota_'s global EC patches. both to learn and for getting that landed 21:28:02 sgundur_: nadeem: anything else you need from the rest of the community? 21:28:05 yes, that's what I was thinking looking at Kota's update earlier 21:28:20 wonderful. thanks 21:28:27 sgundur_: thanks ;-) 21:28:39 Sorry I'm late! :S 21:29:06 joeljwright: no worries. welcome 21:29:38 acoles: your turn. what's going on? 21:30:17 notmyname: before the break I was working with Pavel on this patch https://review.openstack.org/402043 which needs to land 21:30:32 fixes regression in replication suffix hashing 21:31:04 ah, yes. thanks for the reminder. that's a big deal 21:31:15 yes. 21:31:33 #info please review https://review.openstack.org/#/c/402043/ to close a high priority bug 21:32:07 ^^ please go to a quiet place and think hard about whether we now have it right 21:32:18 notmyname: now getting up to speed on the keymaster/barbican patch again. 21:32:23 cool 21:32:31 acoles: anything else you need from upstream? 21:32:46 and found an ssync bug in the process :/ which I'll probably try to fix 21:32:54 yay 21:33:10 (sarcastically for the bug. seriously for the fix) 21:33:21 notmyname: not feeling any need at the moment 21:33:31 ok 21:33:40 * acoles is grieving for donagh 21:33:44 +1 21:33:54 +1 21:33:59 :( 21:34:13 :( 21:34:40 cutforth: anything from you? are you working on anything related to upstream swift this week? 21:34:43 I will still pester him! 21:35:37 tdasilva: your turn. what's new with you in the new year? 21:36:12 hello! just before the break i was working on the libec/pyeclib merger 21:36:19 oh right! 21:36:45 I thought of two options, one was to copy files from pyeclib into libec repo and send gerrit patch 21:37:00 the other was to work with infra to merge the repos, so that way we could keep history of changes 21:37:14 which way are you leaning so far? 21:37:30 I took a stab at creating a throw away repo but still need to get feedback from infra team 21:37:52 ok. I'd prefer to keep the history, if possible. thanks for working on that 21:38:15 yeah, i'd like that too, will continue trying to work with the infra team, let's see... 21:38:21 cool 21:38:31 anything you need from the rest of the community yet? 21:38:40 over the break timburke left comments on symlink patch, so i started going through those 21:38:47 ok 21:38:51 and jrichli send the api-ref patch which I still need to look over 21:39:15 hoping to send an update to symlink patch soon 21:39:46 thanks 21:39:54 nothing from me, thank you for asking 21:40:07 i think that's it. jrichli if you need video conf. call for tomorrow's meeting i can help 21:40:25 tdasilva: ok, cool. thx 21:40:39 timburke: your turn. what's up? 21:40:52 mostly looking at swift3 stuff 21:41:07 ok. anything blocking that you need help with? 21:41:35 can we clone kota_? 21:41:42 :P 21:41:45 heh 21:42:01 so my slow review blocks them, i know :/ 21:42:26 well, i *could* just merge them, but then i'd feel dirty 21:43:35 joeljwright: I think you're the last nick I saw come in. your turn. what's going on with you, related to swift team work? 21:43:55 I got some good feedback on the SLO preamble/postamble stuff 21:44:04 need to talk to timburke about his comments 21:44:05 great 21:44:30 also, the removing slo segments patch for the client 21:44:36 ah, nice 21:44:53 is that up yet and I'm forgetting about it, or is it goign to be proposed? 21:45:10 which one? 21:45:16 removing slo segments 21:45:21 the SLO segment removal patch had issues 21:45:31 ugh, that reminds me that i need to think more about https://review.openstack.org/#/c/310075/ ... 21:45:40 I'd like it fixed too, so that will be a chat with timburke 21:45:50 ok 21:45:52 oh! "removal" -> "expiration" 21:46:15 anything else from anyone? did I skip anyone or did anyone remember something else? anything else to bring up? 21:46:16 sorry - it's been a fun christmas 21:46:31 I also have a machine set up to test container sharding, but no progress yet 21:46:57 joeljwright: nice 21:46:57 will probably bug mattoliverau as soon as I have something 21:46:58 Was on vacation for last few weeks. I will working on trimming feature/hummingbird branch to isolate golang replicator 21:47:02 any updates on anything golang related? 21:47:08 nice! i've been wanting to look at that but haven't gotten around to it 21:47:39 nadeem: cool. please continue to talk with clayg about that too :-) 21:47:53 sure will do :) 21:47:59 thanks 21:48:22 timburke: you got a few mins after the meeting? 21:48:34 yeah, definitely 21:48:46 so in summary, https://review.openstack.org/#/c/402043/ needs some serious review to close a bug, https://review.openstack.org/#/c/415943 is a proposal for symlink API, and talk to jrichli if you're interested in the new keymaster call tomorrow 21:49:06 if there's nothing else.... 21:49:39 thanks, again, for all your work on swift 21:49:43 #endmeeting