Wednesday, 2016-04-13

*** lyrrad has quit IRC00:35
*** acoles_ is now known as acoles07:14
*** openstack has joined #swift311:33
*** openstackgerrit has quit IRC11:35
*** openstackgerrit has joined #swift311:51
*** kota_ has quit IRC13:43
*** bill_az has joined #swift313:46
*** ajiang has quit IRC14:05
*** ajiang has joined #swift314:05
*** bill_az has quit IRC14:38
*** openstack has joined #swift316:10
*** lyrrad has quit IRC16:32
*** lyrrad has joined #swift316:58
*** cschwede has quit IRC18:39
*** openstackgerrit has quit IRC18:39
*** cschwede has joined #swift318:45
*** openstackgerrit has joined #swift318:55
*** acoles is now known as acoles_19:17
*** acoles_ is now known as acoles19:17
*** acoles is now known as acoles_19:23
*** timburke_ has joined #swift320:40
*** hrou_ has joined #swift320:44
*** timburke has quit IRC20:47
*** hrou has quit IRC20:47
*** acoles_ is now known as acoles20:58
*** bill_az_ has joined #swift320:59
*** kota_ has joined #swift321:46
*** timburke_ is now known as timburke21:48
*** acoles is now known as acoles_21:51
*** kota_ has quit IRC22:00
*** kota_ has joined #swift322:15
kota_hello23:00
kota_someone?23:00
kota_timburke?23:01
timburkehi! sorry, forgot to watch the time23:01
kota_no worries, and thanks for your ack :-)23:02
kota_anyone else, here?23:02
kota_ok, let get started...23:03
bill_az_Hi Kota - Bill here23:03
kota_bill_az!!!23:03
bill_az_Sorry I've not been joining - but want to check in today - hope all is well!23:03
kota_bill_az_: welcome and thanks for joining :)23:03
kota_the agenda is at https://wiki.openstack.org/wiki/Meetings/swift323:04
kota_i think today we have some important topics.23:04
kota_fist one, signature v4.23:05
timburkethat's actually the reason i wasn't watching the time :) looking at your patch now23:05
kota_i think we've spent a lot of time to get progress for the patches.23:06
kota_timburke: awesome, thanks.23:06
bill_az_I took a look earlier  - great work!23:06
kota_and, imo it is getting good shape so maybe closely we can land the patch.23:06
kota_I put 3 patches into agenda.23:06
kota_that is because I'd like to hear opinions for some my concerns.23:07
kota_first,23:07
kota_As you can see the first patch in the wiki, we need to bump the keystone version23:08
kota_to enable sigv4 stuff.23:08
timburkeoh right! there's been a release that has support, so we don't have to grab tip of development! love it23:08
kota_timburke: good to hear23:09
kota_so the minimum version will be 9.0.023:09
kota_for keystone.23:09
kota_however, we cannot make the requirement because swift can allow the development model w/o keystone.23:09
kota_i.e. we cannot write "keystone>=9.0.0" in requirements.txt23:10
kota_just make a note into somewhere (conf file or commit log)23:10
bill_az_what is the dependency in mitaka  keystone?23:11
kota_keystone-mitaka is 9.0.023:11
kota_released around a few weeks ago.23:11
bill_az_but why does sigv4 need version?23:12
kota_bill_az_: good question23:12
timburkeprevious versions of keystone didn't have v4 signature support. it was added in https://github.com/openstack/keystone/commit/f11d39623:13
kota_sig v4 requires new algorithms for header parsing and signature calculation.23:13
kota_yeah, that patch adds the new algorithms.23:13
bill_az_ahh - ok - got it23:14
kota_for now, the sig v4 is working only with keystone and we need continous work to improve (maybe with tempauth?) somewhat.23:15
bill_az_In the ibm os distribution we had been using, the s3 code was pulled out of keystone - we packaged separately - but I got it now :-)23:15
kota_bill_az_: ah, it might be affected.23:16
kota_circle back to my first question, can we make it to land with the keystone dependency?23:17
kota_just run functional test in gerrit gate with keystone 9.0.023:17
kota_i.e. we are changing default support keystone into 9.0.023:19
timburkefor our tests? absolutely. for deployers, i think documentation should be sufficient; this isn't worth adding to the extras section in setup.cfg23:19
kota_ah, good catch. need to change setup.cfg too.23:19
kota_ok, thanks23:19
kota_moving on to second concern.23:20
kota_I put 3rd patch in the wiki to make sure what's changed with keystone conversation and amazingly, keystone is no care about the region information v4 stuff using for authentication.23:21
timburkeyep. for better or worse, keystone doesn't really care about the region in the request23:22
kota_in the original patch for v4 andrey wrote, he said "we need to set region name with same value of keystone setting"23:22
kota_i'm not sure for now, but I'm douting that it is really reasonable for authentication (or not)23:23
timburkethis seems consistent with what region-less auth systems will do, though; swauth and tempauth don't have that concept (as far as i know)23:23
kota_yeah, an user should use the region name which is same value of *swift3* setting.23:25
kota_timburke: exactly, if we go this way, it will be easy to apply v4 calculation to any other auth system which don't have the concept23:26
kota_hmm23:26
kota_but some auth info bleed to swift side.23:27
kota_s/some/an/23:27
kota_because I'm not security guy, I'm not sure it's ok swift3 keeps authenticaion info itself.23:28
timburkei think i'm fine with it; i could see an argument for region being part of authorization (and so swift3's responsibility, at least with s3_acl enabled) rather than authentication (keystone's responsibility)23:30
timburkei'd be open to reconsidering that if we ever had some sort of multi-region support, but i'm not sure how we'd do that currently23:30
kota_timburke: thanks, and ok keep it in my mind. For now, we can keep the current way.23:31
kota_that's all for sigv4 from me.23:32
kota_anything else for this topic?23:32
timburkedon't think so. i think i'll have comments ready for you later this week23:33
kota_ok, let's moving to the next.23:33
kota_Release timing23:33
kota_I think, we don't have to make a version bump *before* sigv4 stuff landing23:33
kota_because we have really a few things to land since last updated (sorry slow reviews)23:34
bill_az_That seems reasonable to me - v1.11 has sigv4 + small stuff23:34
timburkesounds good23:34
kota_k, we will make the release after sigv4 stuff done.23:35
kota_and the last topic today from me is Austin summit.23:35
timburkei'll be there!23:36
kota_Summit will happen in the week since 25 Apr.23:36
kota_timburke: great!23:36
kota_bill_az_: how about you?23:36
bill_az_Yes - I will be there!23:37
kota_great!23:37
kota_so my question is that do we need to make an extra time (e.g. mini design summit) for swift3 specific?23:38
kota_I'll be there too23:38
kota_*BUT*23:38
bill_az_I would like to meet up there -23:38
kota_i'll stay really short time for this time (flight in Monday and flyout Friday morning)23:38
kota_bill_az_: good to hear, me too.23:39
bill_az_could we meet on Wed sometime?  or thurs?  (I will leave on Thursday late afternoon)23:39
timburkei'll be there all week; i think any time that works for you guys will be fine for me23:40
bill_az_timburke:  looking forward to meeting you!23:40
kota_yup, maybe we have a hole slot of Swift design summit in Wed?23:41
bill_az_do you know if lyrrad will be attending?23:41
kota_it might be swap with other project, not sure.23:41
timburkeunfortunately, lyrrad won't be there. there'll be some other swiftstackers about, but not as involved in swift323:42
kota_that's too bad:/23:42
timburkewednesday sounds good to me23:42
kota_I'm missing design summit schedule slot23:42
kota_:/23:42
bill_az_I wanted to check on the posting of results of ceph-s3 tests - he had done some work on that, but I don't know where it ended up23:43
kota_i think, timburke also is working on the stuff23:43
timburkei can talk to notmyname about working us in; worst case, we can just go off in a corner sometime23:43
timburkei have been! see patch 30436723:44
kota_https://review.openstack.org/#/c/304367/23:44
patchbottimburke: https://review.openstack.org/#/c/304367/ - swift3 - WIP: add ceph-s3-tests tox env23:44
patchbotkota_: patch 304367 - swift3 - WIP: add ceph-s3-tests tox env23:44
timburkeyeah :-) that one23:44
kota_same one :)23:44
kota_i think it's great stuff waiting for dropping WIP tag with coffee :)23:45
kota_ok, maybe swift3 meeting will happen at Wed, I'll check the free slot later and ping you all.23:46
bill_az_great - Thanks!23:46
timburkei still need to look into getting that as a (non-voting) gate job, though. and i need to think about how to (1) use a known-failures file and (2) update the known-failures file on merges to master23:46
kota_bill_az_: do you want to send the ping via E-mail? or Is IRC enough for you?23:46
timburkethen we could turn it into a voting gate if we wanted23:46
bill_az_do you want to post it on the swift3 wiki?  or if you email me I can add to wiki - billowen@us.ibm.com23:47
bill_az_I will be on IRC more these next weeks too23:48
kota_bill_az_: ok, I'll update the wiki and send the notification for you.23:48
kota_timburke: great23:48
bill_az_Thanks kota_:23:48
kota_timburke: sounds like really useful (I don't have the idea yet)23:50
kota_timburke: thanks for working on that :)23:51
kota_anything else for today?23:51
timburkehappy to; it's one of those useful tools i keep forgetting to use :P23:51
timburkeyou probably noticed a flurry of patches from me recently23:51
timburkei figure it might be nice to have a summary of what they were23:51
timburkei've got a couple testing-infrastructure niceties (patch 294782, patch 294849)23:51
patchbottimburke: https://review.openstack.org/#/c/294782/ - swift3 - Make Swift/Keystone logs available in gate results23:51
patchbottimburke: https://review.openstack.org/#/c/294849/ - swift3 - Fix up some warnings23:51
timburkea couple regressions on newer swift (patch 301976, patch 301937)23:52
patchbottimburke: https://review.openstack.org/#/c/301976/ - swift3 - Catch segment-too-small errors from 2.6.0+ swift23:52
patchbottimburke: https://review.openstack.org/#/c/301937/ - swift3 - Allow multipart uploads to have an empty final part23:52
timburkeand a little patch to prevent an exception in some clients (patch 302475)23:52
patchbottimburke: https://review.openstack.org/#/c/302475/ - swift3 - Include '-' in multipart ETags23:52
timburkei also noticed a behavioral difference between AWS and swift when deleting a key that doesn't exist; AWS returns 204 while swift (and therefore swift3) returns 40423:52
timburkedon't have a patch for that one yet, though23:53
kota_ok, I will look at.23:54
kota_thanks for bringing up.23:54
kota_looking at the titles. all of them are reasonable.23:55
kota_anything?23:56
timburkethat's it for me23:57
kota_ok23:58
kota_bill_az_ ?23:58

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!