Thursday, 2014-04-03

portanteand about license headers00:00
notmynameportante: nope. creiht and I worked out the -info one, so jsut waiting for the zuul dance00:00
portanteI get pep8 failures on my system with that00:00
notmynamehmm..I was hoping someone wouldn't say anything about that ;-)00:00
portantedid I do that?00:00
notmyname:-)00:00
* portante puts on his best erkle immitation00:01
notmynameportante: in the -info patch?00:01
portanteso you are not concerned about the pep8 issues?00:01
portanteyes00:01
portantethree failures00:01
portanteand the fact that it only has 27% coverage00:02
portante;)00:02
* portante portante piles on00:02
*** RockKuo has joined #openstack-swift00:02
portantejust shoot me00:02
portanteif you want, i can work on the coverage00:03
notmynamelooks like the header thing needs to be fixed to pass jenkins00:03
notmynameportante: if you work on coverage can you also push the headers?00:05
portanteyes00:05
notmynameportante: this is the last thing for icehouse (except my authors/changelog updates which I'm working on now)00:05
notmynamethanks00:05
portantewelcome00:06
notmynameportante: I'll be around for about 1.5 hours, then out for the night00:06
portantek00:06
*** mwstorer has quit IRC00:07
*** shri has quit IRC00:11
*** csd has quit IRC00:20
*** matsuhashi has joined #openstack-swift00:28
*** csd has joined #openstack-swift00:30
*** bill_az has quit IRC00:51
openstackgerritPeter Portante proposed a change to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445600:57
notmynameportante: looking00:58
portantenot done yet00:58
portantealmost00:58
portantejust wanted to show the vector I am no00:58
portanteon00:58
portantejust writing the final set of unit tests00:58
portantegot coverage for the rings now00:58
*** csd has quit IRC00:59
notmynamecool00:59
notmynameportante: reconcile the exception catching on the ring in info.py00:59
notmynameportante: line 47 and 16501:00
notmynameportante: are you going to do any more unification on print_*_info()?01:00
notmynameportante: also, I think it needs copyright headers of some sort01:01
*** dmsimard has quit IRC01:02
portantenotmyname: I was following this page: http://docs.openstack.org/developer/hacking/01:02
portanteis that not the up-to-date one?01:02
notmynameno idea01:02
notmynameI normally just copy/paste from another file ;-)01:03
notmynameportante: thanks for working on it01:04
creihtwait... I thought we moved the print code out so that it wouldn't be duplicated01:04
portantenotmyname: regarding unification, I had thought about it, but was going to drive the coverage first01:04
portantecreiht: coverage first, man!01:04
portantethen de-dupe01:04
creihtheh01:04
portanteat least that is what I am going to do01:04
creihtok I'll quit looking then :)01:04
portante;)01:05
openstackgerritA change was merged to openstack/swift: Add "If-None-Match: *" support to PUT  https://review.openstack.org/8164601:05
creihtat least until you are done01:05
notmynamecreiht: :-)01:05
notmynamecreiht: while you're waiting for that....01:05
*** matsuhashi has quit IRC01:05
creihtoh no01:05
notmynamecreiht: can you give me more detail on the if-none-match use case you have? I'm working on the changelog right now01:05
creihtnotmyname: I'm busy 3d printing stuff01:05
creiht:)01:06
notmynamecool01:06
creihthehe01:06
*** matsuhashi has joined #openstack-swift01:06
creihtso this customer only uploads one version of an object01:06
creihtthey absolutely only want to upload if it isn't already there01:06
notmynameie name == unique object?01:06
creihtso they have been doing heads before put01:06
creihtyes01:06
creihtwhich performs horribly for them01:06
creihtof course01:06
notmynameas one would expect01:07
creihtso this is an attempt to get them the same functionality but faster01:07
creihtI was hoping to add etag support as well so that it would be robust01:07
creihtbut then ran into too many hairy edge cases01:07
notmynamecreiht: ya I can see how that's much harder.01:08
notmynameeven so, it's interesting to think about because it's a new feature that has a very specialized use case01:08
creihtthe downside is that for it to be effective, you have to use expect: 100-continue01:08
*** keving has left #openstack-swift01:08
creihtwhich requests doesn't support >:(01:08
notmynameit's not functionally different than what was available before, but we need to be careful not to imply that you can use it to make an atomic write to swift01:09
notmynamecreiht: ya, that's a big negative to requests01:09
creihtabsolutely01:09
notmynameaugh!!01:09
notmyname*can't* *can't* use it for atomic writes01:09
notmynamesee?!01:09
creihtIt shoulf fulfill the same use case as doing a HEAD before PUT if you aren't comparing etags01:12
openstackgerritA change was merged to openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8349301:12
notmynamecreiht: ok. makes sense. that's what I expected you to say, but I wanted to check if there was anything else there01:12
claygunless the original write went to handoffs and the primaryes are now back online - in that case the head would 404, 404, 404, 200 where as if-none-match will just 200/overwrite01:13
notmynameclayg: :-)01:14
creihtit is also assumed that the version they are PUTing is the version they want01:14
creihtso in this case, they would just be helping the cluster recover :)01:14
clayg^ i like that wording!!!01:14
notmynameNew feature: now you can help Swift recover from errors!01:15
claygwell.. not that wording the other part - swift's if-none-match support assumes the client is attempting to upload the version of data they want01:15
creihtnotmyname: but yeah, it is a bit of an obscure feature :)01:16
claygit's almost exactly the opposite of what you'd expect when sending if-none-match: * - but it's definately what we've got01:16
notmynameclayg: I don't agree with that01:16
notmynameor at least that phrasing01:17
notmynameI don't see it as the opposite of what I'd expect01:17
* notmyname is hardly one to be determining what people not familiar with Swift are expecting01:17
claygi think if knew the data i had in hand was the version i wanted in the cluster i would say 'if-none-match: etag-of-data-about-to-be-uploaded'01:18
claygif i wanted to upload some new version - but not overwrite some old version i don't know the content of - i'd say if-none-match: *01:18
claygand that's just not really what you get *under failure* - the scary part is it works *most* of the time01:19
claygi worry people will rely on the behavior because - "swift supports if-none-match"01:19
creihtclayg: depends on what if means01:19
creiht;)01:19
claygi just wish it was documented to be more explicit about what usecase it's appropriate for and the gaurantees we can acctually offer vs what will be observed most of the time but not guaranteed01:21
*** nthacker has joined #openstack-swift01:22
nthackerhi All! Im interested in trying out swift on filesystems w/o xattr support01:22
nthackeri have been digging through the code myself...01:22
nthackerand in diskfile.py i see read_metadata and write_metadata which seem to do this work (writing Metadata to a file)01:23
nthackerbut when I try this on a filesystem over NFSv301:23
nthackerit doesnt seem to work...01:23
claygYES! YES! YES!01:23
nthackerany tips?01:23
* clayg goes to get popcorn01:23
nthackerclayg: haha01:24
creihtI was worried you were going to try to run it on NTFS :)01:24
swifterdarrellnthacker: NFSv401:24
nthackercreiht: haha, no. i am trying to run it on ext4 over nfsv301:24
nthackerswifterdarrell: yes that works!01:25
notmynameswifterdarrell: dont' you mean NFSv4.1?01:25
swifterdarrellnthacker: also, you're better off with reiserfs over nfsv401:25
nthackerswifterdarrell: yes i realize nfsv4 is a good way to go, but lets say i really need to use nfsv3 :) ...im jus hacking around though01:25
notmynamenthacker: so here's the deal. it's really late in the day for all of us and you aren't getting serious answers. the serious answer is to not do that.01:25
nthackerswifterdarrell: i do see some work that will come out in icehouse01:26
notmynameseriously. don't do that (also, don't listen to swifterdarrell)01:26
notmynamewhat you want to do is wait01:26
notmynamelike 6 months01:26
nthackernotmyname: wow...01:26
notmynameand we should have better interfaces in swift for that01:26
notmynamethey're sorta there now01:26
notmynamebut they'll get better01:26
nthackernotmyname: can i try some bleeding edge code??01:27
notmynameand it will be a huge about of work to do it now01:27
notmynamewhich would be great and all, but really. it will be a. lot. of. work.01:27
nthackernotmyname: ah ....interesting....though the code looks quite simple at first glance, i'd take your word for it01:27
swifterdarrellnthacker: maybe embed the swift-proxy into a kernel module inserted just after nfsv301:27
nthackerswifterdarrell: haha01:28
swifterdarrellnthacker: just make sure to pay attention to If-None-Match headers, they may increase network filesystem latencies under load01:28
swifterdarrellalso noatime01:28
notmynamenthacker: I really want to see swift supporting stuff like that. specifically, I really like the idea of migrating in existing data stores into swift. but the reality is that we arent' there yet01:28
*** nosnos has joined #openstack-swift01:29
nthackernotmyname: I understand...i read some of the blueprints and the refactorings for diskfile...but what if i wanted to hack something to make it *work*01:29
notmynamenthacker: and we've seen code and had conversations with existing storage vendors who want to make swift work with their existing products (you may work for one of those companies, I don't know)01:29
notmynamenthacker: then you're looking at the DiskFile abstraction01:29
notmynamenthacker: good places to start are with the gluster-swift project (which, despite its name, doesn't have much to do with glusterFS). it's about putting swift on top of an arbitrary file system01:30
notmynamenthacker: and as such it's a really interesting project.01:30
nthackernotmyname: Great!  in gluster-swift they have managed to hack the DiskFile abstraction01:31
nthackerto work with fs w/o xattrs?01:31
notmynamenot hack. use properly ;-)01:31
notmynameactually I'm not sure. gluster-swift today is designed to run swift code (upstream, no fork) on top of glusterfs01:31
*** zackf has joined #openstack-swift01:32
nthackernotmyname: well that sounds interesting - i'll def poke around their repo on github01:32
notmynameI've installed it. it takes about 10 minutes. they are providing their own disk file abstraction to make it work01:32
swifterdarrellnthacker: if you want a real project, make it store metadata in long cylinders filled with mercury01:32
nthackerswifterdarrell: some real innovative ideas you got!01:32
nthackerswifterdarrell: not trying to change the world you know, just store my metadata in a file :)01:33
Alex_Gaynorswifterdarrell: I'm totally working on a project whose tagline is "Mercury delay lines for the cloud"01:33
notmynameAlex_Gaynor: (he was looking for that phrase)01:33
notmynameswifterdarrell: what about memristors?01:33
notmynamememristors in the cloud! you can have docker in your storage system?01:34
notmynameportante: I'm going to need to check out soon. I'll look at the patch again in the morning, and we won't cut anything until it lands01:36
notmynameportante: but i'm happy with where it is and is going01:36
portantegreat, almost got the coverage01:36
portantenotmyname:01:37
notmynameportante: cschwede: acoles: chmouel: (all you core people significantly east of me) it would be very nice to have it reviewed and merged as soon as possible tomorrow, since ttx is in france01:37
notmynameso that I can do the authors/changelog and we'll be ready asap01:38
*** dmorita has joined #openstack-swift01:38
openstackgerritPete Zaitcev proposed a change to openstack/swift: Pluggable Back-ends for account and container servers  https://review.openstack.org/4771301:41
*** zackf has quit IRC01:44
*** tsg has quit IRC01:49
*** haomaiwang has quit IRC02:02
*** haomaiwang has joined #openstack-swift02:02
*** haomaiw__ has joined #openstack-swift02:20
*** zanc has quit IRC02:23
*** haomaiwang has quit IRC02:23
*** zaitcev has quit IRC02:39
*** bsdkurt has quit IRC02:53
*** bsdkurt has joined #openstack-swift02:54
*** fifieldt_ is now known as fifieldt02:54
*** madhuri has quit IRC02:58
*** matsuhashi has quit IRC03:05
openstackgerritPeter Portante proposed a change to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445603:08
*** nosnos has quit IRC03:23
*** zackf has joined #openstack-swift03:39
*** Edward-Zhang has joined #openstack-swift03:53
*** zackf has quit IRC03:55
*** judd7_ has quit IRC03:55
*** madhuri has joined #openstack-swift04:04
*** Edward-Zhang has quit IRC04:07
*** nosnos has joined #openstack-swift04:09
openstackgerritPeter Portante proposed a change to openstack/swift: Move module level setup under setup_package method  https://review.openstack.org/8433904:09
openstackgerritPeter Portante proposed a change to openstack/swift: Only change collation for functional tests  https://review.openstack.org/8432504:10
openstackgerritPeter Portante proposed a change to openstack/swift: Rework use of constraints to ease testing  https://review.openstack.org/8487704:10
openstackgerritPeter Portante proposed a change to openstack/swift: In-process swift server for functional tests  https://review.openstack.org/6610804:10
openstackgerritPeter Portante proposed a change to openstack/swift: Read the configuration once for all func tests  https://review.openstack.org/8433204:10
hugokuogaob .... I think it's a bug in Swift04:14
*** matsuhashi has joined #openstack-swift04:15
portanteclayg, notmyname, acoles, chmouel: the above series of patches moves us towards being able to run in-process functional tests04:15
portantehowever, the MAX_FILE_SIZE limit tests fail for some reason, which I have not been able to figure out yet04:16
portantethe changes leading up to in-process hopefully make sense and consolidate the functional test environment a bit04:17
*** Midnightmyth has joined #openstack-swift04:17
portanteglange, since you have looked at one of the early ones in the series, would you be willing to consider the others too?04:17
*** psharma has joined #openstack-swift04:18
*** gvernik has joined #openstack-swift04:21
*** gvernik has left #openstack-swift04:23
hugokuogaob : https://bugs.launchpad.net/swift/+bug/130172804:35
Anjuportante:, hugokuo :  why content-length is showing always 0 in a head of any object ?04:36
hugokuoAnju: not my case tho : http://paste.openstack.org/show/74922/04:39
hugokuoContent-Length: 8804:39
Anjuhugokuo:  let me check04:40
*** matsuhashi has quit IRC04:40
Anjuhugokuo:  one thing more , if I am giving content-length =004:40
Anjuin a put request of any object04:40
AnjuIts going fine04:41
Anjubut when I am giving any value other than 004:41
Anjuthen put request not completing successfully04:42
Anjuhugokuo:  http://paste.openstack.org/show/74925/04:44
*** matsuhashi has joined #openstack-swift04:46
Anjuhugokuo:  please try with other user(non admin)04:50
*** ppai has joined #openstack-swift04:52
hugokuoAnju: if you give the content-length: 0 in PUT request, then the object will be an empty object in Swift.  That's why you saw the length of HEAD in 0. That make sense for me tho.04:56
hugokuoYou need to specify the correct content-length during PUT.04:56
Anjuhugokuo:  http://paste.openstack.org/show/74926/04:57
*** Edward-Zhang has joined #openstack-swift04:58
hugokuoAnju: get it back. Check if that's an empty file....04:58
Anjuhugokuo:  no04:59
Anjuits not an empty file04:59
hugokuoAnju: I'm pretty sure it's an empty object hence the Etag is d41d8cd98f00b204e9800998ecf8427e in your head response tho.05:02
Anjuhugokuo:  http://paste.openstack.org/show/74927/05:03
Anjusee the diff05:03
hugokuoAnju: What's fun in this post ?   It's different object from my point of view....05:05
Anjuhugokuo:  first I put from admin account in a different container05:06
Anjuthe same file (.viminfo)05:06
hugokuofull curl command, please05:07
Anjuhugokuo:  yeah sorry05:09
Anjuhugokuo:  http://paste.openstack.org/show/74928/05:10
hugokuoAnju: What's the commands that you upload these two objects ...05:11
Anjuhugoko : I uploaded first   swift -A http://127.0.0.1:8080/auth/v1.0 -U admin:admin -K admin upload anju .viminfo05:12
Anjufor test2   swift -A http://127.0.0.1:8080/auth/v1.0 -U test2:tester2 -K testing2 upload anjua .viminfo05:13
*** Midnightmyth has quit IRC05:18
*** cheri has joined #openstack-swift05:18
hugokuoAnju: http://paste.openstack.org/show/74929/  everything works as expectation in my end.  ......05:22
Anjuhugokuo:  ohhh , then05:23
Anjusomething going wrong in my side05:23
hugokuoAnju: Well, I guess that you just upload the wrong file.  Maybe you can check the log for more clues there.05:24
Anjuhugokuo:  one thing more , you said if I will provide correct size of a file05:24
Anjuin the content length05:25
Anjuin a put request05:25
Anjuof any object then it will be fine ? right ?05:25
*** bvandenh has joined #openstack-swift05:33
hugokuoAnju: I use -T to specify the upload file. It works for whatever the content-lenght is...05:37
Anjuare you using curl ?05:37
Anjuhugokuo:  it will be very helpful if you can paste05:38
hugokuocurl -i -X PUT http://localhost/v1/AUTH_test2/1/test1 -H "X-auth-token:AUTH_tkf13c2948382c43b0ae39bd5949c59570" -T 105:38
*** haomaiw__ has quit IRC05:40
*** haomaiwang has joined #openstack-swift05:41
openstackgerritYuan Zhou proposed a change to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445606:00
*** haomai___ has joined #openstack-swift06:01
*** cheri has quit IRC06:03
*** haomaiwang has quit IRC06:05
*** psharma has quit IRC06:16
yuanhi peter, is the copyright belongs to openstack foundation, sth like this Copyright (c) 2010-2012 OpenStack Foundation?06:20
yuanportante: the header for Intel is: Copyright 2014 Intel Corporation, All Rights Reserved.06:26
openstackgerritChristian Schwede proposed a change to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445606:26
cschwedeyuan: afaik you can use a header like this: http://paste.openstack.org/show/74931/06:29
cschwedepython26 test already passed :) now i hope we can merge this very soon :)06:30
*** psharma has joined #openstack-swift06:31
yuancschwede: OK, I see it, so the new file will need to have a copyright header from the author's employer?06:32
cschwedeyuan: it doesn't need it - but you are free to add one, depends on your employer. disclaimer: i am no lawyer ;-)06:33
yuancschwede: ahh, I think it's OK to skip that :)06:35
*** matsuhashi has quit IRC06:36
*** nshaikh has joined #openstack-swift06:37
cschwedeyuan: all right :)06:37
cschwedeyuan: so python27, pep8 passed too, as soon as all tests passed i'll add my +2 to ithe patch06:37
*** matsuhashi has joined #openstack-swift06:39
yuanthanks a lot! it turns out to be a  bigger refactoring than i plan to do initialy...06:44
*** psharma has quit IRC07:03
*** zigo has quit IRC07:04
*** zigo has joined #openstack-swift07:08
*** psharma has joined #openstack-swift07:30
*** cheri has joined #openstack-swift07:46
*** mmcardle has joined #openstack-swift07:53
*** nacim has joined #openstack-swift07:55
*** mlipchuk has joined #openstack-swift08:03
*** tanee-away is now known as tanee08:12
*** tanee is now known as tanee-away08:12
*** tanee-away is now known as tanee08:13
*** tanee is now known as tanee-away08:13
*** tanee-away is now known as tanee08:13
*** fbo_away is now known as fbo08:16
openstackgerritVictor Stinner proposed a change to openstack/python-swiftclient: Fix test_multithreading on Python 3  https://review.openstack.org/8410408:31
*** foexle has joined #openstack-swift08:44
*** psharma has quit IRC08:57
*** matsuhashi has quit IRC09:07
*** matsuhashi has joined #openstack-swift09:12
*** madhuri has quit IRC09:15
*** Longgeek_ has joined #openstack-swift09:24
*** psharma has joined #openstack-swift09:46
*** Trixboxer has joined #openstack-swift09:51
*** mkollaro has joined #openstack-swift09:53
*** Longgeek_ has quit IRC09:56
openstackgerritPeter Portante proposed a change to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445609:58
*** matsuhashi has quit IRC09:59
*** matsuhashi has joined #openstack-swift09:59
portantecschwede, yuan: ^^^, thanks for the fix, the use of datatime.utcfromtimestamp() method is needed so that we get consistent results on systems that don't run under UTC (like my laptop)10:00
portantechmouel, acoles: ^^^10:00
*** fbo is now known as fbo_away10:09
*** mkollaro has quit IRC10:10
Anjuportante:  hiii, when container_stat tables put_timestamp field value will change ? on every object upload ?10:17
portanteAnju: good question, I'd have to look ... but in a bit10:19
Anjuportante:  will be thankful10:20
*** dmorita has quit IRC10:22
*** chandankumar_ has joined #openstack-swift10:22
*** Longgeek_ has joined #openstack-swift10:43
*** Edward-Zhang has quit IRC10:46
*** dmsimard has joined #openstack-swift10:46
*** matsuhashi has quit IRC10:48
*** Longgeek_ has quit IRC10:50
*** matsuhashi has joined #openstack-swift10:55
*** tdasilva has joined #openstack-swift11:06
*** mlipchuk has quit IRC11:10
*** tanee is now known as tanee-away11:11
*** nacim has quit IRC11:14
*** matsuhashi has quit IRC11:15
*** matsuhashi has joined #openstack-swift11:15
*** matsuhashi has quit IRC11:19
*** ppai has quit IRC11:21
*** mkollaro has joined #openstack-swift11:21
*** matsuhashi has joined #openstack-swift11:21
*** zhiyan_ is now known as zhiyan11:22
*** jamie_h has joined #openstack-swift11:23
*** mlipchuk has joined #openstack-swift11:26
Anjuportante:  ^^^11:29
*** ppai has joined #openstack-swift11:32
*** Manish_ has joined #openstack-swift11:33
portanteAnju: just getting through my morning routine here in EDT, so I'll be able to review and answer a bit later, thanks for your patience.11:35
Anjuportante:  thankyou , no problem  :)11:36
*** Manish__ has joined #openstack-swift11:38
*** Manish_ has quit IRC11:38
*** tanee-away is now known as tanee11:38
cschwedeportante: yeah you're right, utcfromtimestamp is the way to go.11:44
cschwedeportante: according to https://github.com/openstack-dev/hacking/blob/master/HACKING.rst#openstack-licensing an Apache license only header is fine, so if Yuan and Madhuri are fine with that we could finish this11:44
*** tanee is now known as tanee-away11:48
*** tanee-away is now known as tanee11:49
*** matsuhashi has quit IRC11:52
Manish__hugokuo: Hi.... DO you know that who and when updates the "PUT_timestamp" column of "container_stat" table?11:58
*** tdasilva has quit IRC12:02
portantecschwede: okay, I'll fix up the bin one's to have just the license, and we can add madhuri's in another patch12:03
*** cheri has quit IRC12:04
*** tanee is now known as tanee-away12:04
*** tdasilva has joined #openstack-swift12:04
openstackgerritPeter Portante proposed a change to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445612:05
portantecschwede: ^^^12:05
*** mlipchuk has quit IRC12:05
cschwedeportante: thanks - I'll add my +2 to it, to me the patch looks good. Hopefully Jenkins agrees as well :)12:07
portante;)12:07
*** tdasilva has left #openstack-swift12:08
*** StevenK_ has joined #openstack-swift12:10
*** fbo_away is now known as fbo12:10
*** StevenK has quit IRC12:10
*** occupant has quit IRC12:10
*** MooingLemur has quit IRC12:11
*** cschwede has left #openstack-swift12:12
*** cschwede has joined #openstack-swift12:12
*** JuanManuelOlle has joined #openstack-swift12:13
*** marcusvrn has joined #openstack-swift12:13
*** cheri has joined #openstack-swift12:16
Manish__Can anyone help me here?12:19
chandan_kumarManish__, please ask your question here.12:26
Manish__chandan_kumar: Hi...12:27
Manish__DO you know that who and when updates the "PUT_timestamp" column of "container_stat" table?12:27
*** mlipchuk has joined #openstack-swift12:28
portanteAnju, Manish__: if clayg does not answer when he gets in, i'll be looking at that in a bit12:30
*** Manish__ has quit IRC12:31
*** Manish_ has joined #openstack-swift12:33
Manish_chandankumar_: Sorry..i got disconnected12:33
Manish_did you go my query?12:33
cschwedeManish_: there are several places that trigger an update; for example object requests, container requests, background daemons (replicators/auditors)12:42
*** RockKuo has quit IRC12:43
cschwedeManish_: that said all updates should be called from swift/container/backend.py12:43
openstackgerritDonagh McCabe proposed a change to openstack/swift: Reclaim containers even if account db is reclaimed  https://review.openstack.org/8469612:44
Manish_i could find the scenarios where object_count, byte_used, hash columns are being updated...but couldn't find any scenarion when put_timestamp column is getting updated12:45
*** tanee-away is now known as tanee12:46
Manish_cschwede: ^^^^12:47
*** tanee is now known as tanee-away12:47
marcusvrnportante: ping12:50
*** nosnos has quit IRC12:50
cschwedeManish_: so normally this is only set on creation of the table. but then it might be overwritten by a replication process12:50
*** PradeepChandani has joined #openstack-swift12:51
*** tanee-away is now known as tanee12:51
cschwedeManish_: that will be the case if the rowids of two DBs differ by more than 50%, and in that case the whole DB file will be synced using rsync.12:52
*** tanee is now known as tanee-away12:52
cschwedeManish_: hmm, it might also get synced by the replicator without using rsync12:53
*** ppai has quit IRC12:53
*** tanee-away is now known as tanee12:54
*** psharma has quit IRC12:55
*** StevenK_ is now known as StevenK13:02
*** cheri has quit IRC13:05
marcusvrnCan anyone help me? I was trying to disable the object_server replication but keeping the others two working with replication (account_server and container_server). Is it possible?13:07
ctennissure, just stop the swift-object-replicator process13:11
*** changbl has quit IRC13:11
*** mmcardle has quit IRC13:13
marcusvrnbut is possible to disable it in some config file? Or I need to kill swift-object-replicator process each time that I rejoin stack?13:18
*** cheri has joined #openstack-swift13:18
*** chandankumar_ has quit IRC13:19
*** mmcardle has joined #openstack-swift13:40
cschwedeportante, acoles: just one more +2 needed: https://review.openstack.org/#/c/84456/13:46
gholtmarcusvrn: You can remove the [object-replicator] section from the object-server.conf config file.13:51
openstackgerritPeter Portante proposed a change to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445613:55
portantecschwede: sorry, I did not feel comfortable with adding the Intel licences since that code was only refactored into info.py and test_info.py13:55
portantebest left without copyrights until madhuri can weigh in13:56
*** pberis has quit IRC13:58
gholtHehe, I forgot that we at Rackspace should really edit all the files and plaster our copyright on most everything... joking, joking. You can't really "All Rights Reserved" either since it's explicitly unreserving rights with the Apache License.14:00
*** pberis has joined #openstack-swift14:04
*** pberis has quit IRC14:04
portantegholt: yeah, seriously, much of this code should be copyright Rackspace, because the foundation can't take copyrights14:04
*** pberis has joined #openstack-swift14:05
*** mkollaro has quit IRC14:05
*** mkollaro1 has joined #openstack-swift14:05
*** mkollaro1 is now known as mkollaro14:05
*** occupant has joined #openstack-swift14:07
gholtI don't think it was always that way. And honestly, I don't remember why they can't be granted the copyright either. It's actually fine if folks want to place their tags here and there. Credit where due. But it could make for some ugly source files over time. Hehe14:08
*** mlipchuk has quit IRC14:11
cschwedeportante: ok, makes sense to me14:11
*** cheri has quit IRC14:13
*** mlipchuk has joined #openstack-swift14:13
marcusvrngholt: nice!! thx14:16
*** piyush has joined #openstack-swift14:20
*** zackf has joined #openstack-swift14:23
*** bill_az has joined #openstack-swift14:25
*** pberis has quit IRC14:26
*** chandan_kumar has quit IRC14:27
*** chandan_kumar has joined #openstack-swift14:27
marcusvrnportante: I saw that the DiskFile and DatabaseBroker as a Public API blueprint had the priority change from medium to undefined...the diskfile API will be in the icehouse release? do you guys want to change it or sth?14:28
*** tanee is now known as tanee-away14:29
*** tanee-away is now known as tanee14:29
creihtyeah I wish they would just get rid of the copyrights at the tops of files14:29
*** chandan_kumar has quit IRC14:30
*** tanee is now known as tanee-away14:32
*** tanee-away is now known as tanee14:36
*** foexle has quit IRC14:39
*** mkollaro1 has joined #openstack-swift14:39
*** mkollaro has quit IRC14:39
notmynamegood morning14:45
creihthttp://saallergy.info/day/2014-04-0314:46
creiht:(14:46
acolescschwede: been away, will look at https://review.openstack.org/#/c/84456/ now14:46
creihtlol... that one patch has recieved more attention then any before :)14:47
*** pberis has joined #openstack-swift14:47
*** Manish_ has quit IRC14:51
*** tongli has joined #openstack-swift15:15
*** tanee is now known as tanee-away15:17
*** tanee-away is now known as tanee15:19
*** tanee is now known as tanee-away15:20
*** tanee-away is now known as tanee15:20
*** Midnightmyth has joined #openstack-swift15:21
*** mlipchuk has quit IRC15:22
*** jamie_h has quit IRC15:22
creihtportante: thanks for the added coverage for the -info patch15:24
*** mlipchuk has joined #openstack-swift15:25
*** jamie_h has joined #openstack-swift15:25
*** zhiyan is now known as zhiyan_15:25
*** MooingLemur has joined #openstack-swift15:29
*** mwstorer has joined #openstack-swift15:40
portantecreiht: welcome15:43
notmynamehear hear15:45
creihtnotmyname: anything else that needs to be reviewed before making the RC?15:48
notmynameyup. just finishing up my changelog line for describing dfg's cors changes. then I'll submit that to gerrit and would appreciate another set of eyes on it :-)15:49
portantenotmyname: sure15:50
creihtcool15:50
portanteany folks want to put some eyes on the in-process functional test stuff?15:50
creihtportante: I'll look at that after lunch15:50
portantethanks15:50
*** mlipchuk has quit IRC15:50
*** Anju5 has joined #openstack-swift15:52
cschwedeportante: you mean https://review.openstack.org/#/c/66108/ ?15:56
*** changbl has joined #openstack-swift15:59
portantecschwede: yes, and all its dependencies which make it easier to see the refactoring15:59
cschwedeportante: ah yes, so that are 5 patches. ok, will start with the top patch later16:01
portantethanks16:01
openstackgerritJohn Dickinson proposed a change to openstack/swift: updates for 1.13.1 release  https://review.openstack.org/8508816:04
*** ifadams has joined #openstack-swift16:04
notmynamecreiht: portante: cschwede: can you take a look at that please? ^^16:04
*** csd has joined #openstack-swift16:05
cschwedenotmyname: found a typo in first line in https://review.openstack.org/#/c/85088/1/CHANGELOG … just saying ;-)16:05
notmynamebah!16:06
openstackgerritJohn Dickinson proposed a change to openstack/swift: updates for 1.13.1 release  https://review.openstack.org/8508816:06
notmynamecschwede: there ;-)16:06
* notmyname goes to check other speling things16:06
notmynameah. one more. (in my defense, it's from portante's commit message)16:07
cschwedenotmyname: last line in https://review.openstack.org/#/c/85088/2/.mailmap - is that correct?16:07
cschwedenotmyname: VirtualBox mail address?16:08
notmynamecschwede: actually, yes it is (assuming it's the same person)16:08
openstackgerritJohn Dickinson proposed a change to openstack/swift: updates for 1.13.1 release  https://review.openstack.org/8508816:08
*** Anju5 has quit IRC16:08
notmynamecschwede: author email on https://review.openstack.org/#/c/78530/16:09
cschwedenotmyname: ah yes. well then… so i only had a very quick look, but i think patchset 3 looks good? sorry, I’m in a hurry, can have another look in two hours (if it is not merged then)16:11
notmynamecschwede: thanks16:11
notmynameacoles: done16:11
portanteship it16:11
openstackgerritJohn Dickinson proposed a change to openstack/swift: updates for 1.13.1 release  https://review.openstack.org/8508816:11
notmynameportante: cschwede: patch set 4 has the s/and/an/ from acoles16:12
*** jogo has left #openstack-swift16:12
notmynameportante: cschwede: acoles: thanks16:13
*** krtaylor has quit IRC16:13
portanteit'd be nice to get the info patch to land first16:13
notmyname2nd inthe gate queue now. it should16:14
portantegreat16:14
notmynameboth will be in 1.13.1. when they land, that will be the release16:14
portanteawesome16:14
notmynamethanks everyone16:14
portanteso then we can release 1.13.2 next week with the in-process functional test work. ;)16:15
portanteha!16:15
notmynamecontinual releases!16:15
notmyname(I actually kinda like that idea)16:15
portanteagreed16:15
*** csd has quit IRC16:20
*** csd has joined #openstack-swift16:21
*** csd has quit IRC16:22
*** fbo is now known as fbo_away16:26
*** mmcardle has quit IRC16:27
*** zaitcev has joined #openstack-swift16:29
*** ChanServ sets mode: +v zaitcev16:29
*** mmcardle has joined #openstack-swift16:29
*** tanee has quit IRC16:34
*** tanee has joined #openstack-swift16:36
*** nshaikh has quit IRC16:42
*** krtaylor has joined #openstack-swift16:50
*** mmcardle has quit IRC16:51
*** piyush has quit IRC16:57
acolesportante: you around?17:05
portanteyes17:05
portanteacoles:17:05
acoleshi. quick clarification on https://review.openstack.org/#/c/84877/3 ...17:06
portanteah yes, the fun one17:06
acolesre. functional tests using load_constraint() vs importing from constraints,17:07
portanteyes17:07
portantethat is the tricky one17:07
acolesso, right now the tests seem to use value is in swift.conf rather than whats in test.conf, by virtue of reload_constraints()17:08
acolesand this changes to preferring test.conf values over swift.conf, correct?17:09
portanteyes: so, first, this is trying to work in two different scenarios:17:09
portante1. an SAIO where the tree containing the functional tests is co-located with the deployment itself17:09
portante2. a tree containing the tests has no access to the /etc/swift directory of the installation (co-located or on another machine)17:10
portanteso if a test.conf has a setting, we need to honor that above access to a /etc/swift/swift.conf because of scenario #2, as I understand it17:11
portantefor scenario #1, we still honor it, but usually the /etc/swift/test.conf file in an SAIO does not have any constraints set because they can be picked up directly by the test environment17:11
portanteso when the test/functional/* code was referencing constraints directly, a setup using different constraints might end up with bad results17:12
portanteand that is actually still the case, as there are tests that assume certain sizes of objects will always be accepted17:12
acolesok. understand the two scenarios. the subtle change i observe is in scenario 1. that before, IF i had values 'non-standard' values set in swift.conf, the func test would pick them up, regardless of what is in test.conf. Now, the test will use what is in test.conf? because load_constraint prefers test.conf?17:15
portanteonly if the test.conf had that constraint set, yes17:16
acolesok. i'm not saying that is wrong. i just wanted to make sure i understood the subtle shift in precedence.17:17
portanteyes, now the behavior is consistent across the board, because some constraints before this change were using load_constraint and others were not17:18
acolesyeah. that is confusing :)17:18
portanteso all this is needed for the in-process tests so that constraint references are not bound at module import time, or referenced from the wrong environment17:19
acolesyes. i see the dependency chain :)17:20
portante;)17:21
acolesportante: i'll try to get review done before i leave. sorry i cannot contribute more to the cause today.17:21
portantethat is okay, thanks for the help17:21
*** tanee is now known as tanee-away17:22
*** judd7 has joined #openstack-swift17:23
torgomaticso call me stupid (which is probably true right now) but why not use the /info response for the functest constraints?17:29
torgomaticthat way you don't have to match what the proxy process does; you just ask it what it knows17:30
*** tdasilva has joined #openstack-swift17:38
portanteah, yes, we should do that17:42
portanteerr, I can make that happen17:42
portantetorgomatic ... stayin' sharp !17:43
torgomaticthat's probably all the utility you'll get out of me today :)17:45
*** mmcardle has joined #openstack-swift17:51
acolestorgomatic: portante: nice idea. there's a couple of constraints i don't see in info e.g. max_header_size17:51
*** mmcardle has quit IRC17:56
portantetorgomatic: all the best to you17:58
portanteacoles: I'll take a look at reconciling that17:58
*** mmcardle has joined #openstack-swift17:59
torgomaticportante: thanks :)18:01
*** Longgeek_ has joined #openstack-swift18:07
*** Longgeek_ has quit IRC18:12
*** ifadams has left #openstack-swift18:20
notmynamesnafus getting to work, but I'm back online now18:21
*** mmcardle has quit IRC18:23
*** pberis has quit IRC18:27
*** pberis has joined #openstack-swift18:28
creihttorgomatic: don't you have other things you need to be attending to? :)18:28
*** mwstorer has quit IRC18:29
notmynameso we're changing func tests to use /info to get constraints?18:29
portantecreiht: it is hard switching from baby sitting one group to another group, let it go, let it go, ...18:29
portantenotmyname: would like to18:29
notmynamethat sounds like a great idea18:30
portantenot in this patch series, since it will make it more complex18:30
notmynameand falling back to swift.conf defaults for constraints if /info doesn't respond?18:30
portanteor test.conf18:32
*** lpabon has joined #openstack-swift18:33
notmynameright. test.conf defaults just mirror swift.conf defaults though18:36
notmynametest.conf exists because functests can do remote testing and there used to be no way to discover the constraints on the system18:36
notmynamehysterical raisins, and all that18:36
*** jamie_h has quit IRC18:52
cschwedeportante: so i started reviewing https://review.openstack.org/#/c/84877/. what do you think about adding other default values as well to constraints?19:00
portantesec, will be available in a minute19:01
cschwedeportante: no hurry19:01
*** Midnightmyth has quit IRC19:03
notmynamecschwede: I think some of the other constraints would be good, but probably should be added in their respective namespaces. eg https://github.com/openstack/swift/blob/master/swift/common/middleware/slo.py#L78819:06
notmynamealso, it looks like dynamic large objects aren't in /info19:07
cschwedenotmyname: sorry, no i meant swift.common.constraints -> https://review.openstack.org/#/c/84877/319:08
cschwedenotmyname: but i agree we should add missing constraints to /info19:08
notmynamecschwede: yup, actually that's what I was responding to. at least for stuff like max_large_object_get_time19:09
portantecschwede: would you like to propose a patch?19:09
notmynamecschwede: also, IMO /info should only expose stuff that affects the client API. ie not auditing parameters19:10
cschwedeportante: for https://review.openstack.org/#/c/84877/3 or the /info thing?19:10
notmynamecschwede: unless those are in the /info "admin" request. then that's ok19:10
cschwedenotmyname: yep, makes sense19:10
notmynamecschwede: the question you left on line 47 in that patch19:10
cschwedeportante: notmyname: ok, i’ll propose a patch. should i put it in the existing from portante or a new one?19:11
portantedo a new one, if you could19:11
portantethat way it can move forward unemcombered by this work19:11
cschwedeportante: all right, let’s do it like this. I will start with the patch now, but upload it tomorrow morning - i want to avoid silly patchsets from my side because of my local time ;-)19:12
notmynameenemcombered? unem*brush*ed?19:12
*** lpabon has quit IRC19:14
zaitcevIn the traditional functests, is there a quick fix to make https work? Like an environment variable?19:19
notmynamezaitcev: it would be whatever returned as the storage url for the creds given, right?19:20
zaitcevnotmyname: yes, mine returns https19:20
notmynamezaitcev: what's breaking?19:20
zaitcev(cd test/functionalnosetests && nosetests test_container.py:TestContainer.test_cross_account_container)19:21
zaitcevsec, I'll paste for clarity19:21
zaitcevhttp://paste.openstack.org/show/75014/19:22
zaitcevthis used to work, but of course the client is new now, it needs "insecure" passed to new connections19:22
zaitcevwaaait a moment19:23
zaitcevI have a .pyc but no .py19:23
zaitcevthe whole test/functionalnosetests/ was removed19:24
notmynameyes19:24
notmynamewell, moved19:24
*** mmcardle has joined #openstack-swift19:24
openstackgerritA change was merged to openstack/swift: updates for 1.13.1 release  https://review.openstack.org/8508819:25
*** finite has joined #openstack-swift19:26
*** a_hacker_sboss has joined #openstack-swift19:27
*** finite has quit IRC19:27
*** a_hacker has joined #openstack-swift19:28
*** mmcardle has quit IRC19:28
*** fbo_away is now known as fbo19:29
zaitcevanyhow, http://paste.openstack.org/show/75017/19:30
zaitcevthe problem is   parsed[use_account], conn[use_account] = http_connection(url[use_account])19:30
zaitcevfor this server to work at all, http_connection() needs some insecure=True19:31
notmynameya. probably will need some patches (rather than just an env var)19:32
creihtugh19:33
creihtI'm really starting to dislike requests19:33
*** piyush has joined #openstack-swift19:33
zaitcevso... how do I set that, in a test? What's the preferred way? I could just hardcode it in test/functional/swift_testing.py, but that seems dumb.19:33
creihthttp://docs.python-requests.org/en/latest/user/advanced/#blocking-or-non-blocking19:33
creihtswift-bench uses python-swiftclient, and it looks like concurrent perf has really degraded19:34
notmynamecreiht: ugh19:34
creihtsince swift-bench is using eventlet19:34
creihtstill doing some testing, but I'm pretty sure that is the case19:35
notmynamecreiht: FYI, short term solution maybe? https://github.com/swiftstack/ssbench/blob/master/requirements.txt19:35
creihtlol19:36
creihtwell there is https://pypi.python.org/pypi/erequests19:36
creihtthough it doesn't support the same api :/19:37
*** a_hacker2 has joined #openstack-swift19:37
notmynamecreiht: I'm not suggesting that ssbench replace swift-bench, just a short term solution for whatever testing you're doing19:37
creihtahh19:38
creihtnah we are good19:38
notmynameso you can actually get stuff done today19:38
notmynameah, ok19:38
creihtit gave pandemicsyn an excuse to play with golang more :)19:38
notmynameie it's easier to write an ssbench scenario than it is to fix requests ;-)19:38
*** wasmum has joined #openstack-swift19:38
notmynamelol19:38
creihtjust going back now and trying to figre out why swift-bench is broken19:38
a_hacker2notmyname:  greetings, I'm trying to continue some troubleshooting you did with some of my collegues last night.  Do you have  minute to look at a pastebin?  I have an example of a container that just up and "disappears"19:38
a_hacker_sbosswe were troubleshooting the issue as a 404, but have now determined we are dealing with "disappearance"19:39
a_hacker_sbossswift is hard ;)19:40
a_hackerSo hard19:40
creihthow many a_hackers do we have on this ship?19:40
creiht:)19:40
a_hacker2YO!19:40
notmynamehe's multiplying!19:40
a_hacker_sbossthe great ship titanic ;))19:41
a_hacker2I knew it I'm surrounded by hackers19:41
*** Chet_McHacker has joined #openstack-swift19:41
notmynamea_hacker(*): so what's up?19:41
a_hacker2http://paste.openstack.org/show/y4iuUcytY9FFlEwfeUR2/19:41
a_hacker_sbosslol ;)19:41
a_hacker2appreciate your help notmyname19:42
portanteany other takers for reviewing "Rework use of constraints to ease testing"? https://review.openstack.org/8487719:43
portanteGot one +2 so far ... ;)19:43
cschwedeportante: you want to have an approve as well, right? ;-)19:44
portanteyes!19:44
glangeportante: I looked at that but I thought you were going to take the json stuff out?19:46
portantewell, acoles just approved it, so if others don't mind taking that in, i'll leave it as is19:46
portanteif other folks want that out, I'll take that out19:46
portantekinda like fishing19:46
glangeoh, ok19:46
glange:)19:47
portanteI got a fish on the hook19:47
portantejust not in the boat19:47
portanteso you can say that I am angling19:47
portante;)19:47
notmynamea_hacker: how many account servers do you have running?19:47
glangeportante: it looked good to me, but I probably agree with Zaitcev19:48
notmynamea_hacker: looks like just one?19:48
*** a_hacker_sboss has quit IRC19:48
portanteglange: okay, i'll pull that out19:48
portantethanks19:48
cschwedeportante: hmm, i think your patch is fine19:48
portantefight!19:48
glange merge it! :)19:48
portantecschwede: right now, it is 2 to 119:49
cschwedegot me!19:49
portante;)19:49
wasmumnotmyname account servers = 119:49
a_hacker2notmyname: 219:49
a_hacker22 workers19:49
Chet_McHacker2 workers19:49
cschwedeanother hacker!19:50
notmyname2 more19:50
Chet_McHacker:O19:50
*** wasmum has left #openstack-swift19:50
portanteso that means patch 84325 can be approved, too!19:50
*** zhiyan_ is now known as zhiyan19:50
* portante wonders where this patch bot went to ...19:50
portantepatchbot: patch 8432519:50
patchbotportante: https://review.openstack.org/#/c/84325/19:50
zaitcevMy logic was that as long as utils pretend to be like normal json then it should continue looking that way. If we had json.our_special_and_incompatible_json_loads(), then slapping utils on it would do no harm.19:50
portanteah there19:50
cschwedeportante: yep, just looking at it19:51
*** a_hackers_boss has joined #openstack-swift19:51
*** not_a_hacker has joined #openstack-swift19:52
*** not_a_hacker has left #openstack-swift19:52
*** a_not_hacker has joined #openstack-swift19:53
cschwedesince https://review.openstack.org/#/c/84332/ is already approved i will continue with https://review.openstack.org/#/c/84332/ tomorrow morning19:53
notmynamehow many people do we have here for this? who's actually working on it that I shoudl be talking to?19:53
notmynameno need for all of Seagate to be here on it (dig -x says a seagate IP block)19:53
portantenotmyname: any thing I can jump in on and help?19:54
portantemaybe match the number of seagate engineers? ;)19:54
notmyname:-)19:54
openstackgerritA change was merged to openstack/swift: Clean up swift-{account, container}-info  https://review.openstack.org/8445619:54
portanteyeah!19:54
portante1.13.1 is in the can19:55
cschwedei hear 1.13.1 coming :)19:55
notmynamea_hacker: can you add an "X-Newest: True" header to the listing request? I suspect it's likely that all replicas aren't getting updated19:55
notmynameportante: yay19:55
a_hacker2ypu19:56
a_hacker2yup19:56
openstackgerritPeter Portante proposed a change to openstack/swift: Handle getting info on wrong database type  https://review.openstack.org/8515619:56
*** mkollaro1 has quit IRC19:56
notmynamea_hacker2: and since the proxy (by default) chooses a replica at random, you are getting inconsistent results19:57
notmynameor eventaully consistent results ;-)19:57
portantenotmyname: above info patch, 85156 is a nicety, where if you user swift-container-info on an account .db file, by mistake, it won't give you a stack trace, but a simple message suggesting you might want to use another command19:58
portantein so many words, of course19:58
notmynamepatchbot: p 8515619:58
patchbotnotmyname: https://review.openstack.org/#/c/85156/19:58
portantejust did not want to hold up 1.13.1 to wait for it19:58
cschwedeportante: ah nice, was thinking the same this morning.19:58
portanteI actually did that testing the info patch!19:58
notmynameah, nice19:59
portantethat will make our customers want 1.13.2 all the more. :)19:59
portante1.13.1 is already passe19:59
portante;)20:00
portantetrunk chasers unite!20:00
cschwedeyou know how to keep the demand for new releases up ;)20:00
portante:)20:01
*** mkollaro has joined #openstack-swift20:01
notmynamenow to finish the traditional post-facto launchpad updates...20:01
portantekewl20:02
notmynameok, https://launchpad.net/swift/+milestone/1.13.1-rc1 shouldn't be as horribly out of date as it was20:02
a_hacker2notmyname: http://paste.openstack.org/show/fqzfD5YyzDWWNXookJce/20:02
notmynamea_hacker2: I'm trying to work though some edge cases in my mind. I'm not used to thinking about what happens with only one server in the system20:04
a_hacker2we went down to one server for troubleshooting - it has been happening on a 8 storage node cluster20:04
notmynamea_hacker2: should still be fine since there are 3 replicas and more than 3 drives20:05
notmynamea_hacker2: what version of swift are you using?20:05
a_hacker2it's a havana release:  >>> swift.__canonical_version__ '1.10.0'20:06
notmynameok20:06
notmynamea_hacker2: at this point, I'd use swift-get-nodes to find the replicas and look at them on disk. (the swift-account-info tool that just landed would be nice for this)20:09
a_hacker2notmyname:  yep, did that. the container sqlite files are missing20:09
creihta_hacker2: have you verified that you have the same ring on all of the machines?20:10
a_hacker2creiht:  yes - even to the point where we are down to only one storage node20:11
a_hacker2creiht: the current 1 node ring is here: http://paste.openstack.org/show/y4iuUcytY9FFlEwfeUR2/20:12
creihta_hacker: I would search the logs by greping for that container url20:13
creihtand see if any other requests are deleting it20:13
creihtit is odd that 1.) your container count in the account goes back to 020:14
a_hacker2creiht:  yes sir, did that as well.  we see the puts and heads, but no entries for deletes20:14
creihtand the timestamp is updated20:14
creihtso something is specifically removing it20:14
creihtor it seems that is the case20:14
a_hacker2right - and we have no expirers running20:14
creihta_hacker2: sorry, I'm coming up blank at the moment, and my allergies are not helping much either20:18
creihtI'll keep thinking on it though20:18
a_hacker2creigt: NP - thanks for your help20:18
creihta_hacker2: if you HEAD the account several times do they all show without the container?  or do does it go in and out?20:19
*** piyush has quit IRC20:20
*** mmcardle has joined #openstack-swift20:22
*** piyush has joined #openstack-swift20:24
a_hackercreiht: did the actions quickly, got a 204 then 404 http://paste.openstack.org/show/d2TTGrmwD4Pa1enyVt4M/20:26
*** mmcardle has quit IRC20:26
a_hacker2creiht:  I shut down all services except container-server,object-server,account-server on the storage node and am still seeing the behaviror:  http://paste.openstack.org/show/3nMXCFsFNgNUO1WxMFlM/20:27
a_hacker2behavior20:27
*** shri has joined #openstack-swift20:28
notmynamea_hacker2: and does it come back after doing another stat?20:29
creihta_hacker2: it sounds like either your accounts or containers are out of sync20:30
notmynameno, that's not important. I think you already answered that20:30
creihtor both :)20:30
creihtand you have recheck_container_existence and recheck_account_existence set to 020:31
*** Midnightmyth has joined #openstack-swift20:31
creihtso it is always going to go to the account/container server to check for existence20:31
creihta_hacker2: I would like you to create a container, get the txid returned from that create, and pull all the logs with the txid and paste the results20:32
a_not_hackercreiht: yes set to 0 on both20:33
creihtmy guess is that one of the container creates is failing, and not replicated yet20:33
creihtdoing a head of a container or account is going to pull 1 of the 3 replicas at random20:34
creihtso sometimes you get the one that is there and sometimes you don't20:34
creihtjust my guess, but if you can get those logs, it should help determine if that is the case20:34
a_not_hackercreiht: theory, sqlite db issue?  the object is created in the db and reported back successful but fails to write to disk?  can you think of a way to prove/disprove that?20:35
*** piyush has quit IRC20:35
creihta_not_hacker: it will be in the logs20:36
*** piyush has joined #openstack-swift20:36
creihtand since you are reproducing it on one node, my best guess is a permissions issue on one of the device locations20:37
creihtbut the logs should show is the way20:37
a_hacker2creiht:  http://paste.openstack.org/show/c3oEgUWo8Nyo2W4Qms7C/20:37
creihta_hacker2: that's only showing the logs for the proxy-sever, do you have all logs going to /var/log/messages?20:39
creihtI would like you to grep all the logs of all the services for that txid20:39
notmynameportante: FYI https://github.com/notmyname/Patches20:40
a_hacker2we have everything logging to /var/log/messages20:40
creihta_hacker2: is sprswiftstor02 the only storage server that you are using?20:41
a_hacker2creiht: correct20:41
creihta_hacker2: and the container services are on that box as well?20:43
torgomaticcreiht: indeed, which is why I'm only poking my head in here during PBS children's programming :)20:43
creihttorgomatic: haha20:43
torgomaticif I can't see an idea through to its conclusion within one episode of Peg + Cat, it doesn't happen ;)20:43
a_hacker2creiht: yes20:45
creihta_hacker2: well if that were the case, then there would be logs with that txid there20:46
creihta_hacker2: is that server 10.17.9.11?20:47
a_hacker2right - dunno why there are not any entries20:48
openstackgerritA change was merged to openstack/swift: Rework use of constraints to ease testing  https://review.openstack.org/8487720:48
a_hacker2creiht: should be .1220:48
creihthttp://paste.openstack.org/show/d2TTGrmwD4Pa1enyVt4M/20:48
creihtthat past was showing your locations on .1120:48
creihtpost20:49
creihtpaste20:49
creihtheh20:49
notmynamethe ring builder output had .11 too20:49
a_hacker2crap - sorry - looking20:49
*** a_hackers_boss has quit IRC20:51
*** ryanbondseagate has joined #openstack-swift20:52
openstackgerritA change was merged to openstack/swift: Only change collation for functional tests  https://review.openstack.org/8432520:53
ryanbondseagateswift is hard ;)20:53
*** ryanbondseagate has quit IRC20:53
creihtlol20:57
* creiht guesses that a_hackers_boss == ryanbondseagate?20:58
a_hacker2strike 120:58
a_hacker2close tho :)20:58
notmynamemaybe wasmum20:58
creihtlol20:58
notmynameor not_a_hacker20:58
notmynameor a_hacker (the first)20:58
*** JuanManuelOlle has quit IRC20:59
*** an_embaressed_ha has joined #openstack-swift20:59
notmynamelook! another seagate IP!20:59
creihtlol20:59
creihtthere are much easier ways to use irc than the web gateway :)21:00
notmynameunless your company blocks all ports but 80 and 44321:01
notmyname;-)21:01
creihtheh21:01
a_hacker2creiht:  http://paste.openstack.org/show/0NONxlD5j25T0ErKgvgL/     ring fixed, same behavior21:02
creihtso you you run an irc bouncer on port 80? :)21:02
a_not_hackerthanks for "bouncing" that by us...21:02
portantenotmyname: thanks!21:04
creihta_not_hacker: ok so according to that all swift containers were put correctly21:04
* portante ... regarding Patches21:04
creihta_not_hacker: so if you head that container do you get any 404s?21:05
notmynameportante: I was guessing you might want to add other features or personalities to it :-)21:05
portantenice, thanks!21:06
notmynameportante: my requirements we "linkify numbers that portante puts into irc, and don't spend more than an hour on it". so I'm not really planning on adding too much more :-)21:06
a_hacker2yep - 404's21:06
portantecute, 00721:06
notmynameportante: but I'll be happy to restart it with new code if there's something added21:07
portantethanks!21:07
creihta_hacker2: ok then it sounds like the account isn't getting auto created correctly21:08
creihtif it can't find the account, it will 40421:08
notmynameportante: did you play with logflow any more?21:08
creihtif you do a swift-get-nodes for that account21:08
creihtand then run the ssh commands for each, can you find all of the dbs?21:08
portantenot yet, but when I pop my stack to that, which is any day now, yes, I'll be doing that to help debug this problem21:09
notmyname:-)21:09
creihta_hacker_* -^21:09
notmynameya, I was thinking it would be helpful, assuming the ideas we both have for it were actually written ;-)21:09
a_hacker2creiht: ok - that seems familiar... but "allow_account_management = true account_autocreate = true" are in the proxy-server.conf21:09
creihta_hacker2: right, but something seems like it isn't getting created correctly21:10
a_hacker2looking for the db files 1sec21:10
creihtthat's why we are checking21:10
*** piyush1 has joined #openstack-swift21:10
*** piyush has quit IRC21:10
a_hacker2creiht:  no dbfiles found21:12
*** piyush has joined #openstack-swift21:12
creihta_hacker2: ok, then the next step is finding the requests to create those accounts21:12
creihtin the logs21:12
creihtand finding out why they are erroring21:12
creihtsince it is all on one sever, just tail the logs while you make the request, and see what they look like21:13
*** judd7_ has joined #openstack-swift21:14
*** judd7 has quit IRC21:14
*** piyush1 has quit IRC21:14
a_hacker2creiht:  ok, so I see puts and heads for the container (more than expected actually), but no deletes21:15
a_hacker2looking for the account now21:15
creihta_hacker2: or if you can paste the whole log for what happens for that one request21:16
a_hacker2creiht: http://paste.openstack.org/show/o6lAsXTz24Bg00qzzeHy/21:20
a_hacker2not sure i got what was needed21:20
notmynamea_hacker2: no, please grep for the transaction id and don't filter it. or even just every log line while you do the account listing and container put21:22
a_hacker2ok21:22
creihta_hacker2: yeah, I would like for you to start a tail, run the request, and then copy/paste everything that gets logged for that single request21:23
*** mmcardle has joined #openstack-swift21:24
a_hacker2creiht: http://paste.openstack.org/show/E9J1Ne9mOPDIdFGZjzCo/21:25
*** mmcardle has quit IRC21:28
creihta_hacker2: so the handoff requested seems to indicate an issue, but I don't have enough context in the los to determine the exact issue21:37
creihtso what would be preferable on bother servers is21:38
creihttail /var/log/messages21:38
creihthit enter a couple of times to give you some space so you know what is logged for the request21:38
creihtmake the request21:39
creihtthen copy everything after the blank lines to a paste21:39
creihtso we can see what is going on21:39
a_hacker2ok21:43
*** an_embaressed_ha has quit IRC21:44
a_hacker2creiht:  are you going to be on tomorrow?  something has changed and I can't do a post at the moment21:45
creihta_hacker2: possibly :)21:45
creihtmost of us can help21:45
creihtso feel free to try again tomorrow21:45
a_hacker2THANK YOU21:45
*** Chet_McHacker has quit IRC21:46
*** mwstorer has joined #openstack-swift21:46
*** a_not_hacker has quit IRC21:48
*** fbo is now known as fbo_away21:48
notmynamecreiht: thanks for jumping in21:49
creihtmy bet is still bad permissions :)21:49
creihtand np21:49
notmynamecreiht: did you see my log flow thingy?21:49
creihtnotmyname: I remember you posting something about it, but never looked at it21:50
*** a_hacker2 has quit IRC21:50
notmynamecreiht: http://d.not.mn/log_flow.png21:50
notmynamecreiht: given a set of swift log lines, it makes that21:50
notmynamecreiht: actually, this one http://d.not.mn/log_flow2.png21:51
notmynamethe first was/is an experiment to track servers. we don't have a good way to track PIDs right now21:51
creihtinteresting21:52
*** Midnightmyth has quit IRC21:52
notmynamemy original goal was to make some pictures for training/meetups/conferences21:52
creihtI would like a graph like what the html inspectors do with browsers21:52
creihtwhere they show a timeline and all the requests going through21:52
creihtwith flow21:52
notmynameand a pony?21:53
notmyname:-)21:53
notmynameya, that would be really cool21:53
*** a_hacker has quit IRC21:53
creihtI already have a pony :)21:53
notmynameprinted it last night in your garage?21:53
openstackgerritClay Gerrard proposed a change to openstack/swift: Keep status_changed_at up-to-date with status changes.  https://review.openstack.org/8518621:53
creihtwell a pony car :)21:53
openstackgerritClay Gerrard proposed a change to openstack/swift: Merge container storage_policy_index values.  https://review.openstack.org/8394221:53
notmynamelol21:53
creihtnotmyname: and I still need a garage :/21:53
clayglet's see how bad I confused gerrit here...21:54
anticwnotmyname: got a reference to the upcoming colorado (longmont?) swift event?21:55
creihtanticw: heh I should have sent the seagate hackers to you :)21:55
notmynameanticw: https://www.eventbrite.com/e/openstack-swift-june-hackathon-tickets-830956914521:55
anticwcreiht: which ones?21:56
notmynamecreiht: what do you mean? anticw == a_hacker21:56
anticwsorry, i'm not reading scrollback21:56
creihtoh21:56
creihtlol21:56
creihtwell it got kinda confusing for a while21:56
creihta_hacker221:56
notmynameanticw: yesterday and today there were about 4 seagate people all called a_hacker in here asking about container issues21:56
creihtand a_hackerboss21:56
anticwwhich office were they from?21:58
notmynameOKC I think21:59
notmynameanticw: one was http://www.linkedin.com/in/drbond7421:59
anticwdon't know who they are, but interesting all the same22:00
notmynameanticw: sprswiftprox01.stni.seagate.com22:00
claygnotmyname: has patchbot always been in here?22:02
notmynameclayg: no. I just wrote it on sunday22:03
claygneato!22:03
*** tdasilva has quit IRC22:03
notmynameit's stupid simple. an obvious improvement would be to have it detect patch numbers and automatically linkify them rather than only being questioned about it22:04
notmynamepatchbot: path foobarbaz22:04
patchbotnotmyname: Error: "path" is not a valid command.22:04
notmynamepatchbot: patch foobarbaz22:04
patchbotnotmyname: Error: 'foobarbaz' is not a valid integer.22:04
notmynameoh! I did add that check22:04
creihtpatchbot: ☃22:05
patchbotcreiht: Error: "☃" is not a valid command.22:05
notmynamepatchbot: list22:05
patchbotnotmyname: Patches22:05
notmynamepatchbot: list Patches22:05
patchbotnotmyname: p, patch, and testpatch22:05
creihtpatchbot: patch ☃22:05
patchbotcreiht: Error: '\xe2\x98\x83' is not a valid integer.22:05
creihthehe22:05
creihtpatchbot: patch 66622:06
patchbotcreiht: https://review.openstack.org/#/c/666/22:06
gholtDo you guys see this a lot now? https://gist.github.com/gholt/c81f4e8c638bb22e951022:06
gholtThe container sync part doesn't matter. I've seen it with other processes too. Like something changed in the logging stuff in Swift.22:06
*** piyush has quit IRC22:06
gholtJust at exit, of course. Not a big deal, but kinda annoying22:06
notmynameproxy-logging did just change22:07
*** zackf has quit IRC22:07
notmynamegholt: https://github.com/openstack/swift/commit/31b994560332ffa22fbe45e43471db360467434c22:08
gholtProbably just throw a try except KeyError around that close I guess, just seems curious22:08
*** zhiyan is now known as zhiyan_22:08
claygi think i saw that on the weakref change for the python 2.6 logging - and then didn't see it again cause i mostly use py2.722:15
*** krtaylor has quit IRC22:22
*** tdasilva has joined #openstack-swift22:22
*** changbl has quit IRC22:23
openstackgerritClay Gerrard proposed a change to openstack/swift: Merge container storage_policy_index values.  https://review.openstack.org/8394222:24
*** mmcardle has joined #openstack-swift22:24
claygthat's a little better, still think i can clean it up a bit more - but for now i'm headin' out with Will for baseball practice.22:25
*** chuck_ has joined #openstack-swift22:27
*** mmcardle has quit IRC22:28
*** mkollaro has quit IRC22:30
* MooingLemur chuckles at the fact that timestamps are lexically sorted, and if Swift is still a thing in the year 2286, they'll start to have some interesting problems. :)22:35
*** dmsimard has quit IRC22:47
*** marcusvrn has quit IRC22:48
zaitcevportante: I ran normal functests in your tree 66108 (set no environment, and had /etc/swift/func_test.conf) and it immediately skips. I'm trying to find out what's wrong. A stock tree works fine.22:59
anticwpatchbot: system rm -rf /*23:00
patchbotanticw: Error: "system" is not a valid command.23:00
* anticw trolls23:00
*** bvandenh has quit IRC23:00
piousboxhello23:03
piousboxwhat is the Content-Type of an empty response?23:04
piousboxSwift API says that Content-Type is required, but the response on success is empty.23:04
*** matsuhashi has joined #openstack-swift23:05
*** Trixboxer has quit IRC23:06
anticwpiousbox: for an object GET?23:08
piousboxcontainer PUT23:08
piousbox"/v1/account/container -X PUT"23:09
piousboxon success it returns nothing, but content-type header is required.23:09
piousboxLooking at the API: http://docs.openstack.org/api/openstack-object-storage/1.0/content/PUT_createContainer_v1__account___container__storage_container_services.html#PUT_createContainer_v1__account___container__storage_container_services-Response23:09
openstackgerritgholt proposed a change to openstack/swift: Fixed error in container sync exc handling  https://review.openstack.org/8519723:10
notmynameanticw: thanks23:13
gholtnotmyname: That patch I just made isn't an rc-breaking thing. Been that way a while I suspect and just messes with error reporting, not causing an error in and of itself.23:16
gholt[Rackspace is getting ever closer to container sync as a feature... just taking us a while.]23:17
notmynamethanks23:17
*** judd7_ has quit IRC23:24
*** mmcardle has joined #openstack-swift23:26
*** tongli has quit IRC23:26
*** mmcardle has quit IRC23:30
portantezaitcen, shouldn't that be /etc/swift/test.conf?23:32
portantezaitcev23:32
zaitcevportante: it works in normail tree...23:32
portantereally?23:32
portanteI did not change get_config() though, so I wonder what the difference is ...23:32
notmynamepiousbox: I don't see a content-type header being required https://gist.github.com/notmyname/f13a3a87ffcc354e25c423:33
notmynamepiousbox: it would appear that the doc page you linked is incorrect23:34
piousboxnotmyname: thanks. I'll write either nothing or text/plain then.23:34
notmynamepiousbox: well, hang on. that page is weird. what are you looking at? the response?23:35
notmynamepiousbox: you (as the client) don't control what's in the response (which means it's kinda weird to say a header is "required")23:35
notmynamepiousbox: now it turns out that swift will automatically try to detect the content type for any object PUT request that doesn't include a content-type header23:37
notmynamepiousbox: so all data stored in swift will have a content-type set on it (it falls back to "application-octet/stream" IIRC23:37
zaitcevportante: http://paste.openstack.org/show/75041/23:38
zaitcevportante: I sent you other particulars on the internal IRC23:38
piousboxnotmyname: we're writing a thing that's supposed to be compatible with Swift, so I'm actually a server, not a client.23:39
* notmyname has strong opinions on that23:39
piousboxnotmyname: application-octet/stream makes sense.23:40
portantezaitcev: okay23:42
notmynamepiousbox: why are you not using swift's existing extension mechanics? I'm curious about your use case23:43
swifterdarrellpiousbox: that should be super-easy, because the server side of Swift is already written and used in production in many deployments!23:46
piousboxnotmyname: some coworkers said here that Swift's extension mechanics would tie us to technology choices that we may not be comfortable with23:54
piousboxnotmyname: I'm not making these decisions man23:54
notmynamepiousbox: that's quite a vague answer :-)23:55
piousboxnotmyname: I'll be able to answer your question later on, ok?23:56
piousboxI'm just writing a piece in node.js to have data passed back and forth from HTTP to some C functions.23:57
zaitcevIt's not even important. There's a lot of silly stuff going on. Remember that Ceph ships their own Swift implementation written in C++ as a part of RGW.23:57
notmynamezaitcev: ya, but that's the wrong way to do it :-)23:57
zaitcevAnd BTW Ceph's efforts to do the right thing are not going too well23:57
notmynamezaitcev: the ceph diskfile? that's enovance, not inktank IIRC23:58
zaitcevOh really?23:58
zaitcevI thought that Chinese dude worked for Dreamhost23:58
notmynameBabu Shanmugam<anbu@enovance.com> on https://review.openstack.org/#/c/60215/23:59
zaitcevI'm confused23:59
zaitcevBut that looks familiar.23:59

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