Thursday, 2016-07-07

kota_if we have to call socket.close, we need to do that in MemcachePool.creat but I'm not sure what's happen if we got Timeout during socket.connect()00:01
kota_do we need to call socket.close() to ensure closing? or just leave it (and expect to decrease reference counter and gc'ed ) as well as current swift?00:03
notmynamekota_: in my experience with getting swift running under pypy, it's almost always good to have swift explicitly close sockets and not rely on GC to take care of it00:04
*** diogogmt has quit IRC00:04
kota_notmyname: good call00:04
clayglazy garbage collectors00:05
kota_notmyname, clayg: drafting as https://gist.github.com/bloodeagle40234/0fb2b0a65dba382f6ef7a642e41fe40000:06
notmynameif you want some juicy tech details on the bug in eventlet related to closing sockets that is currently blocking swift-on-pypy, check otu https://github.com/eventlet/eventlet/issues/318#issuecomment-224756745 (resolved by https://github.com/eventlet/eventlet/pull/326)00:07
notmynameunfortunately, the eventlet maintainers are silent on the pull request, so the issue is still open00:07
kota_it still need futher work though (remove comment out, and probably we can remove the meaningless sock arg from method call)00:07
kota_notmyname: thanks!00:08
kota_will read it.00:08
claygkota_: seems reasonable00:09
kota_clayg: thanks :-) will push a clean version soon (at least, in today in my time)00:10
*** arch-nemesis has quit IRC00:11
openstackgerritTim Burke proposed openstack/swift: Fix X-*-Container-Update-Override-* header/footer precedence  https://review.openstack.org/33858800:22
openstackgerritTim Burke proposed openstack/swift: Send correct SLO ETag for container updates  https://review.openstack.org/33796000:22
claygnotmyname: the whole thing is suspect, the call to dup in makefile makes no sense - the py3 version doesn't do - gevent doesn't do it - it's burried way back in the history of eventlet code when rdw was working on it - there was an awkward "refcount" implementation *in* eventlet that's all been washed over00:31
*** klamath has quit IRC00:41
*** david-lyle has quit IRC00:42
*** m_kazuhiro has joined #openstack-swift00:52
*** Suyash has joined #openstack-swift01:04
*** tqtran has quit IRC01:07
*** klrmn has quit IRC01:12
*** _JZ_ has joined #openstack-swift01:13
openstackgerrityuyafei proposed openstack/swift: Add __ne__ built-in function  https://review.openstack.org/33742802:01
*** diogogmt has joined #openstack-swift02:07
*** cdelatte has quit IRC02:14
*** klrmn has joined #openstack-swift02:18
*** chsc has joined #openstack-swift02:53
*** chsc has quit IRC02:53
*** chsc has joined #openstack-swift02:53
*** sanchitmalhotra has joined #openstack-swift02:54
*** chsc has quit IRC02:59
*** diazjf has joined #openstack-swift03:16
*** diazjf has quit IRC03:20
*** ManojK has joined #openstack-swift03:22
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873603:31
*** _JZ_ has quit IRC03:39
*** jamielennox is now known as jamielennox|away03:43
*** sgundur1 has left #openstack-swift03:49
*** ppai has joined #openstack-swift03:55
*** jamielennox|away is now known as jamielennox03:56
*** ManojK has quit IRC04:01
*** links has joined #openstack-swift04:03
*** tqtran has joined #openstack-swift04:06
*** sheel has joined #openstack-swift04:09
*** tqtran has quit IRC04:11
*** Suyash has quit IRC04:16
openstackgerritMahati Chamarthy proposed openstack/swift: remove empty db hash and suffix directories  https://review.openstack.org/33160104:20
*** nadeem has joined #openstack-swift04:21
*** jamielennox is now known as jamielennox|away04:35
*** jamielennox|away is now known as jamielennox04:42
*** vint_bra has joined #openstack-swift04:44
*** vint_bra has quit IRC04:45
*** vint_bra1 has joined #openstack-swift04:45
*** vint_bra has joined #openstack-swift04:45
*** vint_bra1 has quit IRC04:45
*** vint_bra1 has joined #openstack-swift04:47
*** vint_bra has quit IRC04:47
*** vint_bra1 has quit IRC04:51
*** Jeffrey4l_ has joined #openstack-swift04:51
*** psachin has joined #openstack-swift05:01
*** ChubYann has quit IRC05:37
*** siva_krish has joined #openstack-swift05:41
*** johanfi has quit IRC05:42
*** siva_krish has quit IRC05:44
*** acoles_ has quit IRC05:49
*** zaitcev has quit IRC05:50
*** acoles has joined #openstack-swift05:51
*** ChanServ sets mode: +v acoles05:51
openstackgerritAndreas Jaeger proposed openstack/swift: Add install-guide for swift  https://review.openstack.org/33007006:00
*** siva_krish has joined #openstack-swift06:12
*** rcernin has joined #openstack-swift06:18
*** klrmn has quit IRC06:20
*** tqtran has joined #openstack-swift06:30
*** SkyRocknRoll has joined #openstack-swift06:34
*** tqtran has quit IRC06:34
*** hseipp has joined #openstack-swift06:52
*** kei_yama has quit IRC07:00
*** tesseract- has joined #openstack-swift07:03
*** kei_yama has joined #openstack-swift07:04
*** nadeem has quit IRC07:08
*** Lickitysplitted has quit IRC07:12
*** Lickitysplitted has joined #openstack-swift07:12
*** ppai has quit IRC07:32
*** SkyRocknRoll has quit IRC07:44
kota_Oh, what...??? I'm stll in a fog...07:49
kota_clayge: Related to (but different from) the conversation at this morning, I'm now checking on sort of closing connection in proxy-server.07:50
kota_ah, sorry, clayg07:50
kota_clayg: and I'm wondering why https://github.com/openstack/swift/blob/master/swift/proxy/controllers/base.py#L1100-L1109 works correctly.07:51
kota_clayg: On my thought, if the conn.getresponse() was timeout, conn reference will be lost and it will leak the socket inside.07:52
*** ppai has joined #openstack-swift07:52
kota_clayg: but it doesn't actually, when I was trying to inject an error at the Line 1100, nothing leaked.07:53
kota_clayg: and then, I noticed it is because we wrap the func with GreenPool (in fact, GreenAsyncPile though).07:54
kota_clayg: https://gist.github.com/bloodeagle40234/e9a1f009336221c085d3d0086e62134007:54
*** oshritf has joined #openstack-swift07:54
*** oshritf_ has joined #openstack-swift07:54
kota_clayg: that is a snippet, I was trying to do. The code shows, if we loose the reference of connection, it causes socket leak but if we do so in GreenPile, the connection will be closed.07:56
*** mvk has joined #openstack-swift07:57
kota_clayg: I thought GreenPool serves just a green thread for a hub of the networking tranpoline but... it semms like correcting the garbage? I'm not entirly sure and I didn't find how it was closed actually.07:59
kota_ah, I wrote as to clayg, but if someone knows something on that, that's great to correct me anyway.08:00
kota_what's happen in actually, and I'm not sure if we can trust the GreenPile to close the connection always.08:01
*** cbartz has joined #openstack-swift08:04
*** rledisez has joined #openstack-swift08:06
*** ppai has quit IRC08:06
*** kei_yama_ has joined #openstack-swift08:08
*** kei_yama has quit IRC08:09
openstackgerritDavanum Srinivas (dims) proposed openstack/swift: [WIP] Testing latest u-c  https://review.openstack.org/31844108:10
*** takashi has joined #openstack-swift08:11
mahatic_pdardeau: notmyname thanks for calling out on veg option, but I'm not going to make it to the mid-cycle this time (lot's of interesting topics on etherpad i'm going to miss out on :( )08:15
* mahatic_ got around the logs only now after a holiday at intel india08:16
*** openstackgerrit has quit IRC08:18
*** openstackgerrit has joined #openstack-swift08:18
*** pcaruana has joined #openstack-swift08:30
*** siva_krish has quit IRC08:34
*** siva_krish has joined #openstack-swift08:35
*** mmcardle has joined #openstack-swift08:44
*** thurloat has quit IRC08:48
*** thurloat has joined #openstack-swift08:48
*** asettle has joined #openstack-swift08:50
openstackgerrityuyafei proposed openstack/swift: Correct reraising of exception  https://review.openstack.org/33877409:00
*** oshritf has quit IRC09:01
*** oshritf_ has quit IRC09:01
*** ouchkernel has quit IRC09:04
*** mmcardle has quit IRC09:09
*** ouchkernel has joined #openstack-swift09:10
*** takashi has quit IRC09:14
*** mmcardle has joined #openstack-swift09:15
*** mmcardle has quit IRC09:25
*** daemontool has joined #openstack-swift10:07
openstackgerritKota Tsuyuzaki proposed openstack/swift: Ensure close socket for memcached if got timeout  https://review.openstack.org/33881910:08
*** mmcardle has joined #openstack-swift10:08
*** oshritf_ has joined #openstack-swift10:14
*** oshritf has joined #openstack-swift10:14
*** thurloat has quit IRC10:25
*** thurloat has joined #openstack-swift10:26
psachinping clayg, https://review.openstack.org/#/c/334238/.  Error and assert the message has been taken care off. https://github.com/psachin/swift/commit/da7ef05bb2aa0d6fc1a5a172b8d0af54aedccabb10:31
patchbotpsachin: patch 334238 - swift - Fix swift-get-nodes arg parsing for missing ring10:31
*** tqtran has joined #openstack-swift10:32
psachinclayg, Not sure how to implement tests for invalid/defined policies.10:32
*** tqtran has quit IRC10:37
*** siva_krish has quit IRC10:40
*** sanchitmalhotra has quit IRC10:42
*** mmcardle has quit IRC10:52
kota_wow....it's hard work to rebase off  global ec staff to the current master. not a big from encryption but around chunk_hasher seems too affected...10:58
kota_test seems to work well but not sure right now, I succeeded the rebasing...10:59
kota_and probably it needs more clean up10:59
openstackgerritKota Tsuyuzaki proposed openstack/swift: PUT/GET path for global ec cluster  https://review.openstack.org/21916511:01
openstackgerritKota Tsuyuzaki proposed openstack/swift: Support EC duplication factor at reconstructor  https://review.openstack.org/23786711:06
kota_probably it seems getting better to squash the later one into the previous one because about 100 lines changes in it.11:07
*** mmcardle has joined #openstack-swift11:08
*** _JZ_ has joined #openstack-swift11:09
*** m3m0 has quit IRC11:15
openstackgerritKota Tsuyuzaki proposed openstack/swift: Add Pros/Cons table for global clusetr consideration  https://review.openstack.org/30438211:21
*** dfflanders has quit IRC11:23
*** mmcardle has quit IRC11:26
*** asettle has quit IRC11:26
openstackgerritKota Tsuyuzaki proposed openstack/swift: CompositeRing Support  https://review.openstack.org/27192011:36
kota_All of them are rebasing.11:36
*** SkyRocknRoll has joined #openstack-swift11:38
*** cdelatte has joined #openstack-swift11:48
*** SkyRocknRoll has quit IRC12:03
*** arcimboldo has joined #openstack-swift12:08
*** NM has joined #openstack-swift12:18
openstackgerritKota Tsuyuzaki proposed openstack/swift: PUT/GET path for global ec cluster  https://review.openstack.org/21916512:28
openstackgerritKota Tsuyuzaki proposed openstack/swift: Support EC duplication factor at reconstructor  https://review.openstack.org/23786712:29
openstackgerritKazuhiro MIYAHARA proposed openstack/swift: Remove an unused variable from tests.py  https://review.openstack.org/33893912:29
*** tqtran has joined #openstack-swift12:33
*** tqtran has quit IRC12:38
*** m_kazuhiro has quit IRC12:42
*** m_kazuhiro has joined #openstack-swift12:46
*** asettle has joined #openstack-swift12:46
*** arcimboldo has quit IRC12:47
openstackgerritOndřej Nový proposed openstack/swift: Add ringbuilder tests for --yes option  https://review.openstack.org/32637312:50
openstackgerritAlistair Coles proposed openstack/swift: Fix unicode errors in object controller logging  https://review.openstack.org/33895012:52
*** oshritf_ has quit IRC12:53
*** oshritf has quit IRC12:53
onovyhi, https://review.openstack.org/#/c/326399/ https://review.openstack.org/#/c/253037/ this was waiting for +A after crypto freeze, which is over, right?12:53
patchbotonovy: patch 326399 - swift - Add simple multiple server type test12:53
patchbotonovy: patch 253037 - swift - Call swift-recon with more than one server type12:53
acolescschwede: patch 338950 has the tests that I mentioned I was working on re. unicode errors. They don't yet test translations, but I think they could be extended to test unicode translations of the error messages.12:55
patchbotacoles: https://review.openstack.org/#/c/338950/ - swift - Fix unicode errors in object controller logging12:55
cschwedeacoles: thx, will have a look!12:55
*** m_kazuhiro has quit IRC12:56
onovyacoles: thanks!12:56
acolesonovy: done12:56
acolescschwede: I think some of those new tests will fail if the error message is translated to have non-ascii (without your fix for gettext another fix)12:57
cschwedeacoles: sounds reasonable12:58
cschwedei thinkg clayg might be interested in patch 338950 as well12:58
patchbotcschwede: https://review.openstack.org/#/c/338950/ - swift - Fix unicode errors in object controller logging12:58
*** arcimboldo has joined #openstack-swift12:59
*** klamath has joined #openstack-swift13:01
*** klamath has quit IRC13:01
*** links has quit IRC13:02
*** klamath has joined #openstack-swift13:02
jrichlimahatic_: you will be missed at the hackathon!13:04
*** ManojK has joined #openstack-swift13:06
*** diogogmt has quit IRC13:21
*** diogogmt has joined #openstack-swift13:26
*** oshritf_ has joined #openstack-swift13:27
*** oshritf has joined #openstack-swift13:27
*** diogogmt has quit IRC13:40
*** vinsh has joined #openstack-swift13:43
*** arcimboldo has quit IRC13:46
*** mmcardle has joined #openstack-swift13:51
*** mmcardle has quit IRC13:59
*** mmcardle has joined #openstack-swift14:02
*** arcimboldo has joined #openstack-swift14:02
*** mmcardle1 has joined #openstack-swift14:04
*** sheel has quit IRC14:05
*** mmcardle has quit IRC14:06
*** ManojK has quit IRC14:11
*** mmcardle has joined #openstack-swift14:12
*** mmcardle1 has quit IRC14:15
*** mmcardle1 has joined #openstack-swift14:24
*** mmcardle has quit IRC14:26
*** sgundur1 has joined #openstack-swift14:29
*** ManojK has joined #openstack-swift14:30
*** vinsh has quit IRC14:32
*** diogogmt has joined #openstack-swift14:32
*** Suyash has joined #openstack-swift14:33
openstackgerritMerged openstack/swift: Add simple multiple server type test  https://review.openstack.org/32639914:34
openstackgerritKota Tsuyuzaki proposed openstack/swift: CompositeRing Support  https://review.openstack.org/27192014:34
acolesjrichli: timburke I was about to abandon patch 327144 but thought some more and wonder if there is still some value in that modification - any thoughts?14:43
patchbotacoles: https://review.openstack.org/#/c/327144/ - swift (feature/crypto) - crypto - Don't encrypt update override etags for e...14:43
timburkeacoles: yeah, now that we always use a random iv, i think there's no threat14:45
acolestimburke: ok, I'll rebase it14:49
*** ametts has joined #openstack-swift14:51
jrichliacoles: I'll take a look.  can't right now, but will soon14:55
acolesjrichli: thanks. IIRC it was addressing an anomaly that you spotted.14:56
acoleswe can discuss it more next week14:56
*** siva_krish has joined #openstack-swift14:56
jrichliacoles: ok, thanks. I took a quick look.  i need to verify a couple things in our current impl now.14:57
openstackgerritMohit Motiani proposed openstack/swift: Fix typo in the account-server.conf manpage  https://review.openstack.org/33904514:57
*** ManojK has quit IRC14:58
*** ManojK has joined #openstack-swift15:01
*** siva_krish has quit IRC15:03
*** diazjf has joined #openstack-swift15:03
*** diazjf1 has joined #openstack-swift15:05
*** diazjf has quit IRC15:08
*** vinsh has joined #openstack-swift15:09
*** mmcardle1 has quit IRC15:11
acolesmmotiani: ^^ the same typo is in the container and object server conf manpages15:11
mmotianiacoles: Yeah, thanks.15:18
mmotianiWill fix that too15:18
mmotianithanks :)15:18
openstackgerritMohit Motiani proposed openstack/swift: Fix typo in object-server.conf and container-server.conf manpage  https://review.openstack.org/33906315:23
*** mmcardle has joined #openstack-swift15:23
*** nadeem has joined #openstack-swift15:24
*** arcimboldo has quit IRC15:24
*** nadeem has quit IRC15:25
*** nadeem has joined #openstack-swift15:25
*** ManojK has quit IRC15:26
*** chsc has joined #openstack-swift15:26
openstackgerritAlistair Coles proposed openstack/swift: Don't encrypt update override etags for empty object  https://review.openstack.org/33907115:28
*** ManojK has joined #openstack-swift15:28
acolesmmotiani: thanks15:29
*** psachin has quit IRC15:37
*** oshritf has quit IRC15:40
*** oshritf_ has quit IRC15:40
*** pcaruana has quit IRC15:49
*** jmccarthy has quit IRC15:50
*** jmccarthy has joined #openstack-swift15:51
*** ManojK has quit IRC16:04
*** mmcardle has quit IRC16:09
*** rcernin has quit IRC16:10
notmynamegood morning16:12
*** hseipp has quit IRC16:14
*** arch-nemesis has joined #openstack-swift16:14
*** siva_krish has joined #openstack-swift16:18
*** tesseract- has quit IRC16:23
*** chsc has quit IRC16:23
*** ManojK has joined #openstack-swift16:24
*** chsc has joined #openstack-swift16:32
*** chsc has joined #openstack-swift16:32
*** chsc has quit IRC16:33
*** chsc has joined #openstack-swift16:33
*** chsc has joined #openstack-swift16:33
*** dmorita has joined #openstack-swift16:39
*** asettle has quit IRC16:45
*** rledisez has quit IRC16:48
*** cdelatte has quit IRC16:58
*** cbartz has left #openstack-swift17:11
openstackgerritMerged openstack/python-swiftclient: Add python version constraint python>=2.7  https://review.openstack.org/33433317:13
openstackgerritMaria Malyarova proposed openstack/swift: Another amendment with missing parenthesis  https://review.openstack.org/33914517:15
*** klrmn has joined #openstack-swift17:18
*** diazjf1 has quit IRC17:20
openstackgerritMerged openstack/swift: Fix intermittent bulk delete unit test failures  https://review.openstack.org/33567417:38
openstackgerritAlistair Coles proposed openstack/swift: Add encryption package requirements to SAIO instructions  https://review.openstack.org/33915617:40
*** acoles is now known as acoles_17:41
*** daemontool has quit IRC17:52
*** catintheroof has joined #openstack-swift17:53
*** tqtran has joined #openstack-swift18:00
*** dmorita has quit IRC18:06
*** ManojK has quit IRC18:07
*** dmorita_ has joined #openstack-swift18:08
*** sheel has joined #openstack-swift18:12
*** gyee has joined #openstack-swift18:17
*** vinsh has quit IRC18:22
*** nadeem has quit IRC18:24
*** madorn has joined #openstack-swift18:25
madornis anyone aware of issues with cross-project ACL's when using keystoneauth?18:25
*** bgmccollum has joined #openstack-swift18:25
*** nadeem has joined #openstack-swift18:25
*** nadeem has quit IRC18:26
madornit appears that in both mitaka and liberty openstack environments with swift, one cannot give a different project read/write access to a container18:26
openstackgerritMerged openstack/swift: Fix typo in the account-server.conf manpage  https://review.openstack.org/33904518:28
*** nadeem has joined #openstack-swift18:28
openstackgerritMerged openstack/swift: Fix typo in object-server.conf and container-server.conf manpage  https://review.openstack.org/33906318:30
openstackgerritMerged openstack/swift: make print python3 compatible  https://review.openstack.org/33380118:30
*** siva_krish has quit IRC18:32
madornmadorn: figured it out... --os-storage-url18:35
*** rcernin has joined #openstack-swift18:39
*** ChubYann has joined #openstack-swift18:41
*** siva_krish has joined #openstack-swift18:41
*** tqtran is now known as tqtran-afk18:46
*** diazjf has joined #openstack-swift18:50
*** ManojK has joined #openstack-swift18:50
*** daemontool has joined #openstack-swift18:54
claygis patch 339071 just belts and braces or some sort of rare failure in metadata handling?19:04
patchbotclayg: https://review.openstack.org/#/c/339071/ - swift - Don't encrypt update override etags for empty object19:04
clayg... there's no associated bug - so i'm inclined to think it's just for "more better"19:04
openstackgerritTim Burke proposed openstack/swift: Run flake8 against scripts in bin  https://review.openstack.org/33919119:05
openstackgerritTim Burke proposed openstack/swift: Turn on H233 and start using print function  https://review.openstack.org/33919219:05
claygtimburke: cschwede: acoles_: nice working merging doc fixes!19:05
openstackgerritMerged openstack/swift: Remove an unused variable from tests.py  https://review.openstack.org/33893919:06
jrichliclayg: I remember that logically there was a hole in one of the crypto patches awhile back.  This plugged it.  I will have to revisit the details and compare with what is on master now.19:06
jrichlijust haven't been able to do that yet today :-(19:06
timburkethere's a chance it had to do with leaking etags when multiple objects were PUT to the same path, but i need to think about whether it's still an issue now that we're always using random IVs19:08
jrichlitimburke: yes, but technically, we do have the hmac where it will also result in the same value for the same path.  but maybe that doesn't get involved here at all.  again, i have to see details19:09
*** diazjf has quit IRC19:09
jrichlioh, right ... this is just for container listing stuff, right?19:10
*** diazjf has joined #openstack-swift19:10
timburkejrichli: yeah, the hmac seems unavoidable... and yeah, that patch just has to do with container listings19:10
claygugh, but I prefer print as a statement :'(19:10
jrichlibut some of the tests added a case for other mw's adding footers. i wanted to be sure we are testing all that19:11
timburkeclayg: we keep getting piecemeal patches to convert it, and if we're ever going to move to py3 it'll be necessary...may as well get used to it now :-/19:11
timburkejrichli: speaking of other middlewares and container listing overrides, you might be interested in patch 33796019:12
patchbottimburke: https://review.openstack.org/#/c/337960/ - swift - Send correct SLO ETag for container updates19:12
jrichlitimburke: its already on my list!  now i just need time to go through my list :-/19:13
timburkethanks :-) don't forget its parent, patch 33858819:13
patchbottimburke: https://review.openstack.org/#/c/338588/ - swift - Fix X-*-Container-Update-Override-* header/footer ...19:13
jrichlikk19:13
openstackgerritMerged openstack/swift: Another amendment with missing parenthesis  https://review.openstack.org/33914519:21
*** ametts has quit IRC19:23
*** cdelatte has joined #openstack-swift19:25
openstackgerritMerged openstack/swift: added note to testFileSizeLimit functional test  https://review.openstack.org/33131819:26
openstackgerritMerged openstack/swift: Add encryption package requirements to SAIO instructions  https://review.openstack.org/33915619:27
*** Jeffrey4l_ has quit IRC19:31
*** Jeffrey4l_ has joined #openstack-swift19:31
*** siva_krish has left #openstack-swift19:33
openstackgerritThiago da Silva proposed openstack/swift: Tighten memcached tests  https://review.openstack.org/33355519:35
openstackgerritTim Burke proposed openstack/swift: Run flake8 against scripts in bin  https://review.openstack.org/33919119:38
openstackgerritTim Burke proposed openstack/swift: Turn on H233 and start using print function  https://review.openstack.org/33919219:38
timburketdasilva: mind looking at the parent change, too? patch 33355419:39
patchbottimburke: https://review.openstack.org/#/c/333554/ - swift - MockMemcached cleanup19:39
tdasilvatimburke: approving that now19:39
tdasilvalooks good19:39
timburkeah, perfect :-) thanks19:39
tdasilvatimburke: great job btw19:40
claygshouldn't the "run flake8 on bin scripts; and add more checks to flake8 and fixes in bin scripts" patches be squashed or reversed?19:43
openstackgerritMerged openstack/swift: Add install-guide for swift  https://review.openstack.org/33007019:48
*** asettle has joined #openstack-swift19:51
brianclineoh wow, patch 335373 got merged19:54
patchbotbriancline: https://review.openstack.org/#/c/335373/ - swift - Prevent down nodes failing PUTs with non-ascii obj... (MERGED)19:54
claygmahatic_: timburke fixed the tox/flake/pep8/merge issue in patch 339192 - but gerrit didn't remove your -1 because it thinks it was "just" a rebase19:55
patchbotclayg: https://review.openstack.org/#/c/339192/ - swift - Turn on H233 and start using print function19:55
brianclineso was i just not moving quickly enough on that one?19:56
*** asettle has quit IRC19:56
claygtimburke: oh geez - I still don't know how to read new gerrits related changes list - the order you have the patches is correct obvs.  - sorry19:56
claygbriancline: what's wrong with it merging?19:57
*** asettle has joined #openstack-swift19:59
*** asettle has quit IRC19:59
brianclineclayg: nothing, i just thought there was more to be done. i guess i was confused whether i should continue on with it after your patchset :/  so i started working on some updates to its tests20:02
claygbriancline: oh sorry, yeah that bug was a hozer - and acoles_ picked up the ball anyway20:08
claygthanks for getting everyone pointed in the right direction - if you ever have time to work on something that isn't a critical bug maybe you'll get to enjoy the month long review process!20:09
timburkemmotiani: i think clayg meant to tag you about patch 339192 above20:20
patchbottimburke: https://review.openstack.org/#/c/339192/ - swift - Turn on H233 and start using print function20:20
mmotianitimburke: got it, thanks!20:28
mmotianithanks clayg20:28
tdasilvatimburke: re patch 339192, why do some of the files not require "from __future__ import print_function" ?20:29
patchbottdasilva: https://review.openstack.org/#/c/339192/ - swift - Turn on H233 and start using print function20:29
*** castulo has joined #openstack-swift20:30
castulohi guys, question, I have seen it takes a while after having set account quota in swift to be enforced, more than 10 minutes in my devstack environment. Is there a way I can tell when the quota is finally being enforced? Or is there a way to force the account quota to be enforced sooner?20:33
*** daemontool has quit IRC20:36
claygtimburke: thanks!20:39
claygtdasilva: which files don't require it!?20:39
claygtdasilva: maybe ones that don't use print?20:39
tdasilvahttps://review.openstack.org/#/c/339192/2/bin/swift-drive-audit20:39
patchbottdasilva: patch 339192 - swift - Turn on H233 and start using print function20:39
tdasilvaclayg: maybe I'm confused, just don't see it there for example20:40
claygcastulo: it's up to the speed of the container updater cycle time - in devstack you can run like idk, just run one cycle in the foreground?  `swift-init container-updater once -nv`20:40
claygtdasilva: how interesting!20:42
castuloclayg: thanks, I'll try that20:43
claygtdasilva: wow, I guess like the parans can just be enclosing?  like print (1 == 2) is reasonable when print is a statement20:44
claygtdasilva: but it should be fixed in the patch, annoying to lint for I guess - print('foo', x) printing a tuple because the future import is missing is going to be annoying20:45
claygchange is fun!20:45
claygrewrite it in golang20:45
*** sheel has quit IRC20:45
*** diazjf has quit IRC20:46
*** tqtran-afk is now known as tqtran20:52
*** diazjf has joined #openstack-swift20:55
*** klamath_ has joined #openstack-swift21:06
*** klamath has quit IRC21:08
timburketdasilva: it comes down to whether the print usage would actually need the function instead of the statement. print("foo") works fine on both py2 and py3, without needing the __future__ import. print("foo", end="") doesn't and raises a SyntaxError. print() doesn't and fails in a subtle way21:12
openstackgerritMerged openstack/swift: Add __ne__ built-in function  https://review.openstack.org/33742821:13
timburkei could've just imported print_function everywhere, but i was lazy21:13
openstackgerritMerged openstack/swift: MockMemcached cleanup  https://review.openstack.org/33355421:14
*** rcernin has quit IRC21:17
notmynameFYI https://review.openstack.org/#/c/339175/21:26
patchbotnotmyname: patch 339175 - governance - [WIP] Community Input for alternate Programming La...21:26
openstackgerritNandini Tata proposed openstack/swift: Fixed inconsistent naming conventions  https://review.openstack.org/33924221:26
*** NM has quit IRC21:31
*** ozialien10 has joined #openstack-swift21:35
claygtimburke: well if there's any bugs with newlines that's all the more reason to move that code out of /bin into tested methods in /cli ;)21:37
castuloclayg: I set a container quota, then I ran the `swift-init container-updater once -nv` as you suggested, then I tried to upload an object larger than the quota and it was still uploaded...21:38
*** arcimboldo has joined #openstack-swift21:39
castuloclayg: anything else I can do to make swift enforce the quota? I'm seeing if I can do something in Tempest regarding bug https://bugs.launchpad.net/tempest/+bug/131059721:39
openstackLaunchpad bug 1310597 in tempest "race between quota setting and quota being enforced" [High,Confirmed]21:39
*** diogogmt has quit IRC21:40
openstackgerritNandini Tata proposed openstack/swift: Fixed inconsistent naming conventions  https://review.openstack.org/33924221:40
claygcastulo: container quotas don't need the container-updater to run like account quotas do21:41
claygcastulo: they are subject to the recheck_container_existence timeout form memcache I 'spose - uploading a new object doesn't nessecarily invalidate the container_info cache values in memcache21:42
*** diogogmt has joined #openstack-swift21:47
notmynamecastulo: also remember that quotas in swift aren't hard. it's known an documented and expected that there will be a little "slop" in the values that are enforced21:48
claygnotmyname: but it's not like we do `if quota_over_limit() and random.random() > 0.5` it's only going to wiff some something hasn't updated yet and stuff updates out-of-band21:49
notmynameof course. enforced for the current view that the container/account has, and those don't get updated synchronously with every object put/delete in the cluster21:50
castuloclayg: my mistake, what I set was the account quota, not container quota21:50
notmynamebut I didn't want castulo to be expecting something that doesnt' happen21:50
torgomaticthat'd be neat, though... between 90% and 100% of quota, start randomly failing requests in proportion to fullness (so 90% = no failures, 95% = half failures, 100% = all failures)21:52
torgomaticit'd be sort of like trying to pack a suitcase really full21:52
notmynameor trying tog et your kid to clean up his room21:52
castulonotmyname: so what do you mean by a "little slop in the values that are enforce"? Sorry if my question is too basic, I'm new to swift21:53
notmynamecastulo: no worries. let me find the link...21:53
notmynamecastulo: http://docs.openstack.org/developer/swift/api/container_quotas.html21:53
notmynamecastulo: specifically, the last 2 paragraphs there21:53
castulonotmyname: I see, and does that apply also to the x-account-meta-quota-bytes? My issue at the moment is with account quota, not container quota21:57
claygnotmyname: that page renders sorta shit - do we need to update some sphinx templates or something?21:57
notmynameclayg: probably oslosphinx. that's where the theme is.21:58
claygnotmyname: the navigation is sort of crap too - those are "the new api docs"?21:59
notmynamethe versions there?21:59
claygnotmyname: that and also there's no like link to the TOC that I can find?21:59
claygcastulo: "The same limitations apply for the account quotas as for the container quotas" -> http://docs.openstack.org/developer/swift/middleware.html#module-swift.common.middleware.account_quotas22:00
torgomaticcastulo: yeah, it also applies to the account... actually it's even worse; for containers, "might not be immediately updated" means "is usually immediately updated, but sometimes has a delay"22:00
torgomaticfor accounts, it's more like "is basically never immediately updated unless you get really lucky in your timing"22:01
openstackgerritShashirekha Gundur proposed openstack/python-swiftclient: fixing nit picks in python-swiftclient doc  https://review.openstack.org/33924922:01
*** diazjf has quit IRC22:01
castuloI see, and there is no way to really know when that update has been done, only by trying I guess?22:02
*** ManojK has quit IRC22:02
openstackgerritShashirekha Gundur proposed openstack/python-swiftclient: fixing nit picks in python-swiftclient doc  https://review.openstack.org/33924922:03
torgomaticyep; all the container -> account updates are done by background daemons running in the cluster somewhere, not by anything in the HTTP-serving path22:03
torgomatic(otherwise you'd incur massive update pressure on the account DB when the object PUT rate was high)22:04
notmynamewell, you look at logs and other metrics as part of the overall cluster monitoring. eg watch the updater cycle times22:04
*** ManojK has joined #openstack-swift22:04
torgomaticright, but as a consumer of the HTTP API, you have no idea when your object PUT will be reflected in account stats22:05
torgomaticand hence quotas22:05
claygthere's no good way in a test - someone said quotas were a bad idea one time for this reason - then we did it anyway22:05
notmynamerigth22:05
castulotorgomatic: I understand now, then I don't think there is really anything that can be done to fix bug https://bugs.launchpad.net/tempest/+bug/1310597 in Tempest, probably just completely remove the test22:05
openstackLaunchpad bug 1310597 in tempest "race between quota setting and quota being enforced" [High,Confirmed]22:05
notmynameclayg: well not just for this reason. I still don't like quotas, but I got over that a while back ;-)22:05
torgomaticclayg: can we find that person and hire them? :p22:05
notmynametorgomatic: I think it was me22:06
notmynametorgomatic: so....yes ;-)22:06
torgomatichehe22:06
*** darrenc is now known as darrenc_afk22:06
claygcastulo: probably not in your stock unittest-y framework - you need something like a burn in CI where you do some upload yesterday that pushes over quota - then today make sure you can't upload anymore and delete the account and create a new one for tomorrow22:06
claygi'm guessin you don't have infrastructure around long enough for that kind of test tho22:07
claygso... what-do-you-do22:07
notmynameclayg: that sounds really similar to what hurricanerix had built a while back for rax deployments22:07
torgomaticcastulo: yeah, it's not really amenable to a test from the consumer standpoint... it's really more suitable as a Swift probetest where the test code actually controls the running of the various daemons, so it can force an update when it wants22:07
claygnotmyname: yeah rax guys are all about that shit - i'm not sure how much "support" for that kind of process is baked into cloudcafe22:08
claygtorgomatic: all new middleware that requires probetests would be a great deterrent - i guess we have container_sync22:09
*** ManojK has quit IRC22:09
notmynameclayg: FWIW https://bugs.launchpad.net/oslosphinx/+bug/160002922:09
openstackLaunchpad bug 1600029 in oslosphinx "short pages are poorly rendered" [Undecided,New]22:09
castuloclayg: cool, I will update the bug then and will bring up the discussion with the QA team to see if the test should be removed from Tempest then.22:09
castulothanks for your help Guys! :)22:09
jrichliclayg torgomatic notmyname : is there something that a swift functional test could do to make this quota update happen? patch 314099 is sort of stuck at this same question22:14
patchbotjrichli: https://review.openstack.org/#/c/314099/ - swift - Container Object Count Quota Functional Test22:14
openstackgerritShashirekha Gundur proposed openstack/python-swiftclient: fixing nit picks in python-swiftclient doc  https://review.openstack.org/33924922:16
*** arcimboldo has quit IRC22:18
claygnotmyname: nice work!22:18
claygwhat if you just uploaded bytes into a container until a HEAD request seemed to reliably return some number of bytes - then set the quota to half of that (via POST which clears memcache) - i bet then you could mostly sort of expect/hope that you get an over quota limit (for containers)22:20
claygi bet 80% of the time it would work 100% of the time22:21
*** ozialien10 has quit IRC22:22
jrichliclayg: worth a shot, thanks22:24
*** darrenc_afk is now known as darrenc22:26
claygjrichli: sorry, i was joking - i don't think trying to test these things from a blackbox perspective is an exercise that will yeild value22:27
claygjrichli: torgomatic is right - we could do it in a whitebox probetest were we take control of all the asyncrouns actions and all failures are controlled22:28
openstackgerritMohit Motiani proposed openstack/swift: Add region in swift-ring-builder add  https://review.openstack.org/31934222:30
*** catintheroof has quit IRC22:40
konghi, guys, do you if there is an efficient way to get object upload/download bytes if users successfully do that?22:55
kongI am thinking about the traffic billing22:55
kongI found an in-progress spec related to that, but maybe not implemented. https://specs.openstack.org/openstack/swift-specs/specs/in_progress/notifications.html22:56
openstackgerritMerged openstack/swift: Python 3: Fix basestring, long and StringIO  https://review.openstack.org/33329723:01
openstackgerritMerged openstack/swift: Python 3: dict.iteritems() and dict.itervalues()  https://review.openstack.org/33329823:03
claygkong: everyone does network bytes for traffic billing from proxy logs, but it's not baked in because everyone seems to roll it different23:03
claygkong: slogging is open source, at some level everyone's code looks basically like this -> https://github.com/notmyname/slogging/blob/master/slogging/access_processor.py23:03
*** manous has joined #openstack-swift23:04
kongclayg: thanks for your reply first. So, swift don't support emit event yet, right?23:05
*** _JZ_ has quit IRC23:05
*** garthb has joined #openstack-swift23:05
notmynamekong: correct. swift does emit statsd messages with some aggregated transfer metrics, but it's not appropriate for billing since it isn't per user/account/tenant/whatever23:07
openstackgerritMerged openstack/swift: Correct reraising of exception  https://review.openstack.org/33877423:07
openstackgerritMerged openstack/swift: Tighten memcached tests  https://review.openstack.org/33355523:07
notmynamekong: the best way to get info for billing from a swift cluster is to process the logs23:07
kota_good morning23:09
kongnotmyname: ok, seems like the log analysis is the preferred way23:09
kota_clayg: do you have a time to look at https://gist.github.com/bloodeagle40234/e9a1f009336221c085d3d0086e621340 a bit?23:09
kongclayg, notmyname, thanks you guys!23:09
notmynamekong: there's also some degree of ceilometer integration, I think, that you could use. it sets up some polling workers and message queues that you could use. it would probably be ok for small, low-traffic clusters, but I have serious concerns about using it at scale23:10
kongnotmyname: is there any doc i can refer to? for ceilometer integration?23:11
*** siva_krish has joined #openstack-swift23:12
*** siva_krish has quit IRC23:12
torgomaticif you're thinking of using a message queue for computing someone's bill, just remember the two hard problems of distributed computing23:12
notmynamekong: unfortunately, I don't know. I mean, I'm sure there are somewhere. I'd start exactly where you would: a google search for "openstack ceilometer"23:12
torgomatic2. Exactly-once delivery23:13
torgomatic1. Guaranteed order of messages23:13
torgomatic2. Exactly-once delivery23:13
torgomatic(credit to https://twitter.com/mathiasverraes/status/632260618599403520?lang=en)23:13
notmynametorgomatic: yeah, I'm not a fan of it at all ;-)23:13
kongnotmyname: hah, good suggestion23:13
notmynamekong: that's one reason why I (strongly) think using logs for billing processing is much better23:14
kongnotmyname: ok, got you, thanks!23:14
notmynamekong: the other reason is because you can reply logs to validate calculations. you can't reply the message queue23:14
kongnotmyname: yes, good point. Actually, we already have a script to do that by reading bytes-in/bytes-out, but I just wonder if there is a better way to do23:15
kongand finally I got answer here23:16
notmyname:-)23:16
kongthanks again23:16
claygkota_: still trying to grok23:16
claygkota_: does my output looks like your output?23:17
clayg... i added a comment in the gist23:17
kota_clayg: my output is the first one shows the established connection still existing but the second one in green pool doesn't23:18
kota_clayg: oh, yes, the gist you pasted is same with me23:19
claygok, so step #1 - there is a different and it's reproduicible - awesome23:19
claygstep #2 - why is it different, what does it mean, is it bad?23:19
kota_so, the difference is the place running, the first one is in just python, the second one is in GreenPool.23:20
kota_but I'm not sure GreePool can collect the leak socket (or not)?23:20
kota_that's my question.23:21
kota_is it expected or not?23:21
kota_ah, ok. explaining step by step.23:22
*** ManojK has joined #openstack-swift23:22
kota_so we have a known issue if a instance of BufferedConnection is missing the reference, it could cause socket leak for the connection, right?23:23
kota_(if we don't call .close() before removeing reference)23:23
kota_correctly speaking, it might be HTTPConnection issue though.23:25
claygheh, we have a "SteamingPile" ... errr there might be an "r" in there somewhere23:25
*** Suyash has quit IRC23:27
kota_and i suppose it could happen even if it's in GreenPool because GreenPool supports network I/O concurrency, switching and I don't expect it supports something like gc on networking socket.23:27
kota_but... it can collect the garbage socket so I'm confused.23:27
*** ManojK has quit IRC23:30
*** ManojK has joined #openstack-swift23:33
openstackgerritMerged openstack/swift: Fixed inconsistent naming conventions  https://review.openstack.org/33924223:34
*** nadeem has quit IRC23:35
*** chsc has quit IRC23:36
claygkota_: maybe it's a green vs. real socket monkey-patch kinda thing?23:37
clayghttps://gist.github.com/clayg/c0e04175d120ffb33e531d02b665665523:37
claygkota_: ^ in this case both sock get closed... but that's dropping the reference to the socket directly instead of by dropping the connection - so maybe it's not apples to apples23:38
claygwell idk, if I replace the first test with a green_socket it shows the leak behavior like the orig23:39
claygwhere the netstat showed the established connection outside of the function call?23:39
kota_wait a bit, trying to the new one23:40
claygi'm sure buffered_http uses green httplib explicitly - so maybe it's just a different in how python works with the non-blocking socket if you don't poll it somehow like the eventlet hub does?23:40
claygkota_: I expect in the next version of the script the port param will make it all the way out to int(sys.argv[1]) - before long we'll be importing argparse :\23:40
kota_yeah, both sock get closed...23:42
*** manous has quit IRC23:43
kota_if we set a green socket to the first one, it seems still leaked, i can see FIN_WAIT23:45
*** siva_krish has joined #openstack-swift23:45
*** diogogmt has quit IRC23:46
kota_hmm.... interesting.23:48
*** siva_krish has quit IRC23:50
notmynamewow. lots of patches have landed today23:51
kota_clayg: the eventlet hubs to read is around here, https://github.com/eventlet/eventlet/tree/master/eventlet/hubs, right?23:52
timburkenotmyname: yup. crypto's done! what else can we do ahead of the hackathon?23:52
notmynametimburke: merge all the patches!23:52
timburkedamn straight!23:52
*** diogogmt has joined #openstack-swift23:54
kota_ah, looks like there is sort of FdListener there, so it could close if the thread ends, maybe???23:55
kota_look at more deelply...23:55

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