Friday, 2014-05-30

*** gyee has quit IRC00:01
*** mwstorer has quit IRC00:01
claygcreiht: peluse_: notmyname: so on the case insenitive names, it seems to make the most sense to use the name as it appears in swift.conf verbatium in responses, and only apply "insensitivity" to client requests and handling duplicate names?00:04
claygok, so hopefully liberal in what we except and strict in what we respond applies00:08
notmynameaccept00:08
claygthe /info response will include *exactly* what you put in swift.conf00:08
notmynameto confim in IRC what I said in the office..00:09
notmynameclayg: +1 that sounds right00:09
claygwhen you get a policy name in a header it's title case normalized00:09
peluse_ditto00:14
claygpeluse_: currently discussing with notmyname if _ should be valid in a policy name00:14
claygi added one and the response from account is X-Account-Storage-Policy-Gold_Stuff-Bytes-Used00:14
notmynamedo we allow it in metadata keys now?00:15
peluse_kinda wierd00:15
claygwhich swift/eventlet seem fine with - but i don't know if the header would be dropped if you stuck some weird http terminating/load-balancing device in the mix00:15
notmynamehttps://gist.github.com/notmyname/2b2b1e7c361a729927b400:16
notmynameso we do weird stuff00:16
notmynameset a metadata key with an underscore and we change it to a dash00:16
claygi think again the strict response may tell us that we should convert _ to - in the account response, and also enfoce you can't have Policy_0 and policy-0?00:16
notmynameclayg: ie normalization is .replace('-','_').upper()00:17
claygprobably - did you see where the swift is doing that for the metadata keys?00:17
notmynameclayg: no, not in the code yet.00:18
*** zhiyan_ is now known as zhiyan00:20
*** judd7 has joined #openstack-swift00:20
zaitcev"a daemon ... works tirelessly to identify and rectify this potential scenario."00:23
claygzaitcev: too much prose in there for you?00:23
claygzaitcev: or anthropomorphism00:24
zaitcevclayg: I think the prose is not appropriate in a document of such kind.00:24
notmynameclayg: swob does it00:25
notmynamechanges _ to -00:25
claygnotmyname: well then why doesn't it do it in header response from account server when I have a storage policy name with a _?00:25
claygI'm feeling more and more like I should force the values in swift.conf to be titlecase and - only?00:26
notmynamewell it's not super straightforward...00:26
*** kashyapk has joined #openstack-swift00:27
notmynameclayg: looks like any swob.Request.headers.keys() will replace _ with -00:28
*** zhiyan is now known as zhiyan_00:29
*** dmorita has joined #openstack-swift00:30
*** matsuhashi has joined #openstack-swift00:30
*** kashyapk has quit IRC00:32
peluse_clayg:  I agree with you, I don't think changing the name of a policy on someone is a good idea00:33
peluse_I'd be like "WTF?"00:33
notmynamebah. swob.Request.headers = HeaderEnvironProxy which does the translation. swob.Response.headers = HeaderKeyDict which only does the title case00:34
claygnotmyname: so it's fine I can normalize the header in the account server response (which is the only place we stuff the name into a header *key*)00:35
notmynameclayg: peluse_: so if policy.name = "thisIs_a_GOLD_policy" you'd error?00:35
claygnotmyname: maybe, or just make it Thisis-A-Gold-Policy and call it a day00:35
claygpeople who like to use CamelCase are going to be mad though :\00:35
notmynameclayg: and make it that way everywhere. no matter what's in swift.conf00:36
claygnotmyname: somethign like that is one option yeah00:36
notmynamefor a second choice, that's ok. the consistency is important I think00:36
peluse_you can please some of the people all of the time, all of the people some of the time... but00:36
* peluse_ heads out for some grub,,, back later00:38
notmynamepeluse_: and all of the people all of the time, if you are a dictator00:38
peluse_:)00:38
*** ozialien has quit IRC00:42
*** shri has quit IRC00:47
*** Edward-Zhang has quit IRC00:48
*** zhiyan_ is now known as zhiyan00:50
claygsweet underscores are out - for reasons00:54
*** zhiyan is now known as zhiyan_00:59
*** zhiyan_ is now known as zhiyan01:09
*** ujjain has quit IRC01:15
*** swat30 has quit IRC01:15
*** Thurloat has quit IRC01:16
creihtclayg: agreed01:19
claygso i guess since we accept spaces and utf-8 in metadata keys they're ok in policy names01:19
*** ujjain has joined #openstack-swift01:19
creihtlol01:22
creihtthat doesn't mean we have to support that01:22
creihtutf-8 policy names seem problematic01:22
creihtmaybe we should only support uuids :)01:22
claygcreiht: yeah idk, someone is going to have a trademark on something and want that to be their storage policy name - i don't know if it's a good idea, but I don't how much we need to hold peoples hands either?01:23
creihthah01:24
zaitcevHow do you post spaces into X-Storage-Policy-A space B-Object-Count:01:26
claygzaitcev: same way you do for X-Account-Meta-Something something: Foo ???01:27
claygzaitcev: anyway, the name of the storage policy is normally a header *value* - but we stick it into the header keys of the account response for per policy object/byte counts - well... i guess you saw that01:28
claygzaitcev: but you don't POST those values anymore than you do X-Account-Object-Count01:28
clayger... POST those keys01:28
claygheh /info response is json so utf comes back unicode literal yay!01:29
creihtlol01:29
*** diegows has quit IRC01:30
claygipyt01:31
clayghrmm... so ConfigParser returns encoded byte array and in python3 it's just a "str" (which are always unicode i guess)01:37
*** Edward-Zhang has joined #openstack-swift01:42
*** nosnos has joined #openstack-swift01:47
claygso I think the most defensible posistion is to be overly restrictive with a nod that it could more easily be expanded than contracted01:57
*** swat30 has joined #openstack-swift02:00
*** NM has joined #openstack-swift02:01
*** nthacker has joined #openstack-swift02:02
nthackerhi all, so i noticed some bugs have patches in them, but they are still open....the patch looks like they fix the issues02:03
nthackerso im curious if the fix can be pushed by the patch owner? or someone can just test it and push it on behalf of the patch author?02:03
nthackerjus curious here....02:03
nthackersince i was looking to fix some bugs myself :P02:03
zaitcevask the guy who worked on the patch, and if he agrees or not responsive, submit it to Gerrit.02:04
*** NM has quit IRC02:04
nthackerzaitcev: Ok, thanks - ask him where? here? or email?02:04
claygnthacker: i think sometimes the bugs with patches don't really include test cases, or cover all corner cases - so it'd be great to get something up in a review - but it make take some additional work beyond just submitting the patch file02:05
claygbut in either case no, I don't think you need to wait on the bug author to submit the patch - or even contact them - if you put the "fixes #<bug-number>" in the commit I think bots are supposed to comment on launchpad02:05
nthackerclayg: Ok. that makes sense. actually i think it was your patches, but I'll try out the patch and verify testing with whatever cases i can come up with02:06
nthackerclayg: dont all checkins need to be reviewed in gerritt?02:06
claygyeah... there's a "submitting to openstack" page out there on the internet somewhere02:07
*** swat30 has quit IRC02:08
claygpeluse_: so I acctually like Policy-0 now... it's like idk... the beginning of everything, or Unimatrix Zero or something02:09
claygI couldn't see it somehow when it was Policy_002:10
*** ozialien has joined #openstack-swift02:12
mattoliveraunthacker: if you are submitting someone else's patch and/or adding to someone's patch then add a 'co-authored-by'. So the orginal author is referenced.02:14
claygmattoliverau: he's taking a .patch file attached to an lp bug and trying to get it into gerrit02:15
mattoliverauFair enough, but did he write the code? if not, when we submits it, it'll be in his name, and unless he has the original authors aporoval there can be legal ramificaitons.. I only know this because someone spoke up about a similar issue (complained) to one of the cores in the infra channel a while ago (pre-summit). The summit also had discussions about it (in the CLA metting). The CLA states that any02:21
mattoliveraucode you submit you have the right to. (in fancier terms of course :P). So by adding the co-auther bit gives them reconition for their work.02:21
claygi think if you attach a .patch to a bug report you're giving up copy-right - otherwise you should inclue a license file with the .patch02:22
claygbut INAL02:22
mattoliverauclayg: very true02:23
claygit's probably more complicated if you've signed the CLA and submitted the patch to gerrit and then someone wants to take over that change - worse if they remove any CopyRight lines you added to the change before it got approved/merged02:24
mattoliverauclayg: that was closer to the situation that happened a few months ago. Someone took the contents of anoher gerrit patch, added to it and submitted it as there work. The original change might have also been abandoned, I can't remember. So maybe LP patch is different. But still I think it's better safe then sorry :)02:26
mattoliverauAnd hey it's only 1 line at the end of the commit message :)02:26
nthackermattoliverau: ok thanks - yes i actually agree with that style02:34
gholtMan, you guys keep thinking of great stuff I'm not catching. Case insensitive policy names, don't overly lazy load rings (if at all), etc.02:42
claygcreiht's good at the api stuff02:43
claygdfg's good at the not be horribly broken stuff02:43
gholtHeheh02:43
clayggo team swift!02:43
zaitcevI'm good at nitpicking02:43
zaitcev*puppyeyes*02:44
gholtI don't know about the schema thing. I think all the schema stuff has been in the backend area from the start so it just seemed logical to be there to me.02:44
gholtHaha, and zaitcev chimes in right when I'm talking about one of his complaints. :)02:44
clayggholt: did I leak some schema stuff out of backend? :\02:45
*** matsuhashi has quit IRC02:45
gholtWell, earlier today you said you were going to fart types; but you weren't really in the mood for that 5-year-old humor. ;D02:45
creihthehe02:46
zaitcevclayg: I haven't seen the code yet. I just think it was underdocumented.02:46
claygi can't tell if you guys are messing with me02:46
gholtAssume always.02:47
*** haomaiwa_ has joined #openstack-swift02:47
creihtlol02:47
*** swat30 has joined #openstack-swift02:48
zaitcevexcept me. I never mess with people... in English02:48
zaitcevI can place a play-doh on your chair though02:48
claygi don't know what to say... i'm just trying to keep high spirts while we noodle around with docs and config file parsing - cause the really good stuff is yet to come02:48
clayglol02:48
creihtclayg: yeah we are getting there02:48
gholtzaitcev: :) Yeah... right. Of course, you might not think you're missing with people; it's just your way.02:48
creihttakes some time to digest everything02:48
creihtthat sounds like a book02:49
creiht"The Way of Zaitcev"02:49
claygyeah... honestly I've always felt it takes longer to review code than to write it - and this crap took like what?  a year?  we're screwed02:49
creihtlol02:49
claygyou all are doing great though thanks for everyone coming together... gholt's right we're still gunna be at in CO - but then you guys can throw stuff at me02:50
claygso the more we get done tomorrow the better i suppose02:50
claygah crap... i was gunna get the policy_string munge on q/tmp dirs in with tonights rebase02:50
zaitcevI thought we ought to complete SP reviews before Longmont and focus on EC there.02:50
claygstupid unicode02:50
zaitcevI know I'm behind on this02:50
claygzaitcev: i'd like to mostly just talk about PBE next week :D02:51
claygs/talk/work-on/02:51
creihtPBE?02:51
zaitcevclayg: Constantin poked me about some changes in PBE. He wants some method protocols changed to accomodate ZeroVM better.02:51
creihtoh yeah02:51
claygzaitcev: oh ok... good!02:52
creihtclayg: I was thinking maybe we should spend one day doing a policies code roast02:52
creihtor half day02:52
creihtwhatever it takes02:52
claygcreiht: i don't even know if that will be enough...02:54
creihtheh02:54
*** haomaiwa_ has quit IRC02:55
*** haomaiwang has joined #openstack-swift02:55
clayggholt: zaitcev: oh you guys were asking about the thing where the auditor will automatically upgrade legacy schemas as it finds them instead of leaving them unmigrated forever until a write forces it?02:56
zaitcevclayg: I was02:56
clayggholt: zaitcev: I'm pretty sure we want to force it... the container_sync schema change can like sit around forever (if you're not running the container-sync daemon) - and every get_info on those db's has to get the sqlite exception, trap it and retry the query.02:57
zaitcevclayg: I don't see a problem with it, and docs mention it in passing right at the end, but I thought it needed some kind of acknowledgement, like the way the new table for account was.02:57
*** shakayumi has quit IRC02:58
claygoh... yeah... maybe... probably something updated on the page that talks about how the auditors work - oh wait... where is that page?02:58
zaitcevclayg: my plan was actually consider those notes I left as margin marks and get back to them when I saw the actual code02:58
claygzaitcev: we'll they'll get burried in tonights rebase if I don't address them somehow02:59
claygzaitcev: do you want a sentence that says something like "Policies were not implemented at the account level because of the overhead of adding support to all legacy auth systems"?03:03
*** nthacker has quit IRC03:03
zaitcevclayg: Something like that. Because I thought they were not because of existing users who have single sign-on or other and need access to 2 policies while only having 1 account.03:04
claygyeah basically - but that's sort of a specific subset03:04
claygzaitcev: what does "one -s" mean03:08
zaitcevthings happens03:08
zaitcevIs "Storage Policies" singular or plural?03:08
claygi.... don't know?03:09
claygs/fits/fit/ maybe?03:09
*** ozialien has quit IRC03:10
*** haomaiw__ has joined #openstack-swift03:12
*** haomaiwang has quit IRC03:13
claygzaitcev: re downgrade - it won't work03:25
zaitcevclayg: so... doc change?03:26
zaitcevpersonally I'm okay with no downgrade, although operators may be not as enthusiastic, in case they hit any regressions03:26
claygzaitcev: yeah well i'm just gunna say "don't" for now... i guess the change log will need something a bit more scary or... idk... maybe i'll have to do something in the triggers... but it's gunna be slower :\03:27
*** haomaiwa_ has joined #openstack-swift03:27
claygdamn03:27
*** ppai has joined #openstack-swift03:28
claygok ok ok, it's not that bad... maybe03:28
claygwe could test it03:28
claygi mean the old code maybe won't report bytes and counts correctly - but the triggers should still be doing the right thing03:30
*** mrsnivvel has joined #openstack-swift03:30
*** haomaiw__ has quit IRC03:30
zaitcevwell we can just cross ourselves and jump into it, and deployers usually do not downgrade anyway03:36
zaitcevwe need to be sensitive to small stuff like that DB cursor thing03:36
claygI don't really have a good answer03:39
*** nosnos has quit IRC03:40
claygzaitcev: I think i was able to address most of your comments except why not a new config file... frankly that decsion was made before I started working on policies - so you might have to ask peluse_ or torgomatic03:43
claygzaitcev: I think we could change it, but I don't really see it as necessary03:43
*** matsuhashi has joined #openstack-swift03:47
*** matsuhashi has quit IRC03:54
*** matsuhashi has joined #openstack-swift03:54
*** matsuhashi has quit IRC03:57
*** matsuhashi has joined #openstack-swift03:58
*** matsuhashi has quit IRC04:03
*** matsuhashi has joined #openstack-swift04:03
*** zaitcev has quit IRC04:17
*** psharma has joined #openstack-swift04:22
*** kashyapk has joined #openstack-swift04:33
*** nosnos has joined #openstack-swift04:42
*** swat30 has quit IRC05:01
*** zhiyan is now known as zhiyan_05:13
*** zhiyan_ is now known as zhiyan05:35
*** zhiyan is now known as zhiyan_05:47
*** ZBhatti has quit IRC05:59
*** zhiyan_ is now known as zhiyan06:03
*** saurabh_ has quit IRC06:10
*** zhiyan is now known as zhiyan_06:19
*** zhiyan_ is now known as zhiyan06:20
*** ujjain has quit IRC06:21
*** ujjain has joined #openstack-swift06:21
*** matsuhashi has quit IRC06:30
*** matsuhashi has joined #openstack-swift06:31
mattoliverauwell im going to call it a day, and a week! have a great weekend all!07:04
*** zhiyan is now known as zhiyan_07:06
*** matsuhashi has quit IRC07:11
*** matsuhas_ has joined #openstack-swift07:16
*** matsuhas_ has quit IRC07:16
*** zhiyan_ is now known as zhiyan07:17
*** matsuhashi has joined #openstack-swift07:17
*** sungju has quit IRC07:28
*** nshaikh has joined #openstack-swift07:43
*** haomaiwa_ has quit IRC07:45
*** haomaiwang has joined #openstack-swift07:46
*** haomai___ has joined #openstack-swift07:49
*** haomaiwang has quit IRC07:53
*** nacim has joined #openstack-swift07:55
*** scotticus has quit IRC07:56
*** scotticus has joined #openstack-swift08:02
*** Midnightmyth has joined #openstack-swift08:18
*** bvandenh has joined #openstack-swift08:19
*** zhiyan is now known as zhiyan_08:25
*** zhiyan_ is now known as zhiyan08:47
*** zhiyan is now known as zhiyan_08:49
*** haomai___ has quit IRC08:52
*** haomaiwang has joined #openstack-swift08:53
*** Edward-Zhang has quit IRC09:03
*** nshaikh has quit IRC09:11
*** haomaiwang has quit IRC09:18
*** haomaiwang has joined #openstack-swift09:19
*** mkollaro has joined #openstack-swift09:22
*** nshaikh has joined #openstack-swift09:28
*** Midnightmyth has quit IRC09:35
*** mrsnivvel has quit IRC09:37
*** Midnightmyth has joined #openstack-swift09:42
*** mrsnivvel has joined #openstack-swift09:48
*** zhiyan_ is now known as zhiyan09:49
*** dmorita has quit IRC09:55
*** kashyapk has quit IRC09:58
*** zhiyan is now known as zhiyan_09:59
*** kashyapk has joined #openstack-swift09:59
*** hxgqh1987 has joined #openstack-swift10:07
*** hxgqh1987 has quit IRC10:07
*** matsuhashi has quit IRC10:16
*** matsuhashi has joined #openstack-swift10:21
*** matsuhashi has quit IRC10:27
*** matsuhashi has joined #openstack-swift10:28
*** haomaiwang has quit IRC10:32
*** haomaiwa_ has joined #openstack-swift10:33
*** haomaiw__ has joined #openstack-swift10:35
*** haomaiwa_ has quit IRC10:39
*** zhiyan_ is now known as zhiyan10:50
*** zhiyan is now known as zhiyan_10:59
*** matsuhashi has quit IRC11:00
*** matsuhashi has joined #openstack-swift11:00
*** kashyapk has quit IRC11:01
*** kashyapk has joined #openstack-swift11:02
*** NM has joined #openstack-swift11:02
*** kashyapk has quit IRC11:03
*** kashyapk has joined #openstack-swift11:04
*** matsuhashi has quit IRC11:05
*** kashyapk has quit IRC11:06
*** kashyapk has joined #openstack-swift11:07
*** kashyapk_ has joined #openstack-swift11:08
*** NM has quit IRC11:08
*** matsuhashi has joined #openstack-swift11:09
*** Midnightmyth has quit IRC11:11
*** kashyapk has quit IRC11:12
*** openstackgerrit has joined #openstack-swift11:18
*** openstackgerrit has quit IRC11:19
*** openstackgerrit has joined #openstack-swift11:24
*** openstackgerrit has quit IRC11:25
*** openstackgerrit has joined #openstack-swift11:25
*** mlipchuk has joined #openstack-swift11:30
*** mlipchuk has quit IRC11:48
*** zhiyan_ is now known as zhiyan11:51
*** swat30 has joined #openstack-swift11:52
*** haomaiw__ has quit IRC11:52
*** matsuhashi has quit IRC12:00
*** zhiyan is now known as zhiyan_12:00
*** matsuhashi has joined #openstack-swift12:00
*** Midnightmyth has joined #openstack-swift12:01
*** matsuhashi has quit IRC12:02
*** matsuhashi has joined #openstack-swift12:02
*** bvandenh has quit IRC12:03
*** diegows has joined #openstack-swift12:05
*** matsuhashi has quit IRC12:12
*** matsuhashi has joined #openstack-swift12:13
*** matsuhashi has quit IRC12:13
*** openstackgerrit has quit IRC12:22
*** openstackgerrit has joined #openstack-swift12:22
*** Thurloat has joined #openstack-swift12:26
*** lpabon has joined #openstack-swift12:31
*** lpabon has quit IRC12:31
*** ppai has quit IRC12:37
gholtHeh, "deleting the policy and associated rings would be problematic for existing data." Or maybe nearly catastrophic.12:38
*** nosnos has quit IRC12:40
*** haomaiwang has joined #openstack-swift12:46
*** zhiyan_ is now known as zhiyan12:51
*** zhiyan is now known as zhiyan_13:03
gholtclayg: notmyname: Oh man, reviewing updates is going to be difficult as hell. ;) It was easy for the top level patchset, but the dependent ones... Can't just diff the previous patchset to the current since that contains everything from the dependency too. Hmm.13:04
*** psharma has quit IRC13:08
gholtI have a solution, albeit cumbersome. In this example, I'll be reviewing the changes to 96027 from its previous patchset 3:13:14
gholtFirst, I check out the current patchset and name that branch "rev96027".13:15
gholtThen I check out the dependency and name that branch "rev96026".13:15
gholtNext I check out the previous patchset 3 of 96027 and name that "anchor".13:15
gholtNow I do a "git log" to figure out the commit hash for the previous 96026 dependency in that particular version of history and "git revert" it.13:15
gholtNext up, I "git merge rev96026" into that branch (still on "anchor" at this point).13:15
gholtNow I can "git checkout rev96027" and do a "git diff anchor" and see the changes, yay!13:15
*** kashyapk_ has quit IRC13:17
*** kashyapk has joined #openstack-swift13:17
gholtI'm reminded of the saying, "If it was a pain in the ass to write, it should be a pain in the ass to read!"13:19
*** NM has joined #openstack-swift13:22
*** kenhui has joined #openstack-swift13:26
*** judd7 has quit IRC13:27
*** mrsnivvel has quit IRC13:28
*** haomaiwang has quit IRC13:29
*** haomaiwa_ has joined #openstack-swift13:29
*** haomaiw__ has joined #openstack-swift13:31
*** Diddi has quit IRC13:35
*** haomaiwa_ has quit IRC13:35
gholtDamn, this won't work well paste the second item in the chain though. I'm on the third now and it's... much worse.13:35
*** tdasilva has joined #openstack-swift13:37
*** kashyapk has quit IRC13:37
gholtHave to revert two commits from the old patchchain and merge in the two new commits from the new patchchain, but there are conflicts trying to the reverts and probably would be conflicts merging in the new stuff. It'll almost be impossible to review the diffs from each patchset individually unless someone comes up with something amazing I'm not thinking of.13:37
*** kashyapk has joined #openstack-swift13:37
gholtI'll just pause for a while and see what folks think of as it's currently nearly impossible for me to tell what changed from patch to patch in 96208 for example.13:39
peluse_we'll talk more at the hackathon but now seems like a good time to plug the strategy of not using an integration branch for the EC work... straight to master with the EC policy disabled until complete...13:40
gholtI might be able to diff diffs and work from there, though that might also be a mess.13:44
acolesgholt: had the same sinking feeling myself this morning13:47
acolesgholt: but how about this...13:47
acolescreate branch from master, then use the cherry pick command from gerrit for e.g. 96027/313:48
acolescreate another branch_2 from master, cherry pick 96027/413:49
acoleson branch2, diff branch113:49
acolesi *think* i see only the relative changes on 9602713:50
gholtI'm not sure you can cherry pick for things that truly depend on the prior commits though right?13:50
acolesgholt: i'm not expecting tests to pass, just hoping to see what changed between versions of that patch13:54
*** zhiyan_ is now known as zhiyan13:54
gholtYeah, I'm just not sure the cherrypick would even succeed though.13:55
gholtThe diff of diffs seems to work reasonably okay.13:56
acoleshmm, maybe further up the chain it will fall down13:56
acolescherrypick i mean13:56
*** jergerber has joined #openstack-swift13:56
gholtFor example, the diff of diffs shows, I think ;), that nothing changed specifically for 96028.13:56
acolesgholt: put a comment on that one then :)13:57
*** haomaiw__ has quit IRC14:03
*** haomaiwa_ has joined #openstack-swift14:03
*** zhiyan is now known as zhiyan_14:03
gholtDamn, my diff of diffs seems to have fallen down at 96030; could just be user error though, which is quite likely for this messy sort of thing.14:06
gholtI guess I could just only work from the end of the chain, but then why bother having clayg split it all up. Even though it's a bit harder to really get going on the reviewing, it's probably just better to have one big commit.14:08
tdasilvagholt and others: if I run a "review -d" of the last commit, will that pull all the other commits? is that how are you guys testing this?14:10
gholttdasilva: Yes14:10
gholtgit review -d 9604914:11
tdasilvagholt: ok, thanks14:11
gholtacoles: Oh, and it's made worse in that some of these have multiple patchsets per day as clayg and peluse_ work through things.14:12
gholtFor example, it seems like there are zero changes in the last patchset for 96049.14:15
gholtThat doesn't seem right, but maybe, just maybe, only a commit message somewhere changed on that one?14:16
*** judd7 has joined #openstack-swift14:20
*** haomaiw__ has joined #openstack-swift14:21
gholtPoor guys. Someone had to be first to walk us through this sort of thing. Heh14:22
*** shakamunyi has joined #openstack-swift14:22
*** haomaiwa_ has quit IRC14:23
acolesgholt: we need another button in gerrit :)14:24
creihtis anyone going to the hackathon flying back on friday?14:27
*** openstackgerrit has quit IRC14:36
*** openstackgerrit has joined #openstack-swift14:36
peluse_creiht:  I'm flying home Thu eve14:43
creihtI have to fly back on Friday and wanted to see if anyone might be able to give me a ride :)14:44
*** kashyapk has quit IRC14:46
*** kashyapk has joined #openstack-swift14:47
portantecreiht: sorry, flying back Thu night red eye14:47
peluse_I'm getting in Sun afternoon and getting a few things ready in the office if anyone is in early enough for dinner at 6ish or 714:49
*** kenhui has quit IRC14:49
*** kenhui has joined #openstack-swift14:49
*** kashyapk has quit IRC14:51
openstackgerritpaul luse proposed a change to openstack/swift: Make quarantine and tmp dirs in DiskFile Storage Policy Aware  https://review.openstack.org/9631314:51
portantepeluse_: coming in at 10:15 PM to Denver, sorry14:52
*** zhiyan_ is now known as zhiyan14:55
acolespeluse_: arrive sun pm too late for dinner sorry creiht: leave late thurs14:56
creihtno worries, I think I have it figured out14:57
creihtpeluse_: yeah I don't get in until late sunday as well14:57
*** zhiyan is now known as zhiyan_15:04
acolesgholt: i have been playing with this to show me what changed between versions on a patchset http://paste.openstack.org/show/82196/15:09
*** haomaiw__ has quit IRC15:10
*** kenhui1 has joined #openstack-swift15:10
*** haomaiwang has joined #openstack-swift15:10
* acoles waits for someone to point out a more elegant solution15:11
dfgon the plus side the review process is so complicated that the actual code change seems pretty straight forward15:12
peluse_I hear that!15:12
creihthaha15:13
*** kenhui has quit IRC15:13
*** haomaiw__ has joined #openstack-swift15:14
acoles:)15:15
* peluse_ is stepping away for 90 min or so...15:15
*** haomaiwang has quit IRC15:17
*** ozialien has joined #openstack-swift15:48
openstackgerritpaul luse proposed a change to openstack/swift: Make quarantine and tmp dirs in DiskFile Storage Policy Aware  https://review.openstack.org/9631315:49
*** Midnightmyth has quit IRC15:55
*** zhiyan_ is now known as zhiyan15:56
*** ozialien has quit IRC16:02
openstackgerritYuan Zhou proposed a change to openstack/swift: Update swift-object-info/swift-get-nodes to be storage policy aware  https://review.openstack.org/8273416:04
*** zhiyan is now known as zhiyan_16:05
*** haomaiw__ has quit IRC16:07
*** haomaiwa_ has joined #openstack-swift16:07
*** mwstorer has joined #openstack-swift16:10
*** Midnightmyth has joined #openstack-swift16:13
*** haomaiw__ has joined #openstack-swift16:17
*** haomaiwa_ has quit IRC16:18
*** shakamunyi has quit IRC16:20
openstackgerritOpenStack Proposal Bot proposed a change to openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925016:33
*** Ju has quit IRC16:52
*** shri has joined #openstack-swift16:53
*** NM has quit IRC16:55
*** zhiyan_ is now known as zhiyan16:56
*** as_ has joined #openstack-swift17:00
creihtpeluse_, clayg: Why did we need a separate policy stat table in the container?17:00
*** kashyapk has joined #openstack-swift17:00
notmynamegood morning. just got done talking about swift in an HP podcast :-)17:04
*** ozialien has joined #openstack-swift17:04
*** nacim has quit IRC17:06
*** zhiyan is now known as zhiyan_17:06
as_does anybody know swiftbrowser? my problem is: when I try to upload something from the swiftbrowser, gets me to that url: https://MYIPHERE:8076/v1/AUTH_system/Test/17:07
as_And I get 401 error17:07
as_Unauthorized17:07
as_This server could not verify that you are authorized to access the document you requested.17:07
as_I've tried with CloudBerry, works perfectly.. so this should be swiftbrowser problem17:08
notmynameas_: hmmm17:08
notmynameas_: can you give me a link to the swiftbrowser you are using? (just want to make sure what I'm assuming you are using is actually what you are using)17:08
as_https://github.com/cschwede/django-swiftbrowser/tree/master/swiftbrowser17:09
notmynameas_: ah yes. you should talk to cschwede_ then :-)17:09
as_uhm, ok thanks :p17:09
notmynameas_: that is, he's in here. and he's on central euro time (IIRC), so it's kinda late for him now, but he should see it.17:10
as_will send him an e-mail :D thank you for your time; have a good day!17:11
*** as_ has quit IRC17:11
*** miqui has quit IRC17:18
*** erlon has quit IRC17:19
peluse_creiht:  because we're keeping a row of stats per policy17:19
*** NM has joined #openstack-swift17:20
notmynamecreiht: did you see this? how LEDs are made https://learn.sparkfun.com/tutorials/how-leds-are-made/all17:21
peluse_creiht:  also note that the table is in the acct DB (you mentioned container) and is analagous to account_stat17:25
*** miqui has joined #openstack-swift17:29
creihtnotmyname: yeah17:44
creihtpeluse_: ok, but a single container can only have one policy right?17:44
creihtpeluse_: I'm looking at: https://review.openstack.org/#/c/96029/6/swift/container/backend.py17:44
creihtPOLICY_STAT_TABLE_CREATE17:45
*** nshaikh has quit IRC17:52
* peluse_ is looking17:52
*** NM has quit IRC17:55
peluse_creiht:  so that's not where that code is supposed to be....17:55
peluse_I'm really confused17:55
creihtheh17:55
peluse_that's not where it is on feature/ec (and not where it I added it)....17:56
creihtodd17:56
creihtI'll leave a note for now and let yall sort it out17:56
peluse_creiht:  thanks, I'm sure clayg knows what's up there17:57
*** zhiyan_ is now known as zhiyan17:57
creihtpeluse_: in my full pull of code, the account backend has a create_policy_stat_table17:59
peluse_creiht:  yeah, that's the one I did.17:59
peluse_creiht:  clayg must have added this one in the last few weeks18:00
creihtk18:00
creihtI'll wait for some clarity from clayg18:01
*** zaitcev has joined #openstack-swift18:01
*** ChanServ sets mode: +v zaitcev18:01
peluse_creiht:  yeah, here's the one I did https://review.openstack.org/#/c/96041/ so its totally different18:03
peluse_and that one ^ is several patches downstream in the set...18:04
*** gyee has joined #openstack-swift18:04
*** kashyapk has quit IRC18:06
*** zhiyan is now known as zhiyan_18:06
*** kashyapk has joined #openstack-swift18:07
*** NM has joined #openstack-swift18:10
*** kashyapk has quit IRC18:11
creihtnotmyname: on a weird side note, I tried recreating all of my notification settings in gerrit.  I get emails for updates for every one, except swift proper18:20
notmynamecreiht: oh fun. just what you wanted :-)18:21
creihtheh18:22
creihtnotmyname: well be clear, the other updates are the other ones that I signed up for18:29
creihtI just don't get the updates for swift which I also tried to sign up for again18:29
creihtI think everyone might have discussed this earlier18:40
creihtbut why do we have constants for the policy header keys, but we don't for any of the others?18:40
clayghrm... was having some computer trouble this morning18:47
claygmight be working now, it seems i've got some comments to go through - thanks all18:47
creihtclayg: howdy :)18:48
claygcreiht: the policy_stat table was added to the container to deal with object rows from different storage policies18:51
creihthrm18:51
creihtseems like a lot of overhead just for that plus the backwards incompatibility18:52
claygcreiht: yup18:53
creihtbecause that's just for when you get split brained containers right?18:53
claygcreiht: well... yeah18:53
creihtok I need to think about that for a bit, it would prefer if we didn't need the extra policy_stat table in the container18:54
creihts/it/I18:54
claygcreiht: i would have preferred that as well - and fought against it for a long time before I finally gave into the inevitble conclusion18:55
creihtheh18:55
creihtyeah that's why I need to think about it a bit to see if I can come up with a better solution to that issue18:55
claygcreiht: ok, well I'll document the other solutions i explored - maybe you'll have better ideas on how they could have been made to work.18:56
creihtk18:56
*** haomaiw__ has quit IRC18:58
*** zhiyan_ is now known as zhiyan18:58
creihtclayg: what about the constants for the policy headers?19:01
creihtI think this might have been covered earlier19:02
creihtbut why do we have them when no other headers have constants?19:02
claygoh heh, so you wanted to drop the constants and go with string literals - funny.19:02
creihtwell, I prefer to be consistent :)19:02
creihtI don't have a real strong preference one way or another19:03
creihteach way has advantages/disadvantages19:03
claygeveryone else seemed to think it was better to have something flake8 could check - notmyname's only concern was that the constants' names didn't indicate they were headers.19:03
claygI believe the concensus was to keep them, but rename to POLICY_HEADER and POLICY_INDEX_HEADER19:04
creihtheh19:04
claygI originally was in the "just use string literals" camp and didn't like the names - but i got used to POLICY and POLICY_INDEX and came to not care.19:04
creihtwell I would hope that we have unit tests that can test if we typo a header somewhere :)19:05
creihtI feel relying on flake8 for correctness is not helpful19:05
gholtI was in the not giving a flip camp and still am, but unfortunately there seem to be lots of flip givers that each give different flips. ;)19:05
creihtheh19:06
creihtI just really want consistency19:06
*** NM has quit IRC19:06
gholtThat's the latest flip given. :D19:06
creihtheh19:07
*** zhiyan is now known as zhiyan_19:07
gholtI'm imaging clayg changing all the header string literals across all the code to constants. Heheh.19:08
clayggholt: not gunna happen19:08
creihthah19:08
gholtWell, the other thing my imagination had was you beating someone Clockwork Orange style, so...19:09
creihtif nobody else cares....19:09
creihtit will just bug me every time that I look at it :)19:09
gholtclayg: I don't know if you got to see all the confusion around reviewing the various patchsets each with their own dependency tree. But I think I'm good now. I'm just going to work from the last patch here on and then translate where to plop comments I have based on git blame git show etc.19:11
claygcreiht: you put up a patch that changes them and see if folks like it in review.19:11
clayggholt: yeah gerrits' handling of the "Base" patchset isn't as great as I would like.19:11
gholtI just hope it's not too bad on your end, keeping up with everyone's comments and then figuring out which commit to alter or whatever it is you have do. O.o19:13
clayggholt: I feel like if I went through each patch change by change and did a rebase on it's parent, review, apply the days changes, review, ... then the Base thing could show you what changed from patch a to c with the intermediate change b as the base which is just there to eat the parent patchset changes19:13
clayggholt: i'm ok so far, but most of the changes have been fairly astetic - i'm glad we got types out and deprecation in though.19:14
gholtYeah, definitely do not make your job even harder, esp just on my account. Working from the last patchset's diffs will do quite nicely for me.19:14
* creiht takes a break for a bit19:23
*** kutija has quit IRC19:29
zaitcev"Setting up Storage Policies was very simple, and using them is even simpler." -- From the Billy Mays school of technical writing.19:31
zaitcevI'm Loving It19:32
peluse_nice!19:44
peluse_man, I never thought the header name contants would garner so much attention :) creiht, FYI, I introduced those early on because we couldn't decide on a name for the longest time so instead of contantly changing literals everyone I just made those constants.  Personally, I'm cool w/however they end up...19:46
creihthehe19:46
creihtoh I can understand :)19:46
peluse_s/everyone/everywhere/19:46
notmynameAlex_Gaynor: around?19:47
peluse_hey, that reminds me, totally off topic.  What's the deal with pypy?  I saw some stuff from Alex last year about it, is anyone pursuing a strategy there?  Someone at work asked me about it...19:48
notmynamecreiht: clayg: I'm fine with them being strings or constants. seemed the consensus yesterday was to keep them that way. mostly I figured it was simpler to keep them and get SP merged rather than bikeshed on it19:48
creihtnotmyname: yeah that's fine... the only thing I was arguing for was consistency :)19:48
notmynamepeluse_: I think the "strategy" is just to make sure it works under pypy then deployers can use what they want19:48
notmynamecreiht: ya. I'm quite sympathetic with you there19:49
*** madhuri has quit IRC19:50
peluse_notmyname:  ah, OK. Does swift run under pypy today?19:50
notmynamepeluse_: AFAIK19:51
notmynamepeluse_: let me rephrase: there's a strong chance that definitely maybe it does19:51
Alex_Gaynornotmyname: yar19:51
peluse_clayg:  hey man, need me to take care of anything (or anyone)?19:51
creihtpeluse_: it is *just* python, so it should *just* work, right :)19:52
notmynameAlex_Gaynor: I'm looking at pypi download stats, and google tells me you wrote a blog about it. do you know if there is any way to get historical info beyond what's on the project page?19:52
claygpeluse_: idk, i'm working on a "the evolution of tracking misplaced objects" for chuck19:52
Alex_Gaynornotmyname: the way you get that info is you ping dstufft in #openstack-infra or #pypa and ask nicely19:52
peluse_clayg:  OK, well just hollar if you need me to take care of anything19:53
claygpeluse_: I think there's doc comments if you wanna get me a diff - really anything that will apply on b4d4ba75d31 would be great if you wannt just check out the end of the patch change and hack on another commit19:53
notmynameAlex_Gaynor: heh, ok thanks :-)19:54
tdasilvahey guys...just fyi..while reviewing and testing SP, I've been able to setup swiftonfile as a storage policy, pretty cool19:56
notmynametdasilva: nice!19:56
peluse_clayg: which is b4d4ba75d31?  To be clear, want me to jsut address comments on 96026 (docs) and send a diff or something different?19:57
tdasilvaif anyone is interested, this pull request https://github.com/swiftonfile/swiftonfile/pull/19 is the work that we are doing to make swiftonfile a SP19:57
*** zhiyan_ is now known as zhiyan19:59
claygpeluse_: check out the last patch in the series and make changes addressing comments in the reviews.  Get me that diff.  THANKS!19:59
claygpeluse_: (i think the last one is something something Reaper - which seems fitting)20:00
peluse_clayg:  got it, cool20:01
*** Thurloat has quit IRC20:04
claygcreiht: https://gist.github.com/clayg/84e11b94735016c1c34120:07
clayggholt: ^ you should probably give it a read too20:07
* clayg knew this day would come20:07
claygi'm so sorry guys20:07
gholtOhshitwalloftext thiscan'tbegood20:08
*** zhiyan is now known as zhiyan_20:08
creihtholy cow20:08
creihtclayg: hehe thanks for the context20:08
gholtHeheh, oh yeah, I remember asking for this. :)20:08
*** spredzy has joined #openstack-swift20:11
*** otoolee has quit IRC20:15
*** jeblair_ has joined #openstack-swift20:20
*** jeblair has quit IRC20:21
*** jeblair_ is now known as jeblair20:22
*** tdasilva has left #openstack-swift20:22
*** otoolee has joined #openstack-swift20:23
*** kenhui1 has quit IRC20:23
zaitcevI only started to understand what Clay meant in that gist in the penultimate paragraph.20:25
* clayg goes to look up penultimate20:25
notmynamenext-to-last20:25
claygtoo late - google is faster20:26
zaitcevI was kinda of wondering. Russian and Japanese have a word for "the day after tomorrow", "poslezavtra" and "asatte" respectively. Why don't English? Or does it?20:27
claygovermorrow?20:28
zaitcevsomething like that20:28
zaitcevhttp://english.stackexchange.com/questions/45412/how-obsolete-is-the-word-overmorrow20:29
*** ozialien has quit IRC20:30
*** NM has joined #openstack-swift20:34
peluse_clayg:  just emailed you resolution for latest comments on doc patch (based off of the last in the chain, the acct reaper)20:36
peluse_zaitcev:  how about "Sunday"  :)20:37
peluse_clayg:  FYI I also fixed a few other grammar/spelling things that were somehow still lingering...20:38
*** miqui has quit IRC20:38
claygpeluse_: i think i keep adding more everytime I try to write something someone asked me to elaborate on20:39
peluse_clayg: yeah, I managed to add a few when I added the section on defecation20:39
peluse_argh, deprecation :)20:39
*** nthacker has joined #openstack-swift20:39
claygoh my20:39
spredzyI am hitting an issue for every swift command I try to run : IndexError: list index out of range20:39
spredzyI am not sure what it is due to. I create d the ring fine, added the zone and rebalanced it just fine20:40
nthackerHi All, How do i run only a single unit test ?20:40
spredzybut when I try to run a swift stat20:40
spredzyit crashed an error 500 with IndexError: list index out of range20:40
peluse_single unit test example:  nosetests --nocapture --nologcapture test/unit/proxy/controllers/test_obj.py:TestObjController.test_COPY_simple20:41
spredzyswift-ring-build {account,container,object}.builder shows correct output20:41
zaitcevnthacker: (cd test/unit && nosetests common/test_wsgi.py:TestWSGI.test_run_server_conf_dir)20:42
nthackerzaitcev: thanks!20:42
claygpeluse_: git diff > mychanges.patch works well with git apply mychanges.patch20:43
peluse_clayg:  cool, so what I sent you worked OK then?20:44
claygpeluse_: yeah i'll make it work - thanks!20:44
peluse_:)20:44
zaitcevspredzy: The only time I hit that was when I had an unclean /srv/node/dev with extraneous index directories and I used a ring with a smaller size than apparenty it had before.20:45
zaitcevspredzy: You probably have to figure your specific cause out for yourself, sorry.20:46
spredzyzaitcev, hehe ok. will keep digging then thanks for the answer20:46
claygpeluse_: sweet those applied great20:46
spredzyquick q. should the device be a minimal size ?20:46
spredzyue. 1G, 100M ?20:47
spredzyfor testing purpose only20:47
peluse_clayg:  rock n roll20:47
peluse_spredzy:  have you already tried setting up an all in one to get familiar with everything? http://docs.openstack.org/developer/swift/development_saio.html20:55
*** zhiyan_ is now known as zhiyan20:59
*** ashish_ has joined #openstack-swift21:01
*** openstackgerrit has quit IRC21:01
*** ashish_ has quit IRC21:05
*** zhiyan is now known as zhiyan_21:09
*** swat30 has quit IRC21:18
*** kenhui has joined #openstack-swift21:28
*** kashyapk has joined #openstack-swift21:44
*** kashyapk has quit IRC21:49
*** kenhui has quit IRC21:56
*** zhiyan_ is now known as zhiyan22:00
*** judd7 has quit IRC22:02
*** zhiyan is now known as zhiyan_22:09
*** Midnightmyth has quit IRC22:11
*** mkollaro has quit IRC22:13
claygoh wow, it's quiet22:16
peluse_yeah, Fri afternoon...22:16
peluse_beer-thirty here soon22:16
notmynameclayg: peluse_: well my meetings with the sales and marketing people are done now, so maybe I can start on the technical part of my day :-)22:23
gholtclayg: For some reason I completely missed that that query is based on ROWID and has a limited start and count. So, just, uhm, pretend I never said anything there.22:25
gholtProbably shouldn't review code when feeling ill. Never really works out well for anyone. ;)22:28
*** gyee has quit IRC22:28
*** openstackgerrit has joined #openstack-swift22:31
*** openstackgerrit has quit IRC22:35
*** openstackgerrit has joined #openstack-swift22:35
clayggholt: it's fine man, thanks for looking at that22:42
claygcreiht: you wanna talk about *args?22:42
clayg... yeah me either22:43
peluse_clayg:  what is noga?22:43
gholtHehe!22:43
*** NM has quit IRC22:43
notmynamepeluse_: noqa ?22:44
gholtI feel a little bad though because, looking at all that code more, it really looks like you spent a lot of time and thought making sure long locking queries would never happen. But ah well, I'm smarter now for having said something stupid. :)22:44
clayggholt: no i was just scared to death of breaking something - don't get all "oh i'm sure clay did this right" on me now22:45
peluse_notmyname:  ask clayg?  I dunno :)  In a few comments in the reconciler22:45
gholtWell, you know that won't happen anyway. We don't even assume that about ourselves.22:46
claygpeluse_: oh it probably is a typo then - yeah I was probably going for noqa22:46
peluse_which is?22:46
notmynamepeluse_: at the end of the patch chain I can't find "noga" anywhere22:46
claygaround some bare excepts maybe?  I'm always thinking that thing we got meged into hacking will get release some day.22:46
peluse_yeah, its noqa22:46
claygpeluse_: it means no QA - skip flake8 checks22:46
peluse_ahh22:47
notmynamepeluse_: IOW "I know this will fail a flake8 test and that's ok"22:47
gholtYeah, and there are some times when coverage will insist you haven't covered a line even though you've verified you truly have.22:47
gholtUsually, pass is the culprit22:47
claygnotmyname: I don't think we even run the flake8 check i'm noqa'ing against - but you know - forward thinking!  it's like py3 support.22:48
peluse_did not know that... thanks.22:48
*** jergerber has quit IRC22:52
claygpeluse_: I need add doc sections for the container-reconciler config options22:52
claygnotmyname: did creiht make any progress arguing for string literals and consistency?22:53
claygacoles: thanks for the reminder on the X-Backend-Timestamp thing on object 40422:53
peluse_clayg:  just left you a reminder on the review to do that :)22:54
claygthanks22:54
*** zhiyan_ is now known as zhiyan23:01
*** zhiyan is now known as zhiyan_23:10
*** nsquare has joined #openstack-swift23:13
*** diegows has quit IRC23:13
claygpeluse_: oh right i need to review the tmp/q change again23:19
peluse_ja23:30
claygcomin' at ya23:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Update container storage_policy_index when auditing  https://review.openstack.org/9635223:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Add functional tests for Storage Policy  https://review.openstack.org/9604223:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Fixes probe tests with non-zero default storage policy  https://review.openstack.org/9635323:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Update swift-container-info to be storage policy aware  https://review.openstack.org/9604323:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Merge container storage_policy_index  https://review.openstack.org/9604023:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to Accounts  https://review.openstack.org/9604123:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to list_endpoints  https://review.openstack.org/9604623:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to Container Sync  https://review.openstack.org/9604723:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Enqueue misplaced objects during container replication  https://review.openstack.org/9604423:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Add LRUCache to common.utils  https://review.openstack.org/9604523:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to ssync  https://review.openstack.org/9603423:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Put X-Timestamp in object 404 responses  https://review.openstack.org/9603523:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to the Auditor  https://review.openstack.org/9603223:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Add storage policy support for the Replicator  https://review.openstack.org/9603323:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Add container-reconciler daemon  https://review.openstack.org/9603823:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Add reconciler probetest outline  https://review.openstack.org/9603923:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Extend interface on InternalClient  https://review.openstack.org/9603623:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Extend direct_client  https://review.openstack.org/9603723:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support  https://review.openstack.org/9602723:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Documentation  https://review.openstack.org/9602623:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy support to Containers  https://review.openstack.org/9602923:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Update FakeRing and FakeLogger  https://review.openstack.org/9602823:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy support to Object Updates  https://review.openstack.org/9603123:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy support to Object Server  https://review.openstack.org/9603023:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy support to the Account Reaper  https://review.openstack.org/9604923:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to Recon Middleware  https://review.openstack.org/9604823:31
claygeveryone have a good weekend - see you next week23:32
peluse_awesome clayg, see ya Mon23:32
claygoh, and sorry for all the updates gholt - maybe you can do a working session on how to review these changes or we can come up with something different than maintaing all of these...23:32
*** NM has joined #openstack-swift23:33
claygI did notice that if you go to the end and select the last base you can see all of the last bits changes (if you just wanna see if your comment was addressed)23:33
*** ozialien has joined #openstack-swift23:38
gholtclayg: Yeah, working from the end seems best.23:40
*** NM has quit IRC23:41
*** NM has joined #openstack-swift23:41
*** NM has quit IRC23:51

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