Monday, 2017-02-13

openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873600:07
*** jamielennox is now known as jamielennox|away00:24
*** jlwhite has quit IRC00:28
*** jlwhite has joined #openstack-swift00:28
*** catintheroof has joined #openstack-swift00:36
*** catintheroof has quit IRC00:37
*** jamielennox|away is now known as jamielennox00:50
*** vint_bra has joined #openstack-swift00:54
*** dmorita has joined #openstack-swift01:03
*** dmorita_ has joined #openstack-swift01:06
*** dmorita has quit IRC01:09
*** nikivi has quit IRC01:17
*** sileht has quit IRC01:19
*** sams-gleb has joined #openstack-swift01:19
*** nikivi has joined #openstack-swift01:19
*** dmorita_ has quit IRC01:19
*** amoralej|off has quit IRC01:19
*** amoralej has joined #openstack-swift01:22
*** sileht has joined #openstack-swift01:22
*** sams-gleb has quit IRC01:23
*** dmorita has joined #openstack-swift01:24
*** dmorita has quit IRC01:28
*** dmorita has joined #openstack-swift01:29
*** dmorita has quit IRC01:32
*** vint_bra has quit IRC01:33
*** vint_bra has joined #openstack-swift01:38
*** dmorita has joined #openstack-swift01:50
*** dmorita has quit IRC01:53
*** dmorita has joined #openstack-swift01:56
*** vint_bra has quit IRC01:56
*** dmorita has quit IRC01:58
*** dmorita has joined #openstack-swift01:59
*** dmorita has quit IRC02:00
*** dmorita has joined #openstack-swift02:01
*** dmorita has quit IRC02:02
*** dmorita has joined #openstack-swift02:03
*** dmorita_ has joined #openstack-swift02:16
*** dmorita has quit IRC02:19
*** ChatSharp has joined #openstack-swift02:20
*** ChatSharp has left #openstack-swift02:23
*** dmorita_ has quit IRC02:30
*** dmorita has joined #openstack-swift02:31
*** dmorita has quit IRC02:34
*** klrmn has quit IRC02:35
*** dmorita has joined #openstack-swift02:43
*** dmorita has quit IRC02:47
*** dmorita has joined #openstack-swift03:07
*** dmorita has quit IRC03:08
*** sams-gleb has joined #openstack-swift03:21
*** sams-gleb has quit IRC03:25
*** SkyRocknRoll has joined #openstack-swift03:48
*** dmorita has joined #openstack-swift03:55
*** dmorita has quit IRC04:01
*** dmorita has joined #openstack-swift04:03
*** dmorita has quit IRC04:09
*** psachin has joined #openstack-swift04:10
*** SkyRocknRoll has quit IRC04:11
*** openstackgerrit has quit IRC04:32
*** hoonetorg has quit IRC04:34
*** hoonetorg has joined #openstack-swift04:47
*** dja has quit IRC05:10
*** tonanhngo has joined #openstack-swift05:14
*** tonanhngo has quit IRC05:16
*** mtreinish has quit IRC05:20
*** sams-gleb has joined #openstack-swift05:23
*** sams-gleb has quit IRC05:27
*** mtreinish has joined #openstack-swift05:31
*** SkyRocknRoll has joined #openstack-swift05:54
*** bkopilov_ has quit IRC05:58
*** bkopilov_ has joined #openstack-swift05:59
*** Jeffrey4l__ has joined #openstack-swift06:01
*** bkopilov_ has quit IRC06:04
*** Jeffrey4l_ has quit IRC06:04
*** bkopilov_ has joined #openstack-swift06:04
*** chsc has joined #openstack-swift06:09
*** chsc has joined #openstack-swift06:09
*** chsc has quit IRC06:15
*** psachin has quit IRC06:33
*** geaaru has quit IRC06:40
*** tnovacik has joined #openstack-swift06:50
*** psachin has joined #openstack-swift06:50
*** psachin has quit IRC06:54
*** psachin has joined #openstack-swift06:54
*** seongsoocho has joined #openstack-swift07:09
*** rcernin has joined #openstack-swift07:15
seongsoochoHi All! . I want to debug swift line by line and see a variables. I already build swift on vm. Is there any idea how to debugging on remote?07:18
*** sams-gleb has joined #openstack-swift07:25
*** tesseract has joined #openstack-swift07:28
*** sams-gleb has quit IRC07:29
*** tesseract is now known as tesseract-RH07:29
*** newmember has quit IRC07:30
*** newmember has joined #openstack-swift07:31
*** tnovacik has quit IRC07:32
*** sams-gleb has joined #openstack-swift07:44
*** pcaruana has joined #openstack-swift07:49
*** kei_yama has quit IRC08:24
*** rledisez has joined #openstack-swift08:28
*** furlongm has quit IRC08:30
*** furlongm has joined #openstack-swift08:31
*** geaaru has joined #openstack-swift08:36
*** kei_yama has joined #openstack-swift08:56
*** cbartz has joined #openstack-swift09:01
*** tqtran has joined #openstack-swift09:05
*** joeljwright has joined #openstack-swift09:08
*** ChanServ sets mode: +v joeljwright09:08
mattoliverauseongsoocho: if you want a line by line debugger that can get hard, as swift has so many moving peices. On an SAIO on my desktop, I've got it working with pycharms. The paid version has remote debugging, but don't use. If you do a bit of scripting to start things I've gotten pudb working working through an SSH connection to debug things like the replicators debugged. Pycharms was easier but you have to start each09:09
mattoliverauservice though the ide, or at least the services you want to debug at the time.09:09
*** tqtran has quit IRC09:09
*** oshritf_ has joined #openstack-swift09:12
*** Shashikant86 has joined #openstack-swift09:22
*** Shashikant86 has quit IRC09:34
*** oshritf_ has quit IRC09:37
*** oshritf_ has joined #openstack-swift09:43
*** Shashikant86 has joined #openstack-swift09:44
*** xlucas has quit IRC09:47
*** jamielennox is now known as jamielennox|away09:48
*** Shashikant86 has quit IRC09:50
*** oshritf_ has quit IRC09:56
*** xlucas has joined #openstack-swift10:01
*** Shashikant86 has joined #openstack-swift10:02
*** tonanhngo has joined #openstack-swift10:03
*** tonanhngo has quit IRC10:05
*** Shashikant86 has quit IRC10:12
*** tqtran has joined #openstack-swift10:15
*** dims_ has quit IRC10:16
*** tqtran has quit IRC10:20
*** dims has joined #openstack-swift10:23
*** jamielennox|away is now known as jamielennox10:24
*** sams-gleb has quit IRC10:35
*** mvk has quit IRC10:40
seongsoochomattoliverau, Thanks. Use PyCharm in same host which is installed SAIO seems to be an approciate solution to debug line by line. Then.. How does contributors works? How they develop swift?10:50
*** jamiec has quit IRC11:04
*** oshritf has joined #openstack-swift11:04
*** psachin has quit IRC11:08
*** mvk has joined #openstack-swift11:09
*** jamiec has joined #openstack-swift11:12
*** psachin has joined #openstack-swift11:25
*** oshritf has quit IRC11:26
*** sams-gleb has joined #openstack-swift11:27
*** oshritf has joined #openstack-swift11:28
*** psachin has quit IRC11:39
*** kei_yama has quit IRC11:42
*** ChatSharp has joined #openstack-swift11:52
*** ChatSharp has left #openstack-swift11:55
*** SkyRocknRoll has quit IRC11:56
*** oshritf has quit IRC12:06
*** oshritf has joined #openstack-swift12:11
*** psachin has joined #openstack-swift12:12
*** SkyRocknRoll has joined #openstack-swift12:13
*** oshritf has quit IRC12:14
*** tqtran has joined #openstack-swift12:17
*** oshritf has joined #openstack-swift12:19
*** oshritf has quit IRC12:22
*** tqtran has quit IRC12:22
*** dims has quit IRC12:23
*** dmorita has joined #openstack-swift12:26
*** oshritf has joined #openstack-swift12:26
*** oshritf has quit IRC12:38
*** oshritf has joined #openstack-swift12:38
*** catintheroof has joined #openstack-swift12:41
*** CowboyPride has joined #openstack-swift12:57
CowboyPrideMorning everyone, could someone look over the upgrade plan for a swift cluster I've been handed and see if there is anything I'm missing. http://pastebin.com/f5yJacuv12:58
CowboyPrideNode 5 was in a bad way but I think I've got that fixed now, just have get everything up to latest stable release.13:00
*** oshritf has quit IRC13:01
*** dmorita_ has joined #openstack-swift13:11
*** dmorita has quit IRC13:12
*** dmorita has joined #openstack-swift13:12
*** dmorita_ has quit IRC13:15
*** oshritf has joined #openstack-swift13:19
*** silor has joined #openstack-swift13:20
*** dims has joined #openstack-swift13:20
*** klamath has joined #openstack-swift13:24
*** klamath has quit IRC13:24
*** klamath has joined #openstack-swift13:25
*** silor1 has joined #openstack-swift13:26
*** oshritf has quit IRC13:27
*** silor has quit IRC13:27
*** silor1 is now known as silor13:27
*** vinsh has joined #openstack-swift13:30
*** oshritf has joined #openstack-swift13:32
*** dmorita has quit IRC13:33
*** pumaranikar has quit IRC13:34
*** pumaranikar has joined #openstack-swift13:38
*** dmorita has joined #openstack-swift13:41
*** dims_ has joined #openstack-swift13:43
*** dims has quit IRC13:45
*** dmorita has quit IRC13:56
*** mvk has quit IRC14:03
*** oshritf has quit IRC14:03
*** tonanhngo has joined #openstack-swift14:05
*** tonanhngo has quit IRC14:06
*** oshritf has joined #openstack-swift14:06
*** amoralej is now known as amoralej|lunch14:11
*** dmorita has joined #openstack-swift14:12
*** dmorita has quit IRC14:17
*** mvk has joined #openstack-swift14:18
*** cdelatte has joined #openstack-swift14:21
*** amoralej|lunch is now known as amoralej14:37
*** jamielennox is now known as jamielennox|away14:39
*** vinsh_ has joined #openstack-swift14:45
*** vinsh has quit IRC14:45
*** nikivi has quit IRC14:45
*** nikivi has joined #openstack-swift14:48
*** pcaruana has quit IRC14:50
*** oshritf has quit IRC14:53
*** sams-gleb has quit IRC14:55
*** pcaruana has joined #openstack-swift14:55
*** sams-gleb has joined #openstack-swift14:56
*** sams-gleb has quit IRC15:00
*** sams-gleb has joined #openstack-swift15:12
*** tqtran has joined #openstack-swift15:19
*** oshritf has joined #openstack-swift15:23
*** tqtran has quit IRC15:24
*** SkyRocknRoll has quit IRC15:30
*** bikmak has joined #openstack-swift15:31
*** _JZ_ has joined #openstack-swift15:44
*** Jeffrey4l__ is now known as Jeffrey4l15:44
*** psachin has quit IRC15:44
*** vinsh_ has quit IRC15:47
*** vinsh has joined #openstack-swift15:48
-openstackstatus- NOTICE: We are currently investigating an issue with our AFS mirrors which is causing some projects jobs to fail. We are working to correct the issue.15:50
*** vinsh has quit IRC15:52
*** mvk has quit IRC15:53
*** klrmn has joined #openstack-swift15:55
*** vinsh has joined #openstack-swift15:56
notmynamegood morning15:58
notmynameI'm going on a kid's field trip today with his class, so I'll be offline most of the day.15:58
zaitcevA day of productivity for the rest of us.15:59
notmynameCowboyPride: I'm not going to flippantly say "looks good" or anything like that. I'm looking at your pastebin now15:59
notmynameCowboyPride: you have a note about looking for the changelog. it's here https://github.com/openstack/swift/blob/master/CHANGELOG16:00
notmynamethis week there should be a 2.13.0 release for Ocata16:00
*** oshritf has quit IRC16:01
zaitcevSomehow this reminds me about "take your daughter to work day" skit of Robot Chicken https://www.youtube.com/watch?v=Cizlx6ODhuE16:01
*** oshritf has joined #openstack-swift16:02
notmynamelol16:04
jrichlizaitcev: thanks, i needed that :-)16:04
notmynamethere was one day I had to bring a kid to the office. he hated it16:04
jrichli*had* to?  :-)16:04
zaitcevYeah. It's not like you can work with them around either.16:04
notmynameyeah, actually I did have to. it's a more involved story that I want to get into on IRC though ;-)16:06
jrichliIt was interesting to me to see some people without kids leave on bring your kid to work day - because they couldnt get work done.16:06
notmynameso... who's "OpenStack Clean" and how do I buy this bot a beer? https://review.openstack.org/#/c/414881/16:06
patchbotpatch 414881 - python-swiftclient - Removes unnecessary utf-8 coding16:06
notmynamejrichli: +10016:06
jrichliomg - that comment is great - re: os clean16:09
mahaticnotmyname: lol jrichli: it's an amazing comment! :D re: OS clean16:12
notmynamelooks like it's on all the patches associated with that same topic16:12
notmynameso, a lot of them16:12
jrichlimahatic: o/  will you be at the PTG?16:13
notmyname-infra says it might not be a bot. and I think it's a surprise for everyone16:13
mahaticjrichli: nope :(16:13
jrichlimahatic: boo!  :(16:13
jrichlinotmyname: interesting!16:14
notmynamelogistics for the week...16:15
mahaticnot a bot and yet so comments on so many patches?16:15
notmynameI'll be finishing up the authors/changelog patch Real Soon Now16:15
notmynameso whatever's in the release needs to be landed ASAP16:16
notmyname(I'll likely spend some more time on that late today or tomorrow)16:16
mahaticIdk why I remembered the release date as 16th Feb16:16
notmynameand the PTG is next week, so in the second half of the week I'll be organizing the etherpad topics into a rough schedule16:16
*** rcernin has quit IRC16:19
*** dims_ has quit IRC16:19
*** pcaruana has quit IRC16:20
*** dims has joined #openstack-swift16:24
*** tqtran has joined #openstack-swift16:25
notmynameok, maybe not a bot. there's quite a few different reviews https://review.openstack.org/#/q/reviewer:%22OpenStack+Clean+%253Copenstack.clean%2540gmail.com%253E%2216:28
notmynamebut it's likely that there was some scripting involved16:28
notmynameCowboyPride: FWIW, https://www.swiftstack.com/blog/2013/12/20/upgrade-openstack-swift-no-downtime/ has some good tips for a general upgrade process, too16:30
*** pcaruana has joined #openstack-swift16:34
CowboyPrideThanks!16:34
*** oshritf has quit IRC16:43
notmynameCowboyPride: in general, there's a few things that stick out to me on your pastebin16:50
notmynameCowboyPride: first is that you're doing a lot of stuff in one upgrade. OS upgrade and swift upgrade. that seems like a lot of moving pieces. however, take this (and other stuff) as from someone who's a dev and not a sysadmin16:51
*** dims has quit IRC16:51
notmynameCowboyPride: I wouldn't expect any of those upgrades to cause issues, but doing them all at once seems to have a higher likelihood of confusing troubleshooting if something goes wrong16:51
notmynameCowboyPride: second is that you should definitely do a canary-node style deployment. upgrade one server and put it in the cluster and see if anything breaks16:52
notmynameCowboyPride: swift is really really good at working around a down server, so even if worst case you end up having to wipe and restore that one server, the cluster should handle it just fine16:53
*** dmorita has joined #openstack-swift16:53
*** dims has joined #openstack-swift16:55
*** tesseract-RH has quit IRC16:55
notmynameCowboyPride: however, that being said, if there are any chnages that have changed the way data is written to disk, you'll have to be more careful. eg in your upgrade path you've got the crypto functionality. so you can't enable crypto on the new node without the new code being everywhere first (otherwise all the old code can't read it)16:55
notmynameCowboyPride: that's generally the way we write stuff in swift. clean upgrades with new features enabled by option after the new code is everywhere16:56
notmyname"generally"16:56
*** pcaruana has quit IRC16:58
*** pcaruana has joined #openstack-swift16:59
CowboyPridenotmyname: Won't be doing upgrades all at once, will be doing one node at at time and making sure the node is funcational again before continueing on to next17:01
*** klrmn has quit IRC17:01
notmynameCowboyPride: great. as with all ops things, monitoring is key :-)17:01
*** cbartz has quit IRC17:02
CowboyPrideNode5 had a undate that was done to it by previous person and it was an incomplete update. And I finally got it back to a good state. It went from icehouse to liberty.17:02
CowboyPride*update17:02
notmynameCowboyPride: keep an eye on response codes (5xx is bad), async pendings (huge spikes can indicate a problem), handoff vs primary partitions, req/sec, any tracebacks in the logs, etc (in addition to normal CPU, memory, drive stuff)17:03
CowboyPridebut they forgot to start repliction and forgot to do a few other things as well, mostly because there was NO action plan.17:03
notmynameah, yikes17:03
*** dmorita has quit IRC17:03
*** dims_ has joined #openstack-swift17:06
*** dims has quit IRC17:07
notmynameCowboyPride: please don't hesitate to drop in here and ask questions as they come up. we're *always* looking for ops feedback (and many people in here run swift clusters and can probably answer general questions)17:07
notmynameCowboyPride: what time zone are you in?17:07
tdasilvajrichli: have you had a chance to run probetest on master since those fixes merged?17:09
notmynameI'm out. I'll check in later this afternoon17:14
*** rledisez has quit IRC17:15
*** tnovacik has joined #openstack-swift17:19
-openstackstatus- NOTICE: AFS replication issue has been addressed. Mirrors are currently re-syncing and coming back online.17:20
*** JimCheung has joined #openstack-swift17:27
*** openstackgerrit has joined #openstack-swift17:35
openstackgerritClay Gerrard proposed openstack/swift master: Deprecate broken handoffs_first in favor of handoffs_only  https://review.openstack.org/42549317:35
claygI still thinkg "Don't use this.  You're so screwed.  I'm sorry." would have been better17:37
*** mvk has joined #openstack-swift17:38
*** chsc has joined #openstack-swift17:39
*** pcaruana has quit IRC17:44
*** klrmn has joined #openstack-swift18:00
*** david-lyle_ has joined #openstack-swift18:08
*** joeljwright has quit IRC18:09
*** david-lyle_ is now known as david-lyle18:12
jrichlitdasilva: i dont think i have done that after the merges.  i had moved on to digging into handoffs only patch.  but ill do that now.  thanks!18:16
timburkegood morning18:24
*** newmember has quit IRC18:25
*** newmember has joined #openstack-swift18:26
*** gatuus has joined #openstack-swift18:31
*** geaaru has quit IRC18:37
*** SkyRocknRoll has joined #openstack-swift18:39
jrichliclayg: do you mind if i push a rebase up on patch 425493 since it changes the logic a little in _revert and it's good to see how it will all fit once merged18:48
patchbothttps://review.openstack.org/#/c/425493/ - swift - Deprecate broken handoffs_first in favor of handof...18:48
tdasilvajrichli: ok, just checking, i ran into errors, but I think it was due to a faulty dev enviroment. I just started with a new VM and everything passed correctly18:50
claygjrichli: a rebase is fine for m18:50
clayg*me18:50
claygit only effects reviewers ability to see changes from base to base AIUI18:50
claygjrichli: anyway - what changed?  did something else get fixed in the reconstructor?18:51
jrichlilooking at the review in gerrit, it still shows the adding of the handoff nodes to what is looped over in revert18:51
jrichlibut yes, i guess then the changes would not be isolated, so maybe i wont do that18:52
claygoic - i had made them orthogonal - but now that the other is merged it makes sense to me to squash things down18:52
clayger... rebase anyway18:53
claygyou can do it locally if you just want to test it?18:53
claygit'll come in a merge commit regardless18:53
clayg`git checkout master; git checkout -b review-test; git merge review/clay/thing` - that's what will acctually be on master after +A18:53
jrichlii did it locally, yes.18:53
*** dmorita has joined #openstack-swift19:04
*** joeljwright has joined #openstack-swift19:04
*** ChanServ sets mode: +v joeljwright19:04
jrichliclayg: I am currently focused on the incrementing of handoffs_remaining in the revert method.  specifically, how the code determines when it should be incremented.19:06
jrichliI am having a hard time understanding why 'syncd_with < len(job['sync_to'])' necessarily implies that there is another handoff remaining.19:07
jrichlithe handoff nodes are no longer in the set of nodes looped over.  this must be  bigger picture thing I dont know about19:08
*** dmorita has quit IRC19:08
*** newmember has quit IRC19:08
*** tonanhngo has joined #openstack-swift19:09
*** tonanhngo_ has joined #openstack-swift19:12
*** tonanhngo has quit IRC19:13
jrichlii see how that particular condition will be true if there are any failures with SYNC19:16
*** tonanhngo_ has quit IRC19:16
*** tonanhngo has joined #openstack-swift19:17
claygi think the question is just "was the job successful"19:19
claygthe sync_to list I guess can be different lengths - so you need to success to at least that many nodes19:19
claygiirc?19:19
*** oshritf has joined #openstack-swift19:20
*** amoralej is now known as amoralej|off19:37
jrichliclayg: ok, so I think I see.  whether we are in handoffs mode or not, all jobs in job['sync_to'] in _revert are going to be REVERT jobs, so handoffs.  I think the "node in job['sync_to']" had me forgetting each loop was for a revert job.19:38
*** oshritf has quit IRC19:41
jrichlii guess that is still have to wonder about how this looping goes if there are more than one REVERT jobs needed on the same node19:41
*** klamath has quit IRC19:43
*** oshritf has joined #openstack-swift19:43
jrichliis there currently a test somewhere that involves the case where more than one REVERT job is needed on the same node?  walking through that whole flow with handoffs only will help me.19:46
claygidk, timburke was trying to explain to me that at somepoint when we dropped handoff reversion the code was correct but convoluted19:47
jrichliclayg: hehe.  yes, maybe that is what is making me doubt things.  it seems like there is a one-to-one assumption here that is probably fine, but I am not familiar enough with this yet to know why it is.19:50
jrichlii am focusing on the tests.  looking for a way to setup that case i mentioned (and maybe we already have that situation somewhere)19:51
*** dmorita has joined #openstack-swift19:53
*** dmorita has quit IRC19:57
jrichlitdasilva, clayg: it seems that I am still getting the intermittent failures ... from different replication probe tests.  tdasilva - is that the type of test that had failed for you before the new19:58
jrichlidev env?19:58
*** gk-1wm-su has joined #openstack-swift19:59
*** gk-1wm-su has left #openstack-swift19:59
*** SkyRocknRoll has quit IRC20:01
tdasilvatdasilva: not sure, since I spawned a new VM the probe tests have run fine for me (i ran it 2x. one with rsync and another with ssync)20:04
tdasilvajrichli: ^^20:04
tdasilvaheh...i typically don't talk to myself20:05
jrichlilol.  ok, i will keep testing to see.20:06
tdasilvajrichli: anyway....the probetests errors I saw in the old environment went beyong just repl tests, there were like 23 failures...20:06
*** gk-1wm-su has joined #openstack-swift20:07
gk-1wm-su.çôêå20:07
jrichlitdasilva: oh, wow.  ok - that isn't anything like i am seeing.  i will get one error only at a time.  but its always with some kind of replication or handoff test - jsut different ones.20:09
tdasilvajrichli: yeah, that's why I mean, once i saw that I knew my dev. environment was just busted20:10
*** gk-1wm-su has quit IRC20:10
jrichliclayg:  looking more at SSYNC, i think i am more clear on the revert now20:11
*** amoralej|off is now known as amoralej20:11
jrichliand as for the probe tests, i think i had just forgotten to rebase when i should have on a couple runs20:38
*** klamath has joined #openstack-swift20:55
*** gatuus has quit IRC20:59
*** jamielennox|away is now known as jamielennox21:02
*** amoralej is now known as amoralej|off21:23
mattoliveraumorning21:25
*** dmorita has joined #openstack-swift21:31
*** Jeffrey4l has quit IRC21:36
*** dmorita has quit IRC21:36
*** Jeffrey4l_ has joined #openstack-swift21:36
*** dmorita has joined #openstack-swift21:36
tdasilvamattoliverau: o/21:42
timburke:-( i just realized that https://github.com/openstack/liberasurecode/blob/master/Makefile.am#L63 doesn't do what we want at all -- using libtool means that test/liberasurecode_test is actually a shell script21:48
timburke...which explains why our gate keeps saying there were no allocs http://logs.openstack.org/50/431850/3/check/gate-liberasurecode-unit/c613b91/console.html#_2017-02-12_22_44_38_32700721:49
*** dmorita_ has joined #openstack-swift21:50
*** dmorita has quit IRC21:53
claygtimburke: but there *is* no handoffs_first :'(21:54
claygtimburke: i'm also trying to keep the words to a minimum - it's just an example config - more detailed prose would be beter suited in docs - but there's an standing bug that those are missing21:55
timburkeclayg: there used to be, we included it in our sample configs (https://github.com/openstack/swift/blob/2.10.0/etc/object-server.conf-sample#L299), and now it's going away. it was terrible and didn't do what ops wanted, but it existed21:56
*** silor has quit IRC21:57
timburkei agree that it doesn't need to be as long as all i said, but i feel like there should be *something* there about this thing that used to be but soon won't be21:57
*** gatuus has joined #openstack-swift21:59
*** dmorita_ has quit IRC22:03
*** dmorita has joined #openstack-swift22:06
*** dmorita has quit IRC22:10
*** catintheroof has quit IRC22:20
*** tnovacik has quit IRC22:25
*** dja has joined #openstack-swift22:39
*** sams-gleb has quit IRC22:50
*** sams-gleb has joined #openstack-swift22:50
*** sams-gleb has quit IRC22:51
*** sams-gleb has joined #openstack-swift22:51
*** sams-gleb has quit IRC22:52
*** oshritf has quit IRC23:07
*** dmorita has joined #openstack-swift23:13
*** oshritf has joined #openstack-swift23:14
*** jamielennox is now known as jamielennox|away23:15
*** dmorita has quit IRC23:17
*** dmorita has joined #openstack-swift23:18
*** jamielennox|away is now known as jamielennox23:20
*** joeljwright has quit IRC23:20
*** dmorita has quit IRC23:22
*** g-k--1-w-m- has joined #openstack-swift23:23
*** g-k--1-w-m- has left #openstack-swift23:23
*** kei_yama has joined #openstack-swift23:30
*** jtomasek has quit IRC23:31
*** chsc has quit IRC23:34
*** jtomasek has joined #openstack-swift23:35
*** tonanhngo has quit IRC23:48
*** sams-gleb has joined #openstack-swift23:52
*** catintheroof has joined #openstack-swift23:55
*** tonanhngo has joined #openstack-swift23:55
*** sams-gleb has quit IRC23:56
kota_good morning23:58
*** tonanhngo has quit IRC23:59

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