Wednesday, 2014-07-30

*** tusharsg has quit IRC00:05
*** Midnightmyth has quit IRC00:09
*** dmorita has joined #openstack-swift00:25
openstackgerritA change was merged to openstack/swift: Fix "Handoff requested (N)" log spam  https://review.openstack.org/10979100:32
*** bill_az has quit IRC00:40
*** cpen has quit IRC00:41
*** mitz has quit IRC00:43
*** tsg has joined #openstack-swift00:44
*** shri has left #openstack-swift00:47
*** mitz has joined #openstack-swift00:48
*** addnull has joined #openstack-swift00:56
*** addnull has quit IRC00:58
*** addnull has joined #openstack-swift00:59
*** mitz has quit IRC01:00
*** mitz has joined #openstack-swift01:03
*** mitz has quit IRC01:04
*** mitz has joined #openstack-swift01:06
*** mitz has quit IRC01:17
*** addnull has quit IRC01:21
*** addnull has joined #openstack-swift01:21
*** tsg has quit IRC01:23
*** mrmoje has quit IRC01:23
*** addnull has quit IRC01:26
*** judd7 has quit IRC01:28
*** nosnos has joined #openstack-swift01:38
*** addnull has joined #openstack-swift01:43
*** haomaiwang has joined #openstack-swift01:43
*** haomaiwang has quit IRC01:44
*** haomaiwang has joined #openstack-swift01:45
*** haomaiw__ has joined #openstack-swift01:58
*** haomaiwang has quit IRC02:01
*** tsg has joined #openstack-swift02:11
*** jyoti-ranjan has joined #openstack-swift03:15
*** abhirc has joined #openstack-swift03:17
*** morganfainberg is now known as morganfainberg_Z03:20
*** morganfainberg_Z is now known as morganfainberg03:22
*** gyee has quit IRC03:23
*** nosnos has quit IRC03:28
*** addnull has quit IRC03:46
*** addnull has joined #openstack-swift03:47
*** addnull has quit IRC03:51
*** nosnos has joined #openstack-swift04:03
*** ppai has joined #openstack-swift04:04
*** jyoti-ranjan has quit IRC04:05
*** haomaiw__ has quit IRC04:09
*** haomaiwang has joined #openstack-swift04:10
*** Shivani has quit IRC04:17
*** addnull has joined #openstack-swift04:17
*** addnull has quit IRC04:22
*** haomaiwang has quit IRC04:29
*** haomaiwa_ has joined #openstack-swift04:29
allyunionAnyone use Puppet with Swift OpenStack?04:41
allyunionEr, OpenStack Swift.04:41
openstackgerritTushar Gohad proposed a change to openstack/swift: EC: Add support for policy types, 'erasure_coding' policy  https://review.openstack.org/10364404:42
*** addnull has joined #openstack-swift04:51
*** tusharsg has joined #openstack-swift04:58
*** morganfainberg is now known as morganfainberg_Z04:59
*** tsg has quit IRC05:01
*** haomaiwa_ has quit IRC05:04
*** haomaiwang has joined #openstack-swift05:04
*** kopparam has joined #openstack-swift05:14
*** haomaiw__ has joined #openstack-swift05:14
*** haomaiwang has quit IRC05:17
*** jyoti-ranjan has joined #openstack-swift05:40
*** kopparam_ has joined #openstack-swift05:42
*** chandankumar has joined #openstack-swift05:44
*** kopparam has quit IRC05:44
*** tusharsg has quit IRC05:45
mattoliveraunotmyname, acoles_away, torgomatic, portante, clayg_: (and anyone else I've missed or want to voice an opinion) can you all take a look at the subject and email template I've put together and can I get your feedback or corrections on this etherpad: https://etherpad.openstack.org/p/abandoner_email06:09
mattoliverauwhen your all up and at work of course :)06:10
fifieldt_mattoliverau, some new contributors might not know what rebase is06:11
mattoliveraufifieldt_: good call :)06:11
fifieldt_I'd also add a stanza about how friendly the swift team is06:12
fifieldt_and where they can go for help if they need it06:12
fifieldt_I normally link to https://wiki.openstack.org/IRC and https://wiki.openstack.org/wiki/MailingLists#Future_Development06:13
fifieldt_but, otherwise06:13
fifieldt_love your work :)06:13
mattoliveraufifieldt_: thanks I appreciate you taking a look!!06:14
*** fifieldt_ is now known as fifieldt06:15
*** haomaiw__ has quit IRC06:19
*** fifieldt has quit IRC06:19
*** haomaiwang has joined #openstack-swift06:19
*** ho has joined #openstack-swift06:30
*** haomaiwang has quit IRC06:35
*** haomaiwang has joined #openstack-swift06:36
*** bvandenh has joined #openstack-swift06:38
*** haomaiw__ has joined #openstack-swift06:42
*** haomaiwang has quit IRC06:42
*** haomai___ has joined #openstack-swift06:58
*** haomaiw__ has quit IRC07:02
*** psharma has joined #openstack-swift07:19
*** astellwag|afk is now known as astellwag07:19
*** fifieldt has joined #openstack-swift07:23
*** nexusz99 has joined #openstack-swift07:35
nexusz99I have question. Is there any request for deleting dynamic large object both manifest file and segments? if i wan't to delete dynamic large object, i have to know all segments and request delete one by one??07:41
*** leopoldj has joined #openstack-swift08:01
*** haomai___ has quit IRC08:08
*** haomaiwang has joined #openstack-swift08:09
*** mrmoje has joined #openstack-swift08:14
*** mkollaro has joined #openstack-swift08:16
*** mmcardle has joined #openstack-swift08:18
*** haomaiw__ has joined #openstack-swift08:24
*** haomaiwang has quit IRC08:26
*** jyoti-ranjan has quit IRC08:47
*** ho has quit IRC08:49
*** nosnos has quit IRC08:49
*** marzif has joined #openstack-swift09:01
*** openstackgerrit has quit IRC09:16
*** openstackgerrit has joined #openstack-swift09:17
*** jyoti-ranjan has joined #openstack-swift09:25
*** nosnos has joined #openstack-swift09:30
*** infotection has quit IRC09:38
*** sungju has joined #openstack-swift09:42
*** sungju has quit IRC09:43
*** sts_ has joined #openstack-swift09:44
*** j_king_ has joined #openstack-swift09:44
*** occupant has quit IRC09:44
*** wer has quit IRC09:44
*** amandap has quit IRC09:44
*** MooingLemur has quit IRC09:44
*** thurloat has quit IRC09:44
*** bsdkurt has quit IRC09:44
*** creiht has quit IRC09:44
*** jd__ has quit IRC09:44
*** sts has quit IRC09:44
*** anderstj has quit IRC09:44
*** alpha_ori has quit IRC09:44
*** j_king has quit IRC09:44
*** torgomatic has quit IRC09:44
*** hurricanerix has quit IRC09:44
*** briancline has quit IRC09:44
*** torgomatic has joined #openstack-swift09:44
*** MooingLe1ur has joined #openstack-swift09:44
*** MooingLe1ur has quit IRC09:44
*** MooingLe1ur has joined #openstack-swift09:44
*** ChanServ sets mode: +v torgomatic09:44
*** occupant has joined #openstack-swift09:44
*** wer has joined #openstack-swift09:44
*** jd__ has joined #openstack-swift09:44
*** bsdkurt has joined #openstack-swift09:44
*** briancline has joined #openstack-swift09:44
*** amandap has joined #openstack-swift09:45
*** hurricanerix has joined #openstack-swift09:45
*** thurloat has joined #openstack-swift09:45
*** nexusz99 has quit IRC09:45
*** infotection has joined #openstack-swift09:45
*** creiht_ has joined #openstack-swift09:45
*** anderstj has joined #openstack-swift09:45
*** nexusz99 has joined #openstack-swift09:45
*** alpha_ori has joined #openstack-swift09:46
*** nexusz99 has quit IRC09:50
*** infotection has quit IRC09:52
*** infotection has joined #openstack-swift09:53
*** nexusz99 has joined #openstack-swift09:59
*** pconstantine has quit IRC09:59
*** Midnightmyth has joined #openstack-swift09:59
*** pconstantine has joined #openstack-swift10:00
*** infotection has quit IRC10:05
*** pconstantine has quit IRC10:05
*** infotection has joined #openstack-swift10:10
*** mmcardle has quit IRC10:18
*** pconstantine has joined #openstack-swift10:19
*** infotection has quit IRC10:19
*** ppai has quit IRC10:20
*** nosnos has quit IRC10:22
*** infotection has joined #openstack-swift10:23
*** mmcardle has joined #openstack-swift10:25
*** ppai has joined #openstack-swift10:33
*** jyoti-ranjan has quit IRC10:43
*** jyoti-ranjan has joined #openstack-swift10:43
*** mkollaro has quit IRC10:48
*** devpadak has joined #openstack-swift10:49
*** nexusz99 has quit IRC10:49
*** mkollaro has joined #openstack-swift11:07
*** mmcardle has quit IRC11:14
*** aswadr has joined #openstack-swift11:22
*** mitz has joined #openstack-swift11:27
*** mitz has quit IRC11:28
*** mitz has joined #openstack-swift11:30
*** mitz has quit IRC11:31
*** mitz has joined #openstack-swift11:33
*** kopparam has joined #openstack-swift11:34
*** kopparam_ has quit IRC11:36
*** ondergetekende has quit IRC11:46
*** ondergetekende has joined #openstack-swift11:48
*** ondergetekende has quit IRC11:53
*** ondergetekende has joined #openstack-swift11:54
*** mmcardle has joined #openstack-swift12:14
*** mrsnivvel has quit IRC12:16
*** tdasilva has quit IRC12:22
*** zslot has joined #openstack-swift12:25
*** mmcardle has quit IRC12:26
*** mmcardle has joined #openstack-swift12:28
*** mrsnivvel has joined #openstack-swift12:29
*** dmorita has quit IRC12:32
*** mrsnivvel has quit IRC12:37
*** addnull has quit IRC12:39
*** ppai has quit IRC12:47
*** mrsnivvel has joined #openstack-swift12:56
*** kopparam has quit IRC12:57
*** devpadak has quit IRC12:58
*** bvandenh has quit IRC13:02
*** bill_az has joined #openstack-swift13:12
*** bvandenh has joined #openstack-swift13:17
*** mmcardle has quit IRC13:17
*** psharma has quit IRC13:25
*** mmcardle has joined #openstack-swift13:26
*** devpadak has joined #openstack-swift13:30
*** nexusz99 has joined #openstack-swift13:30
*** mmcardle has quit IRC13:39
*** mmcardle has joined #openstack-swift13:40
*** tdasilva has joined #openstack-swift13:51
*** judd7 has joined #openstack-swift13:53
*** kopparam has joined #openstack-swift13:53
*** dmsimard_away is now known as dmsimard13:57
*** kopparam has quit IRC13:58
*** kopparam has joined #openstack-swift13:58
*** tsg has joined #openstack-swift14:01
*** kopparam has quit IRC14:03
*** Wimpers has joined #openstack-swift14:04
*** mmcardle has quit IRC14:11
openstackgerritOpenStack Proposal Bot proposed a change to openstack/swift: Updated from global requirements  https://review.openstack.org/8873614:12
*** tsg has quit IRC14:20
*** vr1 has joined #openstack-swift14:21
*** zul has joined #openstack-swift14:23
*** ujjain has quit IRC14:25
*** ujjain has joined #openstack-swift14:27
*** SHiker has joined #openstack-swift14:29
SHikerIf I configure swift to only maintain 2 copies of an object, will it still only return a successful PUT if both copies are written or will it return success if one copy is written to object server?14:30
*** tsg has joined #openstack-swift14:40
*** abhirc has quit IRC14:41
*** bvandenh has quit IRC14:43
*** zul has quit IRC14:47
*** mmcardle has joined #openstack-swift14:49
*** chandankumar_ has joined #openstack-swift14:50
pconstantineSHiker: return (n // 2) + 114:51
*** marcusvrn has quit IRC14:51
*** chandankumar has quit IRC14:53
SHikerPConstantine: Thanks.15:04
*** SHiker has quit IRC15:05
*** tusharsg has joined #openstack-swift15:06
*** tsg has quit IRC15:09
*** tsg has joined #openstack-swift15:10
*** tusharsg has quit IRC15:11
*** mwstorer has joined #openstack-swift15:13
*** zul has joined #openstack-swift15:17
*** kevinc_ has joined #openstack-swift15:18
*** astellwag is now known as astellwag|afk15:19
nexusz99I have question. Is there any request for deleting dynamic large object both manifest file and segments? if i wan't to delete dynamic large object, i have to know all segments and request delete one by one??15:22
*** gyee has joined #openstack-swift15:28
*** mmcardle has quit IRC15:28
pconstantinenexusz99: http://docs.openstack.org/developer/swift/middleware.html#module-swift.common.middleware.bulk15:31
*** mmcardle has joined #openstack-swift15:31
dfg_nexusz99: yes. static large objects has a delete-all function but not dynamic15:33
vr1hi all, we diskfile backend developers, how are we supposed to manage underlying I/O exceptions to the upper layers ?15:34
pconstantinevr1: you can raise one of the HTTPException classes, obj-server will catch it and create a proper response15:38
vr1pconstantine: thx15:39
pconstantinevr1: at least that's what I do, works quite well15:39
*** Wimpers has quit IRC15:39
*** tdasilva has quit IRC15:45
*** chandankumar_ has quit IRC15:45
*** mrmoje has quit IRC15:47
*** kevinc_ has quit IRC15:47
*** MooingLe1ur is now known as MooingLemur15:50
*** gyee has quit IRC15:51
nexusz99dfg_: Thanks. I use s3multi with swift3. The s3multi implements multipart upload by Dynamic large object.. So. i have no idea how to delete multipart object..15:54
*** kevinc_ has joined #openstack-swift15:56
*** tdasilva has joined #openstack-swift15:58
nexusz99pconstantine: Thanks. I will refer to your opinion.16:03
pconstantinenexusz99: you can list parts of multipart object using s3multi and then delete all of them with bulk delete or one by one16:05
*** gyee has joined #openstack-swift16:05
dfg_nexusz99: ya, what pconstantine said. you can get the listing by doing a HEAD on the DLO object, getting the X-Object-Manifest header, and doing a container listing with prefix using that header16:07
*** devpadak has quit IRC16:08
*** gyee has quit IRC16:09
nexusz99pconstantine: dfg_: thank you for your answer16:11
*** cutforth has joined #openstack-swift16:12
*** pberis has quit IRC16:21
*** pberis has joined #openstack-swift16:21
*** nexusz99 has quit IRC16:29
*** pberis has quit IRC16:30
*** vr1 has left #openstack-swift16:31
openstackgerritTushar Gohad proposed a change to openstack/swift: EC: Add support for policy types, 'erasure_coding' policy  https://review.openstack.org/10364416:32
*** pberis has joined #openstack-swift16:33
*** jyoti-ranjan has quit IRC16:34
*** shri has joined #openstack-swift16:40
*** pberis has quit IRC16:44
*** pberis1 has joined #openstack-swift16:44
notmynamegood morning16:48
*** pberis has joined #openstack-swift16:52
*** cpen has joined #openstack-swift16:53
*** pberis1 has quit IRC16:55
*** peluse_ has quit IRC16:55
*** peluse_ has joined #openstack-swift16:57
peluse_good morning!16:57
notmynamegreat openstack reactions post: "trying to use devstack" http://openstackreactions.enovance.com/2014/07/trying-to-use-devstack/16:59
*** leopoldj has quit IRC17:06
cpenI’ve got a question about setting ACLs on the object level17:07
peluse_notmyname:  heh, I like that little clip17:08
*** morganfainberg_Z is now known as morganfainberg17:09
chmouelnotmyname: lol17:14
*** bvandenh has joined #openstack-swift17:14
chmouel /this is posted from a devstack core devs :p/17:15
chmouelbut that's not as bad :)17:15
*** astellwag|afk is now known as astellwag17:19
cpenit seems like Swift doesn’t support object-level ACLs.  I first wanted to make sure that I wasn’t missing something.  but presuming that’s true, I was wondering if there are any thoughts on why that’s the case17:20
*** bill_az has quit IRC17:20
*** mkollaro has quit IRC17:22
*** pberis has quit IRC17:25
*** pberis has joined #openstack-swift17:25
*** abhirc has joined #openstack-swift17:30
*** cutforth has quit IRC17:31
*** pberis1 has joined #openstack-swift17:32
*** pberis has quit IRC17:32
notmynamecpen: that is correct. swift doesn't support object ACLs17:34
cpenbummer :[17:34
cpenare there any conference notes or blog posts, etc. that discuss this design decision?17:35
cpenI tried looking around before coming here, but couldn’t find anything17:35
portantenotmyname: swift would support object acls if you put one object per container. :)17:36
cpen:]17:36
notmynamecpen: the real reason (as with all things programming) is because nobody has written it. the "design decision" is because almost everything in swift is grouped on containers (eg ACLs today, static web, versioning, storage policies)17:37
*** mmcardle1 has joined #openstack-swift17:37
cpenthat makes sense17:37
*** chandankumar_ has joined #openstack-swift17:38
cpenI’m a bit surprised, actually.  S3 has supported object-level ACLs since its inception, if I recall correctly.  they’ve been around for at least a long time.17:38
notmynamemattoliverau: I made a couple of edits to the etherpad email tempate17:39
*** mmcardle has quit IRC17:39
cpenin any case, I may implement a piece of middleware implementing some of this at some point in the future17:39
cpenI’ll make sure to mention it here if/when I do!17:39
notmynamecpen: why in middleware?17:41
cpeneasiest place to implement for my organization17:41
cpennot really ready to start hacking on swift itself17:41
notmynamecpen: if you're considering writing the functionality, maybe you could add it to the proxy server itself17:41
cpenyeah, I can see how that might be a superior implementation17:42
cpenI’ll keep it in mind17:42
notmynamecpen: are you using swift as an internal s3 replacement?17:43
cpennah.  s3 was never used where I’m working now.  but I’ve used it in past gigs.17:43
*** tsg has quit IRC17:43
notmynameah ok17:43
*** anderstj has quit IRC17:44
*** amandap has quit IRC17:44
*** wer has quit IRC17:44
*** occupant has quit IRC17:44
*** anderstj has joined #openstack-swift17:45
*** occupant has joined #openstack-swift17:45
*** amandap has joined #openstack-swift17:45
notmynameoh yeah. swift team meeting in 1.25 hours (at 1900utc) in #openstack-meeting17:48
*** abhirc has quit IRC17:51
*** morganfainberg is now known as morganfainberg_Z17:51
pconstantinecpen: container acls are cached in memcache, memcaching object acls will put a lot of pressure on memcache, and not caching them may lead to unessesary reads and object-server disk cache eviction17:53
pconstantinenow when I'm thinking about it, using memcache on object servers actually can lead to a better performance, as disk cache is highly ineffective without proper hints, and not too many hints are at the developer disposal17:56
cpenyeah, I suspected that’s why container acl management is done in the proxy server in the first place17:56
*** tsg has joined #openstack-swift17:56
pconstantinecpen: but, extending container db to hold object metadata, can solve the problem quite easily17:56
cpenif I was going to do it with middleware, I first thought of doing it on the object server anyway, but was then thinking that I should do it on the proxy server to properly integrate with the auth pipeline there17:56
cpenyeah, that’s another solution17:57
cpenmore complex, of course17:57
pconstantinecpen: not complex at all, like 10 lines of code :)17:57
notmynameI don't think you want to add more per-object info to the container DB though. they can already get quite large. also, the migration story would be harder17:57
notmynameand as cpen mentioned, doing it on a storage node makes it harder because of the auth integration17:58
cpencomplex in the sense of having to consider performance & resource implications, etc.17:58
pconstantinenotmyname: dunno, it's quite a lot of info anyway, and sqlite uses full pages if I'm not mistaken17:58
pconstantinenotmyname: using object-level metadata is easy here, just short read on GET and properly kill it on object server18:00
notmynameit's not that a particular object will store a lot of info for ACLs, it's that a container has millions (or more) of them18:00
notmynamepconstantine: you could do it in the proxy server and not cache it. as soon as the headers are read, do the ACL validation and close the internal connection before streaming the data.18:02
notmynamepconstantine: but as you mentioned, if there are a lot of requests that are denied, then this becomes quite taxing on the cluster as a whole18:02
pconstantinepconstantine: that's the "short read" I'm referring to, you will get errors in logs :)18:02
pconstantinenotmyname: AFAIK, sqlite will use at least 1k per row in object table anyway18:03
pconstantineso, if you have less than 1k data - you're not changing anything18:03
cpenI was initially consdiering just using object-level metadata for an initial implementation, and doing it on the object server for better distribution of work.  but for a complete implementation, you want full auth integration, so that would necessitate doing it on the proxy server, as best I understand18:04
*** gyee has joined #openstack-swift18:04
notmynamecpen: ya, that sounds correct18:04
*** gyee has quit IRC18:05
*** gyee has joined #openstack-swift18:05
pconstantinenotmyname: yep, most certainly Swift is using 1024 byte pages and never vacuumint, which means that each row in the object table is 1024 bytes18:12
*** bvandenh has quit IRC18:13
*** astellwag is now known as astellwag|afk18:14
torgomaticnotmyname: heh, thanks for writing some positive words after my mailing list message :)18:16
notmynametorgomatic: :-)18:17
*** gyee has quit IRC18:18
*** mmcardle1 has quit IRC18:19
*** gyee has joined #openstack-swift18:19
*** cutforth has joined #openstack-swift18:21
*** zslot has quit IRC18:23
*** bvandenh has joined #openstack-swift18:28
*** chandankumar_ has quit IRC18:33
*** tdasilva has quit IRC18:34
*** tdasilva has joined #openstack-swift18:37
*** kevinc_ has quit IRC18:43
*** gvernik has joined #openstack-swift18:47
*** tdasilva_ has joined #openstack-swift18:59
mattoliveraunotmyname: thanks I'll take a look post meeting.19:00
notmynameyup, it's meeting time19:00
*** ChanServ sets mode: +v dfg_19:02
*** tdasilva has quit IRC19:03
*** zul has quit IRC19:04
*** mrsnivvel has quit IRC19:05
*** mrsnivvel has joined #openstack-swift19:07
*** ophuk has joined #openstack-swift19:09
*** creiht_ is now known as creiht19:09
ophukwhen using swift to upload an object you have an option for object-threads to upload said objects with multiple threads. Is there an equivalent for swiftclient?19:12
torgomaticophuk: the command-line tool "swift" is swiftclient19:12
ophuktorgomatic: that's what I thought but I couldn't figure out how to tell it to use multiple threads in my script19:13
*** kevinc_ has joined #openstack-swift19:14
ophuktorgomatic: I import swiftclient.client as swiftClient, and when I upload it I use swiftClient.put_object(SWIFT_ENDPOINT, TOKEN, contName, fileName, file_object, None, None, None, None, None, None, None, None, None) - I couldn't find an option for that one19:15
ophukam I just looking in the wrong spot?19:16
torgomaticophuk: yes... there's some work going on to make that stuff reusable, but at the moment, swiftclient only has lower-level single-threaded operations19:16
torgomaticif you need concurrency, it's roll-your-own time19:17
ophuktorgomatic: gotcha, so I'm not going crazy:)19:17
torgomaticophuk: https://review.openstack.org/#/c/85453/19:17
ophukthought I was just missing something19:17
ophuktorgomatic: so it is being worked on, excellent. Thanks for your help!19:21
torgomaticophuk: no problem; if you can, you should try taking that patch for a test drive and see how you like the API and if it works for you, then leave feedback19:22
torgomaticthat'll help it land faster :)19:22
*** aswadr has quit IRC19:22
*** elambert has joined #openstack-swift19:30
*** bvandenh has quit IRC19:32
*** mmcardle has joined #openstack-swift19:37
*** tsg has quit IRC20:00
mattoliverauWell I'm going back to bed for the last hour or so of the night, bbl20:00
*** tdasilva_ has quit IRC20:00
*** tsg has joined #openstack-swift20:00
*** gvernik has quit IRC20:02
*** tusharsg has joined #openstack-swift20:05
*** gvernik has joined #openstack-swift20:07
*** tsg has quit IRC20:08
*** gvernik has left #openstack-swift20:15
*** elambert has quit IRC20:55
*** cpen has quit IRC20:58
*** tusharsg has quit IRC21:06
*** tsg has joined #openstack-swift21:06
*** mmcardle has quit IRC21:27
*** zaitcev has joined #openstack-swift21:36
*** ChanServ sets mode: +v zaitcev21:36
*** abhirc has joined #openstack-swift21:58
*** kevinc_ has quit IRC22:02
mattoliverauMorning all22:07
*** dmsimard is now known as dmsimard_away22:20
*** ophuk has quit IRC22:21
*** cpen has joined #openstack-swift22:25
*** Midnightmyth has quit IRC22:33
*** elambert has joined #openstack-swift22:38
notmynameblaaaaaaaaaaargh22:45
peluse_bless you22:46
notmynamewant to hear a funny story?22:46
peluse_sure22:46
notmynameso my probe tests on my SAIo have been borked22:47
peluse_still??22:47
notmynameand I've been trying to figure out why22:47
notmynameso through a lot of printf debugging and strace and netstat and etc etc22:47
notmynameI found that the error is that when trying to start up a server it was getting EADDRINUSE when trying to bind22:48
notmynamebut, here's the funny part, **there was nothing listening on that port**22:48
notmynamespooky22:48
peluse_still a mystery?22:48
notmynameno. here's what happened22:49
notmynamethe check_server call for the proxy does a head request to the account (actually this seems unecessary)22:49
notmynamebut anyway it was doing it22:49
notmynamewell, that left a half-open connection to the account server, so there was a socket in TIME WAIT on that port. so the new server couldn't bind22:50
notmynamehere's the fun part22:50
notmynameit turns out that we use the eventlet.listen convenience function to bind to the port22:50
notmynameand in eventlet 0.9.16 and on, it automatically sets SO_REUSEADDR22:51
notmynamebut, our requirements have 0.9.1522:51
notmynameand because of other stuff like this in the past, I've taken to running the earliest versions of our dependencies22:51
notmynameso, eventlet 0.9.15 doesn't do the sockopt22:51
notmynamebut you can't pass that in to eventlet.listen22:52
notmynameso, you have to set the sysctl net.ipv4.tcp_tw_recycle = 122:52
peluse_sounds like you've had fun22:52
notmynameso, the summary is: if you are using the oldest supported version of eventlet, and you haven't set the sysctl stuff to reuse timewait sockets, then probetests don't work22:52
notmynameand you'd never see it if you are running newer eventlet or had set the sysctl22:53
notmynamefun!22:53
peluse_I figured out my keystone swift issue too... nowhere near the excisting story though22:53
notmynameand thank you torgomatic for helping me finish debugging it22:53
notmynamewhat'd you find on the keystone stuff?22:54
peluse_I've been chasing 401 issues for a few days as I could sworn I had it working til a reboot... my keystone server had time drifted from my swift server (VMs) and auth_token.py was calling it expired...22:54
notmynameoh wow22:54
notmynamethat's another hard one to debug22:55
peluse_like no helpful log messages whatsoever, the messges I was getting had me chasing 6 differnt leads that had nothing to do with it :)22:55
peluse_but it was fun (sort of)22:55
peluse_now maybe tomorrow I can look at alcoles v3 patches - finally22:57
notmynameugh. just ran ./.probetests after resetting my codebase back to master. looks like some errors still. wonder what now22:57
*** cutforth has quit IRC22:58
peluse_check your date/time :)22:59
notmynameheh22:59
peluse_BTW, I did notice one failing probe test that I hit sometimes if I forget to unset http_proxy...23:00
mattoliveraunotmyname: is it time to up the requirements to 0.9.16 then :)23:07
torgomaticprecise is 0.9.16... maybe it's RHEL 6 that's a little older?23:08
torgomaticI think there's a distro with 0.9.15 and that's why it's what we use23:08
notmynametorgomatic: lucid IIRC23:09
torgomaticnotmyname: I thought lucid's was even way older than that... could be wrong though23:09
notmynametorgomatic: hmm, maybe so23:11
notmynamehttps://gist.github.com/notmyname/45e6a9e32822c8f98ddd23:12
notmynamewait. why do we have 0.9.15 as the requirement?23:18
notmynameprecise has 0.9.16 https://gist.github.com/notmyname/f48719565fbdc1ee136423:19
notmynameand lucid actually doesn't have it at all23:19
notmynamemaybe RHEL23:20
notmynameportante: zaitcev: ^^?23:20
zaitcevgimme a moment23:21
zaitcev[root@rhev-a24c-01 ~]# rpm -q python-eventlet23:22
zaitcevpython-eventlet-0.9.17-2.el6.noarch23:22
notmynamehmm23:22
*** dmsimard_away is now known as dmsimard23:22
zaitcevRHEL 6 GA might be older, but 6.4 is that23:22
torgomaticwell, time to bump it to 0.9.1623:34
*** dmsimard is now known as dmsimard_away23:37
openstackgerritJohn Dickinson proposed a change to openstack/swift: bumped the eventlet minimum version to 0.9.16  https://review.openstack.org/11081523:37
notmynametorgomatic: ^^23:37
notmynamenow let's see if we're allowed to do that (the global requirements has >=0.1323:40
notmynamelast issue with the probe tests is that I got unlucky with the randomness, and one of my policies with 3.25 replicas messed it up23:50
torgomaticoh, fractional replicas... such fun23:53
*** gyee has quit IRC23:55
*** morganfainberg_Z is now known as morganfainberg23:55
notmynamewoohoo! probetests actually passed23:56
notmynametorgomatic: ya, one of those "other things" I've tried to keep around to break things23:57
openstackgerritJohn Dickinson proposed a change to openstack/swift: Multithread optimization for object updater  https://review.openstack.org/7594123:59

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