Wednesday, 2015-07-29

*** peluse_ has joined #openstack-swift00:00
*** peluse has quit IRC00:01
hogood morning!00:06
*** NM has joined #openstack-swift00:06
*** jasondotstar has quit IRC00:11
*** thurloat is now known as thurloat_isgone00:11
*** kota_ has joined #openstack-swift00:15
*** ChanServ sets mode: +v kota_00:15
kota_hello00:16
*** jasondotstar has joined #openstack-swift00:17
*** esker has quit IRC00:23
*** david-lyle has quit IRC00:24
*** ujjain has quit IRC00:24
*** ujjain has joined #openstack-swift00:26
*** ujjain has joined #openstack-swift00:26
mattoliverauho, kota_: morning00:27
*** changbl has joined #openstack-swift00:34
*** zhill has quit IRC00:39
hokota_, mattoliverau: morning!00:39
*** ccavanna has joined #openstack-swift00:46
*** janonymous_ has quit IRC00:46
*** nakagawamsa has joined #openstack-swift00:57
*** haypo has left #openstack-swift00:57
*** kota_ has quit IRC01:02
*** thurloat_isgone has quit IRC01:03
*** thurloat_isgone has joined #openstack-swift01:06
*** thurloat_isgone is now known as thurloat01:06
*** jasondotstar has quit IRC01:12
*** jasondotstar has joined #openstack-swift01:17
*** jasondotstar has quit IRC01:22
*** breitz has quit IRC01:22
*** thurloat is now known as thurloat_isgone01:27
*** janonymous has quit IRC01:36
*** jrichli has joined #openstack-swift01:37
*** breitz has joined #openstack-swift01:37
*** nexusz99 has joined #openstack-swift01:43
*** NM has quit IRC01:53
*** breitz has quit IRC01:57
*** wbhuber has joined #openstack-swift02:08
*** david-lyle has joined #openstack-swift02:19
*** haomaiwang has quit IRC02:21
*** haomaiwa_ has joined #openstack-swift02:22
*** david-lyle has quit IRC02:23
*** haomaiwa_ has quit IRC02:36
*** haomaiwang has joined #openstack-swift02:36
*** nakagawamsa has quit IRC02:36
*** nakagawamsa has joined #openstack-swift02:49
*** wbhuber has quit IRC02:51
*** sanchitmalhotra has joined #openstack-swift03:00
*** sanchitmalhotra1 has joined #openstack-swift03:05
*** sanchitmalhotra has quit IRC03:07
*** sanchitmalhotra has joined #openstack-swift03:10
notmynamegood evening, world03:10
lifelesso/03:11
*** mragupat has joined #openstack-swift03:12
*** sanchitmalhotra1 has quit IRC03:12
notmynamelifeless: hi! I don't normally see you around these parts. welcome :-)03:12
*** mragupat_ has joined #openstack-swift03:13
*** haomaiwang has quit IRC03:14
lifelessnotmyname: I realised I wasn't lurking here, so fixed that :)03:15
notmyname:-)03:15
lifelesscan't represent folk if I'm not seeing the pan,just for starters03:16
notmynameclayg: kota_: ho: acoles_away: peluse_: redbo: dfg_: torgomatic: in tomorrow's meeting I want to talk about heypo's patch to change flake8 from a whitelist to a blacklist https://review.openstack.org/#/c/205977/03:16
*** mragupat has quit IRC03:16
*** dmorita has joined #openstack-swift03:23
mattoliveraunotmyname: o/03:28
*** NM has joined #openstack-swift03:32
*** david-lyle has joined #openstack-swift03:34
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873603:44
*** jrichli has quit IRC03:46
openstackgerritCarlos Cavanna proposed openstack/swift: Proposed improvement to Swift documentation aimed at first-time contributors.  https://review.openstack.org/20686103:59
notmynamemattoliverau: hey! I saw in the buffer playback that you're deathly ill04:00
*** SkyRocknRoll has joined #openstack-swift04:02
notmynamemattoliverau: I sincerely hope that you do not die04:02
notmyname;-)04:02
mattoliveraunotmyname: yeah, I have had a bad winter this year.. might make sure I get a flu shot next year.04:02
*** NM has quit IRC04:03
mattoliveraunotmyname: thanks, but you know man flu is the biggest killer :P04:03
notmynamemattoliverau: not in your country04:04
*** SkyRocknRoll has quit IRC04:07
*** proteusguy has quit IRC04:07
openstackgerritMerged openstack/swift: Filter Etag key from ssync replication-headers  https://review.openstack.org/17397304:07
notmynameccavanna: that's a great patch! thank you!04:09
*** ppai has joined #openstack-swift04:09
notmynameclayg: check this one out https://review.openstack.org/#/c/206861/04:09
ccavannanotmyname: Sure. I need to ammend one thing that didn't quite come as I expected :-)04:09
*** mragupat_ has quit IRC04:09
ccavannanotmayname: next, I will look for some reviews.04:10
notmynameccavanna: I've got some notes that I email to new contributors, so I'll probably add them to your base document after it lands04:11
openstackgerritCarlos Cavanna proposed openstack/swift: Proposed improvement to Swift documentation aimed at first-time contributors. Ammended link.  https://review.openstack.org/20686104:15
lifelessnotmyname: I've commented on https://review.openstack.org/#/c/88736/04:16
notmynameccavanna: I think you also need to fix the py26 reference. also, and you could mention this in the doc too, (and this is a very small nit that wouldn't block landing) the commit message itself should have a short first line followed by longer paragraphs as needed04:16
lifelessnotmyname: I don't know what you mean by 'resolver for openstack' - if you mean pip resolver, I have a working prototype in pip itself, but I don't understand the relevance to merging/not merging the requirements updates04:17
notmynamelifeless: that's mostly a note to mordred referencing something we talked about a long time ago. note that comment was in early 2014. there are current other patches to update hacking in swift04:18
lifelessnotmyname: yep; I mentioned other bits in my comment there.04:18
ccavannanotmyname: I saw it after my ammed :-) Will fix it now. I really didn't have much to say in the commit message.04:18
notmyname(which BTW is annoying to me because the new versions bring in new flake8 which have IMO a bug but it's required because newer pbr is neede for pbr and newer pbr uses newer hacking)04:19
lifelessnotmyname: but - since I'm the one driving the resolver/ecosystem work, unless I understand what you're actually looking for, all I can be sure of is that I'm unlikely to deliver what you need :)04:19
lifelessnotmyname: hmm, newer pbr doesn't use newer hacking04:19
*** proteusguy has joined #openstack-swift04:19
lifelessnotmyname: the dep is the other way around: old hacking has 'pbr<1.0' as a dep04:19
notmynameah ok04:19
lifelessnotmyname: and that holds pbr back04:19
notmynameI misremembered04:19
lifelessit's a result of the overly tight deps that folk tried during K04:20
lifelessand which I'm hoping we'll get fully unwound this cycle04:20
notmynamepy requires newer pbr which requires newer hacking which requires newer flake804:21
ccavannanotmyname: I will change the text to just "There's no current support for Python 3"04:21
notmyname*py304:21
lifelessnotmyname: py3 compatible requirements requires newer pbr which is blocked by old hacking04:22
lifelessnotmyname: and newer hacking is undesirable due to flake8 ?04:22
*** SkyRocknRoll has joined #openstack-swift04:22
lifelessnotmyname: or is it some specific tests in flake8 that concern you?04:23
notmynameccavanna: hmm...that's something that may soon change (one hopes). but yeah, that would be good04:23
notmynamelifeless: newer flake8 introduces new tests that we want to ignore. but it doesn't support both ignore and select directives at the same time04:24
notmynamewhereas older flake8 did04:24
lifelessnotmyname: ah; seems like pinging sigmavirus about that would be good04:24
notmynamehaypo has been running with it on our side04:24
lifelessyep04:25
notmynamepeluse_: so when do I get some of this in a lab to run swift on? http://www.bbc.com/news/technology-33675734 ;-)04:25
notmynamelifeless: see https://review.openstack.org/#/c/205977/04:26
lifelessnotmyname: the suggestion that xpoint will be a cpu adjunct makes me think its pricey04:26
lifelessnotmyname: [to make, not just to buy :)]04:26
notmynamewhich is why I ask for free samples ;-)04:26
lifelessnotmyname: anyhow04:27
lifelessnotmyname: what resolver thing are you speaking of ?04:27
lifelessand how will it make merging proposal bot updates more ok ?04:28
openstackgerritCarlos Cavanna proposed openstack/swift: Swift documentation for first-time contributors.  https://review.openstack.org/20686104:28
notmynamethe idea we talked about was something that would look at simple dependency version directives to determine if what was required in one file is a superset of what's required in another04:29
notmynameeg if global-requirements says foo>2.3 and swift says foo>2.0, then pass04:29
notmynameand by "simple" we were talking about a limited grammar. maybe not worrying about the places that had exclusions. depends on how complicated it would end up being04:30
notmynamebut the goal was to be able to do better than a simple string match on a project's local requirements vs global requirements.04:30
lifelessok, just forcing the projects to be a superset04:30
notmynameright04:30
notmynamemy understanding is that there is something in the works04:30
lifelessnope04:30
lifelessnothing04:30
notmynameor similar.04:31
lifelessnothing at all04:31
notmynamesomethign about the way requirements are parsed04:31
lifelessno spec, no work queued up, nothing in the backlog04:31
lifelessI need to run, but we should talk about actually putting something in the queue to be done04:31
lifelessand who needs to buy-in to such a thing04:31
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873604:32
lifelessthe parsing has been overhauled already by me during this cycle for the constraints work04:32
*** bwall has joined #openstack-swift04:49
bwallnotmyname: is it cool if i dpm you?04:50
bwall*pm04:50
notmynamesure04:50
*** tamizh_g_ has joined #openstack-swift05:00
*** tamizh_geek has joined #openstack-swift05:03
*** tamizh_g_ has quit IRC05:03
tamizh_geekHello people, my patch is waiting for a final +2 here : https://review.openstack.org/#/c/204196/ Requesting core devs to please take a look.05:11
*** sanchitmalhotra1 has joined #openstack-swift05:13
*** sanchitmalhotra has quit IRC05:16
*** sanchitmalhotra has joined #openstack-swift05:20
*** sanchitmalhotra1 has quit IRC05:22
*** proteusguy has quit IRC05:24
lifelessnotmyname: ok, I'm back05:27
lifelessnotmyname: so yeah - I don't think 'strict superset' is incompatible with the current things driving policies05:28
lifelessnotmyname: but it is wide enough impact that I think we need a cross project spec, + operator and distro checkins05:28
*** nakagawamsa has quit IRC05:32
notmynamelifeless: I'll keep my eyes open for any work on that. if something comes up, I'd appreciate a ping05:35
lifelessnotmyname: I'll put a spec together for the tokyo cycle; we're sufficiently slow implementing the tox constraints stuff that I don't want to put more into the pipeline yet05:37
*** proteusguy has joined #openstack-swift05:40
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873606:15
*** hrou has quit IRC06:20
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Imported Translations from Transifex  https://review.openstack.org/20689906:36
*** sanchitmalhotra1 has joined #openstack-swift06:36
*** sanchitmalhotra has quit IRC06:37
*** sanchitmalhotra has joined #openstack-swift06:58
*** tongli_ has quit IRC07:00
*** sanchitmalhotra1 has quit IRC07:00
*** rledisez has joined #openstack-swift07:02
*** geaaru has joined #openstack-swift07:24
openstackgerritMatthew Oliver proposed openstack/swift: Add handoff region affinity support to replicators  https://review.openstack.org/19986307:33
*** ccavanna has quit IRC07:52
*** sanchitmalhotra1 has joined #openstack-swift07:58
*** sanchitmalhotra has quit IRC08:00
*** jordanP has joined #openstack-swift08:06
*** acoles_away is now known as acoles08:08
*** jistr has joined #openstack-swift08:08
*** tamizh_g_ has joined #openstack-swift08:16
*** tsubic has joined #openstack-swift08:23
*** jasondotstar has joined #openstack-swift08:25
*** mahatic has joined #openstack-swift08:31
*** ho has quit IRC08:35
*** kei_yama has quit IRC08:39
*** km has quit IRC08:39
*** mahatic has quit IRC09:17
*** janonymous has joined #openstack-swift09:17
*** sanchitmalhotra has joined #openstack-swift09:23
*** sanchitmalhotra1 has quit IRC09:25
*** kota_ has joined #openstack-swift09:26
*** ChanServ sets mode: +v kota_09:26
-openstackstatus- NOTICE: Currently our CI system is broken, jobs are not getting processed at all.09:30
*** ChanServ changes topic to "Currently our CI system is broken, jobs are not getting processed at all."09:30
*** sanchitmalhotra1 has joined #openstack-swift09:43
*** haypo has joined #openstack-swift09:44
*** sanchitmalhotra has quit IRC09:45
*** nexusz99 has quit IRC09:52
*** jasondotstar has quit IRC09:57
*** kota_ has quit IRC10:00
*** Kennan has quit IRC10:00
*** mitz has quit IRC10:00
*** sc68cal has quit IRC10:00
*** mitz has joined #openstack-swift10:00
*** Kennan has joined #openstack-swift10:01
*** kota_ has joined #openstack-swift10:01
*** ChanServ sets mode: +v kota_10:01
*** sc68cal has joined #openstack-swift10:02
*** tdasilva has quit IRC10:05
*** blair has quit IRC10:05
*** tsubic has quit IRC10:05
*** acoles has quit IRC10:05
*** jasondotstar has joined #openstack-swift10:09
*** tsubic has joined #openstack-swift10:17
*** geaaru has quit IRC10:24
*** kota_ has quit IRC10:37
*** aix has quit IRC10:38
*** geaaru has joined #openstack-swift10:41
*** blair has joined #openstack-swift10:43
*** NM has joined #openstack-swift10:44
*** acoles_away has joined #openstack-swift11:00
*** acoles_away is now known as acoles11:00
*** ChanServ sets mode: +v acoles11:00
*** tdasilva has joined #openstack-swift11:01
*** dmorita has quit IRC11:04
*** geaaru has quit IRC11:10
*** geaaru has joined #openstack-swift11:13
*** jasondot_ has joined #openstack-swift11:23
*** jasondotstar has quit IRC11:25
*** cdelatte has joined #openstack-swift11:33
*** delattec has joined #openstack-swift11:33
*** sanchitmalhotra1 has quit IRC11:35
*** delatte has joined #openstack-swift11:40
*** delattec has quit IRC11:41
*** cdelatte has quit IRC11:42
*** tamizh_g_ has quit IRC11:47
*** delattec has joined #openstack-swift11:48
*** delatte has quit IRC11:51
*** ppai has quit IRC11:54
*** ChanServ sets mode: +v tdasilva11:57
*** ppai has joined #openstack-swift12:01
*** NM has quit IRC12:02
*** NM has joined #openstack-swift12:04
*** aix has joined #openstack-swift12:07
*** NM has quit IRC12:08
*** marcusvrn has joined #openstack-swift12:16
*** ccavanna has joined #openstack-swift12:17
*** ccavanna has quit IRC12:31
openstackgerritAlistair Coles proposed openstack/swift: Remove unused code in swift/obj/server.py  https://review.openstack.org/20702412:38
*** ppai has quit IRC12:40
tdasilvagood morning12:43
*** ChanServ changes topic to "Review Dashboard: http://goo.gl/8IUcKl | Summary Dashboard: http://goo.gl/qHus5v | Hackathon topics: https://etherpad.openstack.org/p/swift-midcycle-aug-2015 | https://etherpad.openstack.org/p/swift_encryption_issues | Logs: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/"12:51
-openstackstatus- NOTICE: zuul's disks were at capacity. Space has been freed up and jobs are being re-queued.12:51
*** ppai has joined #openstack-swift12:53
*** annegentle has joined #openstack-swift12:57
*** mahatic has joined #openstack-swift13:02
*** tsubic has quit IRC13:04
*** hrou has joined #openstack-swift13:05
*** jrichli has joined #openstack-swift13:07
*** ccavanna has joined #openstack-swift13:15
*** tsubic has joined #openstack-swift13:17
*** NM has joined #openstack-swift13:21
*** jkugel has joined #openstack-swift13:22
-openstackstatus- NOTICE: zuul jobs after about 07:00 UTC may need a 'recheck' to enter the queue. Look if your change is in http://status.openstack.org/zuul/ and recheck if not.13:27
*** ppai has quit IRC13:32
*** annegentle has quit IRC13:36
*** NM has quit IRC13:43
*** jasondotstar has joined #openstack-swift13:49
*** jasondot_ has quit IRC13:52
*** mragupat has joined #openstack-swift13:59
*** mragupat has quit IRC13:59
*** wbhuber has joined #openstack-swift13:59
*** breitz has joined #openstack-swift13:59
*** mragupat has joined #openstack-swift14:00
openstackgerritThiago da Silva proposed openstack/swift: fix rdo link  https://review.openstack.org/20705914:03
*** fbo has quit IRC14:04
*** EmilienM has quit IRC14:05
*** haypo has quit IRC14:06
*** haypo has joined #openstack-swift14:06
*** haypo has quit IRC14:06
*** haypo has joined #openstack-swift14:06
*** EmilienM has joined #openstack-swift14:09
*** fbo has joined #openstack-swift14:09
*** annegentle has joined #openstack-swift14:14
*** NM has joined #openstack-swift14:15
*** NM1 has joined #openstack-swift14:15
*** NM has quit IRC14:19
*** silor has joined #openstack-swift14:24
*** SkyRocknRoll has quit IRC14:32
*** mahatic has quit IRC14:38
*** janonymous_ has joined #openstack-swift14:47
*** jlhinson has joined #openstack-swift14:53
*** esker has joined #openstack-swift14:54
*** minwoob has joined #openstack-swift14:55
*** nadeem has joined #openstack-swift14:55
*** nadeem has joined #openstack-swift14:56
*** jasondotstar has quit IRC14:59
*** jistr has quit IRC15:00
*** haomaiwang has joined #openstack-swift15:01
*** mragupat has quit IRC15:01
*** jistr has joined #openstack-swift15:02
*** haomaiwang has quit IRC15:03
*** haomaiwang has joined #openstack-swift15:03
*** zaitcev has joined #openstack-swift15:07
*** ChanServ sets mode: +v zaitcev15:07
*** mahatic has joined #openstack-swift15:10
*** SkyRocknRoll has joined #openstack-swift15:17
*** hunius has joined #openstack-swift15:19
huniusHi, I wan't to know, what's the best place to extend swift by a Meteor connection. I wan't to insert data into the meteor database from within a custom middleware in swift. My problem is, where to establish the ddp connection to the meteor server? This should happen on startup, but I don't know exactly the best way to do it in swift. Any would be great. Best Daniel15:19
notmynamegood morning15:22
notmynamehunius: in wsgi middleware, the __init__ is called on startup and the __call__ is called for each request. so you should probably look into a threadpool of connections created in the __init__ that is consumed in the __call__15:23
notmynameerr..maybe not "probably". that's just where I'd start :-)15:23
huniussounds good. I will try this. I15:24
huniussounds good. I will try this. I am not so familiar with python, so I will start researching how I can implement a threadpool15:25
notmynamehunius: if you haven't seen it, here's a good place to start with swift middleware http://docs.openstack.org/developer/swift/development_middleware.html#creating-your-own-middleware15:26
notmynamehunius: ah, ok. well a pool of connections might be step 2 then. to start with, just to get the framework of the idea down, just deal with a single connection to meteor and one request at a time. then scale15:27
huniusThanks a very lot for your help. Yes, I know the examples. I have also bought a swift book, but all the wsgi stuff is absolutely new to me:)15:27
huniusyes. My plan is to extract metadata from the uploaded file and write this into the meteor database. I think this has to be done also within  a new thread, so the client gets the success answer when storing was successfull. The extracted metadata should be passed then by meteor automagically:)15:29
hurricanerixhunius: If you are new to Python, I think this book is pretty good: http://www.effectivepython.com/15:31
*** mahatic has quit IRC15:33
huniushurricanerix: thanks, I definetively need to extend my knowledge. I think it will be a bit more work on the swift side as initially assumed...15:34
notmynamehurricanerix: did I see in email that you're doing the defcore thing in austin today?15:34
hurricanerixnotmyname: yeah, I am here now.15:36
hurricanerixThere are currently networking talks going on.  So I am just trying to learn what I can.  :)15:38
*** esker has quit IRC15:39
notmynamehurricanerix: fun ;-)15:41
hurricanerixnotmyname: This is interesting, but I am more excited about the swift midcycle. :)15:42
*** esker has joined #openstack-swift15:50
*** esker has quit IRC15:50
*** esker has joined #openstack-swift15:54
*** mahatic has joined #openstack-swift15:56
*** mahatic has quit IRC15:56
*** tamizh_g_ has joined #openstack-swift15:57
*** haomaiwang has quit IRC16:01
*** esker has joined #openstack-swift16:01
*** haomaiwang has joined #openstack-swift16:02
*** jistr has quit IRC16:08
*** briancurtin has quit IRC16:13
*** zhiyan has quit IRC16:13
*** nottrobin has quit IRC16:13
*** serverascode has quit IRC16:13
peluse_acoles or jrichli - which patch is the tail of crypto again?16:16
claygpeluse_: it's on the wiki!16:17
jrichlihttps://review.openstack.org/#/c/203454/16:17
claygpeluse_: p 20345416:18
jrichliand yes, its on the wiki :-)16:18
peluse_wiki wiki wiki16:18
jrichliwack16:18
clayglike Fozzy the bear?16:18
*** david-lyle has quit IRC16:18
*** silor1 has joined #openstack-swift16:34
*** rledisez has quit IRC16:35
*** silor has quit IRC16:36
*** silor1 is now known as silor16:36
*** nottrobin has joined #openstack-swift16:37
*** jordanP has quit IRC16:39
*** david-lyle has joined #openstack-swift16:42
*** serverascode has joined #openstack-swift16:43
*** zhiyan has joined #openstack-swift16:46
acolespeluse_: i saw some func test failures with patch 201283 - is that just badness with my SAIO? (I pasted failures on review)16:47
patchbotacoles: https://review.openstack.org/#/c/201283/16:47
*** tamizh_g_ has quit IRC16:49
peluse_thanks, I don't see any.  I'm stuck in an all day meeting so have limited time to get anything real done but will take a look at your comments when I can - thanks!16:49
wbhuberclayg: wocka wocka wocka :)16:49
peluse_acoles, yeah, those are strange errors for this patch :)  I don't see them16:51
peluse_acoles, and wrt the refactor diskfile patch, no I didn't see that until I had this other one working16:52
peluse_acoles, do you think we should land that one and then work on this one?  If so I'll review and push it through if it doesn't before I get a chance (tomorrow) and then have fun rebasing16:52
acolespeluse_: ok thats weird i don't see them on master. i'll dig some more.16:53
*** wbhuber has quit IRC16:54
peluse_I'll rerun as well16:55
acolespeluse_: well that would be nice but i am biased ;P i'll try the rebase and see how painful it will be16:56
peluse_:)16:57
*** briancurtin has joined #openstack-swift16:57
peluse_acoles, bah you're right on the func tests.  I didn't have EC as my default.  You'd think I've never done this before...16:59
acolespeluse_: what! you of all people aren't running EC default! :D17:00
acolespeluse_: you need to hand back your t-shirt man :P17:00
peluse_heh, I didn't get one!17:00
acolesawww17:01
*** haomaiwang has quit IRC17:01
*** haomaiwang has joined #openstack-swift17:02
acolespeluse_: we really ought to get a jenkins job running against EC. now there's a nice task for someone.17:03
peluse_for sure17:05
* peluse_ has no idea how to go about doing that17:05
*** _hrou_ has joined #openstack-swift17:05
*** hrou has quit IRC17:06
notmynameacoles: peluse_: I can do that pretty easily in the swiftstack community qa cluster. or, more specifically, I can ask charz to set it up :-)17:06
peluse_delegation... nice17:07
acolesnotmyname: great idea17:08
notmynameit's 1am for him now, so I sent an email.17:09
openstackgerritJohn Dickinson proposed openstack/swift: Fixes for mock 1.1  https://review.openstack.org/20713117:09
openstackgerritJohn Dickinson proposed openstack/swift: Fixes for mock 1.1  https://review.openstack.org/20713217:10
notmyname^ those are backports for the stuff that mock>1.0 broke. both stable branches have mock>=1.0, so any new patches on those branches (any other backports) won't pass the gate until those are landed first17:11
notmynamethey are cherry-picked from haypo's patch: https://review.openstack.org/#/q/Id179513c6010d827cbcbdda7692a920e29213bcb,n,z17:11
charznotmyname: acoles What's ec test against swiftstack community cluster?17:14
peluse_just func tests using an EC policy as default17:14
notmynamecharz: setting up an EC policy as a default policy in swift.conf and running func tests17:14
zaitcevgoodie grief, mock hurt swift too?17:15
notmynamezaitcev: it got more strict (see the patch on master). turns out we were calling some methods that didn't exist and some methods incorrectly17:16
notmynameso it's our fault, not mock's ;-)17:16
charzpeluse_: notmyname oh, got it, I already have ec policy and 3-replica on the cluster, so I need put functional test for ec policy.17:17
notmynamecharz: right17:17
notmynamejust so that we have a test run against both17:17
charznotmyname: yes, we'll.17:17
notmynamethanks17:18
charznotmyname: np17:18
zaitcevnotmyname: I do not understand. The mock 1.1 simply does not support py26. How are we using it in Kilo?17:21
notmynamethat is a good question. I just ran py27 and it worked. might need to think about it more, then. or rather, might need to cap the version there17:22
zaitcevI hit that problem with git-review and I took the patch from swiftclient, which does17:23
zaitcevmock==1.0.1;python_version=='2.6'17:23
zaitcevmock>=1.0;python_version!='2.6'17:23
notmynameoh yeah. that requires newer pbr/pip too, though17:24
timburkezaitcev: notmyname: fwiw, mock went back to supporting 2.6 in 1.1.4 (and continues to through the latest release of 1.3.0)17:25
*** hunius has quit IRC17:25
*** aix has quit IRC17:30
notmynametimburke: zaitcev: I'm open to suggestions on what to do there17:33
zaitcevnotmyname: if the infrastructure team moves to 1.1.4, I'll just review what you posted and we're done. Might need to undo the changes in swiftclient too. And abandon my fix for git-review (it's not merged yet).17:34
notmynamelifeless: mordred: ^17:36
*** janonymous_ has quit IRC17:36
lifelessnotmyname: ? econtex17:37
zaitcevlifeless: is it true that timburke said, that 1.1.4 is okay with py26, and it yes, are you going to have that in the gate? We'll drop "mock==1.0.1;python_version=='2.6'" then.17:38
lifelesszaitcev: I don't know what you mean by 'in the gate'17:38
*** SkyRocknRoll has quit IRC17:38
notmynameglobal test requirements is mock!=1.1.4,>=1.1;python_version!='2.6'17:38
notmynametimburke says mock >1.1.4 works with py26.17:39
lifelesszaitcev: no its not: http://git.openstack.org/cgit/openstack/requirements/tree/global-requirements.txt#n25017:39
notmynameand this matters because I just proposed some mock fixes as a result of newer mock to a backport-branch that still supports py2617:39
zaitcevlifeless: currently, if a project supports Python 2.6, it cannot be pushed through the gate at all. Like COMPLETELY FAILS. The blow-up looks like this: https://bugs.launchpad.net/openstack-gate/+bug/147328617:39
openstackLaunchpad bug 1473286 in OpenStack-Gate "mock fails with SyntaxError in py26" [Undecided,Invalid]17:39
lifeless>=1.2 is the global requirements17:40
lifelesszaitcev: whichever project you're lookin at is probably not synced with global-requirements for some reason17:41
notmynameah ok17:41
lifelessand yes, 1.2 and 1.3 support 2.617:41
notmynameso it seems we're good17:42
notmynamewe need to make sure the mock dependency is updated, but that's easy. and the proposed backport will work and the branch is still supportable py26_17:43
notmynames/_/+17:43
openstackgerritJohn Dickinson proposed openstack/swift: update mock in test-requirements  https://review.openstack.org/20714317:49
openstackgerritJohn Dickinson proposed openstack/swift: update mock in test-requirements  https://review.openstack.org/20714517:49
notmynamezaitcev: ^ there. mock>=1.2 for juno and kilo17:50
openstackgerritJohn Dickinson proposed openstack/swift: Update test-requirements to match global requirements.  https://review.openstack.org/20417917:50
*** SkyRocknRoll has joined #openstack-swift17:52
notmynameand with that my laptop battery is getting very low. I'll be offline until I find more power. definitely by the meeting at 2100utc17:54
*** jasondotstar has joined #openstack-swift17:54
lifelessso the history here is this17:59
lifelessmock was vey stale17:59
lifelesswith dev moved to cpython17:59
lifelessand I volunteered to do the rolling backport of it18:00
lifelesswhen I asked around noone volunteered to help with 2.6, so I took the route of 'if folk want 2.6 support pin < 1.1'18:00
lifelessturns out there were some folk willing to volunteer :). So we reintroduced 2.6 support18:00
*** haomaiwang has quit IRC18:01
lifelessnow, there was a bad change in python 3.4, which we bckported, then reverted, redid and reapplyied18:01
lifelesswhich was the 1.1.x -> 1.2 -> 1.3 transitions18:01
*** haomaiwang has joined #openstack-swift18:02
*** lcurtis has joined #openstack-swift18:19
clayghistory lessons are so much fun18:21
*** jasondotstar has quit IRC18:23
openstackgerritCarlos Cavanna proposed openstack/swift: Swift documentation for first-time contributors.  https://review.openstack.org/20686118:23
*** annegentle has quit IRC18:26
*** annegentle has joined #openstack-swift18:26
acolespeluse_: i rebased your review+my suggested patch on top of patch 198429. It took some work to get things back into the right place but i have it working.18:31
patchbotacoles: https://review.openstack.org/#/c/198429/18:31
acolespeluse_: the result is also less delta because more diskfile code is shared :)18:31
*** openstackgerrit has quit IRC18:31
*** openstackgerrit has joined #openstack-swift18:32
acolespeluse_: but i dunno what to do with my branch! i don't want to force your hand, either on the diskfile refactor review or on my suggested changes to yours.18:32
peluse_acoles, that's great, thanks!18:33
acolespeluse_: so for want of better idea i will push to gerrit as a new review just so it is somewhere other than on my laptop18:33
acolespeluse_: then if you like you can slurp it back into your review18:33
peluse_or you cqan push over mine if you want18:34
* acoles isn't sure `git slurp` is a real command18:34
peluse_I'm debugging the strange failures... I have a screwy range thing going on.  Shouldn't be too bad18:34
tdasilvaacoles: I started reviewing the diskfile refactor a while back and noticed that diskfily.py has around 12 different classes now, have we considered moving manager classes to another file?18:35
acolespeluse_: well i could but maybe you want to look at the refactor first18:35
acolestdasilva: yeah it grew 4 Base* classes18:36
peluse_I can review as part of working on my patch is what I was thinking.  either way works18:36
acolestdasilva: idk how it would best be split out18:36
acolestdasilva: would it make sense for the managers to be separated, or for the policy type class families to be separated?18:37
acolestdasilva: i *think* clayg wanted to eliminate some of the classes altogether (the Reader/Writer perhaps)18:38
tdasilvaacoles: yeah...I was strugling with the same questions...it was just that I noticed the file becoming huge and difficult to 'navigate'18:39
tdasilvamaybe diskfile_base, diskfile_replication, diskfile_ec ??? not really sure...18:40
acolestdasilva: i only made it 19 lines longer and I bet those were really useful comments :D :D18:40
acolestdasilva: but yeah its a pain to navigate18:40
acolestdasilva: if i get chance i will try what you said - diskfile_base, diskfile_replication, diskfile_ec18:41
tdasilvaacoles: +1, didn't mean to offload on you, would be glad to pick it up on a subsequent patch too...18:43
openstackgerritAlistair Coles proposed openstack/swift: Refactor diskfile  https://review.openstack.org/19842918:43
openstackgerritAlistair Coles proposed openstack/swift: WIP Alternate Add ability for GET path to see/select alternate frag archs  https://review.openstack.org/20716518:43
peluse_acoles, cool, thanks18:44
acolespeluse_: np i gotta go so took the quick option :) will be around for mtg later18:45
peluse_K18:45
acolestdasilva: np follow on might be good since i have clayg's +2 and i wanted to minimise the grok'ing for reviewers18:45
*** nadeem has quit IRC18:46
acolespeluse_: the 3 failures are still there i'm afraid ;)18:46
*** nadeem has joined #openstack-swift18:46
peluse_acoles, new ones or same func test as before?18:46
acolespeluse_: same ones18:47
peluse_phew :)18:47
acolesheh18:47
*** acoles is now known as acoles_away18:49
claygpeluse_: heck yeah let's just make patch 198429 the new master - it'll merge eventually18:49
patchbotclayg: https://review.openstack.org/#/c/198429/18:49
peluse_yup, that's the plan.  have to fix a few func tests first where I've got an off-by-one on range requests somewhere18:50
*** acoles_away is now known as acoles18:50
peluse_but I'm stuck in a meeting all day so only sorta half-ass debugging18:51
*** acoles is now known as acoles_away18:51
*** geaaru has quit IRC18:56
openstackgerritCarlos Cavanna proposed openstack/swift: Swift documentation for first-time contributors.  https://review.openstack.org/20686118:59
*** haomaiwang has quit IRC19:01
*** haomaiwa_ has joined #openstack-swift19:01
openstackgerritMerged openstack/swift: Imported Translations from Transifex  https://review.openstack.org/20689919:05
*** silor has quit IRC19:06
openstackgerritMerged openstack/swift: Remove unused code in swift/obj/server.py  https://review.openstack.org/20702419:13
*** jasondotstar has joined #openstack-swift19:18
*** joeljwright has joined #openstack-swift19:25
*** ChanServ sets mode: +v joeljwright19:25
openstackgerritCarlos Cavanna proposed openstack/swift: Swift documentation for first-time contributors.  https://review.openstack.org/20686119:36
*** joeljwright has quit IRC19:45
*** HenryG has quit IRC19:49
*** HenryG has joined #openstack-swift19:52
*** tamizh_g_ has joined #openstack-swift19:54
*** tamizh_g_ has quit IRC19:58
*** haomaiwa_ has quit IRC20:01
*** haomaiwa_ has joined #openstack-swift20:02
*** bill_az has joined #openstack-swift20:06
*** joeljwright has joined #openstack-swift20:08
*** ChanServ sets mode: +v joeljwright20:08
* notmyname back20:15
*** openstackgerrit has quit IRC20:16
*** openstackgerrit has joined #openstack-swift20:16
*** annegentle has quit IRC20:17
*** jasondotstar has quit IRC20:19
notmynamenote that there are 3 patches I'd like to discuss in the meeting (listed on https://wiki.openstack.org/wiki/Meetings/Swift). If you have a chance before the meeting to refresh your memory, that would be good20:20
hayponotmyname: hey. the meeting is in ~40 minutes, right?20:24
notmynamehaypo: correct20:24
hayponotmyname: (hi.) should I prepare something for " change flake8 tests from whitelist to blacklist"?20:25
notmynamehaypo: no more than you currently are. I'm planning on introducing the issue and I want to make sure people are aware of the implications of that patch and discuss any questions that people have20:27
notmynamehaypo: it's not a "beat up on haypo's patch" thing. more of understanding the implications and making sure we are ok with those before we land it20:27
haypook20:28
haypoi just plan to answer questions if somone has a question :)20:28
lifelesso/20:29
haypolifeless: hey. our pip expert :)20:30
lifelesswow thats a terrifying box to be in :)20:31
*** jasondotstar has joined #openstack-swift20:32
*** ahale has quit IRC20:32
*** ahale has joined #openstack-swift20:33
zaitcevcould be a peep expert20:40
lifelessso the problem is, I'm clearly in the state of having forgotten more than I currently know. So I could be whatever and I wouldn't know it :)20:42
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873620:47
haypolifeless: haha20:48
*** blmartin has joined #openstack-swift20:52
*** ho has joined #openstack-swift20:57
notmynamemeeting time in #openstack-meeting20:59
*** kota_ has joined #openstack-swift21:00
*** ChanServ sets mode: +v kota_21:00
openstackgerritMichael Barton proposed openstack/swift: go: make replicateDevice more defensive  https://review.openstack.org/20721721:00
*** minwoob_ has joined #openstack-swift21:00
*** haomaiwa_ has quit IRC21:01
*** ccavanna has quit IRC21:01
*** 6JTABPDW5 has joined #openstack-swift21:02
*** minwoob_ has quit IRC21:02
*** acoles_away is now known as acoles21:03
*** jordanP has joined #openstack-swift21:07
*** ccavanna has joined #openstack-swift21:09
*** jkugel has quit IRC21:15
*** ekarlso has quit IRC21:16
*** ccavanna_ has joined #openstack-swift21:17
*** ccavanna has quit IRC21:20
*** ccavanna_ has quit IRC21:24
*** joeljwright1 has joined #openstack-swift21:32
*** joeljwright has quit IRC21:32
*** joeljwright1 has quit IRC21:33
*** joeljwright has joined #openstack-swift21:34
*** ChanServ sets mode: +v joeljwright21:34
*** jasondotstar has quit IRC21:41
*** ekarlso has joined #openstack-swift21:44
acolesclayg: man you are so right about the bigger fish, i need to suppress my ocd :P21:47
*** hrou has joined #openstack-swift21:48
*** _hrou_ has quit IRC21:48
blmartinI dunno, with imagemagick you probably could programmatically generated jpg image with text :P21:49
torgomaticthat's less "bigger fish" and more "oh crap, Cthulhu"21:51
*** hrou has quit IRC21:52
acolesmattoliverau: hey wassup? you ill?21:59
claygphew - that was close22:00
peluse_clayg, what do you think of https://bugs.launchpad.net/swift/+bug/1469094 ?22:00
openstackLaunchpad bug 1469094 in OpenStack Object Storage (swift) "Missing .durable files of FAs can cause rebuildable objects to be inaccessible" [Medium,Confirmed]22:00
*** 6JTABPDW5 has quit IRC22:01
joeljwrightnotmyname: regards the swiftclient bugs we didn't get to on the agenda22:01
claygpeluse_: FWIW I work with Charles - he's a sharp cat - non native-english22:01
claygpeluse_: I'm not up to speed on that report - do you have a specific question?22:01
peluse_clayg, yeah I gathered that....22:01
claygpeluse_: ok sorry :)22:02
mattoliverauacoles: Hey! welcome back! yeah, been hit with some flu/stomache bug all week, it hasn't been pretty and spend the first 3 days out of it in bed. Getting better now tho, so kinda working again22:02
*** 16WAAEHWP has joined #openstack-swift22:02
peluse_basically only have 2 .durables and relying on their replication via reconstructor worked but it took a while22:02
joeljwrightnotmyname: combination of deadline and being ill for 2 weeks meant I didn't get to them - will try to get some of them triaged this week22:02
peluse_so do we just clsoe the bug or is it better to just require all .durables be written22:02
peluse_is the question22:02
acolesmattoliverau: oh sounds bad, take it easy22:02
*** Kennan2 has joined #openstack-swift22:02
claygpeluse_: ah yes - that's how I read the state of the bug - maybe we could do better?22:02
peluse_or bump up the "2" to something bigger22:02
joeljwrightmattoliverau: if it makes you feel better, you're not the only one who's been sick22:02
peluse_I mean, we chose "2" kinda randomly22:03
claygwell - it's less about how many durables and more about how many fragments?  the durables are just sort of a hint22:03
joeljwrightmattoliverau: it's getting boring now, but the combo of cough and screaming headache is one I could live without22:03
mattoliveraujoeljwright: :(22:03
*** Kennan has quit IRC22:03
acolesjoeljwright: ouch22:03
peluse_clayg, huh?  I think the big report was only about the .durables22:03
claygpeluse_: I think the bug report was about being able to read an object after 20022:04
clayger.. 20122:04
*** blmartin has quit IRC22:05
peluse_clayg, hmmm, maybe I'm reading it wrong but I'm not sure how that could be22:06
openstackgerritVictor Stinner proposed openstack/swift: Update hacking to 0.10.0  https://review.openstack.org/20597722:06
openstackgerritVictor Stinner proposed openstack/swift: Fix pep8 E warning for hacking 0.10  https://review.openstack.org/20723722:06
haypoacoles: https://review.openstack.org/207237 fix _most_ E warnings of hacking 0.1022:07
*** kota_ has quit IRC22:07
*** acoles is now known as acoles_away22:07
*** joeljwright has quit IRC22:07
haypoacoles_away: my hacking 0.10 patch now only ignores E128 & E265 in the E category. they are simply to fix, but they will require larger patches. i prefer to do that later22:08
hoacoles: could you check patch 202411? when you run ./.functinaltests with this patch, you can see the behaivor which you gave me an email. i would like to know whether it's run with expected or not.22:08
patchbotho: https://review.openstack.org/#/c/202411/22:08
claygpeluse_: think about it this way, if we have 10 frags of a 10+4 scheme we have enough information to return the object on GET - even with NO .durables - so how many .durables *need* to exist on a GET to return the object to the client?  all 10 for all the frags?22:08
claygnote i'm using "need" to mean theoretically - not "need" like what does the code do today.22:08
claygif *theoretically* at least we could get back with one or two .durables then in practice we'd probably be fine - but I'm not sure that's what charles is observing - i'll try to tease some more understanding from the comments22:09
peluse_clayg, well in that case none22:09
claygpeluse_: fair point!  .durables are only there for dealing with when is it safe to clean up the older version and which versions we should try to replicate!22:10
*** nadeem has quit IRC22:10
claygif the proxy could some how magically glean it can rebuild an object even without the .durable that'd be neat - but I wouldn't recommend it do so unless it thinks it will also eventually be rebuilt - but even 1 durable should be enough to eventually propogate to all the nodes22:11
claygso if the proxy can find 10 frags and 1 durable I think it "should" return it22:11
claygnote I'm using "should" there to mean - it's a worthy goal - that would prioritized agains other things that also important22:12
peluse_clayg, well that's an implementation change that's not so trivial I don't think22:12
peluse_not for going from beta-->production anyway22:12
claygpeluse_: perhaps - i think this should be done is different from what's blocking taking off a beta tag22:13
peluse_my vote would be leave it as or change the .durable requirement to something bigger like quorum which would simplify the code slightly22:13
peluse_yup22:13
peluse_but either way its not a bug - its doing what we designed it to do right now22:14
claygpeluse_: perhaps, i don't quite understand frags without durables are coming from?22:14
claygpeluse_: maybe in-progress replication/reconstruction?22:14
peluse_clayg, yeah that's what I was trying to get at with the request for exact steps to repro22:14
peluse_clayg, or nodes were taken offline at just the right time (middle of 2 phase operation)22:15
claygpeluse_: idk, to that argument you could say https://bugs.launchpad.net/swift/+bug/1457691 is not a bug22:15
openstackLaunchpad bug 1457691 in OpenStack Object Storage (swift) "EC GET w/not work with just one PUT during handoff" [High,In progress] - Assigned to Bill Huber (wbhuber)22:15
claygpeluse_: but in that case we descovered what we thought was "good enough" wasn't really "good enough"22:15
peluse_clayg, wrt the last comment I dont think so.  We said "good enough for beta" but always said we wanted to handle that sceanrio for production22:15
peluse_so maybe not a bug but still a feature gap :)22:16
peluse_eitehr way we need to fix one and not the other IMHO22:16
claygpeluse_: yeah I don't think charles has tooling to achive that kind of fine grained disablement - he's disabling nodes en masse - and finding GET's don't work when it seems like there should still be enough frags22:16
claygpeluse_: ok, I think we should have both bugs and both should be fixed - they are different priorties22:17
peluse_clayg, but he does say that there are .data's there and if he touched a .durable things worked, right?  So somehow really did have .data without the .druable22:17
claygpeluse_: the durable one I think is acctually an unknown prioirty because I don't understand the failure yet22:17
peluse_clayg, yeah, OK I can get down w/that22:17
claygpeluse_: yesh his find's show that as well - but he didn't *delete* them or anything - they are just not there - very strange22:17
peluse_clayg, could be some other bizarre bug deep down in there that's cleaning up a .durable somehow when it shouldn't :)22:18
claygpeluse_: yes, could be - i understand it's not as high a priority as others - i'm glad charz is working on it22:18
claygpeluse_: I think there's something there22:19
peluse_clayg, is he still?22:19
peluse_working on it that is...22:19
claygoff-and-on ec testing - yes - on that particuarlar issue he may be waiting for more direction22:19
claygi hadnt' digested his latest notes22:19
peluse_OK, I'll go add a note.  thanks22:19
claygpeluse_: do you have any idea where the lost durables went?22:20
claygor a theory that could be tested?22:20
peluse_into the ether maybe?  :)22:21
claygeah maybe - hard to test :\22:21
peluse_alpha particles??22:21
peluse_I dunno, but with that lens on the problem its worh another look at some of the code down there....22:22
claygok22:22
clayggood call22:22
claygtimeouts!22:22
claygthe 1x was perfect, but after the 20x run there was missing durables right out the gate22:23
claygI think the proxy is getting board waiting on the 100 on the fsync of the data file and throwing away the connection - so it never gets the finalization mime part22:24
peluse_could be...22:24
*** ChanServ sets mode: +v peluse_22:24
*** peluse_ is now known as peluse22:25
*** jasondotstar has joined #openstack-swift22:28
*** jordanP has quit IRC22:29
*** NM1 has quit IRC22:30
openstackgerritVictor Stinner proposed openstack/swift: Update hacking to 0.10.0  https://review.openstack.org/20597722:32
openstackgerritVictor Stinner proposed openstack/swift: Fix pep8 E warning for hacking 0.10  https://review.openstack.org/20723722:32
openstackgerritVictor Stinner proposed openstack/swift: Fix pep8 E265 warning of hacking 0.10  https://review.openstack.org/20724222:32
openstackgerritVictor Stinner proposed openstack/swift: Fix warning pep8 E128 warning of hacking 0.10  https://review.openstack.org/20724322:32
*** jrichli has quit IRC22:32
claygpeluse: we'll see if charz can repeat the test and dig into those missing frags just a little bit more22:33
clayger... s/missing frags/frags missing durables/22:34
haypooooh, here you have my new patch serie for hacking 0.10 --^22:34
clayghaypo: that's per fact man - thanks - checking out now22:40
*** flwang1 has joined #openstack-swift22:43
flwang1greetings. anybody know how to create a role to support read only? thanks a lot22:44
claygx-container-read: acl?22:44
flwang1clayg: does that mean i have to set the acl for each container?22:45
*** esker has quit IRC22:46
claygyeah that's how an acl would work; i'm not sure if non admin role is supported with current keystone - probably?  if not alsmost definately with ho's policy.json patch22:46
flwang1seems swift doesn't support the policy.json like most the other components did22:46
claygflwang1: true!22:46
*** fds_ has joined #openstack-swift22:47
flwang1clayg: ho's policy.json patch??? in reviewing?22:47
claygyeah, i was just looking for it :\22:47
flwang1clayg: the scenario is we would  like to have two roles in keystone, both of them are swift only roles, one can r+w, one only can do read22:48
notmynamehttps://review.openstack.org/#/c/149930/22:48
*** nadeem has joined #openstack-swift22:49
*** lcurtis has quit IRC22:50
flwang1notmyname: cool, cheers22:50
flwang1so seems for now, i have to use the x-container-read22:50
flwang1but as for the swift only role, like creating swiftoperator in keystone, I think i can just replace the Member role in proxy_server.conf with operator_roles = admin, swiftoperator22:51
flwang1then it should work, right?22:52
hoflwang1, clayg: yeah, thanks clayg for the review. now i'm stacked for patch 202411 (presupposition of the policy.json patch) :)22:52
patchbotho: https://review.openstack.org/#/c/202411/22:52
flwang1any swift guy can give me a confirmation ? :)22:53
hoflwang1: i think i can help you22:53
flwang1ho:  (10:51:54 AM) flwang1: but as for the swift only role, like creating swiftoperator in keystone, I think i can just replace the Member role in proxy_server.conf with operator_roles = admin, swiftoperator22:53
flwang1(10:51:59 AM) flwang1: then it should work, right?22:53
*** minwoob has quit IRC22:54
hoflwang1: you are right!22:54
flwang1ho: awesome, thanks a lot22:54
*** nadeem has quit IRC22:54
flwang1ho: you're policy.json patch will be really helpful for my 2nd case22:54
flwang1looking forward to seeing it in22:55
*** nadeem has joined #openstack-swift22:55
hoflwang1: thanks! i try to do my best!22:55
hoflwang1: 2nd case means read only? in this case using container acl as clayg mentioned is only way now.22:57
*** flwang1 has left #openstack-swift22:57
*** flwang1 has joined #openstack-swift22:59
claygho: container acl is the only way!?  :'(22:59
flwang1ho: yep, i see22:59
claygho: no wonder you're working so hard on policy changes22:59
flwang1ho: but after merged the policy.json patch22:59
claygwhat does the operator_roles buy you?22:59
flwang1i think we can just create a new role like swift-readonly23:00
flwang1and then update the policy.json, then all done23:00
*** 16WAAEHWP has quit IRC23:01
flwang1clayg:  the operator_roles  can only make sure a role has permission for swift, but it can't get a more granular control, like read, write, isn't it?23:02
*** haomaiwang has joined #openstack-swift23:02
*** km has joined #openstack-swift23:05
*** jlhinson has quit IRC23:06
*** blair has quit IRC23:07
hoclayg: with current logic i think so. swift has three type of role now, reseller_admin_role, operator_roles and no role. if a role has a right to have write access to a container, the role also can have read access to the container.23:07
*** blair has joined #openstack-swift23:08
hoflwang1: i think your approach will be worked soon.. hopefully. :)23:12
*** annegentle has joined #openstack-swift23:28
*** cdelatte has joined #openstack-swift23:28
*** delattec has quit IRC23:30
*** hrou has joined #openstack-swift23:31
*** kei_yama has joined #openstack-swift23:32
*** fds_ has quit IRC23:32
*** jasondotstar has quit IRC23:33
*** jamielennox is now known as jamielennox|away23:39
*** nadeem has quit IRC23:43
*** nadeem has joined #openstack-swift23:43
*** jasondotstar has joined #openstack-swift23:46
*** darrenc is now known as darrenc_afk23:47
*** nadeem has quit IRC23:50
*** Kennan2 is now known as Kennan23:53

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