Tuesday, 2017-03-28

kota_good morning00:02
*** sams-gleb has joined #openstack-swift00:06
mattoliveraukota_: morning00:10
kota_morning mattoliverau00:11
kota_acoles: thanks for updating the patches00:21
kota_acoles: looking at the irc log, we should consider what could be a problem with uuid case. i didn't think the case if someone could copy/paste the builder file???00:22
kota_and it could have same uuid :/00:23
kota_it could be just a mitagation but some commands like "reset" could be useful?00:25
kota_i don't think so much because what he should do is just creating brand-new ring builder file for the case.00:26
kota_the ring.gz file is usually copy/paste to deploy into the cluster env, but copy/pasting *builder* file sounds crazy...00:27
*** tonanhngo has quit IRC00:35
*** catintheroof has joined #openstack-swift00:35
*** gkadam has quit IRC00:40
*** tonanhngo has joined #openstack-swift00:45
*** gyee has quit IRC00:47
openstackgerritTim Burke proposed openstack/swift master: fixup! Add container sharding to Swift containers  https://review.openstack.org/45049100:49
*** tonanhngo has quit IRC00:50
*** jamielennox is now known as jamielennox|away00:54
timburkemattoliverau: to warn you, i'm out later this week and all of next week, but i'll get as far as i can on sharding before i go00:56
mattoliverautimburke: kk, you've already given me alot to work on :) and thanks.00:58
*** jamielennox|away is now known as jamielennox00:59
openstackgerritjunboli proposed openstack/swift master: Use swift tempurl instaed of swift-temp-url  https://review.openstack.org/45049401:02
*** vint_bra has joined #openstack-swift01:20
tone_zGood morning!01:20
*** timburke has quit IRC01:25
*** AndyWojo has quit IRC01:25
*** hugokuo has quit IRC01:25
*** vint_bra has quit IRC01:26
*** vint_bra has joined #openstack-swift01:26
mattoliverautone_z: morning!01:27
*** AndyWojo has joined #openstack-swift01:27
*** timburke has joined #openstack-swift01:28
*** ChanServ sets mode: +v timburke01:28
tone_zmattoliverau: morning!01:28
*** hugokuo has joined #openstack-swift01:28
*** sams-gleb has quit IRC01:40
*** catintheroof has quit IRC01:41
*** JimCheung has quit IRC01:41
*** zhurong has joined #openstack-swift01:53
*** vint_bra has quit IRC02:14
kota_i wonder if someone knows func-encryption gate could be broken?02:21
kota_the patch acoles updated failed at http://logs.openstack.org/21/441921/6/check/gate-swift-tox-xfs-tmp-func-encryption-ubuntu-xenial/857bfd6/console.html but it should not be related to the func tests02:22
kota_that is because it touches only offline ring tools02:23
*** sams-gleb has joined #openstack-swift02:38
*** sams-gleb has quit IRC02:42
openstackgerritjunboli proposed openstack/swift master: Fix subclass call super class's constructor  https://review.openstack.org/45052302:45
*** _JZ_ has quit IRC03:01
*** links has joined #openstack-swift03:35
zaitcevGuys. We have someone running Swift in Docker containers, right? I heard Project Runway does that.03:35
zaitcevHow do they handle logging? The only thing that comes to mind is to install rsyslog in the container, than VOLUME /var/log. This has the disadvantage of not having any logrotate. Ideally I'd like to ship logs outside of the running container somehow.03:37
*** blair has quit IRC03:51
*** zhurong has quit IRC03:57
*** blair has joined #openstack-swift03:57
kota_zaitcev: I didn't actually, but i think storlets also does simliar thing (log to /var/log in the container and then host redirect it to the rsyslogd) so eranrom may know something on that04:06
*** jamielennox is now known as jamielennox|away04:09
mattoliverauzaitcev: runway might go to docker, but atm (unless its changed) is't LXC. You can do bind mounting in LXC (or the equivelnt) which means you can place the logs outside the container if need be.04:18
mattoliveraubut yeah, you probably need a syslog04:18
zaitcevwell, bind works I guess04:19
zaitcevThe host has its own Swift running, I'm concerned the logs will intermingle04:19
kota_mattoliverau: i think it's better than /var/log thing04:19
kota_wow, both inside/outside swift is running!?04:19
mattoliverauzaitcev: if thats the case then you might want to add a rule to syslog to change the naming slightly.04:20
kota_interesting04:20
mattoliverauyou can talk to syslog as a dev, so you might be able to push through the dev, and then talk to it directly. not that that is supported in Swift.. but could be an option.04:20
zaitcevright, I meant to tinker with it, just not sure of success04:21
mattoliverauthen you won't need an addiontal syslog, though you'd need to do some magic on the hosts to put things in the right place.04:21
*** psachin has joined #openstack-swift04:22
*** klrmn has quit IRC04:27
*** jamielennox|away is now known as jamielennox04:30
*** MarkMielke has quit IRC04:35
*** sams-gleb has joined #openstack-swift04:39
*** sams-gleb has quit IRC04:44
*** zhurong has joined #openstack-swift04:55
mahaticgood morning04:57
mahaticnotmyname: after the submissions over here - http://forumtopics.openstack.org/, is there anything the community can do, like voting? I don't think so, I believe the TC and co will decide what's gonna be at the forum?04:58
kota_mahatic: morning, i don't think we can vote it05:04
kota_mahatic: the format looks like similar with the older design summit session proposal (maybe G or H, IIRC) and then...05:05
kota_mahatic: ah, it might be able to *review* it to give your feedback05:06
kota_I can see the box to write something, e.g. http://forumtopics.openstack.org/cfp/details/3305:07
mahatickota_: oic05:07
kota_the intersting point to me is we have only 40 proposal in total05:07
mahatickota_: but not sure if they'd consider those "comments" right05:07
kota_the last item on top of the page shows, http://forumtopics.openstack.org/cfp/details/4005:07
kota_mahatic: yeah, need to ask05:08
kota_40 proposals, swift takes 8 of 40 -->>> 20% of openstack is swift :P05:09
mahatic:D yes!05:09
kota_idk it works as expected by tc05:09
mattoliveraumahatic: morning05:10
mahaticmattoliverau: o/05:10
mahatickota_: re 20%, so we still have opportunity to up the number of proposals for swift then ;)05:11
kota_mahatic: exactly ;-)05:11
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient master: Updated from global requirements  https://review.openstack.org/8925005:17
*** rcernin has joined #openstack-swift05:38
*** sams-gleb has joined #openstack-swift05:42
*** sams-gleb has quit IRC05:48
*** zaitcev has quit IRC05:50
openstackgerritjunboli proposed openstack/swift master: update doc infos to ocata  https://review.openstack.org/45057105:53
*** ChubYann has quit IRC05:54
*** bkopilov_ has quit IRC06:19
openstackgerritMerged openstack/swift master: Remove unused returned value object_path from yield_hashes()  https://review.openstack.org/45026906:19
*** bkopilov has quit IRC06:20
*** silor has joined #openstack-swift06:26
*** silor1 has joined #openstack-swift06:31
*** silor has quit IRC06:33
*** silor1 is now known as silor06:33
*** jamielennox is now known as jamielennox|away06:36
*** hseipp has joined #openstack-swift06:45
*** sams-gleb has joined #openstack-swift06:49
*** mtreinish has quit IRC06:57
*** mtreinish has joined #openstack-swift06:58
*** admin6 has joined #openstack-swift07:12
alecuyergood morning07:13
*** pcaruana has joined #openstack-swift07:13
*** sams-gleb has quit IRC07:17
*** tesseract has joined #openstack-swift07:18
*** cbartz has joined #openstack-swift07:20
*** jamielennox|away is now known as jamielennox07:21
*** jaosorior has joined #openstack-swift07:29
*** geaaru has joined #openstack-swift07:29
*** rcernin has quit IRC07:29
*** rcernin has joined #openstack-swift07:47
*** amoralej|off is now known as amoralej07:53
*** furlongm has joined #openstack-swift07:57
*** bkopilov_ has joined #openstack-swift08:00
*** bkopilov has joined #openstack-swift08:01
acolesgood morning08:04
*** rcernin has quit IRC08:06
*** rcernin has joined #openstack-swift08:07
*** hseipp has quit IRC08:09
*** rcernin has quit IRC08:10
*** rcernin has joined #openstack-swift08:10
acolesmahatic: in case you didn't notice, most of the composite ring patch you were reviewing has been squashed into patch 44192108:12
patchbothttps://review.openstack.org/#/c/441921/ - swift - Add Composite Ring Functionality08:12
kota_acoles: morning08:12
kota_and the composite ring one is under reviewing to me08:12
kota_acoles: just notification on that08:12
acolesmahatic: sorry I should have left a note on patch 449310 to say that08:12
patchbothttps://review.openstack.org/#/c/449310/ - swift - WIP Use uuid to differentiate component rings in c...08:12
kota_i mean patch 44192108:13
patchbothttps://review.openstack.org/#/c/441921/ - swift - Add Composite Ring Functionality08:13
mahaticacoles: good morning08:13
acoleskota_: hi! I hope I have not confused too much with squashing into 44192108:13
* kota_ is still thinking about "check_against_existing"08:14
acoleskota_: you're right - crazy to copy builder files, but our job is to plan for "crazy" sometimes :) the bigger concern is lost builder file and using write-builder from a ring.gz08:15
kota_acoles: ok, before thinking too much, can i leave my draft comment to ask you?08:15
acolesbut I left the uuid ideas in the follow on patch08:15
kota_yup08:15
acoleskota_: of course08:15
mahaticacoles: I did, I glanced to see the diff. I no longer see the "tuple" part as well, thanks.08:15
kota_k, do it now.08:15
acolesmahatic: yep I fixed the parentheses you spotted08:15
kota_acoles: I didn't run all code yet but i concerned at https://review.openstack.org/#/c/441921/6/swift/common/ring/composite_builder.py@214 mostly.08:17
*** mvk has quit IRC08:17
acoleskota_: that test failure is concerning...but it passed on recheck I think. hmmm08:19
acoleskota_: what was your concern here https://review.openstack.org/#/c/441921/6/swift/common/ring/builder.py@1673 ?08:21
*** kirill_ has joined #openstack-swift08:21
kota_acoles: on the func test perspective, i don't think it's related to the change because the existing swift functional tests never calls the new functionality (compose_rings, whatever) right?08:21
acolesis there a way to easily get a link to a specific comment in gerrit?08:21
acoleskota_: agree re func test, just worrying that it failed in general, but can't see how it relates to the patch08:22
kota_acoles: ah - sorry, https://review.openstack.org/#/c/441921/6/swift/common/ring/builder.py@1673 <- i should remove the comment, just I was starting to review from there and I was made sense already we will need it in composite_builder.py08:23
acoleskota_: ok. TBH IDK if me calling it "source" was such a great thing. It's ok. I am just frustrated by not having a *perfect* way to track builder "identity" :/08:25
acoleskota_: re. your comments at https://review.openstack.org/#/c/441921/6/swift/common/ring/composite_builder.py@214 ...08:25
*** oshritf has joined #openstack-swift08:27
kirill_hello everyone! is this an appropriate place to ask a question about swift3?08:28
kota_kirill_: it's ok here but #swift3 channel also works and it's for only swift3 rather than general openstack-swift08:30
acoleskota_: for now I deliberately kept this very simple - you cannot add or remove rings, only compose rings and re-compose the same rings, for example after a component rebalance. test_write_composite_ring_errors asserts that new builders must be same length as old. Once we understand other use cases (add, remove) we can and support but for no I was hoping to keep it simple.08:31
kota_acoles: ok, I like the opinion, "keep it simple"08:33
kota_acoles: that means... oh, I misread one thing08:34
kota_acoles: "if the new component shorter than old component, that's ok i.e. we can remove a (or some) builder(s) in the new_component" <- this is false08:34
kota_i skipped to look at the errors.append() at L213 so if the length is different, anyway, we will get a ValueError08:35
kota_s/skipped/missed/08:36
acoleskota_: yes, if new is shorter then there is an IndexError which is converted to an error08:36
acoleskota_: I have a question for you...08:37
kota_and current code looks still simple. if you want a new ring from different component, please you make it as different ring name.08:37
kota_acoles: sure08:37
acoleskota_: yes, for now if you want to add/remove components then start again with a new composite.ring.gz08:38
acoleskota_: ok, my question is about the source=builder_file08:38
kota_acoles: ok, please go ahead08:39
acoleskota_: builder_file can be relative path or an absolute path, so long as open() can find it. But. the suggestion on etherpad is that we *require* component ring builders to be in same dir as the composite-ring.gz, (again to keep things simple and not too brittle if paths change)08:40
acoleskota_: I don't want to make the builder.source be forced to have only the file name08:41
kota_acoles: let me check the etherpad, I didn't remember to write the requirement that we should locate it in a dir08:42
acolesi.e. basename - feels like that should not be something enforced in builder.py08:42
acoleskota_: I think it was mattoliverau suggestion08:42
kota_acoles: i found at L10008:44
acoleskota_: yes line 100,08:44
acoleskota_: so I am wondering if it is ok for composite_builder.py to be as it is now in the patch i.e. simply check that builder.source values are the same for each component, and then make whatever calls into composite_builder be responsible for what the value of builder.source is?08:45
*** rcernin has quit IRC08:46
acolesso if the sources should all be basenames, then the caller (a CLI for example) should ensure that the builders are loaded that way using only basename for builder_file08:46
*** rcernin has joined #openstack-swift08:46
*** mvk has joined #openstack-swift08:47
acolesbut if a caller wants to use some other way to track builders (e.g. relative path) then the caller can set builder.source appropriately08:47
kota_and the functionality in composite_builder doesn't care of it?08:47
acolescomposite_builder just checks that the builder.source has not changed for each component08:48
*** rcernin_ has joined #openstack-swift08:48
acolesIDK, I am trying to avoid putting something very rigid into composite_builder08:48
acolesat least, for now, when we are still figuring out exact use case08:49
acolesfor a CLI for example08:49
kota_acoles: I'm feeling the identifier(s) is (are) cared by CLI as possible could be better and then composite_builder will trust the identifiers, just checking the sameness08:51
kota_so...08:51
kota_that was why I removed the source file path in the patch, previously08:52
acoleskota_: ok. so let's leave the patch as it is but think some more about that issue. I am curious what we may learn about how others manage builders, ring rebalancing etc, other than using swift-ring-builder.08:52
acoleskota_: ah, which version - I looked back to version 3 for your previous use of  builder file08:53
kota_acoles: i think similar issue still exists in swift ring builder08:53
kota_acoles: that is because the dev check (existing ip/port/dev check) is in cli tool08:54
kota_swift.common.ring.RingBuilder.add_dev doesn't care the same failure domain08:54
kota_set the devs directly could be dengerous, doesn't it?08:55
kota_I hope validate() method work to check before finishing up the rebalance08:57
kota_though08:57
kota_acoles: re: which version, I remove the builder_file in patch set 408:59
kota_removed08:59
admin6acoles: kota: Hi guys, I’ve not been around for a while working on othe projects, but I’m now looking back (a bit) into swift. :-)08:59
acolesadmin6: hi08:59
acoleskota_: where did you remove the source file path? I can't see that yet in patchset 309:00
admin6I’d like to highlight back on bugs 1631144 and 1633647. I’m (still) using swift 2.7 and applied the different patches (387172 and 389746) provided to correct the bug. and it has greatly cleaned my corrupted fragments09:00
openstackbug 1631144 in OpenStack Object Storage (swift) "Swift Erasure Coding : Error when decoding fragment" [Critical,Fix released] https://launchpad.net/bugs/163114409:00
openstackbug 1633647 in OpenStack Object Storage (swift) "bad fragment data not detected in audit" [Critical,Fix released] https://launchpad.net/bugs/163364709:00
kota_acoles: https://review.openstack.org/#/c/441921/4/swift/common/ring/builder.py this one?09:01
kota_it's patch set 409:01
admin6However, It seems that I still have some new corrupted erasure coded fragment (in a far lower proportion than during last autumn). I think they are not detected by the patched auditor.09:01
kota_hi admin609:01
acolesadmin6: :(09:02
kota_:/09:02
admin6May I send you some examples files so you can have a look ?09:02
openstackgerritliuyamin proposed openstack/python-swiftclient master: Fix some reST field lists in docstrings  https://review.openstack.org/45065609:04
kota_admin6: i could look at09:05
acolesadmin6: yes please. are these fragments that have been corrupted since you applied the patches? or corrupted frags that existed before but have still not been cleaned up?09:06
acoleskota_: re file path, OIC sorry I misunderstood you.09:08
admin6as far as I’ve seen, it’s always ‘reconstructed’ fragments that are corrupted. I’ve applied the patch on november but I still have new corrupted fragments that are generated after the application of the patch.09:11
acolesadmin6: ok. if you can file a bug on launchpad that would be very helpful09:13
admin6acoles: Ok09:14
acolesthanks09:14
acoleskota_: another question for you ... :) should we squash 446340 into 441921?09:18
acolespatch 446340 patch 44192109:18
patchbothttps://review.openstack.org/#/c/446340/ - swift - Add ring metadata space to the RingData serialization09:18
patchbothttps://review.openstack.org/#/c/441921/ - swift - Add Composite Ring Functionality09:18
acolespatchbot: it's so good to have you back09:18
kota_no strong opinion from me on that, if you feel it will be easy to review, I'll do that.09:20
kota_i just thought, the metadata space could be worth also current existing Ring09:20
kota_e.g. add the version number to the ring.gz we can confirm the version of the ring.gz and its consistency with the builder file09:21
kota_ah, but... swift-ring-builder tool already may have the capability?09:22
kota_I saw some checks in the recent playing with ring-builder...09:22
acolessure. I just wonder if it will merge on its own without an immediate use. the first use for it is the composite ring. and its "only" ~30 lines diff09:23
acolesIDK we can wait for other reviewers opinions09:23
*** gabor_antal_ is now known as gabor_antal09:23
kota_https://github.com/openstack/swift/blob/master/swift/cli/ringbuilder.py#L500-L50909:24
acoleskota_: actually I just realised that i made some small tweaks to the ring metadata in the composite ring patch so need to get those changes into the same patch one way or the other09:25
kota_hmm.. currently swift-ring-builder can show the diff with the builder file and the ring.gz, although we can not check the gz version.09:25
acoleskota_: https://review.openstack.org/#/c/441921/6/swift/common/ring/ring.py09:25
kota_looking09:25
kota_ah, ok i saw it once09:26
kota_hmm... I'm not sure too which way can work *farst* to us :/09:29
kota_fast09:29
* acoles needs coffee, bbiab09:30
kota_ah... the commit message at patch 446340 looks stale, it tells about md5 which we should not use.09:35
patchbothttps://review.openstack.org/#/c/446340/ - swift - Add ring metadata space to the RingData serialization09:35
kota_anyway, I need to circle back to it09:35
kota_acoles: I walked through all changes https://review.openstack.org/#/c/441921/ and then I'm realizing it's ok to squash up into the pearent patch 44634009:44
patchbotpatch 446340 - swift - Add ring metadata space to the RingData serialization09:44
kota_ah, patch bot cannot refer the URL, just take care of  "patch" phrase.09:44
acoleskota_: ok let's squash them.09:46
kota_acoles: k, could you do it?09:46
kota_or i should do?09:47
acoleskota_: yes no problem I will do it09:47
kota_acoles: thx!09:47
kota_acoles: because of your kindness, i am able to go dinner :D09:47
acoleshehe. have a good evening09:48
kota_;-)09:48
*** cbartz has quit IRC09:50
*** csmart has quit IRC10:04
portantezaitcev, we have been working on logging solutions with containers now for a while, happy share if you want to tinker10:15
*** mvk has quit IRC10:16
*** csmart has joined #openstack-swift10:17
*** sams-gleb has joined #openstack-swift10:18
*** zhurong has quit IRC10:20
*** sams-gleb has quit IRC10:22
*** zhurong has joined #openstack-swift10:28
*** mvk has joined #openstack-swift10:31
openstackgerritAlistair Coles proposed openstack/swift master: Add Composite Ring Functionality  https://review.openstack.org/44192110:35
*** bkopilov_ has quit IRC10:36
*** bkopilov has quit IRC10:36
* mahatic is off work until the weekend. Back to work on 3rd April10:41
acolesmahatic: have a good break10:42
mahaticacoles: thank you10:42
openstackgerritXieYingYun proposed openstack/swift master: Fix some reST field lists in docstrings  https://review.openstack.org/44989011:11
*** furlongm has quit IRC11:19
*** zhurong has quit IRC11:25
*** cbartz has joined #openstack-swift11:26
*** ma9_ has joined #openstack-swift11:27
*** cbartz has quit IRC11:28
*** ma9_ has quit IRC11:29
*** cbartz has joined #openstack-swift11:30
*** furlongm has joined #openstack-swift11:31
*** ma9_ has joined #openstack-swift11:32
*** openstackgerrit has quit IRC11:33
*** ma9_ has quit IRC11:37
*** openstackgerrit has joined #openstack-swift11:39
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873611:39
*** NM has joined #openstack-swift11:40
*** ma9_ has joined #openstack-swift11:41
*** jordanP has joined #openstack-swift12:00
*** sams-gleb has joined #openstack-swift12:01
*** ma9_ has quit IRC12:15
*** chlong has joined #openstack-swift12:16
*** sams-gle_ has joined #openstack-swift12:39
*** ma9_ has joined #openstack-swift12:41
*** sams-gleb has quit IRC12:42
*** klamath has joined #openstack-swift12:45
openstackgerritKaren Chan proposed openstack/swift master: Store version id if restoring object from archive  https://review.openstack.org/43752312:53
openstackgerritKaren Chan proposed openstack/swift master: Add X-Backend-Versioning-Mode-Override  https://review.openstack.org/43719612:56
*** amoralej is now known as amoralej|lunch13:08
*** kirill_ has quit IRC13:18
*** kei_yama has quit IRC13:19
*** links has quit IRC13:22
*** ma9_ has quit IRC13:46
*** jordanP has quit IRC13:49
*** ma9_ has joined #openstack-swift13:53
*** _JZ_ has joined #openstack-swift13:54
*** hseipp has joined #openstack-swift13:58
*** amoralej|lunch is now known as amoralej14:03
*** ma9_ has quit IRC14:03
*** ma9_ has joined #openstack-swift14:10
*** jaosorior has quit IRC14:12
*** vint_bra has joined #openstack-swift14:44
cbartztdasilva: Could you please take a look at patch 423377 ?14:56
patchbothttps://review.openstack.org/#/c/423377/ - python-swiftclient - ISO 8601 timestamps for tempurl14:56
tdasilvacbartz: yes, I started to look at it, just didn't have a chance to finish testing14:57
tdasilvabut i'm happy with it overall, will try to finish up today14:58
cbartztdasilva: Ok, thx.14:58
*** ma9_1 has joined #openstack-swift15:02
*** ma9_ has quit IRC15:04
*** gabor_antal has quit IRC15:05
*** cbartz has left #openstack-swift15:14
*** oshritf has quit IRC15:15
*** klrmn has joined #openstack-swift15:15
openstackgerritAlistair Coles proposed openstack/swift master: Test and fixups for ContainerSharder config  https://review.openstack.org/45084515:21
*** rcernin has quit IRC15:31
*** rcernin_ has quit IRC15:31
*** tonanhngo has joined #openstack-swift15:51
notmynamegood morning16:13
openstackgerritGábor Antal proposed openstack/swift master: Use more specific asserts in test/unit/common  https://review.openstack.org/34278116:15
notmynameis gabor antal here in IRC?16:16
*** ma9_1 has quit IRC16:18
*** psachin has quit IRC16:24
*** pcaruana has quit IRC16:26
*** JimCheung has joined #openstack-swift16:26
*** sams-gle_ has quit IRC16:27
*** bkopilov has joined #openstack-swift16:31
*** bkopilov_ has joined #openstack-swift16:31
*** chlong has quit IRC16:34
*** SkyRocknRoll has joined #openstack-swift16:36
*** gabor_antal has joined #openstack-swift16:43
*** sams-gleb has joined #openstack-swift16:44
*** chlong has joined #openstack-swift16:49
*** hseipp has quit IRC16:49
*** chsc has joined #openstack-swift16:50
*** chsc has quit IRC16:50
*** chsc has joined #openstack-swift16:50
*** gabor_antal_ has joined #openstack-swift16:55
*** gabor_antal has quit IRC16:55
*** Renich has quit IRC17:03
*** geaaru has quit IRC17:04
*** mvk has quit IRC17:13
jrichlinotmyname: I see gabor_antal_ is here now17:14
gabor_antal_hey there17:14
*** gabor_antal_ is now known as gabor_antal17:14
*** SkyRocknRoll_ has joined #openstack-swift17:15
jrichligabor_antal: notmyname was looking for you earlier.  he might be busy now, donno.  but i expect he will reply soon17:16
notmynamegabor_antal: hello!17:16
notmynamegabor_antal: I was looking at patch 34278117:16
patchbothttps://review.openstack.org/#/c/342781/ - swift - Use more specific asserts in test/unit/common17:16
gabor_antaloh, okay, i'll be here for like half an hour17:16
notmynamegabor_antal: before I say anything else, I want to make clear that I agree with you said in the commit message. and so far in my looking at the changes, it seems ok17:18
notmyname(what a terrible intro)17:18
*** SkyRocknRoll has quit IRC17:18
*** amoralej is now known as amoralej|off17:18
gabor_antalit is :)17:18
notmynamebut it's a lot of code churn for something that can't be enforced (eg linting checks)17:19
notmynameand being in tests, it has the chance of some odd side effects (like the comment about truthy not being the same as equal17:20
notmynameagain, the patch isn't wrong or bad itself17:20
notmynamebut in the larger context of review and maintenance, why?17:20
gabor_antalYeah I know it, but the first version when I created the patch, I did not think over that equal change.17:20
notmynamepart of me want's the patch because it's "more" correct. but the other part of me doesn't because it's code churn fixing stuff that isn't broken17:22
notmynamegabor_antal: so I wanted to ask you about your thoughts on it, share my thoughts, and see where we are17:22
notmynameand again, I don't think the patch is wrong or bad itself, and I agree with your commit message :-)17:23
gabor_antalIn fact, most of the rules are already merged to the main hacking project, here: https://review.openstack.org/#/c/354185/17:23
notmynameoh, interesting17:24
gabor_antalAnd beforce the question, hacking is not a requirement which is automatically proposed to the projects.17:24
gabor_antalWe faced in nova too, so i checked  it and it is blacklisted to the proposal bot17:24
gabor_antalI can feel your point, but honestly I think this change is not useless.17:26
gabor_antalAnd beyond the fact that the code is more readable, also on error, a better error message is thrown.17:27
gabor_antalAnd I think this is the main reason for the update. I have faced several times the "False is not True." error message, but this can be changed as it can be seen in the patches17:28
notmynamegabor_antal: sorry. a few conversations going on at once :-)17:32
gabor_antalnotmyname np, but i'll be leave shortly, so maybe we can continue tomorrow17:38
notmynamegabor_antal: I think i would like your patch a lot more if it also added/included the hacking check. however, I don't know what else that will show17:38
gabor_antalThat's not a bad idea, I'll check it tomorrow17:41
*** tonanhngo has quit IRC17:43
notmynamegabor_antal: and thanks for your patch. I definitely appreciate it :-)17:44
*** zaitcev has joined #openstack-swift17:44
*** ChanServ sets mode: +v zaitcev17:44
*** mvk has joined #openstack-swift17:52
gabor_antalnotmyname: I updated the HACKING on my local computer, and enabled the currently available extensions, and there lots of more things to do with them. But I think the above hacking patch is not in the release yet18:05
notmynamegabor_antal: ah, ok18:05
gabor_antalBut I will check it tomorrow more precisely18:05
*** tesseract has quit IRC18:06
gabor_antalH203 is part of the changes, it says: "Use assertIs(Not)None to check for None (off by default) Unit test assertions tend to give better messages for more specific assertions."18:06
*** JimCheung has quit IRC18:19
*** JimCheung has joined #openstack-swift18:20
*** JimCheung has quit IRC18:24
*** gyee has joined #openstack-swift18:26
openstackgerritTim Burke proposed openstack/swift master: fixup! Add container sharding to Swift containers  https://review.openstack.org/45049118:32
timburkeanother stable failure: http://logs.openstack.org/periodic-stable/periodic-swift-python27-mitaka/c04fdce/console.html#_2017-03-28_06_08_32_09869118:34
timburkethose KeyErrors seem suspicious -- something with patch/unpatch_policies? i feel like i saw something about that lately...18:37
*** Renich has joined #openstack-swift18:41
*** ujjain has quit IRC19:12
*** ujjain has joined #openstack-swift19:18
*** ujjain has joined #openstack-swift19:18
*** SkyRocknRoll_ has quit IRC19:18
*** ujjain has quit IRC19:22
*** ujjain has joined #openstack-swift19:27
*** ujjain has joined #openstack-swift19:27
*** ujjain has quit IRC19:41
*** SkyRocknRoll has joined #openstack-swift19:53
acolestimburke: agree, the one I looked at last week when you raised this in the meeting also had a KeyError looking up a policy, in ssync test, and I also wondered if some policy patching was not being undone19:55
*** SkyRocknRoll has quit IRC19:59
openstackgerritAlistair Coles proposed openstack/swift master: Tests and fixups for sharding stats reporting  https://review.openstack.org/45095720:00
*** SkyRocknRoll has joined #openstack-swift20:01
*** klrmn has quit IRC20:04
*** klrmn has joined #openstack-swift20:04
*** silor has quit IRC20:28
*** vinsh has joined #openstack-swift21:29
*** sams-gleb has quit IRC21:35
*** sams-gleb has joined #openstack-swift21:36
*** sams-gleb has quit IRC21:36
*** NM has quit IRC21:36
mattoliverauMorning21:56
*** JimCheung has joined #openstack-swift21:59
*** sams-gleb has joined #openstack-swift22:37
notmynametonyb_: oh! new eventlet has been accepted by openstack requirements22:38
*** _JZ_ has quit IRC22:38
*** sams-gleb has quit IRC22:41
mattoliverauacoles: \o/ sharding patch!22:54
mattoliverautimburke: Nice, get_item_since test. I had a quick go at a get_item_since, so might add an additional check to yours (and see if you like it), that is if you dont mind.22:56
timburkemattoliverau: absolutely! and as i left in a comment on my followup, it needs ts.internal22:57
notmynameare you *sure* that it's ts.internal?22:57
mattoliverautimburke: cool, I'll add that too :)22:57
notmynameas opposed to ts.internal?22:57
timburkenotmyname: or maybe ts.infernal?22:58
mattoliveraumeh, tomato, tomato22:58
notmynameI think it's more "meh, pickle, pickle"22:59
*** vint_bra has quit IRC23:00
*** klamath has quit IRC23:25
openstackgerritTim Burke proposed openstack/swift master: Add functests for disallowed COPYs into a versioned container  https://review.openstack.org/45111123:28
*** catintheroof has joined #openstack-swift23:37
mattoliveraunotmyname: btw, tonyb_ is off this week23:42
*** gyee has quit IRC23:43
*** NM has joined #openstack-swift23:47
timburkenotmyname: i *think* https://review.openstack.org/#/c/451118/ will get us our linky? or, set up jobs such that we'll get our linky the next time there's a commit that touches the releasenotes/ subtree?23:56

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