Wednesday, 2015-12-16

*** lyrrad has quit IRC01:42
openstackgerritMerged openstack/swift3: Deprecated tox -downloadcache option removed  https://review.openstack.org/25672604:24
openstackgerritMerged openstack/swift3: Accept URL-encoded x-amz-copy-source headers  https://review.openstack.org/24601805:44
openstackgerritAndrey Pavlov proposed openstack/swift3: support AWS signature v4  https://review.openstack.org/21193306:15
openstackgerritAndrey Pavlov proposed openstack/swift3: Fix timestamp parsing for non-UTC systems.  https://review.openstack.org/25843811:43
openstackgerritAndrey Pavlov proposed openstack/swift3: support AWS signature v4  https://review.openstack.org/21193311:54
openstackgerritAndrey Pavlov proposed openstack/swift3: support AWS signature v4  https://review.openstack.org/21193312:12
openstackgerritAndrey Pavlov proposed openstack/swift3: support AWS signature v4  https://review.openstack.org/21193312:13
openstackgerritAndrey Pavlov proposed openstack/swift3: support AWS signature v4  https://review.openstack.org/21193314:07
openstackgerritAndrey Pavlov proposed openstack/swift3: support AWS signature v4  https://review.openstack.org/21193314:12
openstackgerritAndrey Pavlov proposed openstack/swift3: support AWS signature v4  https://review.openstack.org/21193314:13
openstackgerritAndrey Pavlov proposed openstack/swift3: support AWS signature v4  https://review.openstack.org/21193314:21
*** lyrrad has joined #swift317:25
*** lyrrad has quit IRC20:05
*** lyrrad has joined #swift320:06
*** lyrrad has quit IRC20:15
*** lyrrad has joined #swift320:19
kota_hello23:00
kota_meeting time?23:00
timburkegood morning!23:01
siva_krishnanhi!23:01
kota_siva_krishnan: hi! i'm happy you are joining this meeting :)23:01
lyrradHi!23:01
kota_timburke, lyrrad: good afternoon (or evening?)23:02
siva_krishnanexcited to be part of this team23:02
kota_alright, let's gett started.23:03
kota_meeting agenda is here, https://wiki.openstack.org/wiki/Meetings/swift323:03
kota_today we have a few agenda23:03
kota_i expected we don't need a lot of time to go through them.23:03
kota_move on to first one23:04
kota_Swift3 v1.9 released in the last week.23:04
kota_that consists of a bunch of swiftstack works almostly23:04
kota_thanks swiftstackers :)23:05
kota_and23:05
kota_i think the release is an important thing because it includes a fix for a CVE issue, you know.23:06
timburkethanks for driving the security-related stuff kota_!23:06
kota_timburke: sure23:06
kota_but sorry it was needed much time because it is the first time to me to work for security :P23:07
timburkeno worries :)23:07
kota_to note that, the CVE id is CVE-2015-846623:08
kota_and we started new-release cycle :)23:08
kota_i'm not sure which version number is suitable for next release :/23:08
kota_i mean, v1.10 vs v2.023:09
siva_krishnanv2.0 sounds good!23:09
kota_anyways, thanks for great works for v1.9 and i'm looking forward to next one will be awsome too :)23:10
kota_siva_krishnan: i expects you will work a lot for v2.0 ;)23:11
kota_that's all for v1.9 release.23:12
kota_next23:12
kota_recent updates23:12
siva_krishnansure23:12
kota_who guys want to start?23:13
kota_start from me...23:14
kota_except v1.9 release...23:14
kota_recently i was working for re-writing x-timestamp stuff23:15
timburkei like where that change is going23:15
kota_at first, that patch was to fix 2 stuff, one is x-timestamp and the other is last-modified in response header.23:15
kota_yeah, i'm sure that is getting better.23:16
kota_x-timestamp stuff is https://review.openstack.org/#/c/242578/23:17
kota_patch 24257823:17
patchbotkota_: https://review.openstack.org/#/c/242578/ - Ensure X-Timestamp always23:17
kota_timburke: tim, do you still have some concerns for it?23:17
kota_timburke: if we don't have any issues for that, i'd like to merge to upstream repo.23:18
timburkei'll have to double check. i don't think so, but i'll be sure to leave a review later this week23:18
timburkeor we can just go with it :)23:18
kota_thanks :)23:19
kota_and i'll take a time to look at other stuffs this month, please feel free to ask me to head up to your patches :)23:20
kota_that's all from me23:20
siva_krishnanI will go next o/23:21
kota_o/23:21
lyrrado/23:21
kota_anything else?23:22
siva_krishnani have trouble installing s3compat suite23:22
siva_krishnancan someone help me with that ?23:23
lyrradWhat seems to be the issue?23:23
kota_lyrrad: your turn ;)23:23
siva_krishnanSAXParseException: <unknown>:19:2: mismatched tag23:24
siva_krishnanI am getting the above error when trying to run bin/run_ceph_tests.py23:25
kota_looks like invalid html/xml exception23:25
lyrradI’m not familiar with that error.  Presumably one of the input file is formatted unexpectedly.  Perhaps you can send me a message with details on where that error is happening.23:25
siva_krishnansure. will send it after the meeting23:26
kota_well23:28
kota_any other issues or patches to discuss?23:29
lyrradNone for me.23:29
kota_ok23:29
timburkejust one heads-up about a fix to multipart uploads. patch 25506923:30
patchbottimburke: https://review.openstack.org/#/c/255069/ - Support x-amz-copy-source-range for Upload Part - ...23:30
kota_looks like SLOrange?23:31
timburkenot exactly, but similar :)23:31
kota_ok, starred and added me to reviewers23:32
kota_will look at in this week.23:32
kota_interesting23:32
timburkewe want an actual COPY request (like with the rest of the copy-to-upload-part stuff), but we need to be able to just use part of the object23:32
kota_yup23:33
kota_Is that range request already supported in normal COPY?23:33
kota_(i forgot something around there23:34
kota_i mean "not multi upload stuff"23:34
timburkeas i recall. it does weird things if there's more than one range specified (it'll store the multi-part mime doc), but S3 only supports a single range anyway23:35
kota_ah23:35
kota_ic23:35
kota_sometimes s3 behaves as weird :/23:35
timburkei should probably write a func test for that one...23:36
kota_and it looks no range api for normal COPY :/23:36
kota_timburke: looking forward to adding that :)23:37
kota_anything?23:37
timburkenope. which is definitely odd. but then, swift doesn't even document that COPY supports Range headers, so...23:38
timburkenone from me23:38
kota_the last part of today is the schedule for next meeting :)23:38
kota_i think we are getting to the end of year23:39
kota_next week in x-mas and the after will be 30th Dec23:39
kota_so if we don't have urgent stuff, I'd like to schedule next meeting at the beggining of next year.23:40
kota_How about 7th Jan?23:40
timburkeworks for me23:40
kota_no23:40
kota_sorry23:40
kota_6th Jan23:40
kota_i meant23:40
kota_on UTC23:41
timburkeclose enough ;)23:41
kota_(JST is earlier than UTC and it will be morning at 7th Jan)23:41
siva_krishnanworks for me23:41
kota_lyrrad?23:42
kota_i believe him too. So I will write down the next schedule in meeting wiki later.23:43
kota_and if you need conversation, please feel free to bring it up on this IRC channel :)23:43
kota_that's all for today.23:44
kota_thanks for working swift3 and have a good x-mas vacations :)23:44
timburkethanks kota_!23:44
timburkeand siva_krishnan, i'll be sure to take a look at patch 155221 this week23:45
patchbottimburke: https://review.openstack.org/#/c/155221/ - Fix Delete Multiple Objects process when multipart...23:45
siva_krishnanthanks all. Happy X-mas and  New year!!23:45
siva_krishnantimburke  thanks a lot23:46
siva_krishnanworking on 159130 patch as well.23:47

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