Thursday, 2014-02-06

*** hurricanerix has quit IRC00:09
notmynamefrom the openstack mailing list: "Also, I have added a section noting crucial bugs/patches that are blocking Minesweeper."00:10
notmynamecan I respond with, "just put flags around them and move on"?00:10
torgomaticYES00:11
torgomaticin fact, I think you're legally obligated to do so00:11
*** _bluev has quit IRC00:19
*** _bluev has joined #openstack-swift00:20
*** matsuhashi has joined #openstack-swift00:20
*** jergerber has quit IRC00:22
*** joeljwright has joined #openstack-swift00:38
*** joeljwright has quit IRC00:42
*** nosnos has joined #openstack-swift00:56
*** tdasilva has left #openstack-swift01:12
*** igor has joined #openstack-swift01:15
*** igor____ has quit IRC01:16
*** zackf has joined #openstack-swift01:27
*** zackf has quit IRC01:35
*** shri has quit IRC01:38
zaitcevGuys01:38
zaitcevImagine I want to review what's up with storage policies.01:38
zaitcevSince it has its own branch... I cannot review what's already merged into that branch.01:39
*** joeljwright has joined #openstack-swift01:40
portantewhat about a query against gerrit for all merged commits against feature/ec?01:40
torgomaticalternately, pull the branch and look at the commits; they're all in git01:42
zaitcevI know how to use git in this case. But I do not see other option except post an old-fashioned review to openstack-dev and cc: peluse01:43
torgomatictrue; you could propose patches to fix things up if you see problems01:43
torgomaticdoes Gerrit not let you post comments on merged reviews/01:43
torgomatic?01:43
portanteit does01:43
torgomaticGerrit query: project:openstack/swift branch:feature/ec01:44
zaitcevah, okay. I can drop "status:open" from gerrit URL01:44
*** joeljwright has quit IRC01:44
*** bada_ has quit IRC01:45
torgomaticstatus:merged will even let you skip the abandoned ones01:45
zaitcevwooow the first commit is "update .gitreview with defaultbranch=feature/ec"01:46
zaitcevno fans of Blitzkrieg I see01:47
*** joeljwright has joined #openstack-swift02:40
*** joeljwright has quit IRC02:45
*** jasondotstar has joined #openstack-swift02:50
*** briancline has quit IRC03:10
*** briancline has joined #openstack-swift03:14
brianclinejust catching up in the scrollback from earlier03:16
brianclineportante: torgomatic: trust me, as a mostly-sane adult, I'm quite aware that some utopian ideal of fairness doesn't exist03:18
brianclinejust voicing a simple observation is all -- it was to some degree a slightly related topic wrt one of the final meeting topics today03:19
*** _bluev has quit IRC03:23
portantebriancline: okay03:23
zaitcevMan, I'm like an hour into the policies and I'm already mad.03:31
zaitcevI'm going to ask peluse tomorrow why he ever thought that exposing policy index might be a good idea.03:32
portantezaitcev: careful03:32
zaitcevportante: Sure.03:32
portantethere have been many design discussions on this topic for 6 months03:32
zaitcevdaaarn03:32
portanteit is not all on peluse03:32
zaitcevBut what are they for, however?03:33
portanteso let's walk through it a bit03:33
portantewhere are you seeing the policy index exposed that you consider it a problem?03:33
*** odyssey4me has joined #openstack-swift03:35
zaitcevI'm building the graph of all the info leakage through all the get_by_index, get_diskfile_through_hash, and so on.03:35
portanteinfo leakage?03:35
zaitcevcall it knowledge leakage03:36
portanteisn't the policy index passed as an argument to the object server?03:36
zaitcevI haven't established that user on the other side of proxy knows anything about indexes03:36
*** odyssey4me2 has joined #openstack-swift03:39
*** odyssey4me has quit IRC03:40
zaitcevMaybe I'm being worked up over nothing. Say, the indexing is in swift.conf. But it also has the main hash suffix, which you cannot afford to lose anyway. So it's not like one could recover any data if anything happened to that information.03:40
*** joeljwright has joined #openstack-swift03:42
*** joeljwright has quit IRC03:46
zaitcevhttps://review.openstack.org/70497 - okay that's a good one03:48
notmynamezaitcev: the storage policy index is the canonical identifier for the policy. and yes, I agree that it leaked too much. that's what prompted me to talk to peluse about it, and all of the patches related to that haven't landed yet03:50
zaitcevnotmyname: thanks.03:51
notmynamebut the index is used to allow the provider to migrate (ie everyone today is using storage policy 0), and it will allow for a policy to have one or more names03:51
zaitcevBTW, does anyone know why it happens like this... If I look at the git log, it says change Change-Id: I71eab0788.... added policies to DiskFile. But if I look at Gerrit, it's a different commit at all and Change-Id is  I70189013.03:52
zaitcevnotmyname: I don't understand how anything can be migrated if indexes are in container meta. Once they get stuck there, you can never change policy index of a given policy, or can you?03:54
notmynamecorrect. and that's why the storage policy can only be set at container creation and can't be changed03:54
notmynamethe policy reconciler that torgomatic is working on handles the split-brain case when the same container is created with 2 different policies03:55
zaitcevhmm. Once thing is clear, I tuned out your discussions due to PBE and other things and you probably talked about all this.03:55
zaitcevportante: in case you have a second, how do you know that get_hashes() is not going to recurse endlessly?04:01
portanteget_hashes in diskfile.py?04:02
zaitcevyes04:02
* portante looks04:02
* portante assumes ec branch ...04:02
notmynamezaitcev: I'm going to wander away from my computer now. if you've got more questions, portante will answer them ;-)04:02
zaitcevI think it does in case there was some kind of conflict04:02
notmyname(or jsut ask me tomorrow)04:02
portante;)04:02
*** zackf has joined #openstack-swift04:06
portantezaitcev: so regarding the module level get_hashes() method04:07
portanteIt can recurse for ever04:08
portanteand if there is a python implementation that does not do tail-call optimizations, this will be a problem04:08
zaitcevbut it's very unlikely, right?04:08
portanteCPython, for better or worse (in some cases) will optimize that call away so that there is no effective stack usage for the call04:09
zaitcevLooks like it's completely in service of replicator, which ought to retry if someone overflows its stack and crashes.04:09
zaitcevNice.04:09
portantebut it won't overflow the stack04:09
zaitcevThanks!04:09
portantenow, run that under pypy, or jython or something else, that fails to do tail call opts, and boom04:09
*** joeljwright has joined #openstack-swift04:43
openstackgerritAmala Basha proposed a change to openstack/python-swiftclient: swift_client needs to close http connection  https://review.openstack.org/5513204:44
*** basha has joined #openstack-swift04:44
bashazaitcev: chmouel : have rebased change https://review.openstack.org/#/c/55132/3. Please can you review it before it runs off to abandoned again. :)04:45
zaitcevbasha: I'll look.04:46
bashathanks zaitcev :)04:46
*** hurricanerix has joined #openstack-swift04:46
*** joeljwright has quit IRC04:47
*** hurricanerix has quit IRC04:47
*** zackf has quit IRC04:51
*** hurricanerix has joined #openstack-swift04:52
*** hurricanerix has quit IRC04:52
*** jasondotstar has quit IRC04:57
*** nosnos_ has joined #openstack-swift05:02
*** nosnos has quit IRC05:06
*** nshaikh has joined #openstack-swift05:19
*** madhuri has joined #openstack-swift05:23
*** zaitcev has quit IRC05:33
*** joeljwright has joined #openstack-swift05:44
*** joeljwright has quit IRC05:49
*** matsuhashi has quit IRC06:07
*** matsuhashi has joined #openstack-swift06:07
*** matsuhas_ has joined #openstack-swift06:09
*** matsuhashi has quit IRC06:09
*** igor has quit IRC06:18
*** igor has joined #openstack-swift06:18
*** ppai has joined #openstack-swift06:19
*** nosnos has joined #openstack-swift06:40
*** nosnos_ has quit IRC06:42
*** joeljwright has joined #openstack-swift06:45
*** joeljwright has quit IRC06:49
*** mfactor has joined #openstack-swift06:54
*** pheadron has joined #openstack-swift06:55
*** kragniz has quit IRC07:03
*** mfactor has quit IRC07:04
*** kragniz has joined #openstack-swift07:05
*** pheadron has quit IRC07:09
*** joeljwright has joined #openstack-swift07:10
*** bvandenh has joined #openstack-swift07:12
*** joeljwright has left #openstack-swift07:28
*** joeljwright has joined #openstack-swift07:28
*** mfactor has joined #openstack-swift07:29
*** foexle has joined #openstack-swift07:49
*** xga has joined #openstack-swift08:07
*** joeljwright has quit IRC08:14
*** joeljwright has joined #openstack-swift08:15
*** mlipchuk has joined #openstack-swift08:22
*** ben_roeder has joined #openstack-swift08:31
*** ben_roeder has quit IRC08:39
*** mmcardle has joined #openstack-swift08:42
*** nacim has joined #openstack-swift08:51
*** fbo is now known as fbo_away09:01
*** odyssey4me2 is now known as odyssey4me09:01
*** fbo_away is now known as fbo09:06
*** mlipchuk has quit IRC09:08
*** mlipchuk has joined #openstack-swift09:22
openstackgerritChristian Schwede proposed a change to openstack/swift: Limit logged headers in proxy_logging middleware  https://review.openstack.org/6436309:27
*** igor_ has joined #openstack-swift09:30
*** igor has quit IRC09:32
*** ben_roeder has joined #openstack-swift09:44
openstackgerritChristian Schwede proposed a change to openstack/swift: Remove swiftclient dependency  https://review.openstack.org/6566009:45
*** xga has quit IRC09:57
*** ben_roeder has quit IRC09:58
*** jasondotstar has joined #openstack-swift10:00
*** xga has joined #openstack-swift10:05
*** xga_ has joined #openstack-swift10:07
*** xga has quit IRC10:08
*** ben_roeder has joined #openstack-swift10:10
openstackgerritEamonn O'Toole proposed a change to openstack/swift: Parallel object auditor  https://review.openstack.org/5977810:12
*** mlipchuk has quit IRC10:17
*** ppai has quit IRC10:32
*** mlipchuk has joined #openstack-swift10:32
*** odyssey4me2 has joined #openstack-swift10:33
*** odyssey4me has quit IRC10:34
*** odyssey4me2 has quit IRC10:38
*** psharma has joined #openstack-swift10:44
*** ppai has joined #openstack-swift10:49
*** jasondotstar has quit IRC11:00
*** gvernik_ has joined #openstack-swift11:10
openstackgerritPrashanth Pai proposed a change to openstack/swift: Make .expiring_objects account name configurable  https://review.openstack.org/7097811:11
*** mef has joined #openstack-swift11:25
*** mfactor has quit IRC11:25
*** fbo is now known as fbo_away11:35
*** jasondotstar has joined #openstack-swift11:50
*** pheadron has joined #openstack-swift12:03
*** basha has quit IRC12:05
*** ben_roeder has quit IRC12:12
*** Anju has joined #openstack-swift12:19
*** igor has joined #openstack-swift12:45
*** igor_ has quit IRC12:46
*** ben_roeder has joined #openstack-swift12:47
*** Trixboxer has joined #openstack-swift12:50
*** fbo_away is now known as fbo12:55
*** mlipchuk has quit IRC12:56
*** jasondotstar has quit IRC13:00
*** psharma has quit IRC13:10
*** mlipchuk has joined #openstack-swift13:10
*** jasondotstar has joined #openstack-swift13:19
*** basha has joined #openstack-swift13:47
*** mfactor has joined #openstack-swift13:58
*** basha has quit IRC14:00
*** ppai has quit IRC14:01
*** mef has quit IRC14:01
openstackgerritA change was merged to openstack/swift: Fix a couple ifs in account quota middleware.  https://review.openstack.org/7140514:08
*** gvernik_ has quit IRC14:08
*** mmcardle has quit IRC14:15
*** ppai has joined #openstack-swift14:18
*** ben_roeder has quit IRC14:18
*** xga has joined #openstack-swift14:24
*** ppai has quit IRC14:25
*** mvenesio has joined #openstack-swift14:26
*** mmcardle has joined #openstack-swift14:33
*** mkollaro has joined #openstack-swift14:34
*** mfactor has quit IRC14:36
*** mef has joined #openstack-swift14:36
mvenesioportante, notmyname, creiht: Hi guys we are choosing hardware to expand our swift pictures cluster,  do you have any recommendations regarding HDDs ? , we are thinking in the seagate 6Gb SAS constellation es3, but also could be some SATA3 drive. Do you have some experience to suggest us ?14:37
*** ben_roeder has joined #openstack-swift14:42
*** mvenesio_ has joined #openstack-swift14:45
*** tongli has joined #openstack-swift14:46
*** mvenesio has quit IRC14:48
*** zackf has joined #openstack-swift14:55
*** zackf has quit IRC15:00
*** zackf has joined #openstack-swift15:08
portantemvenesio: do you need disk speed, or capacity density?15:15
*** matsuhas_ has quit IRC15:17
*** nosnos has quit IRC15:21
*** ben_roeder has quit IRC15:24
mvenesio_portante: disk speed and capacity density :P15:24
mvenesio_portante: but at this time, disk speed15:24
portantewhat do you have for disk speeds on your drives now?15:25
portante54, 72, 100, ... 150?15:25
portantehow much money can I help you spend?!15:25
*** nshaikh has left #openstack-swift15:26
mvenesio_portante: nothing, i'm not using flashcache or something like that, we just have SATA3 disks and SSDs for account & container ops15:27
portanteI meant, 5,400 RPM, 7,200, etc.15:27
portanteare your objects large? and what do you have for network between clients and proxy, proxy and obj store?15:28
mvenesio_portante: 7,2k rpm toshiba SATA3 2TB drives with 64MB cache15:28
mvenesio_portante: we use 10GB interfaces, and our user case is billons of small objects15:29
*** xga has quit IRC15:29
mvenesio_portante: i'm from mercadolibre15:30
*** xga has joined #openstack-swift15:30
*** xga__ has joined #openstack-swift15:30
mvenesio_portante: we store all our site pictures in swift15:30
*** xga_ has quit IRC15:30
mvenesio_portante: just for know if you have some disk model that recommend us, or you tested SATA3 vs SAS in your environment.15:33
mvenesio_portante: the disks that we are considering now are seagate SAS 2TB with 128MB cache, constellation es3 series15:34
mvenesio_portante: money is not an issue with this mission critical clusters, but we must to find a good balance15:37
*** ben_roeder has joined #openstack-swift15:41
*** lpabon has joined #openstack-swift15:46
*** ben_roeder has quit IRC15:46
portantemvenesio_: let me look ...15:46
mvenesio_portante: thankss15:47
*** xga_ has joined #openstack-swift15:50
*** xga__ has quit IRC15:50
*** xga has quit IRC15:50
*** xga has joined #openstack-swift15:50
*** xga_ has quit IRC15:52
*** xga has quit IRC15:52
*** xga_ has joined #openstack-swift15:52
*** xga has joined #openstack-swift15:52
*** mvenesio_ has quit IRC16:02
*** zackf has quit IRC16:02
*** zackf has joined #openstack-swift16:03
portantemvenesio_: I have seagate's datasheet, at http://www.seagate.com/files/www-content/product-content/_cross-product/en-us/docs/storage-solution-guide-oct-13-ssg1351-14-1310us.pdf16:04
portanteis that what you using for the model names?16:04
portanteI want to be sure I am seeing the same drive information specs that you are16:04
notmynamegood morning16:07
*** mvenesio has joined #openstack-swift16:08
portantenotmyname: mornin'16:08
notmynameswift meeting time updated to be every week (same bat time, same bat channel)16:08
portantemvenesio:  I have seagate's datasheet, at16:08
portante           http://www.seagate.com/files/www-content/product-content/_cross-product/en-us/docs/storage-solution-guide-oct-13-ssg1351-14-1310us.pdf16:08
portantenotmyname: great, thanks16:08
notmynamemvenesio: FWIW, we've had some customers use seagate constellation drives (I'm not sure of the exact model number)16:08
notmynamemvenesio: in general, the "SSDs for account + container and SATA for objects" is a good strategy. are you seeing the disk IO as a bottleneck now? what's prompting you to look at new/different drives?16:09
mvenesionotmyname: humm there is not a special reason, our vendors are quoting us storage nodes with SAS 7.2rpm drives and we have no experience with this kind of drives in swift16:12
notmynameah. I don't think I know of anyone using SAS drives with Swift. not that it won't work, but it's just not too cost effective16:13
mvenesionotmyname: okkk, seems that there is not a significant difference between prices16:17
notmynamemvenesio: are you just looking at new stuff for your capacity expansion?16:17
mvenesionotmyname: yes16:18
mvenesionotmyname: we'll expand the pictures cluster to the maximun size16:18
notmynamemvenesio: cool16:18
notmynamemvenesio: what version of swift are you currently running?16:19
notmynameI know you've had it in prod for a long time16:19
mvenesionotmyname: yes we hope16:19
notmynamemvenesio: did you see the backblaze post on drives a few weeks ago? http://blog.backblaze.com/2014/01/21/what-hard-drive-should-i-buy/16:20
notmynamemvenesio: something else you may consider as you run later versions of swift is to test out the per-drive threadpool instead of your current "one object server process per drive" pattern16:23
*** byeager has joined #openstack-swift16:25
portantemvenesio: sorry I dropped off, client issues to my znc server16:30
*** xga__ has joined #openstack-swift16:31
*** xga has quit IRC16:32
*** xga_ has quit IRC16:32
*** mlipchuk has quit IRC16:36
*** xga has joined #openstack-swift16:36
mvenesionotmyname: sorry john, i was in a meeting16:37
mvenesionotmyname: i'll check that post16:37
notmynametalking in IRC during a meeting!?! I'm sure none of the rest of us have ever done that ;-)16:37
mvenesionotmyname: toxic meetings :P16:38
notmynamerunning funk tests http://www.youtube.com/watch?v=camNwgGXb4s16:41
*** ben_roeder has joined #openstack-swift16:42
*** bvandenh has quit IRC16:44
*** ben_roeder has quit IRC16:44
tristanChehe, that is a nice funky tune notmyname :)16:44
notmynameI wonder if I can trigger that to play every time I run functests in swift?16:45
mvenesionotmyname: we are running 1.8.0 grizzly release, and we are planning to migrate it to the 1.9 this year16:47
notmynamedon't stop at 1.9. we've already released 1.12 :-)16:47
mvenesionotmyname: ok we can go there, and believe me when i say that you will have new about that migration :P16:48
mvenesionotmyname: practically we will going  to live to your home16:49
*** gyee has joined #openstack-swift16:50
notmynamecome on! I've got some room downstairs ;-)16:50
notmynamemvenesio: just as long as you're ok with a 3 year-old waking up at 5:30am every day16:51
mvenesionotmyname: no problem we'll be coming back for a breakfast at that hour16:53
*** CrackerJackMack has quit IRC16:54
*** sudorandom has quit IRC16:55
*** zackf has quit IRC16:55
mvenesionotmyname, portante: Thanks for your help guys16:55
*** CrackerJackMack has joined #openstack-swift16:55
*** sudorandom has joined #openstack-swift16:56
*** zackf has joined #openstack-swift17:03
notmynamehmm, so it turns out that jenkins reports stopped jobs as failures to graphite17:03
*** portante has left #openstack-swift17:04
notmyname"sometimes it is reported as ABORTED, sometimes as FAILURE"17:04
notmynameso eg the recent dip in swift-gate-docs pass rate seen on http://not.mn/swift_gate_status.html is actually just the result of jobs being cancelled because of a gate reset17:05
*** xga has quit IRC17:05
*** xga__ has quit IRC17:05
*** xga__ has joined #openstack-swift17:05
*** xga has joined #openstack-swift17:05
*** portante has joined #openstack-swift17:05
*** ChanServ sets mode: +v portante17:05
*** portante has left #openstack-swift17:05
notmynameI'm seeing many links to http://java.dzone.com/articles/openstack-object-store-base on twitter this morning. all about using swift as the base for a video CDN17:09
*** tuxninja has joined #openstack-swift17:11
openstackgerritGreg Lange proposed a change to openstack/swift: Fix a comment in bulk middleware.  https://review.openstack.org/7160017:12
*** tuxninja has quit IRC17:17
brianclineis 1.13 planned to be the release coinciding with Icehouse just prior to summit?17:26
notmynamebriancline: either 1.13 or 1.14. depending on how the storage policy stuff goes these next 2 weeks, we may choose to do a release with everything just before storage policies lands (ie 1.13) and then another for icehouse (ie 1.14). or if storage policies is going really smoothly and lands more quickly than I expect, we may just have 1.13 of icehouse17:28
*** hurricanerix has joined #openstack-swift17:28
*** basha has joined #openstack-swift17:35
*** mvenesio has quit IRC17:42
*** basha has quit IRC17:42
*** mmcardle has quit IRC17:58
*** davidhadas_ has joined #openstack-swift18:01
*** xga has quit IRC18:02
*** xga__ has quit IRC18:02
*** davidhadas has quit IRC18:02
*** fbo is now known as fbo_away18:03
*** xga has joined #openstack-swift18:03
*** xga__ has joined #openstack-swift18:03
*** pberis has quit IRC18:13
*** pberis has joined #openstack-swift18:17
*** shri has joined #openstack-swift18:18
openstackgerritA change was merged to openstack/swift: Make .expiring_objects account name configurable  https://review.openstack.org/7097818:23
*** tuxninja has joined #openstack-swift18:27
*** bvandenh has joined #openstack-swift18:34
*** igor has quit IRC18:40
*** bvandenh has quit IRC18:40
*** shri1 has joined #openstack-swift18:42
*** igor has joined #openstack-swift18:44
*** shri has quit IRC18:44
*** shri1 has quit IRC18:45
brianclineok. thanks18:45
*** nacim has quit IRC18:53
*** byeager has quit IRC18:58
*** krtaylor has quit IRC19:01
*** mvenesio has joined #openstack-swift19:10
*** pberis has quit IRC19:13
*** pberis has joined #openstack-swift19:14
*** mef has quit IRC19:34
*** xga__ has quit IRC19:36
*** xga has quit IRC19:36
*** byeager has joined #openstack-swift19:39
*** byeager_ has joined #openstack-swift19:41
*** byeager has quit IRC19:44
*** foexle has quit IRC19:44
*** bsdkurt has quit IRC19:49
*** zackf has quit IRC19:54
*** lpabon has quit IRC19:59
*** mkollaro has quit IRC20:04
openstackgerritA change was merged to openstack/swift: Fix a comment in bulk middleware.  https://review.openstack.org/7160020:11
*** mkollaro has joined #openstack-swift20:16
*** mvenesio has quit IRC20:29
*** krast has quit IRC20:30
notmynameredbo: have you taken a look at the profiling middleware yet? https://review.openstack.org/#/c/53270/ kinda cool info20:36
*** krtaylor has joined #openstack-swift20:39
redbonope!  my guess is it's going to say swift is slow.20:41
*** krtaylor has quit IRC21:24
pelusenotmyname:  one of our guys here started messing with it, pretty cool21:26
notmynameindeed :-)21:28
pelusewe looked at a sample from some large obj runs yesterday - still some things to figure out wrt getting the output in a totally useful format but what was readable made sense.  He's going to keep messing around with it and I think using it/interpretting a run will be a great activity at the next hackathon21:30
*** byeager_ has quit IRC21:33
*** byeager has joined #openstack-swift21:44
notmynameat what point should we get in on the "replace eventlet" mailing list thread?21:45
torgomaticI think my least favorite commit in Swift is 4bc1b1f, but that's only because I'm really amused by the idea of a container borker.21:45
*** bsdkurt has joined #openstack-swift21:45
notmynamearen't container borkers another name for "users"21:46
torgomaticah, users... imagine the systems we could build if it weren't for those pesky users ;)21:49
*** portante has joined #openstack-swift21:53
*** ChanServ sets mode: +v portante21:53
*** shri has joined #openstack-swift22:02
*** bsdkurt has quit IRC22:03
*** bsdkurt has joined #openstack-swift22:06
notmynamecschwede: around?22:10
pelusenotmyname:  I've got a net 2 line change just waiting for your approval :)  https://review.openstack.org/#/c/70265/22:14
*** usvyatsky has joined #openstack-swift22:20
*** Trixboxer has quit IRC22:25
usvyatskyhi there22:29
openstackgerritJohn Dickinson proposed a change to openstack/swift: Limit logged headers in proxy_logging middleware  https://review.openstack.org/6436322:29
notmynameusvyatsky: hi22:29
usvyatskyI am looking for wire spec for kinetic protocol - is there such a thing?22:30
usvyatskythe reason being, I'd like to write a wireshark plugin for kinetic22:30
usvyatskyand all seagate supplies at the moment is just a binary library22:31
notmynamecool22:32
notmynameusvyatsky: you've looked at their simulator?22:32
usvyatskyyes, it's pretty neat22:32
usvyatskyunfortunately, it comes with either python bytecode API or Java bytecode jar22:32
usvyatskyor some sort of erlang API, of which I know nothing22:33
usvyatskyso the wire protocol remains hidden22:33
usvyatskyideally, I'd like to see a protocol spec or a source-code API library22:34
notmynamemy understanding is that it's "just protocol buffers", but I know that doesn't help too much22:35
notmynameyou still need the actual packet structure22:35
usvyatskyyes, as well as the protocol details w.r.t. authentication, handshakes and such22:35
notmynameusvyatsky: do you know anyone at seagate working on kinetic?22:40
usvyatskyunfortunately I don't22:40
notmynameusvyatsky: send me an email at me@not.mn and I'll introduce you to the guy writing the kinetic api22:40
usvyatskygreat, thank you very much!22:41
*** krtaylor has joined #openstack-swift22:43
usvyatskydone22:43
openstackgerritJohn Dickinson proposed a change to openstack/swift: Replace Policy Index with Policy Name in Response Headers  https://review.openstack.org/7026522:48
notmynamepeluse: done ^ (with the spelling error fixed)22:49
notmynameusvyatsky: fun with graylists. I havne't gotten it yet :-)22:50
notmynamepeluse: the constants at the top of storage_policy.py. I don't really like them because they are the names of headers, not a particular policy or policy index (which is what I assume every time I see them in the code somewhere).22:52
notmynamepeluse: appending "_HEADER_NAME" would make it explicit, but that of course will make things longer. obviously not a functional difference. just something I see every time I switch over to the ec branch22:53
pelusenotmyname:  OK, I can change those names in a separeate patch.  thanks23:00
notmynamepeluse: thanks. I guess I could have submitted a patch too, but now that you said you would...I don't have to! ;-)23:02
pelusehehe... BTW I do know how to spell, I just can't type for sh^*&t :)23:02
notmynameusvyatsky: done23:03
openstackgerritGreg Lange proposed a change to openstack/swift: Fix a comment in SLO middleware  https://review.openstack.org/7168223:14
notmynameglange: whew. good thing we got that one take care of23:15
dfgdammit notmyname23:15
notmynamelol23:15
glangethere are no small changes :)23:16
glangethey all have to run the gates23:16
notmynamelooks like the gate's only about 2 hours deep right now23:18
pelusenotmyname:  big box of stuff coming your way finally... check email23:25
*** mmcardle has joined #openstack-swift23:25
notmynamepeluse: just saw it! awesome.23:28
notmynamethey will go nicely with those 72 6TB helium drives I just got in the mail :-)23:28
*** mmcardle has joined #openstack-swift23:29
pelusecan you crack those open and suck out the gas I wonder?23:29
notmynamenegative shipping costs because they float?23:29
*** mmcardle has quit IRC23:29
pelusehehe... guess I cc'd Martin by accident - menat to add Mario....23:30
notmynameno worries. martin (mlanner) will be helping be rack and wire them up, I'm sure :-)23:31
peluseawesome.... no idea if there are any docs in the boxes but just let me know if there are hw questions and I'll get you to the right guys23:31
notmynamethanks23:31
usvyatskynotmyname: thank you very much!23:32
notmynamefor those of you wondering what's going on, new swift cluster for public community testing coming soon :-)23:32
*** byeager has quit IRC23:32
notmynameimagine! public CI tests on a real cluster!23:32
notmynamemore details when we get it all set up23:33
notmynameusvyatsky: np. hope you're able to get something23:33
pelusenow we just need to invent virtual tests to run on the real hw :)23:33
*** byeager has joined #openstack-swift23:58

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