Wednesday, 2014-04-02

*** csd has joined #openstack-swift00:09
*** shri has joined #openstack-swift00:13
*** matsuhashi has joined #openstack-swift00:26
*** shri has quit IRC00:27
*** openstackgerrit has joined #openstack-swift00:30
*** mmcardle has joined #openstack-swift00:31
*** mmcardle has quit IRC00:35
*** RockKuo has quit IRC00:42
openstackgerritClay Gerrard proposed a change to openstack/swift: Merge container storage_policy_index values.  https://review.openstack.org/8394200:44
*** matsuhashi has quit IRC00:47
*** matsuhashi has joined #openstack-swift00:48
*** csd has quit IRC00:51
*** zackf has quit IRC00:51
*** matsuhashi has quit IRC00:52
*** matsuhashi has joined #openstack-swift00:57
*** mmcardle has joined #openstack-swift01:32
*** zhiyan_ is now known as zhiyan01:32
*** mmcardle has quit IRC01:37
openstackgerritA change was merged to openstack/swift: Only run flake8 on Swift code  https://review.openstack.org/8317701:46
*** nosnos has joined #openstack-swift01:47
*** changbl has joined #openstack-swift01:47
portantenotmyname: seems pretty clear to me that the testFileSizeLimit functional test does not actually test that file size limits are enforced01:54
portanteif you change an SAIO to use 2MB max_file_size in /etc/swift.conf, the test fails01:55
portantesorry, hold on, hopefully it is pilot error01:56
portantewell, at least it does not appear to be, changed /etc/swift/test.conf to have max_file_size=2MB and the test does not appear to work, so might be a test harness problem01:58
openstackgerritClay Gerrard proposed a change to openstack/swift: Merge container storage_policy_index values.  https://review.openstack.org/8394202:04
*** RockKuo has joined #openstack-swift02:32
*** mmcardle has joined #openstack-swift02:33
*** mmcardle has quit IRC02:38
*** gyee has quit IRC02:39
openstackgerritYuan Zhou proposed a change to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445602:44
*** zanc has quit IRC02:52
*** madhuri has joined #openstack-swift02:57
madhuriclayg: there?02:57
claygmadhuri: it's best to just ask whatever you have on your mind, even if i'm not around right then I'll see it later - unless someone else beats me to it - what's up?03:09
*** Anju has joined #openstack-swift03:11
madhuriclayg: Hi..03:11
clayghi :)03:11
madhuriclayg: Just saw your cleanup patch for container-info03:12
Anjuclayg :  in code in every put of a container the account_update method is calling03:13
madhuriIt can be done in account-info case too03:13
claygyeah - there's been a few other's too - turns out the container-info was big hit!03:13
madhurifor me too :)03:13
claygmadhuri: nice03:13
claygAnju: ohia03:13
madhurithanks03:13
claygmadhuri: yeah thank you03:13
madhuriso can I do it for account-info too?03:14
claygmadhuri: yeah i think so03:14
madhuriclayg: ok03:14
Anjuclayg : https://github.com/openstack/swift/blob/master/swift/container/server.py#L29203:17
*** vilobhmm has joined #openstack-swift03:17
madhuriclayg: need some more pointers :)03:17
Anjuclayg : according to this  in every put of any object and container03:18
openstackgerritPeter Portante proposed a change to openstack/swift: Update callback with proper bytes transferred  https://review.openstack.org/8461003:18
claygI feel like I have two outstanding half asked questions...03:18
Anjuthe account_updater method is changing the timestamp03:18
claygAnju: so that line you linked is execute by the container server only on container create - nothing to do with objects, or the account updater?03:20
Anjuclayg  : According to me in every put of any object and any container the account_stat table field "put_timestamp"03:21
Anjushould change03:21
*** matsuhashi has quit IRC03:21
Anjuclayg : the code line I gave you is saying the same03:22
claygAnju: no... i don't think so - you have to watchout with some swift clients - they'll do a container PUT before every object PUT03:23
claygnot that that is so bad...03:24
Anjuclyag : you mean it is going correct according to you03:24
*** zackf has joined #openstack-swift03:24
Anjuclayg:  sorry  I am taking your timr. I did using API03:25
claygAnju: so I'm not seeing a container's put_timestamp change when I upload an object - unless I use like the swift cli which does a container PUT before the object PUT - which of course updates the containers put_timestamp as expected?03:26
claygAnju: i'm not sure I follow your question - are you asking if the account databases should be updated on container create (yes) or if the containers put_timestamp is updated on PUT (yes) or if I can duplicate what you're seeing where object PUT updates container put_timestamp (no)03:27
claygmadhuri: more pointers?03:28
Anjuclayg : yeah . yaeh03:28
madhuriclayg: too work upon ;)03:28
claygoh - lol03:28
*** mmcardle has joined #openstack-swift03:34
*** nosnos has quit IRC03:37
claygmadhuri: swift.common.direct_client is missing a few methods and could use some more/better test coverage?03:37
claygAnju: so did I accidently answer your questions?03:38
madhuriclayg: Ok. Taking a look03:38
Anjuclayg : I want to give you some description  . :)03:39
*** mmcardle has quit IRC03:39
madhuriclayg: Yeah. Methods like put_account, head_Account and many more can be addded.03:43
madhuriRight??03:43
claygmadhuri: yeah!03:44
claygmadhuri: it's just an idea, if you're interested in the backend apis' - and tests03:44
*** peluse has joined #openstack-swift03:44
madhuriclayg: Thanks!!03:44
madhuriYeah. I can do that03:45
Anjuclayg:  http://fpaste.org/90826/10383139/ :)03:46
peluseanticw:  sorry was offline all day.  No, what's there is the latest post but we'll be udpating soon... need to get policies wrapped up03:46
peluseclayg:  how are you doing on catching up torgomatic's patch set and looking at those last few outstanding gerrit reviews?  Anything I can do to help?03:47
claygpeluse: i was ooo yesterday - i'm currently working on a shared pre-req to both our patches - which is a functioning status_changed_at field so we can say who had the "oldest" storage policy index03:49
claygpeluse: did you ever figure out what was up with those account db tests?  sorry i'm behind on ec reviews...03:50
peluseclayg:  cool.  yes, I posted a fix to that failure.  An existing sql trigger was catching our attempt to UPDATE the contaeiner DB03:53
peluseupdate with SPI of 0 that is, for pre-SPI container tables03:53
claygpeluse: hrmm... i need to look at that change again...03:54
claygAnju: I'm not seeing it... what do you mean "No change in Acount Database. No change in put_timestamp"03:55
Anjuclayg:  no chane in account_stat table03:55
pelusegonna go watch a little Game of Thrones... let me know when your pre-req will be ready.  In the meantime I'll go take another look at the pluggable DB thingy..03:55
peluseclayg:  here it is:  https://review.openstack.org/#/c/83840/03:56
Anjuclayg:   what I am saying I pasted it here http://fpaste.org/90830/64113491/04:02
claygAnju: right the account's put_timestamp doesn't change on container PUT - just like the container's put_timestamp doesn't change on object PUT04:09
Anjuclayg : agree , but why in code It is happening04:10
Anjuclayg:  https://github.com/openstack/swift/blob/master/swift/container/server.py#L29204:10
Anjuyou can see here in every put of object and container04:11
Anjuthe account_update method is called04:11
claygyeah that adds a row to the containers table on the account server?04:11
claygit's the "if container" block of of the account server's PUT method04:12
Anjuyes04:12
claygyou can't both agree with me and disagree with me ;)04:13
*** lpabon has quit IRC04:13
claygyeah account server looks basically the same "if container -> put_container; else -> update_put_timestamp"04:14
clayg... but I expected that :D04:14
Anjuhttps://github.com/openstack/swift/blob/master/swift/container/server.py#L16304:14
claygright that's an account server PUT for /account/container - so it's a different branch in the account server's PUT method04:15
clayglook at your logs, backend account/container server's PUT's take two forms depending on if it's creating the resource or adding an object to the resource04:16
claygaccount has PUT /account and PUT /account/container; container has PUT /account/container and PUT /account/container/obj04:16
Anjuyeah yeah04:16
Anjucorrect04:16
claygheheheheh04:17
Anjuclayg:  misleading04:17
* Anju anju is slapping herself04:17
Anju:)04:18
claygand now you know how that works too!04:19
Anju:)04:19
*** Manish_ has joined #openstack-swift04:24
Manish_hugokuo: Hi.....04:27
Manish_Do you know , that of "autocreate" value is set to false...then in this case how user can create Account?04:29
*** nosnos has joined #openstack-swift04:31
Manish_i know that there is one configuration in proxy server.conf.....allow_account_management, but if this one is even set to false, then is it like that no one can create account?04:34
claygManish_: if you're doing manual account managment you typically want a set of proxy servers that your user management system is configured to talk to that will accept the PUT /account request (allow_account_management = true)04:35
*** mmcardle has joined #openstack-swift04:36
*** matsuhashi has joined #openstack-swift04:36
claygthe other option is to have allow_account_management true everywhere with some middleware to handle the authorization of reseller admin requests04:37
*** mmcardle has quit IRC04:40
* hugokuo look around .... 04:44
* clayg backs into the shadows04:45
*** matsuhashi has quit IRC04:50
*** mmcardle has joined #openstack-swift04:58
*** matsuhashi has joined #openstack-swift05:00
*** ppai has joined #openstack-swift05:01
*** mmcardle has quit IRC05:01
*** zackf has quit IRC05:14
openstackgerritClay Gerrard proposed a change to openstack/swift: Keep status_changed_at up-to-date with status changes.  https://review.openstack.org/8462105:14
openstackgerritPete Zaitcev proposed a change to openstack/swift: Relocate DATADIR to backends  https://review.openstack.org/8462405:23
*** mmcardle has joined #openstack-swift05:28
*** mmcardle has quit IRC05:33
*** zaitcev has quit IRC05:44
openstackgerritClay Gerrard proposed a change to openstack/swift: Keep status_changed_at up-to-date with status changes.  https://review.openstack.org/8462105:48
*** sushma has joined #openstack-swift06:02
*** sushma has quit IRC06:04
*** vilobhmm has quit IRC06:06
openstackgerritClay Gerrard proposed a change to openstack/swift: Keep status_changed_at up-to-date with status changes.  https://review.openstack.org/8462106:09
*** psharma has joined #openstack-swift06:13
*** sowmya_ has joined #openstack-swift06:19
*** mmcardle has joined #openstack-swift06:29
*** sungju_ has quit IRC06:34
*** mmcardle has quit IRC06:34
*** tanee-away is now known as tanee06:35
*** saju_m has joined #openstack-swift06:39
*** cschwede has left #openstack-swift06:41
*** cheri has joined #openstack-swift06:51
*** sowmya_ has left #openstack-swift06:59
*** mlipchuk has joined #openstack-swift07:01
*** mmcardle has joined #openstack-swift07:31
*** zhiyan is now known as zhiyan_07:35
*** mmcardle has quit IRC07:36
openstackgerritYuan Zhou proposed a change to openstack/swift: Update container storage_policy_index when auditing  https://review.openstack.org/8309307:37
*** saju_m has quit IRC07:42
*** nacim has joined #openstack-swift07:51
*** tanee is now known as tanee-away07:51
*** saju_m has joined #openstack-swift07:52
*** mmcardle has joined #openstack-swift08:07
*** cschwede has joined #openstack-swift08:08
openstackgerritYuan Zhou proposed a change to openstack/python-swiftclient: Allow to specify storage policy when uploading objects  https://review.openstack.org/7392008:22
*** mmcardle has quit IRC08:23
*** nshaikh has joined #openstack-swift08:27
*** mmcardle has joined #openstack-swift08:27
*** wayneeseguin has quit IRC08:28
*** wayneeseguin has joined #openstack-swift08:28
*** j_king has quit IRC08:28
*** j_king has joined #openstack-swift08:28
openstackgerritVictor Stinner proposed a change to openstack/python-swiftclient: Fix test_multithreading on Python 3  https://review.openstack.org/8410408:31
*** d89 has joined #openstack-swift08:39
*** psharma has quit IRC08:44
*** saju_m has quit IRC08:48
*** tanee-away is now known as tanee08:48
*** tanee is now known as tanee-away08:48
*** tanee-away is now known as tanee08:48
*** tanee is now known as tanee-away08:49
*** tanee-away is now known as tanee08:49
*** saju_m has joined #openstack-swift08:49
*** nshaikh has quit IRC08:57
*** psharma has joined #openstack-swift08:58
*** chandankumar_ has joined #openstack-swift08:59
*** Midnightmyth has joined #openstack-swift09:02
*** psharma has quit IRC09:03
*** Longgeek_ has joined #openstack-swift09:04
*** mmcardle has quit IRC09:07
*** foexle has joined #openstack-swift09:07
*** mmcardle has joined #openstack-swift09:08
*** zanc has joined #openstack-swift09:13
*** acoles is now known as acoles_away09:14
*** acoles_away is now known as acoles09:16
*** Manish_ has quit IRC09:17
*** saju_m has quit IRC09:24
*** saju_m has joined #openstack-swift09:25
openstackgerritMadhuri Kumari proposed a change to openstack/swift: Minor cleanup of swift-account-info  https://review.openstack.org/8467509:26
*** psharma has joined #openstack-swift09:26
*** saju_m has quit IRC09:31
*** saju_m has joined #openstack-swift09:37
*** jamie_h has joined #openstack-swift09:48
*** matsuhashi has quit IRC09:50
*** ccorrigan has joined #openstack-swift09:53
*** matsuhashi has joined #openstack-swift09:57
*** jamie_h has quit IRC09:57
*** psharma has quit IRC10:08
*** chandankumar_ has quit IRC10:11
*** mmcardle has quit IRC10:14
*** Anju has quit IRC10:24
*** RockKuo_iPad has joined #openstack-swift10:29
*** RockKuo_iPad has quit IRC10:30
*** RockKuo_iPad has joined #openstack-swift10:30
*** mmcardle has joined #openstack-swift10:32
*** RockKuo_iPad has quit IRC10:32
*** RockKuo_iPad has joined #openstack-swift10:33
*** Trixboxer has joined #openstack-swift10:41
*** RockKuo_iPad has quit IRC10:42
*** RockKuo has quit IRC10:47
*** ppai has quit IRC10:56
*** ppai has joined #openstack-swift10:58
*** matsuhashi has quit IRC11:00
*** Anju has joined #openstack-swift11:02
*** nosnos has quit IRC11:04
*** openstackgerrit has quit IRC11:08
*** openstackgerrit has joined #openstack-swift11:08
*** Longgeek_ has quit IRC11:10
*** matsuhashi has joined #openstack-swift11:16
openstackgerritDonagh McCabe proposed a change to openstack/swift: Reclaim containers even if account db is reclaimed  https://review.openstack.org/8469611:20
*** mmcardle has quit IRC11:36
*** erlon has joined #openstack-swift11:51
*** acoles has quit IRC11:56
*** tdasilva has joined #openstack-swift12:03
*** cheri has quit IRC12:04
*** ppai has quit IRC12:05
*** mkollaro has joined #openstack-swift12:11
*** mmcardle has joined #openstack-swift12:13
*** saju_m has quit IRC12:17
*** cheri has joined #openstack-swift12:21
*** ppai has joined #openstack-swift12:22
openstackgerritPeter Portante proposed a change to openstack/swift: Only fetch a timestamp when needed  https://review.openstack.org/8471012:36
openstackgerritVictor Stinner proposed a change to openstack/python-swiftclient: Python 3: fix tests on HTTP headers  https://review.openstack.org/8471112:37
*** chandankumar_ has joined #openstack-swift12:38
*** tdasilva has quit IRC12:41
*** ppai has quit IRC12:41
*** saju_m has joined #openstack-swift12:47
*** chandankumar_ has quit IRC12:51
*** mmcardle has quit IRC12:52
*** cheri has quit IRC12:53
*** chandan_kumar has quit IRC12:55
*** tdasilva has joined #openstack-swift12:57
*** JelleB is now known as a1|away12:58
*** a1|away is now known as JelleB12:58
*** matsuhashi has quit IRC13:02
*** matsuhashi has joined #openstack-swift13:02
*** dmsimard has joined #openstack-swift13:06
*** matsuhashi has quit IRC13:07
*** matsuhashi has joined #openstack-swift13:10
*** Longgeek_ has joined #openstack-swift13:15
*** acoles has joined #openstack-swift13:32
*** ChanServ sets mode: +v acoles13:32
*** RockKuo has joined #openstack-swift13:32
*** saju_m has quit IRC13:36
*** jamesu has joined #openstack-swift13:45
*** chandan_kumar has joined #openstack-swift13:49
*** judd7 has quit IRC13:53
jamesuApologies. I'm a bit new to openstack and swift. I'm interested in Hierarchical Storage. I've been reading about erase coding etc. But what is unclear is does it move data from a high performance area (i.e. SSD) to low performance area (i.e large SATA)13:58
*** zaitcev has joined #openstack-swift13:59
*** ChanServ sets mode: +v zaitcev13:59
glangeswift clusters can be all spinning disks, a mix of spinning disks and SSD's, or all SSD's (if you have the budget for that)14:13
glangea mix of both types of discs can get you better performance if the account and container servers run on SSDs14:13
glangethe erasure encocoding changes won't change where objects are stored just now they are stored14:14
glangeI would imagine object GETs and PUTs might be slower with EC because of the overhead14:14
glangejamesu: does that answer your question ?14:15
glanges/just now/just how/14:15
*** judd7 has joined #openstack-swift14:16
jamesuAhh. Ok. Yes it does kind of.14:16
jamesuThe reason for the question is due to a large media (video) storage capability that we need14:17
jamesuthe most recently added is most frequently accessed. Then there is the long-tail historical data14:18
jamesuthe latter requiring a lot less performance.14:18
glangethe one big advantage of EC is that it reduces storage requirements for an object, right now swift keeps 3 copies of each object, with EC the total storage required per object would be less than 3x14:18
glangejamesu: sounds like you might want to stand up a caching layer in front of swift14:19
glangeor use a cdn?14:19
jamesuYes there is a CDN in front of it.14:19
glangethere isn't any feature in swift that makes reads of "hot files" faster14:20
peluseglange:  EC can indeed change where objects are stored by using different media for the drives on the EC policy ring14:20
jamesupeluse: can the historical data be migrated to that area at a pre defined time?14:20
peluseto be clear, policies will let you do that, not EC itself :)  but EC will be implemnted as a policy14:20
glangepeluse: ok, I just meant that with EC the objects would still be stored either on spinning disks or SSD's just like current swift14:20
jamesuor maybe just via an automatic popularity index14:20
pelusejamesu:  that will be possible given the base code we're laying down but its not going be a core feature within swift at the moment14:21
peluseglange:  gotcha, just wanted to be clear that if someone wanted a policy of all HDDs or all SSDs and EC on one or the other they could do that14:21
jamesuso some external component will have to migrate the object from one area to another?14:21
pelusejamesu:  correct14:21
pelusejamesu:  imagine a 'default' policy that stores 3x...14:22
glangepeluse: ok, I'll have to look closely at storage policies, sounds like an interesting change14:22
pelusethen at some later point in time an agent running within the cluster (or outside but that would take more proxy BW) determines its time to migrate stuff to an EC policy, it just 'moves' the data.  It can leave behind a manitest type thing so the app doesn't have to know about the location14:23
jamesuUnderstood.14:23
glangepeluse: is it expected that reads on EC objects will be slower?14:23
*** mmcardle has joined #openstack-swift14:24
peluseglange:  that would be great!  the more eyes, the better.  Right now its all on feature/ec but we're in the middle (clayg/torgomatic/me/others) of refactoring into a set of more reasable/logically ordered patches.  That's WIP right now off of one of torgomatics repos - you should have that info in your email14:24
peluseglange:  yup, most likely14:24
peluseglange:  writes as well14:25
glangeyeah, but that's the trade off for less disk space used14:25
pelusehard to guage how much though, so many variables... some of the PUT path is done and the GET path won't be far behind so it won't be too long before we can take some real measuremens and see what kind of impact there is14:26
peluseglange:  are you coming to the next hackathon?14:26
jamesupeluse: its quite interesting because we are looking to build 3 geographic sites with identical content libraries.14:26
glangepeluse: no, I'm sitting that one out, we will be sending out "top men" though :)14:27
*** zackf has joined #openstack-swift14:27
peluse:)  OK, well we expect to have the main IO paths deomnstrable by then and generate some really good discussion14:28
glangejamesu: you might want to look at swift's container sync feature14:28
glangejamesu: that lets you have containers across clusters with identical content14:29
jamesuhow quickly does the sync happen?14:31
jamesuahh i see there is an interval parameter.14:31
glangehow well it works depends heavily on how much bandwidth you have between clusters14:32
glangebut it's a way to automatically keep the containers in sync14:32
*** tanee is now known as tanee-away14:33
*** nshaikh has joined #openstack-swift14:38
*** chandankumar_ has joined #openstack-swift14:40
*** matsuhashi has quit IRC14:52
*** Longgeek_ has quit IRC15:04
*** lpabon has joined #openstack-swift15:10
*** cheri has joined #openstack-swift15:13
notmynamegood morning15:15
creihtugh... I hate gerrit formatting :/15:18
*** mtaylor is now known as mordred15:19
*** mordred has quit IRC15:19
*** mordred has joined #openstack-swift15:19
*** openstackgerrit has quit IRC15:21
*** jamesu has left #openstack-swift15:21
notmynamecreiht: or lack thereof?15:21
*** openstackgerrit has joined #openstack-swift15:21
creihtnotmyname: heh15:22
creihtnotmyname: I would prefer it didn't try to do anything at all15:22
notmynamecreiht: did you see the mailing list question this morning about HEADs being so expensive when doing small-object PUTs? I read it and thought, "If-None-Match sure would be good there"15:22
creihtlol15:22
creihtor just not doing a head at all? :)15:23
creihtI've always disliked that feature of swiftclient15:23
notmynameI see reasons for it. but they all go away with if-non-match support15:24
creihtyeah but I don't think the head should be the default15:25
creihtif I tell you to put a file, it should put the file :)15:25
creihtif I tell you to put a file, only if it isn't already there, then check first15:25
notmynameswift upload --yes --I-mean-it --really --do-it15:25
notmyname--force15:25
notmynameI think that the range requests on SLOs is the last critical thing to get into Icehouse (https://review.openstack.org/#/c/84483/)15:27
notmynamecreiht: have you seen anything else critical?15:27
creihtdepends on the definition of critical :)15:27
creihtI would really like to get if-none-match in :)15:28
notmynameya, me too :-)15:28
creihtI'll look at the rest of the list15:28
notmynamejust needs one move +215:28
creihtyeah15:28
notmyname*more15:28
creihthttps://review.openstack.org/#/c/81646/15:28
creihtfor anyone interested :)15:28
*** piyush has joined #openstack-swift15:29
creihtacccount to account copy would be cool, but I think it still needs a little more work15:29
notmynameok15:29
creihtit would be nice to get the new -info tools cleaned up15:30
notmynamereminder that we have a team meeting today https://wiki.openstack.org/wiki/Meetings/Swift. Not a lot on the agenda. just a couple of status updates on Icehouse and (hopefully from clayg and/or peluse) on storage policies15:30
notmynamecreiht: oh yeah. that one really annoys me (the current state, not the outstanding patch)15:30
notmynameand if we get it in, we dont' have to worry as much about migrations because we havent' released with it yet15:30
creihtright15:31
creihtThat's all that stick out in my opinion15:32
zaitcevhey, I started breaking out PBEs https://review.openstack.org/8462415:33
pelusenotmyname: hey did you get that other system we shipped you?15:34
pelusezaitcev:  cool, I had the next round of review of that on my TODO list for today (and its my b-day so how about that?).  SHould I wait until you have it broken out further to avoid confusing myself?15:34
zaitcevpeluse: just review them one by one as they come, please15:35
notmynamepeluse: heh, I did. :-)15:35
pelusezaitcev:  will do!  if its not too much trouble please add me as a reviewer as they become ready so I don't forget15:35
zaitcevHow many men did it take to carry15:35
pelusenotmyname:  way cool, wanted to make sure it didn't get lost in the main :)15:36
pelusemain=mail15:36
notmynamehttps://wiki.openstack.org/wiki/Swift/PriorityReviews updated with the 3 patches needed today15:37
creihtnotmyname: I didn't +2 the slo as I would like someone besides us to review it :)15:38
notmynamecreiht: right, I saw that :-)15:38
notmynamecreiht: while I trust you on that one, I understand.15:39
creihtnotmyname: what's the likelyhood that Yuan will finish the cleanup?15:39
Alex_GaynorCan I bug any of ya'll for reviews on https://review.openstack.org/#/c/84205/ and https://review.openstack.org/#/c/84024/ :-)15:39
creihtis he on irc?15:39
notmynamepeluse: do you know?15:39
creihtAlex_Gaynor: are those critical for icehouse? :)15:39
notmynameAlex_Gaynor: no, not until the other 3 are done ;-)15:39
Alex_Gaynorcreiht: Probably not, not unless Py3k is critical15:40
Alex_GaynorI hope what they lack in urgency, they make up in simplicity :P15:40
creihthaha15:41
Alex_Gaynor(in all seriousness, if folks are focusedd on more urgent stuff, I totally understand)15:41
creihtAlex_Gaynor: yeah we are trying to focus to get things done to cut a release candidate15:42
notmynameAlex_Gaynor: ya, we need to get these last patches for icehouse in today15:42
notmynameto have an rc tomorow am15:42
notmynameok, coffee cup empty. time to go to the office15:43
notmynameI'll be back in 30-60 minutes15:43
*** tanee-away is now known as tanee15:46
*** Anjut has joined #openstack-swift15:47
creihtnotmyname: I'm tempted to just clean it up for him15:48
creihtbut I'm also about to go to lunch, so I'll check in when I get back :)15:48
*** mkollaro has quit IRC15:49
creihtpeluse: so you know Yuan Zhou?15:50
*** Anjut has quit IRC15:51
pelusecreiht:  for sure15:53
acolescreiht: question re https://review.openstack.org/#/c/81646/ ?15:54
openstackgerritDonagh McCabe proposed a change to openstack/swift: Reclaim containers even if account db is reclaimed  https://review.openstack.org/8469615:54
* peluse reads the last bit of history, was off reviewing something15:54
creihtpeluse: re: https://review.openstack.org/#/c/84456/15:55
creihtdo you think they will be able to finish the cleanup?15:55
creihtto get it in today15:55
creihtif not, would they mind a little help?15:55
pelusehe's in China so he's probably about to hit the sack right now... I'm certain he wouldn't mind help, he's a really good guy15:56
*** mkollaro has joined #openstack-swift15:57
openstackgerritDonagh McCabe proposed a change to openstack/swift: Reclaim containers even if account db is reclaimed  https://review.openstack.org/8469615:57
*** zhiyan_ is now known as zhiyan15:59
creihtalso, I just noticed that just running `swift setup.py develop` creates a pbr-0.8.0-py2.7.egg file in the swift dir, which is kinda ugly :/15:59
gholtIt's for your own good, I'm sure.16:00
creihtheh16:00
pelusewhatever you do don't delete it!  :)16:00
creihttoo late16:00
creiht:)16:00
creihtI'll see if I can clean it up an push a patch up over his16:03
pelusecool16:03
*** mkollaro has quit IRC16:04
creihtHe'll still get the credit ;)16:05
*** bill_az has joined #openstack-swift16:06
*** gvernik has joined #openstack-swift16:17
*** chandankumar_ has quit IRC16:20
notmynamecreiht: thanks :-)16:22
notmynamecreiht: if you've got that, I'll start on reviewing the SLO range patch16:25
*** nshaikh has quit IRC16:25
notmynamecreiht: do you think that having the common code in swift/cli is a good place?16:25
openstackgerritA change was merged to openstack/swift: Only fetch a timestamp when needed  https://review.openstack.org/8471016:29
*** tanee is now known as tanee-away16:32
*** tanee-away is now known as tanee16:33
*** piyush has quit IRC16:34
*** piyush has joined #openstack-swift16:37
*** nacim has quit IRC16:38
*** piyush1 has joined #openstack-swift16:39
*** piyush has quit IRC16:41
*** zhiyan is now known as zhiyan_16:51
notmynamecool. so in iTerm2, if you right-click on a number, it shows you the hex eqiv in the context menu16:56
*** csd has joined #openstack-swift16:58
*** mlipchuk has quit IRC17:13
notmynameportante: cschwede: zaitcev: will any of you have a chance to review the if-none-match patch today? https://review.openstack.org/#/c/81646/17:17
notmynameah. acoles may be on it :-)17:17
acolesnotmyname: i just reviewd it, few minor queries17:17
acolesnotmyname: meeting time is 7pm UTC right?17:18
notmynameacoles: 1900utc.17:18
notmynamemathing...17:18
notmynameyes. 7pm utc17:18
acolesnotmyname: serious conflict with champions league soccer in europe :)17:19
*** mmcardle has quit IRC17:21
notmynameacoles: I have a follow up to one of your questions there17:21
notmynameacoles: re the spec saying that it should be either * or an etag17:21
acolesnotmyname: yeah, i was curious about that17:22
*** d89 has quit IRC17:23
notmynameacoles: I think you're right that it's either * or "1#entity-tag"17:23
notmynamebut17:23
notmynamewhat's the difference? if we accept * as one of many values passed in, a failure means "we have something there already" (ie 412). if we return a 400 instead, it means malformed request17:24
notmynameright?17:24
notmynamethere is no functional difference in that the client gets a 4xx error.17:25
notmynameso I don't know how important that difference is (also, the principle of being liberal with what you accept)17:26
notmynamepeluse: acoles: also, in response to the question of supporting etag matching on the object server, even if filtered in the proxy, might this be useful later eg for replication or EC rebuilding?17:27
notmynameacoles: so I think you're technically correct (the best kind of correct) wrt tot he spec. good catch! but how important is that in this case? (I don't know)17:28
acolesnotmyname: re *, etag - agreed, 4xx goes back either way. It was a question rather than an objection. And I'm not sure if * only is widely enforced elsewhere.17:29
*** cheri has quit IRC17:29
*** ankit_deshwal has joined #openstack-swift17:30
*** patchbot` has joined #openstack-swift17:31
*** patchbot has quit IRC17:31
acolesnotmyname: re. etag matching in the obj server, happy for it to stay there. but would be nice to have the extra unit test i suggested. unless i missed something.17:32
*** patchbot` is now known as patchbot17:33
*** ankit_deshwal has quit IRC17:34
*** piyush1 has quit IRC17:34
*** tanee is now known as tanee-away17:35
*** hurricanerix_ has joined #openstack-swift17:36
*** nprivalova has quit IRC17:38
*** hurricanerix has quit IRC17:38
acolesnotmyname: creiht: heading out for commute, i'll look at https://review.openstack.org/#/c/81646/ later today17:41
openstackgerritA change was merged to openstack/swift: AssertEquals is deprecated, use assertEqual partI  https://review.openstack.org/7647217:42
zaitcevmuahahaha, I managed to switch Swift meeting reminder to UTC in Zimbra17:44
zaitcevThanks, Obam... er. VmWare? or Yahoo?17:45
*** nprivalova has joined #openstack-swift17:47
*** donagh has joined #openstack-swift17:47
notmynameacoles: creiht: I think the if-none-match parsing has actually shown a bug in swob (/cc redbo)17:48
notmynamein swob, Match objects have values that _must_ be separated by ', ' (note the space) and cannot distinguish between the special case of a value of * or the entity tag "*"17:49
notmynamewhich raises the question, "now that it's harder to fix, how much do we care?"17:50
*** donagh has quit IRC18:02
openstackgerritMadhuri Kumari proposed a change to openstack/swift: Added missing direct backend APIs  https://review.openstack.org/8481918:03
*** vilobhmm_ has joined #openstack-swift18:07
*** zul has quit IRC18:09
*** vilobhmm___ has joined #openstack-swift18:11
*** vilobhmm_ has quit IRC18:12
*** zul has joined #openstack-swift18:12
creihtnotmyname: yeah I was pondering the location, and that seemed good enough18:13
creihtjust got back from lunch and going to try to finish this up18:13
*** vilobhmm___ has quit IRC18:17
cschwedenotmyname: yep, will start reviewing https://review.openstack.org/#/c/81646/ right now and continue after the meeting if required18:18
openstackgerritChuck Thier proposed a change to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445618:36
creihtnotmyname: -^18:36
creihtthere's a quick attempt to clean it up a bit18:36
acolesnotmyname: creiht: ah, so '*, etag' is ok but not '*,etag' :)18:36
creiht*, etag doesn't really make sense anyways18:37
*** chandankumar_ has joined #openstack-swift18:41
creihtso I updated some comments on the if-none-match review18:43
creihtif I need to make any changes, I'll fix the typo18:44
creiht:)18:44
creihtunless anyone feels strong enough that it is absolutely required :)18:44
*** piyush has joined #openstack-swift18:45
cschwedenotmyname: regarding the differentation between * and "*" - it works with double quotes: from swift.common.swob import Match; print Match('bla, ""*""').tags18:46
creihtwell and would "*" ever be a valid etag in swift?18:46
*** piyush1 has joined #openstack-swift18:47
cschwedecreiht: don't think so :)18:47
creihtyeah :)18:47
openstackgerritA change was merged to openstack/swift: Relocate DATADIR to backends  https://review.openstack.org/8462418:47
*** piyush has quit IRC18:49
*** shri has joined #openstack-swift18:51
*** chandankumar_ has quit IRC18:55
notmynamemeeting if a few minutes18:57
notmynamecreiht: right, not valid from a swift perspective. just a way that swob isn't spec-compliant18:58
creihtyeah18:58
creihtbut we can also fix that outside of this patch18:58
notmynameright18:58
notmynameI'll take a look at your comments on the patch after the meeting18:59
notmyname(and potentially lunch)18:59
notmynameswift meeting time19:00
cschwedecreiht: I'm wondering why https://review.openstack.org/#/c/81646/6/test/unit/proxy/controllers/test_obj.py doesn't cover lines 667-674 in https://review.openstack.org/#/c/81646/6/swift/proxy/controllers/obj.py19:01
creihtcschwede: hehe yeah19:01
creihtI was just looking into that :)19:01
cschwedecreiht: :)19:01
zaitcevcreiht: "In combination with "Expect: 100-Continue" this allows the server" -- that is where the switch to Requests turns and bits your behind19:04
creihtzaitcev: heh indeed19:04
zaitcevour collective behind actually19:04
*** dmsimard has quit IRC19:07
*** donagh has joined #openstack-swift19:08
creihtcschwede: heh... so I put a return HTTPServiceUnavailable(request=req) in that block, and the tests fail19:09
creihtso the code is getting executed19:10
creihtzaitcev: luckily for the customer I'm working on this for, they are using .net which does work19:10
creiht100-continue support is something that we do need to figure out for the requests stuff19:11
*** dmsimard has joined #openstack-swift19:13
*** dmsimard1 has joined #openstack-swift19:16
*** dmsimard has quit IRC19:17
*** JuanManuelOlle has joined #openstack-swift19:22
*** fbo is now known as fbo_away19:30
notmynamecreiht: i'll take a look at the patches after I grab some lunch19:36
cschwedecreiht: argh, this makes me crazy. if i put a "print" in line 668 in swift/proxy/controllers/obj.py it won't be executed running the unit tests19:37
cschwedecreiht: so coverage is right, but then the code is executed when actually used (ie outside unit tests)19:37
notmynamecschwede: isnt' that nose eating stdout?19:37
cschwedenotmyname: no, called nose with "nosetest -s" and added also a print right before that to make sure i don't miss anything19:38
notmynameah19:38
*** judd7_ has joined #openstack-swift19:38
*** donagh has quit IRC19:38
*** gvernik has quit IRC19:39
creihtcschwede: hrm19:39
cschwedecreiht: hmm, got it, wait a sec19:40
*** judd7 has quit IRC19:40
cschwedecreiht: if i add two brackets around the statement the print command is executed in the unit tests. but coverage still doesn't notice it19:43
cschwedeif req.if_none_match is not None and ('*' in req.if_none_match):19:43
creihtcschwede: that doesn't make sense19:44
cschwedecreiht: eh, forget what i said. somethings broken here.19:44
cschwedesorry for the noise...19:44
creihthehe19:45
cschwedecreiht: well, anyways. coverage report is somehow wrong, code looks good to me and works as expected, and tests are executed19:48
creihtyeah... I was just double checking the functional tests to make sure they work as expected19:48
creihtit is weird19:48
openstackgerritChuck Thier proposed a change to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445619:52
*** csd has quit IRC19:52
creihthad to fix a couple of small typos19:52
cschwedecreiht: I'll just add my "+2" to the patch without approving - in case someone else wants to have a look before merging19:53
creihtk19:53
creihtthx19:53
acolescschwede: hah! i had same idea :)19:53
creihtlol19:53
acolescreiht: about my unit test comment...19:54
creihtacoles: yes19:54
cschwedeacoles: hehe, so if we put both a 0.5 to the approve it will get merged ;-)19:54
acolescschwede: or tease creiht with .4999 :)19:55
acolescreiht: ok, so its late here and i may have brain fatigue, but i'm not seeing it19:55
creihtacoles: ok, it is possible I misunderstood your question19:55
openstackgerritA change was merged to openstack/python-swiftclient: Removed usage of tuple unpacking in parameters.  https://review.openstack.org/8402419:55
acolesi.e. a second put to existing object with if-none-match that does not match so therefore resulting in a 201 response19:56
creihtoh19:56
creihtwith '*' it will never put if there is any object there19:56
acolescreiht: yes. i'm referring to the non-* case at the object server (since obj server is matching against etags)19:57
creihtoh19:57
creihtheh19:57
creihtyeah forgot this was the object server19:57
*** tsg has joined #openstack-swift19:58
acolescreiht: :)19:58
acolesanyways...i decided on my commute that since its not functionality that is exposed (yet) that the test could wait, for the sake of progressing this19:58
creihtacoles: thx19:59
acolescreiht: cschwede: so one remaining nit is notmyname's observation about whitespace in the etag list (even though etag lists have no value here :)20:00
creihtlol seems my hasty refactor doesn't past flake820:00
cschwedecreiht: do you mind if i update the the clean up patch? Some unused imports in request_helpers20:00
creihtcschwede: by all means20:00
creihtacoles: yeah, but that should be fixed outside that patch20:00
creihtas it is a bug in swob20:00
acolescreiht: cool20:01
cschwedeacoles: yep, i had some troubles with common.swob.Match as well20:01
openstackgerritChristian Schwede proposed a change to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445620:04
creihtcschwede: thx20:05
cschwedecreiht: you're welcome. but i was to hasty, adding an empty line in request_helpers. oh my...20:06
openstackgerritChristian Schwede proposed a change to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445620:07
creihtlol20:08
openstackgerritA change was merged to openstack/swift: Range requests not working with sub_SLOs  https://review.openstack.org/8448320:08
*** mkollaro has joined #openstack-swift20:08
openstackgerritChristian Schwede proposed a change to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445620:08
cschwedeok, it's definitive too late here. I'l continue tomorrow morning...20:09
creihtcschwede: hah... thanks for the help today20:09
cschwedecreiht: no problem, you're welcome! let me know if there is an urgent review i can do in around 10 hours20:10
creihtwill do20:11
creihtbut it is looking like things are winding down20:11
cschwedenice :) see you all, have a nice day! bye20:13
*** fifieldt has quit IRC20:20
*** fifieldt_ has joined #openstack-swift20:20
*** RockKuo_TW has joined #openstack-swift20:35
*** JuanManuelOlle has quit IRC20:35
*** RockKuo has quit IRC20:38
notmynameif-none-match patch marked as approved20:39
notmynamecreiht: are you looking at or pushing anything to the swift*info patch?20:40
*** JuanManuelOlle has joined #openstack-swift20:40
creihtnotmyname: well I'm a bit conflicted since I contributed to it :)20:42
creihtand my allergies are killing me20:42
notmynameyikes. oak is killer today http://saallergy.info20:42
creihtyup20:42
notmynamecreiht: just checking if it's ready for me to review or if you have something outstanding20:42
creihtand we made the mistake of eating outside at chuy's for lunch today20:42
creihtahh20:42
creihtnotmyname: as far as I know it should be ready20:43
notmyname(not that all of your work isn't outstanding)20:43
notmynameok20:43
creihtlol20:43
tdasilvanotmyname: just heard about the Swift June Hackathon, is that open to non-core developers?20:43
notmynametdasilva: it is! https://www.eventbrite.com/e/openstack-swift-june-hackathon-tickets-830956914520:44
tdasilvanice...i'd like to attend...we'll see20:45
tdasilvathx20:45
*** rmitchell has joined #openstack-swift20:47
rmitchellI'm trying to troubleshoot a 503 error from my swift cluster20:47
*** JuanManuelOlle has quit IRC20:47
rmitchellI've looked in /var/log/messages20:47
rmitchellnada20:47
rmitchellI'm using Keystone for Auth20:48
rmitchellI can do every action but when I attempt to delete a container I get not found20:49
rmitchellCan anybody give me some pointers ?20:49
rmitchellSwift is hard ;)20:50
*** a_hacker has joined #openstack-swift20:50
*** csd has joined #openstack-swift20:50
notmynamermitchell: have you reconfigured syslog to send the messages somewhere else20:53
notmyname?20:53
notmynamermitchell: where are you getting the 503? what operation?20:53
*** tdasilva has left #openstack-swift20:55
*** lpabon has quit IRC20:56
*** JuanManuelOlle has joined #openstack-swift20:59
*** JuanManuelOlle1 has joined #openstack-swift21:03
rmitchell<+notmyname> I've added the following to the proxy-server.conf21:03
rmitchell# Logging set log_name = proxy-server set log_facility = LOG_LOCAL0 set log_level = DEBUG set log_address = /var/log/proxy-server.log21:04
*** JuanManuelOlle has quit IRC21:04
rmitchellAnd run swift-init proxy restart21:04
notmynamermitchell: I don't think that will work for log address21:07
rmitchellmakes sense - I'm not seeing a log file21:07
rmitchell;)21:07
*** JuanManuelOlle has joined #openstack-swift21:08
notmynamermitchell: ya, that's for the syslog device (or you can set it up for udp logging to a remote host)21:08
notmynamermitchell: you'll need to configure rsyslogd.conf or syslogng.conf (or whatever you're using) to redirect the logs out to a custom file21:09
rmitchellok - and /dev/log just goes to syslog21:09
*** JuanManuelOlle1 has quit IRC21:09
notmynameright21:10
notmynamermitchell: eg http://docs.openstack.org/developer/swift/development_saio.html#optional-setting-up-rsyslog-for-individual-logging21:10
rmitchellI've gone back to /dev/log.  Assuming the default will put into syslog21:10
*** bvandenh has joined #openstack-swift21:12
*** Trixboxer has quit IRC21:15
notmynamecreiht: can you share any more about the .net user who needs the if-none-match support? what's their use case?21:17
*** bvandenh has quit IRC21:20
notmynameInfo is uncomplete!21:22
*** JuanManuelOlle has quit IRC21:23
*** dmsimard has joined #openstack-swift21:23
*** dmsimard1 has quit IRC21:24
*** sungju_ has joined #openstack-swift21:36
*** foexle has quit IRC21:37
rmitchell<+notmyname> got past the 503.  Had a misconfigured proxy (which has now been shutdown).  I can create a container, but swift reports back a 404.  However I can then turn around and put an object in the container and I get a 40421:39
notmynamermitchell: so you PUT to a container, get a 404, and then try to PUT and object in the container and get a 404?21:39
notmynameyou'll get a 404 on a container PUT if the account doesn't exist. the rest sounds normal to me21:40
rmitchellWhen I shell, I see part of the URI on disk21:40
rmitchellI think the account must exist - I'm using it to connect and interact with the cluster21:41
rmitchellWe're utilmately trying to get to the point of running cosbench - it terminates with 40421:42
notmynamermitchell: your keystone account isn't the same thing as a swift account. pay no attention to the common substring of "account" ;-)21:45
rmitchellI'm obviously confused ;)  We are creating accounts on Keystone.  We are configuring Swift to use Keystone for authentication.21:47
rmitchellWe are able to auth with keystone and then swift stat21:48
notmynameand what do you see when you do that?21:48
notmynamewhat's the value of account_autocreate in your proxy config files?21:48
rmitchell [root@sprswiftprox01 envs]# swift stat   Account: AUTH_838dec975ad948e1aab29c203f5dfb48 Containers: 7   Objects: 021:49
notmynameok, that's good21:49
notmynameso `swift post container` doesn't work?21:49
rmitchellaccount_autocreate = true21:49
rmitchell[root@sprswiftprox01 swift]# swift post container Container PUT failed: http://sprswiftprox01.stni.seagate.com:8080/v1/AUTH_838dec975ad948e1aab29c203f5dfb48/container 404 Not Found  [first 60 chars of response] <html><h1>Not Found</h1><p>The resource could not be found.<21:50
rmitchell[root@sprswiftprox01 swift]# swift stat   Account: AUTH_838dec975ad948e1aab29c203f5dfb48 Containers: 8   Objects: 0     Bytes: 0 Accept-Ranges: bytes X-Timestamp: 1396290904.79357 Content-Type: text/plain; charset=utf-821:50
rmitchell[root@sprswiftprox01 swift]# swift list container containerz containter2 cosbench_trouble mycontainers_1 new_test testing testing221:51
*** sungju_ has quit IRC21:51
rmitchellcontainer put failed, but swift stat then lists it ?21:51
*** sungju_ has joined #openstack-swift21:52
rmitchellanother example21:52
rmitchell[root@sprswiftprox01 swift]# swift post notmyname Container PUT failed: http://sprswiftprox01.stni.seagate.com:8080/v1/AUTH_838dec975ad948e1aab29c203f5dfb48/notmyname 404 Not Found  [first 60 chars of response] <html><h1>Not Found</h1><p>The resource could not be found.< [root@sprswiftprox01 swift]# swift stat   Account: AUTH_838dec975ad948e1aab29c203f5dfb48 Containers: 9   Objects: 0     Bytes: 0 Accept-Ranges: bytes X-Tim21:52
notmynamepaste.openstack.org might be good here ;-)21:52
notmynamermitchell: ok, let's walk through some API requests and see where it fails21:53
rmitchellgotcha21:53
notmynamermitchell: you got the logging set up? ie you can see logs now?21:53
claygpaste.openstack.org is never *good* - it's tolerably slow sometimes...21:53
openstackgerritJohn Dickinson proposed a change to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445621:54
notmynameclayg: well, that's true21:54
notmynamecreiht: added my own patches to the swift-{account,container}-info patch21:54
notmynamecreiht: mostly to fix the pep8 and typo in tests bug. but then also so that swift-object-info uses the same ring locations code too21:55
*** sungju_ has quit IRC21:56
rmitchell+notmyname - are you interested in the proxy server logs ?21:57
notmynamermitchell: mostly just that you can see them :-)21:57
rmitchellyep - seeing handoff requests on the proxy server logs21:57
portanteclayg, notmyname: got a fix for constraints comin'21:58
portantein order to change a constraint for testing, unit or functional, each test seems to pick the location that it gets used21:58
rmitchelland 404 errors from the container-server on the storage nodes21:58
portantebut this means relies on the binding at module import time21:59
notmynamermitchell: I think you need to figure out why the handoff nodes are being used21:59
notmynamermitchell: you've got all the processes running in the cluster, right? ie servers + replication + auditing + etc22:00
*** erlon has quit IRC22:02
rmitchellWe've got Nagios monitoring servers and validating the expected numbers of processes22:03
*** Midnightmyth has quit IRC22:04
openstackgerritPeter Portante proposed a change to openstack/swift: Rework use of straights to ease testing  https://review.openstack.org/8487722:05
rmitchellDoes the log entry "proxy-server Handoff requested (1) (txn: tx61ec43fe14ff4f10a524c-00533c84f5) " indicate that a Handoff is actually being used or does it indicate that a handoff is being identified ?22:05
openstackgerritPeter Portante proposed a change to openstack/swift: Rework use of constraints to ease testing  https://review.openstack.org/8487722:06
*** dmsimard has quit IRC22:06
notmynamermitchell: being used22:06
openstackgerritJohn Dickinson proposed a change to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445622:08
notmynamermitchell:  ok, got that patch taken care of. it was distracting me22:09
notmynamermitchell: you're getting a 404 in response to the PUT. but it's showing up in the listing. which is strange to me22:09
notmynamermitchell: I'd suggest walking through some commands with curl so you know exactly what's going on22:10
notmynamermitchell: start with `swift stat -v` first (assuming you have all the auth creds set in env vars. that will show you the storage url and the auth token you'll need22:10
notmynamermitchell: eg on my SAIO https://gist.github.com/notmyname/187831cb63bd1078eece22:11
notmynamermitchell: so from that, I can do this: https://gist.github.com/notmyname/185edb46b169c5fe434522:12
notmynamermitchell: that's a listing followed by a PUT to create a container, then another listing22:12
rmitchellok - ran swift stat -v22:13
notmynamermitchell: notice that in each of those responses there is the X-Trans-Id header. that's returned on every response from swift and it uniquely identifies that request/response. so you can grep for it in your logs and see everything that happened22:13
rmitchellok22:14
rmitchellsee that22:14
rmitchellhave seen the TX in syslog also22:14
creihtnotmyname: who is going to review it if we all make contributions? :)22:15
notmynamermitchell: so what will be interesting to see is the logs from your container PUT and then from the subsequent container listing22:16
notmynamecreiht: :-)22:16
notmynamecreiht: I would have gone ahead and put my +2, but I didn't since I also changed a few things (and added the swift-object-info stuff)22:16
notmynamecreiht: well it's not like this is patching the ring builder or anything. if you add your +2 I'll add mine and merge it :-)22:18
creihthaha22:18
creihtI was just looking at it22:18
*** Jesse22 has joined #openstack-swift22:18
rmitchell+notmyname Re: http://paste.openstack.org/show/74911/22:18
*** piyush has joined #openstack-swift22:18
*** piyush has left #openstack-swift22:19
*** Jesse22 has quit IRC22:19
rmitchellWhen I check on disk I can see the 59824 directory structure on disk on the primary nodes but nothing inside them22:19
rmitchellI do not see anything on the handoff nodes22:19
*** piyush1 has quit IRC22:20
notmynamermitchell: one of the next things to do is make sure you have the same rings everywhere. eg if you have swift-recon installed (and why wouldn't you?), run `swift-recon --md5`22:21
rmitchell8/8 hosts matched, 0 error[s] while checking hosts.22:23
notmynameok, that's good.22:23
creihtnotmyname: the ring locations for swift-object-info is wrong22:23
notmynameah. oops22:23
creihtit is showing it as hash.data instead of ts.data22:24
notmynamebah22:24
creihthaha22:24
notmynamewell that makes it not nearly as much fun22:28
*** MarkWStorer has joined #openstack-swift22:28
creihtyeah, I thought of messing with the object stuff but then realized it might be a little trickier than I wanted to mess with at the time :)22:28
*** MarkWStorer has quit IRC22:28
rmitchell<+notmyname> any other suggestions ?22:29
notmynamecreiht: ya. I'm reverting that and I'll push it again22:29
notmynamermitchell: can you paste the logs for a container PUT and then the account listing?22:30
*** MarkWStorer has joined #openstack-swift22:32
*** MarkWStorer has quit IRC22:32
notmynamecreiht: ...which actually allows for a little more cleanup22:35
creihtlol22:36
notmynamethis is the most complicated simple patch in a while ;-)22:38
creihthah22:38
*** mwstorer has joined #openstack-swift22:39
rmitchell+notmyname thx - http://paste.openstack.org/show/qZyw42N8PEzkR7F9qQF3/22:42
*** zackf has quit IRC22:43
*** mkollaro has quit IRC22:43
notmynamermitchell: looks like the long keystone token is hiding some info. add "reveal_sensitive_prefix = 12" to the proxy config in the proxy-logging section. that way it will only show the first 12 bytes of the auth token22:44
notmynamermitchell: also, seeing the storage logs too would be helpful22:44
openstackgerritJohn Dickinson proposed a change to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445622:46
notmynamecreiht: ^^22:46
openstackgerritJohn Dickinson proposed a change to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445622:48
notmynamewhat's one more patch set?22:48
notmynameI had a typo in the swift-object-info, so I reverted that whole file back to master22:49
creihtlol22:49
notmynameok, I think I'm good now :-)22:50
notmynamecreiht: compare with patch set 7 to see what I actually ended up changing22:50
notmynamehmm...just noticed the bare except with no # noqa22:51
creihthah22:51
rmitchell+notmyname http://paste.openstack.org/show/AxrUJPmFSq0euWCmVklq/22:52
notmynamecreiht: did you see what rmitchell is doing? POST/PUT to create a container, gets a 404, but its in the listing22:53
creihtnotmyname: sorry haven't followed closely22:54
notmynamecreiht: well, that's the tldr ;-)22:54
creihthah22:54
notmynamermitchell: can you grep your storage node logs for transaction id "tx26b8fa1b186b413b9ac44-00533c9454" ?22:54
rmitchell+notmyname http://paste.openstack.org/show/2kSvHMeIiwuWi8nZ6EVV/    output from storage node22:54
notmynamermitchell: that's the container create22:54
notmynameah, ok22:54
creihtnotmyname: I'm actually just trying to hold on long enough to get this last patch in22:56
creihtallergies kinda have me down22:56
notmynamecreiht: no worries :-)22:56
notmynamecreiht: so the reason for the bare except is to test the call to ring. but the test code only passes in []22:57
notmynameso it gets AttributeError and then the info code raises ValueError22:57
creihtcan you just do22:58
creihtexcept Exception:22:58
notmynameya, I was thinking  except (ValueError, AttributeError):22:59
rmitchell<+notmyname>  any ideas ?23:01
notmynamermitchell: just a second. I'm trying to finish up this last patch for Icehouse with creiht too :-)23:02
rmitchellok, sorry (blush)23:02
openstackgerritJohn Dickinson proposed a change to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445623:03
notmynamecreiht: ok, there.23:03
notmynamermitchell: no worries23:03
notmynamermitchell: maybe I foudn something23:05
notmynamermitchell: lot's of assumptions here, but maybe it's your issue23:06
rmitchellexcited23:06
a_hacker;)23:06
rmitchellsounds probable23:06
rmitchell<waits with baited breath>23:06
notmynameneed to check on emore thing23:07
clayg*bated23:07
notmynamewell, maybe not23:08
rmitchellI've been eating fish ;)23:08
notmynamermitchell: here's what I was thinking....you have a port number wrong in your ring23:08
creihtnotmyname: ok looks good to me23:09
creihtI'm out, see everyone tomorrow23:09
notmynamecreiht: feel better :-)23:09
creihtheh23:09
creihthope so23:09
notmynamermitchell: but looking again, that may not be it. I was seeing the referer log field not the actual request23:09
notmynamermitchell: ie I was thinking the account server was responding to a container request23:10
notmynamermitchell: something to check, for sure. but I'm not sure it's the issue now23:10
rmitchellports look correct on output from lsof on a sample storage node - 6000, 6001, 600223:11
rmitchellI'm going to have to bail and digg into this in the morning23:15
notmynamermitchell: ah ok. a_hacker are you on this too?23:16
a_hackerYes sir23:16
a_hacker:)23:16
rmitchellthanks for your help in looking into this with us23:16
notmynamesure23:16
notmynamea_hacker: you want to keep looking?23:16
a_hackerI'm about to bail as well23:16
notmynameah ok23:16
rmitchellAny reccomended reading on tracing a transaction through the system as we have been doing23:16
a_hackerBut rest assured you will see us tomorrow or even later tonight23:16
notmynamermitchell: I think you have it. use the transaction id23:17
zaitcevI saw those phantom 404s when updaters failed to keep up, but in such cases re-posting that container allowed to delete or use it normally.23:17
notmynamermitchell: a_hacker: seems that the next steps are to simplify the system until it works as expected and then see what goes wrong23:17
zaitcevFixing updaters first of course.23:17
notmynamea_hacker: rmitchell: eg turn off services and using curl instead of the CLI23:18
rmitchellmakes sense23:18
rmitchellthanks again23:18
a_hackerSounds good, we'll play with it some more. Thanks for your help.23:18
notmynameof course23:18
zaitcevIf rmitchell screwed up port assignments, it would be a different error, not 404. I forgot what but it's some kind of Invalid Argument. 420 or something.23:18
* notmyname starts to work on CHANGELOG updates for Icehouse then23:19
notmynamezaitcev: ya, that makes sense23:19
notmynamezaitcev: you thinking of switching over to working on keystone? ;-)23:19
notmynamezaitcev: re your twitter comments :-)23:20
openstackgerritJenkins proposed a change to openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8349323:20
zaitcevnotmyname: I'm surprised because I thought RAX had their own auth.23:20
notmynamezaitcev: ya, but they also invented keystone23:20
zaitcevah23:20
notmynameRAX is an enigma ;-)23:20
openstackgerritJenkins proposed a change to openstack/swift: Updated from global requirements  https://review.openstack.org/8120723:20
zaitcevAnd gosh guys, I went to look over If-None-Match and it's already merged!23:21
zaitcevAgile devel!23:21
notmynameok, why do the global requirements need to be bumped up so often? keystone bumps a version that some library wants and we all need a new version of it? what if the old version still works?23:21
*** a_hacker has quit IRC23:22
*** rmitchell has quit IRC23:22
notmynameclearly this release-critical bug of a minor version bump in keystoneclient must be merged immediately!23:23
* notmyname can only hold back the snark for so long23:23
zaitcevyou are sarcastic, aren't you23:23
notmynameat least my -2 stays on the swift one. updating keystoneclient in test-requirements on swiftclient. sure, I guess. clearly there are valid and critical reasons this is needed23:24
notmynamelet's just go ahead and bump it to >=1.0 so we can just skip over the next several releases23:25
*** bada has quit IRC23:26
notmynameis it appropriate to put a doge meme on a gerrit review?23:26
notmynametoo late23:26
Alex_GaynorI lol'd23:27
notmyname:-)23:28
Alex_GaynorI think the answer to all questions about syncing wrt to global-requirements is that ~~distros~~ want to make sure they can always install everything in one giant global namespace23:28
notmynameright. I totally get that. I'm not opposed to the idea of global requirements. I'm not a big fan of openstack's current implementation of the idea23:30
notmynameeg if we started using some new feature in eventlet 2.0 (because we wrote the feature and it was brackwards-breaking), does that mean that every openstack project now needs to use eventlet 2.0? (substitute whatever library you want)23:31
notmynamethe simpler case (no version brackets) would be massively improved by having a simple version solver23:32
notmynameeg swift's requirements are >= older versions than in global requirements. still works, no conflicts23:32
notmyname(but I will admit we're a little bit lucky in that sense, that some other openstack project or upstream dependency hasn't put an upper bound on some dependency)23:33
*** dmsimard has joined #openstack-swift23:47
*** keving has joined #openstack-swift23:52
portantenotmyname: still around?23:59
notmynameportante: yup. what's up?23:59
portanteanything left to review?23:59

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