Friday, 2015-09-25

*** sayali has joined #openstack-swift00:00
*** thumpba_ has quit IRC00:09
*** jrichli has quit IRC00:11
*** agomez has joined #openstack-swift00:21
*** chlong has quit IRC00:25
*** lyrrad has quit IRC00:28
*** hezhiqiang has joined #openstack-swift00:32
*** alejandrito has joined #openstack-swift00:32
* csmart growls at tonyb00:34
csmarthas another coffee with mattoliverau00:35
*** minwoob has quit IRC00:38
*** peluse has quit IRC00:45
*** peluse has joined #openstack-swift00:46
*** haomaiwang has joined #openstack-swift00:49
tonybcsmart: Good to know.00:54
tonybcsmart: You know I'm avoiding you right ?00:54
tonybcsmart: Also ask Matt if he wants to have lunch at the duxton with a few locals00:54
tonybcsmart: a lift can be arranged.00:54
*** peluse has quit IRC00:54
mattoliverautonyb sure sounds awesome :)00:57
openstackgerritJohn Dickinson proposed openstack/swift: Fix missing container update  https://review.openstack.org/18673500:57
*** haomaiwang has quit IRC01:01
*** david-lyle has quit IRC01:01
*** haomaiwang has joined #openstack-swift01:01
*** alejandrito has quit IRC01:01
hugokuonotmyname: sloslo : https://www.fuel-infra.org/plugins/catalog.html   Fuel doesn't have it so SwiftStack wrote a new plugin in Fuel for this purpose.01:02
*** hezhiqiang has quit IRC01:03
hugokuoThis should be only for SwiftStack user in general. But this version is open for any Swift cluster. Next version of this plugin will be only for SwiftStack since it needs SwiftStack's feature to auto deploy Swift cluster. You can have a look at the current version.01:03
hugokuobtw, it's in the buttom01:04
*** haomaiwang has quit IRC01:08
*** gyee has quit IRC01:24
*** chlong has joined #openstack-swift01:27
*** agomez has quit IRC01:33
*** peluse has joined #openstack-swift01:52
*** peluse has quit IRC01:54
*** peluse has joined #openstack-swift01:54
*** haomaiwa_ has joined #openstack-swift02:00
*** haomaiwa_ has quit IRC02:01
*** haomaiwa_ has joined #openstack-swift02:01
*** hezhiqiang has joined #openstack-swift02:02
*** agomez has joined #openstack-swift02:33
*** haomaiwa_ has quit IRC02:35
*** haomaiwang has joined #openstack-swift02:36
*** jrichli has joined #openstack-swift02:38
*** sanchitmalhotra has joined #openstack-swift02:39
*** wbhuber_ has quit IRC02:47
*** miurahr has joined #openstack-swift02:49
*** sanchitmalhotra1 has joined #openstack-swift02:53
*** darrenc is now known as darrenc_afk02:54
*** sanchitmalhotra has quit IRC02:55
*** haomaiwang has quit IRC03:01
*** haomaiwang has joined #openstack-swift03:01
*** sloslo has quit IRC03:04
*** darrenc_afk is now known as darrenc03:12
*** kota_ has joined #openstack-swift03:39
*** ChanServ sets mode: +v kota_03:39
kota_hello03:39
hugokuoおはよう03:40
kota_hugokuo: awesome!03:40
*** agomez has quit IRC03:49
notmynamekota_: good morning03:50
kota_notmyname: good evening03:50
kota_notmyname: Did you update my patch ... just rebased?03:50
notmynamekota_: torgomatic and I took a look at https://review.openstack.org/#/c/186735/ today. I pushed up a version over yours03:50
kota_yup03:51
notmynamemore than rebases (it didn't need that). we fixed some tests03:51
kota_notmyname: great, thanks03:51
notmynametuens out the tests were only accidentally passing03:51
notmyname*turns03:51
notmynamebut now they are better03:51
kota_sounds good.03:52
kota_I'll take a look at that today and will make a comment for the change.03:53
kota_notmyname: thanks for working that.03:53
notmynamegreat03:53
notmynamekota_: most of the changes we did are in https://review.openstack.org/#/c/186735/12..13/test/unit/proxy/controllers/test_obj.py03:53
kota_notmyname: yeah, that's what I am seeing.03:54
notmynamekota_: the root of the changes are with line 933 in the new patch on that file03:55
notmynamebasically, we had to make sure that each test gets a *new* ring instead of just using the same one over and over for each test03:55
notmynamesome of the tests change the ring inside the test, unfortunately03:55
notmynameso that was happening and setting the replica count to 4 in one test and then the tests you wrote accidentally passed. 4 replicas worked, 1 replica didn't03:56
notmynamemost of the other changes are to get the tests working with a 1 replica ring03:56
kota_I see.03:57
kota_that makes me sense.03:57
kota_thanks, the information makes me easy to review.03:58
notmynameI think there could be some long-term improvements in that test file. eg to make sure more tests loop over every policy. and adding different policies to be tested (partial replicas, ec, etc). definitely some improvements in how FakeRing works03:58
kota_yup03:59
kota_oh, yeah, that affected my tests.03:59
notmynameplease feel free to push over any improvements to what we did04:00
*** haomaiwang has quit IRC04:01
*** haomaiwang has joined #openstack-swift04:01
kota_notmyname: ok, I may do so if needed ;)04:01
* notmyname calls it a night04:04
kota_notmyname: have a good night ;)04:05
*** hrou has quit IRC04:07
mattoliveraunotmyname: night o/04:08
*** sanchitmalhotra has joined #openstack-swift04:13
*** sanchitmalhotra1 has quit IRC04:15
*** peluse has quit IRC04:25
*** peluse has joined #openstack-swift04:26
*** kei_yama has quit IRC04:31
*** kei_yama has joined #openstack-swift04:32
*** garthb has joined #openstack-swift04:34
*** peluse has quit IRC04:35
*** bill_az has quit IRC04:40
*** sanchitmalhotra1 has joined #openstack-swift04:54
*** sanchitmalhotra has quit IRC04:56
*** haomaiwang has quit IRC05:01
*** haomaiwang has joined #openstack-swift05:01
*** sanchitmalhotra has joined #openstack-swift05:12
*** sanchitmalhotra1 has quit IRC05:14
*** SkyRocknRoll has joined #openstack-swift05:17
*** trifon has joined #openstack-swift05:18
*** peluse has joined #openstack-swift05:32
*** proteusguy__ has quit IRC05:33
*** peluse has quit IRC05:39
*** mfalatic has quit IRC05:47
*** garthb has quit IRC05:48
jst_hugokuo: thx for info. are you there?06:00
hugokuojst_: yup06:00
jst_regarding fuel plugin for swift06:00
*** haomaiwang has quit IRC06:01
jst_does fuel plugin than enable all the configuration for swift (replicas, weights etc), but just with swiftstack distribution of swift?06:01
*** openstackgerrit has quit IRC06:01
jst_or is it general purpose plugin?06:01
*** haomaiwang has joined #openstack-swift06:01
*** openstackgerrit has joined #openstack-swift06:01
hugokuojst_: The plugin requires a pre-deployed Swift cluster. It simple handles configurations for Glance and Keystone in Fuel06:02
hugokuojst_: So it's not provide entry for managing your Swift cluster06:02
hugokuoYou need to manage your swift cluster by your own. For SwiftStack customer, they manage the cluster via SwiftStack software as an out-of-box of Fuel.06:03
jst_so let's say i install openstack (nova, identity, neutron) with Mirantis Fuel. And than after the installation i install by hand Swift with configuration  i want.. after swift cluster deployes, i have some managing options than within Fuel with this plugin06:04
jst_so storage policies and ring configuration should be deployed in advance, without fuel.06:06
jst_ok. i found document: http://plugins.mirantis.com/docs/s/w/swiftstack/swiftstack-0.1.0.pdf06:07
hugokuojst_: base on the purpose of this plugin it's opposite. And I do recommend you to deploy Swift before constructing Fuel OpenStack environment. b/c Fuel runs check tests after deploy the entirement. It uploads a test image via Glance for testing by NOVA06:07
hugokuojst_: yes. all Swift wise setting should be separated from fuel06:08
hugokuoFuel doesn't handle too much Swift stuff tho06:08
hugokuoAnd ... Fuel restrict user from changing many settings once the environment been deployed.06:09
*** mac_ified has quit IRC06:11
*** jamielennox is now known as jamielennox|away06:12
jst_hugokuo: ok thank you for the information provided06:13
hugokuoFor the case to associate a Swift cluster to existing Fuel environment must be done manually since the limit in Fuel. You need to 1) add new endpoint for object-store in Keystone 2) change the setting of Swift section in glance-api which includes several options 3) restart glance  4) upload VM images06:13
hugokuojst_: my pleasure06:13
*** haomaiwang has quit IRC06:18
*** haomaiwa_ has joined #openstack-swift06:18
*** sanchitmalhotra1 has joined #openstack-swift06:32
*** sanchitmalhotra has quit IRC06:34
*** peluse has joined #openstack-swift06:36
*** peluse has quit IRC06:45
*** sayali has quit IRC07:00
*** briancline has quit IRC07:00
*** geaaru has joined #openstack-swift07:00
*** haomaiwa_ has quit IRC07:01
*** haomaiwang has joined #openstack-swift07:01
*** rledisez has joined #openstack-swift07:09
*** sayali has joined #openstack-swift07:14
*** ntt has quit IRC07:26
*** peluse has joined #openstack-swift07:42
*** peluse has quit IRC07:49
*** haomaiwang has quit IRC08:01
*** haomaiwang has joined #openstack-swift08:01
openstackgerritKota Tsuyuzaki proposed openstack/swift: Fix missing container update  https://review.openstack.org/18673508:02
*** jordanP has joined #openstack-swift08:03
*** acoles_ is now known as acoles08:05
acolesgood morning08:09
kota_good morning :)08:09
acoleshi kota_08:10
*** mahatic has joined #openstack-swift08:10
*** akle has joined #openstack-swift08:11
*** haomaiwang has quit IRC08:12
acolesho: hi! i tried to add you to a review on gerrit and got an error saying you were not registered.08:13
acolesho: i have no idea why that happened08:13
acolesho: got me worried that you had gone away :/ but then i saw your review comments today, phew! ho is still with us :)08:15
*** openstackgerrit has quit IRC08:16
*** openstackgerrit has joined #openstack-swift08:16
acoleskota_: its still 4 weeks away but i am excited about coming to tokyo :)08:17
*** ktsuyuzaki has joined #openstack-swift08:17
*** KLuka_ has joined #openstack-swift08:18
*** sayali has quit IRC08:19
*** kota_ has quit IRC08:19
*** sayali has joined #openstack-swift08:19
*** haomaiwang has joined #openstack-swift08:22
*** haomaiwang has quit IRC08:23
*** haomaiwang has joined #openstack-swift08:23
*** kei_yama has quit IRC08:25
*** kei_yama has joined #openstack-swift08:25
cschwedeacoles: Good Morning! I have a question regarding http://paste.openstack.org/raw/473886/08:31
cschwedeacoles: i might need more coffee, but what logic is changed there? at the end it returns with req.environ['swift_owner'] set to True before and after applying that patch08:32
acolescschwede: hello!08:32
cschwedeacoles: argh, nevermind, got it. it’s a difference if req.environ['swift_owner'] was set before08:33
hoacoles: hahaha, i'm very busy now and restricted access to irc but i can read email so i could see donagh's patch. :-)08:33
acolescschwede: before it would return None if swift_owner was already True in the env08:33
acolescschwede: yes, that!)08:34
cschwedeacoles: yep, just realized this :)08:34
acolescschwede: now, what i did not do in that patch is clear swift_owner from env if allowed=False08:34
acolescschwede: i dodged that decision ;)08:35
*** Alvin_ has joined #openstack-swift08:36
acolesho: great, hope all is wel08:36
acoleswell08:36
*** Alvin_ has left #openstack-swift08:36
acolescschwede: so, i'm sure you figured this, but the root of the problem was the original COPY having account AUTH_xxx and that being authorised so swift_owner was True when the actual PUT request called back08:39
hoacoles: thanks!08:39
cschwedeacoles: yep, saw that. but then i was also assuming acls would be required too, thus my patch. but i’m removing that, only adding your patch, a small doc update to tempauth (because tempauth seems to be fine), and adding you, Donagh and Hisashi as Co-author08:40
cschwedejust need to finish my tests with it08:40
*** Alvin_ has joined #openstack-swift08:41
acolescschwede: great work, thanks for taking that on08:41
acolescschwede: are you planning to squash donagh's test into your review?08:44
acolesthat would make sense08:44
cschwedeacoles: well, if Donagh is ok with that - sure08:44
acolesdonagh: are you here? ^^08:44
donagh_acoles: yes08:45
acolesdonagh_:u ok with cschwede squashing your test into his review?08:45
*** peluse has joined #openstack-swift08:47
*** donagh_ has quit IRC08:49
*** donagh_ has joined #openstack-swift08:50
*** SkyRocknRoll_ has joined #openstack-swift08:52
*** KLuka_ has quit IRC08:52
*** peluse has quit IRC08:54
*** haomaiwang has quit IRC09:01
*** haomaiwang has joined #openstack-swift09:01
openstackgerritChristian Schwede proposed openstack/swift: Fix copy requests to service accounts in Keystone  https://review.openstack.org/22713309:07
donagh_cschwede: re-reviewing my functional test path, I see something odd. I put a comment in that patch (just in case you hit the problem I thought might occur). I'll debug it a bit more09:11
*** Alvin_ has quit IRC09:13
*** Alvin_ has joined #openstack-swift09:13
openstackgerritChristian Schwede proposed openstack/swift: Fix copy requests to service accounts in Keystone  https://review.openstack.org/22713309:16
*** portante has quit IRC09:20
*** Alvin_ has quit IRC09:22
*** Alvin_ has joined #openstack-swift09:22
cschwededonagh_: alright; meanwhile i just added a very minor change to the existing unit tests, and this change fails on master and passes with the patch: https://review.openstack.org/#/c/227133/6/test/unit/common/middleware/test_keystoneauth.py09:24
cschwededoing this there should be no regression in the future (that’s what i hope for ;))09:25
*** Alvin_ has quit IRC09:25
*** alvin_nathan has joined #openstack-swift09:25
*** portante has joined #openstack-swift09:34
*** ktsuyuzaki has quit IRC09:37
*** kota_ has joined #openstack-swift09:37
*** ChanServ sets mode: +v kota_09:37
*** proteusguy has joined #openstack-swift09:45
hoacoles: cschwede: donagh: i tested patch 227133 and passed so your code works. now i have one concern about swit_owner in env. i think it is better to remove in case of delay_denial to prevent further troubles. what do you think?09:47
patchbotho: https://review.openstack.org/#/c/227133/ - Fix copy requests to service accounts in Keystone09:47
cschwedeho: thx for testing! yeah, Alistair mentioned that and i was thinking about it too09:48
*** silor has joined #openstack-swift09:50
*** peluse has joined #openstack-swift09:51
hocschwede: sounds great!09:53
*** peluse has quit IRC10:00
*** haomaiwang has quit IRC10:01
*** haomaiwang has joined #openstack-swift10:01
*** SkyRocknRoll_ has quit IRC10:05
*** hezhiqiang has quit IRC10:06
donagh_ho: schwede: thinking about clearing swift_owner in the delay_denial ... I think we *must* do so. It's not just a nice to have.10:06
donagh_Consider:10:06
donagh_if ACL grants write access in destination-account, you also have swift_owner at the point...you should only have write access10:08
donagh_Since copy is for objects that does not matter right now (I think), but if there is ever some object metadata that can only be set by swift_owner, than we've allowed a write ACL to set that metadata10:09
*** briancline has joined #openstack-swift10:15
*** akle|2 has joined #openstack-swift10:18
*** SkyRocknRoll_ has joined #openstack-swift10:20
*** briancline has quit IRC10:22
*** akle has quit IRC10:22
openstackgerritChristian Schwede proposed openstack/swift: Fix copy requests to service accounts in Keystone  https://review.openstack.org/22713310:33
openstackgerritDonagh McCabe proposed openstack/swift: Add func tests for COPY and service tokens  https://review.openstack.org/22742110:44
*** silor has quit IRC10:44
*** silor has joined #openstack-swift10:50
*** briancline has joined #openstack-swift10:54
*** peluse has joined #openstack-swift10:57
*** silor has quit IRC10:59
*** silor has joined #openstack-swift11:00
*** briancline has quit IRC11:00
*** haomaiwang has quit IRC11:01
*** haomaiwang has joined #openstack-swift11:01
*** peluse has quit IRC11:04
*** silor1 has joined #openstack-swift11:04
*** silor has quit IRC11:05
*** silor1 is now known as silor11:05
*** cdelatte has joined #openstack-swift11:28
*** delattec has joined #openstack-swift11:28
*** sanchitmalhotra1 has quit IRC11:37
*** haomaiwang has quit IRC12:01
*** haomaiwang has joined #openstack-swift12:01
*** peluse has joined #openstack-swift12:01
*** SkyRocknRoll_ has quit IRC12:02
*** peluse has quit IRC12:09
*** hezhiqiang has joined #openstack-swift12:10
*** miurahr has quit IRC12:11
*** alejandrito has joined #openstack-swift12:13
*** annegentle has joined #openstack-swift12:22
*** NM has joined #openstack-swift12:31
*** alejandrito has quit IRC12:36
*** CaioBrentano has quit IRC12:37
*** alejandrito has joined #openstack-swift12:38
*** CaioBrentano has joined #openstack-swift12:38
*** haomaiwang has quit IRC12:41
*** chlong has quit IRC12:57
*** kota_ has quit IRC12:58
*** km has quit IRC13:02
*** hrou has joined #openstack-swift13:04
*** peluse has joined #openstack-swift13:06
*** janonymous_ has joined #openstack-swift13:07
*** bill_az has joined #openstack-swift13:09
*** jkugel has joined #openstack-swift13:11
*** dustins has joined #openstack-swift13:11
*** peluse has quit IRC13:14
*** peluse has joined #openstack-swift13:14
*** km has joined #openstack-swift13:15
*** km has quit IRC13:15
*** wbhuber has joined #openstack-swift13:28
*** esker has quit IRC13:30
*** kei_yama has quit IRC13:34
*** pberis has joined #openstack-swift13:42
openstackgerritjanonymous proposed openstack/swift: Eventlet green threads not released back to pool  https://review.openstack.org/22785513:48
janonymous_please review +2 ones if possible to avoid rebasing all the patches : https://review.openstack.org/#/q/owner:%22janonymous+%253Cjaivish.kothari%2540nectechnologies.in%253E%22+status:open,n,z13:49
*** annegentle has quit IRC13:53
*** annegentle has joined #openstack-swift13:54
*** marzif has joined #openstack-swift14:04
*** chsc has joined #openstack-swift14:09
*** esker has joined #openstack-swift14:11
*** esker has quit IRC14:11
*** janonymous_ has quit IRC14:12
*** esker has joined #openstack-swift14:12
*** peluse has quit IRC14:14
*** peluse has joined #openstack-swift14:15
*** delatte has joined #openstack-swift14:19
*** delattec has quit IRC14:21
*** marzif has quit IRC14:22
*** cdelatte has quit IRC14:22
*** marzif has joined #openstack-swift14:22
*** david-lyle has joined #openstack-swift14:23
*** jlhinson has joined #openstack-swift14:24
*** peluse has quit IRC14:24
*** akle|2 has quit IRC14:32
*** david-lyle has quit IRC14:35
*** peluse has joined #openstack-swift14:38
*** annegentle has quit IRC14:46
*** thumpba has joined #openstack-swift14:47
*** esker has quit IRC14:48
*** trifon has quit IRC14:50
*** ccavanna has joined #openstack-swift14:52
*** hezhiqiang has quit IRC14:53
*** garthb has joined #openstack-swift14:55
*** peluse has quit IRC14:58
*** marzif has quit IRC14:58
*** peluse has joined #openstack-swift14:59
*** david-lyle has joined #openstack-swift15:02
*** agomez has joined #openstack-swift15:07
*** peluse has quit IRC15:07
*** agomez has quit IRC15:07
*** jkugel1 has joined #openstack-swift15:08
*** jkugel has quit IRC15:08
*** marzif has joined #openstack-swift15:09
*** peluse has joined #openstack-swift15:10
*** david-lyle has quit IRC15:18
*** david-lyle has joined #openstack-swift15:20
*** annegentle has joined #openstack-swift15:29
*** david-lyle has quit IRC15:34
*** peluse_ has joined #openstack-swift15:35
*** peluse has quit IRC15:36
*** peluse has joined #openstack-swift15:37
*** peluse has quit IRC15:37
*** peluse has joined #openstack-swift15:43
*** peluse___ has joined #openstack-swift15:43
*** peluse__ has joined #openstack-swift15:43
*** peluse__ has quit IRC15:43
*** peluse has quit IRC15:43
*** david-lyle has joined #openstack-swift15:44
*** peluse has joined #openstack-swift15:44
*** peluse__ has joined #openstack-swift15:44
*** peluse has quit IRC15:45
*** peluse__ has quit IRC15:45
peluse_hello me15:47
*** delatte has quit IRC15:47
*** delatte has joined #openstack-swift15:47
*** peluse2 has quit IRC15:47
*** Alvin_nathan_ has joined #openstack-swift15:48
*** david-lyle has quit IRC15:48
*** peluse_ is now known as peluse15:48
*** ChanServ sets mode: +v peluse15:49
*** alvin_nathan has quit IRC15:51
*** gyee has joined #openstack-swift15:51
*** janonymous_ has joined #openstack-swift15:53
*** SkyRocknRoll has quit IRC15:54
*** dustins is now known as dustins|afk15:54
*** minwoob has joined #openstack-swift15:56
*** annegentle has quit IRC16:03
*** lyrrad has joined #openstack-swift16:05
*** bill_az has quit IRC16:07
*** marzif has quit IRC16:10
*** marzif has joined #openstack-swift16:10
*** annegentle has joined #openstack-swift16:11
*** haomaiwang has joined #openstack-swift16:20
*** rledisez has quit IRC16:29
*** mfalatic has joined #openstack-swift16:31
*** haomaiwang has quit IRC16:32
*** haomaiwa_ has joined #openstack-swift16:33
*** bill_az has joined #openstack-swift16:39
*** cdelatte has joined #openstack-swift16:39
*** NM has quit IRC16:39
*** delatte has quit IRC16:41
*** thumpba has quit IRC16:41
*** delattec has joined #openstack-swift16:44
*** cdelatte has quit IRC16:45
*** NM has joined #openstack-swift16:48
*** esker has joined #openstack-swift16:49
*** janonymous_ has quit IRC16:49
*** esker has quit IRC16:49
*** esker has joined #openstack-swift16:50
*** vinsh has joined #openstack-swift16:53
notmynamegood morning16:57
mahaticwow it's so quiet!16:57
*** garthb has quit IRC16:57
mahaticnotmyname: morning!16:57
pelusemust be friday :)16:58
notmynamehave of the world is already on the weekend16:58
notmyname(including you mahatic ;-)16:58
peluseat intel we don't get saturday's off...16:58
peluseonly every other sunday :)16:59
mahaticnotmyname: yeah, I'm kinda on the weekend - weekend begins with responding to pending emails :P16:59
notmynameheh16:59
mahaticactually it's a holiday here today16:59
pelusemahatic: you know i'm kidding right.... you should go do something funner than email!16:59
* peluse on the commute...17:00
mahaticpeluse: I *just* got to emails. Outreachy stuff. Will be off again17:00
*** thumpba has joined #openstack-swift17:00
*** haomaiwa_ has quit IRC17:01
*** thumpba has quit IRC17:01
*** thumpba has joined #openstack-swift17:01
*** marzif has quit IRC17:01
*** esker has quit IRC17:01
*** haomaiwa_ has joined #openstack-swift17:01
acolesoh yeah its the weekend17:05
*** marzif has joined #openstack-swift17:07
*** nickchase has joined #openstack-swift17:11
*** zhill has joined #openstack-swift17:14
*** klrmn1 has joined #openstack-swift17:16
*** haomaiwa_ has quit IRC17:16
notmynamewe've got a release coming up. you didn't expect to stop working this weekend, did you? ;-)17:21
acolesno sir17:23
jrichlilol17:24
notmynameI'd just like to point out that the truly important issues are being discussed on the mailing list: what's the allowed limit for git commit messages17:25
acolesnotmyname: actually, let me know the answer because i might be about to violate that17:26
notmynameacoles: someone was complaining that 72 chars is the limit. so I'm guessing that's what it is. also, if someone doesn't like your commit message, they can easily edit it in the gerrit UI. there's even a dedicated button just for that17:27
acolesnotmyname: oh line length. i thought you meant number o flines17:27
notmynameof course line length. what could possibly be more important than that?! ;-)17:28
*** silor1 has joined #openstack-swift17:30
*** silor has quit IRC17:33
*** silor1 is now known as silor17:33
*** dustins|afk is now known as dustins17:41
*** mahatic has quit IRC17:53
*** proteusguy_ has joined #openstack-swift17:58
*** proteusguy has quit IRC18:00
*** agomez has joined #openstack-swift18:00
*** annegentle has quit IRC18:08
*** geaaru has quit IRC18:09
*** pberis has quit IRC18:10
*** trifon has joined #openstack-swift18:18
*** annegentle has joined #openstack-swift18:19
CaioBrentanoHi!18:21
*** silor1 has joined #openstack-swift18:21
CaioBrentano"The erasure code support in Swift is considered “beta” at this point. Most major functionality is included, but it has not been tested or validated at large scale."18:22
CaioBrentanoIs there any release date for production? :-)18:23
*** marzif has quit IRC18:24
*** silor has quit IRC18:24
torgomatic"when it's ready" :)18:25
*** silor1 has quit IRC18:25
CaioBrentanoso there is no "official goal" for this feature?18:30
torgomaticin terms of dates? not that I've heard of18:32
torgomaticI mean, the alternative is that we wait for some OpenStack release and then say "it's production-ready because time has passed!" and people use it and it eats their data18:32
notmynameCaioBrentano: the "production readiness" of EC in swift, in my mind, is the point at which we are treating it like replication: there's always improvements, but there aren't bit outstanding known issues that have data corruption or loss as side-effects18:33
CaioBrentanothanks torgomatic and notmyname18:34
notmynameas of right now, we're working towards finishing the known big EC issues, but certainly not all EC issues, by the end of next week for the liberty openstack release18:34
*** marcusvrn_ has quit IRC18:35
notmynamewe've got a lot to do in the next 7 days :-/18:35
CaioBrentanoI'm asking because we are having some "vendors invites" to test their Object Storage solution, and most of them mentions EC as an advantage compared to Swift18:38
notmynameyeah, I've seen some of that too18:40
*** zhill has quit IRC18:40
*** marzif has joined #openstack-swift18:40
*** zhill has joined #openstack-swift18:40
* notmyname thinks some storage vendors will be in a tight place if their only competitive advantage goes away when swift adds a feature18:41
minwoobacoles: are you there?18:42
*** alejandrito has quit IRC18:42
acolesminwoob: yes18:42
minwoobacoles: So first, I think 'cp -a' will copy over the xattrs -- writing the helper method is easy for this, but I haven't thought of how to write the tests for it yet.18:43
minwoobacoles: And also, regarding test_GET_wih_missing_and_range_unsatisfiable18:43
minwoobacoles: Could you explain why you've defined get_response inside that test? It seems that the get_response method that you want is the one associated with req, the swob.Request object.18:44
*** esker has joined #openstack-swift18:44
minwoobacoles: When I did it that way, I started getting 503's.18:45
minwoobWhich seems to be going in the right direction.18:46
*** tsubic has quit IRC18:47
*** dmsimard is now known as dmsimard|afk18:47
*** esker has quit IRC18:47
acolesminwoob: the get_response i=method is passed to capture_http_requests, which uses it to fake out responses to requests. The same pattern is used in a lot of the tests in that class. There is no real object server for those test Requests to talk to.18:48
*** esker has joined #openstack-swift18:48
acolesre testing the copy function, there are a lot of tests in test_diskfile that create a diskfile, if you look there you'll find some clues to make two valid diskfiles in tow dirs, then try to copy the data file between the dirs with your copy function, and check you can open the diskfile18:49
*** ctennis has quit IRC18:49
*** ctennis has joined #openstack-swift18:50
minwoobacoles: Such a copy_xattrs_too() function would also need to verify that the xattrs have been preserved though, right?18:50
minwoobThe test* for it, I mean.18:51
*** jordanP has quit IRC18:51
acolesminwoob: the diskfile will not open if the xattrs have gone missing, as in using DiskFile.open(), because the xattrs have all the metadata that DiskFile looks for when opening a diskfile18:52
minwoobacoles: Okay, just verifying.18:52
acolesminwoob: You could also try it with the kind of tests where I'd like to use it, similar to test.unit.proxy.test_server.TestECMismatchedFA#test_GET_with_missing_durables, but with a nodes_to_copy parameter.18:52
*** _hrou_ has joined #openstack-swift18:53
*** ujjain has quit IRC18:53
*** ujjain- has joined #openstack-swift18:53
*** ujjain has joined #openstack-swift18:53
*** ujjain has joined #openstack-swift18:53
*** hrou has quit IRC18:55
*** annegentle has quit IRC18:55
acolesminwoob: i gotta leave - good luck and thanks for working on it!19:03
minwoobacoles: Sure, np. Thanks for the info.19:04
openstackgerritAlistair Coles proposed openstack/swift: Enable object server to return non-durable data  https://review.openstack.org/21527619:06
acolespeluse: kota ^^ with claygs new idea for frag preferences. peluse could you check i have the right bug numbers in commit message19:07
acoleswhuber: minwoob fyi ^^ could be worth reviewing this version, although i'm sure there's plenty of scope to improve19:08
acoleswbhuber: ^^19:08
acolesclayg: if you have little time please just read the commit message and tell if i am totally out of whack19:08
acolesgood night19:09
*** acoles is now known as acoles_19:09
*** annegentle has joined #openstack-swift19:18
wbhuberacoles: thx for the pointer.  will have the time to review your version.19:24
wbhuberpeluse: based on your ppt sent earlier this week, is setting the segment size to 640kb instead of 1mb the sweet spot for EC to handle objects larger than the size?19:24
wbhuberpeluse: does specifying a particular EC scheme (i.e. 10+4) weigh the decision in tuning the segment size to 640kb or 1mb?19:25
*** pberis has joined #openstack-swift19:33
*** esker has quit IRC19:36
*** esker has joined #openstack-swift19:37
*** esker has quit IRC19:37
*** thumpba has quit IRC19:44
*** jlhinson_ has joined #openstack-swift19:49
*** jlhinson has quit IRC19:52
*** trifon has quit IRC19:52
*** nickchase has left #openstack-swift20:00
pelusewbhuber: the 640K was based on 10:14 and a proxy chunk size of 64K (64K * 10).  I would presume but haven't tested that yeah if you used a different EC ratio and/or different proxy chunk size you could do better by adjusting segment size20:00
pelusewbhuber: well, not totally true.  I did try with 1MB segment and 10:14 and showed it was slightly less performance than 640K20:01
peluseacoles_: yeah, will check20:01
*** trifon has joined #openstack-swift20:07
wbhuberpeluse: does that also indicate when tuning EC ratio to say 4+2 - we'd use proxy chunk size of 160k (160k *4)?  that would be an interesting experiment test20:07
*** albertom has quit IRC20:07
pelusewbhuber: I don't know that I'd go changing proxy chunk size as a first step, I'd probably adjust segment size (the new parm) and see how that works.  So if default chunk is 64K and you have 4+2 I'd set segment to 64K * 4 and see how that works20:09
*** marzif has quit IRC20:09
*** alejandrito has joined #openstack-swift20:11
minwoobwbhuber: You wanted to know how the segment size is related to the threshold at which we should tier between EC and replication based on object size, correct?20:11
*** breitz has quit IRC20:11
*** breitz has joined #openstack-swift20:12
minwoobpeluse: Do you have some input on that?20:12
wbhuberminwoob: yeah, i was thinking if we are talking segment size = threshold and 640k is the sweet spot for at least EC scheme of 10:14 - we'd tier all objects whose sizes are less than the threshold (segment size) to replication and the larger ones to EC if this makes any sense20:13
wbhuberminwoob: peluse: this has to be evidently internally handled under the covers as long as both policies exist in swift.conf20:15
*** albertom has joined #openstack-swift20:15
*** dmsimard|afk is now known as dmsimard20:15
pelusewbhuber: we're not trying to solve that problem in swift right now - anything related to auto-anything wrt tiering between repl and ec policies.  we have the tier'ing bp's which are about the framework in general and then we need tomanually establish the right "rules" for when based on manual testing, etc20:18
pelusewbhuber: right now we're just looking to identify some perf guidelines for EC as a standalone policy20:18
pelusewbhuber: and comparing it to a baseline of repl is a good way to do that...20:19
wbhuberpeluse: absolutely you're right - this auto-tiering would be introduced in the "Swift EC 2.0" some kind of version.20:20
wbhuberpeluse: tiering bp's?20:20
* torgomatic isn't smart enough for auto-tiering20:21
wbhubertorgomatic, if it would ever exist, you've to be smart to be able to review it! =]20:22
torgomaticwbhuber: let me know how that works out for you :p20:22
peluseso there are bp's up there....20:22
peluseshiva from netapp I think had the last update20:23
pelusei'll ping him and see if he's coming to tokyo20:23
*** rohit_ has joined #openstack-swift20:23
*** ccavanna has quit IRC20:26
*** cutforth has quit IRC20:35
wbhuberpeluse: minwoob: i believe bp you were pointing to is from the third bullet in this old trello post: https://trello.com/c/QWaYXWNf/120-small-file-optimizations20:35
wbhuberpeluse: clearly, the third bullet states the m ring for objects < segment size is directing to the replication path20:36
*** agomez has quit IRC20:37
*** alejandrito has quit IRC20:41
*** garthb has joined #openstack-swift20:44
*** alejandrito has joined #openstack-swift20:46
jrichlitorgomatic:  I am working on the support for footers in the Replication path.  I wanted to check my understanding of the conversation on the wire.20:51
jrichlitogomatic: I saw the EC conversation specified on the patch that added it20:51
jrichlitogomatic: and so I have modified that to be what I think I am striving for with this solution.  could you check out http://paste.openstack.org/show/474069/?20:52
jrichlitorgomatic:  sorry about the handle misspell ...20:53
torgomaticjrichli: uh, let me go read some code... I think there should be a header in the proxy -> obj PUT request that says "hey, here comes some MIME"20:54
jrichligreat, thx!20:55
torgomaticyeah,X-Backend-Obj-Metadata-Footer20:55
jrichlioh, right.  i didn't add the new ones on there.  i just took out what i didn't need ... but its good to know exactly what i need to add!  thx20:56
torgomaticnp20:56
*** breitz has quit IRC21:01
*** hezhiqiang has joined #openstack-swift21:02
*** zhill has quit IRC21:02
*** zhill has joined #openstack-swift21:02
*** dustins has quit IRC21:03
notmynamepython. how does it work21:06
jrichliit's sneaky21:16
*** openstackgerrit has quit IRC21:16
*** openstackgerrit has joined #openstack-swift21:16
*** trifon has quit IRC21:17
*** jrichli has quit IRC21:22
*** pberis has quit IRC21:31
*** jlhinson_ has quit IRC21:32
*** NM has quit IRC21:35
notmynamethe python lesson I just learned is that you should never yield inside a finally clause21:41
notmyname...because it causes an error (Exception RuntimeError: 'generator ignored GeneratorExit' in <generator object foo at 0x10d2a5aa0> ignored): https://gist.github.com/notmyname/bed03c9796bc9dcada1b21:47
*** annegentle has quit IRC22:01
*** openstackgerrit has quit IRC22:01
*** openstackgerrit has joined #openstack-swift22:01
*** Kennan_Vacation2 has joined #openstack-swift22:02
*** Kennan_Vacation has quit IRC22:02
pelusewbhuber: yeah that was a brainstorming conversation...22:02
*** hezhiqiang has quit IRC22:03
*** wbhuber has quit IRC22:07
*** pberis has joined #openstack-swift22:08
*** CaioBrentano has quit IRC22:08
*** vinsh_ has joined #openstack-swift22:15
*** _hrou_ has quit IRC22:15
*** alejandrito has quit IRC22:16
*** vinsh has quit IRC22:19
*** trifon has joined #openstack-swift22:19
*** vinsh_ has quit IRC22:20
openstackgerritJohn Dickinson proposed openstack/swift: Fix missing container update  https://review.openstack.org/18673522:23
*** jkugel1 has quit IRC22:25
*** mac_ified has joined #openstack-swift22:30
*** openstack has joined #openstack-swift22:34
*** chsc has quit IRC22:39
*** albertom is now known as albertom[afk]22:43
*** openstackstatus has quit IRC22:47
*** openstack has joined #openstack-swift22:49
*** hezhiqiang has joined #openstack-swift23:04
*** hezhiqiang has quit IRC23:08
*** vinsh has joined #openstack-swift23:17
*** trifon has quit IRC23:22
*** zhill has quit IRC23:32
*** marzif has joined #openstack-swift23:34
*** gyee has quit IRC23:35
*** hrou has joined #openstack-swift23:39
openstackgerritMerged openstack/swift: Only yield the pending segment on error if it's a SegmentListingError  https://review.openstack.org/22756923:40
*** garthb has quit IRC23:46
*** minwoob has quit IRC23:48
*** vinsh has quit IRC23:57
*** NM has joined #openstack-swift23:59

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