Wednesday, 2015-04-15

*** zhill has quit IRC00:00
*** noye has quit IRC00:02
*** wshao has quit IRC00:13
*** petertr7 has quit IRC00:21
claygtorgomatic: I'm curious what you might think about adding some TBD sections the symlink spec?  Like "we acknowledge this should be discussed in the spec - but rational minds may hold differring opinions - so we explictly do not attempt to resolve them in this revision of the spec in order to find a minimal set of concensus that we can merge" - or something like that?00:21
*** jkugel has joined #openstack-swift00:21
claygacoles_away: oh crap - i guess we should get on reviewing fast-POST?!00:22
openstackgerritClay Gerrard proposed openstack/swift: Better storage server eventlet logging  https://review.openstack.org/17362200:25
hogood morning!00:31
*** dmorita has joined #openstack-swift00:35
mattoliverauho: morning00:40
homattoliverau: morning!00:42
mattoliverauclayg: specs are suppose to be alive, have many iterations and exist so they can be discussed.. So in my opinion TBD's are fine.. So long as there are none in the final (completed) version. In fact TBD can be used as good points to discuss at summit (my 2 cents)00:44
*** thumpba has quit IRC00:47
*** peluse has quit IRC00:53
*** kota_ has joined #openstack-swift00:57
kota_morning00:58
hokota_: good morning!00:59
*** fanyaohong has quit IRC00:59
kota_ho: good morning :)00:59
mattoliveraukota_: morning01:01
kota_mattoliverau: morning :)01:02
kota_yeah, I'm happy to see at commit log that the EC staff has been merged to the master branch :D01:06
kota_great work!01:06
openstackgerritMerged openstack/swift: Fix broken test_policy_IO_override test  https://review.openstack.org/17159301:18
openstackgerritMerged openstack/swift: Add lowest option to swift-recon disk usage output  https://review.openstack.org/16723601:18
openstackgerritMerged openstack/swift: Add test for swift_recon.disk_usage  https://review.openstack.org/17275201:22
openstackgerritMerged openstack/swift: Check if REST API version is valid  https://review.openstack.org/16850901:22
openstackgerritMerged openstack/swift: 2.3.0 authors and changelog updates  https://review.openstack.org/17257301:22
openstackgerritMerged openstack/swift: fixup random test failure  https://review.openstack.org/17357901:22
*** esker has joined #openstack-swift01:24
*** MVenesio has quit IRC01:31
notmynameeverything has merged!01:31
notmynameSHA for the RC, and will be the 2.3.0 release unless anything major is found, is 5ef2e9ec00b1498fb411fc918b71ae9c50b1308f (ie current HEAD of master)01:33
notmynamemaster is now unfrozen01:33
*** ChanServ changes topic to "Review Dashboard: http://goo.gl/vysJqI | Summary Dashboard: http://goo.gl/2By1qv | Summit scheduling: https://etherpad.openstack.org/p/liberty-swift-summit-topics | Logs: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/"01:33
notmynamegreat work, everyone!01:33
notmynamethanks01:33
* notmyname logs off for the night01:37
*** gyee has quit IRC02:02
*** occupant has quit IRC02:06
*** Guest__ has joined #openstack-swift02:12
*** km has joined #openstack-swift02:21
*** Guest__ has quit IRC02:24
*** Guest__ has joined #openstack-swift02:24
*** esker has quit IRC02:57
*** esker has joined #openstack-swift02:57
*** Guest__ has quit IRC02:59
zaitcevWhat a day03:00
zaitcevPicking up pieces from the EC merge, and just got PyECLib building now, barely.03:00
zaitcevOSX and Ubuntu people forgot to support /usr/lib6403:01
*** jrichli has quit IRC03:09
mattoliverauzaitcev: I guess I need to get liberasurecode compiling and working on OSX now if I want to do any work on it, did you have any trouble doing that? (I guess I shold just go try)03:11
zaitcevmattoliverau: I'm on Fedora, so no, I didn't. Only made an RPM for Fedora review - https://bugzilla.redhat.com/show_bug.cgi?id=120869503:15
openstackbugzilla.redhat.com bug 1208695 in Package Review "Review Request: liberasurecode - Erasure Code API library written in C with pluggable backends" [Medium,Assigned] - Assigned to ppisar03:16
mattoliverauzaitcev: fair enough, nice work! Maybe I just need to convince work to give me dev laptop I can just run linux on, then I don't have to worry about OSX nuances ;)03:19
zaitcevI gave up on work laptops. We have Lenovos now and I'm not friendly with the left Ctrl inside the Fn. My pinkie hurts on that.03:23
mattoliveraulol03:28
*** km has quit IRC03:40
zaitcevERROR   0001: file '/usr/lib64/python2.7/site-packages/pyeclib_c.so' contains a standard rpath '/usr/lib' in [/usr/lib/python2.7/site-packages:/usr/lib:/lib:/usr/local/lib:src/c/liberasurecode-1.0.6/src/.libs]03:54
zaitcevKevin, Kevin03:54
*** kota_ has quit IRC04:04
*** krtaylor has quit IRC04:07
*** krtaylor has joined #openstack-swift04:10
*** peluse has joined #openstack-swift04:13
*** ChanServ sets mode: +v peluse04:13
*** zaitcev has quit IRC04:24
*** SkyRocknRoll has joined #openstack-swift05:23
*** resker has joined #openstack-swift05:32
*** esker has quit IRC05:35
*** kota_ has joined #openstack-swift05:48
*** ppai has joined #openstack-swift05:51
*** bkopilov has quit IRC05:53
*** bkopilov has joined #openstack-swift05:59
*** silor has joined #openstack-swift06:07
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Imported Translations from Transifex  https://review.openstack.org/17368706:07
*** ppai has quit IRC06:07
*** ppai has joined #openstack-swift06:08
*** SkyRocknRoll has quit IRC06:18
*** SkyRocknRoll has joined #openstack-swift06:21
*** bkopilov has quit IRC06:24
openstackgerritKota Tsuyuzaki proposed openstack/swift: Small minor refactor on ec diskfile  https://review.openstack.org/17369106:25
openstackgerritSamuel Merritt proposed openstack/swift-specs: Spec for symlinks in Swift  https://review.openstack.org/17360906:28
cschwedeGood Morning!06:31
openstackgerritChristian Schwede proposed openstack/swift: More tests for swift recon  https://review.openstack.org/17326606:37
kota_cschwede: good morning, Christian!06:37
mattoliveraucschwede: morning06:38
cschwedeHello Kota, Hello Matthew!06:38
*** SkyRocknRoll has quit IRC06:39
*** bkopilov has joined #openstack-swift06:50
*** km has joined #openstack-swift06:50
*** bkopilov has quit IRC06:56
*** peluse has quit IRC06:56
*** joeljwright has joined #openstack-swift06:56
*** mmcardle has joined #openstack-swift06:58
*** ho has quit IRC07:00
*** nshaikh has joined #openstack-swift07:00
*** jeblair has quit IRC07:05
*** peluse has joined #openstack-swift07:06
*** peluse has quit IRC07:06
*** jeblair has joined #openstack-swift07:07
*** bkopilov has joined #openstack-swift07:11
*** jordanP has joined #openstack-swift07:13
*** jistr has joined #openstack-swift07:24
*** SkyRocknRoll has joined #openstack-swift07:26
*** krykowski has joined #openstack-swift07:33
*** chlong has quit IRC07:35
*** ppai has quit IRC07:35
*** bkopilov has quit IRC07:45
*** ppai has joined #openstack-swift07:49
*** bkopilov has joined #openstack-swift07:49
openstackgerritAndreas Jaeger proposed openstack/swift: Fix untranslatable string  https://review.openstack.org/17371307:52
*** bkopilov has quit IRC07:54
*** bkopilov has joined #openstack-swift07:54
*** geaaru has joined #openstack-swift07:55
*** peluse has joined #openstack-swift07:55
*** ktsuyuzaki has joined #openstack-swift07:58
*** ktsuyuzaki has quit IRC07:58
*** kota_ has quit IRC07:59
*** peluse has quit IRC08:01
*** bkopilov has quit IRC08:10
*** bkopilov has joined #openstack-swift08:17
*** ujjain has joined #openstack-swift08:20
*** km has quit IRC08:35
openstackgerritKamil Rykowski proposed openstack/swift: More user-friendly output for object metadata  https://review.openstack.org/16401908:37
*** bkopilov has quit IRC08:39
*** bkopilov has joined #openstack-swift08:45
*** AliRezaTaleghani has joined #openstack-swift08:46
AliRezaTaleghaniI would like to add some specific feature on my swift cluster, the case is as follow:08:47
AliRezaTaleghaniI will push some large acale pic on swift after some while one other will try to download that pic name08:48
AliRezaTaleghanibut will smaller size08:48
AliRezaTaleghaniex: original file name is "swift-obj-image_1280x1024.png"08:49
*** acoles_away is now known as acoles08:49
AliRezaTaleghanirequested file name is "swift-obj-image_640x480.png"08:49
AliRezaTaleghaniis such a case I would like to have a middleware to convert the object on the fly and deliver it08:50
AliRezaTaleghaniI'm new to swift and don't have more exprience with python but I'm looking for point to start work on08:51
*** bkopilov has quit IRC08:51
AliRezaTaleghaniplease let me know if I am going wrong with middleware for this porpose08:51
AliRezaTaleghaniplz08:51
*** bkopilov has joined #openstack-swift08:52
*** ppai has quit IRC08:53
ahaleyeah sounds like you need to write some middleware, I did something similar a long time ago for a very old version of swift, https://github.com/ahale/swascii/blob/master/swascii/middleware.py08:53
ahalethats kind amessy and probably needs updated for newer swift, but might help maybe, i dunno08:54
AliRezaTaleghaniahale: tnx i will chk it r-now08:57
*** krtaylor has quit IRC08:57
*** bkopilov has quit IRC08:57
ahalenps, I think I started by copying a real swift middleware and hacking at it until it did what I wanted, they're pretty straightforward though08:59
AliRezaTaleghaniahale: :-) 1+ so will start alike09:01
ahale:)09:02
*** krtaylor has joined #openstack-swift09:04
*** ppai has joined #openstack-swift09:05
*** dmorita has quit IRC09:07
*** nshaikh has left #openstack-swift09:31
*** okdas has joined #openstack-swift09:44
*** ppai has quit IRC09:48
*** jamielennox is now known as jamielennox|away09:52
*** nshaikh has joined #openstack-swift09:59
*** ppai has joined #openstack-swift10:01
*** theanalyst has quit IRC10:06
*** theanalyst has joined #openstack-swift10:09
*** kota_ has joined #openstack-swift10:18
openstackgerritAlistair Coles proposed openstack/swift: Fix untranslatable string  https://review.openstack.org/17371310:32
*** AliRezaTaleghani has left #openstack-swift10:51
openstackgerritLorcan Browne proposed openstack/swift: Update swift-recon doc with more options  https://review.openstack.org/17376710:55
*** ujjain has quit IRC10:59
*** bkopilov has joined #openstack-swift11:07
*** ppai has quit IRC11:10
*** acoles is now known as acoles_away11:13
*** ppai has joined #openstack-swift11:22
*** ppai has quit IRC11:45
*** ppai has joined #openstack-swift11:46
*** aix has quit IRC11:50
*** dencaval has joined #openstack-swift11:51
*** mmcardle has quit IRC11:56
*** AJaeger has joined #openstack-swift12:00
AJaegerThanks a lot swift team for a really speed review and approval of  https://review.openstack.org/173713 !12:00
*** MVenesio has joined #openstack-swift12:13
*** ppai has quit IRC12:21
*** aix has joined #openstack-swift12:28
*** jkugel has quit IRC12:30
*** SkyRocknRoll has quit IRC12:33
*** mmcardle has joined #openstack-swift12:36
*** nshaikh has left #openstack-swift12:40
*** acoles_away is now known as acoles12:40
openstackgerritMerged openstack/swift: More tests for swift recon  https://review.openstack.org/17326612:46
*** SkyRocknRoll has joined #openstack-swift12:47
openstackgerritMerged openstack/swift: Fix untranslatable string  https://review.openstack.org/17371312:47
*** kota_ has quit IRC12:49
*** annegentle has joined #openstack-swift12:50
openstackgerritLorcan Browne proposed openstack/swift: Update swift-recon doc with more options  https://review.openstack.org/17376712:53
*** acoles is now known as acoles_away12:56
*** AJaeger has left #openstack-swift12:56
*** resker has quit IRC12:58
*** peluse_ has joined #openstack-swift13:01
*** proteusguy has quit IRC13:03
*** peluse_ is now known as peluse13:06
*** ChanServ sets mode: +v peluse13:06
*** acoles_away is now known as acoles13:12
*** MVenesio has quit IRC13:23
*** david-lyle has quit IRC13:24
*** jkugel has joined #openstack-swift13:24
*** SkyRocknRoll has quit IRC13:35
*** ozialien has joined #openstack-swift13:39
*** proteusguy has joined #openstack-swift13:41
*** Gue______ has joined #openstack-swift13:50
*** SkyRocknRoll has joined #openstack-swift13:51
*** noye has joined #openstack-swift13:53
peluseacoles, thanks for the trello updates.14:01
acolespeluse: np14:02
peluseall, trello still has misc EC todo items that weren't considered required for beta and is now up to date at https://trello.com/b/LlvIFIQs/swift-erasure-codes14:02
pelusekota, thanks for confirming that pyeclib item also!14:03
*** esker has joined #openstack-swift14:06
*** zaitcev has joined #openstack-swift14:07
*** ChanServ sets mode: +v zaitcev14:07
*** ujjain has joined #openstack-swift14:08
*** SkyRocknRoll has quit IRC14:15
*** ozialien has quit IRC14:17
*** ozialien has joined #openstack-swift14:19
*** ozialien has quit IRC14:26
*** SkyRocknRoll has joined #openstack-swift14:31
*** Fin1te has joined #openstack-swift14:31
*** Gue______ has quit IRC14:36
*** ahale has left #openstack-swift14:42
*** jrichli has joined #openstack-swift14:50
*** Fin1te has quit IRC14:53
*** annegentle has quit IRC14:54
*** jordanP has quit IRC14:55
*** Gu_______ has joined #openstack-swift15:01
notmynamegood morning15:01
*** jdaggett has left #openstack-swift15:02
acolesnotmyname: good morning. enjoyed your podcast.15:02
notmynameacoles: thanks! (I'm glad I didn't do something terrible and forget your name!)15:03
acolesnotmyname: heh.15:03
notmynameI was walking around the world in my head, and was like "I'm missing someone in EU..."15:03
acolesnotmyname: well you *nearly* did :D15:03
notmynamelol15:03
notmynameI know. I feel bad ;-)15:03
acolesdon't!15:03
notmyname:-)15:04
acolesyou were very gracious and complimentary about the whole community which was great15:04
notmynamea fraction of what is deserved15:04
pelusemorning15:05
pelusehey, where's the pdcast link?15:05
notmynamecool. looks like we have an upstream 2.3.0rc1 tag15:05
notmynamepeluse: https://www.youtube.com/watch?v=1ORJKia1pQs15:05
notmynameso today I'll be taking it easy. team meeting today will be "good work on EC. let's talk summit scheduling"15:08
notmynameacoles: cschwede: I wouldn't expect you to stay up late for it today :-)15:09
*** Gu_______ has quit IRC15:12
acolesnotmyname: will most likely be there15:13
notmynameok :-)15:13
*** SkyRocknRoll has quit IRC15:15
*** Gu_______ has joined #openstack-swift15:18
cschwedenotmyname: good morning! i’ll attend the meeting too15:21
cschwedenotmyname: acoles: yeah, i liked the praise for the community in the podcast too. well done!15:21
notmynamewell ok then ;-)15:21
*** ozialien has joined #openstack-swift15:26
peluseyup, great video!  oddly enough watching at 2x speed (for my ADD), John, you don't sound that much different :)15:36
acoleslol15:37
notmynameheh15:37
claygpeluse: how do you watch videos at 2x?  I hate video because it's so slow!15:41
pelusethe little cog wheel icon in the lower right15:41
peluseI watch everything at 2x :)15:41
claygpeluse: this changes *everything*15:42
peluseyeah, its like... almost efficient!15:42
pelusei wouldn't suggest watching your porn at 2x though :)15:42
claygnoted15:43
*** fanyaohong has joined #openstack-swift15:43
acolestry 0.5 speed, notmyname sounds totally spaced :D15:44
acolesnotmyname: you *have* to do a summit presentation in the style of 0.5 speed!15:44
acolesi can't stop laughing15:45
cschwedehaha, 0.5 is really funny!15:45
acolesnotmyname: thats how you will be speaking in 50 years time15:45
notmynamelol15:46
cschwedeacoles: if he’s talking with the same proficiency on storage technologies in 50 years everything is alright :)15:47
acolesits where he's talking about swift birds at 3.35 thats cracking me up15:47
openstackgerritMerged openstack/swift: Imported Translations from Transifex  https://review.openstack.org/17368715:48
cschwedeis this youtube 2x/0.5x thingy the modern version of „you have to play this record backwards to get the hidden message“?15:48
acolescschwede: :)15:49
peluseOMG, yeah the .5 is classic.  Sorry I brought all this up notmyname but you gotta love it!15:49
* peluse thinks it must be tought to be PTL sometimes....15:49
*** annegentle has joined #openstack-swift15:54
portantepeluse: I am sure notmyname could teach us how to be a good PTL15:54
*** jistr has quit IRC16:03
*** jistr has joined #openstack-swift16:04
*** krykowski has quit IRC16:06
peluseportante!  What's happenin man?16:08
pelusenotmyname, chances are good I can't get out of my noon conflict today so wrt scheduling sign me up for whatever...16:09
*** jistr has quit IRC16:09
notmynamepeluse: heh, it's fine. I think i want to go over some summit stuff. what's been proposed, some other ideas. just talk about it in general. not a "hand out tasks" thing16:10
pelusecool16:10
pelusegood call whoever is typing right now on the etherbad wrt EC topic for summit :)16:11
pelusenote that IBM has open sources storlet code now, the link is in the session proposal on the etherpad16:13
*** dosaboy has quit IRC16:13
pelusehttps://github.com/Open-I-Beam/swift-storlets16:14
notmynamethanks16:14
*** dosaboy has joined #openstack-swift16:14
openstackgerritMerged openstack/swift: Update swift-recon doc with more options  https://review.openstack.org/17376716:15
*** jistr has joined #openstack-swift16:15
*** annegentle has quit IRC16:16
*** jistr has quit IRC16:17
acolespeluse: could be me typing16:23
peluseyeah, that was my guess16:25
*** welldannit has quit IRC16:25
openstackgerritAlistair Coles proposed openstack/swift: Filter etag key from ssync replication-headers  https://review.openstack.org/17397316:34
acolespeluse: clayg: ^^ pls tell me i'm wrong about the reconstructor scenario16:35
*** EmilienM is now known as EmilienM|afk16:38
peluseacoles, on my way out the door but will check it out in a few hrs... thanks!16:39
*** Gu_______ has quit IRC16:45
*** peluse has quit IRC16:46
notmynamewho proposed the "test framework" session on the etherpad?16:47
zaitcev"the etherpad"?16:48
*** Gu_______ has joined #openstack-swift16:48
notmynamethe summit talks16:49
acolesnotmyname: i believe jrichli added it and she proposed me to lead it but i made it a tbd cos i'm a chicken16:49
notmynamezaitcev: sorry. WHY CAN"T YOU READ MY MIND?16:49
notmynamelol16:49
zaitcevNo, it makes complete sense. I'm just out of context.16:49
acolesnotmyname: not sure about a fishbowl on that topic, maybe working session???16:49
notmynamedepends on what you want to get out of it. as written, it might be ok as a fishbowl. but if it's more of "here's what we need to change and the next steps" then a working session might be better16:51
acolesnot sure if jrichli is about?16:51
notmynamejrichli: jrichli: jrichli:16:51
*** ozialien has quit IRC17:00
cschwedenotmyname: i put myself onto the „test framework“ topic17:01
notmynamethanks17:02
*** aix has quit IRC17:22
*** bkopilov has quit IRC17:26
*** bkopilov has joined #openstack-swift17:30
*** geaaru has quit IRC17:39
*** bkopilov has quit IRC17:39
*** bkopilov has joined #openstack-swift17:39
*** bkopilov has quit IRC17:44
*** erlon has joined #openstack-swift17:50
*** openstackstatus has quit IRC17:58
*** fanyaohong has quit IRC17:59
*** openstackstatus has joined #openstack-swift18:00
*** ChanServ sets mode: +v openstackstatus18:00
*** ozialien has joined #openstack-swift18:02
*** annegentle has joined #openstack-swift18:04
-openstackstatus- NOTICE: Gerrit has stopped emitting events so Zuul is not alerted to changes. We will restart Gerrit shortly to correct the problem.18:04
*** ChanServ changes topic to "Gerrit has stopped emitting events so Zuul is not alerted to changes. We will restart Gerrit shortly to correct the problem."18:04
*** MVenesio has joined #openstack-swift18:13
*** dosaboy has quit IRC18:13
*** dosaboy has joined #openstack-swift18:14
*** cutforth has joined #openstack-swift18:18
*** dosaboy has quit IRC18:20
*** Gu_______ has quit IRC18:20
*** dosaboy has joined #openstack-swift18:21
*** acoles is now known as acoles_away18:21
*** EmilienM|afk is now known as EmilienM18:22
*** dosaboy has quit IRC18:22
*** dosaboy has joined #openstack-swift18:24
*** dosaboy has quit IRC18:24
*** dosaboy has joined #openstack-swift18:24
*** ChanServ changes topic to "Review Dashboard: http://goo.gl/vysJqI | Summary Dashboard: http://goo.gl/2By1qv | Summit scheduling: https://etherpad.openstack.org/p/liberty-swift-summit-topics | Logs: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/"18:27
-openstackstatus- NOTICE: Gerrit has been restarted. New patches, approvals, and rechecks between 17:30 and 18:20 UTC may have been missed by Zuul and will need rechecks or new approvals added.18:27
*** annegentle has quit IRC18:35
*** annegentle has joined #openstack-swift18:35
notmynameFYI, feature/ec and feature/ec_review have been deleted from upstream repos18:40
notmynamethe old feature/ec has been tagged as erasure_code_dev_history18:40
*** Vinsh has quit IRC18:47
*** thumpba has joined #openstack-swift18:49
*** thumpba_ has joined #openstack-swift18:50
*** ho has joined #openstack-swift18:53
hogood morning guys!18:53
*** thumpba has quit IRC18:53
notmynameho: hello!18:54
honotmyname: hi!18:55
*** kota_ has joined #openstack-swift18:55
notmynamethanks for waking up early18:55
kota_morning :)18:56
claygare we doing this?18:56
honotmyname: I can enjoy the current situation :-)18:57
hokota_: good morning!18:57
*** acoles_away is now known as acoles18:57
kota_ho: Good :)18:58
*** tsg_ has joined #openstack-swift18:58
mattoliverauMorning19:00
*** jrichli_ has joined #openstack-swift19:00
kota_mattoliverau: morning19:00
notmynamehi19:00
notmynameok, meeting time19:00
notmynamein #openstack-meeting19:01
*** Vinsh has joined #openstack-swift19:01
claygacoles: i'm doing some reconstruction and not seeing the Etag (only ETag)19:01
*** silor1 has joined #openstack-swift19:04
claygi'm just reading this and remember trying it one time a long time ago - i could be wrong -> http://docs.openstack.org/developer/swift/misc.html#acls19:05
acolesclayg: the ssync_sender test does blow up if you revert my fix in server.py19:06
*** silor has quit IRC19:06
claygacoles: i'm sure it's worth fixing - i'm trying to understand if we're hozed (or if not, why not - so far we don't look hozed)19:06
acolesclayg: yeah i hope we're not hozed! as my commit msg said it was a hypothetical risk of harm, but a real risk of just being confusing19:10
*** jrichli_ has quit IRC19:13
*** jrichli_ has joined #openstack-swift19:13
*** jrichli_ has quit IRC19:16
*** silor1 has quit IRC19:23
*** mmcardle has quit IRC19:27
*** david-lyle has joined #openstack-swift19:30
*** peluse has joined #openstack-swift19:47
*** ozialien has quit IRC19:50
*** bkopilov has joined #openstack-swift19:54
claygacoles: i'm missing something19:59
acolesclayg: ?20:00
claygi *think* replication rsync is adding the "sent" etag as Etag next to the *computed* ETag20:00
claygacoles: but I don't think ec every *sends* the etag (as Etag or otherwise) and the *only* think that gets stored is the computed ETag20:00
acolesclayg: looking...20:02
mattoliverauwow too many uses of the work etag this early in the morning.. I'm going back to bed for a while, be back later :P20:02
claygacoles: yeah replication (having not *excluded* the etag header) is then adding the 'etag'.title() (in addtiton to the computed value stored as ETag).20:03
kota_mattoliverau: yes, of course :P20:03
*** kota_ has quit IRC20:03
acolesclayg: hmmm ssync_sender send_put just reads the fd metadata and sends all apart from content-length so how would ec not send an etag header?20:04
claygso that's why we're not screwed - ec fixed this ssync bug on accident by removing the data integrity check?  I'm not acctually sure if replication ssync will validate the computed etag matching the sent value.20:04
claygacoles: so you're thinking in the revert case - not where we have a StreamingRebuildingDiskFile and we've manipulated the diskfile20:05
acolesclayg: i'm thinking first you have an FA that has been reverted via ssync so its has ETag and Etag in its meta, then you use that FA as a source of meta for a rebuild20:06
acolesthe rebuild disk stream thingy strips out ETag but not Etag, so Etag gets sent20:06
claygi haven't been able to get a fragment archive with ETag and Etag - i tried rebuild and revert - will keep trying20:06
claygfwiw it was easy to get both on replication20:07
acolesclayg: hm, thats what confuses me cos my ssync_sender test does show them popping up, so have i seeded the test wrong20:07
acoles?20:07
claygacoles: not sure - unanticipated interaction between some other component?  maybe *I'm* testing wrong?  I want to understand which.20:08
acolesclayg: you mean replication+ssync??20:08
claygacoles: yes i tested that - obviously demonstrates the issue you described - but it's not a risk because the etag is the same20:09
claygacoles: i'm *trying* to get the ETag Etag with reconstructor+ssync because it would be really damning if kilo did in fact behave in the way you described20:10
acolesclayg: yup just double checking you, and yup no risk of harm with replication20:10
claygacoles: I *am* saying that *at the moment* I haven't been able to reproduce the potential issue with reconstructor+ssync on master and I'd like to understand why20:10
acolesme too20:10
acolesas in understand!20:10
claygok - i'll keep testing ;)20:10
peluseOK, I'm lost20:11
claygacoles: I think it has to be down in diskfile somewhere - i'm just not seeing the header come across to the object server in the ssync message on revert20:11
claygso you're right it must never get to ssync20:11
claygidk, i'll add prints there first20:12
acolesclayg: just to check - you have any .meta files in dir?20:12
claygacoles: nope20:12
acolesnot that i can think what difference20:12
acolesok20:12
claygacoles: i'll test that next!!!20:12
clayg:D20:12
claygi'm trying to get kota his rc2!20:12
acolesnote to all for liberty - land a bug just in case you need to invoke a reason for RC2 ;)20:13
claygnice!20:13
claygit has to be this wierd thing like some combination of config options that no one would ever use20:14
acolesi did for kilo but forgot what it was, darn!20:14
peluseso not to disrupt the case sensitive etag discussion to much, but...20:14
claygbut you can totally be like - and *see* 500 - can't have that.20:14
claygacoles: LOL20:14
claygacoles: ok, some "name" also comes out of metadata - but I don't see *that* in the replication headers - how does that work?20:15
acolesoh i think that gets filtered somewhere, hang on20:15
peluseahhh never mind20:16
acolesclayg: yes, sorry, ssync_sender filters out name and content-length20:16
claygoh... right pthththth20:16
claygi dont' get it - they *have* an ETag metdata20:17
claygbut send_put get_metadata never sees it20:17
acolesoh man, where'd it go ???20:19
pelusewhere iexactly is the lower case etag being created?20:19
acolespeluse: in the obj server PUT path20:20
acolesit gets an Etag header from ssync_rx (well, i thought it did) and copies it into PUT metadata20:20
acolesbased on it being in replication-headers20:20
claygacoles: i just popped a ECDiskFileManager in the console and it's *totally* in df.read_metadata20:21
acolespeluse: but also computes the hash and adds that to metadata as ETag - with a big T20:21
claygso confused20:21
acolesclayg: right, we didnt futz with any of that code20:21
acolesdid we?20:21
acolespeluse: this bit me when i wrote some ssync tests and the rx metadata != sender metadata and the diff was Etag key, and its so confusing that the 'correct' metadata key on disk is ETag but of course headers are always titlecaseed :/20:24
peluseyeah, I'm almost caught up :)20:25
torgomaticIs there a reason not to run metadata through a HeaderKeyDict?20:26
torgomaticJust asking; I'm not really up to speed here.20:26
*** cutforth has quit IRC20:26
acolestorgomatic: good question20:27
acolestorgomatic: there's lots of files out there with ETag in meta but i guess nothing would break if we started to titlecase it??? like, it happens anyway20:28
clayg^ this is a *seperate* question20:28
acolestorgomatic: we'd still need to fix this replication header thing tho20:28
acolesclayg: yes ^^20:29
torgomaticacoles: ok. Like i said, not up to speed.20:29
claygwe know the current situation is confusing and should be fixed - how to fix it is a good question - if we need an rc2 is another, more pressing question20:29
acolestorgomatic: no, its a good thought20:29
claygok - i have a fragment with Etag and ETag20:30
acoleswhoa20:30
acoleshow?20:31
acolesor rather what changed?20:31
*** Telma has joined #openstack-swift20:33
peluseso, hmm, I have one too and all I did was run the revert probe test and print the metadata in the obj server put path just before the writer.put(metadata) line20:33
peluse{'Etag': '40cdf2b84f90b5ce4704660efeaa58d6', 'Content-Length': '934208', 'X-Object-Meta-Bar': 'meta-bar', 'X-Object-Sysmeta-Ec-Frag-Index': '1', 'X-Object-Sysmeta-Ec-Content-Length': '3735552', 'X-Object-Sysmeta-Ec-Etag': '6196a6a3747f858b39574c3631244260', 'ETag': '40cdf2b84f90b5ce4704660efeaa58d6', 'X-Timestamp': '1429129717.51206', 'X-Object-Sysmeta-Ec-Scheme': 'isa_l_rs_vand 4+2', 'Content-Type': 'application/octet-stream', 'X-Obj20:33
peluseect-Sysmeta-Ec-Segment-Size': '1048576'}20:33
claygi'm not sure - maybe i was missing it before20:34
clayglike i didn't see it - and it was there - it's there now20:34
pelusecould be gremlins...20:35
acolespeluse: nice20:35
acolesclayg: peluse : so now imagine you use peluse 's FA as a source for a rebuild metadata, our code discards the E-BIG-T-ag but the Etag will be sent - thats my pathological case20:36
peluseso did we decide if this was on master before the merge (the double case senstive etag)20:36
peluseyeah, I think that's a real case - not so crazy20:36
*** Telma has quit IRC20:36
acolespeluse: yes it was on master we didn't make it so20:37
peluseseems like the 'safe fix' is to discard both, if they are both there, in the EC recon when we use the template metadata and avoid messing with anything about how master used to operate20:37
pelusebut probably a better fix would be to just have one Etag20:37
peluseI'm nOt Sure which is better :)20:38
peluseoh come one, case sensitive humor has got to be worth something!20:39
acolespeluse: so that would work but i prefer my fix because it removes confusion in every case not just reconn20:39
acolespeluse: or both, belt and braces20:40
peluseoh yeah, forgot there was a patch associated with that commit message - will go look now!20:40
acolespeluse: HEH20:40
claygrofl - the object server 422's20:41
acoleshey, so was i right?20:41
acolesclayg: i love that i sit over the ocean dreaming up issues and you actually *test and prove* in like 10% the time it would take me20:43
claygyeah so i'm not sure why it took me so long to see it - but revert will duplicate etag (same value twice different keys) - then yeah - forcing that object to be used as the base of a rebuild will leave the Etag in the shipped headers - and the remote object server under the ssync reciever will reject the reconstrcted FA because the computed ETag doesn't match the clients requested Etag20:43
acolesvoila20:43
claygi can totally write a probe test for this :P20:44
claygbut I *really* need to go pee20:44
acolesgo. now.20:44
claygacoles: is this my turn to tell YOU to go to bed now?20:44
*** gyee has joined #openstack-swift20:44
*** gyee has quit IRC20:44
claygacoles: I think peluse and I can take it form here (seeing as how you've already written the fix)20:44
peluseacoles, yeah, I like your change, just did a quick check and it worked for my manual test20:45
acolesso maybe peluse's idea of ALSO scrubbing Etag in the recon rebuilder is good too20:45
acolespeluse: clayg: remember i left a comment in the ec review about this :P ;P20:45
peluseacoles, yeah, we decided it was too confusing to think about at the time :)20:46
*** noye has quit IRC20:46
claygpeluse: yeah and it was a known issue that we convinced ourselves in testing didn't matter in practice20:46
claygit's a pretty *specific* failure mode20:46
claygbut ...20:46
claygthat being said...20:46
pelusebut yeah it can't hurt to drop it in the Ecrecon (if there) also20:46
claygacoles: YOU WERE RIGHT20:46
peluseindeed!20:46
acolesclayg: did you pee? i'm getting concerned20:46
* peluse was also curious about claygs bodily functions20:47
acolespeluse: clayg: tbh chances are even i would not grok the comment i left in review ;)20:48
peluseso I have another one that I alsmost have a probe test written for... related to the card on trello in the TODO column (the only one)20:49
peluseat one point the GET path used the node index to pass a hint to the storage node about which FI it wanted, that was pulled and made the EC recon issue decribed in that card go away but a simpler test case...20:50
pelusewhere you just create an extra .data of a different FI in a hash dir and do a GET, its a roll of the dice what you'll get back20:50
*** lpabon has joined #openstack-swift20:51
acolespeluse: so this is plain old proxy GET?20:51
peluseyeah20:51
acoleshum, so you'll get back whatever FI sorts first20:52
pelusewell, a #3 doesn't sort before a #0 and I was getting a #3 back (the bad one I seeded)20:53
acolespeluse: is that a problem, as long as proxy gets back ndata distinct frags20:53
pelusewell, it came up in the context of the EC recon so I haven't thought that much about the generic GET case20:54
pelusebut I suspect if you had a few different participating nodes all holding multiple FI's you may not get enough back of the "right ones" to decode20:54
peluseand maybe that's a bit more pathalogical20:54
acolespeluse: diskfile reverse sorts so would find #3 before #020:55
peluseoh yeah, OK that makes sense20:55
acolespeluse: so if #3 is a handoff, gets reverted to node 3 but then the purge of #3 on node 0 fails, then node 0 and 3 will both return #3 to proxy GET??20:56
peluseI guess the EC recon path is the same as GET now (once upon a time I was only getting the FI's that it needed based on asking pyeclib what those were, now it asks everyone to send theirs)20:56
pelusehmmm20:57
peluseyeah, guess so20:58
acolesumm20:58
pelusefeels like we should still have that hint for all GET of "the FI I prefer is..."20:59
peluseman, long pee for clayg20:59
pelusehey, I'm a poet and didn't even know it20:59
acolespeluse: yes, but torgomatic explained to me that the proxy GET will move onto other nodes if a GET fails, so once its not GETting from a primary it doesn't knwo what FI to request?21:00
*** gyee has joined #openstack-swift21:00
peluseyeah, that's the original issue described in the trello card :)21:01
pelusewhen we had that 'hint' in there21:01
acolesah21:01
peluseI don't know that there's a "trivial" fix for it but seems like we went througha  lot of trouble to suport multiple FI per hash dir and w/o tackling this its sorta for what?21:02
peluseif they alphabetically line up we're good??? :)21:03
acolespeluse: if you always choose a handoff whose node index is < frag index then that node will always return its primary frag21:04
claygacoles: handoff's don't node indexes21:04
pelusehuh?21:04
pelusehuh to acoles because of what clayg said21:05
acolesclayg: peluse yeah, scratch that21:05
peluseand even if they did I think there's problems with the shared node_iter being used by the GET path for EC, I have a few rough comments in the bottom of the trello card as to why21:05
acolesso, "if you got lucky it works"21:05
pelusebut I could be smoking crack, who knows21:05
clayganyway - the multi-fi's in the same hashdir is always temporary - and rare - but when it happens it could effect GET - depending on if the doubled fi also exists on another node21:06
claygyou could have all the fi's in the same node - and then get doesn't work at all21:06
claygyou need ec_ndata disks to have a fragment21:06
pelusewell, you'd have to hav enough nodes in the primary part carrying other FI's that were of large FI value such that you couldn't decode if all the wrong onces were delivered21:06
claygpeluse: yes it's a thing - but mostly requires the proxy to be able to make extra GET's with more context21:07
claygthen we have to make the object server be able to plumb the context to diskfile21:07
peluseyeah21:07
acolesso i took comment at line 1823 in obj.py to embrace *some* of these cases i.e. 'more work needed'21:08
peluseso what hapens in pyeclib I wonder if we feed him a pile of frags where there's a few dups in there but enough to decode?21:08
claygpeluse: either error, garbage, or something else21:09
peluselikely...21:09
pelusewhich means even one incorrectly delivered FI could hose us21:09
peluseworth testing21:09
clayghow the...21:10
acolespeluse: does pyeclib add any indexes in FA 'headers'? (i'm out of depth, but it adds its own header to a frag?) so it might at least throw an error21:10
peluseoh yeah, I forgot it does.  it has its own metadata that may allow it to sort this out21:10
acolespeluse: cool. thats how i'd have done it :P21:10
peluseopaque to us - the headers are I mean21:10
* peluse seems to be speaking like yoda for some reason21:11
peluseclayg, if you want to wrap the etag stuff up, I'll try feeding pyeclib some sutff like this21:11
claygi. am. so. confused.21:12
*** esker has quit IRC21:12
acolespeluse: clay: winding back to the etag thing, i should say that until i wrote the patch today i was only aware of the potential for confusion. it was only today that the potential for 422 dawned on me. otherwise i would have jumped up and down more before.21:12
pelusejust glad you did21:13
*** lpabon has quit IRC21:14
acolesclayg: you need me, or can you take the etag thing from here on...?21:14
*** esker has joined #openstack-swift21:15
claygi've somehow gotten myself backinto a world where get_metadata doesn't include the Etag :'(21:15
claygbut something needs to be fixed21:16
claygacoles: we'll get it - thanks for the clue21:16
peluseclayg, nice trick... I'l be back in just a few...21:16
peluseacoles, later man21:16
acolesclayg: ok, i'm dropping out, leave me a note if there stuff to follow up tomorrow.21:17
acolesclayg: peluse : have a good one21:17
*** acoles is now known as acoles_away21:18
claygoh wow - ok - I think i was seeing the rebuild/revert race21:20
claygok, phew - k - totally need an rc221:21
claygpeluse: so you have a probetest to validate a rebuild from a reverted fragment?21:21
peluseclayg, not right now21:22
pelusebut I can try and whip one together if you'd like?21:22
claygpeluse: nope - i'm on it21:23
peluseOK, I'm going to dork with feeding pyeclib various crap as a data point in the "GET can return the wrong FI if multiple are available" deal21:23
*** jrichli has quit IRC21:23
*** jrichli has joined #openstack-swift21:24
claygpeluse: wfm21:25
*** noye has joined #openstack-swift21:35
peluseclayg, OK, so pyelib is smart enough not to puke if we give it too many frags including if those 'too many' include duplicates so exoosure to the "GET the wrong FI" is limited to the case where there are enough nodes with extra FI's on them that are returned incorrectly such that the min number of unique fragments isn't given to PyECLib21:36
notmynameclayg: ack21:40
claygnotmyname: my favorite part of this bug is that you can *either* add devices to your ec cluster and rebalance the ring *or* you can have drive failures that require reconstruction - BUT NOT BOTH!21:45
claygnotmyname: someone needs to track down kota and tell him to get cracking on his reconstruct vs. decode/encode config option for the reconstructor ;)21:45
*** jamielennox|away is now known as jamielennox21:46
*** annegentle has quit IRC21:47
*** annegentle has joined #openstack-swift21:52
peluseclayg, what config option is that?21:53
claygpeluse: you know the jerasure hack with the comment about parity fragments in the reconstrctuor - _reconstruct method I think21:54
claygit works on the isa-l21:54
peluseyeah, but its fixed - why code in a config option?  I added a trello TODO item to just upgrade to 1.0.6 or better and then change it to always reconstruct21:54
*** jkugel has quit IRC21:55
claygbecause we can't drop the encode/decode hack from kilo as long as people are packaging 1.0.6 (e.g. everyone that has built packages today)21:56
peluseoh man21:56
claygunfortunately the hack in kilo works for everyone except for kota21:58
peluseoh, because of his library?21:58
claygsomething like that21:58
pelusethat's a pisser21:58
clayg... but since we're doing an rc2 - we get the chance to make the hack optional21:58
claygit'll work better for isa-l anyway21:58
pelusegotcha21:59
claygit *maybe* doesn't even have to be a config option - it could just "if backend is jerasure" do this dumb thing21:59
pelusewell, not sure I understand the comment on working better for isa-l anyway?21:59
claygand then we make sure to remove the condition as soon as some sha of swift can depend on at *least* 1.0.721:59
claygbut there is the kilo case where someone *knows* they have 1.0.7 and jerasure - but wants it to not do the hack22:00
pelusedealing with legacy issues issues before we even release, nice22:00
*** esker has quit IRC22:02
*** annegentle has quit IRC22:03
claygpeluse: well... what are you gunna do - we found the jerasure reconstruct bug too late22:05
claygnotmyname: is there *any* chance we could get a 1.0.7 into the kilo dependencies?  Like I *know* swifterdarrell can get it packaged - but what about zaitcev and some debian type person22:05
zaitcevclayg: I don't mind, presuming you mean PyECLib 1.0.7, which does not exist at this time. Now that I got 1.0.6 patched, it should be easier. Poke Kevin or Tushar to cut the release.22:06
pelusetsg just told me in another message that 107 is up and available22:07
zaitcevBUUUUULL22:07
peluseseeing if he can join us...22:07
zaitcevWell, I wanted to have a good word with him about it22:07
zaitcevIt's SUPER STUPID22:07
zaitcevHe uploads random tarballs to PyPi and calls it a release. That is really effin wrong. He should make a tag at bitbucket and upload those tarballs to PyPi.22:08
peluseclayg, others: separate topic I updated the trello card with more info on the GET FI w/multiple thingy, please take a look when you get a chance.  Want to get thoughts on requirement for RC2 or not22:08
zaitcevThere's even a commit at Bitbucket that says "tagging this as 1.0.5m because we have 1.0.5 at PyPy". Seriously!22:09
peluseso how do you really feel zaitcev?22:09
claygzaitcev: us poor developers don't know how to do any of this stuff :)22:09
peluseI thought packaing was done at the FedEx store when I dropped shit off :)22:09
claygyou have to tell us what to type - but with very small words - like teaching a baby22:09
*** MVenesio has quit IRC22:09
tsg_clayg: thank you ;)22:09
tsg_zaitcev: why do you think the tarballs are not random and not associated with a tag??22:10
tsg_s/not random/random22:10
zaitcevtsg_: well, where is 1.0.7?22:10
tsg_https://bitbucket.org/tsg-/liberasurecode/commits/all22:10
zaitcevoh22:11
zaitcev        url = https://bitbucket.org/kmgreen2/pyeclib.git22:11
zaitcevThat... explains it22:11
tsg_zaitcev: patience .. kmgreen2 is testing liberasurecode together with latest pyeclib so we can push that tag22:11
*** shri1 has joined #openstack-swift22:12
tsg_zaitcev: the pyeclib side got complicated because the pypi version needed to be special to keep Jenkins happy22:12
zaitcevtsg_: so, which one is the official upstream, tsg- or kmgreen2?22:12
tsg_so we maintain 2 branches there: master, 1.0_liberasurecode_integrated22:12
claygzaitcev: I'd acctually like to know that as well22:12
tsg_zaitcev: liberasurecode and pyeclib are 2 separate projects :)22:12
zaitcevwait, are we discussing pyeclib or liberasurecode?22:12
shri1Hey Guys.. I have a question about the object auditor. Does the object-auditor compute the md5 checksum and compare it with the one stored in the extended attributes?22:13
claygshri1: yeah it does22:13
notmynameI asked in -infra about what it takes to do a dependency version bump. a feature freeze exception to the requirements repo22:13
claygnotmyname: that sounds like "go fuck yourself"22:13
pelusenotmyname, and what does *that* take?22:13
notmynameclayg: no, I don't think it is ;-)22:14
tsg_zaitcev: I was trying to indicate that liberasurecode is already tagged for 1.0.7 - pyeclib should be tagged next22:14
notmynamejeblair: what does a FFE look like? I've never done one. are there docs?22:14
* peluse thinks clayg still has some sleep to catch up on :)22:14
shri1clayg: Thanks! In the swift/obj/auditor.py file, I don't see any computation of md5(). Where does this happen?22:14
claygif *I* was deciding to handoff FFE on the *GLOBAL REQUIREMENTS REPO* I would be *way* stingy22:14
tsg_zaitcev: you should be creating rpms off of the git tags on "master"22:14
notmynameclayg: indeed22:14
peluseshri1, its in diskfile22:14
zaitcevtsg_: I see no problem with liberasurecode. It's fine.22:14
claygshri1: oh the sneaky - what peluse said22:14
tsg_zaitcev: for pyeclib tags .. only use the latest tag off of master22:15
shri1I see.. let me check.22:15
pelusewas trying to beat clayg to the punch, I can point you to the LOC if you like :)22:15
claygwaho!22:15
pelusegotta have some sort of accomplishment this week!22:15
jeblairnotmyname: i don't know, sorry.  maybe this: https://wiki.openstack.org/wiki/FeatureFreeze  ?22:15
jeblairnotmyname: fungi may know more22:16
tsg_zaitcev: you will see 2 tags pushed latest today - v1.0.7 and v1.0.7m, please use v1.0.7m (that doesn't have integrated liberasurecode etc) and expects liberasurecode be an external dependency22:16
tsg_zaitcev: s/latest today/later today22:16
* notmyname goes down the yellow-brick road to -infra22:16
zaitcevtsg_: thanks, I'll mark it in the RPM spec about the -m22:17
notmynamejeblair: thanks22:17
peluseshri1, check out class DiskFileReader() and you'll see it22:17
shri1oh.. I see. So I guess, DiskFileReader() gets called for auditing as well as when clients issue a GET for the object. Md5 calc has to be done in both cases.22:18
tsg_zaitcev: thank you!22:18
claygpeluse: debug_wtf got left in!22:20
peluseshri1, yes.  the audtor just reads it and that will check the MD5 and quarantine if needed via _handle_close_quarantine()22:20
tsg_zaitcev: eventually, we'll get rid of the "1.0_liberasurecode_integrated" branch off of pyeclib - the whole reason that branch and related tags were created, was to keep Jenkins using the latest version of pyeclib regardless of where rpm/deb packaging stands22:20
peluseclayg, ooops :)22:20
*** annegentle has joined #openstack-swift22:20
zaitcevtsg_: well, whatever works for you guys22:20
pelusewell, we all reviewed it... at least I didn't spell it out!22:21
zaitcevtsg_: I'm going to post a pull request about that madness with /usr/local22:21
zaitcevtsg_: please point out where I'm wrong, including OSX etc.22:22
shri1peluse: oh.. ok. Looking at the code.22:22
notmynameok, good news on the dependency front22:22
tsg_zaitcev: I agree that needs to be cleaned up .. thank you for taking care of that!  that stuff stayed around from the original python C backend implementation22:22
claygnotmyname: wow rly!?22:22
notmynamethe process appears to be: (1) submit a patch to global requirements (2) send a message to the ML linking the patch and requesting the FFE22:23
pelusewow, just ask huh?22:23
pelusewho woulda thunk?22:23
notmynameso since this is a dependency that only affects swift it shoudl be straightforward22:23
claygwow - that's awesome22:23
claygWTG OpenStack!22:23
tsg_awesome!22:23
* clayg takes back all the times he was a pessimistic jerk (today)22:24
notmynamein the message, and in the commit message, we'll have to have justification22:24
peluseso tsg_ when did you say kevin would be done again? :)22:24
claygpeluse: heh22:24
*** annegentle has quit IRC22:24
peluseI did order him a shirt BTW...22:24
notmynameeg "This fixes bugs and eliminates a hack that is causing third-party libraries to not work"22:24
mattoliverauMorning.. Again22:24
notmynameonce it lands there, we can do a patch on master and then backport that to proposed/kilo22:25
pelusenice22:25
pelusemattoliverau, morning22:25
notmynameso (1) patch global requirements (2) ML (3) patch swift master (4) backport swift master patch22:26
notmyname#3 happens after #1 lands22:26
notmynamethen we also land the other stuff we want in the RC on master and backported to proposed/kilo22:26
notmynamethen we tag RC222:26
tsg_notmyname: ack22:26
notmynameso, what part do you want me to do?22:27
* notmyname assumes at least #222:27
claygnotmyname: as soon as tsg_ says i can pip install 1.0.7 i'll start working on the swift patch22:28
*** keving has joined #openstack-swift22:28
notmynamehi keving22:29
kevingyo22:29
tsg_notmyname: I will take care of #1 to start with.  Your word to the ML will help with #2.22:29
pelusehey, its keving!22:29
notmynamekeving: you must have been summoned22:29
peluseor just really good timing :)22:29
kevingy, tushar said irc was blowing up22:30
notmynameheh22:30
clayglol22:30
pelusedust ahs already settled... you're late!22:30
notmynamekeving: we want to update the dependency on liberasurecode to 1.0.7 asap22:30
notmynameso on pypi pyeclib and liberasurecode are bundled?22:30
*** dencaval has quit IRC22:33
notmynameie does pyeclib need to be updated (which is what's in global requirements) or just liberasurecode?22:34
*** annegentle has joined #openstack-swift22:36
kevingsorry, had to step out…22:39
kevingyeah, i am going to run a few more tests and we can push to pypi22:40
kevingwe are still pushing the bundled version, so we need to update the global requirements22:40
kevingbrb22:41
tsg_notmyname: the pypi version would have to be bundled w/ liberasurecode for now, given 1) liberasurecode rpms for centos65 slave are not available 2) if we fix something in liberasurecode, unless we go through the whole Debian/Red Hat release process, Jenkins won't pull the latest22:41
*** annegentle has quit IRC22:41
notmynameok22:41
notmynameeven though they are in 2 separate repos? are you using submodules or something?22:41
tsg_notmyname: at the moment, liberasurecode source is included as a "make dist" style "release" tarball22:42
notmynameah ok22:43
tsg_notmyname: (that was per discussion on -infra)22:43
notmynameproposed ML message: https://etherpad.openstack.org/p/uq5dUh9AJ622:43
openstackgerritClay Gerrard proposed openstack/swift: Don't apply the wrong Etag validation to rebuilt fragments  https://review.openstack.org/17413822:43
notmynameclayg: that's the one, right, that spells R-C-2 for us?22:44
peluseclayg, just curious, why did you make _get_partners() a module level function in that patch just now?22:45
tsg_notmyname: the draft ML message looks good22:45
pelusenotmyname, there's also a cardon trello I'd like us all to look at and make sure we're OK with RC2 (with or without it)22:46
peluseits the only one in doing right now22:46
*** km has joined #openstack-swift22:46
notmynameI need to step out in about 15 minutes22:46
peluseclayg, and also - do you mean for that to be in addition to acoles patch right?22:47
claygpeluse: i wrote it *three* - fucking *three* times in the probetest before I finally got it right!22:48
*** joeljwright has quit IRC22:48
claygit shouldn't be that hard - but apparently if you're an idiot - it's easy enough to get wrong - so... module level export helper22:48
notmynamealso, it doesn't use anything from the class22:49
claygpeluse: i'm not 100% on acoles_away's approach - I think torgomatic had a good idea for addressing the larger issue22:49
claygpeluse: his works too - but your suggestion to just clear it out in the reconstructor (that was his original suggestion too) - seems like a more surgical obviously correct RC sorta of patch22:50
claygI added some comments to acoles patch but I'm down either way I think - i am sorta curious if either torgomatic's HeaderKeyDict or fixing the issue in ssync_sender looks better than fixing it in object-server22:50
claygbut even if either of those works as good or better than acoles patch for the larger issue - i'm not sure how much of it belongs in the RC2 backport22:51
peluseclayg, agree for a quick RC fix, thanks22:51
claygpeluse: you worried about the _get_partners extraction - i sorta unilaterally decided it's one of those things you can sorta visually inspect and decide it's obviously correct - and it was helpful to the probe test - I could back off that tho and reduce the change in reconstructor to just the try KeyError (maybe a pop would have been better)22:53
claygoh or a for all permutations of EtAg metadata.pop()  # for realzy don't f'ing send it22:54
pelusenah, I think its fine it just wasn't obvious to me why it moved but makes sense for making the test a bit easier and is a tiny change22:54
claygyeah i didn't start there - i was really surprized it took me three times22:54
pelusesleep deprived still maybe!22:55
claygfirst was onodes[index + 1] % len(onodes) then it was onodes[index + 1 % len(onodes)] then *finally* onodes[(index + 1) % len(onodes)]22:55
claygso at that point i was like - wow - i should apparently be importing this code from somewhere :P22:56
peluseheh22:56
pelusetesting it now22:57
*** erlon has quit IRC23:01
*** shri2 has joined #openstack-swift23:01
*** shri1 has quit IRC23:02
notmynameI've got to step out. I'll be back in an hour or two and take care of whatever's pending for moving RC2 forward23:04
*** shri2 has quit IRC23:07
*** chlong has joined #openstack-swift23:10
claygdoes anyone besides notmyname know if i'm supposed to propose patch 174138 to master or some sort of stable/kilo branch23:17
patchbotclayg: https://review.openstack.org/#/c/174138/23:17
*** fanyaohong has joined #openstack-swift23:18
pelusestuck in mtg for another 40 min or so will fish review then23:21
tsg_zaitcev: https://bitbucket.org/kmgreen2/pyeclib/commits/tag/v1.0.7m23:21
claygpeluse: perfect - i ended up liking the pop form better - going to post new patch23:21
pelusek23:21
zaitcevtsg_: thanks, got it23:21
openstackgerritClay Gerrard proposed openstack/swift: Don't apply the wrong Etag validation to rebuilt fragments  https://review.openstack.org/17413823:21
tsg_clayg: I have a similar question on the requirements patch .. submit it to master or stable/kilo? :)  let me see if folks on -infra would know23:28
claygtsg_: yeah great - let me know23:31
claygtsg_: if you get a patch up that includes the 1.0.7 bump - i may re-use that same patch to pull out the encode/decode hack23:31
tsg_clayg: sure23:32
tsg_clayg: 1.0.7 is up on pypi btw23:32
claygyup just pip'd it - working on the patch now23:32
tsg_cool23:33
claygtsg_: i was goign to ask - but then was like - oh you know who would know if pypi has 1.0.7????23:33
claygPYPI23:33
*** distroguy has joined #openstack-swift23:33
*** j_king_ has joined #openstack-swift23:34
*** HenryG_ has joined #openstack-swift23:35
*** torgomatic_ has joined #openstack-swift23:37
*** dmsimard has quit IRC23:38
*** torgomatic has quit IRC23:38
*** j_king has quit IRC23:38
*** bkopilov has quit IRC23:38
*** HenryG has quit IRC23:38
*** torgomatic_ is now known as torgomatic23:38
claygtsg_: my ec_crazy_rebuild script is still giving me different md5's from reconstruct vs. encode/decode - worse probetests for rebuild is failing when I revert the hack23:38
*** bkopilov has joined #openstack-swift23:38
claygpip freeze says 1.0.7 - but I'm not sure liberasure and ldconfig i don't even know23:38
*** omame has quit IRC23:39
*** csmart has quit IRC23:39
*** klrmn has quit IRC23:39
*** omame has joined #openstack-swift23:39
*** dmsimard_ has joined #openstack-swift23:39
*** dmsimard_ is now known as dmsimard23:39
*** klrmn1 has joined #openstack-swift23:39
clayghrmm.... yeah locate liberasure finds /usr/local/lib/liberasurecode.so.1.0.623:39
*** klrmn1 is now known as klrmn23:39
tsg_clayg: you don't have liberasurecode.so.1.0.7 under /usr/local/lib at all?23:42
tsg_(and liberasurecode.so.1 relinked to that version)23:42
claygturns out no - i've clone'd the liberasure repo and going to try to build it23:43
claygnope it's a symlink to 1.0.623:43
*** esker has joined #openstack-swift23:44
claygtsg_: yeah so i didn't get any error/warning with pyeclib 1.0.7 when liberasure 1.0.6 was installed23:45
claygtsg_: but everything works when I build and install liberasure 1.0.7 from source23:45
claygtsg_: which I *guess* is what one has to do?23:45
*** distroguy is now known as csmart23:45
tsg_clayg: yeah that's the correct process23:45
tsg_clayg: 1) install latest liberasurecode tag 2) install latest pyeclib tag off of "master"23:46
claygweird... what good is it having pyeclib on pypi if you can't install it without this other project you have to download and install from source?23:46
tsg_clayg: there are checks in place for liberasurecode-1.0.7 to be honest23:46
tsg_(in the pyeclib pypi version)23:47
tsg_not sure why it chose not to build it .. I am looking and nothing seems to have changed in that area recently23:48
claygtsg_: so I just uninstalled liberasure and verified you can't create a pyeclib driver - then I pip reinstalled pyeclib and it build/installed liberasure 1.0.7 for me23:50
claygtsg_: so apparently having 1.0.6 installed made upgrading pyeclib not care to rebuild liberasure code - but not having *any* liberasurecode triggered something that make'd something23:50
zaitcevtsg_: looks like I was able to file an issue just fine, at least for liberasurecode: https://bitbucket.org/tsg-/liberasurecode/issue/11/licensing-in-m423:50
claygtsg_: did you find how to make rc like patches?23:53
*** wolsen_ is now known as wolsen23:59

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