Wednesday, 2014-07-02

mattoliveraunotmyname: The LCA call for papers closes reletively soon, You submitted yours? (I work with the chair's of the paper commitee, and he keeps reminding the team, so why not pass on the love) :P Besides what's an LCA without a talk from notmyname :)00:16
notmynameheh00:23
notmynamenot yet, but it's on my radar00:23
notmynameI gotta talk to the boss man about it. LCA is not quite the same as a conference in denter/portland/atlanta00:24
notmynamealso *denver00:25
mattoliveraulol00:25
*** dmorita has joined #openstack-swift00:26
mattoliveraunotmyname: yeah understandable, let me know if you can make it, if not, I'll submit a proposal to talk SP etc, so we can keep  swift as a continuing trending topic ;) .. but coming from me wont be the same as coming from the PTL :)00:28
notmynamemattoliverau: I believe that peluse_ is going to be submitting a patch00:28
mattoliveraupeluse_: awesome, I'll leave it in his capible hands then :)00:29
mattoliveraunotmyname i mean ^^00:29
*** patchbot has quit IRC00:36
*** patchbot has joined #openstack-swift00:38
*** patchbot has quit IRC00:38
peluse_mattoliverau:  yup, I'll be submitting a proposal or 2 for LCA.  Policies is of course really big, Erasure Coding is coming and that can be sliced and diced a bunch of different ways... something for sure though!00:41
mattoliveraupeluse_: awesome! It'll be good to have you down this way!00:46
*** shri has quit IRC00:56
*** patchbot has joined #openstack-swift01:01
notmynametorgomatic: suppose we wanted to talk about patch 103731. It would be nice if we had an automatic link to it01:02
patchbotnotmyname: https://review.openstack.org/#/c/103731/01:02
claygand what about patch 99999901:06
patchbotclayg: https://review.openstack.org/#/c/999999/01:06
claygoic01:06
claygeven 88888801:07
claygquite nice :)01:07
claygpatches are great 77777701:07
clayghrmmm...01:07
patchbotclayg: You've given me 5 invalid commands within the last minute; I'm now ignoring you for 10 minutes.01:07
notmynameclayg: but if you talke about patch xyzzy, nothing happens01:07
notmynamelol01:07
claygnow that is a FEATURE!01:07
notmynamehmm,, but why was it triggered?01:08
notmynameanother line?01:08
notmynameignore me too!01:08
claygi guess he thinks I'm still talking to him?01:08
claygpatchbot: are you *really* ignoring me?!01:08
claygawwww :'(01:08
notmynameINFO 2014-07-02T01:12:27 Ignoring01:09
notmyname     *!~clayg@ec2-54-235-44-253.compute-1.amazonaws.com for 600 seconds due to01:09
notmyname     an apparent invalid command flood.01:09
notmynamebut why did it think you did commands?01:09
notmynameis it the numbers, lke 2342342401:09
notmynameand 234501:10
notmynameand 78901:10
notmynameand 123301:10
notmynamenopw01:10
notmynamenope01:10
notmynamepatchbot doesn't like clayg01:10
*** mitz_ has joined #openstack-swift01:11
claygi got skillz01:11
notmynamehaxor skillz01:11
zaitcevnice01:11
notmynametoday's IRC flood comes to you courtesy of playing with new toys01:12
clayglolwut "In the endeavor to move from the default deployment of Keystone being eventlet (in devstack) to Apache + mod_wsgi"01:19
zaitcevI don't remember where it comes from but Certain People were plugging at it for a while, with a preservance and dilligence that deserved a better application.01:21
claygno, i may be wrong on both counts, mod_python seems to have gotten a new maintainer as well01:21
*** kota_ has joined #openstack-swift01:36
*** ho has joined #openstack-swift01:43
*** zaitcev has quit IRC01:46
*** nosnos has joined #openstack-swift01:49
*** nosnos has quit IRC01:55
*** nosnos has joined #openstack-swift01:55
*** nsquare has quit IRC01:59
*** nsquare has joined #openstack-swift02:00
*** zaitcev has joined #openstack-swift02:03
*** ChanServ sets mode: +v zaitcev02:03
*** acoles has quit IRC02:13
*** nsquare has quit IRC02:17
*** zhiyan_ is now known as zhiyan02:22
*** acoles has joined #openstack-swift02:22
*** ChanServ sets mode: +v acoles02:22
*** zaitcev has quit IRC02:25
*** zhiyan is now known as zhiyan_02:30
*** zhiyan_ is now known as zhiyan02:42
*** nsquare has joined #openstack-swift02:48
*** ajc_ has joined #openstack-swift02:50
*** theannegentle has joined #openstack-swift03:03
*** theannegentle has quit IRC03:04
*** gyee has quit IRC03:10
*** zhiyan is now known as zhiyan_03:22
*** zhiyan_ is now known as zhiyan03:24
*** nosnos has quit IRC03:27
*** zhiyan has quit IRC03:30
*** zhiyan has joined #openstack-swift03:37
*** zhiyan is now known as zhiyan_03:39
*** zhiyan_ is now known as zhiyan03:40
*** zhiyan is now known as zhiyan_03:46
*** zhiyan_ is now known as zhiyan03:50
*** ky has joined #openstack-swift04:01
*** km has joined #openstack-swift04:01
*** km is now known as Guest4094004:02
*** tong_ has joined #openstack-swift04:02
*** ktsuyuzaki has joined #openstack-swift04:03
*** tongli has quit IRC04:03
*** kota_ has quit IRC04:05
*** kota_ has joined #openstack-swift04:05
*** ktsuyuzaki has quit IRC04:07
*** ktsuyuzaki has joined #openstack-swift04:08
*** kota_ has quit IRC04:10
*** kota_ has joined #openstack-swift04:10
*** ktsuyuzaki has quit IRC04:12
*** ho has quit IRC04:13
*** ktsuyuzaki has joined #openstack-swift04:13
anticw1234504:14
*** kota_ has quit IRC04:15
*** kota_ has joined #openstack-swift04:17
*** ktsuyuzaki has quit IRC04:20
*** ktsuyuzaki has joined #openstack-swift04:20
*** kota_ has quit IRC04:22
*** kota_ has joined #openstack-swift04:23
*** ktsuyuzaki has quit IRC04:24
*** ktsuyuzaki has joined #openstack-swift04:25
*** kota_ has quit IRC04:27
*** ktsuyuza_ has joined #openstack-swift04:28
*** ktsuyuzaki has quit IRC04:30
*** kota_ has joined #openstack-swift04:30
*** ktsuyuza_ has quit IRC04:32
*** ktsuyuzaki has joined #openstack-swift04:33
*** tong_ has quit IRC04:33
*** kota_ has quit IRC04:35
*** kota_ has joined #openstack-swift04:37
*** ktsuyuzaki has quit IRC04:39
*** ktsuyuzaki has joined #openstack-swift04:40
*** nosnos has joined #openstack-swift04:42
*** kota_ has quit IRC04:42
*** kota_ has joined #openstack-swift04:42
*** ktsuyuzaki has quit IRC04:44
*** ktsuyuzaki has joined #openstack-swift04:45
*** kota_ has quit IRC04:47
*** kota_ has joined #openstack-swift04:47
*** ktsuyuzaki has quit IRC04:49
*** ktsuyuzaki has joined #openstack-swift04:50
*** kota_ has quit IRC04:52
*** ppai has joined #openstack-swift04:52
*** kota_ has joined #openstack-swift04:52
*** psharma has joined #openstack-swift04:53
*** ktsuyuzaki has quit IRC04:54
*** ktsuyuzaki has joined #openstack-swift04:57
*** kota_ has quit IRC04:59
*** kota_ has joined #openstack-swift05:01
*** ktsuyuzaki has quit IRC05:03
*** ktsuyuzaki has joined #openstack-swift05:06
*** kota_ has quit IRC05:08
*** kota_ has joined #openstack-swift05:08
*** Midnightmyth has joined #openstack-swift05:10
*** ktsuyuzaki has quit IRC05:10
*** ktsuyuzaki has joined #openstack-swift05:13
*** mmcardle has joined #openstack-swift05:14
*** kota_ has quit IRC05:15
*** kota_ has joined #openstack-swift05:16
*** ktsuyuzaki has quit IRC05:18
*** ktsuyuzaki has joined #openstack-swift05:18
*** kota_ has quit IRC05:20
*** kota_ has joined #openstack-swift05:21
*** ktsuyuzaki has quit IRC05:23
*** ktsuyuzaki has joined #openstack-swift05:23
*** kota_ has quit IRC05:25
*** kota_ has joined #openstack-swift05:26
*** swat30 has quit IRC05:26
*** zul has quit IRC05:27
*** swat30 has joined #openstack-swift05:27
*** ktsuyuzaki has quit IRC05:27
*** zul has joined #openstack-swift05:28
*** ktsuyuzaki has joined #openstack-swift05:30
*** kota_ has quit IRC05:32
*** kota_ has joined #openstack-swift05:33
*** ktsuyuzaki has quit IRC05:35
*** ktsuyuza_ has joined #openstack-swift05:35
*** chandan_kumar has joined #openstack-swift05:38
*** kota_ has quit IRC05:38
*** ktsuyuzaki has joined #openstack-swift05:38
*** ktsuyuza_ has quit IRC05:40
*** bkopilov_ has quit IRC05:44
*** bkopilov has joined #openstack-swift05:44
*** kota_ has joined #openstack-swift05:44
*** ktsuyuzaki has quit IRC05:47
*** ktsuyuzaki has joined #openstack-swift05:47
*** kota_ has quit IRC05:49
*** kota_ has joined #openstack-swift05:51
*** ktsuyuzaki has quit IRC05:53
*** ktsuyuzaki has joined #openstack-swift05:54
*** kota_ has quit IRC05:56
*** ktsuyuzaki has quit IRC06:17
*** kota_ has joined #openstack-swift06:17
*** Midnightmyth has quit IRC06:30
*** ky has quit IRC06:39
*** mitz_ has quit IRC06:48
*** mitz_ has joined #openstack-swift06:50
*** nsquare has quit IRC06:51
*** yuan has quit IRC07:00
*** yuan has joined #openstack-swift07:00
*** yuan has quit IRC07:00
*** yuan has joined #openstack-swift07:00
*** foexle has joined #openstack-swift07:04
*** jamiehannaford has joined #openstack-swift07:04
*** foexle has quit IRC07:20
openstackgerritMatthew Oliver proposed a change to openstack/swift: Add X-Delete-At/After support to FormPost  https://review.openstack.org/10410107:28
openstackgerritMatthew Oliver proposed a change to openstack/swift: Add X-Delete-At/After support to FormPost  https://review.openstack.org/10410107:32
mattoliverauOn that note, time to go make dinner :)07:34
*** mkerrin has joined #openstack-swift07:45
*** mmcardle has joined #openstack-swift07:52
*** mmcardle has quit IRC08:02
*** nacim has joined #openstack-swift08:02
*** mmcardle has joined #openstack-swift08:07
*** foexle has joined #openstack-swift08:07
*** mkollaro has joined #openstack-swift08:14
*** fifieldt_ has joined #openstack-swift08:16
*** fifieldt has quit IRC08:18
*** andyandy has joined #openstack-swift08:21
*** dANOKELOFF has joined #openstack-swift08:22
dANOKELOFFHi , in swift with curl how we can destroy a non-empty containers ?08:25
omameyou can't08:25
omameyou need to delete all the objects first, then you can delete the container08:26
dANOKELOFFomame: oh... ok , and curl command exist for delete all objects?08:26
dANOKELOFFomame: or i need to delete object one-by-one08:26
omamethe latter08:27
omameor use swiftly08:27
omamecheck out the --recursive flag at http://greg.brim.net/swiftly/2.04/#swiftly-help-delete08:27
dANOKELOFFomame: ok , thank's08:29
*** fifieldt_ is now known as fifieldt08:31
*** mkollaro has quit IRC08:35
*** jamiehannaford has quit IRC08:44
*** jamiehannaford has joined #openstack-swift08:44
*** bvandenh has joined #openstack-swift08:48
*** jamiehannaford has quit IRC08:52
*** Guest40940 has quit IRC08:55
*** jamiehannaford has joined #openstack-swift08:56
*** dmorita has quit IRC09:11
*** mkollaro has joined #openstack-swift09:19
*** gvernik has joined #openstack-swift09:22
*** kota_ has quit IRC09:23
*** ujjain has quit IRC09:42
*** gvernik has quit IRC09:44
*** nacim has quit IRC09:48
*** dANOKELOFF has quit IRC09:55
*** nacim has joined #openstack-swift09:58
*** ppai has quit IRC10:04
*** ppai has joined #openstack-swift10:20
*** mmcardle has quit IRC10:22
*** ujjain has joined #openstack-swift10:23
*** ujjain has quit IRC10:24
*** ujjain has joined #openstack-swift10:24
*** mmcardle has joined #openstack-swift10:26
*** ppai has quit IRC10:46
*** TaiSHi has joined #openstack-swift10:50
*** mkollaro has quit IRC11:05
*** lsell has left #openstack-swift11:18
*** Midnightmyth has joined #openstack-swift11:33
*** ppai has joined #openstack-swift11:39
*** mkollaro has joined #openstack-swift11:46
*** mmcardle has quit IRC11:55
*** ajc_ has quit IRC11:58
*** nosnos has quit IRC11:59
*** nosnos has joined #openstack-swift11:59
*** ppai has quit IRC12:02
*** nosnos has quit IRC12:04
*** Midnightmyth has quit IRC12:05
*** bvandenh has quit IRC12:08
*** sombrafam has joined #openstack-swift12:14
*** dANOKELOFF has joined #openstack-swift12:14
*** annegent_ has joined #openstack-swift12:15
dANOKELOFFIt's possible to create tempurl when your objects name is id/title . And your url is so : /account/containers/id/title ?12:15
dANOKELOFFBecause id/title represent object12:15
ahaleshould work - if it doesn't it would be a bug12:16
*** ppai has joined #openstack-swift12:18
*** Midnightmyth has joined #openstack-swift12:21
*** annegent_ is now known as annegentle_12:21
*** nshaikh has joined #openstack-swift12:22
dANOKELOFFI need to put my key in the tempurl filter ?12:25
ahalehaven't set it up for a while, but from what i remember you set the key on the account in an X- header, and then include that when you build the hmac you provide to client to use12:29
*** mmcardle has joined #openstack-swift12:30
dANOKELOFFok thank's12:31
*** mlipchuk has joined #openstack-swift12:37
*** mlipchuk has quit IRC12:40
*** mlipchuk has joined #openstack-swift12:41
*** nshaikh has left #openstack-swift12:43
*** mmcardle has quit IRC12:47
*** mmcardle has joined #openstack-swift12:51
*** annegentle_ has quit IRC12:55
*** swat30 has quit IRC12:58
*** kenhui has joined #openstack-swift12:58
*** swat30 has joined #openstack-swift12:58
*** chandan_kumar is now known as chandankumar13:03
openstackgerritgholt proposed a change to openstack/swift: SimpleClient http proxying  https://review.openstack.org/10259813:08
*** psharma has quit IRC13:09
dANOKELOFFWhen i try to setup the temp_url : swift-temp-url GET 1200 /v1/AUTH_replication/7/48/f26af6ca-bf2c-48bd-bf45-3eac9a711bdc.mp3 testkey , that return tempurl but when i try to curl -i the url i have Error 401 Unauthorized : Temp URL invalid, anyone know this bug ?13:12
*** ppai has quit IRC13:22
*** annegent_ has joined #openstack-swift13:31
*** Midnightmyth has quit IRC13:41
*** robsparker has joined #openstack-swift13:43
*** annegent_ has quit IRC13:43
*** annegent_ has joined #openstack-swift13:44
*** kenhui has quit IRC13:49
*** kenhui has joined #openstack-swift13:50
*** kenhui has quit IRC13:50
*** kenhui has joined #openstack-swift13:51
ctennisdANOKELOFF: when you curl, did you include the entire tempurl in quotes?13:53
dANOKELOFFctennis: i try but same error again13:55
*** miqui has quit IRC13:56
*** bboris has joined #openstack-swift13:56
bborishello14:01
bboriscan anyone tell me how many puts/second can i get with swift using swift all-in-one setup with 5 disks/zones and 3 replicas? currently i'm testing 50 parallel operations and i get results like 53 puts/s for 64k objects14:06
bborisis this normal?14:07
*** mmcardle has quit IRC14:09
bborisif anyone is interested in my results of ceph/swift tests, you can find them here: http://boris.descom.com/ceph-swift-140630.ods14:10
*** mmcardle has joined #openstack-swift14:15
*** dANOKELOFF has quit IRC14:15
bborisswift is quite faster in almost everything it seems, but compared to fopen writes per second... i am about to test writing to a single disk through nfs and compare that to swift, but i am waiting swift to finish replicating the objects of my last test, which was putting 4-32k objects for an hour, then get and delete. it's replicating for 18 hours now, and still going14:15
*** kenhui has quit IRC14:25
*** mmcardle has quit IRC14:29
*** dANOKELOFF has joined #openstack-swift14:30
*** kenhui has joined #openstack-swift14:31
*** mmcardle has joined #openstack-swift14:32
*** zaitcev has joined #openstack-swift14:35
*** ChanServ sets mode: +v zaitcev14:35
*** thurloat has quit IRC14:36
*** mkollaro has quit IRC14:40
creihtbboris: in your test, are you writing to a single container or multiple containers?14:42
*** thurloat has joined #openstack-swift14:42
creihtif you aren't using multiple containers that could be part of it14:43
bboriseach thread creates it's own container in the beginning, writes as much objects as it can for 60 minutes, gets them back, deletes them and deletes the container14:43
creihthow many threads?14:43
bboris5014:43
creihtahh14:43
creihtyeah you should be good there then14:44
bborison a different machine, also14:44
bboristhe network is good, i can reach almost 1 Gbit14:45
creihthave you tweaked any of your worker settings?14:45
bborisnothing, as is from the swift all-in-one documentation14:46
creihtk14:46
creihteverything defaults to only 1 worker with saio14:47
creihtwhen running your benchmark look at the swift processes, and see if any of them are reaching 100% cpu14:48
creihtlike maybe the proxy for example14:48
creihtif they are then bump the worker count up14:48
creihtthe saio is probably not the best thing to benchmark though14:49
creihtas it simulates running 4 servers on 114:49
creihtstill interesting to test though :)14:49
creihtgotta run to the dentist14:50
bborisit's true, but i don't have free machines. also, for comparison, ceph is also on that single server. i'm still waiting for the replication to finish ... how can i stop it, i dont care about the current objects14:50
bborisokay then. i'll be here tonight i guess14:50
bborisgot to figure that performance issue14:51
creihtbboris: start with trying to see what is bottlenecking during your perf run14:52
creihteither cpu is maxed on one of the servers14:52
creihtor disk io is maxed14:52
creihtonce you figure that out, then we can help you tweak14:52
creihtgotta run, but will be back later14:52
bboriscreiht: i will, thanks. later14:53
*** foexle has quit IRC14:53
*** miqui has joined #openstack-swift14:59
*** mmcardle has quit IRC15:03
*** kevinc_ has joined #openstack-swift15:08
*** mmcardle has joined #openstack-swift15:16
*** nacim has quit IRC15:16
bborishow do i stop the current replication? i don't care about the objects that swift is currently replicating and want to get rid of them so i can continue testing.15:19
*** mmcardle has quit IRC15:28
*** mmcardle has joined #openstack-swift15:30
*** Anticimex has quit IRC15:34
*** Anticimex has joined #openstack-swift15:35
*** chandankumar has quit IRC15:44
nthacker_bboris, the way i have done it is used a single copy in my ring, but i am guessing you can also choose to not run the object-replicator by changing the conf file ( i havent tried this out though so cant comment on it)15:52
*** stevemac has joined #openstack-swift15:55
*** mwstorer has joined #openstack-swift15:56
*** stevemac has quit IRC15:58
*** stevemac has joined #openstack-swift15:58
*** kevinc_ has quit IRC16:02
*** gyee has joined #openstack-swift16:03
stevemachi guys16:03
*** yuanz has joined #openstack-swift16:04
*** kevinc_ has joined #openstack-swift16:07
*** yuan has quit IRC16:08
claygcreiht: I think the default worker is auto now, doesn't saio use that?16:08
claygbboris: just swift-init all stop (pkill -f swift if it comes to it) then rm -fr /srv/node/*/objects*16:09
claygbboris: maybe service rsync stop in there somewhere16:10
*** bboris has quit IRC16:11
*** bboris has joined #openstack-swift16:12
*** dANOKELOFF has quit IRC16:37
claygso is https://review.openstack.org/#/c/91133/4 solving like the *opposite* of the un-yielding starvation issue?16:38
clayglike on the one side, before we had the threadpool, write was blocking, and if your client was pushing bytes to the object server fairly fast you'd never trampoline on socket recv so that one request would starve everyone else (that's how it went right?)16:40
*** tellesnobrega has joined #openstack-swift16:42
claygbut now that we *have* a threadpool we're gunna trampoline into run_in_thread no matter how few bytes are in the buffer to write, so there's all this extra overhead context switching spent in the hub instead of parsing the chunked bytes coming out of the socket buffer and sending down epic writes into the threadpool16:42
tellesnobregahi, im starting a devstack with swift but im getting an error when trying to create the swifttestusers16:42
claygwith this change, we let a single request do more work before kicking it back to the hub?16:42
tellesnobregait says that the crendentials are note valid16:42
claygtellesnobrega: try a different pitch?16:43
* clayg hangs his head in shame at his terrible pun16:43
claygtellesnobrega: so like ./devstack/stack.sh is failing?16:43
claygtellesnobrega: cause like when I setup devstack I just get those users for free, i always figured it was scripted; i barely understand keystoneclient16:44
tellesnobregait finishes, but when i try to use sahara and register and image it fails16:44
tellesnobregai was looking for the path of the certificates and found that they are not there16:45
*** annegent_ has quit IRC16:45
notmynamegood morning16:46
claygwhoa16:46
claygso but sahara is like a services vs. the swifttestusers guys which are just like... users16:47
tellesnobregayes16:47
tellesnobregaon top of that i get some other errors, but i thought that this might be the root of all the others16:48
claygand which certificate now?  you're trying to find the signing certificate that keystone hands out to... swift?  or sahara?16:48
tellesnobreganova --os-password admin --os-username swiftusertest2 --os-tenant-name swifttenanttest2 x509-create-cert /home/stack/devstack/accrc/swifttenanttest2/swiftusertest2-pk.pem /home/stack/devstack/accrc/swifttenanttest2/swiftusertest2-cert.pem16:49
tellesnobregai was looking fot this -cert.pem file16:49
tellesnobregaor pk.pem16:49
tellesnobregait might be a glance problem as wel16:49
tellesnobregaim not sure16:49
tellesnobregaim actually brainstorming to find the problem16:50
patchbottellesnobrega: You've given me 5 invalid commands within the last minute; I'm now ignoring you for 10 minutes.16:50
claygnotmyname: what is this guy doing!?16:50
*** zhiyan is now known as zhiyan_16:50
claygtellesnobrega: don't worry about patchbot he's a jerk16:50
* notmyname goes to shoot patchbot in the head for now16:50
tellesnobregaclayg: no problem16:50
*** patchbot has quit IRC16:51
*** zhiyan_ is now known as zhiyan16:51
claygtellesnobrega: but i don't get why a failing nova command is a swift issue?  does that command like work with the demo user?16:51
tellesnobregayes16:51
tellesnobregait fails only when creating swift users16:51
claygwhat about swift stat --os-password --os-username swiftusertest2 --os-tenant-name swifttenanttest216:52
claygumm... but that user is already created?16:52
*** rook_ has joined #openstack-swift16:53
rook_anybody installed swift 1.13 via rpm packages on centos 6.4 ?   (ducks)16:54
claygtellesnobrega: i'm trying to read up on x590-create-cert but it seems to be some sort of eucatools shim - are you sure this workflow is correct for your usecase?  I really don't think i know what you're trying to do.16:55
tellesnobregaim just trying to start a devstack installation with sahara16:56
tellesnobregasahara uses swift, so i need it running, but maybe the problem isnt with swift itself16:56
claygis #openstack-sahara a thing?16:57
notmynameclayg: I'm working on getting https://review.openstack.org/#/c/103731/ through jenkins this morning, then I'll land the 2 backport patches and we can cut an RC216:58
claygnotmyname: ok, zaitcev caught a typo in the commit - you want me to fix it up - or stay out the way of the merge train?17:01
zaitcevnotmyname: commit message actually, not even code comments17:02
*** shri has joined #openstack-swift17:04
claygi'm afk for a bit17:06
*** zhiyan is now known as zhiyan_17:08
acolesnotmyname: i may not make meeting today. no issues to report wrt SP17:15
notmynameacoles: thanks. I'll be getting an rc2 with the two small issues clayg found with the reconciler and container sync. it shouldn't invalidate any of your existing testing17:16
peluse_notmyname:  and my 2.0 update, going pretty good although I clearly don't spend enough time manually installing/operating swift... few more hiccups to work through and I'll be done w/rolling upgrades w/rsync will then do ssync real quick17:16
tellesnobregaclayg: yes, i'm there already17:20
tellesnobregathanks anyways17:20
bborisdoes 1 replica mean a partition and 1 copy of it, or just a single partition?17:34
notmynamebboris: 1 replica means that you have the data in one and only one place17:35
notmyname2 replicas == 2 locations, etc17:35
*** mmcardle has quit IRC17:35
bborisnotmyname: thanks :)17:35
*** bboris has quit IRC17:42
*** andyandy has quit IRC17:46
*** openstackgerrit has quit IRC17:49
*** mlipchuk has quit IRC17:49
*** openstackgerrit has joined #openstack-swift17:50
notmynameclayg: I fixed the commit message typo since jenkins failed again17:51
*** annegent_ has joined #openstack-swift17:54
*** annegent_ has quit IRC18:03
openstackgerritA change was merged to openstack/swift: SimpleClient http proxying  https://review.openstack.org/10259818:14
*** Kbee has joined #openstack-swift18:16
KbeeHello, Q - when are accounts or account objects created .. I don't see a api for it.. but i see in code that PUT is annotated @public18:20
peluse_notmyname:  FYI all rolling ugprade tests w/rsync completed OK. Not being an operator I stumbled through some non SP related stuff but noted that I had to restart memcached on the proxy after upgrading as cached info data didn't have policy info it.  I assume that's a normal part of one's process for ugprading (ro restart memcached).  Onto ssync after some meetings18:29
*** jamiehannaford has quit IRC18:31
Kbeeanyone ? - when are accounts or account objects created .. I don't see a api for it.. but i see in code that PUT is annotated @public18:32
*** jamiehannaford has joined #openstack-swift18:32
claygtorgomatic: did you see the py26 failure on gzip/ring fix?  seems unrelated to your change - i think it may have been some other test changes I did recently?18:32
torgomaticclayg: no, I didn't... does py26 not support getargspec or some nonsense?18:33
* torgomatic goes to look18:33
claygtorgomatic: i tested on py26 and py3 and it seemed fine - i think the failure is unrelated, py26 tests passed on the change earlier18:34
torgomatichuh... it passed check but failed gate, so it can work18:34
torgomaticoh I see; let me go fix it real quick18:35
claygyou see it!?  i don't follow18:40
claygwhy would status be an instance of Timeout?18:41
claygoh nm, i see it :P18:42
claygwell... :\18:42
torgomaticI thought I saw it, but I don't18:43
claygheh18:43
*** tongli has joined #openstack-swift18:43
torgomaticI thought it was a swob.Response and it should be .status_int instead, but it's an httplib thing, so it's probably someone's FakeConn being bad at life18:44
notmynameclayg: torgomatic: is this in https://review.openstack.org/#/c/103731/ ?18:44
claygdoh, if isinstance(Timeout(), Exception) <- not gunna work :P18:44
notmyname(just catchign up after a meeting)18:44
torgomaticnotmyname: nope, it's http://logs.openstack.org/15/97615/2/gate/gate-swift-python26/957c8b0/nose_results.html18:44
claygnotmyname: wut?18:45
torgomaticclayg: where's that?18:45
clayga few places in FakeConn18:45
notmynameah https://review.openstack.org/#/c/97615/18:46
*** cutforth has joined #openstack-swift18:46
Kbeenotmyname, creiht , Q - when are accounts or account objects created .. I don't see a api for it.. but i see in code that PUT is annotated @public18:47
notmynameKbee: so there's a couple of different way, but let me tell you about the common way18:48
notmynameKbee: if swift sees a request to PUT a container in an account, and the token given is valid for that operation, and the account doesn't exist, then swift will automatically create the account18:49
*** sombrafam has quit IRC18:49
notmynameKbee: if the token is valid and the account doesn't exist and it's a read operation for the account, swift will short-circuit and return a default empty response18:49
claygnotmyname: yeah that one is an ordering thing :\18:50
claygnotmyname: i'll fix that one, torgomatic you got the other one?18:50
torgomaticclayg: the timeout thing? yeah, running tests now18:50
notmynameKbee: there is a config value (default to off) that must be turned on before PUT/DELETE to an account will be accepted. so the other way is that you have a separate proxy server with that turned on and firewalled off to only accept connections eg from trusted sources like your provisioning system18:51
notmynameKbee: (ok, I said I would just tell you one way, but that ^^ is the other way. now you know everything)18:51
Kbeenotmyname,  hmmm.. I tried this using keystone.. Suppose you auth using keystone and try to create a container using an account name different from ( AUTH_<tenant_id) , it throws 404.. so is it keystone middleware which doesnot allow accees to an account other than tenant_id ?18:53
notmynameKbee: that sounds reasonable (but I'm not a keystone expert18:53
*** angelastreeter has joined #openstack-swift18:53
*** Midnightmyth has joined #openstack-swift18:53
notmynameKbee: reasonable == doesn't surprise me18:53
*** openfly has quit IRC18:54
Kbeenotmyname,  :)  .. got it ..18:54
*** bboris has joined #openstack-swift18:55
notmynameswift team meetng in a few minutes in #openstack-swift18:58
*** elambert has joined #openstack-swift18:58
notmynameerr...in #openstack-meeting18:58
Kbeenotmyname, i dug into keystoneauth middleware.. and yes.. they check whether account matches tenatn_id -> https://gist.github.com/keshavab/0d48163467d5ff0a2f5418:59
Kbeenotmyname, thanks18:59
notmynameKbee: np19:00
notmynamemeeting time19:00
*** kenhui has quit IRC19:06
openstackgerritClay Gerrard proposed a change to openstack/swift: Fix order dependent test in proxy.test_server  https://review.openstack.org/10430619:20
*** jamiehannaford has quit IRC19:21
openstackgerritSamuel Merritt proposed a change to openstack/swift: Fix exception raising in FakeConn  https://review.openstack.org/10431919:26
*** Kbee has quit IRC19:28
*** angelastreeter has quit IRC19:34
*** jasond has joined #openstack-swift19:38
jasondi noticed the swift-temp-url script requires v119:38
jasondhttps://github.com/openstack/swift/blob/master/bin/swift-temp-url#L6119:38
jasondshould that be updated to accept v1 or v2?19:38
mattoliverauCool, with that done, I'm going back to bed, see you all in a few hours :)19:38
claygcreiht: you know how your always railing on pipeline construction - have you looked at how some of the other os projects do it?19:39
zaitcevjasond: um there's no v219:39
zaitcevor x2 or n3 or anything else but v119:39
*** cutforth has quit IRC19:40
jasondzaitcev: ah, i guess i assumed "swift -V 2.0" meant swift v2, but i see it's the auth protocol.  thanks19:40
*** angelastreeter has joined #openstack-swift19:47
*** stevemac has quit IRC20:04
*** stevemac has joined #openstack-swift20:05
peluse_clayg:  there?20:11
creihtclayg: not recently20:15
peluse_creiht:  thx, will gather a bit more data on the issue I'm still seeing w/rolling upgrades, probably not a real problem but want to double check a few things20:16
*** stevemac has quit IRC20:18
peluse_notmyname:  you there?20:28
notmynamepeluse_: yes. what's up?20:29
peluse_notmyname:  ahh, jsut texted you :)20:29
notmynamepeluse_: ya, I got that too :-)20:29
notmynamepeluse_: is in here fine, or do we need a phone?20:29
peluse_notmyname:  so clayg's keyError fix is along the same lines as this but doesn't address what I see20:29
notmynameok20:29
peluse_here is fine20:30
peluse_here's the scenario:20:30
notmyname( torgomatic is listening too)20:30
torgomaticlies20:30
peluse_if I'm doing IO, banging away, and I upgrade my proxy from 1.13.1 to v2 (claygs patch) the PUt in proxy obj server tries to ready the storage_policy key from container_info and gets a keyError20:31
notmynamethe probability that torgomatic is listening is >020:31
peluse_one easy patch is to try/except on keyError and define policy_index to None if it fails20:31
notmynamepeluse_: proxy obj controller?20:31
peluse_or, like I said, reset memchache so the info is cleared and you don't get the error but guess that's bad :)20:31
peluse_notmyname:  yes20:31
peluse_right at the top of PUT20:32
notmynameagainst master, what file and line number are you looking at?20:33
peluse_I'm looking at clayg patch but its policy_index = req.headers.get..... like 3 lines into PUT20:33
notmynamecontrollers.obj.py:460?20:33
peluse_yup20:34
notmynamepeluse_: should be container_info.get('storage_policy')?20:34
torgomaticif I only had a time machine...20:34
notmynametorgomatic: well, the good news is that it doesn't matter when you get one20:34
peluse_yes20:34
peluse_torgomatic:  well, that I wasn't sure of so I was asking.  You get an unhandled exception20:35
torgomaticmemcache would get the *headers* jammed into it, not the result of _headers_to_blah, and then the same compatibility logic that saves us during rolling upgrades would also work with stale memcache data20:35
torgomaticbut yeah, now that you see the bug it's obvious how it happens ;)20:36
torgomatic"obvious once pointed out"20:36
peluse_torgomatic:  so an unhandled exception doesn't puke that reqeust?20:36
torgomaticpeluse_: oh, it'll screw things up all right; it should turn into a 50020:36
peluse_torgomatic:  yeah, my cosbench run fails if I don't catch the exception20:36
notmynameok, ya, that's my next question. unpatched, what does this do? cause a 5xx to the client?20:37
peluse_sure looks that way....20:37
peluse_6 places total this can happen (one in LE middleware, 5 in proxy controllers obj)20:39
notmynamepeluse_: as in 6 places that need to be patched or this PUT is called in 6 places?20:39
TaiSHiHi everyone20:39
TaiSHiI'm planning on a structure and I'm considering swift as an object storage, since I'll be managing a great amount of small files20:40
peluse_notmyname:  6 places where we pull the policy_index out of container_info so 6 places to patch worst case20:40
peluse_err, 'storage_policy' out of container_info20:41
torgomaticeither that or we make container_info do something smarter20:42
peluse_torgomatic:  how do you make a dict do somethign smarter?20:42
notmynamepeluse_: clayg is telling me why this isn't bad20:42
peluse_oh, you mean the function :)20:42
TaiSHiStructure would be mostly webservers that need to have their data equal at all times, occasionally (and temporarily) new webservers might fire up. Also, webservers (at least fixed ones) would act as storage nodes20:42
torgomatic:)20:42
TaiSHiCan swift do this ?20:42
torgomaticpeluse_: well, it's sort of hard; it's easy to chuck a value in for 'storage_policy', but what should that value be?20:43
peluse_torgomatic:  if it doesn't exist it can be None and will be handled properly later on20:44
torgomaticI guess if the container was ever seen by a pre-policy proxy (which is how it got in memcache) then it's policy 020:44
peluse_yup, for a patch 0 or None would work20:44
torgomaticokay, that sounds reasonable then20:44
* peluse_ awaits clayg's insight as to why this isn't bad20:44
notmynamepeluse_: nm. just walking through it with him20:45
notmynamepeluse_: headers_to_container_info() defaults to SP 020:45
notmynamebut if it's cached, it won't get added20:46
notmynameso a patch to container_info() would probably be best. and default to 0 seems right20:46
peluse_but that doesn't fix the exception at line 460 (or the other places), thats downstream20:47
torgomaticnotmyname: which is why we should get our time machine and start to always have stored the headers in memcache ;)20:47
notmyname:-)20:47
peluse_right?  (about the exception)20:47
notmynameTaiSHi: simply, yes. (but I'm focusing on the issue peluse_ has found that may require a backport in our current release QA first)20:48
claygtorgomatic: I think we can just pass the memcache info through a fill in defaults function before handing it out to the app20:48
TaiSHinotmyname: It is not urgent, but I'd like to get it out of the way20:48
notmynamepeluse_: well, yes handling exceptions is good, but if we can guarantee that the header is always in the result, then the code gets simpler, right?20:49
TaiSHiPing me whenever you want, I'll most likely be around here20:49
torgomaticclayg: proxy.base.Controller.container_info() seems like a good place to stick a call to setdefault20:49
notmynamepeluse_: ie instead of patching those 6 locations, patch container_info (or whatever) once20:49
claygpeluse_: we could also throw out cache entries that don't have all the good bits we want and make that shit go out to the container servers as they find them20:49
peluse_notmyname:  ya, that's why I said "worst case" 6 places :)20:49
notmyname:-)20:49
peluse_clayg:  sounds intersting, don't know how to do that quickly on my end though.  In fact you or torgomatic can probably nail this much faster than me although I'm glad to handle it of course20:50
notmynamepeluse_: can you put together a patch and unit test for it? then between clayg torgomatic and me well find two reviewers to land it20:50
peluse_heh, I'm game for anything - clayg/torgomatic?20:50
* peluse_ starts to put something together...20:52
*** miqui has quit IRC20:53
peluse_looks like the container_info() patch will be simple20:53
notmynamepeluse_: thanks for catching that. after you submit the patch, I'd love to hear how you found it20:56
peluse_you got it20:57
*** kevinc_ has quit IRC21:02
*** kevinc_ has joined #openstack-swift21:03
*** openfly has joined #openstack-swift21:04
*** tellesnobrega has quit IRC21:14
*** gyee has quit IRC21:18
*** annegent_ has joined #openstack-swift21:18
peluse_notmyname:  propose to master then?21:19
torgomaticpeluse_: sounds good to me21:22
peluse_cool, letting one last test finish and will hit 'go'21:23
*** tellesnobrega has joined #openstack-swift21:27
openstackgerritpaul luse proposed a change to openstack/swift: Fix potential missing key error in container_info  https://review.openstack.org/10435021:30
torgomaticpeluse_: fwiw, you can condense those 3 lines to simply "info.setdefault('storage_policy', None)"21:32
torgomaticor if you're really into code golf, "info.setdefault('storage_policy')"21:32
peluse_torgomatic:  sweet... needs it one other spot though... I pushed before doing my system level upgrade test and won't make that mistake again :)21:43
claygtorgomatic: peluse_: I'm not sure that's exactly the plce that needs fixing is it?22:00
claygoh.... i guess i was just expecting it closer to the memcache get_info since that's the place where it might not be there22:00
*** tongli has quit IRC22:01
claygbut i guess that covers everything22:01
*** bboris has quit IRC22:03
peluse_well, I tried there but that can return None so there are two callers that need it that wouldn't get it. I could be wrong, will udpate it in just a second, just passed my system test but need one more line of coverage in unit :)22:03
mattoliverauMorning.. again :)22:07
openstackgerritClay Gerrard proposed a change to openstack/swift: Fix exception raising in FakeConn  https://review.openstack.org/10431922:10
claygpeluse_: are you making another change, or are we just waiting on gerrit?22:12
*** angelastreeter has quit IRC22:13
claygpeluse_: i take back what i said about it being in the wrong spot - it's in the right spot for exactly the reason you gave.22:13
peluse_hmm, OK.  let me post what I have and you can take a look22:13
openstackgerritpaul luse proposed a change to openstack/swift: Fix potential missing key error in container_info  https://review.openstack.org/10435022:14
peluse_clayg:  take a gander, its functional but I don't have an assertion for the change at line 992 in base.py yet22:15
peluse_clayg:  I have to leave to pick up my son or he'll be stranded.  Be back online in an hour or so feel free to move it forard as you see fit, I'll check back when I get on again22:20
claygpeluse_: i see a good place to add the test for def container_info method on base controller?22:30
claygpeluse_: are you hacking or you want me to push something up?22:30
*** annegent_ has quit IRC22:34
*** Midnightmyth has quit IRC22:36
claygpeluse_: k, i'm going to take that as you're not on it just right this minute22:56
claygtorgomatic: you see the test changes i snuk in with that FakeConn fixup you did?22:57
claygtorgomatic: it's got your name on it, and i've had a rough track record lately, so - HEADS UP!22:57
openstackgerritClay Gerrard proposed a change to openstack/swift: Fix potential missing key error in container_info  https://review.openstack.org/10435022:57
torgomaticclayg: yeah, I +2'ed it already; just waiting for someone without code in the mix to get in there and approve it22:58
claygwooooo clayg the plagiarist22:58
claygtorgomatic: speaking of doesn't yet have code in the mix; I think peluse_'s container_info fix is ready to go -> https://review.openstack.org/10435022:59
claygprobably be a nice treat when he gets back online to see it's ready already ;)22:59
*** rook_ has quit IRC22:59
peluse_clayg:  muchas gracias!23:06
peluse_torgomatic:  saw your comment too and, yup, that's why I used '0'...23:07
*** annegent_ has joined #openstack-swift23:12
notmynamepeluse_: looking23:14
*** Tyger has joined #openstack-swift23:20
TygerGood morning/afternoon/evening/night as appropriate for your local timezone.23:23
*** annegent_ has quit IRC23:26
TygerAnyone besides torgomatic feel like taking a look at a simple cleanup patch 102401?23:26
Tygerhttps://review.openstack.org/#/c/102401/23:27
*** gyee has joined #openstack-swift23:33
peluse_Tyger:  curious, what's the main reason for that change?23:36
*** kevinc_ has quit IRC23:37
Tygerpeluse_: Mostly just a cleanup for consistency; I don't really have a strong opinion of if it is the right way to do it, but I was grepping the logs for requests originating at the object services (replication, etc) and assumed it would be "object-replicator" and the like.23:38
TygerIf I made that assumption, other people might as well.23:39
*** kevinc_ has joined #openstack-swift23:39
peluse_Tyger:  OK, wanted to make sure I was missing something somewhere :)  I guess I wonder if changing something like this, sort of a "title" in the logs could impact other folks who may already have tools for log parsing that are going to have to change now and wonder "what the heck did this change for?" kinda thing.  No idea if that's a real thing to be considered about or not though...23:42
Tygerpeluse_: That thought occurred to me as well. But like you, I have no idea if it's a consideration either.23:44
TygerI suspect people would be more interested in requests from the proxy server rather than requests from replication or container updates.23:44
TygerIf they are interested in the origin of the request at all, that is.23:45
peluse_that's why it takes a few reviewers I guess :)23:49
Tygerpeluse_: Feel free to add that as a comment so other reviewers might consider it.23:52
peluse_yup, will do23:53
notmynameTyger: when proposing changes to logs, two things to keep in mind: (1) logs are considered sacred like an API. that is, assume it's a public interface that is only changed carefully. and (2) leave the http://docs.openstack.org/developer/swift/logs.html docs better than you found them23:53
notmynamere #1, ie things can be added, but reordering is right out. changing values isn't forbidden, but it is only done carefully23:54
*** ho has joined #openstack-swift23:54
*** kevinc_ has quit IRC23:54
Tygernotmyname: Noted. Do you have any opinions on changing the user agent of the object server/replicator/etc? It would make ammending the "Storage Node Logs" section on "referer" easier when it can just say that all services use the name of the service and process ID as their user agent, rather than having to specify that object server uses obj-server, etc23:56
*** kevinc_ has joined #openstack-swift23:57
TygerGiven that only the proxy server is specifically mentioned at the moment, that does sort of confirm my feeling that people mostly care about requests from the proxy server.23:58
notmynameTyger: while I think your proposed changes are probably better, I'd have to think a little more about that particular issue. I suspect it's ok to change that, but I'm not sure. I'd especially like to get input from gholt, acoles, and portante23:58
openstackgerritOpenStack Proposal Bot proposed a change to openstack/swift: Updated from global requirements  https://review.openstack.org/8873623:59
Tygernotmyname: Sounds like a good idea to me.23:59

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