Wednesday, 2021-02-03

*** jmasud has joined #openstack-meeting00:04
*** ianychoi__ has joined #openstack-meeting00:14
*** tosky has quit IRC00:15
*** ianychoi_ has quit IRC00:17
*** martial has quit IRC00:17
*** yasufum has quit IRC00:19
*** jmasud has quit IRC01:26
*** yasufum has joined #openstack-meeting01:28
*** jmasud has joined #openstack-meeting01:35
*** jmasud has quit IRC01:36
*** jmasud has joined #openstack-meeting01:40
*** jamesmcarthur has joined #openstack-meeting01:42
*** baojg has joined #openstack-meeting01:48
*** yasufum has quit IRC01:52
*** yasufum has joined #openstack-meeting01:54
*** mlavalle has quit IRC01:55
*** jamesmcarthur has quit IRC02:07
*** jamesmcarthur has joined #openstack-meeting02:14
*** lbragstad_ has joined #openstack-meeting02:14
*** lbragstad has quit IRC02:17
*** jamesmcarthur has quit IRC02:19
*** jamesmcarthur has joined #openstack-meeting02:29
*** toabctl has quit IRC02:34
*** jmasud has quit IRC02:35
*** rcernin has quit IRC02:37
*** toabctl has joined #openstack-meeting02:50
*** rcernin has joined #openstack-meeting02:51
*** jamesmcarthur has quit IRC03:05
*** jamesmcarthur has joined #openstack-meeting03:06
*** jamesmcarthur has quit IRC03:11
*** jamesmcarthur has joined #openstack-meeting03:13
*** jamesmcarthur has quit IRC03:14
*** jamesmcarthur has joined #openstack-meeting03:16
*** jamesmcarthur has quit IRC03:20
*** jamesmcarthur has joined #openstack-meeting03:20
*** jamesmcarthur has quit IRC03:20
*** jamesmcarthur has joined #openstack-meeting03:22
*** jamesmcarthur has quit IRC03:26
*** dustinc has joined #openstack-meeting03:29
*** jamesmcarthur has joined #openstack-meeting03:32
*** jamesmcarthur has quit IRC03:37
*** jamesmcarthur has joined #openstack-meeting03:51
*** lbragstad_ is now known as lbragstad03:51
*** jamesmcarthur has quit IRC03:52
*** jamesmcarthur has joined #openstack-meeting03:53
*** manpreet has joined #openstack-meeting04:33
*** baojg has quit IRC04:37
*** baojg has joined #openstack-meeting04:38
*** psahoo has joined #openstack-meeting04:40
*** jmasud has joined #openstack-meeting04:53
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-meeting05:33
*** xinranwang has joined #openstack-meeting05:35
*** dustinc has quit IRC05:39
*** psahoo has quit IRC05:58
*** psahoo has joined #openstack-meeting06:05
*** rcernin has quit IRC06:08
*** rcernin has joined #openstack-meeting06:08
*** rcernin has quit IRC06:17
*** rcernin has joined #openstack-meeting06:17
*** rcernin has quit IRC06:17
*** rcernin has joined #openstack-meeting06:19
*** jamesmcarthur has quit IRC06:34
*** dasp has joined #openstack-meeting07:00
*** dasp_ has quit IRC07:01
*** jamesmcarthur has joined #openstack-meeting07:04
*** jamesmcarthur has quit IRC07:10
*** psahoo has quit IRC07:11
*** psahoo has joined #openstack-meeting07:11
*** jamesmcarthur has joined #openstack-meeting07:22
*** slaweq has joined #openstack-meeting07:28
*** ralonsoh has joined #openstack-meeting07:28
*** vishalmanchanda has joined #openstack-meeting07:33
*** ircuser-1 has joined #openstack-meeting07:45
*** dklyle has quit IRC07:58
*** psachin has joined #openstack-meeting08:11
*** e0ne has joined #openstack-meeting08:12
*** macz_ has joined #openstack-meeting08:23
*** macz_ has quit IRC08:27
*** jamesmcarthur has quit IRC08:40
*** tosky has joined #openstack-meeting08:40
*** rpittau|afk is now known as rpittau08:41
*** jamesmcarthur has joined #openstack-meeting08:56
*** jamesmcarthur has quit IRC09:04
*** ociuhandu has joined #openstack-meeting09:06
*** jamesmcarthur has joined #openstack-meeting09:15
*** jamesmcarthur has quit IRC09:22
*** ociuhandu has quit IRC09:28
*** ociuhandu has joined #openstack-meeting09:33
*** jamesmcarthur has joined #openstack-meeting09:34
*** baojg has quit IRC09:34
*** baojg has joined #openstack-meeting09:35
*** psachin has quit IRC09:40
*** jamesmcarthur has quit IRC09:40
*** psachin has joined #openstack-meeting09:43
*** ociuhandu has quit IRC09:45
*** jmasud has quit IRC09:46
*** yasufum has quit IRC09:50
*** jamesmcarthur has joined #openstack-meeting09:51
*** jamesmcarthur has quit IRC09:58
*** yamamoto_ has quit IRC10:04
*** psachin has quit IRC10:04
*** jamesmcarthur has joined #openstack-meeting10:09
*** baojg has quit IRC10:12
*** jamesmcarthur has quit IRC10:17
*** ociuhandu has joined #openstack-meeting10:19
*** tris has quit IRC10:23
*** ociuhandu has quit IRC10:24
*** rcernin has quit IRC10:24
*** jamesmcarthur has joined #openstack-meeting10:29
*** jamesmcarthur has quit IRC10:36
*** ociuhandu has joined #openstack-meeting10:36
*** e0ne has quit IRC10:40
*** ociuhandu has quit IRC10:41
*** ociuhandu has joined #openstack-meeting10:42
*** jamesmcarthur has joined #openstack-meeting10:47
*** rcernin has joined #openstack-meeting10:55
*** jamesmcarthur has quit IRC10:59
*** jamesmcarthur has joined #openstack-meeting11:12
*** xinranwang has quit IRC11:13
*** jmasud has joined #openstack-meeting11:15
*** rcernin has quit IRC11:15
*** jamesmcarthur has quit IRC11:19
*** yamamoto has joined #openstack-meeting11:23
*** ociuhandu has quit IRC11:27
*** jamesmcarthur has joined #openstack-meeting11:31
*** jamesmcarthur has quit IRC11:37
*** baojg has joined #openstack-meeting11:44
*** yamamoto has quit IRC11:46
*** e0ne has joined #openstack-meeting11:48
*** jamesmcarthur has joined #openstack-meeting11:49
*** jamesmcarthur has quit IRC11:56
*** ociuhandu has joined #openstack-meeting11:59
*** yamamoto has joined #openstack-meeting12:00
*** rcernin has joined #openstack-meeting12:01
*** jamesmcarthur has joined #openstack-meeting12:09
*** ociuhandu_ has joined #openstack-meeting12:12
*** ociuhandu has quit IRC12:15
*** jamesmcarthur has quit IRC12:16
*** macz_ has joined #openstack-meeting12:20
*** macz_ has quit IRC12:24
*** jmasud has quit IRC12:24
*** jamesmcarthur has joined #openstack-meeting12:30
*** jamesmcarthur has quit IRC12:37
*** rcernin has quit IRC12:43
*** ociuhandu_ has quit IRC12:46
*** ociuhandu has joined #openstack-meeting12:47
*** jamesmcarthur has joined #openstack-meeting12:50
*** jamesmcarthur has quit IRC12:57
*** jamesmcarthur has joined #openstack-meeting13:09
*** ociuhandu has quit IRC13:10
*** ociuhandu has joined #openstack-meeting13:11
*** jamesmcarthur has quit IRC13:14
*** jamesmcarthur has joined #openstack-meeting13:27
*** baojg has quit IRC13:30
*** jamesmcarthur has quit IRC13:36
*** jamesmcarthur has joined #openstack-meeting13:51
*** jamesmcarthur has quit IRC13:56
*** lbragstad has quit IRC13:57
*** zaneb has quit IRC13:58
*** ociuhandu has quit IRC14:08
*** jamesmcarthur has joined #openstack-meeting14:08
*** ociuhandu has joined #openstack-meeting14:09
*** thgcorrea has joined #openstack-meeting14:10
*** jamesmcarthur has quit IRC14:15
*** ociuhandu has quit IRC14:27
*** ociuhandu has joined #openstack-meeting14:28
*** ociuhandu has quit IRC14:32
*** lbragstad has joined #openstack-meeting14:35
*** yasufum has joined #openstack-meeting14:41
*** jamesmcarthur has joined #openstack-meeting14:52
*** jamesmcarthur has quit IRC14:57
*** bcafarel has quit IRC14:58
*** bcafarel has joined #openstack-meeting14:59
*** jamesmcarthur has joined #openstack-meeting15:05
*** ociuhandu has joined #openstack-meeting15:06
*** jamesmcarthur has quit IRC15:09
*** ociuhandu has quit IRC15:15
*** jamesmcarthur has joined #openstack-meeting15:18
*** ociuhandu has joined #openstack-meeting15:18
*** jamesmcarthur has quit IRC15:23
*** jamesmcarthur has joined #openstack-meeting15:36
*** jamesmcarthur has quit IRC15:43
*** dklyle has joined #openstack-meeting15:51
*** jamesmcarthur has joined #openstack-meeting15:52
*** dklyle has quit IRC15:53
*** david-lyle has joined #openstack-meeting15:53
*** jamesmcarthur has quit IRC15:57
*** jamesmcarthur has joined #openstack-meeting15:58
*** ociuhandu_ has joined #openstack-meeting16:00
*** ociuhandu has quit IRC16:03
*** macz_ has joined #openstack-meeting16:12
*** jamesmcarthur has quit IRC16:14
*** psahoo has quit IRC16:26
*** jamesmcarthur has joined #openstack-meeting16:29
*** jamesmcarthur has quit IRC16:29
*** ociuhandu_ has quit IRC16:30
*** jmasud has joined #openstack-meeting16:34
*** mlavalle has joined #openstack-meeting16:34
*** jamesmcarthur has joined #openstack-meeting16:36
*** ociuhandu has joined #openstack-meeting16:38
*** yasufum has quit IRC16:46
*** yasufum has joined #openstack-meeting17:03
*** ralonsoh has quit IRC17:31
*** ociuhandu_ has joined #openstack-meeting17:34
*** ociuhandu has quit IRC17:37
*** ociuhandu_ has quit IRC17:38
*** david-lyle is now known as dklyle17:39
*** ociuhandu has joined #openstack-meeting17:56
*** ociuhandu has quit IRC18:01
*** yasufum has quit IRC18:04
*** rpittau is now known as rpittau|afk18:08
*** jmasud has quit IRC18:32
*** jmasud has joined #openstack-meeting18:33
*** e0ne has quit IRC18:43
*** e0ne has joined #openstack-meeting18:56
*** e0ne has quit IRC19:35
*** rcernin has joined #openstack-meeting19:49
*** e0ne has joined #openstack-meeting20:00
*** e0ne has quit IRC20:00
*** ociuhandu has joined #openstack-meeting20:04
*** e0ne has joined #openstack-meeting20:16
*** rcernin has quit IRC20:20
*** rcernin has joined #openstack-meeting20:20
*** jamesmcarthur has quit IRC20:22
*** e0ne has quit IRC20:25
*** SpamapS has quit IRC20:52
*** jmasud has quit IRC20:58
*** acoles has joined #openstack-meeting20:59
timburke_#startmeeting swift21:00
openstackMeeting started Wed Feb  3 21:00:03 2021 UTC and is due to finish in 60 minutes.  The chair is timburke_. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: swift)"21:00
openstackThe meeting name has been set to 'swift'21:00
timburke_who's here for the swift meeting?21:00
mattoliverauo/21:00
seongsoochoo/21:00
kota_o/21:00
rledisezo/21:00
claygo/21:01
acoleso/21:01
timburke_as usual, the agenda's at21:01
timburke_#link https://wiki.openstack.org/wiki/Meetings/Swift21:01
timburke_first up21:01
timburke_#topic vagrant swift all in one21:01
*** openstack changes topic to "vagrant swift all in one (Meeting topic: swift)"21:02
timburke_#link https://github.com/swiftstack/vagrant-swift-all-in-one21:02
*** zaitcev has joined #openstack-meeting21:02
timburke_i know clayg and i have been pretty heavy users of this tooling to set up our dev environments21:02
clayg๐Ÿด IT WHILE IT'S ๐Ÿ”ฅ21:03
timburke_but in the near future, it's likely to go away (as part of some long-standing cleanup necessary to get rid of the old swiftstack github account)21:03
rledisezme and alecuyer (and some other colleagues) used it a lot too. very useful21:03
*** e0ne has joined #openstack-meeting21:04
claygtimburke_: update as of today - there's a non-zero chance it will just end up living at github.com/nvidia/vagrant-swift-all-in-one ๐Ÿคทโ€โ™‚๏ธ21:04
claygeveryone here that uses it should still fork it now just in case21:04
timburke_i do wonder if it'd be good for us to have something like it moved in-tree...21:05
claygvirtualbox yes, vagrant maybe, chef NO (like HELL NO)21:06
timburke_could probably re-use a lot of the ansible playbooks we've already got for setting up probe tests21:06
claygtimburke_: SOLD21:06
rledisezit's so handy that i'm wondering if there is swift devs that does not use it :D21:06
seongsoochoI really love this tool :-)21:08
claygrledisez: apparently mattoliverau has "better things" that he keeps to himself21:08
timburke_it's the sort of thing i'm always a bit torn about -- it's way easier to stand up an environment, but there's definite value in having a range of setups that we each use. vsaio's definitely got some opinions baked in21:08
mattoliveraulol, I don't know about better :P21:08
mattoliverauI just have a dodgy bash script I wrote back when I needed to deploy a bunch on rackspace cloud that sets SAIO the way I want it (and am now used too). But it doesn't do all the things vsaio does. (like s3api).21:09
timburke_fwiw, i remember notmyname linking https://gist.github.com/notmyname/40b8131963346676dd18817aeb5ef799 a while back if anyone wanted to go virtualbox with no vagrant ;-)21:09
zaitcevI always follow our in-tree manual to set up SAIO.21:10
claygzaitcev: you are a hero ๐Ÿ˜21:10
zaitcevhttps://knowyourmeme.com/memes/no-take-only-throw21:11
timburke_๐Ÿค” i wonder if we could generate some bits of the manual based on in-tree playbooks....21:11
zaitcev"IT dog, how do you automate?"  "No automate" "Only type"21:11
claygtimburke_: the super weird thing about vsaio is the configuration - like it's opinionated, but supports *some* options (which in a few cases are like... flip this ONE config option to false ๐Ÿคจ)21:12
timburke_py3? yes/no21:12
claygright, then there's other options that are super useful - maybe when we port to in-tree ansible we can square that up to something more sensible21:13
timburke_(i *still* wish i had good tooling for working with mixed py2/py3 development)21:13
claygit'd be nice to have a change that requires some crazy config (servers-per-port) and you can include the saio stuff for reviewers to check it out!21:13
*** jmasud has joined #openstack-meeting21:14
mattoliveraumy dodgy one is: https://github.com/matthewoliver/simple_saio but ignore the ubuntu in the readme. I'm not sure what it really supports. I mainly using centos SAIOs atm and Opensuse probably works, well it did a few months ago.21:15
acolesIMHO a common dev and CI ansible setup would be great21:15
rledisezone thing that always bothered me is that it seems there is in the code stuff that are specific so that ir works in SAIO. I'm wondering if the one server/vm is still relevant in a world where docker is everywhere. I can imagine creating a real cluster just with some docker-compose file21:15
mattoliveraubut yeah, vsaio + ansible would be nicer.21:15
mattoliverauI have a some chef experience, and I didn't enjoy it :P21:15
*** e0ne has quit IRC21:15
timburke_anyway, i guess we covered what needed to be said. namely, vsaio is a repo that (might) go away, so if you want to keep using it, it's probably a good idea to fork it sooner rather than later21:15
claygrledisez: i think that's quite reasonable - the trick is porting probetests ๐Ÿค”21:16
timburke_i think it was also (vaguely) what notmyname was trying to do with runway21:16
claygs/might/probably/ go away - s/sooner rather than later/like right now... during this meeting/21:17
claygoh right runway!!!  that one might already be gone ๐Ÿค”21:17
timburke_yeah, that one's already gone21:17
clayghttps://gitlab.com/nvidia/proxyfs-ci/runway21:18
timburke_we can keep thinking about how best to do dev envs and how similar they need to be to CI vs prod vs some other crazy thing, but i think we should probably keep moving21:19
timburke_#topic sharding in train21:19
*** openstack changes topic to "sharding in train (Meeting topic: swift)"21:19
timburke_zaitcev, i haven't seen patches yet, how's it going?21:19
zaitcevI put together a stack of 18 patches, they pass unit tests.21:20
zaitcevThe 19th was much too hard, so I gave up.21:20
timburke_\o/21:20
claygdidn't sinatra do a song about "sharding in the rain"?21:20
zaitcevUnfortunately, I must focus on RBAC this week.21:20
timburke_no worries, and thank you for taking on the RBAC work!21:21
timburke_i just wanted to check in, make sure you weren't blocked21:21
zaitcevSo, I'm tempted to throw them into Gerrit in one big stack, just so they're not locked in my laptop.21:21
zaitcevAfter we talked about it last week, I wanted to feed them in batches of 4 or 5, to let review them easier.21:21
timburke_that's fine by me. i'll try to get through them quickly once they're up21:21
zaitcevI replaced Change-ID at least21:22
*** rcernin has quit IRC21:22
timburke_if possible, try to include the cherry-picked sha in the commit message; makes it a little easier for me to compare master vs stable21:23
zaitcevYes, I changed old Change-Id with Cherry-Picked-From.21:23
zaitcevThat's all21:23
timburke_#topic eventlet and ssl21:24
*** openstack changes topic to "eventlet and ssl (Meeting topic: swift)"21:24
timburke_#link http://lists.openstack.org/pipermail/openstack-discuss/2021-January/020100.html21:24
*** jmasud has quit IRC21:24
timburke_i was catching up on mailing list recently and saw zigo has been having trouble with eventlet and ssl in swift-proxy21:25
zigotimburke_: I found out that the issue is dnspython 2.0.21:25
timburke_i wanted to check if anyone has a ssl-enabled-keystone handy to try to repro21:25
*** jmasud has joined #openstack-meeting21:25
timburke_oh, curious21:26
zigotimburke_: The issue is swift-proxy connecting to Keystone to check credentials...21:26
zaitcevIronically I don't21:26
zaitcevI created a different region for Keystone and set Swift to talk using that region.21:26
zigoSo the problem is not a swift-proxy binding over SSL.21:26
rlediseztimburke_: we do have that, swift talking to a Keystone over SSL21:26
timburke_...i guess maybe dnspython imports ssl before eventlet's monkey-patched it?21:26
zigotimburke_: I can't tell, but it's definitively a monkey paching issue between dnspython and eventlet.21:27
timburke_i know i've seen similar recursion errors before, and it's been a matter of not monkey-patching early enough21:27
zigoThe same issue happens when Neutron tries to tell Nova (over the Nova API) that a VM port is up.21:27
zigoWell, I'd prefer if there was a strong movement to get out of this madness.21:28
zigoMonkey patching is a terrible idea.21:28
zigoIt has numerous times, and still bites hard...21:29
zigohttps://github.com/eventlet/eventlet/issues/619 <--- The issue has been opened since 25th of June ...21:30
timburke_https://github.com/rthalley/dnspython/blob/v2.0.0/dns/query.py#L48 i guess? i don't see an ssl import on 1.16.0 (at a quick glance, anyway)21:30
timburke_yeah, monkey-patching's... not great. one more reason we ought to look at that PUT+POST(+POST) patch again... it bugs me that we're so tied to eventlet21:31
zigoMy guess, is that we do eventlet monkey patching early, but then dnspython does monkey patching *after*, and then accessing stuff on the SSLContext object breaks hard.21:32
zigo(I'm not sure, just double-guessing)21:33
timburke_oh -- it does its own monkey patching or something, is that it? ick21:33
zigoIsn't what you've just linked does?21:34
zigo(ie: creating an SSLSocket object...)21:34
timburke_does anyone have bandwidth to try to repro/fix the issue? having a pin on a two-year-old version of dnspython doesn't seem sustainable21:35
zigoIt's also currently completely broken in both Fedora and Debian (both have dnspython 2.0.x).21:35
zigoI'm trying to push to revert to 1.16.0, but I'm not sure I'll be successful.21:36
*** jmasud has quit IRC21:36
claygtimburke_: does anyone remember why we depend on dnspython?21:36
zigoclayg: eventlet does depend on it ...21:36
*** ociuhandu has quit IRC21:36
claygcname_lookup21:37
zigo python-eventlet (master)$ cat setup.py | grep dns21:37
zigo        'dnspython >= 1.15.0, < 2.0.0',21:37
timburke_so we *do* use it for cname_lookup, but the bigger issue seems to be that if you have it installed for the sake of something else, it'll break ssl in eventlet-ified processes21:38
zigoIndirectly, yes.21:38
zigoWe use keystoneauth, which calls requests, which calls urllib3.21:39
zigoUrllib3 access the SSL socket SSLContext.options object, and when it does ... big crash !21:39
zigoI believe the issue is because this:21:40
zigohttps://github.com/eventlet/eventlet/blob/master/eventlet/green/ssl.py#L44921:40
zigoisn't in use because of dnspython overriding the eventlet monkey patching.21:40
zigoI may be wrong, but so far, that's where I am...21:41
timburke_all right, i'll look into it. the dnspython tip was useful, looks like i might have a repro now!21:41
zigoWhat's the intention behind this:21:42
zigohttps://github.com/rthalley/dnspython/blob/v2.0.0/dns/query.py#L5821:42
zigo?21:42
timburke_#topic orphaned shard ranges21:42
*** openstack changes topic to "orphaned shard ranges (Meeting topic: swift)"21:42
zigoOk, thanks.21:42
zigotimburke_: Feel free to ping me anytime and we can discuss this later.21:42
timburke_zigo, i think it's just trying to stub out enough to prevent NameErrors and the like in case ssl isn't available21:43
* zigo will try to patch this out, just to see if it continues to work ...21:43
timburke_i know we picked up https://review.opendev.org/c/openstack/swift/+/771086 recently to prevent us from running into this orphaned-shard situation...21:45
timburke_is https://review.opendev.org/c/openstack/swift/+/770529 still viable for cleaning up any orphans that may already be on disk? or should we abandon that?21:46
mattoliverauyup, and that stops them being created.21:46
mattoliverauThere is work on getting the new shrink code working.21:46
mattoliverauacoles: has a chain starting: https://review.opendev.org/c/openstack/swift/+/77188521:47
timburke_yeah, maybe i should change the agenda item to cover shrinking generally ;-)21:47
mattoliverauyeah21:47
mattoliverauthe start of the chain will allow the root to provide the final shard acceptor as it's self when collapsing. (to keep it root driven)21:48
mattoliverauacoles recently did an awesome job of simlifying that with a auditing state21:49
acolesI prefer the root driven shrink & delete approach rather than the shard self-determination in https://review.opendev.org/c/openstack/swift/+/77052921:49
mattoliverau+121:49
mattoliveraulater on that chain is the new compact shard-manage-shard-ranges command21:49
mattoliverauwhich reworks how shrinking works in the sharder.21:50
acolesin general the shrinking and overlap repair is coming along nicely, but we uncovered a couple of bugs along the way21:50
mattoliverauOnce all these peices are done, orphan shards will be dealt with. initially manually, but its moving in the right direction for automatically too.21:50
acolesmattoliverau: has fixed one https://review.opendev.org/c/openstack/swift/+/77383221:50
acolesI'm about to push another fix, these are both bug fixes in addition to the new feature in swift-manage-shard-ranges commands21:51
acolesso its been an interesting journey :)21:52
mattoliverau:)21:52
timburke_cool! sounds like things are moving right along. blocked on anything?21:52
acolestimburke_: not enough hours in a day ! :)21:54
mattoliveraunot right now, just testing, reviews, coding.. and confidence we've fixed all the bugs :P21:54
acolesthere's the other bug fix https://review.opendev.org/c/openstack/swift/+/77400221:54
*** SpamapS has joined #openstack-meeting21:54
timburke_all right then21:54
timburke_#topic relinker21:54
*** openstack changes topic to "relinker (Meeting topic: swift)"21:55
acolesnote: these bugs would not impact *sharding*, just shrinking of shards21:55
timburke_i'm still working on some relinker enhancements, and wanted to call out a couple things21:55
timburke_first, my patches are (mostly) in a single chain now, so it's easier to try out all the improvements at once by checking out the end of the chain21:55
timburke_second, the first couple patches in the chain make it so you can point the relinker at a config file to read most (but not quite all) of the cli flags21:56
timburke_that was mostly because i realized we've got a bunch of options that should already be in you [DEFAULT] section of your object-server.conf (--swift-dir, --devices, --skip-mount-check)21:57
timburke_with https://review.opendev.org/c/openstack/swift/+/772419, --user21:57
timburke_i was mainly wondering if the config file seemed like as reasonable idea to everyone; i can't think of any other one-off tools we have in the swift repo that would go read a conf file...21:58
mattoliverauthe config file is still optional tho right? you can still use cli ops if need be.21:59
mattoliverauSo I think it makes sense to allow a config, esp when most of the options may already be set. But also it optional so wont stop how others may already be using the tool.21:59
timburke_yup -- existing cli tooling should all still work21:59
mattoliveraugreat job22:00
timburke_with that in mind, should i make sure that all config options get CLI args?22:00
acolestimburke_:+1  I think it is very reasonable22:00
acoles+1 was for having a conf file. not sure if you *must* expose all the options if they are beyond current cli22:01
acolesif the defaults are sensible22:02
mattoliverauI think we're at time :(22:02
timburke_yeah, i was noticing that, too ;-)22:02
timburke_thank you all for coming, and thank you for working on swift!22:02
timburke_#endmeeting22:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"22:02
openstackMeeting ended Wed Feb  3 22:02:30 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2021/swift.2021-02-03-21.00.html22:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2021/swift.2021-02-03-21.00.txt22:02
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2021/swift.2021-02-03-21.00.log.html22:02
*** rcernin has joined #openstack-meeting22:05
*** rcernin has quit IRC22:06
*** rcernin has joined #openstack-meeting22:07
*** zaitcev has left #openstack-meeting22:12
*** vishalmanchanda has quit IRC22:30
*** slaweq has quit IRC22:41
*** slaweq has joined #openstack-meeting22:43
*** rcernin has quit IRC22:45
*** slaweq has quit IRC22:47
*** thgcorrea has quit IRC23:09
*** bbowen_ has quit IRC23:24
*** tosky has quit IRC23:54

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!