Wednesday, 2018-09-19

*** gyee has quit IRC00:19
*** DHE has joined #openstack-swift00:34
*** two_tired2 has joined #openstack-swift00:42
openstackgerritSam Morrison proposed openstack/swift master: WIP: s3 secret caching  https://review.openstack.org/60352901:35
kota_good morning02:09
*** jistr has quit IRC03:00
*** jistr has joined #openstack-swift03:00
kota_mattoliverau: btw do you have time to look at p 447129 ? I and rledisez like to make it progressed but me also worried you may find any issue with your good eyes. If you have any concerns so far, I'd like to help your reviews.03:31
patchbothttps://review.openstack.org/#/c/447129/ - swift - Configure diskfile per storage policy - 20 patch sets03:31
openstackgerritSam Morrison proposed openstack/swift master: s3 secret caching  https://review.openstack.org/60352903:51
*** two_tired2 has quit IRC04:21
*** rcernin has quit IRC05:30
*** rcernin has joined #openstack-swift05:30
*** silor has joined #openstack-swift05:35
*** geaaru has joined #openstack-swift05:44
*** rcernin_ has joined #openstack-swift06:04
*** rcernin has quit IRC06:06
*** kirubak has joined #openstack-swift06:08
kirubak?help06:11
kirubaki am trying to build swift-rocky for xenial, do we have the location of the debian package that i can use to build rocky on xenial ?06:12
*** rcernin has joined #openstack-swift06:34
*** rcernin_ has quit IRC06:36
kota_kirubak: I'm not sure ubuntu/debian package is actively maintained. Instead, you can find tar ball of python package around http://tarballs.openstack.org/swift/06:48
kota_kirubak: specifically, http://tarballs.openstack.org/swift/swift-stable-rocky.tar.gz is the rocky stable one.06:49
sorrisonkirubak: ubuntu package up 2.19.0 in their cloud archive for bionic06:57
*** rcernin has quit IRC07:06
zigonotmyname: Around? Or sleeping already?07:10
*** hoonetorg has quit IRC07:17
*** mikecmpbll has joined #openstack-swift07:21
*** hoonetorg has joined #openstack-swift07:30
*** gkadam has joined #openstack-swift07:36
*** e0ne has joined #openstack-swift07:36
*** mikecmpbll has quit IRC07:43
*** e0ne has quit IRC07:48
*** gkadam has quit IRC07:57
*** mikecmpbll has joined #openstack-swift08:01
*** e0ne has joined #openstack-swift08:25
*** e0ne has quit IRC08:26
*** e0ne has joined #openstack-swift08:33
*** e0ne has quit IRC09:02
seongsoocho:-(  When I add a new node, object-replicator(and rsync) degrades the performance of object-server...09:22
seongsoochoThere are a lots of small size files in object server and utilization of disks are almost 8009:22
seongsoocho80%.. Could this be the cause?09:23
alecuyerseongsoocho: It could be. How many files do you have per object-server, and how much RAM ? if all inodes cannot be cached, you may see performance degradation09:27
*** e0ne has joined #openstack-swift10:47
*** kirubak has quit IRC12:04
*** patchbot has quit IRC12:07
*** patchbot has joined #openstack-swift12:08
*** e0ne has quit IRC12:20
*** DHE has quit IRC12:46
*** silor has quit IRC12:48
seongsoochoalecuyer:  sorry for late reply.  It is almost 100milion files per object servers and 64GB RAM12:51
*** DHE has joined #openstack-swift12:55
*** kukacz_ is now known as kukacz13:00
*** geaaru has quit IRC13:41
notmynamezigo: good morning. what's up?14:43
zigonotmyname: Everything's fine ! :)14:44
notmynamegreat!14:44
zigonotmyname: I got my cluster setting-up correctly ...14:44
zigonotmyname: I'm writting a provisionning tool, which is puppet-openstack.14:44
zigonotmyname: The first thing that I'm doing is a swift cluster.14:44
zigoSo far, so good ...14:44
zigo:)14:44
zigonotmyname: I just discovered this though: https://bugs.debian.org/90917114:45
notmynamecool14:45
openstackDebian bug 909171 in python3-swiftclient "python3-swift never exits" [Important,Open]14:45
zigoAny idea what could be doing this?14:45
zigoonovy: ^14:46
notmynameno that sounds odd. may be good to test with curl to see if it's a particular server-side thing or something in the client14:46
zigonotmyname: That's not the issue. It works perfectly with openstackclient or the python 2 version of swiftclient.14:47
zigo(Debian has both clients...)14:47
zigoSo, this looks like a Py3 problem with the cli.14:47
notmynameok. just trying to find a way to make it simpler to debug. IIRC there's a --debug flag you can pass to the CLI. maybe that will reveal something14:48
zigoNothing that I saw helped with --debug.14:48
notmynamethat's unfortunate14:48
zigoI'm doing a redeployment from scratch, I can maybe give you the output of --debug later when it's deployed again in my PoC.14:51
onovyas I wrote to bug, I can't reproduce it14:52
onovyBUT I tested agains swauth, not keystone14:52
onovyso maybe it's keystoneauth related?14:52
onovyAND I tested @sid, zigo probably @stretch14:53
zigoyeah, stretch15:00
zigoUsing keystoneauth indeed.15:00
*** gyee has joined #openstack-swift15:37
notmynameAJaeger: done15:46
*** pcaruana has joined #openstack-swift15:47
*** e0ne has joined #openstack-swift16:07
*** e0ne has quit IRC16:17
*** pcaruana has quit IRC16:27
*** e0ne has joined #openstack-swift16:31
*** mikecmpbll has quit IRC16:34
*** e0ne has quit IRC16:35
openstackgerritTim Burke proposed openstack/swift master: s3 secret caching  https://review.openstack.org/60352916:53
AJaegerthanks, notmyname17:52
AJaegerswift cores, small cleanup for zuul.yaml, could you import https://review.openstack.org/#/c/600732/ , please?17:54
patchbotpatch 600732 - swift - Use templates for cover and lower-constraints - 1 patch set17:54
tdasilvaAJaeger: just for the sake of my understanding, in this case a template is a "zuul job template", not to be confused with an 'ansible template', correct?18:08
AJaegertdasilva: yes18:09
AJaegertdasilva: one as listed here: https://docs.openstack.org/infra/openstack-zuul-jobs/project-templates.html18:09
notmynameAJaeger: I'm looking forward to having these sort of patches settle down. I love the move to put stuff in each project repo. maybe these patches are necessary because of that. but there's no real way for me to validate them or know what's right or wrong. so all I can really do is think "oh, some -infra proposed this, gate seems to pass, I guess I should +A".18:13
notmynameI'll land this, but I'm worried about maintainability18:13
notmynametdasilva: timburke: clayg: I don't know if you feel the same way ^^18:15
AJaegernotmyname: I'm happy to answer questions  - now or also later...18:15
AJaegernotmyname: I understand your concerns, my change was made to make maintainability easier for you.18:15
AJaegernotmyname: feel free to drop in anytime in #openstack-infra18:16
notmynameyeah, I understand. I'm just hoping the setup phase is nearly done :-)18:16
AJaegernotmyname: I'm not aware of anything else coming (famous last words ;)18:16
notmynamelol18:16
*** silor has joined #openstack-swift18:17
*** zaitcev has joined #openstack-swift18:17
*** ChanServ sets mode: +v zaitcev18:17
tdasilvaAJaeger: for this particular patch, what's the benefit of the template? over listing the actual job?18:18
tdasilvai think i got it: http://git.openstack.org/cgit/openstack-infra/openstack-zuul-jobs/tree/zuul.d/project-templates.yaml#n50318:18
timburkei just realized: we almost certainly shouldn't be using the generic openstack-tox-lower-constraints job -- it isn't going to get us an xfs tmpdir, so we skip ~1400 tests18:19
AJaegertdasilva: cosmetics ;) It gives us the chance to change jobs in one place instead of in each repo18:19
AJaegertimburke: oh, indeed - yes18:19
tdasilvabasically the template already lists the job(s) to run, but also where to run (i.e., check, gate, etc)18:19
AJaegertdasilva: yes, exactly18:19
notmynametimburke: good call. but shoudl we replace the other one? or just add a new one?18:20
AJaegerwant me to propose a followup? or will one of you do it?18:20
notmynameI guess the generic one doesn't do much that's useful if we've got another that uses xfs18:20
AJaegernotmyname: agreed18:20
tdasilvazaitcev: just a reminder about swift community meeting later today...18:24
zaitcevtdasilva: thanks18:25
zaitcevtimburke: I always do  TMPDIR=/var/tmp tox -e py2718:25
notmynametimburke: are you in the middle of stuff? will you be able to make a better constraints job for us? or should I work on it?18:25
zaitcevSomeone wrote me about my kernel patch to have xattr on tmpfs while we were in PTG18:26
notmynameI /think/ all that's needed is to inherit from the upstream on, set the envvar in .zuul.yaml then use that job instead of the generic one in the queues18:27
zaitcevPeople still need that, but nobody is willing to put in enough work. Kinda like container sharding used to be.18:27
notmynamezaitcev: everything needs a sponsor18:27
zaitcevnotmyname: I can work out a transfer to kernel team...18:28
zaitcevnow that Tim is on py3 and Clay is rewriting PUT+POST with verbs18:28
zaitcevnot much left to do18:28
notmynamenah, we still *really* need you with py3 work18:28
timburkenotmyname: i'm working on something else at the moment; if you could work on it, that'd be great18:29
notmynametimburke: kk18:29
*** mikecmpbll has joined #openstack-swift18:29
notmynameAJaeger: did my comment earlier about how to make a better coverage job sound right?18:29
AJaegernotmyname: yeah, should work - give it a try ;) feel free to add me as reviewer18:30
notmynameAJaeger: thanks18:30
timburkezaitcev: speaking of py3, i might have you take a look at my alternative approach to p 592761 -- see p 602822 / p 60282318:30
patchbothttps://review.openstack.org/#/c/592761/ - swift - py3: Adapt direct_client and internal_client - 7 patch sets18:30
patchbothttps://review.openstack.org/#/c/602822/ - swift - py3: port direct_client - 2 patch sets18:30
patchbothttps://review.openstack.org/#/c/602823/ - swift - py3: port internal_client - 2 patch sets18:30
notmynameAJaeger: should the "irrelevant-files" directive match for the check and gate queues? I see some things where it doesn't right now18:38
AJaegernotmyname: your call ;) I would match them in general so that the same jobs really runs in same situations.18:40
timburkenotmyname: pretty sure i caused some of that. i tried to capture my thinking in https://github.com/openstack/swift/blob/2ddc979e1d6fa680e8867249e11224d2bb1ca477/.zuul.yaml#L183-L18618:48
notmynametimburke: I see where you're coming from. was wondering from AJaeger on the aesthetics or The Way It Should Be (tm) view ;-)18:49
openstackgerritJohn Dickinson proposed openstack/swift master: Use templates for cover and lower-constraints  https://review.openstack.org/60073218:53
openstackgerritJohn Dickinson proposed openstack/swift master: set up a lower constraints job that uses an XFS tmpdir  https://review.openstack.org/60387018:53
openstackgerritJohn Dickinson proposed openstack/swift master: set up a lower constraints job that uses an XFS tmpdir  https://review.openstack.org/60387018:55
*** silor has quit IRC19:16
openstackgerritFatema Khalid Sherif proposed openstack/swift master: Enabling direct_client users to overwrite X-Timestamp  https://review.openstack.org/60326119:45
notmynameFYI the CI jobs are super backed up. clarkb sent an email about what's going on and some ways to help. put simply, there's flaky tests and a bunch of repeated failures tracked on http://status.openstack.org/elastic-recheck/index.html that aren't resolved. I've checked the various gate tracking pages, and there's not really anything that affects swift right now20:11
notmyname(well, one transient zuul error two days ago)20:12
notmynamethe team meeting is still happening today (in 37 minutes from now. I won't be leading it, but tdasilva will20:24
notmynameI've put patchbot in there already20:24
notmynameI'll be around before and after the meeting, but I have a conflicting personal commitment I need to take care of today20:24
notmynamefatema_: oh hi! you're pushing patches. how's it going? any questions?20:30
mattoliveraukota_: I'll try and find time to look today sometime. I'm on leave this week, but will try to give it another pass before I can review better first thing next week. If you can wait that long.20:31
fatema_notmyname:  well I am still trying to understand the context of the bug as the implementation is there. But there has been objections about the context20:34
fatema_thank you for checking :D20:34
notmynamefatema_: please do not hesitate to ask in here or in gerrit when you have questions.20:35
notmynamefatema_: and if you're not always logged into irc, services like https://www.irccloud.com can make it easier. clayg uses that one20:36
timburkeidk about "objections" -- but it'd definitely help to have clayg chime in with some more guidance (since he reported the bug)20:36
claygwhich bug20:36
claygirccloud.com is great - and I can use it on my phone and I don't have to pay for a bouncer20:37
timburkehttps://launchpad.net/bugs/175725020:37
openstackLaunchpad bug 1757250 in OpenStack Object Storage (swift) "direct_client gen_headers is inconsistent" [Wishlist,New]20:37
claygI used it free for awhile, but ultimately the $5/mo was cheaper than running irssi in a cloud vm so I'm very happy20:37
claygthere's even a desktop client I use on my ubuntu laptop!20:37
timburkeso like, how valid is the use-case "i don't want to send any x-timestamp and let the server figure it out instead"?20:37
fatema_notmyname:  I am using irccloud now and it's very nice.20:38
timburkeclayg: personally, i kinda wanna get rid of both add_ts and add_user_agent20:39
* notmyname is out for a bit20:39
notmynameI'll catch up on meeting logs later20:39
timburkeand have the helper always add those headers if absent20:39
notmynamethansk tdasilva!20:39
claygyeah I think the intent was more clear with "ensure_ts"20:40
fatema_if I am understanding this rightously, then I see that no need for the user to be able to override those two variable as timburke  says20:40
claygI believe there was a specific add to direct_client recenty-ish where acoles had to twist gen_headers because it wasn't letting him say what he needed explicitly20:41
claygi'd be around the same time the bug was filed20:41
claygif there a need for more context20:41
clayganyway, I think half the job was not just re-write gen_headers - but make it called in all the direct_client methods20:41
claygsome methods like "get_XXX" can ensure_ts=False as they don't require a X-Timestamp and shouldn't add one unless the caller passes through headers20:42
timburkeyeah, i still don't want that :P i want a no-arg helper so x-timestamp is always in the header dict. and if we *really* want to support not sending an x-timestamp, make the caller pass it as None or something20:42
claygwhich I think is the big motivation for the change - not all direct_client methods support headers kwarg because of this opinionated stuff in gen_headers20:43
claygmaybe i'm mis-remembering20:43
timburkeseems to make sense. maybe i could be talked out of my stance. but passing x-timestamp can cause differences even on GET...20:44
timburke(iirc)20:44
claygtimburke: it's not obvious to me why you care if an ignored header get's sent along with the safe http requests ... oh ... CAN IT?20:44
fatema_ok I was still on partial-bug fix but still not getting why woul the user need to override x-timestamp ?20:44
claygmaybe that was the problem... let me find that other review20:45
timburkewell, i'm thinking of expired-but-not-yet-reaped objects... i *think* changing x-timestamp can turn that 404 back to a 20020:45
fatema_ok this seems legit timburke20:46
claygmeh, looks like the issue was more about the user_agent p 56574520:47
patchbothttps://review.openstack.org/#/c/565745/ - swift (feature/deep-review) - Add shard range support to container server (MERGED) - 11 patch sets20:47
claygIIRC the thinking at the time was - why should the method ever overwrite the existing ts/agent - shouldn't the kwarg be more like "ensure_XXX"20:47
clayg🤷‍♂️20:48
clayg@timburke that's surprising to me if that's true20:48
claygdisk_file.open(current_time=req_timestamp) ... interesting20:50
timburkeclayg: i think it might be needed for reconstruction? in case there's a POST that kicked out the expiration... or something20:51
claygp 53259520:51
patchbothttps://review.openstack.org/#/c/532595/ - swift - Use X-Timestamp when checking object expiration (MERGED) - 7 patch sets20:51
claygThere was no associated bug, look like it made sense to Sam & Tim tho20:51
claygi guess it's stupid for one server to 404 and another 200 so... that's fine20:52
claygso maybe remove add_ts and instead just `if 'x-timestamp' not in ...` that's fine20:52
fatema_ok how is the bug and the patches related ?20:53
claygwe still have methods like e.g. `direct_head_container` that don't use hdrs_in when they call gen_headers - I think that's mostly what the bug is about ifxing20:54
claygfatema_: read the bug and commit messages very carefully and ask a more specific question please.  😁20:54
*** m_kazuhiro has joined #openstack-swift20:55
fatema_clayg:  ok will do20:55
clayg👍 sorry!!! 😊20:55
kota_morning20:57
timburkefatema_: so some background on x-timestamp and how it relates to eventual consistency. 'cause i think it might be handy regardless :-)20:57
timburkex-timestamp is how swift orders events. a client does PUT, POST, PUT to the same object, but because of failures individual object servers may only see PUT, POST or PUT, PUT and find out about the missing events during replication20:57
timburkeso think about the latter one: server sees a PUT, stores it. sees another PUT, overwrites it. asynchronously, it finds out there was a POST -- but should it actually apply the metadata?20:57
timburkeby assigning timestamps at the proxy for each request, we get a more-or-less well-ordered system: PUT at t0, POST at t1, PUT at t2. the object-server can see that the POST at t1 was superseded by the PUT at t2 and basically ignores it during replication20:57
tdasilvameeting time @ #openstack-meeting21:00
tdasilvaclayg, zaitcev joining us?21:02
claygzaitcev: I'd be cool to discuss more immediately after the meeting - but like I said, I don't have any ideas I'm in love with right now21:37
openstackgerritTim Burke proposed openstack/swift master: Use latest eventlet in probe tests  https://review.openstack.org/60252621:59
claygzaitcev: so I have a few - but honesty it's 5pm here so I need to run in a bit - we could schedule something for later in the week - or get an email thread going?22:01
kota_btw, anyone knows where we can find our team photos?22:02
claygI'm commited to finishing STAGE+UPDATE+COMMIT to the point where all the tests pass, but less concerned about the polish considering that I don't really think it's the the right path forward over all22:02
tdasilvakota_: yeah i had seen a link for them22:03
tdasilvaand added to my swift photo album22:03
*** m_kazuhiro has quit IRC22:03
kota_tdasilva: nice, could you share it?22:03
kota_i wanna get it22:04
tdasilvakota_: https://photos.app.goo.gl/CwuHgqN6bJMpGzBw822:04
kota_tdasilva: much appreciated!22:04
tdasilvai'm trying to find team photos from 2017 ptg denver to add there22:05
zaitcevclayg: just hit me with a review link... add me as a reviewer22:05
claygzaitcev: rock on - as soon as I get it up22:05
claygthen we can regroup22:05
tdasilvaok, gotta run too22:06
* notmyname back22:06
notmynametdasilva: thanks!22:06
tdasilvanotmyname: yw22:07
kota_tdasilva: i may have the picture on my lap top in my office, trying to find out to share22:09
kota_probably tomorrow in my time because of a dayoff today.22:09
notmynametdasilva: kota_: http://d.not.mn/swift_team_denver_ptg.jpeg and http://d.not.mn/swift_team_denver_ptg_hats.jpeg22:10
kota_nice work notmyname22:10
fatema_according to this patch 532595, if I understand correctly this means it is safer/ preferred to send x-timestamp, is this right ?22:16
patchbothttps://review.openstack.org/#/c/532595/ - swift - Use X-Timestamp when checking object expiration (MERGED) - 7 patch sets22:16
openstackgerritSam Morrison proposed openstack/swift master: s3 secret caching  https://review.openstack.org/60352922:26
sorrisontimburke: now with unit tests :-)22:26
timburkethanks sorrison! i'll try to take a look... soon. not quite sure when, unfortunately. kota_ might be interested too, though22:31
sorrisoncheers22:32
*** hoonetorg has quit IRC22:41
*** rcernin has joined #openstack-swift22:44
*** mikecmpbll has quit IRC22:51
*** hoonetorg has joined #openstack-swift22:58
*** mvkr has joined #openstack-swift23:10

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