Thursday, 2016-12-08

*** Jeffrey4l has quit IRC00:03
claygtimburke: can you say all of that on the review "for other reviewers here's what you can do ..."00:03
*** Jeffrey4l has joined #openstack-swift00:03
*** vint_bra has joined #openstack-swift00:08
*** asettle has joined #openstack-swift00:12
*** Worry has joined #openstack-swift00:13
*** asettle has quit IRC00:17
*** Worry has quit IRC00:27
*** krypto has quit IRC00:30
*** chsc has quit IRC00:33
claygtdasilva: you have the 1.4.0 release stuff right there!00:43
*** jamielennox is now known as jamielennox|away00:45
claygok, let's see what I can do with patch 408257 and patch 40828000:45
patchbothttps://review.openstack.org/#/c/408257/ - liberasurecode - 1.4.0 release00:45
patchbothttps://review.openstack.org/#/c/408280/ - pyeclib - release 1.4.000:45
*** tqtran has quit IRC00:54
*** jistr|mtgs has quit IRC01:00
*** jistr has joined #openstack-swift01:00
*** tovin07 has quit IRC01:08
tdasilvaclayg: hi, sorry i'm back now01:10
tdasilvaclayg: yeah we need to merge those two patches01:10
*** asettle has joined #openstack-swift01:13
*** Jeffrey4l has quit IRC01:18
*** asettle has quit IRC01:18
*** Jeffrey4l has joined #openstack-swift01:19
*** _JZ_ has quit IRC01:30
*** mingyu has joined #openstack-swift01:38
*** diogogmt has quit IRC01:49
*** jamielennox|away is now known as jamielennox01:50
*** vint_bra has quit IRC02:05
*** klrmn has quit IRC02:12
*** asettle has joined #openstack-swift02:14
*** asettle has quit IRC02:19
*** Jeffrey4l has quit IRC02:26
*** Jeffrey4l has joined #openstack-swift02:26
*** Jeffrey4l has quit IRC02:31
*** Jeffrey4l has joined #openstack-swift02:31
kota_hello02:36
kota_a bit late morning due to no meeting02:36
kota_it looks like a lot of ec conversation occurred while i was asleep02:38
kota_let's scroll back to check....02:38
*** bkopilov has quit IRC02:43
*** cdelatte has quit IRC02:43
*** Jeffrey4l has quit IRC02:46
*** Jeffrey4l has joined #openstack-swift02:47
*** clu_ has quit IRC02:47
*** diogogmt has joined #openstack-swift02:50
*** dmorita has quit IRC03:05
mattoliveraukota_: o/03:07
kota_mattoliverau: o/03:07
*** siva_krish has joined #openstack-swift03:07
*** saltsa has quit IRC03:12
*** saltsa has joined #openstack-swift03:13
*** asettle has joined #openstack-swift03:15
*** asettle has quit IRC03:20
*** dmorita has joined #openstack-swift03:26
*** dmorita has quit IRC03:30
*** klrmn has joined #openstack-swift03:33
*** Jeffrey4l has quit IRC03:38
*** Jeffrey4l has joined #openstack-swift03:38
*** Jeffrey4l has quit IRC03:42
*** Jeffrey4l has joined #openstack-swift03:43
openstackgerritMatthew Oliver proposed openstack/swift: Move documented reclaim_age option to correct location  https://review.openstack.org/37441903:50
mattoliverau^^ just a rebase03:51
*** psachin has joined #openstack-swift03:54
*** Jeffrey4l has quit IRC03:56
*** Jeffrey4l has joined #openstack-swift03:56
*** klrmn has quit IRC03:59
*** mingyu has quit IRC03:59
*** Jeffrey4l has quit IRC04:00
*** Jeffrey4l has joined #openstack-swift04:01
*** manous has quit IRC04:03
*** bkopilov has joined #openstack-swift04:03
*** Jeffrey4l has quit IRC04:06
*** Jeffrey4l has joined #openstack-swift04:06
*** Jeffrey4l has quit IRC04:09
*** Jeffrey4l has joined #openstack-swift04:09
*** asettle has joined #openstack-swift04:16
*** asettle has quit IRC04:21
*** Jeffrey4l has quit IRC04:24
*** Jeffrey4l has joined #openstack-swift04:24
*** Jeffrey4l has quit IRC04:25
*** Jeffrey4l has joined #openstack-swift04:27
mahatic_mattoliverau: thanks04:36
openstackgerritMerged openstack/pyeclib: Add tests for the availability of individual backends  https://review.openstack.org/40826104:40
kota_tdasilva, clayg, timburke: as well timburke said, I'd love to https://review.openstack.org/#/c/405926/ to get in to the 1.4.0 liberasurecode release.04:52
patchbotpatch 405926 - liberasurecode - Add get_version functionality to liberasurecode lib04:52
kota_tdasilva: clayg, timburke: reading back the log, the idea pyeclib (and future go lang ec lib) will be into liberasurecode as bindings are great04:53
kota_tdasilva, clayg, timburke: however, we still have to look up pyeclib a little more time until the work finished and the version reference could be problematic for anyone who dosn't know what's going on at pyeclib/liberasurecode04:54
kota_tdasilva, clayg: timburke's example looks quite to make me sense to get sanity the difference w/ or w/o the change so that it will help you to review the patch.04:56
*** ppai has joined #openstack-swift05:03
*** links has joined #openstack-swift05:05
*** arch-nemesis has joined #openstack-swift05:14
*** asettle has joined #openstack-swift05:17
*** arch-nemesis has quit IRC05:18
*** asettle has quit IRC05:22
*** hseipp has joined #openstack-swift05:29
*** arch-nemesis has joined #openstack-swift05:39
*** tovin07 has joined #openstack-swift05:59
*** chsc has joined #openstack-swift06:03
*** chsc has joined #openstack-swift06:03
*** chsc has quit IRC06:08
*** peter-wang has joined #openstack-swift06:09
peter-wanghi This is peter06:10
peter-wangI met 503 Service Unavailable when upload new file to swift06:12
peter-wangI add new storage devices to swift cluster06:12
peter-wangbut seems not succeeded, the cluster capacity did not increase.06:13
peter-wangcan anyone help me out?06:13
kota_peter-wang: I don't think 503 is related to capacity problem because if no enough space is there to be written, probably it will be 507 InsufficientStorage instead of 50306:16
kota_peter-wang: so that you may hit another problem.06:16
kota_peter-wang: did your proxy or object server log say anything?06:17
*** asettle has joined #openstack-swift06:18
*** dmorita has joined #openstack-swift06:19
*** ChubYann has quit IRC06:20
*** asettle has quit IRC06:23
*** dmorita has quit IRC06:23
*** mingyu has joined #openstack-swift06:28
*** _david_cole_soho has joined #openstack-swift06:37
*** sams-gleb has joined #openstack-swift06:40
*** sams-gleb has quit IRC06:40
*** sams-gleb has joined #openstack-swift06:40
_david_cole_sohoI have upgraded a medium size cluster to newton and I’m finding that after I upload an object, I may get one etag back and later I get a different etag back.06:45
_david_cole_sohoI wonder if one of my backends is running old code, gonna check that first06:46
zaitcevwhich of those etags is correct though? You can verify by running md5sum07:10
_david_cole_sohoWhen I saw it change, the most recent one was correct07:11
*** hseipp has quit IRC07:11
_david_cole_sohoI have a bunch of account/container/object paths from an application that is failing at the moment.  Maybe if I use swift-get-nodes on them I will find a correlation07:13
zaitcevSo the etag returned by PUT is incorrect?07:14
*** mingyu has quit IRC07:14
zaitcevBut the one in HEAD is correct?07:14
_david_cole_sohoI am not sure if the PUT etag is correct or not.   I was looking at an object with Cyberduck (which most likely just HEAD’s the object) and the etag changed, from one minute to the next07:17
_david_cole_sohoThat sounds like the object being overwritten I know07:17
_david_cole_sohoBut the data in question is written by an application that only writes once, using a UUID based object path07:18
_david_cole_sohoAnd this has only started to occur since I upgraded to Netwton over the weekend07:18
*** asettle has joined #openstack-swift07:19
*** mingyu has joined #openstack-swift07:19
*** asettle has quit IRC07:23
*** SkyRocknRoll has joined #openstack-swift07:25
*** SkyRocknRoll has quit IRC07:25
*** SkyRocknRoll has joined #openstack-swift07:25
*** rcernin has joined #openstack-swift07:26
*** McMurlock1 has joined #openstack-swift07:32
*** oshritf has joined #openstack-swift07:32
_david_cole_sohoI’ve checked my ACO servers and they all seem to be running the newton package and the processes were all restarted on the 5th, so I don’t think it’s a mismatch.  I’m going to try and confirm if PUT is returning a different etag to a later HEAD07:37
zaitcevWith Cyberduck, I think it's interesting to (a) get logs and filter proxy logs by your own client IP, the TxID (transaction), then collect transaction logs. This should point out if a particular node reports wrong Etag.07:44
zaitcevAnd (b) check if etag flips back and forth - although that does not tell you anything really07:45
*** mingyu has quit IRC07:48
_david_cole_sohoUsing curl I have been able to upload the same object 20 times, the PUT returns the same ( correct!) etag but a GET on the container shows me some of the objects I uploading have a different etag07:51
zaitcevyeah, your updater lags07:51
zaitcevprobably you can find a megabyte-long pending/ directory somewhere07:52
_david_cole_sohoThank you for the help, I will look at the updater and see if there is a big pending directory07:53
_david_cole_sohoWe enabled encryption at rest when we upgraded to newton a few days ago, I hope that is not involved...07:53
zaitcevugh07:54
zaitcevWell, that's for Janie or whoever knows how that works. I don't use it, so no idea.07:54
_david_cole_sohoI may disable it if nothing else is wrong07:55
zaitcevEncryption creates a challenge for etags, because now the object's on-disk etag differs from what the client wants, which is plaintext etag.07:55
zaitcevI heard that some extraordinary tricks are used to shuffle etags, I wonder if it's a bug07:56
zaitcevAuditor can only verify the encrypted etag (obviously...), so that one is attached to object as the Etag parameter, and the data's etag is stuffed somewhere, like sysmeta... I dunno really, sorry.07:57
*** hseipp has joined #openstack-swift08:01
_david_cole_sohoI’ve matched one of the incorrect etags in the container GET to a .data file on the object server, which of course which by encrypted.  That’s concerning, the encrpted file etag is presented to the user, which I don’t think it ever should be08:09
*** dmorita has joined #openstack-swift08:11
*** dmorita has quit IRC08:15
*** asettle has joined #openstack-swift08:20
*** mingyu has joined #openstack-swift08:20
*** asettle has quit IRC08:24
_david_cole_sohoA pastebin showing what I am seeing regarding encrypted object etags sporatciatlly appearing in container listings: http://paste.openstack.org/show/591755/08:25
*** jamielennox is now known as jamielennox|away08:33
*** rledisez has joined #openstack-swift08:34
*** mingyu has quit IRC08:40
*** mingyu has joined #openstack-swift08:43
*** jordanP has joined #openstack-swift08:43
openstackgerritCao Xuan Hoang proposed openstack/swift: Use assertGreater(len(x), 0) instead of assertTrue(len(x) > 0)  https://review.openstack.org/40848808:47
zaitcev_david_cole_soho: file a bug in the launchpad, please. Sorry, this may not have an immediate resolution08:50
_david_cole_sohowill do, thanks for your help08:51
zaitcev_david_cole_soho: if nobody picks in a day or two, try to poke acoles_ or jamielennox|away08:51
zaitcevprobably what happens here, if the object server succeeds in update, it updates correctly, but if the update goes into pending, then the updater screws it up08:53
*** cbartz has joined #openstack-swift08:53
*** cbartz has quit IRC08:53
_david_cole_sohoit’s interesting that over time, the first set of objects that have incorrect etags in the listing are corrected, but others that were fine go bad08:55
zaitcevalthugh, I dunno... your pastebin says the md5 of the encrypted object is not 2ca803d66d53d85c3b7c6ded5cdcd2e8, but d2cffe8cadfd3e7f7cf6d998285da18f08:55
zaitcevanyway, I need to drop08:55
zaitcevLet Jamie & Co. to figure it out08:56
*** pcaruana has joined #openstack-swift08:58
*** peter-wang has quit IRC09:15
*** peter-wang has joined #openstack-swift09:16
mahatic__david_cole_soho: hello, did you happen to verify this part you've mentioned? "<_david_cole_soho> I wonder if one of my backends is running old code, gonna check that first"09:19
mahatic_It could be the case that one of the backends is not upgraded and the data is not being decrypted - probably the reason for you to be seeing encrypted etag values09:20
*** asettle has joined #openstack-swift09:24
_david_cole_sohomahatic_: I confirmed that the Ubuntu packages were all correct on the back end - all running Newton.  I believe all were restarted after the package install, but I suppose it might be possible that one was not.09:26
openstackgerritSachin Patil proposed openstack/swift: Fix swift-get-nodes arg parsing for missing ring  https://review.openstack.org/40601209:27
*** mvk has quit IRC09:39
*** mingyu has quit IRC09:42
*** hseipp has quit IRC09:43
mahatic__david_cole_soho: ok, could you file a bug after confirming that and with more details on your cluster config?09:44
mahatic_I'm gonna try and reproduce it09:45
_david_cole_sohomahatic_: sure, will do09:45
*** hogepodge has quit IRC09:45
*** hogepodge has joined #openstack-swift09:46
mahatic_also you could make sure that your conf adheres to this: http://docs.openstack.org/developer/swift/overview_encryption.html#deployment-and-operation09:49
*** sams-gleb has quit IRC09:57
*** sams-gleb has joined #openstack-swift09:58
*** sams-gleb has quit IRC10:02
*** mvk has joined #openstack-swift10:11
mahatic__david_cole_soho: FWIW, I tried to reproduce, my container listing shows the correct etags for all the objects (I tried 20 objects with similar data uploaded with diff names)10:16
openstackgerritChristopher Bartz proposed openstack/swift: tempurls with a prefix-based scope  https://review.openstack.org/27404810:24
*** peter-wang has quit IRC10:24
*** si1ver has quit IRC10:24
*** cbartz has joined #openstack-swift10:25
*** _david_cole_soho has quit IRC10:33
*** links has quit IRC11:00
*** hogepodge has quit IRC11:01
*** acoles_ is now known as acoles11:07
*** links has joined #openstack-swift11:16
*** Jeffrey4l has quit IRC11:20
*** hogepodge has joined #openstack-swift11:21
*** hogepodge has quit IRC11:26
acolesis david cole still here?11:29
acolesjoel?11:30
*** jarbod has joined #openstack-swift11:32
acolesfwiw the mixed etag issue described could be due to some object servers not being upgraded. Obviously I can't say for sure but it would explain the symptoms,11:35
acolesmahatic_: zaitcev ^^11:35
mahatic_acoles: agree, it looks like it11:37
*** hogepodge has joined #openstack-swift11:38
*** psachin has quit IRC11:42
*** Jeffrey4l has joined #openstack-swift11:43
*** hogepodge has quit IRC11:48
*** vint_bra has joined #openstack-swift11:54
*** Wzze has joined #openstack-swift12:00
*** hogepodge has joined #openstack-swift12:00
*** psachin has joined #openstack-swift12:01
*** joeljwright has joined #openstack-swift12:08
*** ChanServ sets mode: +v joeljwright12:08
*** psachin has quit IRC12:08
*** psachin has joined #openstack-swift12:10
joeljwrightacoles: you about? we're having some 'interesting' experiences with encryption12:10
joeljwrightacoles: the etag returned for an uploaded object seems to be inconsistent between requests12:11
joeljwrightacoles: same proxy each time12:12
joeljwrightacoles: just wondering if you had any thoughts?12:12
*** bkopilov has quit IRC12:15
*** Wzze has quit IRC12:16
*** McMurlock1 has quit IRC12:21
*** jordanP has quit IRC12:23
acolesjoeljwright: hi.12:24
acolesjoeljwright: I read what david described in scrollback12:25
acolesjoeljwright: It would be consistent with not all object servers being upgraded when objects are PUT12:25
acolesjoeljwright: if that were the case then some container updates would have the etag of the ecnrypted object content, which is what david sees in listing some timez12:26
acolesjoeljwright: but some ocntainer updates (from upgraded object servers) would get the encrypted etag of the original object.12:27
joeljwrightacoles: we believe that everything is upgraded at the moment and we're seeing this with new uploads12:27
acolesjoeljwright: oh. then I don't have a ready explanation :/12:28
joeljwrightacoles: I guess it's time to go checking the object servers :)12:28
joeljwrightthanks for the suggestions12:28
*** McMurlock1 has joined #openstack-swift12:37
acolesjoeljwright: let us know12:39
acolestdasilva: did you have a patch for swift-object-info to show transient sysmeta? or did I dream that?12:39
openstackgerritChristopher Bartz proposed openstack/python-swiftclient: prefix-based tempurls support  https://review.openstack.org/40859612:45
*** vinsh has quit IRC12:48
*** psachin has quit IRC12:50
*** psachin has joined #openstack-swift12:52
*** links has quit IRC12:53
*** psachin has quit IRC12:59
*** psachin has joined #openstack-swift13:03
*** links has joined #openstack-swift13:05
*** AndyWojo has quit IRC13:09
*** AndyWojo has joined #openstack-swift13:10
*** psachin has quit IRC13:15
tdasilvagood morning13:31
tdasilvaacoles: the patch was to pring the metadata checksum13:32
tdasilvaacoles: but that does sound like a good idea13:32
acolestdasilva: right, thanks. maybe someone else did it.13:59
*** klamath has joined #openstack-swift14:03
*** klamath has quit IRC14:03
*** klamath has joined #openstack-swift14:03
*** psachin has joined #openstack-swift14:07
*** _JZ_ has joined #openstack-swift14:11
*** dmorita has joined #openstack-swift14:12
*** dmorita has quit IRC14:17
*** bkopilov has joined #openstack-swift14:17
*** StraubTW has joined #openstack-swift14:26
*** jordanP has joined #openstack-swift14:33
*** si1ver has joined #openstack-swift14:44
openstackgerritShashirekha Gundur proposed openstack/python-swiftclient: modify 'swift <sub_command> —help' display  https://review.openstack.org/39011914:47
*** daemontool has joined #openstack-swift14:49
*** si1ver has quit IRC14:49
*** psachin has quit IRC15:04
*** klrmn has joined #openstack-swift15:05
*** chlong has joined #openstack-swift15:13
*** si1ver has joined #openstack-swift15:19
*** links has quit IRC15:20
*** sams-gleb has joined #openstack-swift15:29
jrichliIs there a Denis Makogon here?15:41
*** cdelatte has joined #openstack-swift15:43
*** delattec has joined #openstack-swift15:43
*** delattec has quit IRC15:44
*** cdelatte has quit IRC15:44
*** cdelatte has joined #openstack-swift15:44
*** arch-nemesis has quit IRC15:46
*** ppai has quit IRC15:59
*** chsc has joined #openstack-swift16:02
*** daemontool has quit IRC16:05
*** SkyRocknRoll has quit IRC16:05
notmynamegood morning16:12
notmynametdasilva: looks like there was some progress on ec stuff yesterday. what do you need me to do to help with the releases?16:14
notmynamealso, is the get_version() patch going to be part of it?16:14
notmynamealso, I support merging pyeclib and liberasurecode :-)16:14
*** SkyRocknRoll has joined #openstack-swift16:15
notmynamealso, I had a conversation here yesterday with someone who wants to add another EC backend and get involved16:15
tdasilvanotmyname: could you help review https://review.openstack.org/#/c/408257/16:15
patchbotpatch 408257 - liberasurecode - 1.4.0 release16:15
tdasilvaand https://review.openstack.org/#/c/408280/16:15
patchbotpatch 408280 - pyeclib - release 1.4.016:15
tdasilvanotmyname: was it https://memoscale.com/ ?16:16
notmynameno16:16
tdasilvaok16:16
notmynamebut that's cool too :-)16:17
tdasilvaheh, i think they were in barcelona or austin16:17
tdasilvacan't remember16:17
tdasilvanotmyname: re: get_version() IIRC it looks like kota_ would like to have it in, but clayg and timburke were fine if it landed after release16:18
tdasilvaso i guess it would be nice to get consensus16:18
*** pcaruana has quit IRC16:19
*** mingyu has joined #openstack-swift16:23
notmynameit's already got a +2 on it (https://review.openstack.org/#/c/405926/)16:25
patchbotpatch 405926 - liberasurecode - Add get_version functionality to liberasurecode lib16:25
notmynameunless there's a reason we need the release *TODAY*RIGHT*NOW* instead of tomorrow, then let's land p 405926 and do the release including it16:27
patchbothttps://review.openstack.org/#/c/405926/ - liberasurecode - Add get_version functionality to liberasurecode lib16:27
*** mvk has quit IRC16:30
*** rcernin has quit IRC16:31
*** oshritf has quit IRC16:32
*** hseipp has joined #openstack-swift16:34
*** vinsh has joined #openstack-swift16:35
*** cbartz has left #openstack-swift16:39
*** SkyRocknRoll has quit IRC16:41
*** mingyu has quit IRC16:56
openstackgerritAlistair Coles proposed openstack/swift: line wrap overview_expiring_objects.rst  https://review.openstack.org/40871716:58
*** rcernin has joined #openstack-swift17:03
acolestdasilva: found it, it was timburke's patch 341663 :)17:10
patchbothttps://review.openstack.org/#/c/341663/ - swift - Call out transient sysmeta in swift-object-info17:10
tdasilvaacoles: nice! we should try to land that, it will probably be useful for debugging encrypted data files??17:11
*** hseipp has quit IRC17:11
acolesyes! this ^^ might help joeljwright diagnose his mixed up etags. if you PUT an object with some x-object-meta-foo and have encryption in proxy then only upgraded object servers will store the associated x-object-transient-sysmeta.17:12
acolesSo using patched swift-object-info on "dodgy" objects would indicate upgrade or not.17:13
jrichliI'll take a look at the patch as well.  and, btw, i wasn't aware of joeljwright having the above mentioned issue.17:16
jrichliah, i see i missed some scrollback.  reading now17:19
joeljwrightacoles, jrichli: thanks, we're still digging, it really it the worst kind of transient failure17:21
acolesjoeljwright: fyi I am not here tomorrow but back next week17:22
joeljwrightacoles: now I'm confused **and** jealous!17:22
pdardeaui put together some basic docs about swift ec pieces/parts (for my own understanding)17:25
pdardeauhttp://goo.gl/rlhA0M17:25
pdardeauwill continue filling in some of the missing pieces17:26
clayggood morning17:31
claygi still see no tarballs on liberasure releases - so i'm guessing i'm still working on that today17:32
acolesjoeljwright: if you can PUT an object with user metadata (x-object-meta-*) and then use swift-get-nodes to find the data file for one of the misbehaving objects, then do python -c "import swift.obj.diskfile as df;print(df.read_metadata('path_to_.data_file'))"17:32
*** vinaypotluri has joined #openstack-swift17:33
acolesjoeljwright: you should see a key(s) starting 'X-Object-Transient-Sysmeta-Crypto-Meta-17:33
acolesjoeljwright: if you don't, then the object server was not upgraded17:33
joeljwrightacoles: that's a great test, thanks17:34
claygnotmyname: i need a release of liberasurecode and pyeclib today - also patch 405926 doesn't really solve anything without the pyeclib change to expose it - and pyeclib can't merge that because of dependencies and distros17:34
patchbothttps://review.openstack.org/#/c/405926/ - liberasurecode - Add get_version functionality to liberasurecode lib17:34
acolesif we'd merge timburke's patch then swift-object-info would have done that for you :/17:34
tdasilvaacoles: just got started with this: https://etherpad.openstack.org/p/swift_tiering_foundational_work17:34
tdasilvaacoles: looking forward to your (and others) input17:34
acolestdasilva: great, thanks17:35
*** rledisez has quit IRC17:35
tdasilvagoing out to get some lunch, brb17:36
acolesjoeljwright: note, you need to have some X-Object-Meta-Blah=blah with the PUT for there to be any 'X-Object-Transient-Sysmeta-Crypto-Meta expected17:36
*** vinaypotluri has left #openstack-swift17:36
acolesjoeljwright: are you using EC policy or replica?17:37
joeljwrightacoles: replica17:38
claygwell what's wrong with patch 341663 !?17:38
patchbothttps://review.openstack.org/#/c/341663/ - swift - Call out transient sysmeta in swift-object-info17:38
acolesclayg: us its whats wrong, we're so bad at reviewing stuff17:38
joeljwrightacoles: but it's not consistent either, we've managed to get 3 different etags for a single object17:39
joeljwrightacoles: it's hard to identify a single 'problem' object17:39
claygacoles: I think we're bad at finding patches that should merge17:39
claygacoles: that one looks like it should merge17:40
joeljwrightacoles: we think we've found one, then it behaves consistently and correctly for ages :(17:42
acolesjoeljwright: single object or same content?17:44
acolesi.e. same path or same content?17:45
*** dmorita has joined #openstack-swift17:45
joeljwrightacoles: same path17:46
acolesclayg: thanks for introducing some sanity to reclaim_age conf, patch 374419, always drive me crazy17:46
patchbothttps://review.openstack.org/#/c/374419/ - swift - Move documented reclaim_age option to correct loca...17:46
joeljwrightacoles: same path, same content17:47
joeljwright3 different etags17:47
*** dmorita has quit IRC17:47
joeljwrightbut mostly the correct one17:47
*** dmorita has joined #openstack-swift17:47
acolesso what's not good enough about "mostly" :P17:47
acoles3 ?!?17:47
acoles2 makes sense17:48
claygacoles: dunno how i missed the doc build thing - i normally like to have my autodoc going when I'm editing in that tree just cause i'm curious - very strange17:48
acolesjoeljwright: unless of course you also have some proxies upgraded and others not17:48
acolesjoeljwright: but did you say you're hitting just one proxy?17:48
claygis this something with made up etags on *LO's?17:49
acolesjoeljwright: same path, same content, same PUT request? or repeating same request gives etag variations?17:50
acolesclayg: rst tables are pretty brittle it seems17:51
*** mingyu has joined #openstack-swift17:51
acolesclayg: I learnt that the hard way so I am alert to changes in those tables17:51
claygacoles: yeah i learned that one time too - good catch17:52
claygacoles: reviews work!17:52
claygi'm mad at encryption right now - i have both mw in my pipeline; disable_encryption = false (worst double negative) - but i'm not getting encrypted stuff!17:53
claygis there another step i'm forgetting?  my "modified pipeline" log lines show they mw is in there...17:54
claygacpahpcahp!  i just rebuilt everything - werx now17:54
acolesjoeljwright: assume you put the same content multiple times - every path gets encrypted differently, and every unique request to same path gets encrypted differently, hence the Etag of the data on disk is different in every case. And old object server will send that Etag to container and that would explain varying etags in listings. Upgraded object servers should send the encrypted etag of the plaintext which should be co17:55
acolesnstant.17:55
joeljwrightacoles: same content, same path - only one PUT (keep etag) then just HEADs17:55
joeljwrightacoles: result is sometimes inconsistent, but with no pattern we have been able to identify17:56
acolesjoeljwright: huh. I was working off David's pastebin from earlier, thought you were seeing the issue with container GETs http://paste.openstack.org/show/591755/17:57
acolesso object HEADs give back varying Etags?17:57
claygok, i'ma assume you guys got this and go look at liberasurecode releases17:58
joeljwrightacoles: yes, we've been trying to refine the problem since David's pastebin17:58
acolesjoeljwright: so like clayg mentioned, asre these slo's or just plain old objects?17:58
*** McMurlock1 has quit IRC17:59
*** jordanP has quit IRC17:59
joeljwrightacoles, clayg: just simple objects17:59
joeljwrightacoles, clayg: but we're unable to reproduce this consistently18:00
joeljwrightacoles: yeah, the 3 really confused me18:00
joeljwrightacoles: it was this morning, but we're pretty sure we didn't overwrite the object at any point18:02
*** _david_cole_soho has joined #openstack-swift18:04
claygpatch 405450 looks really close to merged to me - it's mostly just a logging and test change - me, acoles and kota seem on board - i'd like it landed because it's a fixup for another change that i'm packaging18:04
patchbothttps://review.openstack.org/#/c/405450/ - swift - Fixups for ghost listing fix18:04
acolesjoeljwright: any chance the HEADs use different proxies and one wasn't upgraded?18:07
joeljwrightacoles: sadly not18:07
joeljwrightI forced the request through individual proxies multiple times18:08
acoleshmm. ok well if you were able to do that read_metadata on one of these objects and capture the on disk metadata of all three replicas that would be very interesting18:09
joeljwrightI'll do my best18:09
*** StraubTW has quit IRC18:10
*** StraubTW has joined #openstack-swift18:10
timburkegood morning18:11
*** silor1 has joined #openstack-swift18:14
claygtimburke: good morning!18:20
openstackgerritClay Gerrard proposed openstack/liberasurecode: 1.4.0 release  https://review.openstack.org/40825718:21
*** silor1 has quit IRC18:25
*** zul_ has joined #openstack-swift18:31
* acoles away til Monday18:33
*** tqtran has joined #openstack-swift18:33
*** acoles is now known as acoles_18:34
openstackgerritClay Gerrard proposed openstack/pyeclib: release 1.4.0  https://review.openstack.org/40828018:36
*** clu_ has joined #openstack-swift18:39
openstackgerritClay Gerrard proposed openstack/pyeclib: release 1.4.0  https://review.openstack.org/40828018:39
claygok, I think the liberasurecode/pyeclib release is ready to go (cc: timburke tdasilva notmyname )18:41
claygplease let me know if that is blocked or looks like it won't happen this afternoon if there is anything I can do18:41
claygalso, gah, the error logs please - patch 40545018:42
patchbothttps://review.openstack.org/#/c/405450/ - swift - Fixups for ghost listing fix18:42
timburkejoeljwright: maybe i missed it; what do you see when you do swift-object-info for all of the replicas?18:42
timburkeand it works *fine* without my patch, right? it just lumps all that stuff under "Other Metadata"18:43
timburkeclayg: tdasilva: i'm more and more partial toward merging the get_Version thing, at least for liberasurecode. that shit works, we can totally get a pyeclib patch in building against distro packages, it's gonna be great18:44
timburke(whether we get that patch in ahead of the pyeclib release is a separate matter)18:45
*** zul_ has quit IRC18:46
*** zul_ has joined #openstack-swift18:48
*** siva_krish has quit IRC18:53
*** ChubYann has joined #openstack-swift18:59
tdasilvatimburke: whether we get that patch in ahead of the pyeclib release is *THE* matter19:03
tdasilvaclayg: ^19:03
tdasilvatimburke: or are you saying merge the libec patch ahead of the libec release19:03
tdasilvaand then it might be ok to wait for the pyeclib patch for after the pyeclib release19:04
tdasilva?19:04
timburketdasilva: the latter. if we end up wanting to do a pyeclib 1.4.1 or something to pick up better version handling, w/e19:04
timburkeor i could finish putting out a separate small fire, and help get the pyeclib patch in shape to merge today. both are good options.19:06
timburkebut i see no reason that the libec code can't merge as is19:06
*** hseipp has joined #openstack-swift19:22
*** joeljwright has quit IRC19:25
claygpdardeau: ntata: do you know Sachin Patil - i'm not sure why i associate him with osic - he's doing a bang up job on patch 40601219:33
patchbothttps://review.openstack.org/#/c/406012/ - swift - Fix swift-get-nodes arg parsing for missing ring19:33
claygI really hope he sticks with it - it's turning into a great cleanup effort!  so helpful!19:34
tdasilvaclayg: he is from RH19:34
claygpdardeau: ntata: NM!19:34
tdasilvabut i don't know him personally19:34
claygtdasilva: hrm... wonder what group he's with - or if he's on irc?19:34
tdasilvapsachin i thik19:35
tdasilvathink19:35
tdasilvabut he is India, so different TZ19:35
claygtimburke: i disagree that it matters at all if the version code thing is added to liberasure in 1.4.019:37
*** mingyu has quit IRC19:37
claygtimburke: IMHO the whole situation with liberasurecode and pyeclib dependencies and gate tests is %^&*ed and I don't think having a gate job that builds against liberasurecode master so we can skip tests that run against distro pacakges is the right target19:37
timburkeclayg: one fewer things that need to be released after landing the pyeclib change to actually use it19:37
claygtimburke: I *do* agree that the liberasurecode function can get merged without breaking the pyeclib gate - but I do not agree that provides any value to anyone because pyeclib can't use it because our whole situation is screwed19:38
claygmeanwhile - i really need to shipt isa_l_rs_cauchy and i have few braincells nerves to spare for how to un^&* liberasurecode and pyeclib19:39
timburkeclayg: pyeclib can *totally* use it. working on updating kota_'s patch now19:39
timburkeand that can still be *after* a 1.4.0 release19:39
claygbut I appreciate your thinking about it - not trying to deminish that effort - you are a rockstart19:39
clayg... but I disagree that this change should hold up liberasurecode 1.4.0 - it's more complicated than that - if we have to cut a 1.4.1 next week I don't care at all19:39
claygproduction production production19:39
timburkewhat was that earlier about the trouble being finding code that should merge?19:40
claygtimburke: ok i don't understand how you can make unitests that are using distro packaged .so's that don't include the function you want to expose exercise the *unexposed in that version* function - but i'm sure you can educate me if we had a few days to kill19:41
openstackgerritMerged openstack/swift: Call out transient sysmeta in swift-object-info  https://review.openstack.org/34166319:42
claygtimburke: exactly - in this case it's not obvious to me that it should merge!  I obviously don't care if it's obvious to tdasilva that it *should* - as long as 1.4.0 is not blocked any longer than it has to be19:42
timburkeclayg: oh yeah, the unit tests are gonna be worthless. it's going to rely *entirely* on people actually testing against a more-recent liberasurecode19:42
clayggvlop[oftuyiuop-oiugyhol19:42
patchbotError: Missing "]".  You may want to quote your arguments with double quotes in order to prevent extra brackets from being evaluated as nested commands.19:42
clayg[;l'jbkhj19:42
patchbotError: Missing "]".  You may want to quote your arguments with double quotes in order to prevent extra brackets from being evaluated as nested commands.19:42
*** rcernin has quit IRC19:43
claygtimburke: ok, fair to say that we disagree on both the correctness and value of this approach - quite possible i'm wrong19:43
timburkedo you want to have code that works or tests that are meaningful? if we wait for the tests to be meaningful, you'll forever have this chicken-and-egg problem19:43
claygtimburke: but I'm acctually choosing not pass judgement since I don't know enough to evaluate the correctness - frustrated it's being raised as a blocker against 1.4.0 tho :'(19:44
timburke"no point in merging libec change, pyeclib can't use it" "no point in even *thinking* about pyeclib change; we'll never be able to test it"19:44
timburkei don't think it's a blocker, i think it's a nice-to-have that already has a +219:45
claygtimburke: i *just* want to talk about this after I get out my release :'(19:45
tdasilvatimburke, clayg so i just looked at the libec change19:45
claygi also think that merging pyeclib into liberasure code is what we should be doing19:45
claygyay - great!19:45
tdasilvait looks straight forward and I tested as timburke suggested19:45
tdasilvalooks great!19:45
claygtdasilva: awesome!  go guys!19:45
tdasilvai just don't know if i'm missing something19:45
tdasilvabut I'm ready to +2 +A19:46
claygtdasilva: did you figure out how it's going to be used in pyeclib!?19:46
tdasilvaand get this over with19:46
claygtdasilva: good call!19:46
tdasilvano, not thinking about that right now19:46
claygROFL19:46
tdasilvajust want to merge this and move on19:46
tdasilvaclayg, timburke thoughts?19:47
timburkei'm totally on board19:48
* clayg hugs timburke 19:48
claygthanks tdasilva !19:48
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873619:54
openstackgerritMerged openstack/liberasurecode: Add get_version functionality to liberasurecode lib  https://review.openstack.org/40592619:54
*** mingyu has joined #openstack-swift19:55
openstackgerritThiago da Silva proposed openstack/liberasurecode: 1.4.0 release  https://review.openstack.org/40825719:57
*** rcernin has joined #openstack-swift19:58
tdasilvaclayg, timburke: can you +2 p 408257 again?19:58
patchbothttps://review.openstack.org/#/c/408257/ - liberasurecode - 1.4.0 release19:58
tdasilvatimburke: also did you have a chance to look at p 408280 ?19:58
patchbothttps://review.openstack.org/#/c/408280/ - pyeclib - release 1.4.019:58
timburkei've not looked at either yet; sorry :-(19:59
timburkewill do today19:59
*** mingyu has quit IRC20:00
*** mingyu has joined #openstack-swift20:04
*** jamielennox|away is now known as jamielennox20:13
claygtdasilva: thanks!20:15
openstackgerritTim Burke proposed openstack/pyeclib: WIP: Change the version reference  https://review.openstack.org/40592920:17
timburkekota_: ^^^ hope you don't mind20:17
openstackgerritThiago da Silva proposed openstack/pyeclib: release 1.4.0  https://review.openstack.org/40828020:20
timburke"Verified+1" see that, we can totally get this through the gate when we want20:21
claygtdasilva: gah!  nice catch :P20:21
*** mingyu has quit IRC20:21
claygtimburke: :)20:23
tdasilvanotmyname: around?20:26
claygtdasilva: I think he's traveling (SLC?  OpenStack Midwest?) - so he may be spotty20:27
tdasilvaah ok!20:27
tdasilvacool, np20:27
timburke"mountain west." different.20:27
claygi mostly piece it together from twitter - i have no idea - he said something at some point in this channel this am I think?20:27
claygtimburke: ah, thank you -> https://twitter.com/notmyname/status/80650821461541273620:28
*** d0ugal has quit IRC20:29
openstackgerritMerged openstack/liberasurecode: 1.4.0 release  https://review.openstack.org/40825720:31
*** zul_ has quit IRC20:33
clayg^ wooooooo!20:33
*** d0ugal has joined #openstack-swift20:35
openstackgerritMerged openstack/pyeclib: release 1.4.0  https://review.openstack.org/40828020:47
*** rcernin has quit IRC20:51
*** rcernin has joined #openstack-swift20:51
zaitcevwaaah, no 1.3.220:52
tdasilvazaitcev: decided to go with 1.4.0 since we added support for a new EC lib20:55
zaitcevwhich one is that?20:55
zaitcevI thought both shss and isa-l were in 1.3.120:56
timburkezaitcev: isa-l cauchy; 1.3.1 has isa-l vand20:57
zaitcevdoes it allow for more parities?20:58
zaitcev(than 4)20:58
timburkeyup :-) at least, that's what clayg and kota_ keep telling me20:58
claygzaitcev: yeah it do!  isa_l_rs_cauchy is where it's *at*21:02
*** rcernin has quit IRC21:09
tdasilvaclayg: release tags have been pushed21:09
*** joeljwright has joined #openstack-swift21:10
*** ChanServ sets mode: +v joeljwright21:10
*** chlong has quit IRC21:10
*** rcernin has joined #openstack-swift21:12
claygtdasilva: yeah it has!21:13
clayghttps://github.com/openstack/liberasurecode/releases21:13
*** siva_krish has joined #openstack-swift21:14
tdasilvamy changes to pyeclib did not work as expected https://pypi.python.org/pypi/PyECLib/1.4.0 :(21:14
*** siva_krish has quit IRC21:24
*** chsc has quit IRC21:25
claygtdasilva: my pypi username is clayg - if you want to add me on the project and I can poke around?21:27
*** dmorita has quit IRC21:27
claygtdasilva: maybe only kgreen has the ability to change that particular piece of metadata?21:28
claygtdasilva: as timburke pointed out - it was kind of a log shot that the metadata would help21:28
* clayg shrugs21:28
*** dmorita has joined #openstack-swift21:28
*** mvk has joined #openstack-swift21:33
*** StraubTW has quit IRC21:33
*** Jeffrey4l has quit IRC21:35
*** Jeffrey4l has joined #openstack-swift21:36
tdasilvaclayg: added you the project21:37
*** vint_bra has quit IRC21:40
*** sams-gleb has quit IRC21:47
*** sams-gleb has joined #openstack-swift21:47
*** sams-gleb has quit IRC21:52
openstackgerritMerged openstack/swift: Use assertGreater(len(x), 0) instead of assertTrue(len(x) > 0)  https://review.openstack.org/40848821:52
*** hseipp has quit IRC21:54
*** hseipp has joined #openstack-swift21:55
claygtdasilva: yeah i couldnt see anything - i'm in #pypa see if anyone there knows how it works22:00
tdasilvaclayg: yeah, looks like they changed their web interface, so it's not very clear22:01
claygzaitcev: timburke: tdasilva: notmyname: torgomatic: making good progress on packages for liberasure/pyeclib now - only hold out for swift is patch #40545022:02
patchbothttps://review.openstack.org/#/c/405450/ - swift - Fixups for ghost listing fix22:02
claygI would love to see that go in before my updaters loose their mind on async pendings22:02
zaitcevclayg: wait, what packages22:03
zaitcevclayg: I've already started Fedora build for 1.4.0 that I got with  git archive -o ../liberasurecode-1.4.0.tar.gz --prefix=liberasurecode-1.4.0/ 1.4.022:03
claygpyeclib liberasurecode 1.4.0 packages!22:04
claygzaitcev: nice sounds like we're on the right track22:04
zaitcevok22:04
claygzaitcev: after i finish with pyeclib & liberasurecode i'm *also* building packages for swift with a bunch of >2.11 bug fixes that have gone in22:04
tdasilvazaitcev: should i ping apevec about centos packages?22:05
claygi'm sure notmyname will be thinking about cutting a swift 2.12 pretty soon for the same reason22:05
zaitcevtdasilva: too soon22:05
claygtdasilva: is that how that works?  yeah we should send it to liberasure/pyeclib-annouce or something?22:05
zaitcevclayg: I think CentOS use DLRN, which is a script that automatically builds whatever is the latest tag.22:06
claygzaitcev: yeah now *that's* what i'm talking about!22:06
tdasilvazaitcev: not sure it's automatic? for the last time, i had to ask apevec to kickoff a build, sounded like it was a more manual process?22:07
zaitcevtdasilva: well, maybe they realized that it was wasteful22:07
tdasilvahehehe22:07
tdasilvamaybe i'm looking at the wrong thing22:07
tdasilvai've been looking at this: https://cbs.centos.org/koji/packageinfo?packageID=64322:08
zaitcevlooks fine to me. I was confused about what was good in 1.3.x cycle, so I skipped it22:10
zaitcevwe had this issue about some more silly messages flooding with 1.3.0 or such22:10
claygi think 1.3.1 included a fix for that maybe?22:12
zaitcevmaybe22:12
zaitcevBut I have good hopes for 1.4.0, so let's go with that.22:12
claygyeah i think i packaged 1.3.1 *for* that fix - oh maybe that was to make isa_l_rs_vand return an error instead of garbage on erase lists with parity > 422:12
claygzaitcev: i kid you not - 1.4.0 is the best liberasurecode/pyeclib evar22:13
tdasilvalol22:13
claygi have it on good authority liberasurecode even has a function that can tell you waht it's version is22:13
clayg;)22:13
zaitcevnot like anyone calls it though22:13
* clayg snickers22:13
tdasilvaROFL22:14
claygi'm so so so just kidding - it was for a laugh - god i'm such a jerk :'(22:14
tdasilvatimburke: i'm a little pessimistic about that prefix tempurl api22:15
tdasilvare path 27404822:15
tdasilvapatch 27404822:15
patchbothttps://review.openstack.org/#/c/274048/ - swift - tempurls with a prefix-based scope22:15
timburketdasilva: the implementation, or the whole premise?22:16
tdasilvait seems awkward to have to provide the patch to a whole object like https://swift-cluster.example.com/v1/my_account/container/my_prefix/object only to then say pprefix temp_url_prefix=my_prefix22:16
tdasilvas/patch/path22:18
tdasilvacan't spell today22:18
*** jamielennox is now known as jamielennox|away22:29
mattoliveraumorning, I probably wont be in much today. At the airport, flying to Sydney for a day in the Sydney office and Christmas party.22:31
tdasilvatimburke: nevermind, i understand better now on second read22:33
*** jamielennox|away is now known as jamielennox22:34
*** dmorita has quit IRC22:36
*** dmorita has joined #openstack-swift22:37
timburkehrm. although you still can't create SLOs...22:39
*** hseipp has quit IRC22:40
*** hseipp has joined #openstack-swift22:40
claygmattoliverau: party time!22:40
mattoliverauyou know it!22:40
*** cschwede has quit IRC22:43
*** tmoreira has quit IRC22:44
*** joeljwright has quit IRC22:52
*** david-lyle_ has joined #openstack-swift23:05
*** david-lyle has quit IRC23:07
*** rcernin has quit IRC23:11
notmynamehello23:18
notmynameonline at the airport (and flight was just delayed)23:18
notmynameclayg: tdasilva23:18
claygnotmyname: afaik everything is awesome tdasilva and timburke are hero - zaitcev and I are building packages23:19
notmynameawesome!23:19
notmynametdasilva: did you pushed the signed tags?23:19
*** chsc has joined #openstack-swift23:21
claygwhen I fetch them they sure *look* signed - PGP some such - release tarballs were published, pypi was updated, i think tdasilva knows what he's doing23:21
notmynameyay23:21
claygnice23:21
notmynameoh, sorry, I meant that in "was it tdasilva who did it" instead of "did tdasilva know what to do"23:21
notmynamecool, yeah, my local fetch finally finished. I see the tags23:22
claygoh interesting... i have know idea if tdasilva had to do something by hand or magic - if anything good happened there i'm pretty sure it was tdasilva23:22
claygas opposed to kota_ or timburke (who are also both high on my list of blame when something good happens related to ec libararies)23:23
clayg*praise23:23
notmynameindeed23:26
notmynameclayg: the "magic" for a release (of non-governance openstack projects like pyeclib and libec) is simply to make a signed tag and push it to the gerrit remote23:26
notmynamefor governance projects, you have to create/update some yaml in the openstack-releases repo and get that +A'd by the release team23:27
claygnotmyname: gtk23:27
*** rcernin has joined #openstack-swift23:33
*** david-lyle_ is now known as david-lyle23:35
*** kei_yama has joined #openstack-swift23:37
claygEVERYTHING IS AWESOME!23:48
*** klamath has quit IRC23:49
timburkebest release yet23:49
openstackgerritMerged openstack/swift: line wrap overview_expiring_objects.rst  https://review.openstack.org/40871723:49
*** rcernin has quit IRC23:49
*** jamielennox is now known as jamielennox|away23:49
openstackgerritMerged openstack/swift: adding unit tests for if-none-match fix  https://review.openstack.org/40104423:50
notmynametimburke: clayg: tdasilva: is there something pressing I should be looking at while sitting here?23:58
notmyname(if not, I'll be working on the 2.12.0 release notes)23:58

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