Wednesday, 2014-02-05

portante1.8 is grizzly, 1.10 is havana (for swift at least, right notmyname?)00:00
themadcanudist1 proxy node, 32 workers on the same server00:00
themadcanudistthat seems to be fine00:00
notmynameportante: correct00:00
portantethemadcanudist: run00:00
portanteaway00:00
portante:)00:00
themadcanudistlol00:00
notmynameand a newer version of swift will still be compatible00:00
portantesorry, just kidding00:00
themadcanudisthehe, i know00:00
portanteso my guess is that the traffic of lo is high?00:01
portantecan I assume you have separate storage nodes?00:01
themadcanudistyep00:01
themadcanudistfor both00:01
themadcanudisthigh, busy, but like 30 mbits00:01
themadcanudist60 mbits at peack00:01
themadcanudiston lo00:02
themadcanudistbut still00:02
themadcanudistthat's not *crazy*00:02
notmynamethemadcanudist: so first off, yes. what you are seeing is known. the bad news is that there are 2 basic ways around it. 1) add more keystone servers (this is what mercado libre did). 2) don't use keystone. this is what most swift deployments do (because of what you see right now)00:02
notmyname(just getting that out there so everything else from now on can be good news for you)00:02
themadcanudisthmmm, add more keystone servers? as in workers that the proxy servers can contact in some round robin fashion?00:03
notmyname"don't use keystone" probably is a non-starter for you, so let's figure out a way to do more with what you have00:03
themadcanudistexactly ;) i must use it00:03
themadcanudistis this "fixed" in future versions?00:03
notmynamesort of. well, it's a little better. I don't know that "fixed" is the right word. keystone was able to use swift's memcache ring strategy starting in grizzly. that's a good improvement. anything else as to their indexing or whatever they are doing internally, I don't knwo00:04
themadcanudistok. the "multi-keyston server strategy" how does that look? how do the proxies utilize it?00:05
notmynamehmmm....that's a good question. /me is open to suggestions here00:05
notmynameunfortunately, according to instagram, the mercado libre guys are out salsa dancing right now ;-)00:06
*** rando has joined #openstack-swift00:06
*** mdonohoe has quit IRC00:08
*** shri has quit IRC00:18
openstackgerritJohn Dickinson proposed a change to openstack/swift: Added docs about the swift_source log field  https://review.openstack.org/7116300:23
notmynamegit st00:23
notmynameI don't suppose that works here00:24
torgomaticI can tell you about my local changes if you want00:24
torgomaticthey're mostly rubbish00:24
*** matsuhashi has joined #openstack-swift00:25
notmynamethemadcanudist: I'm not really sure where to tell you to look for optimizations in keystone, because I don't know where it's internal bottlenecks are. you may try asking ayoung in #openstack-dev, but he may simply tell you to upgrade (I'm hoping it can be something more helpful than that)00:26
* themadcanudist nods00:26
themadcanudistthank you!00:26
notmynamethemadcanudist: I want you to have a happy swift cluster. you're always free to ask questions in here about swift :-)00:27
*** shri has joined #openstack-swift00:27
jokke__notmyname: \o00:27
jokke__how are you? Keeping busy it seems00:27
notmynameswifterdarrell: https://review.openstack.org/71163 should address your comment on the log docs, and it adds some more info about swift_source00:27
notmynamejokke__: indeed (aren't we all?) :-)00:28
themadcanudisti *very much* appreciate it!00:28
*** jokke__ is now known as jokke_00:30
notmynamethemadcanudist: sorry you got those responses :-(00:30
themadcanudistno problem00:31
themadcanudistthey're good responses00:31
themadcanudistsometimes things are just contingent00:31
themadcanudist=)00:31
*** Dieterbe has joined #openstack-swift00:34
notmynameDieterbe: you aren't using keystone are you?00:36
notmynameon your swift cluster00:36
Dieterberight00:36
Dieterbetempauth00:36
notmynameah ok00:36
Dieterbewhy?00:37
notmynameDieterbe: right before you came in, themadcanudist was asking about some scaling issues with keystone in front of swift00:37
Dieterbeha. i've had my fair share of issues with swift, but nothing keystone related :]00:38
Dieterbeafk*00:38
notmynamethemadcanudist: if you end up upgrading swift too, then you can take a look at https://swiftstack.com/blog/2013/12/20/upgrade-openstack-swift-no-downtime/00:39
themadcanudistwonderful!00:39
notmynameI'm out for most of the evening. later, everyone00:41
*** mkollaro has quit IRC00:41
jokke_take care00:41
themadcanudistpeac00:42
*** jokke_ has quit IRC00:43
*** jokke_ has joined #openstack-swift00:44
*** sungju has joined #openstack-swift00:47
*** jokke_ has quit IRC00:47
*** jokke_ has joined #openstack-swift00:48
openstackgerritSteve Kowalik proposed a change to openstack/swift: Drop nose, switching to testtools and testr  https://review.openstack.org/6501400:55
*** nosnos has joined #openstack-swift00:57
*** nosnos has quit IRC01:01
*** nosnos has joined #openstack-swift01:01
*** dmorita has joined #openstack-swift01:26
*** themadcanudist has left #openstack-swift01:28
*** shri has quit IRC01:42
openstackgerritA change was merged to openstack/swift: Let swift-object-info skip etag verification  https://review.openstack.org/6729601:55
*** jasondotstar has joined #openstack-swift02:22
zaitcevMother of god02:53
zaitcevportante: I started writing tests for the code that I copied verbatim from Gluster and its FULL OF BUGS.02:53
portantezaitcev: gluster is full of bugs?03:11
portanteor i should say the gluster-swift code is full of bugs?03:11
portantecan you say more?03:11
zaitcevportante: no, just the UFO03:11
portanteso what kind of bugs are you seeing?03:12
zaitcevAlthough truth to be told Swift Devguide is kind of undewhelming, too.03:12
portanteswift devguide in the gluster-swift tree?03:12
zaitcevportante: the first was the limit. You know, GET /v1/a/c?limit=303:12
portanteokay, and does that fail in gluster-swift unmodified?03:13
zaitcevif c/ only contains 2 objects, the filter_limit() tracebacks with index outside of array03:13
portanteperhaps we should discuss this in the gluster-swift channel instead?03:13
zaitcevWell. I need to refresh my git trees for UFO, see maybe Kaleb or whoever already had all it patched up.03:14
portantewhat is the tree you are using?03:14
portantehttps://github.com/gluster/gluster-swift.git03:15
portante?03:15
zaitcevurl = git://github.com/gluster/gluster-swift.git03:15
portantenobody uses the UFO name anymore, it has no meaning, btw03:15
portanteso did you run all the functional tests in your tree?03:16
portanteor is this something that is not tested?03:16
portanteand can we switch to the #gluster-swift channel in freenode so the folks in Bangalore can join the discussion?03:17
portantezaitcev?03:17
zaitcevNo, I did not run functional tests.03:17
zaitcevNot against the in-memory back-ends, I mean.03:17
portantezaitcev: can we talk about the base gluster-swift issues in the #gluster-swift channel and the in-memory ones here?03:18
zaitcevportante: sure. But I'll probably need to take it all back. << >>. I'm looking at the semi-recent tree and the code is nothing like what I picked up.03:19
zaitcevportante: My point was that your idea to have tests was brilliant.03:19
portantethanks03:22
portantelet's hope it makes a material difference03:22
*** themadcanudist has joined #openstack-swift03:50
openstackgerritPete Zaitcev proposed a change to openstack/swift: Pluggable Back-ends for account and container servers  https://review.openstack.org/4771304:15
*** jd__ has quit IRC04:21
*** jd__ has joined #openstack-swift04:22
*** byeager has joined #openstack-swift04:48
*** marcusvrn has quit IRC04:48
*** ppai has joined #openstack-swift04:54
*** nshaikh has joined #openstack-swift05:16
*** igor__ has joined #openstack-swift05:37
*** byeager has quit IRC05:58
*** krast has joined #openstack-swift06:14
*** igor__ has quit IRC06:21
*** jasondotstar has quit IRC06:22
*** mmcardle has joined #openstack-swift06:22
*** zaitcev has quit IRC06:23
*** mmcardle has quit IRC06:26
*** nshaikh has quit IRC06:27
*** odyssey4me has joined #openstack-swift06:39
*** SkyRocknRoll__ has quit IRC07:55
*** haomaiwa_ has quit IRC08:28
*** haomaiwang has joined #openstack-swift08:28
*** haomai___ has joined #openstack-swift08:32
*** haomaiwang has quit IRC08:36
*** krtaylor has quit IRC08:47
*** mlipchuk has joined #openstack-swift08:49
*** krtaylor has joined #openstack-swift08:49
openstackgerritChristian Schwede proposed a change to openstack/swift: Add tests for swift-ring-builder  https://review.openstack.org/7110608:52
*** matsuhashi has quit IRC08:54
*** krtaylor has quit IRC08:55
*** matsuhashi has joined #openstack-swift08:55
*** nacim has joined #openstack-swift08:55
*** krtaylor has joined #openstack-swift08:56
*** psharma has joined #openstack-swift08:57
*** mkollaro has joined #openstack-swift09:05
*** fbo_away is now known as fbo09:13
*** thomaschaaf has joined #openstack-swift09:19
*** odyssey4me has quit IRC09:25
*** mmcardle has joined #openstack-swift09:31
thomaschaafHey I am running 1.10.0 on all my servers (5 total) and the network traffic between them being mostly idle is almost 10 MB/s how could I debug this? Is this expected behaviour?09:32
thomaschaaf10 MB/s per server09:32
thomaschaafthis is the recon output: https://gist.github.com/thomaschaaf/d8367a1ad8865c634a4909:33
*** odyssey4me has joined #openstack-swift09:34
*** grapsus_1 has quit IRC09:52
*** grapsus_ has joined #openstack-swift09:54
*** xga has joined #openstack-swift09:57
*** themadcanudist has quit IRC10:00
*** jasondotstar has joined #openstack-swift10:00
*** sphoorti has joined #openstack-swift10:08
sphoortiI have swift-keystone running on a vm.  I am trying to run this command "swift -v -V 2.0 -A http://192.168.1.16:5000/v2.0/ -U admin -K password stat" but i get the following error : "Endpoint for object-store not found - have you specified a region?"  . This command however works fine locally from the vm. What possibly could be going wrong?10:15
saurabh_sphoorti: execute 'keystone catalog' is there any entry for Service: object-store10:18
openstackgerritChmouel Boudjnah proposed a change to openstack/python-swiftclient: Add missing backslash.  https://review.openstack.org/7122410:19
chmouelthe easiest commit to review ever ^10:19
sphoortisaurabh_: i see only service :- identity10:21
sphoortiand object store too saschpe_10:22
sphoortisaurabh_:10:22
openstackgerritChristian Schwede proposed a change to openstack/swift: Add tests for swift-ring-builder  https://review.openstack.org/7110610:23
saurabh_sphoorti:  execute 'keystone endpoint-list' is there any entry for object-stor 's IP and port10:24
sphoortisaurabh_: I do see Auth urls10:25
saurabh_sphoorti: any entry for swift endpoint10:26
saurabh_?10:26
saurabh_like http://IP:808010:26
saurabh_v1/AUTH_$(tenant_id)s10:26
sphoortiyes saurabh_10:27
openstackgerritChristian Schwede proposed a change to openstack/swift: Add tests for swift-ring-builder  https://review.openstack.org/7110610:31
sphoortisaurabh_: ?10:41
*** nosnos has quit IRC10:53
*** saurabh_ has quit IRC10:59
*** jjw has joined #openstack-swift11:00
*** jasondotstar has quit IRC11:00
*** jjw is now known as Guest9607911:01
*** ben_roeder has joined #openstack-swift11:02
*** joeljwright has joined #openstack-swift11:07
*** saurabh_ has joined #openstack-swift11:10
*** saurabh_ has joined #openstack-swift11:10
*** jasondotstar has joined #openstack-swift11:13
chmouelhahah the one char commit failed11:13
openstackgerritChmouel Boudjnah proposed a change to openstack/python-swiftclient: Add missing backslash.  https://review.openstack.org/7122411:15
*** ben_roeder has quit IRC11:27
*** mmcardle has quit IRC11:32
*** mmcardle has joined #openstack-swift11:36
*** ben_roeder has joined #openstack-swift11:48
*** dmorita has quit IRC11:55
*** igor_ has joined #openstack-swift11:57
*** ppai has quit IRC12:04
*** ben_roeder has quit IRC12:08
*** mkollaro has quit IRC12:11
*** bada has joined #openstack-swift12:22
*** bada_ has quit IRC12:24
*** bada_ has joined #openstack-swift12:30
*** bada has quit IRC12:31
*** jasondotstar has quit IRC12:41
*** saurabh_ has quit IRC12:44
*** mkerrin has joined #openstack-swift12:44
*** saurabh_ has joined #openstack-swift12:44
*** saurabh_ has joined #openstack-swift12:44
*** mmcardle has quit IRC12:50
*** Guest96079 has quit IRC12:51
*** xga has quit IRC13:02
*** thomaschaaf has quit IRC13:03
*** ppai has joined #openstack-swift13:04
*** xga has joined #openstack-swift13:08
*** ppai has quit IRC13:09
*** Trixboxer has joined #openstack-swift13:13
*** ppai has joined #openstack-swift13:26
*** igor_ has quit IRC13:27
*** mkollaro has joined #openstack-swift13:27
*** igor_ has joined #openstack-swift13:28
*** mmcardle has joined #openstack-swift13:29
openstackgerritChristian Schwede proposed a change to openstack/swift: Add tests for swift-ring-builder  https://review.openstack.org/7110613:31
*** igor_ has quit IRC13:33
*** ppai has quit IRC13:46
*** zigo_ is now known as zigo13:50
*** igor_ has joined #openstack-swift13:58
*** igor__ has joined #openstack-swift14:00
*** igor_ has quit IRC14:03
*** sphoorti has quit IRC14:05
*** jasondotstar has joined #openstack-swift14:14
*** tongli has joined #openstack-swift14:16
*** ccorrigan has joined #openstack-swift14:18
ccorrigannotmyname: ot - eventual consistency explained - - http://www.youtube.com/watch?v=s6EaoPMANQM14:23
*** psharma has quit IRC14:31
joeljwrightHi, I'm trying to develop a middleware for swift that needs to read the entire body of a PUT request14:39
joeljwrightobviously I want to avoid reading (and buffering) the wsgi.input multiple times14:40
joeljwrightso is there some best practice for doing this?14:40
joeljwrightcurrently I'm wrapping the wsgi.input and performing my calculations when the proxy-server performs its reads, and using a WSGIContext to catch the response and perform actions on the result14:42
joeljwrightany advice would be greatly appreciated14:42
*** zaitcev has joined #openstack-swift14:48
*** ChanServ sets mode: +v zaitcev14:49
*** mlipchuk has quit IRC14:51
*** xga has quit IRC15:03
*** jergerber has joined #openstack-swift15:09
*** jergerber has quit IRC15:12
*** mlipchuk has joined #openstack-swift15:12
*** nacim_ has joined #openstack-swift15:13
*** nacim has quit IRC15:14
*** matsuhashi has quit IRC15:17
*** matsuhashi has joined #openstack-swift15:18
*** bvandenh has joined #openstack-swift15:19
*** peluse has quit IRC15:22
*** peluse has joined #openstack-swift15:22
*** xga has joined #openstack-swift15:26
*** byeager has joined #openstack-swift15:31
notmynamejoeljwright: do you need to read the whole body before you can pass it on to the underlying app? or can you simply do your calculation as you stream it through the middleware?15:33
*** matsuhashi has quit IRC15:34
joeljwrightI only want to add a header, I don't want to allow/deny the request15:35
dfgjoeljwright: to me sounds like you're on the right track. you can look at swift/common/middleware/proxy_logging.py as an example if you want15:36
notmynamejoeljwright: do you have to add the header based on the full contents of the body?15:37
notmynamejoeljwright: dfg: proxy_logging is a good place to look, especially to take advantage of eventlet posthooks for callbacks. but for a very simply middleware example that adds a header, take a look at catch_errors15:38
joeljwrightnotmyname: yes, I need to read the full content - I'm just calculating SHA1 and CRC32 atm to add them as headers15:38
joeljwrightdfg: thanks for the hint, I'll take a look15:40
notmynamejoeljwright: so that means you'll have to read the full body in the middleware, reset the stream (ie you'll have it spooled), then send it on with your new headers. that seems not good15:42
dfgisn't he just setting headers on the response? just like proxy_logging is?15:43
notmynameI thought it was being saved with the object15:45
joeljwrightactually, I'm adding the headers afterwards with a separate POST15:45
notmynameso what is your middleware doing?15:46
dfgoh- turn post_as_copy off :)15:46
joeljwrightI'm wrapping the wsgi.input so that the sha1 and crc32 are calculated ad the proxy server does its reads15:47
notmynamereads from what? the client or the cluster?15:47
joeljwrightand using a WSGIContext to get the final result of the put15:47
notmynameand what do you do with the hashes once you have them?15:48
joeljwrightan extra post from within the middleware to add the headers15:48
joeljwrightI got the idea from the undelete middleware here https://github.com/swiftstack/swift_undelete15:49
joeljwrightusing a wsgicontext to keep hold of access to the wrapped wsgi.input and intercept the final response form the put15:49
joeljwrightonce the put has succeeded I know the data has all been read and the checksums are calculated, so I can make another request before returning the result of the put to the client15:50
joeljwrightthe second request is a post to add the headers to the object15:50
notmynamedfg: any chance you'll be working on unifying the POST data flows into just the fast-POST version, like we talked about last fall in Austin?15:51
notmynamejoeljwright: ya, like dfg said, you'll want to turn off post_as_copy15:52
*** pscheie has quit IRC15:54
notmynamejoeljwright: just curious, but why are you calculating the hashes server side? what are they used for and why does the client not have them?15:56
*** mmcardle1 has joined #openstack-swift15:56
*** igor__ has quit IRC15:57
joeljwrightnotmyname: we're generally interested in having the hashes, but don't have control over the clients used to upload the data15:58
*** mmcardle has quit IRC15:59
joeljwrightwe've been asked if we can add the data by some clients, but they still want to continue using apps like cloudberry/cyberduck to upload16:00
*** mmcardle has joined #openstack-swift16:01
dfgnotmyname: like- me doing all the typing and stuff? no prob not :) we have a bunch of other stuff to do- somebody should do it though...16:01
joeljwrightto be honest, this was as much an investigation of writing middlewares for me as it was a requirement16:01
notmynameI wonder if having a DiskFile to calculate and save those would be more efficient (just thinking aloud; paging portante). you'd do the math on each replica, but you'd also have it spread out to every storage node without having to coordinate a 2nd request from the proxy16:01
*** mmcardle1 has quit IRC16:01
*** ChanServ sets mode: +v chmouel16:01
notmynamedfg: ok. just curious16:02
notmynamedfg: and ya. somebody should do all that typing ;-)16:02
*** igor_ has joined #openstack-swift16:03
*** mkollaro has quit IRC16:07
*** mmcardle has quit IRC16:08
*** igor_ has quit IRC16:08
*** mmcardle has joined #openstack-swift16:10
*** byeager has quit IRC16:13
joeljwrightnotmyname: I'm not sure I understand that last suggestion16:15
*** mmcardle has quit IRC16:20
openstackgerritChristian Schwede proposed a change to openstack/swift: Add tests for swift-ring-builder  https://review.openstack.org/7110616:20
*** jasondotstar has quit IRC16:21
zaitcevpushing the calcs out to DiskFile means that it's redundant (3x) but then it unloads proxy which is what we want most of the time16:25
joeljwrightI think I'm starting to understand the DiskFile suggestion16:26
joeljwrightthanks for all the help, I'll have a dig about in the code16:27
chmouelcschwede: about the test ringbuilder tests, wouldn't that work to just create the tempfile in create_sample_ring() directly?16:31
*** jasondotstar has joined #openstack-swift16:31
*** mmcardle has joined #openstack-swift16:32
cschwedechmouel: well, than we need to collect all the filenames to delete them in tearDown i think?16:33
chmouelcschwede: ah yeah right16:33
chmouelcschwede: it did come to mind at certain point and i'm not sure why i thought it may have been a good idea :)16:33
cschwedechmouel: well there are two ways to do it, and i think both are ok :)16:33
cschwedechmouel: i can change that also if you prefer ;-)16:34
chmouelcschwede: ah no nervermind, i don't want to nitpick :)16:34
*** tdasilva has left #openstack-swift16:43
*** bvandenh has quit IRC16:46
*** nacim_ has quit IRC16:46
notmynametorgomatic: are dynamic large objects setting the swift_source for any of the subrequests generated?16:50
*** gyee has joined #openstack-swift16:56
*** hurricanerix has joined #openstack-swift16:59
*** tdasilva has joined #openstack-swift17:04
*** igor_ has joined #openstack-swift17:04
gholtswifterdarrell: All the error log lines with no txn: are probably because of that bug you filed on background coroutines, right?17:05
gholtI mean, it's because you filed the bug, but due do that bug, and... oh nm17:05
*** CoilDomain has joined #openstack-swift17:07
*** CoilDomain has left #openstack-swift17:07
*** igor_ has quit IRC17:09
brianclinemorning -- is 1.12.0 currently planned to be the release to coincide with the 2014.1/Icehouse release prior to summit?17:10
brianclinesorry, 1.13.017:10
portantenotmyname: what's up, something about using DiskFile to calculate hashes, it does that on PUT already, not sure I followed the above well17:20
*** odyssey4me2 has joined #openstack-swift17:23
*** odyssey4me has quit IRC17:24
*** odyssey4me2 is now known as odyssey4me17:24
*** mlipchuk has quit IRC17:37
torgomaticnotmyname: I have no idea, but I'd guess not17:44
torgomaticif the original code did, then mine will too, but otherwise... maybe?17:44
*** bsdkurt has joined #openstack-swift17:45
*** jasondotstar has quit IRC17:46
notmynameportante: joeljwright wants to compute some extra stuff on a write and save it with the data. seems that doing that in a diskfile could be an interesting avenue to explore17:51
notmynametorgomatic: I didn't see anything in the DLO patch, but I wanted to ask in case I missed something17:51
notmynametorgomatic: it probably should, but I'm noticing it now because I submitted a patch yesterday to document all that17:51
notmynametorgomatic: but I wouldn't (won't) hold up your current patch because of that. just something that should probably be added17:52
portantenotmyname: yes17:54
notmynameportante: and I have the ulterior motive of pushing for that kind of functionality since I think that will result in better config designation of a particular DiskFile (like clayg's pluggable daemons method) ;-)17:55
portante=)17:57
swifterdarrellgholt: haha!  I'm not sure... that could be a perverse side-effect of letting those laggard greenthreads "finish".  I didn't specifically investigate that17:57
* portante thinks, "smile and wave boys, just smile and wave."17:57
*** xga has quit IRC17:57
portanteo/17:58
* portante forgot the wave17:58
*** shri has joined #openstack-swift17:59
swifterdarrellgholt: I went back and checked one of my smoking-gun log-grabs and sure enough, the final log message from the laggard greenthread, which complains about hitting Timeout (10s) even though that 3rd req cleared the object-server in ~1.8s, does not have a txid18:03
*** gyee has quit IRC18:05
*** jasondotstar has joined #openstack-swift18:05
*** kris_h has joined #openstack-swift18:05
*** igor__ has joined #openstack-swift18:05
*** kris_h has quit IRC18:05
*** kris_h has joined #openstack-swift18:06
gholtswifterdarrell: Oh good, I was hoping it was that and not something more sinister.18:07
*** igor__ has quit IRC18:10
*** jokke__ has joined #openstack-swift18:11
*** jokke__ has quit IRC18:12
*** CoilDomain has joined #openstack-swift18:14
*** gvernik has joined #openstack-swift18:28
*** CoilDomain has left #openstack-swift18:31
*** bvandenh has joined #openstack-swift18:31
*** zul has quit IRC18:33
*** zul has joined #openstack-swift18:37
*** lpabon has joined #openstack-swift18:47
notmynameswift team meeting in 10 minutes in #openstack-swift https://wiki.openstack.org/wiki/Meetings/Swift18:50
notmynameer..in #openstack-meeting18:50
*** bvandenh has quit IRC18:51
*** mmcardle has quit IRC18:51
*** mmcardle1 has joined #openstack-swift18:51
*** joeljwright has quit IRC18:53
*** joeljwright has joined #openstack-swift18:53
notmynamepeluse: torgomatic: portante: I want to talk about the storage policy/EC status first up in the meeting18:53
peluseOK18:55
portantenotmyname: okay18:55
notmynamecreiht: did you add the item to the agenda about the asyncio lib for python2? or maybe portante?18:56
portanteI did not add it, but I think it is worth talking about18:56
notmynameya, absolutely. it was listed on the agenda under the swiftclient topic. I think that was wrong and moved it under creiht's topic of py3k support18:57
*** dirk has joined #openstack-swift18:57
portantek18:57
notmynamelooks like we have quite a bit (potentially) to cover today18:58
notmynameswift meeting time in #openstack-meeting19:00
*** tgohad has joined #openstack-swift19:02
*** bvandenh has joined #openstack-swift19:05
*** igor__ has joined #openstack-swift19:06
*** igor__ has quit IRC19:10
*** mfactor has joined #openstack-swift19:17
*** byeager has joined #openstack-swift19:26
*** hurrican_ has joined #openstack-swift19:28
*** hurrican_ has quit IRC19:29
*** mmcardle1 has quit IRC19:29
*** hurricanerix has quit IRC19:31
*** igor___ has joined #openstack-swift19:32
*** hurricanerix has joined #openstack-swift19:35
*** igor___ has quit IRC19:37
*** odyssey4me has quit IRC19:40
*** mfactor has quit IRC19:41
*** mfactor has joined #openstack-swift19:42
openstackgerritTristan Cacqueray proposed a change to openstack/python-swiftclient: Port to python-requests  https://review.openstack.org/6918719:43
portanteclayg: I should have put a smiley face on the end of that /me comment19:47
claygportante: i could tell you were kidding around - it was funny19:50
portante:)19:51
*** davidhadas has joined #openstack-swift19:56
*** joeljwright has quit IRC19:59
notmynamebah. time limits20:01
portanteclayg: I am thinking that a core dev sponsor will help with folks who are not cores to get their patches considered20:01
portanteso a core dev could review it sufficiently to help notmyname prioritize it20:01
chmoueli think we need hyperthreading on sam20:01
pelusegood meeting today notmyname20:01
*** gvernik has quit IRC20:02
claygyeah I mean I think of it as a formalization of jump in IRC and be like "hey yeah so, i've been thinking this was a good idea -> link to review"20:02
portantetorgomatic: how about we give you more machines?20:02
notmynamepeluse: the meetings are as good as the participation. thanks for taking ec and storage policies updates :-)20:02
torgomaticportante: coffee machines?20:02
portante:)20:02
portanteyes20:02
portante!20:02
portantelol20:02
notmynameactually, I''m working on getting torgomatic some more machines (not for coffee) :-)20:02
*** gvernik_ has joined #openstack-swift20:03
claygI think we should do meetings every week (notmyname is really the only one that has to ALL of them) - and he can dole out "sponsers" to patches that no-one has looked at20:03
notmynameI got a pile of hard drives to put in them yesterday20:03
*** igor___ has joined #openstack-swift20:03
torgomaticI don't think the sponsorship thing is particularly official right now; it's just an emergent behavior20:03
zaitcevIt was v.informative meeting today. I did not know about gevent.20:03
notmynametorgomatic: ya20:03
brianclineare there not folks currently who focus primarily on specific parts of swift? or is it currently a free-for-all? that may be part of the problem20:04
notmynameclayg: the same time slot on the other weeks is currently taken by "Neutron Advanced Services' Common requirements team meeting"20:04
brianclinecore folks, that is20:04
portanteclayg: for example, I'd like to be able to say that before others spend time on a patch, it is verified to pass unit/func/probe and all tox stuff independent of jenkins20:04
torgomaticif some other core reviewer has looked at a patch, then it's probably easier to review for me because it'll at least have had some basic sanity checks20:04
claygisn't there an openstack-meeting-alt?20:04
notmynamebriancline: although there is some degree of specialization, there isn't too much siloing in swift20:04
torgomaticand if everyone observes the same thing, then we get the current situation where patches take a long time for the first +2, and then ZOOM they're done20:04
*** dirk has quit IRC20:04
notmynameclayg: and now also #openstack-meeting-320:04
*** igor____ has joined #openstack-swift20:05
torgomaticwait, so meeting, meeting-alt, and meeting-3? Can we have meeting-delta next?20:05
brianclineI've heard #whatdayisit is also available20:05
notmynameclayg: oh, wait, that other meeting is in -alt20:05
claygx-temp-url-key and x-temp-url-key-2 - these things happen man20:05
brianclinenotmyname: well, I'd hate to think of it as siloing, as that tends to have a negative connotation20:06
torgomaticclayg: yeah, but I'm not adding temp-url-key-three and -key-cuatro next :)20:06
claygyes!20:06
notmynamebriancline: ya, I know.20:06
* notmyname will look into moving to a weekly meeting20:07
*** igor___ has quit IRC20:07
chmoueltorgomatic: :)20:08
notmyname /lunch20:09
*** hurricanerix has quit IRC20:09
chmoueldinner time!20:09
brianclineas a somewhat separate topic, to be honest I've seen non-core folks with legitimate concerns over patches (echoing what I would have written in some cases) that get hurried in and merged because of specific attention from core folks20:09
brianclinecertainly not the case for the majority20:09
brianclinejust another thing to consider as we think about this20:09
brianclineperhaps it's not *because* of core attention, but it gives the appearance that voices get lost in the shuffle or in the dash to get something implemented20:12
*** kragniz has quit IRC20:16
zaitcevBah, I think the only time it went pear shaped was when Alex busted DB cursors and thus Havana GA went out with the "DB Locked" tracebacks under any decent load.20:17
zaitcevOtherwise it's just the SJF that any printer spooler does.20:17
zaitcevI learned to be philosophical about it while sitting on 1 patch for a few months.20:18
*** gvernik_ has quit IRC20:18
brianclinejust a thought. luckily we can be smarter than the print spooler ;)20:21
*** mfactor has quit IRC20:21
*** hurricanerix has joined #openstack-swift20:28
*** joeljwright has joined #openstack-swift20:30
*** dirk has joined #openstack-swift20:30
portantebriancline: core devs are human beings, and have preferences and leanings, just like the folks submitting patches20:31
portanteit is the nature of the community20:31
portanteno community is fair20:32
portantewe are fooling ourselves to think that we are any different20:32
portantewe just need to acknowledge that, and point things out, be as open as possible, and available for folks to make their case for their patches20:32
portantenotmyname, clayg, torgomatic, chmouel, zaitcev, briancline: not that I don't see anybody else in #openstack-meeting20:34
* zaitcev is very confused by the double negative20:37
*** joeljwright has quit IRC20:38
torgomaticyeah, it's true... if it's a patch I have a use case for, I'm much (much!) more likely to help it along than if it's something I'm indifferent to20:41
glangesome patches address production issues and thus get more immediate attention20:44
*** _bluev has joined #openstack-swift20:45
*** _bluev has quit IRC20:46
*** shri has quit IRC20:56
*** gvernik_ has joined #openstack-swift21:02
pelusezaitcev:  wow, that patch you mentioed is a monster :)  I will indeed take a look for what its worth though (there are some areas there I'm not super familiar with)21:11
zaitcevpeluse: I started by splitting it, but then some complained that it's hard to review without seeing how all parts fit together.21:12
peluseyup, I can see that view for sure21:12
*** ben_roeder has joined #openstack-swift21:15
*** tongli has quit IRC21:18
*** _bluev has joined #openstack-swift21:19
*** bvandenh has quit IRC21:21
*** kris_h has quit IRC21:30
*** kris_h has joined #openstack-swift21:30
*** kris_h has quit IRC21:31
*** joeljwright has joined #openstack-swift21:35
*** joeljwright has quit IRC21:39
*** lpabon has quit IRC21:40
*** wer has joined #openstack-swift21:43
notmynamechmouel: are you seeing https://twitter.com/chmouel/status/431178123649249280 in swift? if so, can you document some examples for me (maybe send privately)? I don't want this to happen in swift21:44
* notmyname is worried about it21:44
*** ben_roeder has quit IRC21:48
*** _bluev has quit IRC21:50
*** _bluev has joined #openstack-swift21:52
*** jasondotstar has quit IRC21:56
*** jasondotstar has joined #openstack-swift21:57
*** gvernik_ has quit IRC21:58
*** nacim has joined #openstack-swift22:03
*** nacim has quit IRC22:07
*** nacim has joined #openstack-swift22:08
*** nacim has quit IRC22:12
*** tgohad has quit IRC22:12
*** dirk has quit IRC22:15
openstackgerritA change was merged to openstack/swift-bench: Sync with global requirements  https://review.openstack.org/6706422:16
*** Trixboxer has quit IRC22:23
*** jergerber has joined #openstack-swift22:25
*** shri has joined #openstack-swift22:25
creihtnotmyname: sorry I'm on vacation this week... chmouel added it for me22:25
notmynamecreiht: ah, ok. have fun on your vacation :-)22:30
creihthehe22:35
creihtfwiw, I also think there is a lot more to the question of python3 support than just eventlet22:35
creihtbut maybe we should just have a session about it at the summit22:36
creihtor we just choose to port to go instead ;)22:36
*** joeljwright has joined #openstack-swift22:36
*** joeljwright has quit IRC22:40
chmouelnotmyname: oh not at all22:40
chmoueli think we are doing a very good job about being relax22:41
portantecreiht: there was some talk about possibly switching to gevent first, and then ride that to py322:41
creihtportante: well that assumes that gevent ever actually gets to py3 compat22:42
creihtit has been stalled for quite a while22:42
creihtat least the last time that I checked22:42
creihtin my mind, the biggest concern is are we shooting for py2.x and 3 compat, or just moving to 322:42
chmouelcreiht: this one? https://github.com/fantix/gevent22:42
creihtshooting for both is very hairy in my estimation22:42
chmouelcreiht: what do you think about asyncio/tulip?22:43
portantemy take is that we can't leap to py3 and support existing distributions22:43
portantewe need a transition period22:43
* creiht needs to get back to vacationing22:44
creihtbut I'll submit a proposal for the next summit22:44
portantegood for you, and the creepers22:44
chmouelcreiht: proposals for python3 ?22:44
creihtbecause I think it warrants a much deeper discussion22:44
creihtchmouel: yeah22:44
creihtI also would like to have a focused plan rather than these drive by python3 patches that may or may not help down the road22:45
chmouelit would be a nice thing to have both but I think what victor is trying to do is to easy the migration with the trollius project22:45
creihtchmouel: yeah I read some of that, but I'm also cautious22:45
portantecreiht: agreed22:45
creihtchmouel: last I heard quido talk about tulip, is that it would never work on python 2.x22:45
portanteit is still going to be a fair amount of work to do that transition22:46
chmouelcreiht: ah he changed his opinions on it22:46
creihtand having a different syntax isn't really compat22:46
chmouelhe was endorsing it in his talks22:46
creihtchmouel: ahh well that is good to know22:46
chmoueland may even plan to make it easier for p python222:46
* creiht goes back to vacation now :)22:46
chmouelah22:46
chmoueli go to sleep :)22:46
creihtportante: oh, I have moved on to bigger and better things :)22:47
chmouelcreiht: thanks for jumping in22:47
creihtlike warhammer 40k figures :)22:47
creihtoh but the bigger issue will be all the unicode handling and changing to bytestreams22:47
creihtthat seems to be the most difficult to me22:47
creihtor at a minimum, the least understood22:47
*** jasondotstar has quit IRC22:48
chmouelyeah that part is going to be a PITA22:48
portantecreiht: if you have creepers walking down the streets of Austin, we are NOT going to have the hackathon there!22:49
pelusecreepers?22:51
creihtlol22:51
creihthttp://minecraft.gamepedia.com/Creeper22:51
creihtpeluse: -^22:51
peluseahhh22:51
portanteand yes, I am a scaredy cat22:51
openstackgerritGreg Lange proposed a change to openstack/swift: Fix a couple ifs in account quota middleware.  https://review.openstack.org/7140522:52
*** _bluev has quit IRC22:54
openstackgerritA change was merged to openstack/swift: Move all DLO functionality to middleware  https://review.openstack.org/6332622:59
openstackgerritZack Feldstein proposed a change to openstack/swift: Implements checking ring file existence on recon  https://review.openstack.org/7140822:59
*** _bluev has joined #openstack-swift23:00
openstackgerritZack Feldstein proposed a change to openstack/swift: Implements checking ring file existence on recon  https://review.openstack.org/7140823:03
*** byeager has quit IRC23:07
*** zackf has joined #openstack-swift23:13
*** byeager has joined #openstack-swift23:13
openstackgerritSamuel Merritt proposed a change to openstack/swift: Make ranges_for_length return (first, last) pairs  https://review.openstack.org/6332723:15
*** byeager has quit IRC23:19
*** zackf has quit IRC23:19
openstackgerritSamuel Merritt proposed a change to openstack/swift: Ensure swift.source is set for DLO/SLO requests  https://review.openstack.org/7141523:24
*** kragniz has joined #openstack-swift23:31
*** joeljwright has joined #openstack-swift23:37
*** joeljwright has quit IRC23:42
claygso setuptools entry_points for console_scripts were "too slow" -> https://github.com/openstack-dev/pbr/commit/8e58c2fa58fd1aa6f9985dcb4e210508a73e1df723:46

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