Thursday, 2015-06-04

*** wbhuber has quit IRC00:01
openstackgerritHisashi Osanai proposed openstack/swift: Add metadata size tests on the border  https://review.openstack.org/18748900:02
*** jkugel has joined #openstack-swift00:17
*** gyee has quit IRC00:23
portanteswifterdarrell: yes, I can appreciate those goals.  I'd be interested to know how that turns out.00:39
*** breitz1 has quit IRC00:45
*** breitz has joined #openstack-swift00:45
notmynamehello00:59
notmynamesorry about the last minute meeting canceling. thanks clayg for telling everyone00:59
mattoliveraunotmyname: No probs, looks like your been busy bug triaging01:09
notmynamejust this morning before my laptop ran out of juice01:09
notmynameI hope that will become a normal thing, though. depends how much I'll get bothered at the office, though ;-)01:10
notmynamenew plan: go to conferences so I have some uninterrupted time to work ;-)01:10
mattoliverauLol01:11
mattoliverauGood plan01:11
notmynamemattoliverau: speaking of which, LCA CFP opened up!01:13
*** openstack has joined #openstack-swift01:23
*** openstack has joined #openstack-swift01:38
mattoliveraunotmyname: have fun01:45
*** openstack has quit IRC01:52
*** openstack has joined #openstack-swift01:54
*** blmartin_ has quit IRC01:55
*** wbhuber has joined #openstack-swift02:05
*** kota_ has joined #openstack-swift02:08
*** bill_az has quit IRC02:11
*** jkugel has left #openstack-swift02:16
wbhuberkota_: do you happen to have status for this bug: https://bugs.launchpad.net/swift/+bug/145769102:20
openstackLaunchpad bug 1457691 in OpenStack Object Storage (swift) "Insufficient Fragments occurred on EC GET object" [Undecided,New]02:20
wbhuberkota_: if not i can go take a crack at it02:21
kota_wbhuber: hi, wait a second02:22
wbhuberkota_: absolutely.02:23
kota_wbhuber: I didn't start to work about it yet. If you could take it, it seems good to me :)02:24
wbhuberkota_: okay, i might need some guidance on the problem recreation though.02:27
kota_wbhuber: Thanks! If you need a help, please feel free to ask me ;)02:28
wbhuberkota_: ok, i will leave a comment in the bug report that i'm starting investigation on it02:30
*** zaitcev has quit IRC03:12
*** wbhuber has quit IRC03:22
*** asettle-afk is now known as asettle03:45
*** EmilienM|off has quit IRC03:55
*** clyps___1 has quit IRC03:55
*** ppai has joined #openstack-swift03:58
*** EmilienM has joined #openstack-swift04:00
*** clyps___1 has joined #openstack-swift04:02
*** sc has quit IRC04:20
*** mordred has quit IRC04:21
*** sc has joined #openstack-swift04:23
*** mordred has joined #openstack-swift04:25
*** sorrison_laptop has quit IRC04:29
*** ChanServ sets mode: +v kota_04:38
notmynameI'd like to welcome kota_ as a new swift core reviewer04:42
kota_yey, much appreciated!04:42
dmoritaCongrats! kota_!04:43
kota_dmorita: Thanks :)04:43
*** sorrison_laptop has joined #openstack-swift04:50
openstackgerritJanie Richling proposed openstack/swift: WIP - working on the encryption feature.  https://review.openstack.org/15790704:57
jrichlikota: congrats!04:57
jrichlikota_ ^^04:57
kota_jrichli: Thanks :)04:57
*** jrichli has quit IRC05:00
*** nadeem has joined #openstack-swift05:08
*** nadeem has quit IRC05:08
*** [1]dimasot has joined #openstack-swift05:32
*** SkyRocknRoll has joined #openstack-swift05:40
*** SkyRocknRoll has joined #openstack-swift05:40
*** [2]dimasot has joined #openstack-swift05:47
*** ppai has quit IRC05:48
*** [1]dimasot has quit IRC05:49
*** Triveni has joined #openstack-swift05:55
*** ppai has joined #openstack-swift06:02
*** [1]dimasot has joined #openstack-swift06:21
*** [2]dimasot has quit IRC06:24
*** flaper87 has quit IRC06:33
*** flaper87 has joined #openstack-swift06:33
mattoliveraukota_: Woo!! Congrats!06:40
kota_mattoliverau: Thanks! I'm very happy!06:41
mattoliveraukota_: Next panel, you'll be the new core guy ;)06:42
kota_mattoliverau: absolutely, I can introduce myself as so :)06:43
*** chenhuayi has joined #openstack-swift06:55
*** chenhuayi has quit IRC07:09
*** holahola has joined #openstack-swift07:11
holaholaa question. Is it possible to backup openstack swift data with TSM ?  http://docs.openstack.org/juno/config-reference/content/swift-backup-driver.html07:12
holaholai find a general driver. and a tsm driver for cinder volumes07:12
cschwedeGood Morning!07:20
cschwedekota_: congrats :D07:20
kota_cschwede: good morning and thanks :D07:21
*** ppai has quit IRC07:21
*** ppai has joined #openstack-swift07:35
*** chlong has quit IRC07:44
*** jistr has joined #openstack-swift07:50
*** jistr is now known as jistr|mt07:54
*** jistr|mt is now known as jistr|mtg07:54
*** dimasot has joined #openstack-swift08:00
*** [1]dimasot has quit IRC08:01
*** aix has joined #openstack-swift08:03
*** km has quit IRC08:06
*** km has joined #openstack-swift08:07
hokota_: Congrats!08:08
*** acoles_away is now known as acoles08:11
acolesmorning08:11
acoleskota_: welcome and congratulations!08:12
kota_acoles, ho: thank you so much!08:20
hokota_: thanks for your first +2 :-)08:21
acolesho kota_ : heh, quick to get going :)08:22
*** mmcardle has joined #openstack-swift08:24
*** jordanP has joined #openstack-swift08:27
*** mmcardle has quit IRC08:34
*** mmcardle has joined #openstack-swift08:45
*** km has quit IRC08:59
*** km has joined #openstack-swift08:59
acolestorgomatic: heh, i spent several years working on a project called 'sup' so did a double take when scrolling back09:01
*** [1]dimasot has joined #openstack-swift09:07
*** mandarine has joined #openstack-swift09:08
*** dimasot has quit IRC09:11
*** [1]dimasot is now known as dimasot09:11
*** ho has quit IRC09:19
*** jistr|mtg is now known as jistr09:19
*** dmorita has quit IRC09:28
*** ppai has quit IRC09:36
*** Trixboxer has joined #openstack-swift09:43
*** sorrison_laptop has quit IRC09:45
*** geaaru has joined #openstack-swift09:50
*** ppai has joined #openstack-swift09:50
*** kota_ has quit IRC09:51
*** ahale has joined #openstack-swift10:03
*** sorrison_laptop has joined #openstack-swift10:15
*** ppai has quit IRC10:29
holaholais there anyone who know when tivoli storage manager will start to support to store data on Swift ?10:33
holaholatried cloudberry, that was easy and working very well.10:33
cschwedeholahola: most likely someone from IBM can answer that. I’m curious, are there plans to add Swift support to TSM?10:40
*** sorrison_laptop has quit IRC10:40
*** ppai has joined #openstack-swift10:42
*** sorriso__ has joined #openstack-swift10:43
*** sorriso__ has quit IRC10:44
*** marzif_ has joined #openstack-swift10:47
*** marzif_ has quit IRC10:50
*** marzif_ has joined #openstack-swift10:50
holaholarumors say so10:57
holaholaa version in late fall10:57
holaholathis yar10:57
holaholathis year10:57
holahola1q 2016 will tsm have s3 support as well10:57
*** csmart has quit IRC11:05
*** csmart has joined #openstack-swift11:07
*** aix has quit IRC11:30
*** Triveni has quit IRC11:33
*** ppai has quit IRC11:35
*** tellesnobrega has joined #openstack-swift11:47
*** dimasot has quit IRC11:48
*** ppai has joined #openstack-swift11:49
*** mmcardle has quit IRC11:58
*** mmcardle has joined #openstack-swift11:58
*** sorrison_laptop has joined #openstack-swift11:59
*** mmcardle has quit IRC12:03
openstackgerritMerged openstack/python-swiftclient: Allow reading from object body on download  https://review.openstack.org/15529112:08
*** km has quit IRC12:10
*** chlong has joined #openstack-swift12:19
openstackgerritMerged openstack/swift: EC: support multiple ranges for GET requests  https://review.openstack.org/17349712:24
*** thurloat_isgone is now known as thurloat12:28
*** aix has joined #openstack-swift12:30
*** ppai has quit IRC12:36
openstackgerritChristian Schwede proposed openstack/python-swiftclient: Run functional tests using keystone auth options  https://review.openstack.org/12351412:42
*** holahola has quit IRC12:43
*** jkugel has joined #openstack-swift12:44
*** marzif_ has quit IRC12:44
*** fanyaohong has joined #openstack-swift12:44
*** jkugel1 has joined #openstack-swift12:45
*** sorrison_laptop has quit IRC12:47
*** kei_yama has quit IRC12:48
*** ppai has joined #openstack-swift12:48
*** jkugel has quit IRC12:49
acolescschwede: thx for rebase. actually, when i saw that both func test runs were running all 36 tests was when i realised we need the passenv trick :) so we should now see one run with 24 skips and one with no skips.12:51
openstackgerritChristian Schwede proposed openstack/python-swiftclient: Run functional tests using keystone auth options  https://review.openstack.org/12351412:55
cschwedeacoles: you’re welcome. same for me, i was looking at the code, then at the logs - and realized something is missing there :)12:56
cschwedei just realized that i rebased only against master, not against the outstanding tox.ini patch. so i fixed that now12:56
acolescschwede: yes ^^ thats makes sense :)12:56
acoleswas just typing the same12:56
*** delatte has joined #openstack-swift12:58
*** cdelatte has quit IRC12:59
*** delattec has quit IRC12:59
*** delattec has joined #openstack-swift13:00
*** delatte has quit IRC13:02
*** petertr7_away is now known as petertr713:15
*** nileshb has joined #openstack-swift13:20
*** Triveni has joined #openstack-swift13:24
*** Triveni has quit IRC13:29
*** odsail has joined #openstack-swift13:49
*** nileshb has quit IRC13:57
*** blmartin has joined #openstack-swift14:01
*** blmartin_ has joined #openstack-swift14:01
openstackgerritpradeep kumar singh proposed openstack/python-swiftclient: SwiftClient object upload beginning with / or "./"  https://review.openstack.org/18526914:02
*** mandarine has left #openstack-swift14:05
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925014:05
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873614:05
*** odsail has quit IRC14:08
*** wbhuber has joined #openstack-swift14:19
*** SkyRocknRoll has quit IRC14:20
*** acampbel11 has joined #openstack-swift14:21
*** acampbell has joined #openstack-swift14:21
*** jrichli has joined #openstack-swift14:27
*** mwheckmann has joined #openstack-swift14:31
*** jrichli has quit IRC14:32
*** odsail has joined #openstack-swift14:35
*** acampbel11 has quit IRC14:37
*** acampbell has quit IRC14:37
openstackgerritDarrell Bishop proposed openstack/swift: Allow 1+ object-servers-per-disk deployment  https://review.openstack.org/18418914:43
swifterdarrellclayg: notmyname: cschwede: acoles: tdasilva: portante: zaitcev: "not any worse and slightly better when healthy" benchmarks for servers_per_port patch: https://gist.github.com/dbishop/c214f89ca708a6b1624a#file-summary-md14:46
*** chlong has quit IRC14:47
*** chenhuayi has joined #openstack-swift14:47
swifterdarrellclayg: notmyname: cschwede: acoles: tdasilva: portante: zaitcev: going to investigate any difference with 2 of 30 disks (7%) hammered with I/O (one from an unleashed object-auditor and 1 from some kind of synthetic filesystem benchmark program)14:49
*** SkyRocknRoll has joined #openstack-swift14:52
*** fanyaohong has quit IRC14:53
*** mwheckmann has quit IRC14:55
*** lpabon has joined #openstack-swift15:00
*** SkyRocknRoll has quit IRC15:00
*** mwheckmann has joined #openstack-swift15:01
*** chenhuayi has quit IRC15:02
*** SkyRocknRoll has joined #openstack-swift15:04
*** SkyRocknRoll has joined #openstack-swift15:04
openstackgerritAlistair Coles proposed openstack/swift: Add metadata size tests on the border  https://review.openstack.org/18748915:08
*** jrichli has joined #openstack-swift15:09
*** annegentle has joined #openstack-swift15:13
*** silor has joined #openstack-swift15:13
portanteswifterdarrell: nice, that is a good result15:19
*** minwoob has joined #openstack-swift15:19
portanteI am guessing that the 90 worker count will track well against the servers-per-port work, but the 30 will be "off"15:23
*** elmiko has joined #openstack-swift15:28
elmikonotmyname: hey, might you have a minute or two to talk about the api-wg?15:28
peluseswifterdarrell, you there?15:31
swifterdarrellpeluse: ya!15:31
swifterdarrellpeluse: what's up?15:31
pelusewondering about your patch just now, you know ctennis is out here in phoenix all week and we're just about ready to confirm good baseline 3x nubers on a 14 node cluster15:32
pelusenot sure how much time we'll have but does it make sense to try and check your patch on this setup?15:32
peluse(we have to do EC first though)15:32
swifterdarrellpeluse: I'd consider it a nice-to-have, but IIRC, you guys were short on time relative to what you wanted to benchmark15:33
*** gyee has joined #openstack-swift15:33
swifterdarrellpeluse: so I wouldn't consider benchmarking my patch a high priority15:33
* portante thinks so, but just increasing worker counts would lend credence to swifterdarrell's work15:33
peluseyeah, kinda what I figured but since I saw the patch I figured I'd ask :)15:33
swifterdarrellpeluse: *nod* thanks!  So if you have time and want to fiddle with it, that'd be great, but definitely do your primary objectives first15:34
peluserock n roll15:34
swifterdarrellportante: I'm excited about my while-disks-are-beat-up testing; I have a bonnie++ killing one disk per node now, and just setting up the ssbench stuff15:35
portantekewl15:36
peluseswifterdarrell, so another question - do you recall when threads_per_disk was introduced (I think by torgomatic) I thought the default was non-zero and the intent was to prevent things from getting backed up from a single slow/hosed disk.  Def is now 0 - am I remembering wrong or did just experience/perf work move us to 0?15:36
portantehow long until we can see your results ya think? ;)15:36
peluseI ask because we have a node here with a few wonky disks and they were really jacking up cluster performance15:37
swifterdarrellpeluse: defautl for threads-per-disk was always 0 (which is good)15:37
portantepeluse: try ramping up worker counts to alleviate those effects15:37
portanteI think you'll see that by doing so you'll see improvements15:37
swifterdarrellpeluse: it's tricky keeping the thread count low (it's the product of disk_count * workers * threads_per_disk); when that gets near or over 1000, everything goes to shit; even before that, threads-per-disk has huge overhead15:38
peluseportante, hey!  Well, we were hoping today but we came in this morinng to a small screwball something so need to figure out what happened with the overnight gremlins then we'll be off to the races.  If all goes well 3x and EC by EOW (maybe not fully written up but baseline numbers collected)15:38
portantenice15:38
portantetorgomatic: did we ever get the splice work into swift?15:39
swifterdarrellportante: eta on next batch of results is probably a couple of days?  I am going to use shorter run times and a little more automation 'cause I can't do this forever15:39
swifterdarrellportante: zero-copy (splice) for read path got in, IIRC but not for writes?15:39
peluseportante, I think the GET splice made it in but not PUT15:40
swifterdarrellportante: RHEL 6.x doesn't have the required crypto-socket thing in its kernel, tho15:40
portanteswifterdarrell: so that is in play with your testing, right?15:40
peluseyeah, what swifterdarrell said :)15:40
portanteyou guys should try out RHEL 7, nice performance gains in that environment15:41
swifterdarrellpeluse: re: the bad disks screwing you up, that would be a good test bed for servers_per_disk, but as portante said, he and I have seen good results with just cranking the worker count up; I would *not* recommend threads-per-disk due to its overhead15:42
swifterdarrellportante: not using zero-copy stuff atm15:42
portanteswifterdarrell, peluse, torgomatic, I ask about the splice thing because another possibility would be to hand off a port to a thread to drive all the I/O instead of passing it through the eventlet hub.15:43
swifterdarrellportante: re: RHEL 7, we do what the customers do, and RHEL customers, almost by definition, are slow-moving ;)  we'll obvs get there, but in proportion to customer demand/adoption15:43
peluseswifterdarrell, thanks.  yeah this morn that was the first thing I wanted to try but one of guys came in last night to get a few more nodes added and things went haywire (temporarily I hope)... we will likely have to punt on investigating the slow disk thing and just get HW replaced so we can move fwd on BM15:43
*** thurloat is now known as thurloat_isgone15:43
pelusebenchmarking that is, not bowel movement :)15:44
portanteswifterdarrell: understood about RHEL 7 adoption rates15:44
* portante smiles quietly to himself15:44
*** zaitcev has joined #openstack-swift15:45
*** ChanServ sets mode: +v zaitcev15:45
*** jordanP has quit IRC15:45
portantezaitcev: see above about zero-copy work in read path not in play on RHEL 6 due to missing crypto thingy15:46
zaitcevportante: "above"?15:46
portanteoh, you don't use znc?15:46
*** nadeem has joined #openstack-swift15:48
*** evanjfraser has quit IRC15:53
*** evanjfraser has joined #openstack-swift15:53
*** nadeem has quit IRC15:54
*** nadeem has joined #openstack-swift15:54
*** nadeem has quit IRC15:54
*** jistr has quit IRC16:01
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/17434316:05
*** annegentle has quit IRC16:08
*** jordanP has joined #openstack-swift16:18
*** jordanP has quit IRC16:19
notmynamegood morning16:26
notmynameelmiko: sure, but give me a little bit to get settled. I just got to the office16:27
elmikonotmyname: no worries, i've got a couple meetings atm16:27
openstackgerritAlistair Coles proposed openstack/swift-specs: Updates to encryption spec  https://review.openstack.org/15431816:27
*** silor has quit IRC16:28
*** SkyRocknRoll_ has joined #openstack-swift16:30
pelusemorning16:32
*** aix has quit IRC16:33
*** petertr7 is now known as petertr7_away16:33
openstackgerritAlistair Coles proposed openstack/swift-specs: Updates to encryption spec  https://review.openstack.org/15431816:35
wbhubermorning16:36
openstackgerritAlistair Coles proposed openstack/swift-specs: Updates to encryption spec  https://review.openstack.org/15431816:36
openstackgerritAlistair Coles proposed openstack/swift-specs: Add keymaster discussion to encryption spec  https://review.openstack.org/18301416:36
*** marzif_ has joined #openstack-swift16:37
*** breitz has quit IRC16:37
*** breitz has joined #openstack-swift16:38
*** odsail has quit IRC16:59
acolestorgomatic: any chance you could cast an eye over the spec update in patch 154318, its been hanging around for a while and maybe good enough to land then patch as we iterate on the details?17:00
patchbotacoles: https://review.openstack.org/#/c/154318/17:00
*** marzif_ has quit IRC17:00
*** odsail has joined #openstack-swift17:05
*** ppai has quit IRC17:10
*** marzif_ has joined #openstack-swift17:11
notmynameoh, cool. I just saw that the multi-range get for EC patch just landed17:17
notmynamenew keyboard at work now. yay17:18
acolesnotmyname: what do you have?17:18
lcurtisHello all...is erasure coding fully 'supported' in latest swift release or should it still be considered beta17:18
notmynameacoles: WASD code keyboard http://www.wasdkeyboards.com/index.php/products/code-keyboard/code-87-key-mechanical-keyboard.html17:18
notmynameacoles: I got one at home a while back, and just got a 2nd for work17:18
*** haomaiwang has joined #openstack-swift17:19
notmynamelcurtis: beta17:19
lcurtisthank you notmyname...so best not to run production workloads with it at the moment?17:19
*** haomaiw__ has quit IRC17:20
notmynamelcurtis: I wouldn't. there have been a few patches that have landed since the last release that you'd need in prod, and there is still various testing going on to understand what it does at larger scales and wrt performance17:20
acolesnotmyname: nice. i was looking recently - the clear keys the quietest right?17:21
notmynamelcurtis: that being said, I feel a lot better about EC on master right now17:21
notmynameacoles: this one isn't too loud. certainly not silent, but it's not "clicky"17:21
lcurtisnotmyname...that is fantastic news17:21
lcurtiskeep up the great work!17:21
notmynamehi acoles. i'm making a video now of typing on my new keyboard17:22
acolesnotmyname: maybe i should ask your colleagues for a loudness assessment after a day or two ;)17:22
notmyname:-)17:22
notmynamelet me figure out how to upload this17:23
acolesi've been using tenkeyless for years but not of a great quality17:24
notmynameacoles: http://d.not.mn/typing.m4v17:24
acoleswow thats quiet!17:25
lcurtisnotmyname will EC be an in-place upgrade?17:25
acolesoh wait, let me un-mute...17:25
*** Viswanath has joined #openstack-swift17:25
notmynamelcurtis: what do you mean?17:25
notmynameacoles: lol17:25
*** petertr7_away is now known as petertr717:26
lcurtisis it something that can be enabled and replicas will be chunked automatically?17:26
notmynamelcurtis: it's a storage policy. so you can have either (or both) EC and replication17:27
notmynamebut it's set on a per-container level17:27
notmynameat the time the container is created17:27
lcurtisah..so cannot retroactively perform on container?17:27
*** acampbel11 has joined #openstack-swift17:28
*** acampbell has joined #openstack-swift17:28
*** Viswanath has quit IRC17:30
*** SkyRocknRoll_ has quit IRC17:30
*** doxavore has joined #openstack-swift17:30
acolesnotmyname: i thought about taking on the challenge of a ninja https://www.diatec.co.jp/en/det.php?prod_c=775 but don't think my touch typing is quite there yet ;)17:30
notmynamecheck out the wasd keyboards site. they've got a ton of configuration options17:33
*** SkyRocknRoll_ has joined #openstack-swift17:33
acolesyeah and i read about retrofit collars you can fit to reduce travel etc17:34
*** delattec has quit IRC17:34
*** cdelatte has joined #openstack-swift17:34
*** geaaru has quit IRC17:35
notmynameyeah, the o-rings17:35
notmynameI ended up getting the clear switches because they are rated at the same force as the keyboards I was used to (macbook/apple)17:35
notmyname65N17:36
acolespeluse: wow swift-dispersion-report was totally broken if default wasn't policy 017:38
acolesnotmyname: makes sense17:38
acolespeluse: (just looking at your patch)17:38
*** haomaiwa_ has joined #openstack-swift17:39
elmikonotmyname: hey, finally got free. can you spare a few minutes?17:39
*** cdelatte has quit IRC17:39
*** haomaiwang has quit IRC17:41
notmynameelmiko: sure. what's up?17:43
notmynameelmiko: do you want to talk in here? or do you want to video chat? phone?17:45
elmikonotmyname: we can chat here, i just wanted to share a few links17:46
notmynameok17:46
elmikoso, i'm reaching out to all the listed liaisons17:46
elmikoi want to share this list of proposed liaison responsibilities from the nova team, https://wiki.openstack.org/wiki/Nova/APIWGLiaisons17:47
elmikoand also, this merge process review we are working on, https://review.openstack.org/#/c/18683617:47
*** dontalton has joined #openstack-swift17:47
elmikoi imagine over the next few weeks we'll be sending some emails to the ML with proposed guidelines that are going into freeze before merge17:47
elmikono specific action is required from the liaisons, but we'd like to help improve communcation about the upcoming guidelines17:48
elmikoalso, if you have any questions/comments/concerns we usually hang out in openstack-api17:48
*** gyee has quit IRC17:49
elmikonot sure if we've met at summit before or not, but my name is michael mccune =)17:49
notmynameI lurk in the -api channel17:49
notmynameI'm looking over the process doc17:49
elmikocool, thanks!17:49
elmikoyea, i know you've got the global regex for "swift" on freenode ;)17:49
notmynameI do think that keeping the patches in front of people is a good thing17:50
notmynameheh, not quite17:50
elmikoyea, we're hoping that getting more visibility will help17:50
elmikoanyways, that's about all for my song and dance, thanks for your time =)17:51
notmynameelmiko: thanks for the info17:51
notmynameelmiko: what's the current process for the api-wg for when a proposal doesn't match existing APIs? or isn't compatible with an existing API?17:52
notmynamefrom what I can tell, the wg pretty much says "well this is just guidance" and then nothing happens17:52
notmynameso far :-)17:52
elmikoyea, we try to set out the guidelines in a way that won't obstruct projects that might be doing things differently17:53
*** SkyRocknRoll_ has quit IRC17:53
elmikoi think our preferred engagement method is to help on reviews for new api content17:53
elmikoand we'd like to become a resource that projects can call on if there are questions17:53
elmikomaybe about new versions, or revamps to old code17:53
elmikowe're going with more of the carrot than the stick ;)17:53
notmynameso far the feedback I've gotten is "swift is doing it wrong"17:54
elmikolol, yea. there's a lot of that going around. i don't necessarily agree17:54
elmikoi mean, you guys have some reasoning as to why you've crafted the api the way it is.17:55
elmikoif the project is open to suggestions, then i'm sure there would  be folks in the wg who would want to help, but17:55
*** marzif_ has quit IRC17:55
elmikoif you'd like to keep developing in the manner that's been working, imo we need to respect that17:56
notmynamethat's good to hear17:56
*** marzif_ has joined #openstack-swift17:56
elmikothe overarching goal for the wg is help bring the overall apis into a more consistent state, but that does not mean beating projects into submission17:56
elmikosome projects will always have reasons for going against the guidelines, that's fine imo.17:57
notmynamemy concern that I've tried to share with the wg is that many things in openstack have started as "here's some helpful guidance that you can choose to use or not" and then turned in to "why aren't you doing things the OpenStack Way(tm)?!"17:57
notmynamewhich is where the root of my concern about the api-wg comes from17:57
notmynamein general, I think the idea of consistent APIs is wonderful! I have no argument there17:58
elmikoi can't predict how things will go in the future, but i know there are several voices within the wg (mine included) who are against becoming the api police17:59
notmynameand that being said, I'm happy to work with the api-wg as new things are proposed. and we'll use those in swift where we can (ie not gratuitous changes from existing behavior or breaking changes)17:59
elmikocool, i know we'll be glad to have another voice =)18:00
*** annegentle has joined #openstack-swift18:01
*** Viswanath has joined #openstack-swift18:01
*** barra204 has joined #openstack-swift18:01
*** jrichli has quit IRC18:03
elmikothanks again notmyname, take care18:03
*** Viswanath has quit IRC18:04
*** tellesnobrega_ has joined #openstack-swift18:06
*** barra204 has quit IRC18:07
*** jrichli has joined #openstack-swift18:07
portantenotmyname: can't resist ... who is saying "swift is doing it wrong"?18:08
redbopeople who think POST should be the only verb that can create things?18:09
*** haomai___ has joined #openstack-swift18:09
*** haomaiwa_ has quit IRC18:10
portanteoh boy, the REST police to the rescue18:10
notmynamelol18:11
redboTo be fair, there are some things swift does wrong.  But we still work with clients written like 6.5 years ago, which seems worth keeping a few warts to me.18:12
notmynameportante: redbo: people who don't like us using headers that start with X-. or that want us to have a different path URL for metadata18:12
notmynameredbo: yes, that. exactly18:12
*** Fin1te has joined #openstack-swift18:12
portantesounds like these folks have not developed, deployed, run for a while and maintained real software in production18:13
notmynameI think that might be a little unfair ;-)18:13
notmyname(or ad-hominem)18:13
sweeperstrawmen are the funnest18:14
portanteif the target of that is the sentiments listed above then I agree, but if that is referring to the comment about real software ...18:14
portante"that" in quotes above ...18:14
portantethat is18:14
redboyeah, who wants to be fair?18:14
notmynameso far, there's a few things that the api-wg have approved that are ok, and there are a few that IMO are pretty bad (at least from swift's perspective). if there is something net-new that we add to swift, the api-wg can offer some guidance on how others also have implemented a similar problem. but the ones that don't work at all, I don't think we should worry about18:19
*** annegentle has quit IRC18:21
*** annegentle has joined #openstack-swift18:22
*** kr4zy has joined #openstack-swift18:22
*** MVenesio has joined #openstack-swift18:23
*** acoles is now known as acoles_away18:24
*** silor has joined #openstack-swift18:27
clayglol @ redbo18:28
*** tellesnobrega_ has quit IRC18:29
*** tellesnobrega_ has joined #openstack-swift18:29
*** tellesnobrega_ has quit IRC18:29
*** tellesnobrega_ has joined #openstack-swift18:32
*** tellesnobrega_ has quit IRC18:32
*** friedchicken has joined #openstack-swift18:36
*** dimasot has joined #openstack-swift18:38
*** openstackstatus has joined #openstack-swift18:40
*** ChanServ sets mode: +v openstackstatus18:40
*** tellesnobrega_ has joined #openstack-swift18:41
-openstackstatus- NOTICE: Gerrit has been restarted to clear an issue with its event stream. Any change events between 17:25 and 18:38 UTC should be rechecked or have their approvals reapplied to initiate testing.18:42
*** tellesnobrega_ has quit IRC18:43
*** silor has quit IRC18:45
*** tellesnobrega_ has joined #openstack-swift18:45
*** marzif_ has quit IRC18:47
*** Fin1te has quit IRC18:51
*** elmiko is now known as _elmiko18:53
*** SkyRocknRoll has quit IRC18:53
*** kr4zy has quit IRC18:54
*** mmcardle has joined #openstack-swift18:56
*** Fin1te has joined #openstack-swift18:57
*** Fin1te has quit IRC19:00
*** marzif_ has joined #openstack-swift19:04
*** Fin1te has joined #openstack-swift19:05
*** annegentle has quit IRC19:07
*** petertr7 is now known as petertr7_away19:16
*** Viswanath has joined #openstack-swift19:18
*** mjseger has quit IRC19:20
*** petertr7_away is now known as petertr719:21
*** Viswanath has quit IRC19:21
*** kr4zy has joined #openstack-swift19:21
kr4zyFor 1G NICs server, is ~1.62/sec for object-replicator a normal speed?19:22
*** Fin1te has quit IRC19:24
*** mmcardle has quit IRC19:31
notmynamekr4zy: there's not a "normal" since it's so dependent on hardware. however, while the replication network speed does matter, normally replication is limited by disk IO19:32
jrichlitorgomatic: glad to see the +2 on the spec!  Thanks for taking a look19:33
notmynamekr4zy: so the answer is really that you should look at what is normal to you instead of normal for anyone else19:33
*** csmart has quit IRC19:35
*** csmart has joined #openstack-swift19:38
*** csmart has quit IRC19:43
*** csmart has joined #openstack-swift19:45
*** Fin1te has joined #openstack-swift19:47
*** mwheckmann has quit IRC19:53
*** Viswanath has joined #openstack-swift19:55
*** dimasot has quit IRC19:58
*** odsail has quit IRC20:00
*** Viswanath has quit IRC20:00
*** marzif_ has quit IRC20:00
*** mwheckmann has joined #openstack-swift20:01
*** csmart has quit IRC20:05
*** csmart has joined #openstack-swift20:05
*** Viswanath has joined #openstack-swift20:07
*** Viswanath has quit IRC20:10
*** csmart has quit IRC20:10
*** Viswanath has joined #openstack-swift20:16
*** csmart has joined #openstack-swift20:16
claygdid the guy yesterday with the ssl cert thing ever figure out what keystone was doing?20:19
claygjlk: <- this guy right?20:19
*** Viswanath has quit IRC20:20
jlkclayg: I haven't yet, I was distracted with other things.20:35
*** Viswanath has joined #openstack-swift20:44
pelusenotmyname, can you repost the lcoation of the EC data you showed in vancouver?20:45
*** mmcardle has joined #openstack-swift20:47
*** Viswanath has quit IRC20:47
notmynamepeluse: yeah, let me find it.20:58
notmynamealso, I need to look and see if there's any newer data20:58
notmynamepeluse: http://d.not.mn/20150512_run2_15fullness.tgz20:59
notmynameit's about 200MB20:59
*** Fin1te has quit IRC21:01
pelusethanks21:01
*** operator99 is now known as gyee21:02
*** zhill_ has joined #openstack-swift21:02
*** blmartin has quit IRC21:06
*** blmartin_ has quit IRC21:07
*** petertr7 is now known as petertr7_away21:09
*** jrichli has quit IRC21:10
*** nadeem has joined #openstack-swift21:16
*** doxavore has quit IRC21:16
*** tellesnobrega_ has quit IRC21:21
lcurtisdoes anyone happen to know unit of measure used in statsd middleware metrics for stats.SERVER.proxy-server.object.PUT.201.xfer21:22
lcurtistrying to figure actual throughput into my cluster21:23
lcurtisor perhaps I can use swift-recon divided by number of replicas?21:24
*** acampbel11 has quit IRC21:33
*** acampbell has quit IRC21:33
*** wbhuber has quit IRC21:36
*** lpabon has quit IRC21:36
*** wbhuber has joined #openstack-swift21:36
*** MVenesio has quit IRC21:39
lcurtisfound it..its bytes21:42
lcurtishttp://docs.openstack.org/developer/swift/admin_guide.html#reporting-metrics-to-statsd21:42
*** mmcardle has quit IRC21:46
*** _elmiko is now known as elmiko21:47
*** elmiko has left #openstack-swift21:47
*** friedchicken has quit IRC21:51
*** kr4zy has quit IRC21:56
*** jkugel1 has quit IRC22:03
*** Fin1te has joined #openstack-swift22:07
*** wbhuber_ has joined #openstack-swift22:20
*** wbhuber has quit IRC22:24
*** Fin1te has quit IRC22:25
*** ndk has quit IRC22:27
claygso what name are we likeing for M?22:27
*** ndk has joined #openstack-swift22:27
*** sorrison_laptop has joined #openstack-swift22:28
torgomaticMongoose!22:34
*** dontalton has quit IRC22:35
*** annegentle has joined #openstack-swift22:35
claygtorgomatic: not on the list -> https://wiki.openstack.org/wiki/Release_Naming/M_Proposals22:36
torgomaticwell, it darn well should be :p22:36
*** zaitcev has quit IRC22:37
notmynameI like Metropolis22:37
claygI like the Monkey -> http://en.wikipedia.org/wiki/Japanese_macaque22:38
clayghow do you pronounce "Macque"22:38
notmynameyeah, that one too :-)22:38
notmynameclayg: click the speaker link on http://www.oxforddictionaries.com/us/definition/american_english/macaque22:39
claygwow - is it really muh-kawk?22:39
claygyeah this release should toally be all 'bout muh-kwak22:40
claygnot *your* kawk mind you22:40
*** Guest47317 has quit IRC22:40
*** annegentle has quit IRC22:40
*** sorrison_laptop has quit IRC22:41
*** minwoob has quit IRC22:41
*** scott has joined #openstack-swift22:41
*** scott is now known as Guest4871922:41
*** annegentle has joined #openstack-swift22:42
mattoliverauMorning22:43
*** zhill_ has quit IRC22:45
torgomaticwelp, the monkey has my vote22:45
*** zhill_ has joined #openstack-swift22:56
*** km has joined #openstack-swift22:58
*** zhill_ has quit IRC23:01
*** annegentle has quit IRC23:08
claygyeah macque - how do we vote23:15
*** sorrison_laptop has joined #openstack-swift23:16
*** wbhuber_ has quit IRC23:16
*** zhill_ has joined #openstack-swift23:20
*** kei_yama has joined #openstack-swift23:22
*** zhill_ has quit IRC23:24
*** chlong has joined #openstack-swift23:27
*** odsail has joined #openstack-swift23:34
*** nadeem has quit IRC23:35
*** odsail has quit IRC23:37
*** dmorita has joined #openstack-swift23:37
*** asettle has quit IRC23:46
*** asettle has joined #openstack-swift23:48
*** ho has joined #openstack-swift23:52
*** sorrison_laptop has quit IRC23:58

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