Wednesday, 2016-09-21

*** jamielennox is now known as jamielennox|away00:00
timburkeclayg: well, transparent in the sense that post-as-copy/fast-post is transparent. you'll definitely know which mode you're in, but with sufficient timeouts, you shouldn't really care00:01
timburkex-versions-location & x-better-versions-location00:01
*** tongli has quit IRC00:02
claygtimburke: oh interesting - i tought something about POSTing somewhere would make something a difference?00:02
claygbut versions + metadata updates makes my head hurt anyway00:03
*** Suyi_ has quit IRC00:03
timburkeclayg: ok, jrichli pointed out earlier today that one of them sends back a body on POST while the other doesn't00:03
timburkemetadata updates aren't versioned! it's great!00:04
claygtimburke: oh yeah that's right - someone was pointing that body/content difference - i thought that was you?00:08
*** jamielennox|away is now known as jamielennox00:14
openstackgerritDarrell Bishop proposed openstack/swift: Add support for PROXY protocol v1 (only)  https://review.openstack.org/37356300:22
*** tqtran has quit IRC00:25
tdasilvahi clayg, timburke i'm back00:38
timburkeyay, more opinions!00:38
tdasilvai just read the scrollback really quickly and my 2 cents on x-stack-container is that i don't see the point of introducing thew new header. the problem is not with the current header name per se, but the functionality it provides. so (IMO) when we talk of deprecating x-versions-location00:40
tdasilvawe are talking about deprecating the functionality, not just the header00:40
tdasilvaso if we ever were to deprecate x-version-location, we would also deprecate x-stack-container...00:40
claygtdasilva: oh that's a good point too - the only thing i hate more than the name of the header is the stack based functionality00:42
claygbut if the name was better I might forget how much I hate it?00:43
tdasilvaclayg: the whole point of introducing history mode was that it was better functionality00:44
claygtdasilva: yeah it is00:45
kota_good morning01:02
mattoliveraukota_: o/01:03
kota_mattoliverau: o/01:03
timburketdasilva: k. so x-versions-location / x-history-container, or x-versions-location / x-history-location?01:04
tdasilvax-history-location???01:07
tdasilvadon't have a really strong opinion on that thou01:07
timburkefor consistency with x-versions-location. should i take that as a vote to stick with "container"?01:08
tdasilvatimburke: not sure i understand your question :(01:09
* mattoliverau has been in a meeting and now has to step out.. bbs01:10
timburkeyou seemed incredulous at x-history-location. or more likely, subtlety is lost in irc ;-)01:10
tdasilvatimburke: what's the chance we can ever get to a point where users don't know about the container where archives are stored?01:10
tdasilvasorry...the question marks was more like "i think x-history-location is better, but really don't have a strong opinion"01:11
timburkeyep, got it. thanks01:11
timburkeon never knowing/thinking about the archive container, it'll probably make for some unhappy users who aren't sure where their usage went...01:12
tdasilvawell, they would have a way of listing versions01:12
tdasilvai'm thinking something more like s301:12
tdasilvawhere you just enable versioning on a bucket01:12
timburkei know you are :-)01:13
tdasilvabut don't specify where archives get stored01:13
tdasilvaheh01:13
timburkeand oh man am i gonna have fun with it in swift301:13
*** McMurlock1 has quit IRC01:13
tdasilvaright, so if you are planning on support that in swift3, would it make sense to have the same in swift?01:14
timburkebut swift allows (nearly) any utf-8 as a container name, so it'll be tricky to hide01:14
tdasilvai mean, is it a better API than what we have? honest question01:14
timburkegenerally? they're just different. i really like the power and reusability of SLOs; S3 can't do that. i rather like how much less you have to think about as a client for S3, though01:16
timburkefor this in particular, i could see some value in having some automated script that rotates out the archive container monthly or something. then you could change who has permission to what based on date range01:17
claygtimburke: if you know of a valid utf-8 container name that we can scope to a clints account - but you can't acctually create via the API - i want to know about it01:20
timburke"a valid ... container name ... you can't actually create via the API" seems like a contradiction01:21
clayglike maybe there's some magic way we could create a container with a "/" *in* the name and still have a world that makes sense?  because god oh dear god how many times I've wished we could carve out "dot containers" like we did "dot accounts"01:22
claygoh I guess you just %2F - stupid urlencoding thought of everything01:23
timburkeyeah, i was thinking about that, too. /v1/a/c%2fstill-part-of-the-container/o would be nice, but we unquote() everything pretty early on as i recall01:23
timburkeand we'd be back to wondering what clients we're gonna break01:24
* kota_ is catching up the conversation for new versioned-write namespaces01:26
kota_tdasilva: AFAIK, swift3 is using "+" for the versions-location container because "+" is not allowed for the bucket name in actual S301:29
timburkeyup01:29
kota_tdasilva: something like "original_container+versioned"01:29
kota_timburke: looking at the back log, we cannot set both x-history-location and x-stack-location at a container, right?01:30
timburkeand there's a similar thing with = in header keys that i'm using to do https://review.openstack.org/#/c/345739/01:30
patchbotpatch 345739 - swift3 - Add support for more characters in header keys01:30
kota_timburke: I'm wondering how we can resolve the not allowed header conbination in the split brain case eventually.01:30
timburkekota_: correct. it will 400 if you try to set both in one request; in separate requests, last write wins01:30
kota_timburke: currently, we are using same header key (i.e. x-versions-location) so that it will be resolved one of them.01:31
claygkota_: because they both resolve to x-versions-location in the data model the last-write-wins is enforced in the consistency engine with no extra code (nice work there timburke !)01:31
kota_mode, too.01:31
claygkota_: yup timburke is only changing the presentation layer - data model stays the same (it's a good data model!)01:32
kota_clayg: gotcha!, nice work, I didn't see the patch yet, just wondering from conversation01:32
kota_clayg: thanks01:32
tdasilvaso is the mode header also hidden from the user?01:33
tdasilvai also have not yet looked at the patch01:33
tdasilva:P01:33
kota_tdasilva: :P01:33
claygtdasilva: afaik it is simply not translated from it's sysmeta location01:34
claygtdasilva: I'm mostly leaning towards x-versions-location and x-history-location (I think?)01:34
claygacctually i'd be fine with x-versions-location and x-history-container01:35
tdasilvaclayg: yeah, i think either works for me01:37
MooingLemurbefore I open a bug on this, was there a reason DLO and SLO do not take Referer auth into account?01:39
MooingLemurSLO fails to do the make_subrequest to fetch the manifest because there's no auth token for the request, and DLO has the same issue but this time it's a container list.01:40
MooingLemuroh well, bug filed. :)01:45
claygHTTP_REFERER is in the make_env list?01:47
claygi thought we even had a functest for public DLO's?01:47
claygwell public *lo's rather01:47
MooingLemurhow about nonpublic ones with a specific referer?01:48
claygi'm sure i'll see the lp bug in my inbox in a minute - i'll read it over make sure i'm understanding what you're saying is not working as expected01:48
claygyeah i'd guess it's less likely we have a specific test for that - so much more possible it's broken - but in some non-obvious way since acl rules would seem to work for public containers and the referer header should be getting copied across to the sub requests01:49
claygshould be easy to duplicate and add a failing functional test for if needed01:50
*** StraubTW has joined #openstack-swift01:50
jrichliclayg: timburke had recently noted an inconsistency in having a body with the 416 case for multiget slos patch 35265701:55
patchbothttps://review.openstack.org/#/c/352657/ - swift - Support multi-range GETs for static large objects.01:55
openstackgerritTim Burke proposed openstack/swift: Use separate headers for versioned_writes' stack and history modes  https://review.openstack.org/37353701:59
MooingLemurclayg: I'm embarrassed to say it may have been fixed between 2.5.0 and 2.7.0.  It appears to behave correctly with 2.7.0.01:59
MooingLemurwithout a patch01:59
claygMooingLemur: you were asking for some other rsync fix to back ported too yeah?02:00
claygMooingLemur: does this mean you're gunna get on the close to master train with the rest of us!?02:01
MooingLemur:)02:01
claygMooingLemur: or just that you're going to continue to advocate for the changes that we should be backporting because we're obviously clueless :P02:01
MooingLemurIn 2.7.0 I have the problem of object-replicator hanging.  I haven't opened anything on that one yet :)02:01
MooingLemurhowever, I do have an open bug that I'm certain still exists in 2.9.0 :)02:02
claygyou mean thats a *new* problem you *didn't* have 2.5.0 (!?)02:02
MooingLemuryes02:03
timburkeMooingLemur: your slo/dlo issue seems to have been fixed in 2.6.0 -- https://github.com/openstack/swift/commit/87f7e9002:04
MooingLemurtimburke: thanks :)02:04
MooingLemurhttps://bugs.launchpad.net/swift/+bug/145443302:04
openstackLaunchpad bug 1454433 in OpenStack Object Storage (swift) "swift-ring-builder does not seem to properly parse setting weights for multiple devices at one time" [Undecided,New]02:04
MooingLemurthat one appears to have happened when swift-ring-builder was being refactored to allow the "new" syntax02:05
claygmattoliverau: you're such a champ!02:06
MooingLemurswift-ring-builder ... set_weight <spec1> <weight> <spec2> <weight> ... # for some reason it parses out spec1 and weight (expanding spec1 into as many devices as it points to), passes them into _set_weight_values, then on the second round of the loop, appends the devices from spec2 into the same devs array without clearing them, and then calls _set_weight_values again, but now it has all of th02:08
MooingLemure devices from spec1 as well as spec2, ...02:09
MooingLemur... and it tries to apply the weight of spec2 to all of it02:09
tdasilvagood night02:10
tdasilvaccccccdkkgthegjdtedcelidgugkjrcluedgjllbeeht02:10
MooingLemurso the devs array gets longer and longer :)  Correct behavior seems to be to assign the value to devs rather than devs.extend02:10
MooingLemurHi, kitty.02:11
kota_tdasilva: good night02:11
MooingLemuractually looks too keyboard mash to be cat typing.  Also it contains "clue" :P02:12
claygMooingLemur: it's probably one of those rsa security key thingy's02:15
MooingLemurclayg: http://www.thinkgeek.com/product/ae83/02:15
claygMooingLemur: and do you *want* this syntax?  Maybe rather than trying to fix that mess which no one is using (successfully) we could take the oppertunity to make the interface closer to something that would be useful?  What's your use-case?02:16
claygMooingLemur: that is *fabulous*02:17
kota_clayg: btw, could you keep attention for my global ec thing?02:19
MooingLemurclayg: I'm claiming the documented syntax: swift-ring-builder <builder_file> set_weight <search-value> <weight> [<search-value> <weight] ... is broken.  It only works if you specify one search value and one weight.  If you specify more than one, it ends up applying the weight of the final search value to *all* of the matched search values including the ones earlier on the command line.02:19
kota_clayg: patch 219165 is now on the master and got +1 from Jenkins, I addressed your items at patch 34303202:20
patchbothttps://review.openstack.org/#/c/219165/ - swift - EC Fragment Duplication - Foundational Global EC C...02:20
patchbothttps://review.openstack.org/#/c/343032/ - swift - Items for EC Duplication to consider02:20
claygkota_: full ack - i'll loop back around to that02:21
kota_clayg: ah, the converstaion is still progress, not urgent right now. just notification.02:21
kota_clayg: thanks02:21
claygMooingLemur: i believe you it's busted - the code there is fully of crufty jank - i'm just thinking the documented (and broken) synax is sort of not that great/useful to begin with02:21
claygi don't want to fix it just because the docs say it work that way - esp if it's broken because it's so terrible to implement and also - not useful02:22
MooingLemurclayg: I can specify one search value and one weight per invocation of swift-ring-builder, however if I'm doing many (hundreds) of weight adjustments (while bringing on new storage), the amount of time to do that process is severely amplified.02:22
claygright obviously - do you need explicit (device, weight) pairs or would [dev, dev, dev, dev] [weight] work in your use-case02:23
MooingLemurit's more useful to do the former, since the script that manages the slow reweighting already has knowledge of each device, its size, and current weight, but if I need to split out the invocations of swift-ring-builder so that I group them by weight assignment, I can do that02:25
MooingLemurbut it seems like a silly limitation02:25
*** _JZ_ has quit IRC02:25
claygis the script that manages the slow reweighting happen to be written in python by any chance?02:26
MooingLemurnope :)02:26
claygone can dream02:26
MooingLemurperl02:26
*** ChubYann has quit IRC02:30
*** dmorita has quit IRC02:40
*** ukaynar has joined #openstack-swift02:42
*** StraubTW has quit IRC02:53
mattoliverau.02:54
mattoliverauclayg: I yeah, I remember that patch, yeah we fixed that referrer thing :)02:54
*** takashi has joined #openstack-swift02:54
mattoliveraualso, for those of you who like me have to participate in many a video conference: https://www.youtube.com/watch?v=DYu_bGbZiiQ02:54
*** dmorita has joined #openstack-swift02:56
*** dmorita has quit IRC03:01
*** winggundamth_ has quit IRC03:03
*** david-lyle has quit IRC03:04
claygmattoliverau: that's pretty good - tyler is my hero - esp when he's in the hallway talk to the wall03:04
mattoliveraulol yeah :)03:06
jrichlimattoliverau: love it!03:15
*** vinsh has joined #openstack-swift03:32
*** chsc has joined #openstack-swift03:37
*** chsc has joined #openstack-swift03:37
*** klrmn has quit IRC03:47
*** chsc has quit IRC03:50
*** ukaynar has quit IRC03:55
*** ukaynar has joined #openstack-swift04:02
MooingLemurclayg: says the developer to the end user "You're using that for WHAT?!" :)04:10
MooingLemurWe encounter a little bit of that internally in our company from time to time. :)04:12
*** ppai has joined #openstack-swift04:33
*** psachin has joined #openstack-swift04:38
*** vinsh has quit IRC04:39
*** psachin has quit IRC04:40
*** psachin has joined #openstack-swift04:41
zaitcevwell you saw that guy yesterday with Swift on top of ZFS04:44
*** psachin has quit IRC04:45
zaitcevSeems like one of the dumbest ideas ever on the surface of it, since you can't access on ZFS side anyway, without swift-on-file anyway04:45
*** psachin has joined #openstack-swift04:47
*** ppai has quit IRC04:59
*** McMurlock1 has joined #openstack-swift05:00
*** McMurlock1 has quit IRC05:09
*** ppai has joined #openstack-swift05:12
*** asettle has joined #openstack-swift05:20
*** wuhg has joined #openstack-swift05:22
openstackgerritMatthew Oliver proposed openstack/swift: Use separate headers for versioned_writes' stack and history modes  https://review.openstack.org/37353705:23
mattoliverautimburke: ^^ Turns out the api-ref's parameters in parameters.yaml need to be in alphabetical order. I just fixed the ordering to Jenkins would pass.05:25
*** tqtran has joined #openstack-swift05:25
*** asettle has quit IRC05:28
*** tqtran has quit IRC05:30
*** SkyRocknRoll has joined #openstack-swift05:38
claygtimburke: lol - I just ran into this today -> https://bitbucket.org/ianb/pastedeploy/pull-requests/13/fix-string-formatting-args-when-raising/diff05:50
*** Jeffrey4l has joined #openstack-swift05:51
clayg... the TypeError ... for which the fix is almost definately laying on my filesystem in saio - then later in an unrelated search I came across your patch!05:52
*** tqtran has joined #openstack-swift05:53
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873606:04
*** rcernin has joined #openstack-swift06:07
*** ppai has quit IRC06:11
*** ukaynar has quit IRC06:33
openstackgerritSharat Sharma proposed openstack/python-swiftclient: Replace MagicMock with Mock class  https://review.openstack.org/37373706:39
*** ppai has joined #openstack-swift06:41
openstackgerritMerged openstack/swift: api-ref: fix some header definitions  https://review.openstack.org/36623206:44
openstackgerritClay Gerrard proposed openstack/swift: Make NullLogger more logger like  https://review.openstack.org/37378406:49
*** kmARC has quit IRC06:49
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873606:49
*** hseipp has joined #openstack-swift06:55
*** kmARC has joined #openstack-swift07:00
claygdo I tell them every with mock.patch() as returns a MagicMock?  lp bug #147572207:05
openstackLaunchpad bug 1475722 in python-neutronclient "Never use MagicMock" [Low,In progress] https://launchpad.net/bugs/1475722 - Assigned to lilintan (lilintan)07:05
*** rledisez has joined #openstack-swift07:06
*** pcaruana has joined #openstack-swift07:13
*** tqtran has quit IRC07:19
*** sams-gleb has joined #openstack-swift07:23
*** silor has joined #openstack-swift07:27
openstackgerritClay Gerrard proposed openstack/swift: Fix unstable json.dumps ordering in obj-server test  https://review.openstack.org/37381907:33
*** dmorita has joined #openstack-swift07:41
*** geaaru has joined #openstack-swift07:43
*** dmorita has quit IRC07:46
openstackgerritzheng yin proposed openstack/python-swiftclient: remove swiftclient/openstack/common/* in the .coveragerc  https://review.openstack.org/37384607:53
openstackgerritKota Tsuyuzaki proposed openstack/swift: Support last modified on listing containers  https://review.openstack.org/19863407:56
*** oshritf has joined #openstack-swift08:03
*** oshritf_ has joined #openstack-swift08:03
*** SkyRocknRoll has quit IRC08:10
openstackgerritKota Tsuyuzaki proposed openstack/swift: Support last modified on listing containers  https://review.openstack.org/19863408:24
kota_Updates my oldest.08:24
*** SkyRocknRoll has joined #openstack-swift08:31
*** kei_yama has quit IRC08:43
*** asettle has joined #openstack-swift08:45
*** mvk has quit IRC09:00
*** acoles_ is now known as acoles09:02
psachinHello #openstack-swift, Deploying account and containers on separate servers for large infrastructure make sense? Is it possible?09:05
*** mvk has joined #openstack-swift09:31
acolesother cores: easy review and worth fixing before release - patch 37381909:34
patchbothttps://review.openstack.org/#/c/373819/ - swift - Fix unstable json.dumps ordering in obj-server test09:34
ahale_psachin, its possible yes, and sometimes a good idea. we keep account and container together but apart from object09:41
ahale_the acc/cont/obj rings are kind of independent , just as long as the ip's can all communicate09:44
*** takashi has quit IRC09:50
*** SkyRocknRoll has quit IRC09:54
psachinahale_: what about the internal communication between account-container and object? Do you suggest dedicated network?09:55
ahale_the proxy needs to be able to hit it all too so idk.. but a dedicated replication network can work. depends on your needs and scale i guess (i dont use dedicated network for different traffic but we do split replication and regular traffic to different listening processes on the same ip)09:58
psachinahale_: Thanx for your suggestions10:06
ahale_np, might get some other ideas later when all the US timezones wake up too :)10:06
*** SkyRocknRoll has joined #openstack-swift10:10
*** tqtran has joined #openstack-swift10:17
*** dabukalam has quit IRC10:19
*** tqtran has quit IRC10:21
*** silor1 has joined #openstack-swift10:35
*** silor has quit IRC10:37
*** oshritf_ has left #openstack-swift10:39
*** silor has joined #openstack-swift10:40
*** silor1 has quit IRC10:40
openstackgerritKota Tsuyuzaki proposed openstack/swift: Support last modified on listing containers  https://review.openstack.org/19863410:43
*** dfflanders has quit IRC10:47
*** Jeffrey4l has quit IRC10:50
*** Jeffrey4l has joined #openstack-swift10:50
*** dabukalam has joined #openstack-swift11:37
*** daemontool has joined #openstack-swift11:39
*** dmorita has joined #openstack-swift11:43
*** dabukalam has quit IRC11:46
openstackgerritAlistair Coles proposed openstack/swift: Add more comment to authtoken sample options  https://review.openstack.org/37257311:46
*** dmorita has quit IRC11:47
*** wuhg has quit IRC12:01
*** dabukalam_ has joined #openstack-swift12:07
*** dabukalam_ has quit IRC12:14
*** dabukalam_ has joined #openstack-swift12:18
openstackgerritTuan Luong-Anh proposed openstack/swift: Fix using filter() to meet python2,3  https://review.openstack.org/36864912:18
*** dabukalam_ has quit IRC12:26
*** ppai has quit IRC12:41
*** david-lyle has joined #openstack-swift12:56
*** acoles is now known as acoles_12:58
*** tgtanya has joined #openstack-swift12:59
*** SkyRocknRoll has quit IRC13:01
*** StraubTW has joined #openstack-swift13:02
*** SkyRocknRoll has joined #openstack-swift13:03
*** dabukalam has joined #openstack-swift13:06
*** dabukalam has quit IRC13:12
*** kei_yama has joined #openstack-swift13:14
*** klamath has joined #openstack-swift13:19
*** psachin has quit IRC13:21
*** dabukalam has joined #openstack-swift13:22
*** dabukalam has quit IRC13:23
*** psachin has joined #openstack-swift13:23
*** kei_yama has quit IRC13:25
*** vinsh has joined #openstack-swift13:37
jrichlipatch 357559 only needs one more +2 and is on our priority reviews list.  16 lines changed in 2 files.13:49
patchbothttps://review.openstack.org/#/c/357559/ - swift - Include object sysmeta in POST responses13:49
*** asettle has quit IRC13:54
*** tongli has joined #openstack-swift13:54
*** asettle has joined #openstack-swift13:55
*** vinsh has quit IRC13:56
*** lifeless has quit IRC13:57
*** lifeless has joined #openstack-swift13:59
*** acoles_ is now known as acoles14:03
*** chsc has joined #openstack-swift14:07
*** chsc has joined #openstack-swift14:07
*** mathiasb has quit IRC14:10
*** mathiasb has joined #openstack-swift14:11
*** tqtran has joined #openstack-swift14:19
*** tqtran has quit IRC14:23
*** vinsh has joined #openstack-swift14:24
*** psachin has quit IRC14:30
*** vinsh has quit IRC14:38
*** vinsh has joined #openstack-swift14:39
*** vinsh has quit IRC14:39
*** vinsh has joined #openstack-swift14:40
*** acoles is now known as acoles_14:40
*** daemontool_ has joined #openstack-swift14:41
*** dmorita has joined #openstack-swift14:42
*** daemontool has quit IRC14:44
*** dmorita has quit IRC14:46
openstackgerritDonagh McCabe proposed openstack/swift: Document access control lists (ACLs)  https://review.openstack.org/37421514:47
*** tgtanya_ has joined #openstack-swift14:49
*** acoles_ is now known as acoles14:49
openstackgerritAlistair Coles proposed openstack/swift: Add more comment to authtoken sample options  https://review.openstack.org/37257314:49
*** daemontool_ has quit IRC14:58
*** arch-nemesis has joined #openstack-swift14:59
*** openstack has joined #openstack-swift15:01
*** sams-gleb has quit IRC15:04
*** _JZ_ has joined #openstack-swift15:08
*** oshritf has quit IRC15:11
*** klrmn has joined #openstack-swift15:20
*** sams-gleb has joined #openstack-swift15:23
*** sams-gleb has quit IRC15:24
*** mvk has quit IRC15:31
tdasilvatimburke, clayg, notmyname and other cores: are we trying to get patch 373537 done before release? can we add to Priority Reviews?15:32
patchbothttps://review.openstack.org/#/c/373537/ - swift - Use separate headers for versioned_writes' stack a...15:32
jrichliacoles: re: container-sync : have there been any discussions around an approach to sync container metadata?15:32
jrichlitdasilva: FWIW I agree, it would be good to add to priority reviews.  i will be taking a look today15:33
*** klrmn has quit IRC15:33
openstackgerritDonagh McCabe proposed openstack/swift: Document access control lists (ACLs)  https://review.openstack.org/37421515:35
*** kei_yama has joined #openstack-swift15:36
*** kei_yama has quit IRC15:41
acolesjrichli: there is a bug report https://bugs.launchpad.net/swift/+bug/1464022 but looks like little activity for a while, I don't recall any discussion I had on that topic other than what is noted there15:42
openstackLaunchpad bug 1464022 in OpenStack Object Storage (swift) "Container sync does not replicate container metadata" [Wishlist,Confirmed] - Assigned to Eran Rom (eranr)15:42
tdasilvajrichli: ack15:43
jrichliacoles: thanks15:43
*** d0ugal has quit IRC15:48
*** d0ugal has joined #openstack-swift15:50
*** rcernin has quit IRC16:03
*** chianingwang has quit IRC16:04
*** chianingwang has joined #openstack-swift16:04
*** SkyRocknRoll has quit IRC16:11
*** pcaruana has quit IRC16:15
*** pcaruana has joined #openstack-swift16:17
*** arch-nemesis has quit IRC16:18
*** arch-nemesis has joined #openstack-swift16:18
openstackgerritAlistair Coles proposed openstack/swift: Check duplicate fragments do not cause 500 status  https://review.openstack.org/37427416:19
*** arch-nemesis has joined #openstack-swift16:19
*** hseipp has quit IRC16:25
*** nadeem has joined #openstack-swift16:27
*** dmorita has joined #openstack-swift16:34
*** rledisez has quit IRC16:34
*** chsc has quit IRC16:54
*** ukaynar has joined #openstack-swift16:54
*** nikivi has joined #openstack-swift16:56
*** klrmn has joined #openstack-swift17:02
timburkethanks jrichli and acoles! and mattoliverau, for fixing up my yaml!17:05
acolestimburke: what did I do ?17:06
timburkeclayg: yeah, that was a weird one. figured i ought to submit a patch in case anyone else hits it17:06
jrichlimy thoughts exactly :-)17:06
acolesyaml?17:06
timburkeacoles: +A'ed the object sysmeta patch17:07
timburkeand jrichli goaded you into it :-)17:07
acolesoic. and mattoliverau did something with yaml. got it17:07
acolestimburke: I previously goaded her into +A'ing one of clayg's. what goes round comes round :)17:08
jrichlilol17:08
* jrichli is running to lunch17:08
*** dmsimard has joined #openstack-swift17:10
claygweee17:11
tdasilvaacoles: re your comment about copying sysmeta to meta on POST requests, i think versioned writes would do that17:11
tdasilvaacoles: https://github.com/openstack/swift/blob/master/swift/common/middleware/versioned_writes.py#L64317:13
claygpsachin: I'm not aware of anyone that splits up accounts from conainers - they are so similar.17:13
claygOTOH, I know lots of folks hat don't split a&c from o - and they all now realize it's terrible17:13
timburketdasilva: likely, but for the moment we're only talking object sysmeta17:13
claygnotmyname says "always use SSD" - i'm mostly satisfied if you just use seperate disks17:15
tdasilvatimburke: duh, true17:16
tdasilvanevermind17:16
acolestimburke: tdasilva yep that is a container request, but a good example of indiscriminate translation of resp headers17:16
timburketdasilva: it'll certainly be something we want to think about when we're encrypting account/container meta, if we want to similarly expose encryption status17:17
*** thebloggu has joined #openstack-swift17:22
*** nadeem has quit IRC17:24
*** nadeem has joined #openstack-swift17:24
*** tgtanya has quit IRC17:31
*** cdelatte has joined #openstack-swift17:32
*** tgtanya_ has quit IRC17:33
*** Suyi_ has joined #openstack-swift17:34
*** chsc has joined #openstack-swift17:38
openstackgerritMerged openstack/swift: Fix unstable json.dumps ordering in obj-server test  https://review.openstack.org/37381917:40
*** geaaru has quit IRC17:44
*** acoles is now known as acoles_17:57
*** hseipp has joined #openstack-swift18:04
openstackgerritTim Burke proposed openstack/swift: Use separate headers for versioned_writes' stack and history modes  https://review.openstack.org/37353718:11
zaitcevGuys, is there a dedicated authentication server that supports v2, but it's not Keystone? Like swauth.18:18
timburkezaitcev: i know that swiftstack's auth middleware handles something kinda-vaguely-almost like v2 (if you squint a little)18:21
timburkesomething similar could probably be done for tempauth18:21
zaitcevWell, it's because I don't want to stand up MySQL and Keystone threatens to remove support for SQLite back-end.18:22
zaitcevAlso, the requirements for Keystone are long. I just installed it again and it's 41 packages.18:22
timburkeand i think that rax has something that does v2 but does not seem to be keystone. i forget what funniness i saw that led me to that conclusion...18:23
openstackgerritMerged openstack/swift: Include object sysmeta in POST responses  https://review.openstack.org/35755918:24
timburkezaitcev: how much of the api do you want/need? do you want to be able to add/remove users, projects, etc. or just get & verify tokens?18:24
zaitcevI suppose I need to configure accounts and users somehow.18:25
timburkewould a flat file work? like tempauth but with enough v2 support to get & verify tokens?18:27
timburke'cause we could just split off the :, call the first piece "project" and the rest "user". if all you need is password auth, that should work well enough18:28
*** rcernin has joined #openstack-swift18:30
zaitcevI'm just trying to reproduce a problem in python-swifclient that occurs with v2.18:33
*** hseipp has quit IRC18:35
*** klamath has quit IRC18:47
*** tqtran has joined #openstack-swift18:47
*** ig0r_ has joined #openstack-swift18:51
*** asettle has quit IRC18:58
tdasilvathere's no community meeting today, correct?18:58
zaitcevI think notmyname is in NY or DC or something19:00
*** thebloggu has quit IRC19:04
*** catintheroof has joined #openstack-swift19:12
*** ukaynar has quit IRC19:27
openstackgerritMerged openstack/python-swiftclient: remove swiftclient/openstack/common/* in the .coveragerc  https://review.openstack.org/37384619:41
claygtdasilva: I think that's correct - notmyname said we should have one if someone will chair - and we all sulked19:46
*** silor has quit IRC19:48
*** cdelatte has quit IRC19:54
*** kei_yama has joined #openstack-swift20:00
*** kei_yama has quit IRC20:05
*** panbalag has joined #openstack-swift20:07
*** catintheroof has quit IRC20:08
*** panbalag has quit IRC20:12
*** sinval has joined #openstack-swift20:34
*** Jeffrey4l has quit IRC20:35
*** Jeffrey4l has joined #openstack-swift20:37
*** kei_yama has joined #openstack-swift20:44
*** cutforth has joined #openstack-swift20:52
*** kei_yama has quit IRC20:52
*** nikivi has quit IRC20:53
*** nikivi has joined #openstack-swift20:56
*** cutforth has quit IRC20:59
*** sinval has left #openstack-swift21:00
claygnova has a new contributor liaison!  https://wiki.openstack.org/wiki/Nova/Mentoring#How_to_Get_Involved21:00
claygwe should have notmyname do that job21:00
*** tongli has quit IRC21:00
*** nikivi has quit IRC21:01
zaitcevIt was one case where capitalization was essential.21:02
*** cdelatte has joined #openstack-swift21:08
openstackgerritClay Gerrard proposed openstack/swift: Delete old tombstones  https://review.openstack.org/34686521:10
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925021:10
openstackgerritClay Gerrard proposed openstack/swift: Update diskfile docstring for get_ondisk_files  https://review.openstack.org/37439921:17
timburkeclayg: i thought notmyname already does all the jobs? we need to clone him21:19
*** rcernin has quit IRC21:24
*** wasmum has joined #openstack-swift21:24
*** ujjain has quit IRC21:29
*** ujjain has joined #openstack-swift21:30
*** ujjain has joined #openstack-swift21:30
*** nadeem has quit IRC21:43
*** ig0r_ has quit IRC21:45
*** nadeem has joined #openstack-swift21:56
mattoliverauMorning22:01
*** klamath has joined #openstack-swift22:10
*** StraubTW has quit IRC22:12
*** timburke has quit IRC22:16
*** timburke has joined #openstack-swift22:16
*** ChanServ sets mode: +v timburke22:16
openstackgerritClay Gerrard proposed openstack/swift: Move documented reclaim_age option to correct location  https://review.openstack.org/37441922:22
timburkeclayg: in my head, i read your description from https://bugs.launchpad.net/bugs/1626290 like one would "there's nothing in the rulebook that says a dog *can't* play football!"22:23
openstackLaunchpad bug 1626290 in OpenStack Object Storage (swift) "[object-reconstructor] section is not documented" [Wishlist,New]22:23
*** StraubTW has joined #openstack-swift22:59
*** mvk has joined #openstack-swift23:04
*** jamielennox is now known as jamielennox|away23:04
*** asettle has joined #openstack-swift23:04
*** asettle has quit IRC23:09
*** hoonetorg has quit IRC23:10
*** nadeem has quit IRC23:16
*** chsc has quit IRC23:16
*** klamath has quit IRC23:17
openstackgerritClay Gerrard proposed openstack/swift: Move documented reclaim_age option to correct location  https://review.openstack.org/37441923:25
clayghow many skips are folks averaging in unitttests these days?  I'd generally prefer we not have to have skips in *unit* tests?23:27
claygi haven't really dug into what they are?23:28
claygSKIP=14?  is it just me!?23:28
klrmnclayg: aren't most of the skips around which features are supported for which swift versions?23:29
claygoh, it's the new linkat O_TMP stuff23:29
claygklrmn: not in swift's own unittests - they just test whatever features are supported int he commit your testing - there's a few crazy tests for the databases that like had to capture the old db schema's and test migration upgrades - and sometimes a mock might do something like "old object servers used to respond like this bullshit here" - but generally there's no unitests "run against old swift versions" per say23:31
clayganyway - I think i just need to get on some xenial stuff?  or upgrade my kernal or something?23:31
*** nikivi has joined #openstack-swift23:32
claygnotmyname: mattoliverau: you guys approved patch 162243 - how do i get my business up where I can run all the tests for the new hawtness?!23:33
patchbothttps://review.openstack.org/#/c/162243/ - swift - Make object creation more atomic in Linux (MERGED)23:33
claygi'm also seeing the return of the ChunkWriteTimeout(60) in the stderr's again23:34
claygtimburke: do you remember the hacks we had to do to track it down last time?23:34
timburkeclayg: ugh. i think i put it out of my mind. only thing i remember was that it was a PITA23:35
openstackgerritClay Gerrard proposed openstack/swift: Move documented reclaim_age option to correct location  https://review.openstack.org/37441923:37
claygtimburke: i remember some hack i did somewhere in... nose?  that kept the hub around long enought so that it would definately fire if the test that triggered it ran23:38
claygbut I don't recall what crazy stack/patch/debug I had to do to *find* the timeout created with 60 seconds?23:38
clayg.... I might have ... if timeout == 60: asdf somewhere in eventlet (!?23:39
*** Suyi_ has quit IRC23:40
timburkei thought we maybe just found (one of?) the tests that caused it and stuck a sleep() at the end. that seems to be what you did in https://gist.github.com/clayg/64d659bcae9991e5686c23:40
*** nikivi has quit IRC23:41
openstackgerritTim Burke proposed openstack/swift: Use separate headers for versioned_writes' stack and history modes  https://review.openstack.org/37353723:42
*** jamielennox|away is now known as jamielennox23:43
claygtimburke: yes!  but how did we find that test!?23:47

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