Wednesday, 2015-06-03

*** thurloat_isgone is now known as thurloat00:00
hogood morning!00:01
mattoliverauho morning00:03
homattoliverau: morning!00:03
hoBrian, around?00:04
*** shakamunyi has joined #openstack-swift00:12
*** barra204 has joined #openstack-swift00:12
*** jkugel has joined #openstack-swift00:14
hoall, do you know Brian Cline's IRC name and time zone?00:19
*** remix_tj has quit IRC00:21
*** remix_tj has joined #openstack-swift00:23
*** thurloat is now known as thurloat_isgone00:28
*** asettle has quit IRC00:42
*** breitz has quit IRC00:45
*** breitz1 has joined #openstack-swift00:45
*** bkopilov has quit IRC00:58
*** bkopilov has joined #openstack-swift01:08
*** superfly_ has joined #openstack-swift01:12
*** superfly_ is now known as superflyy01:14
hoping bcline01:21
tdasilvaho: I think it's briancline01:21
hotdasilva: briancline is right one?01:22
tdasilvaho: I believe so, but I think he is in the US01:23
tdasilvaso he might not be available around this time01:23
hotdasilva: thanks! it's difficult to get in touch with him because of our time zone ...01:23
*** barra204 has quit IRC01:24
*** shakamunyi has quit IRC01:24
*** superflyy has quit IRC01:24
*** blmartin has quit IRC01:34
*** nadeem has joined #openstack-swift01:50
*** kota_ has joined #openstack-swift01:52
kota_morning01:53
hokota_: morning!01:53
kota_ho: :)01:56
*** nadeem has quit IRC01:59
*** kota_ has quit IRC02:02
*** wbhuber has quit IRC02:15
*** jrichli has joined #openstack-swift02:22
*** haigang has quit IRC02:26
*** haigang has joined #openstack-swift02:27
*** annegentle has joined #openstack-swift02:28
*** haigang has quit IRC02:30
*** haigang has joined #openstack-swift02:32
*** haigang has quit IRC02:33
*** haigang has joined #openstack-swift02:34
*** haigang has quit IRC02:38
*** annegentle has quit IRC02:44
*** haigang has joined #openstack-swift02:46
*** annegentle has joined #openstack-swift02:51
*** annegentle has quit IRC02:51
*** Ciipher has quit IRC02:55
*** proteusguy has joined #openstack-swift02:58
*** gyee is now known as operator9903:00
*** jkugel has quit IRC03:11
*** remix_tj has quit IRC03:35
*** remix_tj has joined #openstack-swift03:38
*** jlk has joined #openstack-swift03:41
jlkhalp! I'm stuck in a world of invalid keystone tokens and I can't get out!03:42
jlkI can't figure out the magic to get my swift proxy to auth with keystone. I can't figure out if it's the password that's bad or the user's token that's bad, or something else entirely03:42
*** dimasot has joined #openstack-swift03:44
*** lcurtis_ has joined #openstack-swift03:48
hojlk: I try to solve your problem. but i have 1H meeting from now. could you tell me more detail of it?03:54
jlkho: so I am running swift client, with debug, and I can see it hit keystone for a token03:54
jlkit takes that token and attempts to use it against the swift end point, but gets a 401 from that03:54
jlkINFO:swiftclient:REQ: curl -i https://tardis-swift.openstack.blueboxgrid.com:8090/v2/9d60928c9cde4b2ea488c8296a03:54
jlk5707b9 -I -H "X-Auth-Token: 091a2dca7a054b6ca2accc48d78d9fac"03:54
jlkINFO:swiftclient:RESP STATUS: 401 Unauthorized03:54
jlkthat transactoin ID shows this in the swift log03:56
jlkJun  3 03:53:22 localhost.localdomain proxy-server: 173.247.104.24 10.230.6.16 03/Jun/2015/03/53/22 HEAD /v2/9d60928c9cde4b2ea488c8296a5707b9 HTTP/1.0 401 - - 091a2dca7a054b6c... - - - txb9cdeb3923e04a248f7d8-00556e7a32 - 0.0008 - - 1433303602.956839085 1433303602.95759201003:56
jlkit /seems/ to me that while my client is able to get a token, it's swift-proxy unable to auth to keystone in order to validate tokens03:57
*** jrichli has quit IRC04:03
hojlk: is it correct endpoint? it seems to use v2 api.04:04
jlkyes04:04
jlkendpoint is correct04:04
jlkI specified -V 2 in my swift command04:04
hojlk: v2 fro04:06
jlkhrm?04:06
hojlk: v2 for keystone works but not for swift04:06
jlkdid it work at one point?04:07
hojlk: i have to go to meeting now.04:07
jlkho: but my point is, the error happens when swift client talks to swift proxy and gives over the token. Swift proxy ties to do something with it, to validate the token and that's when the 401 comes back04:09
*** sorrison_laptop has joined #openstack-swift04:29
*** ppai has joined #openstack-swift04:40
*** lcurtis_ has quit IRC04:52
jlkdefinitely appears to be a problem in the ssl stuff. If I point it directly at keystone without ssl things work.05:01
hojlk: I'm back. If you don't use https for the communication, I think that the endpoint will be "http://tardis-swift.openstack.blueboxgrid.com:8090/v1/AUTH_%(tenant_id)s".05:07
jlksorry, let me rephrase05:07
jlkwhenI configure the authtoken middleware in the swift-proxy server to connect to keystone via http then everything works.05:07
jlkswift-proxy is able to validate the tokens.05:07
jlkbut if I have swift-proxy connect to keystone via https (through our haproxy) then it gets 401s05:08
*** Triveni has joined #openstack-swift05:08
hojlk: i see. in proxy-server log you wrote, there is "HEAD /v2/9d60928c9cde4b2ea488c8296a5707b9" message. So I think your endpoint registration to keystone seems to be wrong.05:16
jlkI switched it back to v1 (even though v2 was working in our havana version)05:16
jlkand even with v1 it is acting as I describe. http fine, https not fine05:16
jlkit's in how the proxy server is talking to keystone and ssl05:16
*** kota_ has joined #openstack-swift05:22
*** proteusguy has quit IRC05:28
hojlk: is it possible to execute curl command for getting token from keystone? http://paste.openstack.org/show/258504/05:35
hojlk: then I would like to know authtoken info in proxy-server.conf (lines of identity_uri and auth_uri)05:37
jlkthat token is kind of long, a big blob of json05:38
jlkso, auth_uri doesn't appear to actually be used, only identity_uri05:39
*** SkyRocknRoll has joined #openstack-swift05:39
*** SkyRocknRoll has joined #openstack-swift05:39
hojlk: both commands work? could you paste the uri of the commands here?05:45
jlkwell, I'm not sure what all from this token response I need to cpy. It's like 30 lines05:45
hojlk: I need only your execution line. not output.05:45
hojlk: s/execution line/executed command/05:46
jlkif what ou want is to make sure I can see the endpoints with the user that swift proxy is configured to use, yes, I can. When I create a stackrc with those credentials, I can do a keystone catalog just fine05:47
jlkDEBUG:keystoneclient.auth.identity.v2:Making authentication request to https://tardis.openstack.blueboxgrid.com05:48
jlk:5001/v2.0/token05:48
jlkit gets the token, gets the catalog05:48
jlkcurl -g -i -X GET https://tardis.openstack.blueboxgrid.com:35358/v2.0/endpoints -H "User-Agent: python-keystoneclient" -H "Accept: application/json" -H "X-Auth-Token: {SHA1}9d9ae562e6289b605:49
jlk810e77836f5c304f25b6286cf"05:49
jlkendpoints come across fine05:49
hojlk: can I see the endpoit of object-store and identity_uri in proxy-server.conf ? just make sure.05:50
jlkobject-store endpiont is05:51
jlk| 0eb4fce9d14941b5b7d26de329a6dcad | RegionOne | https://tardis-swift.openstack.blueboxgrid.com:8090/v1/%(tenant_id)s | https://tardis-swift.openstack.blueboxgrid.com:8090/v1/%(tenant_id)s | https://tardis-swift.openstack.blueboxgrid.com:8090/v1/%(tenant_id)s | 9695a549a04044838fde970a31e3a4e9 |05:51
jlkright now, I have identity_uri as identity_uri = http://10.230.6.1:5000  which is the private IP of the keystone server, because it works.  Normally it would be https://tardis.openstack.blueboxgrid.com:35358/v2.005:52
openstackgerritMerged openstack/swift: Don't quarantine on read_metadata ENOENT  https://review.openstack.org/18711605:58
hojlk: thanks! is it possible to try this: identity_uri = https://10.230.6.1:3535805:58
jlkI can try, but I did try that. That port will hit the haproxy running on that host (we run haproxy on both our keystones). that will break. SSL is terminated at the haproxy.06:02
jlkAccount GET failed: https://tardis-swift.openstack.blueboxgrid.com:8090/v1/5da25cc3853f4c54850898f9614c20bb?format=json 401 Unauthorized  [first 60 chars of response] <html><h1>Unauthorized</h1><p>This server could not verify t06:03
jlkproxy log shows06:04
jlkJun  3 06:03:20 localhost.localdomain proxy-server: Authorization failed for token06:04
hojlk: i see. is it possible to change endpoint using AUTH_?  your endpoint is not using AUTH_ for tenant name. https://tardis-swift.openstack.blueboxgrid.com:8090/v1/AUTH_%(tenant_id)s  is there any reason?06:06
jlkBecause it's not necessary?06:07
jlkWe don't use it in other swift endpoints06:07
hojlk: Does it work?06:07
jlkyes06:07
hojlk: you use habana right? I will check the code of keystoneauth.06:08
jlkWe were on havana, now we're on juno06:08
jlkI have another swift stack on juno as well with seemingly identical configuration and it's functional. I can't find the difference.06:09
jlkI'm giving up for the night, it's late and I have to be up early. Thank you for your help so far06:12
hojlk: have a good night! Sorry I can not solve it...06:13
*** shakamunyi has joined #openstack-swift06:16
openstackgerritChristian Schwede proposed openstack/swift: Fix testing issues  https://review.openstack.org/18775406:17
*** barra204 has joined #openstack-swift06:17
ppaicschwede, I noticed in my saio vm that "tox -e func" when none of the swift services are running returns a success. Does 187754 fix that ?06:19
*** proteusguy has joined #openstack-swift06:20
*** proteusguy has quit IRC06:20
cschwedeppai: yes, exactly - there are two issues here: 1. exception is catched and tox reports a success 2. missing python-keystoneclient, raising the exception06:20
cschwedeppai: i’m still investigating why openstack.nose_plugin catches the exception atm06:20
hojlk: I assume you don't use user which has reseller_admin_role. If your endpoint is not started with AUTH_, you meet L394 in keystoneauth. https://github.com/openstack/swift/blob/stable/juno/swift/common/middleware/keystoneauth.py#L39406:22
ppaicschwede, cool!06:22
hojlk: So you need to put reseller_prefix for your endpoint at least in Juno. But if you use an user which is reseller_admin_role, it works.06:26
*** sorrison_laptop has quit IRC06:27
openstackgerritPrashanth Pai proposed openstack/swift: Make object creation more atomic in Linux  https://review.openstack.org/16224306:29
*** Trixboxer has quit IRC06:32
*** silor has joined #openstack-swift06:35
openstackgerritChristian Schwede proposed openstack/swift: Fix testing issues  https://review.openstack.org/18775406:35
hokota_: around?06:38
ppaicschwede, your patch fixes it http://paste.openstack.org/show/258658/06:38
cschwedeppai: cool, thanks for checking this!06:39
kota_ho: hi06:44
kota_I'm now reading scroll back recent irc channel logs...06:45
hokota_: thanks for the review. as for the patch 187489, I think your understanding is not correct.06:46
patchbotho: https://review.openstack.org/#/c/187489/06:46
kota_ho: ok, let me know...06:46
*** asettle has joined #openstack-swift06:49
kota_ho: swift has constraints about max_meta_name_length, max_meta_value_length and max_meta_overall_size, right/06:49
kota_?06:49
hokota_: wait a minute06:50
kota_ho: i think existing tests makes some kinds of metadata under constraint max_meta_overall_size and then filling up the rest of size by X-Account-Meta-k06:51
kota_ho: ok, waiting06:51
hokota_: sorry, I was caught by my boss...06:54
kota_ho: no worries :)06:55
hokota_: the post at L827 is first one with the header the size is 409606:55
kota_ho: test/functional/test_account.py?06:56
hokota_: the post at 840 is only update X-Account-Meta-k without any size change.06:56
hokota_: yes06:57
kota_ho: I still didn't get the purpose.06:58
kota_ho: you mean we need an assertion for metadata updates?06:59
kota_ho: but the first post means metadata updates because "POST" is used for metadata updates.06:59
hokota_: now i'm looking for acoles' patch. wait a minute.06:59
kota_ho: which one? related to 187489?07:01
*** admin6 has joined #openstack-swift07:01
hokota_: found it the patch #18726407:02
kota_ho: thx07:03
hokota_: in this patch, acoles added a test "this last POST would be ok by itself but takes the aggregate backend metadata size over limit"07:05
hokota_: I thought it's better to have border one but my review for it didn't meet the dead line. So I submitted by myself.07:06
kota_ho: sounds these are just sanity for successful request...07:08
kota_ho: now reading the acoles's commit message.07:09
hokota_: the purpose is "tighten up the metadata size tests"07:10
kota_ho: I'm assuming acoles intended that we should assert the constraint should be checked from the backend aggregation.07:12
kota_ho: and it has done on 187264 basically.07:13
kota_ho: now I'm realising we might have your patch but maybe more description seems needed to land.07:13
kota_ho: because the constraint test has existed by 187264 and I don't want to make other reviewers to misunderstand, if it's only me to do so...07:15
*** hugespoon has quit IRC07:16
*** sudorandom has quit IRC07:16
*** hugespoon has joined #openstack-swift07:16
*** sudorandom has joined #openstack-swift07:18
*** hseipp has joined #openstack-swift07:18
*** hseipp has quit IRC07:18
*** hseipp has joined #openstack-swift07:18
kota_ho: so maybe commit message should be updated because the border case is existing.07:18
*** haigang has quit IRC07:19
hokota_: i think constraint test needs to cover it's border such as line829 and line835.07:20
kota_ho: I guess you want to add the border case of the constraint on the aggregated size between incomming and existing metadata size, right?07:20
kota_ho: does it increase test corverage on nosetests?07:21
hokota_: yes.07:22
hokota_: as for the coverage, i didn't check it.07:23
hokota_: do i need to check the coverage? do you know how to do it?07:24
kota_ho: not sure but I guess tox shows the coverage or use an option to show it (please see nose manual)07:25
kota_ho: if it increase the coverage, it will be good reason to land.07:25
kota_s/increase/increases/07:26
kota_ho: right now I'm realising not to oppose your opinion to add the sanity but I'd like to reccomend you to write the reason why we need this and what's difference from exisiting *the border case* in commit message.07:28
kota_ho: like as acoles's merged patch.07:29
kota_ho: *because* the border case looks duplicated...07:30
kota_ho: and I'd like to appologize my misundrstanding (2nd) on gerrit comment. This change should assert the border case.07:33
*** silor has quit IRC07:33
hokota_: I was caught by my boss again.. sorry... thanks for your comment. I will update the commit message and I'm happy to have your understanding of the code.07:34
*** chlong has quit IRC07:37
*** zhill_ has joined #openstack-swift07:38
kota_ho: logged the summary on the discussion, here :)07:40
*** jistr has joined #openstack-swift07:51
*** acoles_away is now known as acoles07:58
acolesgood morning07:59
kota_acoles: morning08:00
cschwedeGood Morning!08:02
cschwedeacoles: found the bug: https://github.com/cschwede/nose-example-bug08:02
acolescschwede: so running nose with --with-openstack fixes all bugs! thats the power of openstack :D08:05
*** admin6 has quit IRC08:05
*** admin6_ has joined #openstack-swift08:05
cschwedehaha, yeah! :D08:05
acolescschwede: seriously, good work, thx.08:06
cschwedei’m sending a mail to -infra and -dev soon, might be that other projects are affected too08:06
cschwedethx08:06
acolesso is the issue that errors raised *during package setup* are ignored?08:07
cschwedeacoles: yes08:09
cschwedeand then the whole package isn’t executed08:09
cschwedewhich basically means - skip the tests08:10
*** sudorandom has quit IRC08:11
*** jordanP has joined #openstack-swift08:12
*** hugespoon has quit IRC08:13
*** CrackerJackMack has quit IRC08:13
*** hugespoon has joined #openstack-swift08:13
acolescschwede: my saio is in a mess after last night, i will restore and then try out your patch 187754 locally.08:13
patchbotacoles: https://review.openstack.org/#/c/187754/08:13
acolesi'm curious to see if jenkins passes func tests with keystone now you have added keystoneclient requirement08:14
acoleskota_: hi!08:14
kota_acoles: hi :)08:15
*** CrackerJackMack has joined #openstack-swift08:18
*** sudorandom has joined #openstack-swift08:19
cschwedeacoles: notmyname: bug report for the -infra team: https://bugs.launchpad.net/swift/+bug/146144008:19
openstackLaunchpad bug 1461440 in OpenStack Object Storage (swift) "Tests are not run, but reported as success" [Undecided,In progress] - Assigned to Christian Schwede (cschwede)08:19
*** admin6 has joined #openstack-swift08:19
*** admin6_ has quit IRC08:19
*** zhill_ has quit IRC08:19
kota_cschwede: hi08:27
kota_cschwede: I pushed a pull request to your durability calculater repository for EC case :)08:28
kota_cschwede: just now08:28
kota_cschwede: please let me know if you have requests to fix my patch set ;)08:30
openstackgerritChristian Schwede proposed openstack/swift: Fix testing issues  https://review.openstack.org/18775408:31
cschwedekota_: great, just saw that! thanks for the PR, i will review it later and merge it then08:32
kota_cschwede: :)08:34
*** ho has quit IRC08:36
jordanPcschwede, thanks for fixing the func tests in the gate :)08:42
cschwedejordanP: you’re welcome - glad that you brought this up! might be that other projects are affected as well?08:43
jordanPI don't know, in fact, we run a 3rd party CI to test swift again our diskfile and we kept failing the "test_tempurl_keys_visible_to_account_owner" test. So I wondered whether this test passed 'upstream'. That's how I noticed it was not run.08:44
cschwedejordanP: it didn’t pass upstream on the gate, but locally. i just updated my patch, and hopefully the last version fixes the issue with the tempurl tests as well08:49
*** tellesnobrega has quit IRC09:07
*** geaaru has joined #openstack-swift09:30
*** silor has joined #openstack-swift09:31
cschwedeyeah, tests are running & passing again! https://jenkins05.openstack.org/job/check-swift-dsvm-functional/226/console09:57
cschwedeacoles: ^^09:57
acolescschwede: nice09:59
*** tellesnobrega has joined #openstack-swift10:02
*** hseipp has quit IRC10:03
*** mmcardle has joined #openstack-swift10:12
*** mmcardle has quit IRC10:14
*** [1]dimasot has joined #openstack-swift10:24
*** dimasot has quit IRC10:26
*** [1]dimasot is now known as dimasot10:26
*** rvasilets has left #openstack-swift10:27
acolescschwede: i am so confused :(10:30
cschwedeacoles: ? maybe i can help?10:30
acolesthe func tests ran but both runs were with keystone config i think (tests requiring account acls skipped both times)10:30
acoleswhich i thought i had fixed back in february10:31
*** samueldmq has joined #openstack-swift10:31
samueldmqnotmyname, morning10:31
samueldmqnotmyname, thanks for updating the oslo.policy bug on swift side10:31
acolescschwede: https://review.openstack.org/#/c/158671/ ... tests after that merged were running against tempauth10:33
*** mmcardle has joined #openstack-swift10:39
cschwedeacoles: hmm, that’s strange10:44
*** mmcardle has quit IRC10:45
cschwedeacoles: found it - top of the changelog, 2.0.0: http://tox.readthedocs.org/en/latest/changelog.html10:45
cschwede"introduce environment variable isolation"10:45
acolescschwede: yes. i wondered if the test config file was not being found but that would cause IN_PROCESS mode to be used and that would be clearly logged10:45
acolescschwede: heh. that would explain it!10:46
acolesso looks like we need to patch infra with the passenv setting10:47
acolespatch tox.ini i mean10:48
cschwedeyes, doing that right now10:49
cschwedeSWIFT_TEST_AUTH,SWIFT_TEST_USER,SWIFT_TEST_KEY,SWIFT_TEST_POLICY,SWIFT_TEST_IN_PROCESS_CONF_DIR,SWIFT_TEST_IN_PROCESS,SWIFT_TEST_IN_MEMORY_OBJ - anything i forgot?10:49
acolescschwede: good man!10:50
acolesjust the important one: SWIFT_TEST_CONFIG_FILE :D10:51
acoleslooks like passenv = SWIFT_* might work10:51
acolescschwede: https://bugs.launchpad.net/openstack-gate/+bug/1455102 <- be worth linking from your patch10:54
openstackLaunchpad bug 1455102 in python-novaclient "some test jobs broken by tox 2.0 not passing env variables" [High,In progress] - Assigned to Sean Dague (sdague)10:54
openstackgerritChristian Schwede proposed openstack/swift: Fix testing issues  https://review.openstack.org/18775410:54
cschwedeok, trying with SWIFT_* - looks better than the long line, and using that is is more likely to catch all possible future env variables as well10:55
openstackgerritChristian Schwede proposed openstack/swift: Fix testing issues  https://review.openstack.org/18775410:55
acolesBTW the swiftclient bug I found that was causing my func tests to not run came in after 2.4.0 so not yet affecting jenkins10:56
cschwedebut it is a bug and will break things if a new release is published?10:57
acolesoh yes, i have a fix just running tests...10:58
cschwedeacoles: patch 187749 ?10:59
patchbotcschwede: https://review.openstack.org/#/c/187749/10:59
acolescschwede: i updated  bug 1455102 with a link to your patch10:59
openstackbug 1455102 in python-novaclient "some test jobs broken by tox 2.0 not passing env variables" [High,In progress] https://launchpad.net/bugs/1455102 - Assigned to Sean Dague (sdague)10:59
acolesyes 18774911:01
openstackgerritKota Tsuyuzaki proposed openstack/swift: Fix missing container update  https://review.openstack.org/18673511:02
*** lcurtis_ has joined #openstack-swift11:03
openstackgerritAlistair Coles proposed openstack/python-swiftclient: Make default get_auth timeout be None  https://review.openstack.org/18774911:04
acolescschwede: zaitcev: ^^11:08
cschwedeacoles: thx, just saw it - now with tests :)11:08
*** kota_ has quit IRC11:09
*** lcurtis_ has quit IRC11:10
acolesok time for a coffee...11:11
*** Triveni has quit IRC11:12
*** zul has quit IRC11:22
*** cdelatte has joined #openstack-swift11:25
*** aix has quit IRC11:25
*** delattec has joined #openstack-swift11:25
*** zul has joined #openstack-swift11:28
*** [1]dimasot has joined #openstack-swift11:30
*** dimasot has quit IRC11:33
*** [1]dimasot is now known as dimasot11:33
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873611:35
*** dimasot has quit IRC11:46
*** distroguy has quit IRC11:55
*** aix has joined #openstack-swift12:00
*** lpabon has joined #openstack-swift12:02
*** distroguy has joined #openstack-swift12:02
*** ppai has quit IRC12:04
*** distroguy has quit IRC12:07
*** SkyRocknRoll has quit IRC12:16
openstackgerritMark Seger proposed openstack/swift: Change usage help and Attention messages to warnings  https://review.openstack.org/18797412:17
*** distroguy has joined #openstack-swift12:17
*** ppai has joined #openstack-swift12:17
acolescschwede: so it seems the reason i could not get tox 2.0.1 to install a venv last night is because of the change you spotted - my http_proxy env vars are no longer passed so pip cannot reach pypi :/ and there seems to be no tox command line override to force the var through to venv12:20
acolescschwede: do you think it is acceptable to add http_proxy (and https_proxy and no_proxy) to passenv in tox.ini? seems ugly but i can't see an alternative12:22
cschwedeacoles: oh wow, now that is bad luck! i’m wondering if adding a *_proxy would work too. trying12:23
acolescschwede: the other answer is that i work at home everyday ;)12:24
*** mmcardle has joined #openstack-swift12:24
acolesactually we have a pypi mirror inside but that brings another set of issues...12:25
cschwedeacoles: what do you prefer? shall i search for a good technical reason to avoid that env variable, and force you to stay home? ;)12:25
openstackgerritKota Tsuyuzaki proposed openstack/swift: Fix missing container update  https://review.openstack.org/18673512:25
*** mmcardle has quit IRC12:26
acolescschwede: heh12:26
acolesi can try *_proxy12:26
acolescschwede: yes *_proxy works. so do you think it could be added with your patch or shall i do a follow on patch?12:31
cschwedeacoles: thx for checking, i’ll add it12:32
acolesbt i ran into this because i am verifying your patch with tox2.0.1 locally12:32
acolescschwede: maybe there is someone else that will benefit from passenv = *_proxy12:33
openstackgerritChristian Schwede proposed openstack/swift: Fix testing issues  https://review.openstack.org/18775412:33
cschwedeacoles: yes, i would assume so. i think an update to the bugreport is also a good idea to notify others12:34
acolesyup i will do that12:34
*** mmcardle has joined #openstack-swift12:36
*** mwheckmann has joined #openstack-swift12:45
*** bi_fa_fu has joined #openstack-swift12:51
*** jistr is now known as jistr|mtg12:57
*** kei_yama has quit IRC13:05
*** mmcardle has quit IRC13:06
*** km has quit IRC13:12
*** jkugel has joined #openstack-swift13:14
openstackgerritAlistair Coles proposed openstack/swift: Fix testing issues  https://review.openstack.org/18775413:14
acolescschwede: ^^ passenv needed to be space separated13:15
acolescschwede: i added a note in the docs about needing tox -r13:15
cschwedeacoles: thx for the update, looks good!13:16
acolescschwede: just realised i have the same issue with tox and http_proxy on all projects!13:22
cschwedeacoles: ouch! that hurts13:24
*** petertr7_away is now known as petertr713:25
acolescschwede: yeah. i think i will need to write a tox.ini-morphing script to add the passenv option locally13:26
*** ppai has quit IRC13:28
*** hseipp has joined #openstack-swift13:31
*** hseipp has quit IRC13:31
*** hseipp has joined #openstack-swift13:32
petertr7Hi cschwede, I was wondering, what are your general plans are for django-swiftbrowser?13:37
*** ahale has quit IRC13:38
*** blmartin has joined #openstack-swift13:40
*** blmartin_ has joined #openstack-swift13:42
*** SkyRocknRoll has joined #openstack-swift13:44
cschwedepetertr7: Hello Peter! Well, I want to add a few more key features, for example pagination, metadata and a better way to integrate 3rd party addons/plugins13:45
cschwedepetertr7: I’m also looking into making it usable (again) without Javascript, by using some more sane defaults13:45
petertr7cschwede, Hello =) Ahh I see13:46
cschwedepetertr7: what are you looking for?13:46
cschwedeanything specific that you’d like to see?13:46
petertr7cschwede, I got started on pagination actually. I created a stack that tracks container names. It works but it's a little messy13:46
petertr7Thanks for asking. I just wanted to get an idea of what direction you were moving in so I can potentially push back upstream13:47
cschwedepetertr7: yes, please do so :) that said, i think there is already a PR from you, adding pagination, or not?13:49
petertr7Yes that's me13:50
petertr7I think I need to build some test cases for it13:50
cschwedethat would be great13:51
petertr7Great13:51
petertr7I am a little stumped. How would I replicate queries to a swift cluster while doing unit testing?13:52
petertr7For example, I have a function that retrieves the next 5 containers starting from container "alpha". While testing locally I just created the containers on my cluster manually13:52
petertr7How do I automate it so that the unit test can run independent of connecting to a swift cluster?13:53
*** zaitcev has joined #openstack-swift13:53
*** ChanServ sets mode: +v zaitcev13:53
cschwedepetertr7: you need to mock the functionality in the tests. for example: https://github.com/cschwede/django-swiftbrowser/blob/master/tests/test_swiftbrowser.py#L83-L10913:56
cschwedepetertr7: line 94 (https://github.com/cschwede/django-swiftbrowser/blob/master/tests/test_swiftbrowser.py#L94) contains the dummy data (container listing), that is then used by swiftbrowser in the tests13:57
petertr7Ohhh I see13:57
petertr7That's convenient13:57
petertr7Thank you!13:57
*** jistr|mtg is now known as jistr13:59
cschwedeyou’re welcome!13:59
openstackgerritMark Seger proposed openstack/swift: Change usage help and Attention messages to warnings  https://review.openstack.org/18797414:01
*** distroguy has quit IRC14:07
openstackgerritAlistair Coles proposed openstack/python-swiftclient: Run functional tests using keystone auth options  https://review.openstack.org/12351414:09
*** csmart has joined #openstack-swift14:10
*** silor has quit IRC14:11
*** silor1 has joined #openstack-swift14:11
*** bkopilov has quit IRC14:12
*** petertr7 is now known as petertr7_away14:15
*** petertr7_away is now known as petertr714:16
*** acampbell has joined #openstack-swift14:18
*** acampbel11 has joined #openstack-swift14:19
*** wbhuber has joined #openstack-swift14:20
*** david-lyle has quit IRC14:25
*** bsdkurt has joined #openstack-swift14:27
*** bsdkurt has quit IRC14:28
*** bsdkurt has joined #openstack-swift14:28
*** thurloat_isgone is now known as thurloat14:29
*** petertr7 is now known as petertr7_away14:30
*** petertr7_away is now known as petertr714:31
*** barra204 has quit IRC14:36
*** shakamunyi has quit IRC14:36
*** minwoob has joined #openstack-swift14:37
*** acampbel11 has quit IRC14:39
*** acampbell has quit IRC14:39
openstackgerritMark Seger proposed openstack/swift: Change usage help and Attention messages to warnings  https://review.openstack.org/18797414:49
*** petertr7 is now known as petertr7_away14:55
*** jordanP has quit IRC15:17
openstackgerritMark Seger proposed openstack/swift: Change usage help and Attention messages to warnings  https://review.openstack.org/18797415:19
*** petertr7_away is now known as petertr715:26
*** mmcardle has joined #openstack-swift15:33
*** david-lyle has joined #openstack-swift15:39
*** jrichli has joined #openstack-swift15:41
*** mmcardle has quit IRC15:41
*** david-lyle has quit IRC15:47
thurloatdoes the swift-ring-builder do anything differently if it has access to the services listed in the rings?15:49
thurloatI'm getting drastically different results running a ring-builder add & rebalance between a local server, and a proxy node15:50
thurloathere's the different outputs: https://gist.githubusercontent.com/thurloat/fdd8f33db357c0451518/raw/1a48890617c5462905dc46fed07d28faa2c4e9d6/output15:53
*** david-lyle has joined #openstack-swift15:53
*** acampbell has joined #openstack-swift15:54
*** acampbel11 has joined #openstack-swift15:54
thurloatbuilders are the same both local and on proxy server (checksummed to make sure)15:54
*** lpabon has quit IRC15:54
notmynamegood morning15:55
acolesnotmyname: good morning15:58
thurloatnotmyname, word16:00
notmynameI'm down at http://storageconference.us today16:01
notmynameunfortunately, I'm on a panel that looks like it will overlap with today's swift team meeting16:01
*** mmcardle has joined #openstack-swift16:02
*** mmcardle has quit IRC16:03
*** jistr has quit IRC16:11
*** nadeem has joined #openstack-swift16:15
notmynamewhich raises the question of having today's meeting or not16:16
notmynameany thoughts?16:16
*** nadeem has quit IRC16:16
*** pksingh__ has joined #openstack-swift16:17
notmynamecurrent agenda is at https://wiki.openstack.org/wiki/Meetings/Swift16:18
notmynamenot much there except a question of what to do with py3/six patches16:18
pksingh__Hi,  could you guys please review :  SwiftClient object upload beginning with / or "./"   https://review.openstack.org/#/c/185269/216:19
acolesnotmyname: maybe py3/six discussion can wait a week? i see plenty of other reviewing to keep us busy16:20
*** admin6 has quit IRC16:20
notmynameacoles: yeah16:20
pksingh__Hi could you guys please review : Read the response body, if response status is greater than 300 https://review.openstack.org/#/c/183899/16:20
notmynameand every mornign when I wake up I'm seeing a ton of swift emails from gerrit. very nice to see a lot of reviews going on16:20
*** jamielennox is now known as jamielennox|away16:21
*** barra204 has joined #openstack-swift16:21
*** david-lyle has quit IRC16:22
acolestorgomatic: ping16:22
*** bi_fa_fu has quit IRC16:22
*** gyee has joined #openstack-swift16:23
notmynameok, let's skip today's meeting16:23
notmynamesorry for the last minute notice.16:24
*** barra204 has quit IRC16:28
*** pksingh__ has quit IRC16:29
*** proteusguy has joined #openstack-swift16:29
thurloatI think i found out why I had different output: https://review.openstack.org/#/c/115441/16:29
thurloatlooks like I was running a newer version on the local server -- and it appears as if it works 'better' than the prod version in rebuilding.16:29
ctennisthurloat: reassigning 100% partitions in the 2nd example seems really odd (bad?).  Essentially every partition has moved, which is likely something you really do not want to have happen.16:32
ctennisi'm sure there's some strange nuance to that, but I don't know why it would do that16:33
thurloatctennis, i thought it was strange behaviour for adding two drives to want to redistribute everything16:36
ctennisyeah that sounds wrong.16:36
*** SkyRocknRoll has quit IRC16:37
thurloatthanks for the sounding board ctennis. going to move forward /w my upgrades now :)16:38
*** dimasot has joined #openstack-swift16:38
notmynameI'm starting to go through some LP bugs while I'm in the back of the room at this conference16:38
*** petertr7 is now known as petertr7_away16:38
notmynametag for erasure-code related work is "ec". please tag things there as needed, and look there for stuff that we need to get done16:39
notmynamepeluse: torgomatic: clayg: ^16:39
*** marzif_ has joined #openstack-swift16:39
notmynamehttps://bugs.launchpad.net/swift/+bugs?field.tag=ec16:40
pelusecool16:46
peluseso remind me again how I tag something? :)16:46
*** RackerShagz has joined #openstack-swift16:47
*** bsdkurt has quit IRC16:48
*** bsdkurt has joined #openstack-swift16:49
*** dimasot has quit IRC16:50
notmynamepeluse: heh, I had to relearn that myself16:50
notmynamepeluse: right under the description there's a "tags" field16:51
*** SkyRocknRoll has joined #openstack-swift16:51
*** hseipp has left #openstack-swift16:51
notmynamepeluse: if none are assigned, then it says "add tags"16:51
notmynameif there are some, it will list them16:51
peluseOK, is it just for bugs?16:51
notmynametags are space-separated16:51
notmynameand seemingly don't allow _16:51
notmynamebut - is fine16:51
notmynameyeah. or rather, it's for launchpad16:51
peluseOK thanks,  For patches should we use topic EC or not worry about trying to all be consistent there?16:52
openstackgerritAlistair Coles proposed openstack/python-swiftclient: Add passenv to tox.ini to make functests run with tempauth  https://review.openstack.org/18808016:52
notmynamepeluse: so my idea is that I want to get a good portion of the LP bugs for swift/swiftclient triaged and tagged and then have something similar to the gerrit dash or the priority reviews page to track them and know what to work on16:52
acolescschwede: ^^ same issue on swiftclient func tests16:52
pelusegotcha16:52
notmynamepeluse: oh yeah. whatever you want. I don't really care about what "topic" you use for patches16:52
pelusethat opens up all sorts of doors :)16:53
acolespeluse: be good ;)16:53
peluseFYI low hanging review fruit policy/EC related fix: https://review.openstack.org/#/c/185459/16:55
*** kutija has joined #openstack-swift16:57
*** david-lyle has joined #openstack-swift17:13
*** david-lyle has quit IRC17:13
*** david-lyle has joined #openstack-swift17:15
*** geaaru has quit IRC17:19
*** david-lyle has quit IRC17:28
*** petertr7_away is now known as petertr717:29
notmynametimburke: seems like your patch fixes this? https://bugs.launchpad.net/swift/+bug/118114617:30
openstackLaunchpad bug 1181146 in OpenStack Object Storage (swift) "TypeError: exceptions must be old-style classes or derived from BaseException, not NoneType" [Medium,Fix committed] - Assigned to Samuel Merritt (torgomatic)17:30
notmynametimburke: you tagged the patch as "related bug", not "closes bug". is there more work needed for that bug?17:31
notmyname(I marked it as "fix committed" for now17:31
*** fthiagogv has joined #openstack-swift17:34
jlkHey all, so I need some help in debugging swift <-> keystone interaction, particularly over SSL. If I point my swift at my haproxy that terminates SSL for keystone I get failures authing tokens from swift-proxy. But if I point it directly at keystone non-ssl things work. I need some help.17:44
claygjlk: what are you using to validate haproxy is terminating ssl and forwarding to keystone correctly (outside of swift)17:52
jlkclayg: my other services all do this, nova, glance, neutron, etc.. and they all work fine. My client software can get tokens from that keystone endpoint correctly.17:53
acolesjlk: someone had a similar issue in here recently, turned out be to do with setting insecure=true in authtoken middleware config section of proxy-server.conf iirc. ymmv17:53
jlkswift client code gets the token successfully from the same auth point that swift-proxy points to.17:53
acolesjlk: https://github.com/openstack/keystonemiddleware/blob/master/keystonemiddleware/auth_token/__init__.py#L27017:53
jlkI would hope we don't have to do that. We are pointing to a ca file that has our cert in it inside the swift-proxy config17:53
claygjlk: excellent - can you reproduce the results with keystone client *on* one of the proxy nodes?17:54
jlkyes, that's what I've been doing, using swift client on the proxy node17:54
acolestorgomatic: you around?17:54
jlkthe cert is cafile = "/etc/ssl/certs/ca-certificates.crt"17:54
claygnotmyname: you're going to town on some bug triage - nice!17:56
jlkI've also constructed a stackrc file with swift's credentials and with that stackrc I can still get a catalog from keystone17:56
acolestorgomatic: nm. i'm +2 on your mult-range ec get patch but the ocd in me wants to fix the rfc ref in the commit message.17:56
acolestorgomatic: i'll change it and risk incurring your wrath17:56
timburkenotmyname: mainly marked it as related since it only addressed the logging, rather than whatever was triggering exceptions under load. i suppose that'll have to wait for another, more specific ticket17:57
claygjlk: yeah so that's swiftclient talking to the public keystone uri - what about the admin uri that's used for token validation?  Can you validate that path - from a proxy node - outside of swift (e.g. using the keystone-client command line utility and swift's service account creds pointed to the keystone admin uri you have configured in the proxy's authtoken middleware section)17:58
openstackgerritAlistair Coles proposed openstack/swift: EC: support multiple ranges for GET requests  https://review.openstack.org/17349717:58
jlkclayg: yes17:59
jlkclayg: our swift runs out if a venv, I'm wondering if it's some problem with ssl validation inside the venv, even with the config settings pointing to our ca file. I just don't know how to properly debug that bit of interaction inside swift-proxy18:00
claygwell - it's hard - the keystone authtoken middleware doesn't log that great :\18:02
jlkso I've noticed.18:02
jlkit has log.DEBUG in the code, but how does one turn that on?18:02
claygyou could ativate the virtualenv and repeat the keystone admin with swift creds from the commandline test18:03
clayglog_level = DEBUG in the [DEFAULT] section in proxy conf + restart proxy18:03
jlkyeah I have that18:03
jlkoh18:03
claygs/restart/reload/g18:03
*** acoles is now known as acoles_away18:03
torgomaticacoles: sup?18:03
torgomaticpfft :D18:03
*** proteusguy has quit IRC18:04
jlkokay got more now.18:05
jlkraise exceptions.SSLError(msg)#012SSLError: SSL exception connecting to https://tardis.openstack.blueboxgrid.com:35358: [Errno 185090050] _ssl.c:340: error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib18:05
jlkso looks like authtoken isn't loading the CA file correctly18:06
claygheh - tardis18:13
jlklovely, how the heck.18:13
claygjlk: oh yeah - i was going to ask if you tried what acoles_away suggested about testing with insecure = true18:13
jlkI'm sure that'll work, but that's not a solution.18:13
claygjlk: did you test it - or you're just "sure"18:14
claygjlk: just curious - it's your time :P18:14
jlksure, I can test it.18:15
jlkbut I'm 99.9% it'll work18:15
jlkyeah that totally "works"18:15
claygok, well still - it would move the problem from "ssl doesn't work" to "ssl certificate verification doesn't work" - which seems a fair bit more specific18:15
claygjlk: nice!18:16
claygso - i wonder how it's loading the certificate - maybe a different ssl lib on this box that other services?18:16
claygmaybe from the commandline client you have to --secure to get the certificate validation to play?18:16
*** RackerShagz has quit IRC18:16
jlkI think the command line client, it's outside the venv, and gets to load the standard ca paths18:17
jlkbut that's what the cafile option for authtoken is supposed to fix18:17
notmynameI _really_ wish that LP bugs has some other categories for confirming or closing a reported bug18:17
notmynameeg https://bugs.launchpad.net/swift/+bug/63435818:17
openstackLaunchpad bug 634358 in OpenStack Object Storage (swift) "remote address ACLs" [Wishlist,Confirmed]18:17
*** acampbel11 has quit IRC18:18
*** acampbell has quit IRC18:18
*** acampbell has joined #openstack-swift18:18
*** acampbel11 has joined #openstack-swift18:18
*** Kr4zy has joined #openstack-swift18:19
*** marzif_ has quit IRC18:19
claygjlk: yeah idk custom certifcates have always confused me - you have to tell the ssllib to use them - and i'm not sure how the keystone middleware plumbs that - can you just install your cert on the box and then update the ca databases or whatever?  what distro is this on?18:19
*** marzif_ has joined #openstack-swift18:19
jlkit's on Ubuntu. We DO have our cert installed in /etc/ssl/certs/ca-certificates.crt18:20
jlkbut apparently python httplib / requests inside the venv isn't loading it18:20
*** RackerShagz has joined #openstack-swift18:21
claygjlk: so.... if you activate the venv and use the commandline client it reproduces the certificate failure?18:21
Kr4zyI am seeing slow replication speed for the object-replicator relative to other nodes in a Swift cluster. Anyone know the root cause for this?18:22
*** RackerShagz has quit IRC18:22
claygjlk: i'm just trying to understand why you think the venv has anything to do with it - i would think the ssl stuff punts to a shared library installed on the system somewhere18:22
jlkclayg: let me try that. I don't think we have the client installed inside the venv.18:22
claygjlk: if not you could create a new venv and install the same deps see if it's reproduceable there18:23
notmynamelove this conference. "so we've got 40TB of DRAM in this cluster...."18:23
*** annegentle has joined #openstack-swift18:23
jlkhrm, there is keystone in the venv18:24
jlkand it can get a catalog when called from the venv18:24
claygnotmyname: hrmm... http://yourdatafitsinram.com/ says that's not likly18:24
*** RackerShagz has joined #openstack-swift18:24
jlkclayg: I mention the venv because we've had similar problems before. python httplib ships its own ca certificate pile and loads it, rather than the system's.18:25
jlkbut I can't find that inside the venv18:25
notmynameclayg: well this is the "massive storage systems and technology" conference ;-)18:27
notmynamethese are the people that have been dealing with hundreds to thousands of PB for many years now18:27
claygjlk: weird, i've never run into that - well for one because stdlib doesn't normally *do* certificate validation - so idk18:27
pelusethat's a good conf BTW18:28
claygjlk: and with requests it's always seems to work if it works for curl - even if i use requests from w/i a venv it's still the same comipled shared object from openssl under the hood18:29
claygnotmyname: yeah, i was just joking around - my way of saying "that's a rather impressive amount of ram"18:29
notmynameheh :-)18:30
notmyname...another bug who's last activity was 3 years ago...18:30
claygnotmyname: but I guess it's really only a few hundered boxes with 128 GiB :D18:30
jlkwell, then I don't know why keystoneauth isn't able to find it18:30
jlkkeystone client from the venv can18:31
claygare you sure keystone client from the venv is *doing* certificate validation?  Can you move the custom ca out of the way and see if it still "works"18:31
jlkhrm.18:32
jlkI'll try, but there is no insecure setting in my stackrc. and with --debug I see it hitting the https spot.18:32
torgomaticjlk: strace the proxy to see where it's looking on the filesystem?18:32
*** david-lyle has joined #openstack-swift18:33
jlkhrm, client may not actually be doing the ssl verify :/18:35
Kr4zyI am seeing slow replication speed for the object-replicator relative to other nodes in a Swift cluster. Anyone know the root cause for this?18:37
Kr4zynotmyname: do you know?18:37
notmynameno18:37
notmynamedo you have a failed/failing drive on that box?18:38
claygjlk: so all of the connecting to keystone is handled by keystone's authtoken middleware - if you have other servcies that use it and are workig you might spend a few sorta checking for differences between those boxes and here?18:39
notmynamebah. laptop power is nearly gone.18:39
*** aix has quit IRC18:39
claygjlk: e.g. version of python packages in venvs, version of openssl libraries, md5 of ca, etc.18:40
notmynamebe back later when/if I can find power18:40
openstackgerritSamuel Merritt proposed openstack/swift: EC: support multiple ranges for GET requests  https://review.openstack.org/17349718:42
*** flaper87 has quit IRC18:44
*** nadeem has joined #openstack-swift18:45
swifterdarrellportante: just how high have you bumped workers (for object-server) and seen improvement?18:45
openstackgerritMerged openstack/python-swiftclient: Make default get_auth timeout be None  https://review.openstack.org/18774918:47
openstackgerritMerged openstack/swift: Fix testing issues  https://review.openstack.org/18775418:47
claygswifterdarrell: how high have *you* bumped workers for object-server!?  </spoiler-alert>18:49
ctennisnotmyname: I've hand patched your policy stuff into ssbench on these nodes, btu I'm getting errors with zmq.green import in worker.py not being found18:50
ctennisnotmyname: I assume there's a python lib change/requirement needed but I don't see it in the pull req18:51
*** silor has joined #openstack-swift18:53
*** mordred has quit IRC18:55
*** mordred has joined #openstack-swift18:55
*** silor1 has quit IRC18:55
*** marzif_ has quit IRC18:57
*** barra204 has joined #openstack-swift18:57
*** barra204 has quit IRC19:02
*** mjseger has joined #openstack-swift19:08
*** flaper87 has joined #openstack-swift19:08
*** flaper87 has quit IRC19:09
*** flaper87 has joined #openstack-swift19:09
mjsegerjenkins finally ran on https://review.openstack.org/#/c/187974/ and it's generating errors with19:16
mjsegergate-swift-python27 complaining about some modules associated with erasure code, not part of any of the code I patched19:16
mjsegeranyone have any clue how to track down the problem?  given that it took may hours for jenkins to run I'd like to fix whatever is causing the problem 1st try and and wondering what the possibility is of something else unrelated to my patch causing this and if I should just upload again?19:18
*** SkyRocknRoll has quit IRC19:20
tdasilvamjseger: I don't think those errors are related to your patch with the exception of this one: FAIL: test_print_obj_policy_name_mismatch (test.unit.cli.test_info.TestPrintObjFullMeta)19:26
tdasilvaI get the same failure on my saio19:26
mjsegertdasilva: thanks, I'll look more closely at that one, but I guess my issue is even if the others aren't my problem won't they prevent my patch from going forward?19:27
mjsegertdasilva: now I see the problem, I changed the text of an error message and the test didn't match. easy fix, but should I do that and re-upload?19:30
tdasilvamjseger: yes19:30
mjsegerthx19:30
*** RackerShagz has quit IRC19:31
*** RackerShagz has joined #openstack-swift19:31
pelusetdasilva, congrats man!19:31
tdasilvapeluse: thanks! :)19:31
pelusedid notmyname tell you about the monthly dues?19:32
tdasilvahe mentioned you take beer and he takes tequilla19:32
openstackgerritMark Seger proposed openstack/swift: Change usage help and Attention messages to warnings  https://review.openstack.org/18797419:32
pelusesounds good to me!19:33
tdasilvapeluse: lol...not sure about everyone else...19:33
mjsegerpeluse: did you see my question about swift-get-nodes and storage policies?19:33
peluseclayg works for whiskey19:34
tdasilvapeluse: oh yeah, i've heard that somewhere before19:34
pelusemjseger, I didn't.  I'm on a tiny screen and pretty tied up for the rest of the week - can you repeat real quick?19:34
mjsegersure - in swift-get-nodes it looks like it pulls the policy index from a ring named object-idx19:35
mjsegerbut my question is what if the ring is named foo-idx?  I don't think it's going to work, or am I missing somethign?19:35
pelusethe ring has to be named object-X where X is the index19:36
peluseor no -X for policy 0 of course19:36
mjsegerthats what I thought, but I had a very long discussion with acoles: beciase submitting the patch and he felt pretty strongly that there is no need for explicit ring names, they can be anything19:37
mjsegerI think if the naming really isn't a convention but more of a rule, tools like get-nodes should verify the container names match account/container/object and throw an error if they don't19:38
mjsegerthen again it may be too late19:38
peluseI know there's multiple places in the code where 'object' is expected - remember from adding policy support but acoles_away is generally correct so maybe something has changed19:38
mjsegerright19:38
mjsegerwhile I'm in the midst of the patch, I could see if somoene specifies an account container object and a ring named xxx-yyy to tell them it looks like a policy ring but must be named object-yyy to work19:39
mjsegermay be a longer discussion for another day especially if you need to run19:40
peluseyeah, it wouldn't be hard to check the code but yeah I'm off to a meeting...19:40
mjsegerI'm thinking this may be the case where the code had changed multiple times over multiple years and while there may once have been a reason for doing something that reason may have gone away and everyone if afraid (including me) to change anything19:41
portanteswifterdarrell: we run 2 object-servers per CPU on 24 core systems19:42
mjsegerit also begs the question that with all the scrutiny policies got, if nobody complained about explicitly naming the object ring object-policy,perhaps the name are more of a convention and should be a rule19:42
swifterdarrellportante: do you count HT cores in that?19:43
portanteI don't think I did at the time, I had HT turned off19:45
swifterdarrellportante: k, I'm seeing normal object-servers doing better all the way up to 3x disk count (in my case, I've got ~30 disks, ~12 cores not counting HT); significant improvement between workers=30 and workers=90, though workers=90 is still not quite as good as servers_per_port=3 (w/about 90 processes, 3 per disk)19:45
swifterdarrellportante: so you had 24 actual cores? like 4 sockets and 6 cores each?19:46
*** blmartin_ has quit IRC19:47
*** blmartin has quit IRC19:47
thurloatfun question: is there a way to make the rebalanced objects go faster? currently transferring across nodes at around ~50Mbps, have already uppped the rsync concurrency but that's no longer a bottleneck19:47
portanteswifterdarrell: what is the difference between the workers=90 and servers_per_port=3?19:48
swifterdarrellportante: still quantifying that (have one more workers=90 run to do to get two samples on that one)19:49
*** petertr7 is now known as petertr7_away19:49
swifterdarrellportante: I think it'll be single-digit percentage difference19:49
swifterdarrellportante: after this, I'll emulate a clobbered disk and normal object-auditor and expect to see the benefit of the I/O isolation kick in19:50
*** petertr7_away is now known as petertr719:50
portanteI would expect that with an normal distribution for objects across the set of disks that servers_per_port would beat the default always because a greedy object server accepting connections won't have as bad an effect for servers_per_port19:50
portanteswifterdarrell: are you lowering the greenthread count when using the higher object server counts?19:52
swifterdarrellportante: no; always the def. 102419:53
portantetry lowering it, it should help with the higher worker counts19:53
swifterdarrellportante: well, it's extremely time-expensive for each thing I check; not sure I'll get to new ideas not already in my plan ;)19:53
portante;)19:54
portantealways happy to heap more work on!19:54
clayg lol19:56
claygportante: what are you doing hanging about - we missed you!19:56
claygportante: you should come sabatocal on some swift stuff - ec is kind of interesting - we'll offer you a temporary-core-visa.19:56
claygs/what-ever-the-heck-that-was/sabbatical/g19:57
*** flaper87 has quit IRC19:57
portanteclayg: thanks, now that thiago is a core dev I can just delegate to him!19:58
portante;)19:58
*** barra204 has joined #openstack-swift19:58
*** flaper87 has joined #openstack-swift19:59
portanteand I have never left, just lurking. ;)20:00
*** RackerShagz has quit IRC20:02
*** barra204 has quit IRC20:03
*** flaper87 has quit IRC20:03
*** nadeem has quit IRC20:03
clayg:)20:08
*** thurloat is now known as thurloat_isgone20:10
*** Kr4zy has quit IRC20:16
*** flaper87 has joined #openstack-swift20:16
*** RackerShagz has joined #openstack-swift20:24
mattoliverauMorning all.. So we move the meeting, so I should be able to sleep in, but the wife needs to travel today so  up early #sleepfail20:28
*** acampbell has quit IRC20:33
*** acampbel11 has quit IRC20:33
mattoliverauOn the plus side, I've got a new version of best candidate sub trees algorithm (used in the container sharder) that can scan even a giant containers in one iteration while using minimal ram. (Well finished it last night, but scarily working in testing this morn)20:34
*** ho has joined #openstack-swift20:37
hoGood morning!20:38
swifterdarrellportante: haha, so what I'm hearing is that tdasilva can do your benchmarking for you!20:38
swifterdarrellportante: oh, one other thing, my current round of tests is 2hr runs, but the workload is "realistic" which also means "random variance", so there's a fair bit of noise in the measurements; OTOH, it's less synthetic20:39
swifterdarrellportante: I may do some more shorter GET/PUT-only runs, as well as use swift-bench to make sure ssbench isn't biasing or otherwise doing something stupid20:40
hoping briancline20:41
mattoliverauho: morning20:44
homattoliverau: morning!20:45
claygnotmyname reminds us "no meeting today!"20:52
*** kota_ has joined #openstack-swift20:52
kota_good morning20:53
zaitcevwhat, really no meeting?20:53
hurricanerix_clayg: thanks, i would have been sitting in there for a while wondering where everybody was.  =P20:53
zaitcevIt's the first time I remembered about the new time.20:53
claygho: mattoliverau: zaitcev: kota_: sorry!20:53
claygzaitcev: well let's do it then!20:54
* clayg is not it for agenda20:54
kota_no meeting?20:54
hoclayg: np!20:55
kota_oh, just finding at wiki20:55
mattoliverauAhh the agenda is dated for next week.. date recognition fail :P20:55
claygho: kota_: zaitcev: mattoliverau: so the issue is that notmyname couldn't make it and no one wanted to setup and cover for him because none of us really had anything we wanted to go over today20:56
mattoliverauclayg: fair enough.. too big shoes to fill anyway :)20:56
mattoliverauI might go a rage sleep then :P20:56
kota_clayg: I see, no problem20:57
clayg:)  still - GOOD MORNING!20:57
kota_mattoliverau: +1!20:57
clayglol20:57
mattoliverauLike rage sleep == rage quit, but really means simply going back to bed :P20:57
claygperfect20:57
mattoliverauclayg: oh and good morning clayg :)20:57
claygfrom what i understand we should be back to normal next week - so - GOOD NIGHT!20:58
*** nadeem has joined #openstack-swift20:59
kota_ok, have a good day :)20:59
*** kota_ has quit IRC20:59
mattoliveraucools, no stress :)21:00
*** silor has quit IRC21:01
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925021:01
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873621:01
*** bsdkurt has quit IRC21:01
*** bsdkurt has joined #openstack-swift21:03
*** annegentle has quit IRC21:06
*** samueldmq has quit IRC21:06
*** petertr7 is now known as petertr7_away21:09
portanteswifterdarrell: sorry, back21:12
portanteswifterdarrell: so ... can't resist, one more thing to consider ... we saw small requests starve out large requests21:13
claygyay nova thread from garbutt about going semver - and infra's all like "on the plus side we already support this because Swift"21:13
clayg"Swift doing it right until you catch up"21:13
portantebasically, 5 clients, one at 10 K, one pulling 100K, one pull 1 M, one pulling 10 M, one pull 100M, the 10M and 100M go "slow" until the 10 K clients clear out21:14
portanteso I would expect to NOT see that behavior with servers_per_port, because you have enough object servers to cover the cases (assuming small and large requests don't land on the same disk)21:15
portanteusing normal object servers, we eliminated that effect by raising work count and lowering greenlets to 1 (maxclients, I believe)21:16
portantethe graphs were published a while, I can dig them up if you'd like21:17
*** RackerShagz has quit IRC21:24
*** mwheckmann has quit IRC21:25
*** bsdkurt has quit IRC21:35
*** bsdkurt has joined #openstack-swift21:37
*** dontalton has joined #openstack-swift21:38
*** mmcardle has joined #openstack-swift21:41
*** fthiagogv has quit IRC21:45
*** mmcardle has quit IRC21:52
*** nadeem has quit IRC21:53
*** nadeem has joined #openstack-swift21:54
*** jkugel has quit IRC21:54
*** thurloat_isgone is now known as thurloat22:05
*** nadeem has quit IRC22:19
*** jamielennox|away is now known as jamielennox22:20
*** bill_az has joined #openstack-swift22:23
swifterdarrellportante: interesting22:29
swifterdarrellportante: I don't have time to mess with too much characterization atm; I'm mostly after A) not worse; and B) demonstrably better when 1 or 2 of your disks really suck22:30
swifterdarrellportante: I'm pretty happy with A so far; and I'm about to target B22:30
swifterdarrellportante: for these 2 hr runs, between initial file setup, the run itself, deletion, and letting object replication catch up, I get maybe 1 run every 4 hrs or so22:31
swifterdarrellportante: in the last 32 hours, I will gotten nearly 6 runs (the evenness of the results in that period says something about my sleep schedule and prioritization of this work); so that's ~5.3 hrs per run22:34
*** minwoob has quit IRC22:35
*** bsdkurt has quit IRC22:40
*** bsdkurt has joined #openstack-swift22:41
*** barra204 has joined #openstack-swift22:48
*** barra204 has quit IRC22:53
*** wbhuber has quit IRC22:57
*** km has joined #openstack-swift23:01
*** blmartin has joined #openstack-swift23:04
*** blmartin_ has joined #openstack-swift23:04
*** jrichli has quit IRC23:08
*** kei_yama has joined #openstack-swift23:11
*** chlong has joined #openstack-swift23:19
*** thurloat is now known as thurloat_isgone23:22
MooingLemurclayg: were you able to backread to yesterday, etc?23:31
*** dontalton has quit IRC23:37
*** asettle has quit IRC23:38
*** tellesnobrega has quit IRC23:40
*** wbhuber has joined #openstack-swift23:43
*** asettle has joined #openstack-swift23:45

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