Tuesday, 2017-02-07

kota_jrichli: the bug you are looking at (https://bugs.launchpad.net/swift/+bug/1662159) looks like to have something related to https://bugs.launchpad.net/swift/+bug/149330300:00
openstackLaunchpad bug 1662159 in OpenStack Object Storage (swift) "TCP leak between proxy and object-server on client disconnection" [Undecided,New]00:00
openstackLaunchpad bug 1493303 in Ubuntu Cloud Archive liberty "[OSSA 2016-004] Swift proxy memory leak on unfinished read (CVE-2016-0738)" [Undecided,Triaged]00:01
kota_jrichli: i don't look at it deelpy yet but the previous bug of proxy memory leak is for slo get, and the bug you are in looks slo put.00:01
jrichlikota_: oh, thanks.  i had looked at a previous bug that we had that was similar, and fixed at the time of encryption footers.  but I didn't see this one.00:01
jrichlikota_: except that when I chatted with jcaron, he said that he could reproduce the issue without slo.00:02
kota_that may be good to dig some of resp or req body iter is closed correctly if the leak is available on your env.00:02
kota_jrichli: ah, ok.00:03
timburkefrom my read, it seemed like slo just made it more obvious, since there would be a bunch of connections00:03
jrichliI have not yet reproduced the issue.  jcaron also has tried using a fresh SAIO and could not.  our going theory is that there is some config value they might run with that is not default.00:03
jrichlitimburke: that is correct00:03
kota_jrichli: kk, it needs more deeper eyes and the way to reproduce00:04
kota_timburke: thx!00:04
jrichliI have looked at the different config options client_timeout and such, and even tested with different values.  but nothing there so far.00:04
kota_jrichli: just notify you to that ;-)00:04
kota_ok00:04
jrichlikota_: Thanks!  I will take a look00:04
jrichliI noticed that we have a "test_PUT_timeout_during_transfer_data" in the test_obj.py which sounds like it should be revealing this issue - or could if we find out what the real trigger is00:05
claygjrichli: when I'm looking for connection leaks I always start with a slow client https://gist.github.com/clayg/a4c96c9b1d5819bf83e700:07
jrichliclayg: thanks!00:07
kota_nice00:08
claygthen I netstat until I have all the connections in my notes - client -> proxy, proxy <- client, proxy -> storage, storage <- proxy00:08
claygthen I KILL things00:08
kota_clayg: hello, sorry for blocking your patch :/00:08
claygkota_: it's no problem!00:08
kota_clayg: but it looks you can read my thought via telepathy00:09
* kota_ is reading the gerrit comment00:09
claygkota_: you explained your concern very clearly - I think it is valid - I think jrichli has a plan to fix everything tho - i'll e fine00:09
kota_I was thinking we could have an option to add "handoff_only" on my bed.00:09
kota_while asleep00:09
clayglol!  that was jrichli!  :D00:09
claygmaybe *she* can read minds!?00:10
jrichliwhat?!  that was clayg.00:10
kota_so +1 to add handoff_only for both of replicator and reconstructor00:10
jrichliI only mentioned the handoff_only because clayg had mentioned it in the commit message :-) and maybe in a comment too00:10
notmynameclayg: do you remember (or still use) the mempeek middleware? do you use that for finding leaks?00:10
kota_either is fine if handoff_first should be deprecated, for now, to me.00:11
claygnotmyname: I only barely remember it - I definately have never used it to troubleshoot an actual memory leak00:11
claygkota_: jrichli: ok, based on your support I may try to spin something up ahead of the meeting00:11
openstackgerritTim Burke proposed openstack/swift master: Prevent traceback in object-server on client disconnect  https://review.openstack.org/41718700:12
claygbut I'm also trying to get a SwiftStack release out this week - and spend more time with global EC!00:12
jrichliclayg: typey, typey!00:12
kota_clayg: yey! I think almost of your concern addressed (or commented) and I have to resolve a (small...??) gate failure which seems freaky00:13
kota_in my global ec00:13
claygkota_: yes - you are a rockstar - I'll make time before bed00:13
kota_clayg: i could have another *crazy* thought for the handoff_first/only mode00:19
kota_clayg: now we're thinking of only *rebalance* cases for that00:19
kota_clayg: but I'm still thinking of global cluster case which could have a lot of handoffs00:20
kota_in a region00:20
kota_so perhaps, the concurrency for each *normal* replicator and *hanoff_only* replicator setting could be nice to have?00:21
kota_e.g. normal * 2 and handoff_only * 1, it prioritize the ratio as 2:1 for primary: handoff00:21
kota_not sure if it's convinient00:22
kota_and it should be futher work after handoff only00:23
kota_future00:23
kota_just my dump of my idea.00:23
claygkota_: that's a great thought!00:41
claygkota_: I've been thinking about a "heartbeat" sort of idea00:42
kota_clayg: k, I'll add it to ptg topics00:42
claygI think hummingbird had something where it tried to target checking one primary part per second - or something like this - a target rate - I could see the target rate for retrying a failed handoff being much higher than the target rate of syncing primaries during a rebalance00:44
*** zaitcev has quit IRC00:45
kota_oh, sounds nice00:45
* kota_ should learn about REPCON protocol00:46
notmynameFYI Intel Avoton chips are bricking some machines (I've seen these for storage, so people in here may be affected http://www.theregister.co.uk/2017/02/06/cisco_intel_decline_to_link_product_warning_to_faulty_chip/00:56
*** JimCheung has quit IRC00:58
*** JimCheung has joined #openstack-swift00:59
kota_hello JimCheung!01:01
kota_JimCheung: sorry my delay for the patch 424353 but it's still in my rader01:01
patchbothttps://review.openstack.org/#/c/424353/ - liberasurecode - Add Phazr.IO libphazr backend to liberasurecode01:01
*** JimCheung has quit IRC01:03
*** caiobrentano has joined #openstack-swift01:22
*** _JZ_ has joined #openstack-swift01:48
*** caiobrentano has quit IRC01:51
*** tqtran has quit IRC01:53
*** winggundamth_ has joined #openstack-swift01:58
*** dmorita has quit IRC02:01
*** dmorita has joined #openstack-swift02:03
*** tanee is now known as tanee_away02:07
*** tanee_away is now known as tanee02:07
*** JimCheung has joined #openstack-swift02:48
*** JimCheung has quit IRC02:55
*** JimCheung has joined #openstack-swift02:56
openstackgerritgengchc2 proposed openstack/swift master: Use https instead of http for git.openstack.org  https://review.openstack.org/43000402:58
*** JimCheung has quit IRC03:08
mahaticgood morning03:15
mahaticclayg: glad they're of help!03:15
mahaticre: reviews03:15
*** JimCheung has joined #openstack-swift03:21
*** kei_yama has joined #openstack-swift03:22
*** links has joined #openstack-swift03:41
*** JimCheung has quit IRC03:51
*** winggundamth has joined #openstack-swift03:58
*** takashi has joined #openstack-swift03:59
*** winggundamth has quit IRC04:04
*** dmorita has quit IRC04:04
*** winggundamth has joined #openstack-swift04:08
*** bkopilov_ has joined #openstack-swift04:12
*** bkopilov has joined #openstack-swift04:12
*** SkyRocknRoll has joined #openstack-swift04:16
jrichliclayg: seems that sleeps in the upload did the trick ;-)04:17
jrichlii dont have a solution yet, but i could reproduce it04:19
*** dmorita has joined #openstack-swift04:23
*** winggundamth has quit IRC04:25
*** dmorita has quit IRC04:27
*** klrmn has quit IRC04:27
*** tonanhngo_ has quit IRC04:47
*** psachin has joined #openstack-swift04:49
*** winggundamth has joined #openstack-swift04:51
*** tonanhngo has joined #openstack-swift04:52
*** adu has joined #openstack-swift04:55
*** winggundamth has quit IRC05:01
*** adu has quit IRC05:03
*** _JZ_ has quit IRC05:05
*** adu has joined #openstack-swift05:11
*** winggundamth has joined #openstack-swift05:20
*** winggundamth has quit IRC05:25
*** dmorita has joined #openstack-swift05:36
*** adu has left #openstack-swift05:36
openstackgerritKota Tsuyuzaki proposed openstack/swift master: EC Fragment Duplication - Foundational Global EC Cluster Support  https://review.openstack.org/21916505:39
*** winggundamth has joined #openstack-swift05:40
*** winggundamth has quit IRC05:45
*** dmorita has quit IRC05:47
*** takashi has quit IRC05:49
*** sams-gleb has joined #openstack-swift05:50
*** tqtran has joined #openstack-swift05:51
*** links has quit IRC05:51
*** sams-gleb has quit IRC05:52
*** tqtran has quit IRC05:55
*** winggundamth has joined #openstack-swift05:58
*** JimCheung has joined #openstack-swift06:00
*** rcernin has joined #openstack-swift06:00
*** dmorita has joined #openstack-swift06:01
*** rcernin has quit IRC06:03
*** rcernin has joined #openstack-swift06:04
*** JimCheung has quit IRC06:05
*** winggundamth has quit IRC06:06
*** dmorita has quit IRC06:07
*** links has joined #openstack-swift06:07
*** mweshi has joined #openstack-swift06:13
*** sams-gleb has joined #openstack-swift06:15
*** links has quit IRC06:22
*** winggundamth has joined #openstack-swift06:26
openstackgerritAnh Tran proposed openstack/swift master: Typo fix: curent => current  https://review.openstack.org/43008506:35
*** links has joined #openstack-swift06:38
*** sams-gleb has quit IRC06:44
*** sams-gleb has joined #openstack-swift06:45
*** winggundamth has quit IRC06:49
jrichliwell, i take it back.  i might not have reproduced the real issue.07:03
*** links has quit IRC07:07
*** mweshi_ has joined #openstack-swift07:12
*** mweshi has quit IRC07:14
*** links has joined #openstack-swift07:19
*** mweshi_ has quit IRC07:20
*** links has quit IRC07:30
*** tesseract has joined #openstack-swift07:31
*** tonanhngo has quit IRC07:36
*** ChubYann has quit IRC07:37
*** links has joined #openstack-swift07:42
*** pcaruana has joined #openstack-swift07:46
*** pcaruana has quit IRC07:48
*** pcaruana has joined #openstack-swift07:55
openstackgerritMerged openstack/swift master: Typo fix: curent => current  https://review.openstack.org/43008507:56
*** jamielennox is now known as jamielennox|away07:59
*** takashi has joined #openstack-swift07:59
*** tonanhngo has joined #openstack-swift08:03
*** tonanhngo has quit IRC08:04
*** jamielennox|away is now known as jamielennox08:06
*** dmorita has joined #openstack-swift08:07
*** dmorita has quit IRC08:12
*** rledisez has joined #openstack-swift08:13
*** kei_yama has quit IRC08:32
*** Shashikant86 has joined #openstack-swift08:42
*** oshritf has joined #openstack-swift08:45
*** Shashikant86 has quit IRC08:46
*** oshritf has quit IRC08:47
*** geaaru has joined #openstack-swift08:49
*** Shashikant86 has joined #openstack-swift08:51
*** tqtran has joined #openstack-swift08:52
*** oshritf has joined #openstack-swift08:54
*** tqtran has quit IRC08:56
*** cbartz has joined #openstack-swift09:03
*** winggundamth has joined #openstack-swift09:16
*** silor has joined #openstack-swift09:17
*** jordanP has joined #openstack-swift09:19
*** winggundamth has quit IRC09:25
*** silor has quit IRC09:32
*** silor1 has joined #openstack-swift09:32
*** silor1 is now known as silor09:34
*** winggundamth has joined #openstack-swift09:34
*** Shashikant86 has quit IRC09:35
*** mariusv has quit IRC09:38
*** mariusv has joined #openstack-swift09:39
*** xlucas has joined #openstack-swift09:42
*** Shashikant86 has joined #openstack-swift09:46
*** winggundamth has quit IRC09:47
*** winggundamth has joined #openstack-swift09:49
*** winggundamth has quit IRC09:54
*** winggundamth has joined #openstack-swift09:55
*** Shashikant86 has quit IRC09:56
*** xlucas has quit IRC09:56
*** Shashikant86 has joined #openstack-swift09:57
*** Shashikant86 has quit IRC10:01
*** Shashikant86 has joined #openstack-swift10:03
*** winggundamth has quit IRC10:03
*** Shashikant86 has quit IRC10:04
*** mariusv has quit IRC10:10
*** winggundamth has joined #openstack-swift10:10
*** winggundamth has quit IRC10:16
*** Shashikant86 has joined #openstack-swift10:17
*** Shashikant86 has quit IRC10:18
*** Shashikant86 has joined #openstack-swift10:23
*** Shashikant86 has quit IRC10:23
*** winggundamth has joined #openstack-swift10:24
*** sams-gleb has quit IRC10:27
*** sams-gleb has joined #openstack-swift10:28
*** jtomasek has joined #openstack-swift10:32
*** sams-gleb has quit IRC10:32
jtomasekHi all, what is the recommended way to duplicate a swift container using API? Only way I see is create a new container and copy all objects to it10:36
*** Shashikant86 has joined #openstack-swift10:36
*** xlucas has joined #openstack-swift10:40
*** oshritf has quit IRC10:43
*** Shashikant86 has quit IRC10:46
*** sams-gleb has joined #openstack-swift10:47
*** geaaru has quit IRC10:53
kota_jtomasek: AFAIK, it's only way to force it. Perhaps container-sync is an option to enable sync your container to another one with out copy for new incomming objects.10:55
kota_jtomasek: the docs for container-sync is http://docs.openstack.org/developer/swift/overview_container_sync.html10:56
jtomasekkota_: ok, thanks, I'll check it10:57
*** SkyRocknRoll has quit IRC10:57
*** geaaru has joined #openstack-swift11:05
*** mvk has quit IRC11:27
*** Shashikant86 has joined #openstack-swift11:28
ahaleperhaps if you wanted to move rather than copy you could use http://docs.openstack.org/developer/swift/overview_object_versioning.html11:37
*** takashi has quit IRC11:56
*** Shashikant86 has quit IRC12:05
*** tonanhngo has joined #openstack-swift12:05
*** tonanhngo has quit IRC12:06
*** mvk has joined #openstack-swift12:07
*** cbartz has quit IRC12:12
*** cbartz has joined #openstack-swift12:13
*** cbartz has quit IRC12:13
*** cbartz has joined #openstack-swift12:15
*** bkopilov_ has quit IRC12:28
*** acoles_ is now known as acoles12:28
*** bkopilov has quit IRC12:28
*** links has quit IRC12:48
*** catintheroof has joined #openstack-swift12:50
*** tqtran has joined #openstack-swift12:53
*** tqtran has quit IRC12:58
*** xlucas has left #openstack-swift13:04
*** xlucas has joined #openstack-swift13:04
*** chlong has joined #openstack-swift13:14
*** klamath has joined #openstack-swift13:24
*** klamath has quit IRC13:24
*** klamath has joined #openstack-swift13:24
openstackgerritMerged openstack/swift master: Fix test_replicator assertion  https://review.openstack.org/42967313:37
*** cdelatte has joined #openstack-swift13:43
*** remix_tj has quit IRC13:45
*** bkopilov_ has joined #openstack-swift13:51
*** bkopilov has joined #openstack-swift13:52
*** remix_tj has joined #openstack-swift13:53
*** cdelatte has quit IRC14:43
*** zaitcev has joined #openstack-swift14:48
*** ChanServ sets mode: +v zaitcev14:48
*** JimCheung has joined #openstack-swift14:53
*** tonanhngo has joined #openstack-swift14:58
*** JimCheung has quit IRC14:58
*** tonanhngo has quit IRC14:58
*** sams-gleb has quit IRC15:03
*** sams-gleb has joined #openstack-swift15:04
*** tqtran has joined #openstack-swift15:04
*** sams-gleb has quit IRC15:08
*** dmorita has joined #openstack-swift15:08
*** dmorita has quit IRC15:13
*** vint_bra has joined #openstack-swift15:13
*** vint_bra has quit IRC15:16
*** sams-gleb has joined #openstack-swift15:21
*** abqkawi1000 has joined #openstack-swift15:30
*** _JZ_ has joined #openstack-swift15:30
*** MVenesio has joined #openstack-swift15:32
*** abqkawi1000 has quit IRC15:33
*** abqkawi1000 has joined #openstack-swift15:34
*** cdelatte has joined #openstack-swift15:40
abqkawi1000joined hoping for some guidance on where I should be looking to fix an auth problem.  Logs in my swift proxy box show "Identity server rejected authorization" "Unable to validate token: Identity server rejected auth necessary to fetch token data.15:44
patchbotError: No closing quotation15:44
*** tonanhngo has joined #openstack-swift15:59
*** cdelatte has quit IRC16:12
*** acoles is now known as acoles_16:14
*** rcernin has quit IRC16:16
*** pcaruana has quit IRC16:17
*** tqtran has quit IRC16:20
*** klrmn has joined #openstack-swift16:29
*** openstackgerrit has quit IRC16:35
notmynamegood morning16:37
notmynamefungi: is this appropriate? https://review.openstack.org/#/c/430004/16:38
patchbotpatch 430004 - swift - Use https instead of http for git.openstack.org16:38
funginotmyname: sure, that's a valid browseable url and we maintain trusted certs for the site16:39
notmynamefungi: kk. thanks16:40
funginotmyname: if you want a more performant git url instead of a browser-oriented one, drop the /cgit from the path16:40
fungithen it will go through the smart git backend rather than the cgit rendering cgi16:41
*** oshritf has joined #openstack-swift16:42
*** oshritf has quit IRC16:44
*** chsc has joined #openstack-swift16:47
*** chsc has joined #openstack-swift16:47
*** cdelatte has joined #openstack-swift16:49
*** psachin has quit IRC16:50
*** tqtran has joined #openstack-swift17:11
*** oshritf has joined #openstack-swift17:26
*** JimCheung has joined #openstack-swift17:27
*** oshritf has quit IRC17:34
*** ganders has joined #openstack-swift17:36
*** mvk has quit IRC17:37
*** nikhil|afk has joined #openstack-swift17:38
*** dmorita has joined #openstack-swift17:41
*** rledisez has quit IRC17:44
*** tonanhngo has quit IRC17:47
*** dmorita has quit IRC18:01
*** tesseract has quit IRC18:01
*** dmorita has joined #openstack-swift18:02
*** silor has quit IRC18:05
claygjrichli: I had posted a lengthy analysis of another socket leak backend connection buffer issue18:10
*** winggundamth_ has quit IRC18:28
jrichliclayg: where?  oh no, you mean the ML?  I guess i should really subscribe to that ...18:29
jrichliI see https://bugs.launchpad.net/swift/+bug/1466549 also was a similar issue in the past18:29
openstackLaunchpad bug 1466549 in OpenStack Object Storage (swift) "[OSSA 2016-004] Download DLO objects leak connections when client kill connection (CVE-2016-0737)" [Undecided,Fix released]18:29
*** openstackgerrit has joined #openstack-swift18:30
openstackgerritChristopher Bartz proposed openstack/python-swiftclient master: ISO 8601 timestamps for tempurl  https://review.openstack.org/42337718:30
timburkeabqkawi1000: i saw a bit of the start of that in -keystone -- looked like swift was sending back a 503? that usually means the proxy was having trouble talking to the backend, like maybe the account server isn't running?18:31
timburkei think it could also mean that swift couldn't validate tokens against keystone; you might want to double check the creds for authtoken middleware and the roles assigned for that user18:32
claygjrichli: i was thinking of my comments on this super old bug https://bugs.launchpad.net/swift/+bug/156865018:33
openstackLaunchpad bug 1568650 in OpenStack Object Storage (swift) "Connection between client and proxy service does not closes" [High,Confirmed] - Assigned to drax (devesh-gupta)18:33
claygafaik it's been confirmed for ~1yr18:33
*** geaaru has quit IRC18:35
*** caiobrentano has joined #openstack-swift18:37
*** cbartz has quit IRC18:49
openstackgerritTim Burke proposed openstack/swift master: Remove per-device reconstruction stats  https://review.openstack.org/42747619:01
jrichliclayg: ok, thanks.  at first glance at the explanations, I can tell that I will need to take some time for a deeper look :-)19:04
*** tonanhngo has joined #openstack-swift19:14
*** tonanhngo has quit IRC19:19
*** ChubYann has joined #openstack-swift19:32
*** xlucas has quit IRC19:33
*** stradling has joined #openstack-swift19:34
*** tonanhngo has joined #openstack-swift19:35
timburketdasilva: does the ring builder have any knowledge of how the ring will be used? i'm not sure it does... all of that information lives in swift.conf, yeah?19:38
openstackgerritMerged openstack/swift master: Use https instead of http for git.openstack.org  https://review.openstack.org/43000419:39
*** ganders has quit IRC19:44
*** ukaynar has joined #openstack-swift19:58
*** jordanP has quit IRC20:13
*** ukaynar_ has joined #openstack-swift20:16
*** ukaynar has quit IRC20:16
tdasilvatimburke: not sure I follow, what info live in swift.conf?20:25
*** ukaynar has joined #openstack-swift20:35
*** ukaynar_ has quit IRC20:35
*** caiobrentano_ has joined #openstack-swift20:46
timburketdasilva: mapping from ring file to whether it's being used for acct, cont, or obj20:47
*** jordanP has joined #openstack-swift20:48
timburkelike, i don't think we *can* have the ring builder prevent you from trying to increase the part_power of an acct/cont ring -- i don't think it has enough information to know that20:48
*** joeljwright has joined #openstack-swift20:49
*** ChanServ sets mode: +v joeljwright20:49
*** caiobrentano has quit IRC20:49
*** caiobrentano_ has quit IRC20:50
tdasilvatimburke: Yes, I agree, but my concern was more out of practicality thinking of operators. The documentation talks about increasing partition power and it mentions objects, but it says nothing about account or containers20:55
timburkesure. yeah, i agree that we probably want to be more explicit in the docs20:55
claygtimburke: it's more like if we decide later to drop the whole function and punt to a library - someone is going to say "what about aarch64 - did anyone test it" - and then we're stuck with the reality that noone who is able to maintain the feature/moddule *ever* tested it on aarch6420:55
tdasilvacan we assume that operators just know that they can't increase part power for account and container rings?20:56
*** ukaynar has quit IRC20:56
claygif we're not going to run it test it - i don't see how we can "support/maintain" it - how can we validate the use-case still works if we want to change the implementation?20:56
*** ukaynar has joined #openstack-swift20:56
claygtimburke: again, i'm all for fixing the tests20:57
*** adu has joined #openstack-swift20:57
claygI think the unittest failure is pointing at bad coupling - using good clean pactching to avoid ties to the system running the tests squares that and the feature continues to work as it was written20:58
timburkeclayg: same way we're doing it right now -- the thing *isn't supported* -- there's no update to the README or docs or setup.cfg implying otherwise. so if we need to change some implementation details, we change it and see if anyone balks21:00
timburkewhich is how we got where we are *right now*. he's not asking for full and proper support; he's asking for unit tests to pass. and if we can get unit tests pass *and* move closer to full and proper support, that seems better than papering over the issue and not knowing how well our tests reflect reality21:00
claygi included a diff to fix the unittests21:00
claygi think it's objectively better than the purposed change21:00
claygI think if mattoliverau or torgomatic want to +A it i'm over it21:01
claygbut I also think if someone wants to change how io_prio/nice settings work - i'm going to send it your way to validate the change still works on aarch64 ;)21:01
claygthat's acctually my only beef - if I had a good way to validate the change on aarch64 I think I could "support" maintaining the subsystem on that arch - so i'd be find merging support - because I can test it?21:02
claygidk, it doesn't seem insane to me21:02
*** jordanP has quit IRC21:03
claygbut I think choosing to do that should be orthogonal to fixing the test coupling with the aarch running the tests - i feel like i've said this - my argument is clear - but I see no reason that anyone should feel compelled to agree with me21:03
claygi recognize the desire to "be helpful and merge things that people *in the communitiy like*" is very strong21:03
claygand my threshold for YAGNI is maybe higher21:03
claygit's totally subjective judgement21:04
*** caiobrentano has joined #openstack-swift21:14
claygtimburke: related to some of the stats output thread stuff you've been working on -> lp bug #166267221:18
openstackLaunchpad bug 1662672 in OpenStack Object Storage (swift) "db replicator missing stats output" [Undecided,New] https://launchpad.net/bugs/166267221:18
claygtdasilva: timburke: the part_power_increase relating to account/container sounds like a hozer21:20
claygtdasilva: timburke: you could add something in some of the background ring reloading for a/c services to warn if they encounter something that looks part-power-increase-y21:21
claygtdasilva: timburke: the relinker guy should know enough to error if you tried to envoke it on a non object ring21:21
claygyou could *warn* in the CLI if you try to do something part-power-increase-y on a ring named account/container - or maybe even anything not `object[-X]` ?21:22
timburkeclayg: so how do you feel about the proprietary backends for libec? or, for that matter, jerasure? wasn't that part of your beef with https://review.openstack.org/#/c/425471/ -- "it's not something i care about and i'm not sure how to test it" so why have that support at all?21:22
patchbotpatch 425471 - liberasurecode - Make free_rs_cauchy_desc tolerate partially-initia...21:22
tdasilvaclayg: yeah, i was leaning towards the cli warning, it seems prudent to me21:24
claygtimburke: honestly my stance on jerasure is somewhat weak - being that it's a open source library and I'm a core maintainer for liberasurecode - at *some level* I should feel obliged to maintain jerasure support21:24
clayg... but the reality is it has to sit below the already lowered capacity I have to prioritize changes for libec in general compared to ... e.g. upstream swift21:24
timburkeclayg: the relinker is already smart enough to only look at object policies -- and it looks at all of them, checking if any seem to be in that transition state21:24
timburkeyou literally *can't* run it against an account/container ring21:25
*** delattec has joined #openstack-swift21:25
claygtimburke: but for something like Phzer.IO or w/e it's called - yeah i'm *super* nervous we can't test it - I *don't* think we should merge support - I think we should talk to Neutron and Cinder about how plugins to proprietary code is bad for everyone and what alternatives are available21:25
*** cdelatte has quit IRC21:26
claygtimburke: RE relinker - NICE21:26
claygtdasilva: yeah a warning can't hurt - and something in the docs that goes out of it's way to explicitly state "i'm not sure where you might have got the idea this is related in anyway to a/c - but it is not - you can not increase part power on a/c"21:27
clayg... of course cschwede probably already a plan underway :P21:27
tdasilvatimburke: nice catch on symlink patch, I had not noticed that subtle change: https://review.openstack.org/#/c/232162/51/swift/common/middleware/symlink.py@24721:30
patchbotpatch 232162 - swift - Symlink implementation.21:30
*** jordanP has joined #openstack-swift21:32
mattoliveraumorning, I'm back and I didn't sink or die while driving home.. now just have like a bazillion emails to catch up on.21:34
notmynamewelcome back mattoliverau :-)21:35
notmynamemattoliverau: finally back to the stressful beach life after so many weeks away?21:35
*** Jeffrey4l has quit IRC21:35
notmynamemattoliverau: I have an ansible question for you that I hope you can help me with21:36
*** Jeffrey4l has joined #openstack-swift21:36
notmynamemattoliverau: in a role, I've got the mail.yaml. but there's a set of functionality that takes several tasks to do that I feel like should be in a different file. how do I "call" that different file from main.yaml?21:36
*** MVenesio has quit IRC21:37
mattoliverauyup, first time here this year21:37
mattoliveraucan't wait to get down to the beach!21:37
*** jordanP has quit IRC21:37
mattoliveraunotmyname: you can just create the other file in say the tasks folder, then simply include it. Where you include it in the file is where it'll play from21:38
notmynameoh ok21:38
mattoliveraunotmyname: example coming21:38
mattoliveraunotmyname: https://github.com/matthewoliver/swift-ansible/blob/master/roles/swift_common/tasks/main.yml#L7-L1521:39
notmynamemattoliverau: I see. thanks21:40
mattoliverauare a bunch of include examples, the files they include you'll find in the tasks dir21:40
*** jamielennox is now known as jamielennox|away21:42
*** catintheroof has quit IRC21:48
*** catintheroof has joined #openstack-swift21:49
*** ukaynar has quit IRC21:53
*** catintheroof has quit IRC21:54
*** ukaynar has joined #openstack-swift21:55
*** xlucas has joined #openstack-swift21:56
*** tesseract has joined #openstack-swift21:59
*** tesseract- has joined #openstack-swift22:00
*** jcaron1 has joined #openstack-swift22:06
*** xlucas has quit IRC22:06
*** tesseract has quit IRC22:07
*** tesseract- has quit IRC22:07
*** tesseract has joined #openstack-swift22:08
*** jcaron has quit IRC22:10
*** sams-gleb has quit IRC22:11
*** sams-gleb has joined #openstack-swift22:22
*** tesseract is now known as tesseract-RH22:26
*** tesseract-RH is now known as tesseract22:31
*** caiobrentano has quit IRC22:35
*** stradling has quit IRC22:36
*** jamielennox|away is now known as jamielennox22:42
*** sams-gleb has quit IRC22:57
*** sams-gleb has joined #openstack-swift22:58
*** tesseract has quit IRC23:00
*** tesseract has joined #openstack-swift23:00
*** tesseract-RH has joined #openstack-swift23:01
*** tesseract has quit IRC23:01
*** tesseract-RH has quit IRC23:01
*** sams-gleb has quit IRC23:02
*** JimCheung has quit IRC23:13
*** JimCheung has joined #openstack-swift23:13
*** joeljwright has quit IRC23:15
*** kei_yama has joined #openstack-swift23:23
*** chsc has quit IRC23:31
*** stradling has joined #openstack-swift23:33
*** adu has quit IRC23:36
*** klamath has quit IRC23:44
openstackgerritJim Cheung proposed openstack/liberasurecode master: Add Phazr.IO libphazr backend to liberasurecode  https://review.openstack.org/42435323:46
kota_good morning23:54
kota_mattoliverau: welcome back!23:54
kota_clayg, timburke: how's going global ec reviews?23:54
kota_clayg, timburke: can i help you on something to progress (e.g. more fix, more tests or just waiting :P) it?23:55
mattoliveraukota_: morning23:56

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