Wednesday, 2017-02-08

JimCheungMorning kota_:00:01
kota_morning JimCheung00:01
JimCheungKota_: Sorry I missed you yesterday.00:02
kota_JimCheung: np00:02
JimCheungKota_: We submitted a new patch for review.  Still need some help with how to add the test to gate00:03
kota_JimCheung: k, thanks. will look at00:03
JimCheungKota_:  Thanks!00:04
kota_JimCheung: for the gate testing, I think there is a couple of way to enable it00:05
kota_JimCheung: 1. add custom script to setup your backend in the liberasurecode repo but it requires that your backend should be available at online00:07
kota_JimCheung: it may be difficult because of patented00:07
notmynameFYI the (few) PTL elections have concluded, and the list of PTLs has been posted http://lists.openstack.org/pipermail/openstack-dev/2017-February/111769.html00:07
kota_JimCheung: 2. Another solution could be adding third party testing.00:07
kota_I'm not familir with the third party setting but someone knows about more detail...00:08
kota_maybe swiftstackers?00:08
JimCheungKota_: For option 1 but create a debian package to add on the server.  This will be a minimal function test only00:08
notmynamehere's docs on the third party CI. this is what's done with the swiftstack community qa cluster http://docs.openstack.org/infra/system-config/third_party.html00:09
JimCheungKota_: Option 2 maybe tricky to implement00:09
claygkota_: just waiting on me I'm sorry :'(00:09
notmynameJimCheung: it's not too tricky. there's plenty of docs and people to ask00:10
kota_notmyname: nice00:10
notmynameJimCheung: however, it does require you to commit compute resources, so that part may or may not be tricky for you00:10
notmynameJimCheung: also, note that 3rd party ci can only be advisory. it will never be able to actually gate a commit00:10
kota_clayg: no worries, I'll grub my coffee and chocolate while waiting :P00:10
*** stradling has quit IRC00:11
JimCheungKota_: and notmyname: Okay, let me review the document.  We maybe able to implement a compute resource w/o too much issue00:11
*** mvk has joined #openstack-swift00:11
kota_JimCheung: sounds nice00:12
JimCheungKota_: and notmyname: Cool!  Will get back with you.  Thanks very much!00:12
kota_looking at the ML for PTL election, PTLs are as I expected :P00:13
claygkota_: notmyname: wouldn't it be *better* to have a built package to test so we can help troubleshoot issues - vs 3rd part CI (e.g. probetests on community cluster broken since... post as copy something someting?)00:13
-kota_- * Storlets : Eran Rom00:13
-kota_- * Swift : John Dickinson00:13
notmynameJimCheung: also, please note clayg's comments earlier here in IRC.00:13
kota_on my related projects.00:13
notmynameJimCheung: there's a discussion to be had (but maybe not at the moment)00:13
kota_clayg: yeah, currently it seems it has been broken00:14
notmynameJimCheung: but I will state that whatever is agreed to, if it involves phazr.io support, it absolutely *must* be tested in an automated way. so the 3rd party ci is a good start00:14
JimCheungnotmyname: Understood.  I'll rope in GaryG into the conversation as well00:14
kota_(definitely, I should add shss 3rd party :/)00:15
notmynameJimCheung: honestly, i'm not sure when/where to have that conversation (I know clayg's in the middle of internal stuff at the moment). probably the best place to start is in gerrit00:15
notmynamekota_: yes! ;-)00:15
claygkota_: so like I can't test shss on my dev machines right?00:15
claygkota_: or I *could* but I don't - because i'm lazy?00:15
kota_only on your machine (not online available), it could be tested, IIRC, you got testing binary of shss at the past tokyo summit?00:16
claygnotmyname: I think kota_ timburke and tdasilva are the main people driving maintainership of liberasurecode - I think *those* people need to have a conversation about what they can realistically hope to "support" with an increased plugin matrix00:16
claygI would expect it would include defining some sort of scope/requirements - and then hopefully the can get some feedback if thats reasonable00:17
JimCheungClayg: Makes sense00:17
notmynamekota_: yeah, you gave us each one. on a cd. I don't have a cd drive ;-)00:17
clayghowever - I think there's lots of examples opensource and openstack projects that have walked down this path - I think there's lots of good insight to be gained from talking to people that have been there done that00:17
claygnotmyname: maybe I can find a torrent somewhere?00:18
notmynamelol00:18
kota_notmyname: that's too bad :/ you need to google where you can buy a portable cd drive from.00:19
clayglol00:19
notmynamelol00:19
*** stradling has joined #openstack-swift00:23
*** stradling has quit IRC00:36
*** delatte has joined #openstack-swift00:42
*** delattec has quit IRC00:43
*** tqtran has quit IRC00:51
*** tonanhngo has quit IRC00:57
*** sams-gleb has joined #openstack-swift00:59
*** ukaynar has quit IRC01:03
*** sams-gleb has quit IRC01:04
*** _JZ_ has quit IRC01:10
*** yarkot has quit IRC01:10
*** tonanhngo has joined #openstack-swift01:17
*** adu has joined #openstack-swift01:19
*** adu has quit IRC01:21
*** tonanhngo has quit IRC01:22
*** tongli has joined #openstack-swift01:29
*** winggundamth_ has joined #openstack-swift02:16
claygwweeee git review -d 21916502:19
*** ukaynar has joined #openstack-swift02:19
kota_clayg: that shows patch set 5302:28
claygi'm just laughing that i'm only now getting to checking it out finally02:28
claygwhat's the short version of the tests that got updated?02:29
*** adu has joined #openstack-swift02:30
kota_the changes in the tests are related to some points of view with retry counts for read node and sort key on proxy.02:30
clayg... the diff still ~2K lines in proxy.test_server that changed - but I think maybe only one or two tests in that module are *new*02:30
*** winggundamth has quit IRC02:31
kota_as you know, I removed the sor key on the proxy read which ignores affinity, the proxy is now going to access the object-servers (basically shuffled in the tests)02:31
claygis that good? (for the tests)02:32
kota_so I reviewed some assertions02:32
kota_some of them are changed from assertEqual to assertGreaterEqual and assertLessEqual.02:32
claygoh wow, so somewhere deep in that 2K line diff is a few very small subtle changes to the tests - but since they moved to an entirely different part of the file it's very hard to find them?02:33
kota_clayg: ah, you're right02:34
claygk02:34
kota_however, almost of 2K lines are tested both ECPolicy w/ and w/o ECDuplication02:35
claygright - still need to wrap my head around that02:35
kota_the new test should be https://review.openstack.org/#/c/219165/53/test/unit/proxy/test_server.py@5650, if i remember correctly02:36
patchbotpatch 219165 - swift - EC Fragment Duplication - Foundational Global EC C...02:36
kota_and other changes are from making Mixin for https://review.openstack.org/#/c/219165/53/test/unit/proxy/test_server.py@554902:37
patchbotpatch 219165 - swift - EC Fragment Duplication - Foundational Global EC C...02:37
claygk02:37
*** tongli has quit IRC02:38
kota_ah one more, adding test setup (maybe you don't like) for policy 4 (i.e. ec_duplication storage policy)02:38
claygkota_: right i saw that - it's ok - i'll get over it02:39
*** winggundamth_ has quit IRC02:45
*** ukaynar has quit IRC02:45
claygtimburke: kota_: I bump into this while testing the reconstructor a lot -> 42549502:47
claygpatch 42549502:47
patchbothttps://review.openstack.org/#/c/425495/ - swift - Give spawn a cycle02:47
*** winggundamth_ has joined #openstack-swift02:47
claygI think the associated bug report has a lot of repro details - i think the risk is pretty small overall02:47
claygtfw ctrl-r matches the wrong command but you hit enter too fast02:51
kota_looking02:55
kota_ah, got it, it's in *once* mode02:55
kota_and never re-call reconstruct to tranpoline the event hub via sleep02:56
claygis *that* what's going on!?02:56
kota_is it?02:56
claygI really never understood why the changes fixes it - much less enough to write a test - i just notice the traceback pretty consistently except when I have that sleep in there02:56
claygi found "the spot" by trial and error02:57
kota_in my quick view02:57
claygi have no idea02:57
kota_and will look at more deeply after lunch02:57
clayghave a good lunch!  thanks02:57
*** sams-gleb has joined #openstack-swift03:01
*** sams-gleb has quit IRC03:06
claygTIL git fetch origin master:master to update local tracking branch w/o changing branches!03:06
*** hurricanerix has quit IRC03:07
*** klrmn has quit IRC03:09
mattoliverauyou can also use the 'git fetch origin master' 'git merge origin master' to do a 2 phase git pull (actually what a pull is), except the merge can then be aborted if required.03:09
*** dmorita has quit IRC03:09
mattoliverau^ speaking of sometimes useful git tips ;)03:10
*** dmorita has joined #openstack-swift03:11
claygand I don't have to be *on* master to merge origin/master into master?03:11
mattoliverauoh yeah, you may still have to change branches.. but ^ has got me out some acidental merges on saios I have floating around and not updated in a while :P03:13
claygmattoliverau: oh!  sorry!  yes!  :protip:03:13
mattoliverauclayg: yeah sorry, not trying extend yours :P03:14
* mattoliverau its still recovering from vaction03:14
mattoliverau*vacation03:15
claygrofl03:15
*** dmorita has quit IRC03:18
*** adu has quit IRC03:41
*** dmorita has joined #openstack-swift03:43
*** links has joined #openstack-swift03:50
*** JimCheung has quit IRC03:55
*** mkaminski has joined #openstack-swift03:55
*** mkaminski has quit IRC04:04
*** psachin has joined #openstack-swift04:49
*** dmorita has quit IRC04:59
*** sams-gleb has joined #openstack-swift05:03
claygkota_: I don't understand lack list05:06
kota_clayg: ok, let me describe05:07
*** sams-gleb has quit IRC05:08
kota_clayg: parhaps, it could be said as priority list05:09
kota_in the case using duplication factor05:09
claygkota_: it's trying to make error handling better right?05:09
kota_we would have diffrent number of missing hole with indexes05:09
kota_i'm not sure to get correctly for *the error handling* you said.05:10
clayglike if a node['index'] % uniq_frags == 4 - then it tries to connect another node then it tries to pick that node maybe?05:10
kota_it may be called as error handling but...05:10
clayger... tries to pick another node that might have same frag_index?  maybe?05:10
kota_the test for the process is https://review.openstack.org/#/c/219165/53/test/unit/proxy/controllers/test_obj.py@430505:12
patchbotpatch 219165 - swift - EC Fragment Duplication - Foundational Global EC C...05:12
kota_er05:12
claygok, let me read those05:12
claygthanks!05:12
kota_yeah05:13
kota_maybe you're closing to the answer05:13
kota_it's a kind of technique when we need another node (i.e. handoffs) to pick for missing primaries05:13
kota_when choosing handoffs and iif the case # of handoff nodes is less than replicas05:14
kota_# of replicas05:14
claygyeah the test was good a tip - thanks05:15
kota_e.g. 4-2 * 2 case, we need 12 nodes to store whole fragments05:15
kota_and if only 6 ~ 11 nodes available, how we could choose the index which should be stored.05:15
kota_and the lack list will be effective to choose the indexes as possible as unique05:16
kota_please feel free to ask me any time you need more description05:17
*** tonanhngo has joined #openstack-swift05:25
timburkehmmm.... once we land https://review.openstack.org/#/c/425493/, i guess https://review.openstack.org/#/c/340584/ can be abandoned?05:43
patchbotpatch 425493 - swift - Make the reconstructor handoffs_first work (and us...05:43
patchbotpatch 340584 - swift - Make handoffs_first per partition in reconstructor05:43
claygi've never seen patch 340584 before?05:44
patchbothttps://review.openstack.org/#/c/340584/ - swift - Make handoffs_first per partition in reconstructor05:44
clayglol - that's *very* similar to patch 42840805:46
patchbothttps://review.openstack.org/#/c/428408/ - swift - Optimize reconstructor handoffs_first05:46
claygat one point I even had witten the is_handoff in a closure like that05:47
claygtoo funny05:47
claygonovy: is in the future!05:47
claygI think onovy's patch would have fixed lp bug #1491605 too05:52
openstackLaunchpad bug 1491605 in OpenStack Object Storage (swift) "Reconstructor jobs are ordered by disk instead of randomized" [High,Fix released] https://launchpad.net/bugs/149160505:52
claygonovy: when you put up changes you should associate them with bugs - help prioritize reviews "objective observable undesirable behavior" goes away after you review this (hopefully samll and well tested) change05:53
clayg^ MY FAVORITE REVIEW05:53
*** sams-gleb has joined #openstack-swift06:06
*** sams-gleb has quit IRC06:10
*** SkyRocknRoll has joined #openstack-swift06:20
mahaticswift-ring-builder doesn't seem to have a -h or --help command option, but does have good docs inside code!06:25
claygOMG lack_list is for PUT :'(06:27
timburkemahatic: yeah, i've been disappointed by that too :-(06:27
timburkeclayg: ...yes? of course. what *else* would it be for??06:27
timburkei mean, we don't want 2 of frag 0 and none of frag 1, right?06:28
claygI thought it had something to do with picking handoffs for GET06:28
timburke:P06:28
clayg... is that what would happen?06:28
mahaticso what's a good way to help myself get ramped up on patch 219165 other than reading code :P06:28
patchbothttps://review.openstack.org/#/c/219165/ - swift - EC Fragment Duplication - Foundational Global EC C...06:28
claygmahatic: I always ran ith w/o any args - seems to print a bunch of text?06:29
timburkeit could. the idea behind lack_list is to avoid that sort of situation, anyway06:29
mahaticclayg: works like a charm \o/ thanks!06:30
timburkeok, so -- EC: great! high durability, lower storage requirements! global clusters: great! high durability (because things are in multiple data centers) *and* nice response times (because you can totally prefer to service requests locally)06:31
mahatictimburke: ^06:32
timburkeEC + global clusters: sad :-(06:32
timburkecurrently.06:32
timburkeyou could *try* to make it less sad by upping parity frags past data frags. but you'll still be sad, because now you *always* have to reconstruct on GET (in at least one region)06:33
timburkekota's patch (assuming your ring is *just right*) -> not so sad. lots of data frags, some of parity frags, ~same storage requirements compared to replicated, better durability06:34
timburkekota_: i think i'm representing it right? yeah?06:34
timburkebut now i should sleep, not review. because margaritas.06:35
timburkeg'night!06:35
mahatictimburke: :D good night!06:36
mahaticthat looks like a gist, but I didn't know that we *did not always* reconstruct on GET prior to kota_ 's patch06:36
kota_timburke: right and good night!06:37
mahatictimburke: thanks!06:38
claygmahatic: there used to be some presentation slides linked from the commit message06:38
claygmahatic: yes, they're still there -> http://www.slideshare.net/tsuyuzaki/global-ec-cluster-updates-openstack-mitaka-swift-design-summit06:39
mahaticclayg: looking, thanks06:39
kota_mahatic: note that, it could be a bit stale info (espically about frag index design at Page 7)06:40
kota_mahatic: but the anlysis about performance should be always true.06:40
mahatickota_: oic06:41
claygI personally have a *different* reason for not liking a 10+14 schema sort of solution to global EC06:41
claygwith a 10x14 I have a fixed width - I can support rebuilding from either side of even split (any 10 will do, so two regions should get 12 frags each, so i'm ok)06:42
claygbut if I want to increase to 3 regions - can't06:42
claygwith a 10+2x2 I can always migrate to a 10+2x306:42
kota_clayg: definately06:42
claygand it's *also* faster06:42
* mahatic is off to lunch06:47
*** tqtran has joined #openstack-swift06:50
*** sams-gleb has joined #openstack-swift06:50
mahatickota_: clayg: "(object ring must have 6 replicas)" commit message says that after swift.conf example. Does it mean EC  global clusters will need 6 replicas? Did I read it wrong?06:51
kota_mahatic: it's an example06:52
claygmahatic: yes, you'll need to make some ring chnages to test this change06:52
kota_mahatic: actually, (ec_k + ec_m) * duplication_factor -> # of replicas06:52
claygare you using vsaio or something fancy like that - or just plain vanilla?06:52
kota_mahatic: in the case, ec_k = 2, ec_m = 1, and duplication_factor = 2 -> (2 + 1) * 2 == 6 you need.06:53
mahaticclayg: plain vanilla. My current testing env has swift + keystone (installed via devstack). But I also have just saio vms06:53
claygwhat's the default # of devices for the ec policy?06:54
clayghow many sdb* looking things do you have in /srv/node*/06:54
*** tqtran has quit IRC06:54
mahatickota_: can it go lower than that? I don't think so?06:54
kota_mahatic: on ec setting? or just # of replicas?06:55
mahatickota_: ec_k and ec_m06:55
mahatickota_: in effect the number of replicas06:55
kota_mahatic: it could be on the setting constraint but...06:56
kota_mahatic: i think the setting with lower values is nothing effective06:56
kota_ec_k = 1, ec_m = 1, it looks just 2 replica?06:56
claygheh06:57
claygmahatic: how many *devices* do you have?06:57
mahaticclayg: sorry06:57
*** abqkawi1000 has quit IRC06:57
kota_with ec_k = 2, and ec_m = 0... hmm, it could be effective as striping?06:57
mahaticclayg: in my current vm saio, i have what I configured via loopback06:57
mahaticso 406:57
claygmahatic: yeah that's not enough :'(06:57
mahaticclayg: what do I need? I just fetched a brand new server!06:58
claygI think the saio docs have instructions for setting up ec - wants at least 8 devices for a 4+206:58
kota_not sure if current swift ec works as striping. I don't think we have big problem on that except durability and reliability.06:58
claygkota_: ?06:59
kota_what?06:59
*** rcernin has joined #openstack-swift06:59
claygkota_: I didn't follow what you were saying about striping/durability/reliablity?06:59
claygkota_: but it sounded important!07:00
claygmahatic: http://docs.openstack.org/developer/swift/development_saio.html#using-a-loopback-device-for-storage07:00
kota_ah07:00
claygsays you need 8 devices07:00
*** dmorita has joined #openstack-swift07:00
claygmahatic: you should try https://github.com/ntata/swift-setup-scripts07:00
kota_e.g. if you set ec_k = 5 and ec_m =0 (which should work likely RAID 0 striping), we don't have any redundancy with the stored data.07:01
kota_clayg:^^07:01
claygmahatic: vsaio makes it easy to build saio with different configs - for my global-ec test I'm using 4 nodes x 4 devices (sdb1-sdb16) 4+2x207:01
kota_I'm not sure if such a parameter could be available in current Swift master07:01
mahaticclayg: I do have that setup too in a vm. this one - http://docs.openstack.org/developer/swift/development_saio.html#using-a-loopback-device-for-storage07:02
claygkota_: OH!07:02
-kota_- >>> driver = ECDriver(ec_type='liberasurecode_rs_vand', k=5, m=0)07:02
-kota_- Traceback (most recent call last):07:02
-kota_- File "<stdin>", line 1, in <module>07:02
-kota_- File "/usr/local/lib/python2.7/dist-packages/pyeclib/ec_iface.py", line 169, in __init__07:02
-kota_- "Invalid number of data fragments (m)")07:02
-kota_- pyeclib.ec_iface.ECDriverError: Invalid number of data fragments (m)07:02
mahaticclayg: oic07:02
kota_unfortunately, we cannot07:02
kota_ec_m must be >007:02
kota_it looks like weird error message though07:03
claygkota_: that'd be cool tho!  3+0x3 sounds really interesting all the sudden :P07:03
kota_it should say "Invalid number of *parity* fragments (m)", right?07:03
claygdata frags?  m?07:03
clayglol07:03
mahatic:D07:03
claygkota_: you *had* to go turn over the rock07:03
mahaticyes parity07:03
claygkota_: and I didn't even know I wanted 3+0x3 - i totally do now tho07:04
claygi want that07:04
*** dmorita has quit IRC07:04
claygor like maybe 5+0x3 no sure07:04
kota_lol07:04
* mahatic needs be afk. Be back in a bit07:05
kota_it sound like raid 0 + 1 (and +1)?07:05
claygmahatic: but with 8 devices (I think ntata's script will setup 8 devices) - I think you can do a 2+1x2 and be ok07:05
openstackgerritKota Tsuyuzaki proposed openstack/pyeclib master: Fix error message with invalid parity number  https://review.openstack.org/43059907:12
kota_done for fixing the error message at pyeclib07:12
claygkota_: I think my 16 devices are maybe to constrained to really understand lack list with 12 total frags07:15
clayghttps://gist.github.com/clayg/26c804954ffa1032228bff8649b830eb07:15
claygso without lack list my handoff devices are r1sdb11#3, r2sdb6#0, r2sdb12#4 - with lack list my handoffs are r1sdb11#0, r2sdb6#3, r2sdb12#407:16
claygso 0 & 3 flip?  is that... good?07:16
clayglike it's the same handoff nodes in the iter (obvs.) so what are the principles we even use to decide which handoff node should get which fragment?07:17
clayghow would I even say one list is better than another?  I think the holes enumeration on master is determistic - same nodes down gives you same indexes on same handoffs - but we don't go out of our way to assign any specific handoff any specific node index07:18
claygI think we get it on disk and let the proxy sort it out on read07:18
claygproxy is good at sorting it out on read07:18
kota_looking07:19
kota_it looks like the down node 1 assignged a primary half of ec unique_fragments?07:21
kota_i think if node 2 (it looks to have secondary half  of fragments) down, it will be different behavior between w/ and w/o lack_list07:22
claygkota_: cool I try it!  thanks!07:23
openstackgerritChristian Schwede proposed openstack/swift master: Add support to increase object ring partition power  https://review.openstack.org/33729707:24
kota_oooh07:24
kota_it may need more specific situation07:24
kota_i think 1 node down behaves only 1 missing for 3 indexes07:25
*** tonanhngo has quit IRC07:25
kota_the lack_list will be effective when mixture case with 2 missing and 1 missing for each index07:26
claygwhy?  why is missing index 0, 6 any different in 4+2x2 than missing 0, 5 - all that matters it that the missing index gets assigned to a handoff - and that the backend conversion changes the assigned index to correct frag index?07:28
clayghow do I say which node in my handoff iter is better to have frag #X vs frag #Y07:28
claygwhat is the rules used to govern such a decision?  I don't under stand why assinging on or another is better as long as one get assigned.07:29
*** pcaruana has joined #openstack-swift07:29
claygso what if fist handoff gets 0 and second handoff gets 6 (also 0 frag index) - what choice do you have?07:29
kota_wait a bit, I'm trying to understand the situation on your gist.07:29
*** ChubYann has quit IRC07:30
claygi'm trying to understand the motivation of changing the holes assignment07:30
claygyou have primaries missing - they have indexes - you replace them with handoffs - you give the primary indexes you don't have assigned to handoffs - simplicity itself07:31
clayghow would I evaluate if assigning the missing set (0, 5, 6) is better (0, 6, 5) or (5, 6, 0)07:31
claygwhat is the model by which I would say one is better than another?07:31
claygonly requirement I have is "deterministic"07:32
kota_ah, not intend to the order07:32
claygwhich is why I like first handoff gets first hole, second handoff gets second hole07:32
kota_set (0, 5, 6)  and 0 == unique_idnex(6), right?07:32
kota_you mean?07:33
claygsure that's the idea07:33
kota_and if we have only one handoff07:33
claygbut... I mean also like how is assigning the set (0, 5, 6) have different requirements from assigning the set (0, 5, 7)07:33
kota_should we choose 0 or 6 rather than 507:33
kota_right?07:33
claygonly *one* handoff!?07:33
* clayg mind blown07:33
kota_when get_more_nodes gave up to pop07:34
clayglazy ass get_more_nodes - someone needs a bigger cluster07:34
clayglol07:34
kota_clayg:07:34
kota_yes07:34
claygso my 16 devices had *too many* devices to show the issue07:34
clayg:D07:34
kota_if we have enough devices for handoffs07:35
kota_nothing intended in the lack list in my mind07:35
claygand here I thought I better have at least enough handoffs that I can kill a whole node07:35
claygok - that is super helpful - thanks07:35
*** tesseract has joined #openstack-swift07:35
*** david-lyle_ has joined #openstack-swift07:37
kota_clayg: great, exactly it may be a corner case but i could not stop to think the case the handoff nodes filled out only duplicated one dropping unique ones07:37
claygwhat's the total number of responses I need for success in a 4+2x2?07:39
* mahatic is back07:40
mahaticclayg: ack07:40
kota_clayg: depends on # of node down? but thinking of failure domain, at least 2 nodes should be down07:40
kota_with more than or equal to one same frag index and there is a few frag index with single missing07:41
kota_looking at the gist above...07:42
kota_down node 1 and node 2 will be missing index 0, 4 (2 missing) and 5 (1 missing)07:43
kota_so if you would have 2 available devices in node 3, 4 (sounds like 1 device for each)07:44
kota_could be nice to reproduce07:44
kota_the handoff devices in node 3, 4 will have index 0, 4 fragments07:45
claygok, so total number of successful backend responses required to 201 on PUT from a 4+2x2 depends on which frags are in response?  (in the ideal?  or what's in the patch?)07:45
claygwhat's the *bounds*07:46
clayg4 < x < 12 - can we get any tighter?07:46
claygI think 4x2 is 5 (k + 1)07:46
claygs/4x2/standard ec 4+2/07:47
kota_clayg: sorry, I may not get the question07:48
kota_ah07:48
kota_you means # of quorum?07:49
kota_ah, 5, ec_k + 1 IIRC07:50
claygyeah - my 4+2x2 also returns 507:50
kota_but the 5 should be unique07:50
clayg*interesting*07:50
kota_oops!???07:55
kota__check_failure_put_connections doesn't care about frag_index???07:56
claygkota_: https://gist.github.com/clayg/36c87fc8fdb07bff70f7160828725e9508:00
claygwith lack list I get a #4 :D08:01
kota_clayg: great :D08:03
kota_and you may point out good catch08:03
*** tonanhngo has joined #openstack-swift08:03
kota_i think it could happen, iif we have no handoffs and get connected with 3 indexes and 3 duplicate indexes (e.g. 0, 1, 2, 0, 1, 2) > 5 could result in success???08:03
kota_even if it's compltely no durable.08:04
*** tonanhngo has quit IRC08:04
claygidk, up until an hour ago I wasn't even considering the case where you might connect to < total frags nodes08:05
kota_ok08:05
kota_it could be, need to try to make sure.08:06
claygfor all the time I spend worrying about how long it takes to 404 a HEAD request on EC - thinking about *less* disks isn't really on my radar08:06
kota_GET?08:08
claygsure 404 on GET is just as bad08:08
kota_got it08:08
claygbecause node_iter tends to not run out08:08
claygin practice08:08
claygunlike in our dev environments08:08
claygI think quorum for ec should be * duplication_factor08:10
claygdodge that bullet08:10
*** rledisez has joined #openstack-swift08:11
kota_clayg: might be08:12
kota_for now, it's just ec_k I'm making sure now.08:12
kota_make sure the code08:13
*** david-lyle_ has quit IRC08:28
*** chlong has quit IRC08:30
*** chlong has joined #openstack-swift08:31
*** winggundamth__ has joined #openstack-swift08:32
*** stevemar has quit IRC08:33
*** winggundamth_ has quit IRC08:35
*** stevemar has joined #openstack-swift08:35
claygkota_: I don't think it was such a great idea to bring in those reconstructor changes from my WIP08:36
claygthere's a lot of untested branches in that change :\08:36
clayglike I think it might be better than what's on master - but it might have bugs and be hard to maintain if it's not tested?08:36
*** oshritf has joined #openstack-swift08:49
*** tqtran has joined #openstack-swift08:52
*** tqtran has quit IRC08:56
*** kei_yama has quit IRC08:58
openstackgerritChristian Schwede proposed openstack/swift master: Fix timing test error when rebalancing  https://review.openstack.org/43066009:01
*** xlucas has joined #openstack-swift09:01
*** Shashikant86 has joined #openstack-swift09:17
*** jordanP has joined #openstack-swift09:21
*** oshritf has quit IRC09:29
*** oshritf has joined #openstack-swift09:29
*** openstackgerrit has quit IRC09:34
*** links has quit IRC09:35
*** gabor_antal_km has joined #openstack-swift09:35
*** Shashikant86 has quit IRC09:37
*** sanchitmalhotra1 has joined #openstack-swift09:37
*** JimCheung has joined #openstack-swift09:39
*** clayg_ has joined #openstack-swift09:40
*** ChanServ sets mode: +v clayg_09:40
*** Guest66676 has joined #openstack-swift09:41
*** JimCheung has quit IRC09:43
*** bobby2_ has joined #openstack-swift09:43
*** topol_ has joined #openstack-swift09:44
*** dims_ has joined #openstack-swift09:44
*** cschwede_ has joined #openstack-swift09:44
*** mlanner_ has joined #openstack-swift09:44
*** hugokuo_ has joined #openstack-swift09:45
*** timur has joined #openstack-swift09:45
*** jordanP has quit IRC09:45
*** SkyRocknRoll has quit IRC09:45
*** dims has quit IRC09:45
*** gabor_antal_ has quit IRC09:45
*** jtomasek has quit IRC09:45
*** sanchitmalhotra has quit IRC09:45
*** pdardeau has quit IRC09:45
*** topol has quit IRC09:45
*** aj701_ has quit IRC09:45
*** hoonetorg has quit IRC09:45
*** timss has quit IRC09:45
*** cschwede has quit IRC09:45
*** mmmucky has quit IRC09:45
*** timur_ has quit IRC09:45
*** bobby2 has quit IRC09:45
*** ntata has quit IRC09:45
*** clayg has quit IRC09:45
*** hugokuo has quit IRC09:45
*** balajir has quit IRC09:45
*** Guest66666 has quit IRC09:45
*** mlanner has quit IRC09:45
*** mlanner_ is now known as mlanner09:45
*** hugokuo_ is now known as hugokuo09:45
*** balajir_ has joined #openstack-swift09:45
*** oshritf has quit IRC09:46
*** mmmucky has joined #openstack-swift09:46
*** ntata has joined #openstack-swift09:46
*** sanchitmalhotra1 is now known as sanchitmalhotra09:46
*** aj701 has joined #openstack-swift09:46
*** Shashikant86 has joined #openstack-swift09:50
*** links has joined #openstack-swift09:51
*** pdardeau has joined #openstack-swift09:51
*** SkyRocknRoll has joined #openstack-swift09:52
*** timss has joined #openstack-swift09:52
*** jordanP has joined #openstack-swift09:52
*** jtomasek has joined #openstack-swift09:52
*** oshritf has joined #openstack-swift09:54
*** hoonetorg has joined #openstack-swift09:54
*** Shashikant86 has quit IRC09:55
*** Shashikant86 has joined #openstack-swift09:56
*** oshritf has quit IRC10:03
clayg_kota_: it's looking good!10:06
kota_clayg_: :D10:07
kota_clayg_: are you still around!?10:07
clayg_kota_: I think you should consider increasing the quorum size10:07
kota_clayg_: yeah, I was thinking on that, and just trying to make it (k + 1) * duplication10:08
clayg_kota_: yeah i like that - only hit a couple of tests - just needed to dial back some ... it's in the a gist in the review somewhere10:08
kota_it looks like only 2 tests at proxy/controllers/test_obj.py failed with the setting, but no failures on proxy/test_server.py10:08
kota_clayg_: it seems we're doing same thing :\10:09
clayg_is it wierd that you can make that kind of change to a "fundemental constraint" and only a couple of minor spurious unrelated tests fail?10:09
clayg_idk, maybe not - i wonder how many tests fail if you jerk around quorum in replicated10:09
kota_maybe we *want* to add more tests for *really* strict case less than quorum but more than ec_k.10:12
*** dmorita has joined #openstack-swift10:13
kota_i think almost of tests addresses less than ec_k which should not fail because they're consistent the new quorum10:13
kota_so it should fail anyway10:13
kota_s/it/they10:13
clayg_yeah making replicated quorum +1 fails a lot - making it -1 much fewer tests notice10:14
*** Shashikant86 has quit IRC10:15
clayg_I like proxy.controllers.test_obj - stuff like test_PUT_with_just_enough_durable_responses10:15
*** dmorita has quit IRC10:17
clayg_I think (k + 1) * duplication prevents a lot of worry10:17
clayg_i think maybe you depend on the duplication like replication - just because [201, 503, 503] in triple replica *can* fully rebuild - doesn't mean it's durable enough to trust10:18
*** Shashikant86 has joined #openstack-swift10:18
kota_clayg_: i agree with increasing quorum rather than worrying with current one for data loss after 201. we could have more efficiency in the future (check the unique indexes count) but set it as in the future.10:21
clayg_werd10:21
*** clayg_ is now known as clayg10:22
kota_so I'll try to read/address on your comments and push a new version maybe either today or tommorow.10:23
*** dmorita has joined #openstack-swift10:29
kota_ah, you already found the way to fix the failed tests (e.g. test_DELETE_mostly_not_found) with increasing duplication factor10:29
kota_nice10:29
kota_what i will do is just merging and testing in local10:30
*** dmorita has quit IRC10:33
claygkota_: other thing is either pull out the fixes in reconstructor or add tests for them10:40
*** winggundamth__ has quit IRC10:49
*** links has quit IRC10:50
kota_clayg: ok10:50
*** sams-gleb has quit IRC10:56
*** sams-gleb has joined #openstack-swift10:57
*** tanee is now known as tanee_away11:00
*** sams-gleb has quit IRC11:01
*** acoles_ is now known as acoles11:02
kota_hah? It looks like I hit the bug cschwede_ is trying to solve at https://review.openstack.org/430660?11:05
patchbotpatch 430660 - swift - Fix timing test error when rebalancing11:05
clayg+A it!11:05
kota_the report said11:06
-kota_- AssertionError: '1 hours (1:00:00 remaining)' not found in 'No partitions could be reassigned.\nThe t11:06
-kota_- ime between rebalances must be at least min_part_hours: 1 hours (0:59:59 remaining)\n'11:06
*** links has joined #openstack-swift11:06
kota_clayg: is it same bug?11:06
claygyeah11:06
claygwell - same error output11:06
claygwe could easily make that same bug in more than one test11:07
kota_k, I should look at it first to add my +A11:07
*** saltsa has quit IRC11:11
*** silor has joined #openstack-swift11:14
*** dmorita has joined #openstack-swift11:18
*** sams-gleb has joined #openstack-swift11:18
*** ganders has joined #openstack-swift11:22
*** dmorita has quit IRC11:23
kota_done!11:24
*** silor1 has joined #openstack-swift11:31
*** silor has quit IRC11:32
*** silor1 is now known as silor11:32
*** mvk has quit IRC11:53
*** Shashikant86 has quit IRC11:56
*** Shashikant86 has joined #openstack-swift12:01
*** Shashikant86 has quit IRC12:01
kota_hmm, i got a weird report when adding logger assertion, 'Unable to get enough responses (27/10) :/12:02
kota_probably, it's from handoff retry to get in reconstruct12:03
*** silor has quit IRC12:03
*** silor has joined #openstack-swift12:04
*** silor1 has joined #openstack-swift12:07
kota_ah... no?12:08
*** silor has quit IRC12:09
*** silor1 is now known as silor12:09
*** oshritf has joined #openstack-swift12:12
*** dmorita has joined #openstack-swift12:18
*** mvk has joined #openstack-swift12:21
*** Shashikant86 has joined #openstack-swift12:21
*** dmorita has quit IRC12:22
*** SkyRocknRoll has quit IRC12:35
*** MVenesio has joined #openstack-swift12:38
*** acoles is now known as acoles_12:47
*** acoles_ is now known as acoles12:53
kota_hmm... it's time I should leave office...12:56
*** mvk has quit IRC13:04
*** dmorita has joined #openstack-swift13:06
*** psachin has quit IRC13:07
*** catintheroof has joined #openstack-swift13:08
*** dmorita has quit IRC13:10
*** klamath has joined #openstack-swift13:13
*** mvk has joined #openstack-swift13:17
*** openstackgerrit has joined #openstack-swift13:35
openstackgerritMerged openstack/swift master: Fix timing test error when rebalancing  https://review.openstack.org/43066013:35
*** links has quit IRC13:39
*** silor has quit IRC13:42
*** dmorita has joined #openstack-swift13:42
*** oshritf has quit IRC13:46
*** dmorita has quit IRC13:47
eranromgreetings: does anybody know if a container's read-acl can be set from the openstack cli?13:55
*** oshritf has joined #openstack-swift13:55
*** tongli has joined #openstack-swift13:59
eranromLooking at the code, it seems like the answer is no.14:00
*** stradling has joined #openstack-swift14:02
*** dmorita has joined #openstack-swift14:07
*** Shashikant86 has quit IRC14:10
*** Shashikant86 has joined #openstack-swift14:11
*** dmorita has quit IRC14:11
*** oshritf has quit IRC14:23
*** oshritf has joined #openstack-swift14:26
*** oshritf has quit IRC14:29
*** Shashikant86 has quit IRC14:29
*** oshritf has joined #openstack-swift14:32
*** Shashikant86 has joined #openstack-swift14:34
*** ganders has quit IRC14:34
*** Shashikant86 has quit IRC14:37
*** JimCheung has joined #openstack-swift14:38
*** ganders has joined #openstack-swift14:43
*** JimCheung has quit IRC14:43
*** Shashikant86 has joined #openstack-swift14:43
*** dmorita has joined #openstack-swift14:43
*** dmorita has quit IRC14:47
*** dosaboy_ is now known as dosaboy14:50
*** oshritf has quit IRC14:51
*** oshritf has joined #openstack-swift14:53
*** tonanhngo has joined #openstack-swift15:01
*** Shashikant86 has quit IRC15:01
*** tonanhngo has quit IRC15:02
*** dmorita has joined #openstack-swift15:07
*** sams-gleb has quit IRC15:08
*** sams-gleb has joined #openstack-swift15:08
*** oshritf has quit IRC15:09
*** dmorita has quit IRC15:12
*** stradling has quit IRC15:12
*** sams-gleb has quit IRC15:13
*** mvk has quit IRC15:14
*** caiobrentano has joined #openstack-swift15:15
*** tongli has quit IRC15:16
*** gabor_antal_km is now known as gabor_antal15:19
*** chsc has joined #openstack-swift15:19
*** chsc has joined #openstack-swift15:19
*** sams-gleb has joined #openstack-swift15:25
*** chsc has quit IRC15:30
*** tongli has joined #openstack-swift15:31
*** philipw has quit IRC15:32
*** hurricanerix has joined #openstack-swift15:38
*** stradling has joined #openstack-swift15:39
*** _JZ_ has joined #openstack-swift15:40
*** mvk has joined #openstack-swift15:42
*** dmorita has joined #openstack-swift15:56
*** dmorita has quit IRC16:00
*** Shashikant86 has joined #openstack-swift16:03
*** dmorita has joined #openstack-swift16:10
*** dmorita has quit IRC16:14
*** SkyRocknRoll has joined #openstack-swift16:26
*** ganders has quit IRC16:32
*** dmorita has joined #openstack-swift16:34
*** silor has joined #openstack-swift16:37
*** dmorita has quit IRC16:38
*** rcernin has quit IRC16:39
*** chsc has joined #openstack-swift16:41
*** chsc has joined #openstack-swift16:41
*** nickchase has joined #openstack-swift16:42
nickchaseHey, all, can anybody tell me if there's anything new for Swift between the Newton and Ocata releases?16:43
tdasilvanickchase: hi, there has been two swift releases since the newton release. The changelog details what went in: https://github.com/openstack/swift/blob/master/CHANGELOG16:46
tdasilvanickchase: there will also be another release (2.13) before the ocata release16:46
*** silor has quit IRC16:46
*** silor has joined #openstack-swift16:46
tdasilvacoincidentally i believe notmyname said the deadline for that is 2/1316:47
nickchasetdasilva: Awesome.  Thanks so much!16:52
*** Guest66676 is now known as Guest666616:53
*** nickchase has left #openstack-swift16:54
*** stradling has quit IRC16:55
*** tonanhngo has joined #openstack-swift16:56
*** tonanhngo has quit IRC16:56
*** ganders has joined #openstack-swift16:57
notmynamegood morning16:57
notmynamehmm...my IRC bouncer is dropping messages. what I see in my client is not complete when compared to the eavesdrop bot16:58
*** Shashikant86 has quit IRC16:59
*** stradling has joined #openstack-swift16:59
*** stradling has quit IRC17:05
*** tesseract has quit IRC17:05
*** tqtran has joined #openstack-swift17:06
*** silor1 has joined #openstack-swift17:06
*** delattec has joined #openstack-swift17:07
*** delatte has quit IRC17:08
*** silor has quit IRC17:08
*** silor1 is now known as silor17:08
*** tqtran has quit IRC17:10
notmynametdasilva: thanks for responding to nick. my bouncer completely missed that conversation17:11
notmynameare there any cores who are *not* going to be at the PTG?17:19
notmynamehere's why I ask...17:19
notmynamethe foundation is inviting PTLs to give a project update in boston. as part of that, they are giving me the chance to put down 2 cores who will get free registration codes for boston17:20
notmynamehowever, if you're going to the PTG, you'll already get a free code for boston anyway17:21
notmynameso if someone isn't going to the PTG but likely going to the boston summit, I'd like to know17:21
*** MVenesio has quit IRC17:24
tdasilvanotmyname: did mattoliverau say if he was going? i remember he was looking into it17:25
notmynameyeah, he'll be at the PTG for wed-fri17:25
notmynamehonestly, if I recommended only one of the events for a dev to attend, it would be the PTG instead of the summit (since AFAIK there won't be any rooms for projects in boston)17:26
*** JimCheung has joined #openstack-swift17:32
*** topol_ is now known as topol17:33
openstackgerritJoel Wright proposed openstack/swift master: Add Preamble and Postamble to SLO and SegmentedIterable  https://review.openstack.org/36537117:35
*** dmorita has joined #openstack-swift17:36
*** dmorita has quit IRC17:36
*** dmorita has joined #openstack-swift17:36
acolesnotmyname: is joel going?17:37
*** dmorita has quit IRC17:37
*** rledisez has quit IRC17:37
notmynameacoles: that is a great question. I don't know17:37
acoleshe's not here right now17:38
* tdasilva wonders if OVH guys are going...17:38
*** dmorita has joined #openstack-swift17:41
*** joeljwright has joined #openstack-swift17:41
*** ChanServ sets mode: +v joeljwright17:41
*** klrmn has joined #openstack-swift17:44
notmynamejoeljwright: we were just talking about you!17:48
notmynamejoeljwright: are you going to the PTG? or the boston summit?17:48
joeljwrightI'm not going to the PTG, Boston is undecided17:48
joeljwrightIt all depends on whether we'll have any chance for developer stuff in Boston17:49
notmynamejoeljwright: ok. mind if I put you down for a free ticket to boston? (PTG attendees will get one, I'm told, but I've been given the opportunity to put down a couple of names for boston tickets)17:49
joeljwrightthat would be great!17:50
notmynamejoeljwright: I don't know about dev stuff. I don't think there will be any room for swift (or any project), but I think there will be ops sessions.17:50
notmynamejoeljwright: ok, I'll add you17:51
joeljwrightI'm sure people will still find time to discuss things :)17:51
notmynamejoeljwright: as clayg's said before, get a few swift devs in the same city and see if a hackathon doesn't break out17:51
notmynamemaybe if it all gets too expo-hall-ish, we can just catch a train up to tdasilva's house and get some work done ;-)17:52
joeljwright:)17:52
joeljwrightnotmyname: is there a swift meeting today?17:56
notmynameyes. clay has an ops question to raise, and we need to be winding down on the ocata release. also we'll emphasize the ptg planning etherpad17:57
notmynameoops. I didn't update the date on the wiki17:57
notmynameok, done17:57
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873617:58
joeljwrightnotmyname: that's why I asked :)17:58
*** jamielennox is now known as jamielennox|away18:00
*** tqtran has joined #openstack-swift18:04
openstackgerritJoel Wright proposed openstack/swift master: Add Preamble and Postamble to SLO and SegmentedIterable  https://review.openstack.org/36537118:05
tdasilvanotmyname: sounds like a great deal!18:15
joeljwrighttdasilva: I'm sold on the plan already18:15
timburkeeranrom: yeah, my understanding (when last i looked at it) was that OSC doesn't support sending arbitrary headers18:15
*** dmorita has quit IRC18:16
tdasilvajoeljwright: i'll fire up the grill and we'll have some great food with that :)18:16
joeljwright:)18:17
*** acoles is now known as acoles_18:18
*** fbo has quit IRC18:21
*** dmorita_ has joined #openstack-swift18:25
timburkei... what? i go to add a reviewer on a patch, get the error message "Invalid authentication method. In order to authenticate, prefix the REST endpoint URL with /a/ (e.g. http://example.com/a/projects/)."18:30
*** stradling has joined #openstack-swift18:35
*** robcresswell has quit IRC18:35
*** kmARC has quit IRC18:35
*** kozhukalov has quit IRC18:35
*** amit213 has quit IRC18:35
*** ogelbukh has quit IRC18:35
*** janonymous has quit IRC18:35
*** ediardo has quit IRC18:37
*** DuncanT has quit IRC18:37
*** cargonza has quit IRC18:37
*** AndyWojo has quit IRC18:37
*** nottrobin has quit IRC18:45
*** serverascode has quit IRC18:45
*** tonanhngo has joined #openstack-swift18:45
*** tonanhngo has quit IRC18:47
*** tonanhngo has joined #openstack-swift18:48
*** stradling has quit IRC18:52
*** stradling has joined #openstack-swift18:53
notmynametimburke: have you considered using a valid authentication method?19:00
*** ChubYann has joined #openstack-swift19:05
eranromtimburke: yep. that is what I saw. Thanks.19:21
*** nottrobin has joined #openstack-swift19:29
claygis there a meeting today!?19:31
*** DuncanT has joined #openstack-swift19:31
notmynamethere is! hooray!19:31
claygjrichli: those probetests failures are with handoffs_first enabled in your saio configs maybe?19:31
*** serverascode has joined #openstack-swift19:32
claygi mean maybe not - they may just be flaky/broken?19:32
jrichliI didn't change my config for that patch yet.  so, not enabled.19:32
*** nikivi has joined #openstack-swift19:32
claygjrichli: k, i'll try to confirm - do they work for you on master currently?19:33
jrichliso they dont fail for you?  i will look more closely19:33
claygwe land stuff that breaks probetests not infrequently19:33
jrichliclayg: lol, yes.  i will check19:33
claygjrichli: no i'm sorry - i haven't confirmed that - i will19:33
*** kozhukalov has joined #openstack-swift19:33
*** jordanP has quit IRC19:34
*** DuncanT has quit IRC19:35
jrichliclayg: i just ran one on a different vm, with the patch, and it succeeded.  looking farther ...19:41
*** ogelbukh has joined #openstack-swift19:47
jrichliclayg: one difference is it is failing with replication as default, but succeeding for EC.  but your changes wouldnt have affected repl path ... so, doubtful that is the thing19:47
*** DuncanT has joined #openstack-swift19:51
*** SkyRocknRoll has quit IRC19:54
*** ganders has quit IRC19:54
*** tonanhngo has quit IRC19:54
*** robcresswell has joined #openstack-swift19:55
claygjrichli: probetests are the most fun thing evar!19:58
jrichliclayg: that they are!  so ... repl vs. ec as default wasn't the thing.  so far, test_replication_servers_working.py:TestReplicatorFunctions.test_main fails on both the vms i have tried20:02
jrichliclayg: doh!  that one does fail against master!20:07
*** stradling has quit IRC20:07
*** tonanhngo has joined #openstack-swift20:08
*** mrda has left #openstack-swift20:09
*** cargonza has joined #openstack-swift20:10
*** amit213 has joined #openstack-swift20:11
jrichliclayg: yes, i can get both the failures against master.  I will remove my -l and keep looking at how to fix those.20:12
*** ediardo has joined #openstack-swift20:12
*** AndyWojo has joined #openstack-swift20:13
*** jordanP has joined #openstack-swift20:13
*** janonymous has joined #openstack-swift20:14
claygjrichli: you can leave it -1 - i never got around to updating it to deprecate support for handoffs_first in favor of handoffs_only20:16
*** kmARC has joined #openstack-swift20:19
*** jordanP has quit IRC20:19
jrichliclayg: ok.  I haven't proved it yet, but I am thinking it was the "Fix race in new partitions detecting new/invalid suffixes." that introduced one of the failures.20:20
jrichliit complains about a behavior of a hashes.invalid file20:20
claygrofl - that'd be awesome20:20
clayglp bug #1663016 annoyed me this morning - be kind of a soft introduction to db_replicator if someone was so inclined20:25
openstackLaunchpad bug 1663016 in OpenStack Object Storage (swift) "db replicator missing override partitions/devices options" [Medium,Confirmed] https://launchpad.net/bugs/166301620:25
*** foexle has joined #openstack-swift20:27
*** stradling has joined #openstack-swift20:36
*** pcaruana has quit IRC20:43
tdasilvajrichli, clayg: i'm seeing two failures on probetests too20:44
tdasilvaFAIL: test_delete_propagate (test.probe.test_reconstructor_revert.TestReconstructorRevert and test_main (test.probe.test_replication_servers_working.TestReplicatorFunctions20:45
tdasilvaran into this by chance while running probe test for patch 33729720:46
patchbothttps://review.openstack.org/#/c/337297/ - swift - Add support to increase object ring partition power20:46
jrichlitdasilva: oh, thanks.  I just wrote https://bugs.launchpad.net/swift/+bug/1663021 so you can add to that if you like20:46
openstackLaunchpad bug 1663021 in OpenStack Object Storage (swift) "TestReplicatorFunctions probetest fails" [Undecided,New]20:46
notmynamemeeting in5 minutes in #openstack-meeting20:54
claygomg omg omg20:54
claygtdasilva: jrichli: nice work on lp bug #166302120:57
openstackLaunchpad bug 1663021 in OpenStack Object Storage (swift) "TestReplicatorFunctions probetest fails" [Undecided,Confirmed] https://launchpad.net/bugs/166302120:57
*** m_kazuhiro has joined #openstack-swift20:57
mattoliveraumorning20:58
kota_good mornin20:58
mattoliveraukota_: morning20:58
notmynamehello20:59
kota_mattoliverau: o/20:59
notmynamemeeting started in #openstack-meeting21:00
*** acoles_ is now known as acoles21:02
*** stradling has quit IRC21:02
*** joeljwright1 has joined #openstack-swift21:02
*** jamielennox|away is now known as jamielennox21:03
*** stradling has joined #openstack-swift21:05
timburkei've not had good experiences submitting patches to meetbot. notmyname, if *you* want to make #link work inline, godspeed, but i'm not touching it21:05
notmynametimburke: nope21:06
*** silor has quit IRC21:10
*** mmotiani_ has joined #openstack-swift21:22
*** caiobrentano has quit IRC21:30
*** caiobrentano has joined #openstack-swift21:31
*** Jeffrey4l has quit IRC21:34
*** Jeffrey4l has joined #openstack-swift21:34
*** caiobrentano has quit IRC21:35
*** foexle has quit IRC21:39
*** jordanP has joined #openstack-swift21:40
*** mmotian__ has joined #openstack-swift21:41
claygtdasilva: should put a soft -1 or something on the part power until you get the probetest question where you want it21:42
claygI see no reason not to +A this with +2 from timburke mattoliverau and yourself (and anyone else!)21:42
tdasilvaclayg: yeah, trying to figure out right now, but i have a hard stop in 15min today21:43
tdasilvaso if people want to +A that's fine by me, i'll try to add a comment with the failures i'm seeing21:43
mattoliverautdasilva: if you could leave a comment about the probe test, when I get round to the patch today, I'll have a play21:44
tdasilvaok21:44
*** mmotiani_ has quit IRC21:44
timburkein case we ever need a logo for hummingbird, let's use https://en.wikipedia.org/wiki/File:Emu-wild.jpg as a starting point21:59
joeljwright1:D21:59
*** stradling has quit IRC21:59
acolestimburke: nah, https://en.wikipedia.org/wiki/Gibson_Hummingbird#/media/File:Gibson_Hummingbird_2008_-_Vintage_Sunburst.jpeg22:01
*** m_kazuhiro has quit IRC22:01
kota_acoles, timburke: humming bird? https://youtu.be/Jfat_FReZIE?t=92222:03
jrichlii guess these are the proposals?  https://www.youtube.com/watch?v=JmMTCWyY8Y422:06
notmynamejrichli: yeah, those are the rev 1 of them22:06
jrichlii still couldnt find actual links (and attachments were scrubbed for ml history)22:06
claygjrichli: how reliably does test_replication_servers_working fail for you on master?22:07
* kota_ is off for breakfast and will be back at office22:07
claygis test_delete_propagate the one that fails because of ssync and expired objects tombstones22:07
jrichligood question.  i was so focused on testing to find out if it was a particular patch or config option, i haven't done that bit.  will do now22:07
jrichlii just learned of the test_delete_propagate before the meeting from tdasilva22:08
claygit just passed for me on master with ssync - testing again with rsync22:08
claygok, that one failed for me twice in a row22:08
claygbut wasn't one of the two referenced on patch 42549322:09
patchbothttps://review.openstack.org/#/c/425493/ - swift - Make the reconstructor handoffs_first work (and us...22:09
jrichlicorrect, because that one succeeds for me against that patch22:09
claygnotmyname: you might just keep it in your mind that we *do* want to get probetests working before the release in case we do need to backport something22:09
jrichlii updated the bug with some info on that22:09
claygoh right - the bug22:09
mattoliverautimburke: yay emu22:13
notmynamemattoliverau: didn't you lose a war to those?22:14
jrichliclayg: so far, I think i hit the test_replication_servers_working every time against master for both the vms i have been using for this.22:15
*** JimCheung has quit IRC22:15
claygjrichli: try it with ssync - it only started failing for me when I switched to rsync22:17
jrichliclayg: ok, will do22:18
*** acoles is now known as acoles_22:19
jrichliclayg: success!22:22
jrichliwith ssync, that is22:22
*** jordanP has quit IRC22:27
*** sams-gleb has quit IRC22:28
jrichliclayg: rebase of your patch does cause it to fail test_delete_propagate, so i at least have a set of suspect merges22:29
clayginteresting :\22:29
openstackgerritJoel Wright proposed openstack/swift master: Add Preamble and Postamble to SLO and SegmentedIterable  https://review.openstack.org/36537122:33
*** JimCheung has joined #openstack-swift22:37
mattoliveraunotmyname: we actually did, humans lost the emu war ;)22:38
jrichliclayg, tdasilva: I updated the bug with the latest results i know about.  I gotta go now, but will be back on it later.  keep me posted.22:42
claygjrichli: thanks!22:43
*** dmorita_ has quit IRC22:49
*** dmorita has joined #openstack-swift22:49
*** JimCheung has quit IRC23:02
*** joeljwright1 has quit IRC23:02
*** JimCheung has joined #openstack-swift23:02
*** dja has joined #openstack-swift23:09
*** lespaul has joined #openstack-swift23:09
*** tonanhngo has quit IRC23:12
*** joeljwright1 has joined #openstack-swift23:21
*** joeljwright1 has quit IRC23:22
*** catintheroof has quit IRC23:25
*** sams-gleb has joined #openstack-swift23:28
*** mmotian__ has quit IRC23:29
*** sams-gleb has quit IRC23:33
*** chsc has quit IRC23:36
*** kei_yama has joined #openstack-swift23:36
*** JimCheung has quit IRC23:44
*** JimCheung has joined #openstack-swift23:45
*** dja has quit IRC23:46
*** dja has joined #openstack-swift23:48
*** klamath has quit IRC23:52
*** lespaul has quit IRC23:55

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