Monday, 2012-10-01

*** danwent has joined #openstack-meeting00:12
*** littleidea has quit IRC00:15
*** littleidea has joined #openstack-meeting00:22
*** ryanpetrello has joined #openstack-meeting00:29
*** n0ano has quit IRC00:30
*** littleidea has quit IRC00:33
*** reed has joined #openstack-meeting00:35
*** lloydde has joined #openstack-meeting00:37
*** ryanpetrello has quit IRC00:44
*** littleidea has joined #openstack-meeting00:44
*** lloydde has quit IRC00:47
*** Gordonz has joined #openstack-meeting00:50
*** ryanpetrello has joined #openstack-meeting01:00
*** ryanpetrello has quit IRC01:01
*** lloydde has joined #openstack-meeting01:07
*** stevebake has quit IRC01:10
*** ryanpetrello has joined #openstack-meeting01:24
*** Gordonz has quit IRC01:26
*** littleidea has quit IRC01:28
*** littleidea has joined #openstack-meeting01:29
*** lloydde has quit IRC01:47
*** matiu has joined #openstack-meeting01:50
*** matiu has quit IRC01:50
*** matiu has joined #openstack-meeting01:50
*** littleidea has quit IRC02:04
*** littleidea has joined #openstack-meeting02:06
*** littleidea has quit IRC02:06
*** littleidea has joined #openstack-meeting02:07
*** tgall_foo has joined #openstack-meeting02:07
*** tgall_foo has joined #openstack-meeting02:07
*** jaypipes has joined #openstack-meeting02:09
*** dkehn_ is now known as dkehn_zzz02:29
*** ryanpetrello has quit IRC02:30
*** lloydde has joined #openstack-meeting02:30
*** Gordonz has joined #openstack-meeting02:56
*** lloydde has quit IRC02:58
*** dendrobates is now known as dendro-afk03:05
*** mikal has quit IRC03:06
*** mikal has joined #openstack-meeting03:08
*** s0mik has quit IRC03:13
*** koolhead17 has joined #openstack-meeting03:16
*** Gordonz has quit IRC03:29
*** hemna has quit IRC03:30
*** lloydde has joined #openstack-meeting03:33
*** tgall_foo has quit IRC03:42
*** koolhead17 has quit IRC04:25
*** littleidea has quit IRC04:33
*** s0mik has joined #openstack-meeting04:36
*** mikal has quit IRC04:37
*** mikal has joined #openstack-meeting04:40
*** lloydde has quit IRC04:54
*** s0mik has quit IRC05:48
*** srini_g has quit IRC05:48
*** stevebake has joined #openstack-meeting06:05
*** dolphm has joined #openstack-meeting06:20
*** stevebake has quit IRC06:46
*** stevebake has joined #openstack-meeting06:46
*** rafaduran has joined #openstack-meeting07:05
*** stevebake has quit IRC07:08
*** vishy has quit IRC07:22
*** vishy has joined #openstack-meeting07:22
*** cp16net has quit IRC07:22
*** cp16net has joined #openstack-meeting07:22
*** ameade_ has quit IRC07:22
*** ameade has joined #openstack-meeting07:23
*** nikhil has quit IRC07:23
*** markwash has quit IRC07:24
*** _cerberus_ has quit IRC07:24
*** nikhil has joined #openstack-meeting07:25
*** markwash has joined #openstack-meeting07:25
*** _cerberus_ has joined #openstack-meeting07:26
*** dolphm has quit IRC07:28
*** darraghb has joined #openstack-meeting07:47
*** stevebake has joined #openstack-meeting08:00
*** sdake has quit IRC08:01
*** shang has joined #openstack-meeting08:08
*** sdake has joined #openstack-meeting08:16
*** shang_ has joined #openstack-meeting08:21
*** stevebake has quit IRC08:23
*** shang has quit IRC08:23
*** ayoung has joined #openstack-meeting09:05
*** dprince has joined #openstack-meeting09:44
*** dprince has quit IRC09:50
*** jmichel has joined #openstack-meeting10:01
*** shang_ has quit IRC10:08
*** DuncanT has quit IRC10:15
*** DuncanT has joined #openstack-meeting10:16
*** shang_ has joined #openstack-meeting10:25
*** jamespage_ has joined #openstack-meeting10:51
*** dprince has joined #openstack-meeting10:55
*** jamespage_ has quit IRC11:10
*** ayoung has quit IRC11:14
*** sdake has quit IRC11:18
*** shang_ has quit IRC11:20
*** GheRivero is now known as Ghe_Rivero11:44
*** Ghe_Rivero is now known as GheRivero11:45
*** milner has joined #openstack-meeting11:45
*** maurosr has joined #openstack-meeting11:47
*** dwcramer has quit IRC11:49
*** garyk has joined #openstack-meeting12:05
*** dprince has quit IRC12:26
*** krtaylor has joined #openstack-meeting12:29
*** zykes- has quit IRC12:29
*** zykes- has joined #openstack-meeting12:32
*** sdake has joined #openstack-meeting12:49
*** sandywalsh has joined #openstack-meeting12:52
*** littleidea has joined #openstack-meeting13:02
*** martines_ has quit IRC13:12
*** matiu has quit IRC13:25
*** dkehn_zzz is now known as dkehn13:28
*** ttrifonov_zZzz is now known as ttrifonov13:31
*** tgall_foo has joined #openstack-meeting13:32
*** tgall_foo has joined #openstack-meeting13:32
*** ryanpetrello has joined #openstack-meeting13:33
*** matiu_ has joined #openstack-meeting13:38
*** matiu_ has joined #openstack-meeting13:38
*** markmcclain has joined #openstack-meeting13:39
*** mtreinish has joined #openstack-meeting13:40
*** dendro-afk is now known as dendrobates13:42
*** littleidea has quit IRC13:47
*** dhellmann-afk is now known as dhellmann13:49
*** AlanClark has joined #openstack-meeting13:59
*** dwcramer has joined #openstack-meeting14:02
*** koolhead17 has joined #openstack-meeting14:05
*** s0mik has joined #openstack-meeting14:17
*** Gordonz has joined #openstack-meeting14:37
*** Gordonz has quit IRC14:42
*** ozstacker has joined #openstack-meeting14:43
*** rnirmal has joined #openstack-meeting14:44
*** Gordonz has joined #openstack-meeting14:55
*** ryanpetrello has quit IRC14:55
*** ryanpetrello has joined #openstack-meeting14:56
*** cp16net is now known as cp16net|away14:58
*** mattray has joined #openstack-meeting14:59
*** cp16net|away is now known as cp16net14:59
*** s0mik has quit IRC15:04
*** hggdh has quit IRC15:04
*** ayoung has joined #openstack-meeting15:06
*** hggdh has joined #openstack-meeting15:07
*** jmichel has quit IRC15:14
*** Mandell has quit IRC15:21
*** primeministerp has joined #openstack-meeting15:21
*** mnewby has joined #openstack-meeting15:25
*** gatuus has joined #openstack-meeting15:28
*** hggdh has quit IRC15:31
*** danwent has quit IRC15:33
*** colinmcnamara has joined #openstack-meeting15:36
*** hemna has joined #openstack-meeting15:51
*** hggdh has joined #openstack-meeting15:53
*** shang has joined #openstack-meeting15:54
*** amotoki has joined #openstack-meeting15:58
*** GheRivero is now known as Ghe_Rivero15:58
*** rafaduran has quit IRC15:59
*** johnpur has joined #openstack-meeting16:02
*** amotoki has quit IRC16:05
*** amotoki has joined #openstack-meeting16:06
*** danwent has joined #openstack-meeting16:11
*** dwalleck has joined #openstack-meeting16:16
*** dwalleck has left #openstack-meeting16:16
*** martines has joined #openstack-meeting16:19
*** colinmcnamara has quit IRC16:19
*** s0mik has joined #openstack-meeting16:24
*** shang has quit IRC16:25
*** shang has joined #openstack-meeting16:27
*** hggdh has quit IRC16:31
*** shang has quit IRC16:34
*** shang has joined #openstack-meeting16:34
*** littleidea has joined #openstack-meeting16:47
*** sdake has quit IRC16:47
*** hemna_ has joined #openstack-meeting16:50
*** garyk has quit IRC16:51
*** hggdh has joined #openstack-meeting16:52
*** darjeeling has joined #openstack-meeting16:56
*** dolphm has joined #openstack-meeting16:59
*** Mandell has joined #openstack-meeting16:59
*** adjohn has joined #openstack-meeting17:01
*** PotHix has joined #openstack-meeting17:02
*** danwent_ has joined #openstack-meeting17:02
*** danwent has quit IRC17:03
*** danwent_ is now known as danwent17:03
*** stevebake has joined #openstack-meeting17:03
*** dolphm has quit IRC17:08
*** maoy has joined #openstack-meeting17:10
*** jdurgin has joined #openstack-meeting17:11
*** heckj has joined #openstack-meeting17:11
*** darjeeling has quit IRC17:15
*** darraghb has quit IRC17:15
*** jog0 has joined #openstack-meeting17:19
*** lloydde has joined #openstack-meeting17:19
*** gmb has quit IRC17:19
*** gholt has joined #openstack-meeting17:21
*** jog0 has quit IRC17:22
*** s0mik has quit IRC17:25
*** ayoung has quit IRC17:26
*** s0mik has joined #openstack-meeting17:27
*** ayoung has joined #openstack-meeting17:27
*** jog0 has joined #openstack-meeting17:32
*** jhenner has joined #openstack-meeting17:34
*** colinmcnamara has joined #openstack-meeting17:35
*** dkehn is now known as dkehn_brb17:46
*** danwent_ has joined #openstack-meeting17:52
*** jhenner has quit IRC17:53
*** danwent has quit IRC17:55
*** danwent_ has quit IRC17:56
*** s0mik has quit IRC17:56
*** stevebake has quit IRC17:59
*** troytoman-away is now known as troytoman18:03
*** maoy has quit IRC18:03
*** maoy has joined #openstack-meeting18:03
*** s0mik has joined #openstack-meeting18:04
*** troytoman has quit IRC18:05
*** troytoman-away has joined #openstack-meeting18:05
*** troytoman-away is now known as troytoman18:05
*** reed has joined #openstack-meeting18:09
*** s0mik has quit IRC18:09
*** mnewby_ has joined #openstack-meeting18:18
*** mnewby_ has quit IRC18:19
*** mnewby_ has joined #openstack-meeting18:19
*** mnewby has quit IRC18:21
*** mnewby_ is now known as mnewby18:21
*** dkehn_brb is now known as dkehn18:25
*** novas0x2a|laptop has joined #openstack-meeting18:32
*** troytoman is now known as troytoman-away18:42
*** tongli has joined #openstack-meeting18:43
*** salmon_ has joined #openstack-meeting18:48
*** colinmcnamara has quit IRC19:05
*** ryanpetrello has quit IRC19:08
*** ryanpetrello has joined #openstack-meeting19:08
*** antoine1 has joined #openstack-meeting19:09
*** danwent has joined #openstack-meeting19:13
*** troytoman-away is now known as troytoman19:14
*** s0mik has joined #openstack-meeting19:18
*** judd7 has joined #openstack-meeting19:22
*** ryanpetrello has quit IRC19:25
*** ryanpetrello has joined #openstack-meeting19:26
*** s0mik has quit IRC19:27
*** zaitcev has joined #openstack-meeting19:33
*** torgomatic has joined #openstack-meeting19:34
*** adjohn has quit IRC19:38
*** EmilienM has joined #openstack-meeting19:39
*** pandemicsyn has joined #openstack-meeting19:44
*** troytoman is now known as troytoman-away19:47
*** danwent has quit IRC19:55
*** colinnich has joined #openstack-meeting19:59
notmynameHi! Who's here for the swift meeting?20:00
notmynameok, let me get the meetbot set up20:01
notmyname#startmeeting swift community meeting20:01
openstackMeeting started Mon Oct  1 20:01:39 2012 UTC.  The chair is notmyname. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
openstackThe meeting name has been set to 'swift_community_meeting'20:01
notmynamewelcome and thanks for coming20:01
notmynamethere is an agenda at
notmynameand and etherpad doc at
*** sudorandom has joined #openstack-meeting20:02
notmynameGoal for this meeting: 1) wider dissemination of stuff to work on in swift and 2) determine what people will be working on over the next 6 months (openstack grizzly). This is also prep for the summit and how talks are scheduled and planned there.20:02
notmynamemy vision is for swift to be used by everyone, every day, whether they know it or not.20:03
notmynamegreat example of how this is being done today is through wikipedia and the recent iphone 5 event20:04
*** briancline has joined #openstack-meeting20:04
notmynameanyone who goes to wikipedia sees the media content served from a swift cluster, and the gdgt's liveblog of the iphone 5 event used swift (RAX cloud files) to serve up the content20:04
*** glange has joined #openstack-meeting20:05
notmynameTo help guide the discussion for today's meeting, I've listed out a bunch of ideas on the agenda and etherpad20:05
notmynameThese ideas have come from users and swift devs20:05
*** dfg_ has joined #openstack-meeting20:05
notmynameJust to cover the bases, just because I listed something here doesn't mean it will get implemented, nor does the absence of an item mean it won't get implemented.20:05
*** redbo has joined #openstack-meeting20:05
notmynameI'll be goving over each category in turn. please add your items as you see fit, and if you are interested in the feature, please add your name/org so we can keep a rough poll of what's important to who.20:05
*** adrian_smith has joined #openstack-meeting20:06
notmynameI think there are 4 broad areas for swift development20:06
notmynamehe first is focusing on new contributors20:06
notmynameThis helps swift in 2 ways. One, it adds momentum to the project by adding more devs and dev teams as contributors. Two, the process of making the codebase more friendly to new devs simply makes the codebase better for existing devs too.20:06
*** spligak has joined #openstack-meeting20:06
*** danwent has joined #openstack-meeting20:06
notmynameA good way to help new devs get involved is to provide and improve our getting started docs. Docs about the code organization, overall system design, and improvements around setting up and testing a dev environment would go a long way to facilitating new devs coming into the project.20:07
notmynameWould anyone like to work on this, or is there anything to add in this category?20:07
*** scotticus has joined #openstack-meeting20:07
notmynameThe second major area for swift development is focusing on new deployers. Deployers are the people who actually choose swift over alternatives and keep it running in production day in and day out. The features deployers look for have to do with automation, performance, and operational costs.20:08
zaitcevI think it's the usual place for new people to start.20:08
*** yuanz has joined #openstack-meeting20:08
notmynamezaitcev: docs or deployer concerns?20:08
ogelbukhwe've got some docs on swift internals here at Mirantis20:08
ogelbukhsome of them we've published to our blog20:08
*** dendrobates is now known as dendro-afk20:08
*** CrackerJackMack has joined #openstack-meeting20:08
notmynameogelbukh: cool. anything you can do to add some of those to the docs in the codebase?20:09
ogelbukhothers mostly internal materials and kb stuff20:09
zykes-hoii notmyname !20:09
ogelbukhnotmyname: if we can break down into subsections20:10
notmynameif anyone is interested in or working on the deployment category of things, please add your name/org there too20:10
ogelbukhI think we can try to list anything we have20:10
notmynameogelbukh: great20:10
zaitcevDeployment is also common to work on, I think. Here's one thingie, installs Swift among other things -
notmynamezaitcev: that's cool20:12
tongliguys, I've started looking at the multi-range support.20:12
brianclineis there interest enough in better docs for folks running swift on alternative *nix platforms, in addition to what's there today?20:12
ogelbukhregarding deployment, it's interesting to know the status of multi-region20:13
tongliI think that the getting started dev guide and few experienced swift developers taking turns really monitor the questions regarding the swift develoment will be good.20:13
notmynamebriancline: there are several things that have come up from time to time, but the core dev mostly see ubuntu+xfs20:13
*** aabes has joined #openstack-meeting20:14
notmynametongli: go ahead and add your name to the etherpad please20:14
*** aabes is now known as Guest8002420:14
notmynamebriancline: and the openstack CI testing isn't very broad as far as  differing platforms goes20:14
notmynamebriancline: so the biggest concerns are around supporting the code and regressions and reliable testing for it20:14
notmynameThe third major category of swift development focuses on client apps. As nice as a REST-based API is, the vast majority of users will never touch HTTP. Good client apps bring a healthy ecosystem to the project and help swift thrive.20:15
tonglijohn, you mean put my name after the feature?20:15
notmynameWhat can we do to provide tools an information to the people making the client apps so that they add swift support to their products?20:15
notmynametongli: ya, I saw you did. thanks20:15
*** s0mik has joined #openstack-meeting20:15
notmynameOne way is to encourage community language bindings (Rackspace has several, as do other deployers like SoftLayer and HP). We can also provide docs around how to design good swift clients and how to design data sets to be used with swift.20:16
notmynameI don't want to say that all swift needs is better docs, but there are areas where better docs would help ;-)20:16
ogelbukhit's hard to overestimate the importance of docs )20:17
adrian_smithAnother way to encourage client apps would be CORS compatibility20:17
brianclinenotmyname: is that due to lack of easily accessible expertise with alternative platforms and even distributions? would also be interested in hearing more offline about the details on support concerns20:17
pandemicsynapi docs with some sample apps, or maybe links to opensource apps might be handy20:17
notmynamebriancline: ya, that's part of it20:17
adrian_smithHas there been anything done on this recently?20:18
notmynamepandemicsyn: good idea, can you add it to the etherpad20:18
*** adjohn has joined #openstack-meeting20:18
notmynameI'll be using the etherpad to facilitate a similar discussion at the summit20:18
adrian_smithLast I checked we were looking to put this kind of thing out into a separate project rather than keep in in the core project.20:18
tonglihow about the idea I had above to have one take turns to supervise the doc and answer very technical questions, say like 1per a month?20:19
notmynameadrian_smith: there was a patch for it (was it yours?) but it never got merged20:19
notmynameadrian_smith: I don't immediately see why it would need to be in a separate project20:19
Guest80024some analysis / comparison to other storage solutions out there might be helpful to increase adoption20:19
adrian_smithnotmyname: it was yes. I meant to follow up and put it in a separate project but just haven't had a chance yet.20:19
notmynameadrian_smith: ah ok. ya, I'd love to see full CORS support for swift20:20
scotticusnotmyname: working on it.20:20
adrian_smithnotmyname: just rereading your review now,
notmynamescotticus: CORS? cool20:20
notmynamescotticus: you and adrian_smith should talk ;-)20:21
*** dendro-afk is now known as dendrobates20:21
*** jjm3lp has joined #openstack-meeting20:21
adrian_smithnotmyname: I'll try and take your comments into the next changeset20:21
notmynamemoving to the next big category...20:22
notmynameThe fourth major area is a focus on new end users. The end users are ultimately why we're working on this. This category is for things that are user-facing. Users want features to meet a specific pain point or to open up new use cases for the storage. For example, on-disk encryption is a pain point for some users for compliance reasons. On the other hand, a tiered storage cluster would allow swift to solve some new use cases.20:22
*** salv-orlando has joined #openstack-meeting20:22
ogelbukhwe've done a design for on-disk encryption as a part of joint effort with Webex20:23
notmynameogelbukh: ya, I came across your blog post this morning20:23
ogelbukhthere's a link to blog on it20:23
notmynameogelbukh: do you have an implementation for it yet?20:23
ogelbukhnot ready to publish it yet20:24
notmynameogelbukh: also, I'd love for you to submit a proposal to talk about it at the design summit (
ogelbukhbut we're working on it20:24
adrian_smithogelbukh: could you post a link to your post. sounds interesting. love to see how you manage keys.20:24
notmynameFinally, there's the "catch-all" of "make swift more awesome". These are things like code refactorings, speed improvements, and system support. These are issues that get a lot of attention from the swift devs since it's what we deal with on a daily basis. These are things that will always be improved and will make up the largest number of commits in any swift release.20:24
creihtyeah the encryption part is pretty easy, the key management is where things get sticky20:24
ogelbukhyes, that's the hardest part20:25
ogelbukhfor the initial implementation it's very simple20:25
creihtI've wondered if it would deserve its own service20:25
glangekeys as a service?20:25
ogelbukhwe need pluggable back-end there eventually20:25
judd7is keystone a hard requirement these days?20:26
notmynamejudd7: for swift? it's never been a requirement for running swift20:26
creihtI imagine keys are going to be more important in the other projects20:26
ogelbukhnot really hard, i believe20:26
zaitcevKeystone is not a requirement to run Swift but some distros may pull it in as a dependency.20:26
Guest80024you're thinking of having keystone serve out keys?20:26
CrackerJackMackGuest20200: seems like a fit20:26
judd7it's in the name. :)20:26
Guest80024might make sense - having tenant level keys + user level keys might make much sense20:27
judd7As long as we need ANOTHER key management project in the universe, it might as well be in keystone.20:27
judd7Unless the keystone devs want to make that a pluggable backend too.20:28
judd7Which is fine.  Would help corporate adoption.20:28
creihtall things are pluggable in openstack right?20:28
notmynamecreiht: isnt' it all middleware?20:28
redboencryption is "easy"20:28
*** primeministerp has quit IRC20:28
judd7"keep your keys in verisign's or whomsoever's safe."20:29
judd7"we default to sqlite.20:29
creihtjudd7: yeah20:29
creihtI haven't done very much research in that area though20:29
*** mattray has quit IRC20:30
notmynameis there any work being done on this already in keystone?20:30
judd7I might pull something together.  Dell has/needs that data for our own efforts.20:30
*** milner has quit IRC20:30
notmynamejudd7: cool. also, submit a talk for it for the summit :-)20:30
judd7And by "pull together" I merely mean names/versions of customers who have at least asked us about it.20:30
redbothere are some big concerns I have about encryption20:31
*** mattray has joined #openstack-meeting20:31
Guest80024seems that mirantis is already doing a talk about their arch20:31
ogelbukhredbo: could you please share some?20:32
notmynameGuest80024: ogelbukh: not in the technical tracks though20:32
notmynamewhat else in the feature list or category list would you like to discuss before moving on to the summit plans?20:32
redboif it's implemented as middleware, I'm assuming you'll lose the ability to serve ranges inexpensively20:32
redboas opposed to something like an encrypted block device20:33
adrian_smithunique-as-possible data placement is really interesting20:33
Guest80024(reading the blog) - they encrypt each block seperatly20:33
Guest80024not block - each chunk.20:33
ogelbukhyes, it's by-chunk20:33
adrian_smithit really opens the door for distributed clusters20:33
notmynameredbo: ogelbukh: we've got an implementation at swiftstack that uses LUKS devices20:33
notmynameadrian_smith: ya, the unique-as-possible is really cool. it's already in swift, but it needs to be expanded somewhat for the global clusters20:34
redbomy other concern is mostly CPU usage20:34
ogelbukhshould be actually faster then middleware encryption20:35
ogelbukhhowever, it's all or nothing20:35
Guest80024can you elaborate on unique-as-possible?20:35
*** colinmcnamara has joined #openstack-meeting20:35
Guest80024(i.e. link?)20:35
adrian_smithnotmyname: sure. it's a really attractive feature. looking forward to seeing where it goes20:35
ogelbukhsome range of options here )20:35
*** hemna has quit IRC20:36
adrian_smithGuest80024: described here,
notmynameadrian_smith: thanks20:36
Guest80024there was some talk about dedup within swift...20:37
notmynameso, anything else before we move on to the summit plans? (summit plans discussion should be short)20:37
Guest80024is that on anyone's radar?20:37
tongliwhat do you mean by remove webob?20:37
notmynameGuest80024: it's possible (anything's possible!) but probably unlikely20:37
notmynametongli: redbo has an outstanding patch to do so. basically, webob keeps breaking us with every version bump20:38
Guest80024there was a Msc dude in portogal that started circulating a proposal that got some traction on the ML20:38
notmynametongli: it's a pain to amange20:38
tonglii c. I remember once that the HEAD operation failed. had to apply a patch.20:38
notmynametongli: and has annoying "magic properties" that do stuff when you don't expect it to (like content-type and charset setting)20:38
pandemicsyn - swob20:39
notmynameok, summit plans20:39
notmynameI hope you are all going to the summit, but I know some of you won't be there20:40
tongliquite big change. so it will be merged?20:40
*** lloydde has quit IRC20:40
notmynameplease submit your talk proposals at http://summit.openstack.org20:40
notmynameyou can also see what's currently proposed there20:40
Guest80024nexenta put out a detailed proposal for the dedup stuff.. not sure it ever went anywhere:
notmynameWe've got a swift track all day on monday (8 slots) and possibly 2 more slots on tuesday morning. The sessions are intendend to be for community feature dev work, but in the past we have also had talks on design overviews and in-depth discussions on how existing features work.20:40
notmynamethere are some additional workshop sessions that will cover some swift topics, so there should be some very good swift content at this summit20:41
notmynameis anyone planning on submitting talks that hasn't done so already (we've only had 3 people submit talks so far)20:42
Guest80024can i float an idea here?20:42
notmynameI'd like to see one from ogelbukh on the encryption. perhaps someone from rax or adrian_smith on CORS20:43
notmynameGuest80024: sure20:43
Guest80024automatic ring adjustment for add/remove disks, with timed, gated adjustment of disk weights20:43
tongliI would love to see someone talks about the ring generation in details and how we can make that automated in the future.20:43
tongli@Guest80024, are we thinking about the same thing?20:43
Guest80024there are a few tools out there that do generation.20:44
Guest80024the problem is maintaining.... and adjusting to changes in available disks/servers20:44
notmynamepandemicsyn: arent' you working on soemthing like that? the ring-server?20:44
judd7Guest80024: can you list some of those tools?20:44
ogelbukhpersonally I won't be able to attend, but mirantis will do the talk about it20:44
tongliI would like to see a talk about ring and ring related session.20:44
notmynameogelbukh: cool. please try to get something on the summit page, even a placeholder ASAP20:44
pandemicsynnotmyname: ring server just lets you add/remove/manage devices , doesn't manage rebalance/deployments20:45
ogelbukhon the ring generation, we've done some things in puppet20:45
ogelbukhbased on current stuff but slightly modified20:45
zaitcev says that SwiftStack's cluster management has "add gradually" mode20:45
judd7I did (in a previous life) ring management with chef+rundeck.  It was cool.20:45
Guest80024I was talking about crowbar20:45
notmynametongli: we're doing a meetup in sunnyvale next week about that :-)20:45
Guest80024but it's not yet updated for the smarter folsom ring20:46
tongliyeah, in Raleigh NC, can not attend.20:46
*** EmilienM has quit IRC20:46
notmynamePlease go to your org and campaign for what is important to you. And bring other ideas to the summit. :-)20:46
Guest80024(and IRC is being stupid about letting me use my handle for some reason.. its aabes_)20:46
tongliit will be nice to have some one write up something for a session not only about the ring in current implementation, but also look at the future and some options to improve20:46
notmynametongli: ya, we can look into something about that20:47
Guest80024if there's interest in having a discussion about my suggestion, I'll submit a summit session.20:47
notmynameGuest80024: I'm interested. please submit it :-)20:47
notmynameAnd now to the last item on the agenda: are there any outstanding concerns or questions about swift that I can answer or work on, on your behalf?20:47
Guest80024better deployment consideration documentation?20:48
zaitcevnotmyname: I added it to Etherpad - do you know if gholt is going to continue on Swiftly?20:48
notmynamegholt: around and want to answer?20:48
pandemicsynzaitcev: not sure if gholt is around today (hes got bird flu or something)20:48
glangenotmyname: he's been out sick today20:49
notmynamezaitcev: swiftly is a community or ecosystem thing20:49
pandemicsynbut we use swiftly alot at $RAX20:49
zaitcevI'm sick of the client CPU burn, so I was going to have a look. Not sure if it should go into python-swiftclient or perhaps he's already solved it.20:49
notmynamezaitcev: ya, talks around the client certainly would be appropriate at the summit too20:49
Guest80024haven't looked recently - how's the swift support in fog?20:50
zaitcevNot coming to Summit this time sadly20:50
*** scotticus has left #openstack-meeting20:50
torgomaticzaitcev: the client CPU burn can, in principle, be cleaned up provided that it doesn't have to run on Python <= 2.420:50
*** markvoelker has joined #openstack-meeting20:50
zykes-still swift meeting notmyname ?20:51
notmynamezykes-: ya20:51
notmyname9 minutes left. anything I can address, either with swift or openstack-related? also, feel free to email me at me@not.mn20:52
creihtnotmyname: I may have another one, but I can't talk about it yet :)20:52
creiht(summit talk)20:52
notmynamecreiht: cool20:52
swifterdarrellzaitcev: torgomatic: I think I've fixed at least one Queue busy-waiting in python-swiftclient's swift20:52
notmynamecreiht: when will you be able to?20:52
Guest80024notmyname: fog support for swift?20:52
notmynameGuest80024: I'm not a ruby dev, so I haven't kept up to date on fog support20:53
Guest80024just checked, doesn't seem to be there.. there's rax and s320:53
notmynameGuest80024: RAX == swift20:53
Guest80024keystone auth?20:53
notmynameassuming it let's you set the auth endpoint20:53
creihtnotmyname: be able to?20:53
zaitcevswifterdarrell, I'll check if it's the same. I saw a problem with SSL enabled.20:53
creihtI have an idea of something that I want to talk about, but have to run it by some people here first20:54
notmynamecreiht: able to talk about it20:54
*** AlanClark has quit IRC20:54
notmynameok, let me knwo20:54
*** colinmcnamara has quit IRC20:54
creihtahh... it is probably best that I don't yet :)20:54
*** AlanClark has joined #openstack-meeting20:54
notmynameoh the suspense ;-)20:54
judd7We wont tell anyone.20:54
notmynameok, let's go ahead and wrap this up so that the next meeting can start20:54
brianclinedon't worry, this definitely isn't logged20:55
swifterdarrellzaitcev: may be unrelated--I was referring to CPU burn related to busy-waiting on threads/Queues; one place has been changed and as torgomatic pointed out, there are several left to fix20:55
*** dwalleck_ has joined #openstack-meeting20:55
judd7Thanks notmyname, pandemicsyn20:55
swifterdarrellzaitcev: but that's probably unrelated to something re: SSL?20:55
notmynameThanks for your time. We all work for different organizations. Please go to your org and campaign for what is important to you. And bring other ideas to the summit. Looking forward to seeing you there.20:55
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"20:56
openstackMeeting ended Mon Oct  1 20:56:03 2012 UTC.  Information about MeetBot at . (v 0.1.4)20:56
ogelbukhnotmyname: thanks for the opportunity20:56
openstackMinutes (text):
ogelbukhthanks everyone )20:56
*** adrian_smith has quit IRC20:56
*** dwalleck_ has quit IRC20:56
*** redbo has left #openstack-meeting20:56
*** zaitcev has left #openstack-meeting20:56
*** dwalleck_ has joined #openstack-meeting20:57
*** heckj has quit IRC20:57
*** yuanz has left #openstack-meeting20:58
*** dwalleck_ has quit IRC20:58
*** colinnich has quit IRC20:58
zykes-danwent: are you alive or ?20:58
zykes-wrong channel though but20:58
danwentzykes-: i'm just busy.  if you have a bug, best to use LP for that.20:59
*** glange has left #openstack-meeting20:59
*** nati_ueno has joined #openstack-meeting21:00
*** CrackerJackMack has left #openstack-meeting21:00
danwenthi folks… channel is looking a little dead today :)21:00
danwent#startmeeting quantum21:01
openstackMeeting started Mon Oct  1 21:01:05 2012 UTC.  The chair is danwent. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
openstackThe meeting name has been set to 'quantum'21:01
*** antoine1 has quit IRC21:01
danwent#link agenda:
danwentshould be a pretty short meeting today… I assume people are still recovering from the release :)21:01
*** dwalleck has joined #openstack-meeting21:01
danwent#info Quantum Folsom release is out!  Congrats to the whole team!21:01
zykes-danwent: or just hiding ;)21:02
danwent#info all bugs found that may be considered for backport to Folsom should be fixed in master and have the bug tagged with 'folsom-backport-potential'21:02
* markvoelker cheers21:02
*** ijw has joined #openstack-meeting21:02
danwenthere is the current list:
*** Guest80024 has quit IRC21:03
*** dfg_ has left #openstack-meeting21:03
danwentso far there is nothing i've seen of significant concern, so we'll hold off on a stable release until either a bunch of small things pop-up, or there is a major issue that we feel we need to address urgently.21:03
danwent#help  we're looking for people to help manage the stable/folsom branch and keep track of what fixes need to be back-ported, decide on timing of stable releases, etc.21:04
danwentI believe rkukura or garyk worked on this in the past21:04
*** antoine1 has joined #openstack-meeting21:04
*** tongli has quit IRC21:05
danwentneither of them seem to be here today, but if others are interested in helping out as well, let me know.  the more the merrier in my opinion.21:05
danwentThere was also a ton of great work that went into creating content for the openstack docs in the past week.21:05
danwentI believe the major gaps we outlined have for the most part been closed.21:06
annegentlenice job all!21:06
*** mtreinish has quit IRC21:06
danwent#info any remainning doc issues should be filed against the openstack-manuals project and tagged with 'quantum' (for the quantum admin guide) and 'netconn-api' for the API guide.21:06
*** mcohen has joined #openstack-meeting21:07
danwenthere are the existing links:
*** koolhead17 has quit IRC21:07
*** colinmcnamara has joined #openstack-meeting21:07
amotokiwhat is the status of netconn-api?21:07
danwentwe'll want to be very vigilent that if someone asks something on the mailing list, and we can't answer by pointing to a section of either of those two docs, then we should probably be filing a bug to add that content to one of the guies.21:07
danwentsalv-orlando: ?21:08
*** pandemicsyn has left #openstack-meeting21:08
salv-orlandoamotoki: we have a final patch in WIP for l3 extension21:08
salv-orlandoand then we still need to document the Quota extension21:08
amotokihave you solved the problem in
danwentsalv-orlando: can you create netconn-api bugs for those if there aren't already?21:08
salv-orlandoApart from that, it is complete (pending bugs and errors that you guys might find)21:08
danwentor rather openstack-manuals bugs, tagged with netconn-api21:08
salv-orlandodanwent: already created, probably not tagget21:08
danwentah, makes sense.21:09
salv-orlandoamotoki: should have been transient failure as this morning a patch dependent on this built fine. Let me do a recheck.21:09
danwentOk, any other topics to discuss on Folsom release or docs?21:09
ijwPer what I said earlier today on the list, if there's not Python API stuff in the docs then there probably ought to be (I haven't looked at the Quantum docs specifically)21:09
amotokisound good.21:09
*** maurosr has quit IRC21:10
danwentijw: i'm not sure what the right place for such content is.21:10
*** markvoelker1 has joined #openstack-meeting21:10
ijwYeah, indeed.  Not with the web API itself, I guess, but it ought to be somewhere.21:11
danwentI want to keep the API spec relatively clean and focused on the rest calls.  I assume you're looking for something that documents the python bindings?21:11
*** dwalleck has quit IRC21:11
danwentijw: agreed...21:11
salv-orlandodanwent, ijw: looking at your email seems you're looking for developer docs21:11
*** antoine1 has left #openstack-meeting21:11
danwentwell, there's two types of that salv-orlando21:11
danwentone is for building quantum itself, and another is for calling its APIs, but via python bindings21:11
danwenti thought ijw  was talking about API bindings for python21:12
salv-orlandoI meant the second one - aimed at developers wishing to use quantum21:12
annegentleall the colors of the rainbow developers :) Really just red (API) or blue (Python).21:12
annegentleor the purple ones who are both21:12
ijwI'm talking about the Python bindings - I think there should be a straightforward docstring extraction (assuming anyone gives the docstrings love when they write things) plus an explanation of how the API is used, and a pointer so that it can all be found.  But I'll take what I can get ;)21:13
annegentleijw: I think the current problem your issue raises is that the docstrings are not getting love in certain projects - haven't examined quantum to know if they <3 docstrings21:14
danwentI think the reality is that there is no documented, stable API other than the webservice API itself.21:14
ijwannegentle: actually, there's the open question of whether they should be called at all - nothing says it's public21:14
*** markvoelker has quit IRC21:14
annegentleijw: and "public" is whether the endpoint is public (based on what the cloud provider deploys)?21:14
danwentwe could push for certain APIs within python-quantumclient to be those APIs, but at this point, I'm not aware of stabilitization promises around that.21:15
danwentI think this is a good point though21:15
annegentleijw: or governed by policy (again from the cloud provider)21:15
amotokiijw: horizon/api/ is a good example if you want to know how to use python-quantumclient.21:15
ijw'Public' as in 'we expect to maintain compatibility'21:15
*** torgomatic has left #openstack-meeting21:15
ijwannegentle: since the Python bindings are relatively divorced from the web API you have to have some assurance that they're going to be stable.21:15
annegentleijw: ok, understood21:16
danwentthis might be a good topic for future discussion, as I agree that (a) there is potential value in a stable python API and (b) that we make no such promises at this point.21:16
danwentijw: do you want to discuss this @ summit?21:16
danwentor simply create a BP around it if you don't think there's much to discuss21:16
ijwYes, and I don't think it's just a quantum thing, so a wider audience might be a good idea21:16
*** heckj has joined #openstack-meeting21:17
danwentijw: yeah, ideally we'd have consistency in terms of the behavior of these python APIs across projects.  I suspect that is far from the case right now.21:17
*** aclark_ has joined #openstack-meeting21:17
danwentijw: definitely consult with Yong on this too, as he created most of the latest rev of the client, I think.21:18
*** heckj has quit IRC21:18
danwent(he doesn't seem to be here today… post folsom vacation I guess)21:18
*** AlanClark has quit IRC21:18
danwentOk, so moving on...21:18
salv-orlandodanwent: or probably finally enjoying the comfort of his bed at 5 in the morning :)21:18
danwentperhaps :P21:19
danwent#topic quantum tempest + gating21:19
*** openstack changes topic to "quantum tempest + gating"21:19
danwentI wanted to revive this discussion now that folsom is out.  I think its probably the most important thing our team needs to be focused on now, so I wanted to figure out where we were, and what we needed to plan for at the summit21:19
danwentmnewby nati_ueno any info?21:20
nati_uenoHere is meeting log
nati_uenoWe are discussing after openstack-qa meeting21:20
danwentnati_ueno: ah, ok, there's another meeting coming up soon?  when is that?21:21
danwenti saw the existing tempest review expire, so I wasn't sure if people were still actively working on it.21:21
nati_uenoIt is not formal meeting21:21
nati_uenodanwent: Ah sorry. I was in bussiness trip to Japan. So I haven't progressed the work yet.21:21
danwentnati_ueno: can you work with mnewby, folks from tempest, and the CI team to make sure we have a session on this at the summit?21:22
nati_uenodanwent: Sure21:22
danwentwe can put it on the quantum track and invite others21:22
danwent#todo nati_ueno create summit session around quantum tempest efforts + gating21:23
danwent#topic grizzly summit21:23
*** openstack changes topic to "grizzly summit"21:23
danwentsummit is two weeks away21:23
*** maoy has quit IRC21:23
danwentwe will want session schedule finalized by early next week21:23
danwent(well, sometimes individual slots change last minute, but our general set of topics should be set by then)21:24
danwent#info quantum summit sessions are mon/tues/wed21:24
danwentno sessions thurs21:24
danwent#info  to propose sessions, use:
danwenta couple reminders here, as people always go a bit crazy around summit time21:25
danwentfirst, its not about who proposes a session first… if multiple people want to talk on the same topics, we'll commonly merge sessions one all sessions have been proposed21:25
danwentwe need a healthy balance of "community projects" vs. "shiny objects"… topics like system test, horizon integration, HA improvements, etc. are very important to average users21:26
danwentas I mentioned before, we really need to focus on system test/ tempest + gating.  to me this is the biggest gap for us right now.21:27
danwentone particular "shiny object" that peopel are already creating a lot of content around is "load-balancer-as-a-service"21:27
danwent#info content for load-balancer as a service discuss is being put here:
danwentfeel free to add your own thoughts21:28
*** markvoelker1 has quit IRC21:28
salv-orlandoI would also add "do not refresh the web page after submitting a session" :)21:28
*** markvoelker1 has joined #openstack-meeting21:28
amotokiI made a mistake already :-(21:29
danwentover the past few months I've been keeping a list of good community topics… i'll send out an email with those items.21:29
danwentI'll be asking people to organize sessions around many of those topics.21:29
*** devananda has quit IRC21:29
danwentany other questions/comments on summit proposals?21:29
zykes-danwent: which one of the lbaas projects is it? the mirantis one or ?21:30
nati_uenoI would like to propose quantum-scheduler session21:30
danwentzykes-: there are several different proposals for lbaas, all on that page.21:30
nati_uenoIt may be merged to HA session21:30
danwentnati_ueno: sure, just propose session for now, and we'll figure out what sessions may make sense to merge once that is done.21:31
nati_uenodanwent: I got it21:31
danwent#topic open discussion21:31
*** openstack changes topic to "open discussion"21:31
danwentany other comments/questions? or will this be the shortest meeting ever? :)21:31
danwentok, that's a wrap.  thanks folks.  look for email about community topics for the summit21:32
danwentwe'll finalize the list early next week.21:32
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"21:32
openstackMeeting ended Mon Oct  1 21:32:48 2012 UTC.  Information about MeetBot at . (v 0.1.4)21:32
openstackMinutes (text):
danwentworld record time :)21:32
mesterylater folks!21:32
amotokithank folks!21:33
markvoelker1Night all!21:33
*** markvoelker1 has quit IRC21:33
*** nati_ueno has quit IRC21:33
*** nati_ueno has joined #openstack-meeting21:34
*** hemna_ has quit IRC21:34
*** amotoki has left #openstack-meeting21:34
*** nati_uen_ has joined #openstack-meeting21:35
*** Vinay has joined #openstack-meeting21:35
*** Vinay is now known as Guest6082921:35
*** Guest60829 has quit IRC21:38
*** mcohen has left #openstack-meeting21:38
*** tgall_foo has quit IRC21:38
*** nati_ueno has quit IRC21:38
*** vbannai has joined #openstack-meeting21:39
*** danwent has quit IRC21:39
*** hemna has joined #openstack-meeting21:40
*** danwent has joined #openstack-meeting21:40
*** dwalleck has joined #openstack-meeting21:44
*** dwalleck has left #openstack-meeting21:45
*** amotoki has joined #openstack-meeting21:47
*** dwalleck_ has joined #openstack-meeting21:47
*** rnirmal has quit IRC21:48
*** amotoki has left #openstack-meeting21:49
*** blamar_ has joined #openstack-meeting21:50
*** blamar has quit IRC21:50
*** blamar_ is now known as blamar21:50
*** rkukura has joined #openstack-meeting21:50
*** ijw1 has joined #openstack-meeting21:55
*** huats has quit IRC21:55
*** huats has joined #openstack-meeting21:56
*** huats has quit IRC21:56
*** huats has joined #openstack-meeting21:56
*** ijw has quit IRC21:57
*** nati_uen_ has quit IRC22:01
*** sudorandom has left #openstack-meeting22:01
*** nati_ueno has joined #openstack-meeting22:02
*** gholt has left #openstack-meeting22:02
*** dwalleck_ has quit IRC22:04
*** mnewby has quit IRC22:07
*** salmon_ has quit IRC22:08
*** dwcramer has quit IRC22:10
*** salv-orlando has quit IRC22:15
*** aclark_ has quit IRC22:17
*** lloydde has joined #openstack-meeting22:17
*** tgall_foo has joined #openstack-meeting22:20
*** tgall_foo has joined #openstack-meeting22:20
*** dendrobates is now known as dendro-afk22:24
*** milner has joined #openstack-meeting22:29
*** dendro-afk is now known as dendrobates22:35
*** Gordonz_ has joined #openstack-meeting22:37
*** EmilienM has joined #openstack-meeting22:38
*** Gordonz has quit IRC22:40
*** rkukura has quit IRC22:41
*** EmilienM has left #openstack-meeting22:41
*** tgall_foo has quit IRC22:42
*** markmcclain has quit IRC22:44
*** sdake has joined #openstack-meeting22:46
*** SumitNaiksatam has joined #openstack-meeting22:46
*** spligak has quit IRC22:46
*** SumitNaiksatam has quit IRC22:47
*** dkehn is now known as dkehn_away22:48
*** cdub has quit IRC22:50
*** cdub has joined #openstack-meeting22:50
*** danwent has quit IRC22:56
*** blamar has quit IRC23:01
*** danwent has joined #openstack-meeting23:01
*** blamar has joined #openstack-meeting23:02
*** mattray has quit IRC23:04
*** nati_uen_ has joined #openstack-meeting23:11
*** huats has quit IRC23:12
*** nati_ueno has quit IRC23:15
*** huats has joined #openstack-meeting23:17
*** huats has quit IRC23:17
*** huats has joined #openstack-meeting23:17
*** gatuus has quit IRC23:20
*** shang has quit IRC23:20
*** lloydde has quit IRC23:28
*** hemna has quit IRC23:34
*** vbannai has quit IRC23:35
*** adjohn has quit IRC23:42
*** colinmcnamara1 has joined #openstack-meeting23:42
*** colinmcnamara has quit IRC23:45
*** reed has quit IRC23:46
*** colinmcnamara1 has quit IRC23:47
*** danwent has quit IRC23:59

Generated by 2.14.0 by Marius Gedminas - find it at!