Wednesday, 2013-05-01

*** lindj_ has quit IRC00:00
*** armax has quit IRC00:06
*** gyee has quit IRC00:06
*** ryanpetrello has joined #openstack-meeting00:11
*** danwent has quit IRC00:11
*** kebray has quit IRC00:12
*** sandywalsh has quit IRC00:16
*** markpeek has joined #openstack-meeting00:27
*** markpeek has quit IRC00:31
*** lloydde has quit IRC00:31
*** danwent has joined #openstack-meeting00:37
*** salv-orlando_ has joined #openstack-meeting00:38
*** salv-orlando has quit IRC00:38
*** salv-orlando_ is now known as salv-orlando00:38
*** salv-orlando_ has joined #openstack-meeting00:39
*** salv-orlando has quit IRC00:39
*** salv-orlando_ is now known as salv-orlando00:39
*** garyTh has quit IRC00:40
*** lindj_ has joined #openstack-meeting00:40
*** dolphm has quit IRC00:45
*** sandywalsh has joined #openstack-meeting00:49
*** colinmcnamara has quit IRC00:57
*** Mandell has quit IRC01:02
*** reed has joined #openstack-meeting01:06
*** ijw1 has quit IRC01:15
*** dolphm has joined #openstack-meeting01:16
*** colinmcnamara has joined #openstack-meeting01:16
*** terry7 has quit IRC01:20
*** dolphm has quit IRC01:24
*** salv-orlando has quit IRC01:27
*** maoy has joined #openstack-meeting01:29
*** dolphm_ has joined #openstack-meeting01:31
*** dolphm_ has quit IRC01:32
*** vkmc has quit IRC01:35
*** dolphm has joined #openstack-meeting01:36
*** sacharya has joined #openstack-meeting01:39
*** cp16net is now known as cp16net|away01:42
*** hartsocks has quit IRC01:43
*** markmcclain has quit IRC01:46
*** jrodom has joined #openstack-meeting01:49
*** fnaval has joined #openstack-meeting01:52
*** jrodom has quit IRC01:53
*** colinmcnamara has quit IRC01:53
*** danwent has quit IRC02:06
*** jrodom has joined #openstack-meeting02:06
*** danwent has joined #openstack-meeting02:07
*** colinmcnamara has joined #openstack-meeting02:07
*** FnordDownUnder has quit IRC02:10
*** kgriffs has joined #openstack-meeting02:14
*** anniec has quit IRC02:16
*** dwcramer has quit IRC02:16
*** danwent has quit IRC02:19
*** ladquin has quit IRC02:27
*** novas0x2a|laptop has quit IRC02:29
*** ryanpetrello has quit IRC02:29
*** cp16net|away is now known as cp16net02:34
*** alexpilotti has joined #openstack-meeting02:38
*** lbragstad has joined #openstack-meeting02:38
*** dolphm has quit IRC02:40
*** lbragstad has quit IRC02:44
*** jrodom has quit IRC02:46
*** jrodom has joined #openstack-meeting02:46
*** lbragstad has joined #openstack-meeting02:46
*** jbresnah has quit IRC02:49
*** dkehn_ has joined #openstack-meeting02:55
*** dkehn has quit IRC02:57
*** dkehn__ has joined #openstack-meeting02:59
*** markpeek has joined #openstack-meeting02:59
*** saurabhs has joined #openstack-meeting03:00
*** dkehn_ has quit IRC03:00
*** dkehn__ is now known as dkehn03:01
*** saurabhs has quit IRC03:01
*** ryanpetrello has joined #openstack-meeting03:01
*** ryanpetrello has quit IRC03:02
*** dragondm has quit IRC03:06
*** Mandell has joined #openstack-meeting03:07
*** dragondm has joined #openstack-meeting03:07
*** jrodom_ has joined #openstack-meeting03:13
*** jrodom_ has joined #openstack-meeting03:13
*** bdpayne has quit IRC03:14
*** jrodom has quit IRC03:15
*** Mandell has quit IRC03:21
*** Mandell has joined #openstack-meeting03:23
*** kgriffs has quit IRC03:24
*** kgriffs has joined #openstack-meeting03:25
*** RajeshMohan has quit IRC03:28
*** RajeshMohan has joined #openstack-meeting03:28
*** dwcramer has joined #openstack-meeting03:29
*** kgriffs has quit IRC03:33
*** novas0x2a|laptop has joined #openstack-meeting03:34
*** jrodom_ has quit IRC03:38
*** same5336 has quit IRC03:39
*** jrodom has joined #openstack-meeting03:41
*** jrodom has quit IRC03:47
*** lbragstad has quit IRC03:47
*** sean_embry has left #openstack-meeting04:01
*** stevemar has joined #openstack-meeting04:04
*** kebray has joined #openstack-meeting04:07
*** glikson has joined #openstack-meeting04:13
*** dwcramer has quit IRC04:19
*** stevemar has quit IRC04:24
*** amyt has joined #openstack-meeting04:25
*** maoy has quit IRC04:30
*** Mandell has quit IRC04:31
*** cp16net is now known as cp16net|away04:31
*** glikson has quit IRC04:31
*** colinmcnamara has quit IRC04:35
*** sacharya has quit IRC04:45
*** simo has quit IRC04:56
*** ehorley has joined #openstack-meeting05:08
*** glikson has joined #openstack-meeting05:08
*** ehorley has quit IRC05:09
*** Mandell has joined #openstack-meeting05:23
*** reed has quit IRC05:35
*** glikson has quit IRC05:36
*** markpeek has quit IRC05:36
*** jbresnah has joined #openstack-meeting05:41
*** SergeyLukjanov has joined #openstack-meeting05:42
*** danwent has joined #openstack-meeting05:52
*** garyk has joined #openstack-meeting05:53
*** Daviey has quit IRC05:56
*** Daviey has joined #openstack-meeting06:01
*** fungi has quit IRC06:06
*** lindj_ has quit IRC06:09
*** glikson has joined #openstack-meeting06:28
*** glikson has quit IRC06:42
*** MarkAtwood has joined #openstack-meeting06:44
*** eglynn has joined #openstack-meeting06:45
*** kpavel_ has joined #openstack-meeting06:50
*** kpavel_ has quit IRC06:53
*** MarkAtwood has quit IRC06:55
*** MarkAtwood has joined #openstack-meeting07:00
*** eglynn has quit IRC07:01
*** glikson has joined #openstack-meeting07:04
*** matiu has quit IRC07:05
*** matiu has joined #openstack-meeting07:06
*** MarkAtwood has quit IRC07:10
*** eglynn has joined #openstack-meeting07:10
*** Mandell has quit IRC07:16
*** SergeyLukjanov has quit IRC07:19
*** danwent has quit IRC07:23
*** boris-42 has joined #openstack-meeting07:31
*** ndipanov has joined #openstack-meeting07:40
*** ndipanov has quit IRC07:40
*** ndipanov has joined #openstack-meeting07:41
*** rerngvit_ has joined #openstack-meeting07:50
*** rerngvit_ has quit IRC07:51
*** psedlak has joined #openstack-meeting08:09
*** cdub_ has quit IRC08:28
*** SergeyLukjanov has joined #openstack-meeting08:28
*** rnirmal has joined #openstack-meeting08:29
*** salv-orlando has joined #openstack-meeting08:45
*** psedlak has quit IRC09:08
*** jhenner has joined #openstack-meeting09:09
*** lloydde has joined #openstack-meeting09:19
*** SergeyLukjanov has quit IRC09:20
*** johnthetubaguy has joined #openstack-meeting09:28
*** jhenner has quit IRC09:30
*** esker has joined #openstack-meeting09:38
*** esker has quit IRC09:45
*** henrynash has joined #openstack-meeting09:50
*** henrynash has quit IRC09:55
*** SergeyLukjanov has joined #openstack-meeting09:55
*** garyk has quit IRC10:28
*** garyk has joined #openstack-meeting10:29
*** pcm__ has joined #openstack-meeting10:29
*** pcm__ has quit IRC10:29
*** pcm__ has joined #openstack-meeting10:30
*** SergeyLukjanov has quit IRC10:30
*** salv-orlando has quit IRC10:40
*** salv-orlando has joined #openstack-meeting10:40
*** salv-orlando has quit IRC10:42
*** ryanpetrello has joined #openstack-meeting10:47
*** salv-orlando has joined #openstack-meeting10:59
*** yaguang has joined #openstack-meeting11:08
*** SergeyLukjanov has joined #openstack-meeting11:08
*** salv-orlando_ has joined #openstack-meeting11:18
*** salv-orlando has quit IRC11:18
*** salv-orlando_ is now known as salv-orlando11:18
*** salv-orlando has quit IRC11:19
*** salv-orlando has joined #openstack-meeting11:19
*** AndChat|76041 has joined #openstack-meeting11:31
*** yaguang has quit IRC11:31
*** davidhadas has quit IRC11:33
*** sandywalsh has quit IRC11:54
*** salv-orlando_ has joined #openstack-meeting11:55
*** salv-orlando has quit IRC11:55
*** salv-orlando_ is now known as salv-orlando11:55
*** salv-orlando_ has joined #openstack-meeting11:56
*** salv-orlando has quit IRC11:56
*** salv-orlando_ is now known as salv-orlando11:56
*** salv-orlando has quit IRC11:57
*** salv-orlando has joined #openstack-meeting11:57
*** dprince has joined #openstack-meeting12:03
*** SergeyLukjanov has quit IRC12:05
*** sandywalsh has joined #openstack-meeting12:07
*** SergeyLukjanov has joined #openstack-meeting12:21
*** garyk has quit IRC12:31
*** radez_g0n3 is now known as radez12:34
*** lloydde has quit IRC12:40
*** garyk has joined #openstack-meeting12:41
*** jhenner has joined #openstack-meeting12:41
*** flaper87 has joined #openstack-meeting12:50
*** amyt has quit IRC12:56
*** jhenner has quit IRC12:59
*** topol has joined #openstack-meeting13:00
*** eglynn is now known as hungry-eglynn13:06
*** litong has joined #openstack-meeting13:10
*** lloydde has joined #openstack-meeting13:10
*** eharney has joined #openstack-meeting13:14
*** anteaya has joined #openstack-meeting13:20
*** lloydde has quit IRC13:20
*** woodspa has joined #openstack-meeting13:31
*** hungry-eglynn is now known as eglynn13:36
*** RajeshMohan has quit IRC13:38
*** RajeshMohan has joined #openstack-meeting13:38
*** lbragstad has joined #openstack-meeting13:40
*** esker has joined #openstack-meeting13:45
*** lloydde has joined #openstack-meeting13:46
*** salv-orlando_ has joined #openstack-meeting13:49
*** salv-orlando has quit IRC13:49
*** salv-orlando_ is now known as salv-orlando13:49
*** RajeshMohan has quit IRC13:49
*** RajeshMohan has joined #openstack-meeting13:49
*** garyTh has joined #openstack-meeting13:50
*** lloydde has quit IRC13:50
*** vkmc has joined #openstack-meeting13:57
*** markpeek has joined #openstack-meeting13:58
*** fungi has joined #openstack-meeting13:59
*** rnirmal has quit IRC14:00
*** markvan has joined #openstack-meeting14:05
*** markvan_ has joined #openstack-meeting14:05
*** nimi has quit IRC14:06
*** markvan has quit IRC14:09
*** markvan_ is now known as markvan14:09
*** yaguang has joined #openstack-meeting14:11
*** AndChat|76041 has quit IRC14:12
*** sacharya has joined #openstack-meeting14:12
*** stevemar has joined #openstack-meeting14:14
*** mestery has joined #openstack-meeting14:16
*** topol has quit IRC14:17
*** dwcramer has joined #openstack-meeting14:17
*** dolphm has joined #openstack-meeting14:18
*** dolphm has quit IRC14:18
*** fnaval has quit IRC14:20
*** fnaval has joined #openstack-meeting14:21
*** cp16net|away is now known as cp16net14:21
*** fnaval has quit IRC14:25
*** dolphm has joined #openstack-meeting14:26
*** sacharya has quit IRC14:27
*** salv-orlando has quit IRC14:27
*** salv-orlando has joined #openstack-meeting14:27
*** amyt has joined #openstack-meeting14:29
*** jcru has joined #openstack-meeting14:30
*** danwent has joined #openstack-meeting14:30
*** danwent has quit IRC14:31
*** RajeshMohan has quit IRC14:36
*** RajeshMohan has joined #openstack-meeting14:37
*** markmcclain has joined #openstack-meeting14:39
*** fnaval has joined #openstack-meeting14:39
*** rnirmal has joined #openstack-meeting14:42
*** lloydde has joined #openstack-meeting14:47
*** glwky has joined #openstack-meeting14:47
*** MarkAtwood has joined #openstack-meeting14:48
*** diogogmt has joined #openstack-meeting14:48
*** hopper has joined #openstack-meeting14:49
*** topol has joined #openstack-meeting14:51
*** spzala has joined #openstack-meeting14:51
*** mgiles has joined #openstack-meeting14:51
*** glwky has quit IRC14:51
*** markwash has quit IRC14:51
*** lloydde has quit IRC14:51
*** markmcclain has quit IRC14:52
*** kebray has quit IRC14:52
*** mgiles has quit IRC14:53
*** amyt_ has joined #openstack-meeting14:54
*** amyt has quit IRC14:54
*** amyt_ is now known as amyt14:54
*** dosaboy_ is now known as dosaboy14:55
*** maoy has joined #openstack-meeting14:59
*** sacharya has joined #openstack-meeting15:01
*** markmcclain has joined #openstack-meeting15:02
*** hopper has quit IRC15:10
*** garyk has quit IRC15:11
*** glikson has quit IRC15:19
*** yaguang has quit IRC15:19
*** cp16net is now known as cp16net|away15:21
*** cp16net|away is now known as cp16net15:21
*** flwang has joined #openstack-meeting15:22
*** kebray has joined #openstack-meeting15:23
*** MarkAtwood has quit IRC15:23
*** flwang has joined #openstack-meeting15:23
*** bdpayne has joined #openstack-meeting15:26
*** thingee has joined #openstack-meeting15:26
*** rushiagr has joined #openstack-meeting15:26
*** mestery has quit IRC15:26
*** ayoung is now known as ayoung-afk15:27
*** SergeyLukjanov has quit IRC15:28
*** hartsocks has joined #openstack-meeting15:30
*** dolphm has quit IRC15:31
*** amyt has quit IRC15:32
*** amyt has joined #openstack-meeting15:32
*** ivasev has joined #openstack-meeting15:36
*** cp16net is now known as cp16net|away15:41
*** cp16net|away is now known as cp16net15:41
*** salv-orlando_ has joined #openstack-meeting15:42
*** salv-orlando has quit IRC15:42
*** salv-orlando_ is now known as salv-orlando15:42
*** glikson has joined #openstack-meeting15:43
*** dolphm has joined #openstack-meeting15:45
*** mestery has joined #openstack-meeting15:48
*** anteaya has quit IRC15:48
*** hemnafk is now known as hemna15:49
*** RajeshMohan has quit IRC15:51
*** RajeshMohan has joined #openstack-meeting15:52
*** otherwiseguy has joined #openstack-meeting15:52
*** jungleboyj has joined #openstack-meeting15:56
*** xyang has joined #openstack-meeting15:56
*** cdub_ has joined #openstack-meeting15:56
*** varma has joined #openstack-meeting15:57
*** bswartz has joined #openstack-meeting15:59
jgriffithDuncanT: thingee bswartz rushiagr kmartin hemna around?16:01
* med_ waves in silence16:01
rushiagrjgriffith: yup!16:01
jgriffithmed_: well hey there16:01
thingeeo/16:01
hemnayup16:01
jgriffith#startmeeting cinder16:01
openstackMeeting started Wed May  1 16:01:27 2013 UTC.  The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
bswartzhi16:01
*** openstack changes topic to " (Meeting topic: cinder)"16:01
openstackThe meeting name has been set to 'cinder'16:01
varmahi16:01
hemnamorning16:01
eharneyhi16:01
xyanghi16:01
med_\o16:01
*** jbrogan has joined #openstack-meeting16:01
jgriffithHey everyone.. good slushy morning to you16:01
DuncanThey16:01
med_indeed, very slushy16:01
jungleboyjMorning / evening to you all.16:01
*** dricco has joined #openstack-meeting16:02
* bswartz wonders if he's missing something16:02
jgriffithSo here's the agenda for today: https://wiki.openstack.org/wiki/CinderMeetings16:02
jgriffithbswartz: it's rain/snow mix in Colorado this morning16:02
jgriffithbswartz: very unpleasant16:02
*** skolathu has joined #openstack-meeting16:02
med_lots of snow16:02
bswartzah, that's too bad16:02
hemnanice and warm here today :)16:03
jungleboyjWord is you guys are sending that our way jgriffith.  :-(16:03
jgriffithhemna: rub it in16:03
med_heh, good for farmers, etc.  Not too bad.16:03
*** anteaya has joined #openstack-meeting16:03
jgriffithI'm happy... I'll have hay this year, but at any rate... we digress :)16:03
jgriffith#topic bp status updates16:03
*** openstack changes topic to "bp status updates (Meeting topic: cinder)"16:03
jgriffithTake a look at https://launchpad.net/cinder/havana16:04
jgriffithOr better yet: https://blueprints.launchpad.net/cinder/havana16:04
jgriffithI believe that's a pretty comprehensive list of what we talked about at the summit16:05
jgriffithbut if there are things missing please do let me know or get something proposed ASAP16:05
jgriffithkmartin: I did not approve yours yet16:05
bswartzjgriffith: pls add the share service blueprint16:05
DuncanTMoving big I/O jobs out to a worker process16:05
jgriffithkmartin: I had an equivalent but folks from NetApp protested so I removed it for now16:06
jgriffithkmartin: I'm also not sure about having a Copyright on a blueprint TBH :)16:06
bswartzjgriffith: https://blueprints.launchpad.net/cinder/+spec/file-shares-service16:06
jgriffithDuncanT: ahh.. yes16:07
hemnajgriffith, ok so you are going to do the state machine?16:07
jgriffithpart of the migration bp16:07
*** ollie1 has joined #openstack-meeting16:07
eharneylio-support-via-targetd may be changing shape a bit from the original plan16:07
jgriffitheharney: changes are *ok* just so we have something recorded16:07
jgriffitheharney: or do you mean like "not doing it that way"16:07
hemnaand where is the "brick" BP ?16:07
jgriffithhemna: brick is broken out into 4 or 5 sub-bps16:08
hemnaok16:08
jgriffithhemna: we'll go from there on how it gets packaged/distributed16:08
jungleboyjjgriffith: We are working on getting DB2 support in Havana.  Any chance we can get that BP here too?16:08
eharneyjgriffith: looking at leveraging libstoragemgmt rather than writing a driver that uses jsonrpc with targetd -- so, still supports targetd, but may do other stuff too16:08
jgriffithhemna: may be oslo, may be our own pypi upload etc16:08
DuncanTjgriffith: I'll probably separate the I/O worker into a blueprint of its own16:08
*** jc has joined #openstack-meeting16:08
jgriffitheharney: that should be fine, feel free to update whiteboard etc as you go along16:09
eharneyjgriffith: ok i'll add some notes now16:09
jgriffithDuncanT: is the milestone ok with you?16:09
jgriffitheharney:16:09
*** dtynan has joined #openstack-meeting16:09
jgriffithnot DuncanT sorry16:09
jgriffitheharney: I wanted to check with you but took a chance and made it H216:09
jgriffitheharney: It would really be nice to have it in sooner rather than later and get it tested16:10
jgriffitheharney: I'd also like to consider making LIO default16:10
jgriffitheharney: so the more time on all of these different pieces in test the better16:10
eharneyjgriffith: hmm, certainly possible, i'll say stick with H2 for now and i'll let you know if concerns arise16:10
jgriffitheharney: sounds fair16:11
jgriffithhemna: I assigned state-machines to myself16:11
kmartinjgriffith: sorry, I was late today. HP is requiring that we add the copyright to the blueprints.16:11
jgriffithhemna: however if there's an interest or somebody gets to it first we can reassign16:11
jgriffithkmartin: no worries, we'll just use the other version then :)16:12
DuncanTThe other blueprint that is missing is anything volume-encryption related16:12
jgriffithDuncanT: haha :)16:12
hemnaok I was kinda interested in helping with that and the brick project16:12
hemnaI have cycles to work on it at least16:12
jgriffithhemna: yes... I put you down for the attach bp of course16:12
jgriffithhemna: and there's going to be some other things I think that are going to creep in there16:12
*** tomoiaga has joined #openstack-meeting16:12
hemnawe should just get together at some point and iron out the direction, if you want me to help.16:12
jgriffithhemna: but we can sync up and work together16:13
jgriffithhemna: :)16:13
hemnaok sounds great.16:13
jgriffithagreed16:13
jgriffithDuncanT: back to encryption16:13
jgriffithDuncanT: sighhhh16:13
jgriffithDuncanT: we need to figure out what to do there16:13
*** mkerrin has joined #openstack-meeting16:13
med_words can be copywritten. Just makes it hard when someone needs to go in and change the blueprint, likely need to add their own copyright atop.16:13
*** SergeyLukjanov has joined #openstack-meeting16:13
jgriffithLet's have a topic later in the meeting to talk a bit about that16:14
med_s/atop/below/16:14
DuncanTjgriffith: I'll ping the guys from the summit and see if we can get a revised design sketched up16:14
jgriffithmed_: indeed... and really the product of a summit session doesn't really seem to get an HP copyright IMO16:14
*** SergeyLukjanov has quit IRC16:14
jgriffithDuncanT: I also recieved an email from them last night about a meeting to go through things again16:14
DuncanTjgriffith: It has so many dependencies I'd be surprised if it gets sorted this cycle TBH16:14
med_jgriffith, completely agree.16:14
jgriffithOk... so we were missing:16:15
DuncanTjgriffith: I'm certainly interested in talking to them again... some sensible ideas were starting to fall out at the end16:15
jgriffith1. encryption (which is kinda TBD on how that looks)16:15
*** lloydde has joined #openstack-meeting16:15
*** armax has joined #openstack-meeting16:15
jgriffith2. and kinda missing the worker service (I've commented in Avishay's BP to break that up and add those sorts of details)16:15
jgriffithAnything else?16:16
eharneyi will likely be submitting another one related to Gluster16:16
eharneyrelated to QEMU direct gluster support16:16
jgriffitheharney: sure... sooner is better than later but I expect we'll have new ideas as we go along16:16
rushiagrjgriffith: the share service blueprint16:17
jgriffithrushiagr: bswartz yes I haven't forgotten you16:17
jgriffithrushiagr: bswartz I'm cursious to learn more about the gluster changes and why they can make things work without a separate service16:17
jgriffithrushiagr: bswartz also would like to find out if there's a way for you to collaborate with eharney and the folks from IBM that want GPFS16:17
thingeejgriffith: are we onto new proposals now?16:18
jgriffiththingee: sure16:18
jgriffith:)16:18
thingeeif we're talking about what's missing16:18
med_[topic] new BPs16:18
bswartzjgriffith: we haven't done anything w/ gluster yet16:18
jgriffithbswartz: let's come back16:18
jgriffith#topic new bp's that we missed16:18
*** openstack changes topic to "new bp's that we missed (Meeting topic: cinder)"16:18
*** cdub_ has quit IRC16:19
jgriffiththingee: please go ahead16:19
thingeeswitch to another web frame work and no pissing off ops in the upgrade16:19
jgriffiththingee: haha!16:19
hemna:)16:19
jgriffiththingee: I can't believe I missed that one16:19
thingeejgriffith: I just added it last night16:19
jgriffiththingee: we already planned on doing it and going forward16:19
hemnawhat are the other projects doing wrt the web frameworks?16:19
rushiagri had a chat with eharney yestday, and he seemed interested in shares service work16:19
jgriffiththingee:  :)16:20
thingeejgriffith: been pushing hard at work for switching to new projects ;)16:20
eharneyyes, i am going to try to get involved there16:20
*** salv-orlando has quit IRC16:20
*** cdub_ has joined #openstack-meeting16:20
*** salv-orlando has joined #openstack-meeting16:20
jgriffitheharney: rushiagr bswartz I promise I'll get to your shares service16:20
jgriffithbe patient16:20
rushiagrjgriffith: cool16:21
jgriffiththingee: link to your BP?16:21
thingeehttps://blueprints.launchpad.net/cinder/+spec/web-framework-switch16:21
jgriffiththingee: cool... thoughts on delivery milestone?16:22
thingeeoh man would I love h116:22
thingeedon't think there would be enough time for reviewing though at this point16:22
xyangthingee: does this support both python 3 and 216:23
hemnathe sooner the better :)16:23
jgriffiththingee: hehe me too... I can target it for H1, but that might be ambitious16:23
thingeexyang: both16:23
thingeewe should be moving towards py3 compatible16:23
jgriffiththingee: let's do H2 with the hope of seeing it very early16:23
jgriffiththingee: seem reasonable?16:23
thingeeearly is my goal of course so we have people catching any issues.16:24
thingeesure16:24
*** ayoung-afk is now known as ayoung16:24
thingeeI might just surprise y'all16:24
jgriffiththingee: I won't be surprised :)16:24
med_does that answer the question: Does pecan force a Python3 version change?16:24
jgriffiththingee: I have high expectations :)16:24
jgriffithmed_: it doesn't force it no16:25
med_nod.16:25
jgriffithbut I'll let thingee answer16:25
xyangthingee: do we eventually need to rewrite everything in python 3?16:25
thingeejgriffith: correct16:25
jgriffithxyang: no16:25
thingeexyang: that's a goal for sure16:25
thingeemaybe early I16:25
xyangok, good16:25
jgriffiththingee: ?16:25
thingeerelease16:25
jgriffithxyang: thingee maybe I'm not clear on the question16:25
thingeejgriffith: py3 compatible in cinder core, but not deps in early I16:26
jgriffiththingee: k16:26
jgriffithpy3 compat is different than rewrite in py3 IMO16:26
jgriffith:)16:26
thingeejgriffith: lets shoot for getting rid of xml template crud in H216:26
thingeeusing wsme16:26
jgriffithyep, sounds good16:26
thingeeI gotta make the bp to talk about that some more16:26
jgriffithxyang: there's an OS wide effort to start working on py3 compat as well this cycle16:26
thingeeI've been mainly spending my time over the weekend trying to get paste to still be fine with the pecan stuff so people don't need to make config changes16:27
xyanggriffith: I saw that.  Not sure about the details.16:27
thingeethat is all for me.16:27
jgriffiththingee: thx16:28
jgriffithxyang: there's a subteam of folks volunteering to work on it16:28
jgriffithxyang: not much detail yet but there's an etherpad of the session outcomes out there16:28
xyangjgriffith: ok16:29
jungleboyjjgriffith: Is this an appropriate time for me to put my plug for the DB2 BP?16:29
xyangjgriffith: sure, I'll check it out16:29
jgriffithjungleboyj: sure16:30
jgriffith#topic DB2 BP16:30
*** openstack changes topic to "DB2 BP (Meeting topic: cinder)"16:30
jgriffithjungleboyj: link please16:30
jungleboyjhttps://blueprints.launchpad.net/cinder/+spec/db2-database16:30
*** amyt has quit IRC16:31
*** amyt has joined #openstack-meeting16:31
jgriffithjungleboyj: so my hesitation on this was...16:31
jgriffithjungleboyj: it seems like a much broader feature than just a cinder feature16:31
DuncanTjungleboyj: Are you looking at doing the same for nova or just cinder? Should this be OSLO work?16:31
jgriffithjungleboyj: was curious as to why you wanted to start with Cinder, why it wasn't targetted for OSLO etc16:31
jgriffithDuncanT: haha!16:31
jungleboyjjgriffith: DuncanT: Good questions.  This is broader than just Cinder.  We have done the work, internally, to get all the services running on DB2.16:32
jgriffithjungleboyj: I'd suggest making it a contribution to OSLO16:32
jungleboyjWe are now just working on the details for getting it back to the community.16:32
jgriffithjungleboyj: IIRC there's some effort taking place to move the DB stuff there already16:33
thingeejgriffith: +116:33
jungleboyjjgriffith: Ok, so, just to be clear, if we have changes to the migration scripts, etc. we would want to be tracking all of those against an OSLO BP?16:34
jgriffithjungleboyj: well...16:34
jungleboyjjgriffith: For all the projects?16:34
jgriffithjungleboyj: I think common db code is a goal we already have16:34
jgriffithjungleboyj: and I don't see the point in just modifying/updating cinder db only16:34
jgriffithjungleboyj: you'll get more bang for your buck doing this OS wide16:34
hemna+116:35
jgriffithheavier lift obviously, but ther'es a lot of shared code there16:35
DuncanTI think fixing up migrate etc is a sub-task, after get DB into OSLO and doing the DB2 work there16:35
jungleboyjjgriffith: Right.  We are able to run a combination of DBs, but I doubt real-world people do that.16:35
jgriffithjungleboyj: don't get me wrong, I like the idea, just not sure it's a good approach to do it as a Cinder change16:35
jgriffithjungleboyj: indeed, but people come up with interesting thing16:36
jgriffiththings16:36
jgriffithjungleboyj: you should also be looking at reddwarf project16:36
jungleboyjDuncanT: jgriffith:  Ok, this is helpful.  We are trying to figure out how we bring this in.16:36
jungleboyjI think I may be blazing the trail a bit here.16:36
jgriffithjungleboyj: I think you want a much broader audience than just us block storage folks :)16:36
jungleboyjjgriffith: Ok, I will take this back and check into the OSLO aspect.  With that said, at some point we are going to want to say that the Cinder support is in.16:37
jungleboyjjgriffith: The good news is that getting Cinder on DB2 was quite painless.  :-)16:38
jgriffithjungleboyj: cool16:38
jgriffithjungleboyj: the rest should be pretty much the same16:38
*** noslzzp has quit IRC16:38
jgriffithjungleboyj: all of that sqla code is pretty similar16:38
jgriffithjungleboyj: the models/design are identical across cinder/nova16:38
*** noslzzp has joined #openstack-meeting16:38
jgriffithOk... I think that sort of covered item 2 on the agenda, but just incase16:39
jgriffith#topic new proposals16:39
*** openstack changes topic to "new proposals (Meeting topic: cinder)"16:39
jgriffithanything we missed?16:39
kmartinjgriffith: do we need to talk about https://blueprints.launchpad.net/cinder/+spec/multi-attach-volume16:39
jungleboyjjgriffith: In fact, I didn't have any code changes for Cinder, now that I look again.  It just worked.16:39
jungleboyjjgriffith: Anyway, thanks for the discussion!16:39
*** anteaya has quit IRC16:39
jgriffithjungleboyj: welcome16:39
jgriffithkmartin: we did, but you missed it :)16:39
jgriffithkmartin: I had an equivalent posted/accepted already16:40
jgriffithkmartin: wait...16:40
jgriffithyou were here16:40
jgriffithbahh16:40
kmartinok...thanks16:40
jgriffithwe can discuss it and the objections raised by esker and bswartz16:41
jgriffithwe'll save it for the end :)16:41
kmartinok16:41
bswartzso to be clear, we don't object to this16:41
*** roampune has joined #openstack-meeting16:41
jgriffith#topic status updates16:41
*** openstack changes topic to "status updates (Meeting topic: cinder)"16:41
bswartzthe objections I rasied were ones others raised at the design dummit16:41
jgriffithIn terms of status, I think most of the focus has been on gettign bp's16:42
bswartzI and Rob's comments were mostly to draw attention to the fact that some use cases for multi-attach-volume overlap with the share service stuff16:42
jgriffithand decompressing after the summit :)16:42
jgriffithbswartz: ok, thank you for the input16:42
jgriffithSo here's something I'd like to try this cycle :)16:42
jgriffithI was thinking that we could have formal updates on work being done in the current cycle each week16:43
jgriffithIt would be a standing agenda item in the weekly or biweekly meeting16:43
jgriffithThe idea is, if you have a bp assigned to you for the current milestone16:43
jgriffithyou go in at least once a week and update the status/whiteboard whatever16:43
jgriffithjust some way for us to track progress16:44
jgriffithI'd like to avoid the mad-dash or surprises the last week of the release cycle16:44
jgriffithdoes that sound reasonable/useful to everyone?16:44
kmartinjgriffith: sounds like a good idea, we did that in Grizzly for the FC changes16:44
jgriffithkmartin: indeed16:44
bswartzlast week of the release or last week of the milestone?16:44
jgriffithmilestone16:44
bswartzAre all the milestones problematic or just the last one?16:44
jgriffithsorry16:44
xyangjgriffith: sounds good16:44
jgriffithall16:45
bswartzokay I like it16:45
varmasounds good16:45
jgriffithbswartz: a number of us typically end up pulling all nighters the last couple days of each milestone16:45
jgriffithdoing reviews, baby-sitting CI etc16:45
bswartzI'm aware of the CI issues16:45
kmartinvarma: hey, welcome!16:46
*** cp16net is now known as cp16net|away16:46
varmakmartin: thanks, Kurt16:46
jgriffithMost of them aren't CI issues any longer but things like merges, rebases etc16:46
xyanghi varma16:46
jgriffithvarma: hey.. wann intro yourself?16:46
*** jbresnah has left #openstack-meeting16:46
varmajgriffith:sure16:47
hemnavarma, welcome!!16:47
jgriffithvarma: sorry... times up16:47
jgriffithvarma: just kidding :)16:47
varmaProposed FC SAN Zone/Access Control Manager at the summit and working on zone manager and zone driver interfaces for cinder-fc-zone-manager bp to bring in FC SAN support to Cinder16:48
varmahemna: thanks, Walter16:48
jgriffithvarma: very cool... real name?16:48
varmaYep16:48
varmaVarma Bhupatiraju16:48
jgriffithNice to meet ya16:48
jgriffithOk...16:48
varmaxyang: thanks, Xing16:48
jgriffith#topic behavior standardization16:49
*** openstack changes topic to "behavior standardization (Meeting topic: cinder)"16:49
*** gyee has joined #openstack-meeting16:49
jgriffithSo this is something I seem to be in the minority on16:49
med_ruh roh, big brother.16:49
jgriffithThe concept of same expected behaviors regardless of driver/backend16:49
jgriffithsince I can't seem to get concensus on this, even though I think it's a bad idea16:50
jgriffith....  I have a possible compromise16:50
jgriffithSo for example: jdurgin DuncanT16:50
jgriffithYou want to be able to delete parent volumes of snaps16:50
jgriffith(others may want this as well)16:50
bswartzjgriffith: I think the actual issue is where we draw the line -- I don't think anyone disagrees that there needs to be a minumum bar16:50
jgriffithMy argument is bad to have different capabilities/behaviors for diff drivers etc16:51
*** jcru is now known as jcru|away16:51
jgriffithDuncanT: jdurgin my proposal goes like this:16:51
jgriffithWhat if we provided a flag in the conf file to enable this?16:51
jgriffithThen that was the global behavior for the install16:51
DuncanTOk... still some complications with multi-backend though16:52
jgriffithIn other words, it's up to the OS-admin to set this correctly based on what his backend is16:52
jgriffithDuncanT: how so?16:52
*** rushiagr has quit IRC16:52
jgriffithDuncanT: What I'm getting at is it's LCD16:52
*** anteaya has joined #openstack-meeting16:52
med_jgriffith, you're saying the admin defines what "standard" means to him16:53
jgriffithmed_: not entirely... but16:53
DuncanTI'd still like a mechanism where a backend can express what it is capable of... the trouble with a switch is that people poke it to see what happens16:53
*** rushiagr has joined #openstack-meeting16:53
jgriffithOk...16:53
guitarzanmultibackend also has issues with the snapshots included in gb flag16:53
jgriffithit seems my compromise won't fly either16:53
guitarzanbut I digress16:53
jgriffithnever mind16:53
DuncanTI'm not necessarily against a switch to say 'enable not quite standard behaviours'16:53
DuncanTBut I'd like to maybe add a method to the drivers to express which of those behaviours they support16:54
jgriffithDuncanT: ok, I'll just give up16:54
hemnaisn't that what the capabilities thing is about?16:54
hemnaor no.16:54
guitarzanit could be16:54
DuncanTThese are not mutually exclusive or incompatable ideas I don't think?16:54
jgriffithhemna: yes,but the proposal is to not have everything behave the same16:54
*** xyang_ has joined #openstack-meeting16:54
jgriffithhemna: it would be wild wild west16:55
*** xyang has quit IRC16:55
jgriffitheverybody does what they want as long as the report it16:55
jgriffiththey16:55
guitarzancats and dogs living together. mass hysteria!16:55
hemnaugh16:55
jgriffithguitarzan: haha!16:55
hemnawell that's bad mmmkay16:55
jgriffithhemna: in other words no standard expected behaviors16:55
DuncanTDefine the 'correct' behaviour and have a switch to enable any none-standard behaviours seems fine16:55
guitarzanI think the idea of having the provider define behavior globally is interesting16:55
jgriffithguitarzan: it's the best compromise I could come up with16:56
guitarzanagain, multiple backend makes that hard16:56
jgriffithguitarzan: so then HP for example could configure their cloud to allow delete parent vols16:56
guitarzanbut it's going to make everything hard :)16:56
DuncanTbut in order to actually make that work, some form of driver functionality expression is also needed16:56
jgriffithif they throw in LVM or something that doesn't support that then oops16:56
DuncanTParticularly for multi-backend16:56
*** cody-somerville has quit IRC16:56
DuncanTI'd rather be smarter than 'ooops' if possible16:57
guitarzanI think folks are going to have to go lowest common denominator if they want multiple backends to work exactly the same16:57
*** markwash has joined #openstack-meeting16:57
jgriffithguitarzan: agree,,, and I still stand by my viewpoint that the behavior should be the same16:57
hemnaDo we even know how divergent the drivers are right now?16:57
DuncanThemna: Yes16:58
jgriffithhemna: yes, and it's not horrid16:58
hemnashould we document this in a wiki or something right now?16:58
hemnaI know the FC drivers don't support copy volume to image/image to volume.16:58
jgriffithhemna: kmartin already did that IIRC16:58
DuncanTI think adding a way of getting better, more informative error messages out of drivers is a good thing16:58
jgriffithDuncanT: sure, I agreee with that16:58
DuncanTEven if in an ideal world / stable release they'd never get seen16:58
thingeehttps://wiki.openstack.org/wiki/CinderSupportMatrix16:59
jgriffithalright, let's move on... there's no point in me wasting time on this any more16:59
hemnashould the drivers that don't support features throw a warning/exception at startup?16:59
DuncanTAdding your requirement that a flag is needed to enable certain none-standard behaviours I've no objection to16:59
jgriffitheverybody feel free to do what they like, I won't fight it any longer16:59
bswartzjgriffith: we're out of time :-(16:59
hemnadoh16:59
jgriffithYay!17:00
jgriffith:)17:00
jgriffith#endmeeting17:00
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"17:00
openstackMeeting ended Wed May  1 17:00:07 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-05-01-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-05-01-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-05-01-16.01.log.html17:00
*** thingee has left #openstack-meeting17:00
med_heh.17:00
jgriffiththat's why we have openstack-cinder :)17:00
*** reed has joined #openstack-meeting17:00
*** varma has quit IRC17:00
*** xyang_ has left #openstack-meeting17:01
*** rushiagr has left #openstack-meeting17:01
*** dtynan has left #openstack-meeting17:01
*** jungleboyj has left #openstack-meeting17:01
*** bswartz has left #openstack-meeting17:01
*** skolathu has quit IRC17:01
*** terry7 has joined #openstack-meeting17:02
*** garyk has joined #openstack-meeting17:03
*** ollie1 has left #openstack-meeting17:03
johnthetubaguy#startmeeting XenAPI17:03
openstackMeeting started Wed May  1 17:03:54 2013 UTC.  The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot.17:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:03
*** openstack changes topic to " (Meeting topic: XenAPI)"17:03
openstackThe meeting name has been set to 'xenapi'17:03
johnthetubaguyHey, anyone here for the XenAPI meeting?17:04
*** jc has quit IRC17:04
johnthetubaguytalking to BobBall and matelakat we were going to move the meeting17:04
*** otherwiseguy has quit IRC17:04
*** lindj has joined #openstack-meeting17:04
*** dwcramer has quit IRC17:05
*** dwcramer has joined #openstack-meeting17:06
guitarzanjohnthetubaguy: where to?17:07
johnthetubaguy#action johnthetubaguy to email the list about the proposed new time: Wednesday at 15:00 UTC17:07
johnthetubaguywould that one work for you?17:07
guitarzansure17:07
johnthetubaguycool, lets call it a day for this weeks meeting17:07
johnthetubaguymy plan is to sift through all the blueprints we need to raise from the Summit sessions and things by then17:07
johnthetubaguywell hopefully will have that done by the end of today, early tomorrow17:08
johnthetubaguytalk soon17:08
johnthetubaguy#endmeeting17:08
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"17:08
openstackMeeting ended Wed May  1 17:08:25 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:08
openstackMinutes:        http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-05-01-17.03.html17:08
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-05-01-17.03.txt17:08
openstackLog:            http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-05-01-17.03.log.html17:08
*** cody-somerville has joined #openstack-meeting17:09
*** fnaval_ has joined #openstack-meeting17:09
*** rnirmal has quit IRC17:10
*** jrodom has joined #openstack-meeting17:11
*** fnaval has quit IRC17:12
*** krtaylor has joined #openstack-meeting17:13
*** sacharya has quit IRC17:13
*** markmcclain has quit IRC17:17
*** dontalton has joined #openstack-meeting17:22
*** beagles is now known as beagles_brb17:23
*** wirehead_ has joined #openstack-meeting17:25
*** Mandell has joined #openstack-meeting17:26
*** markmcclain has joined #openstack-meeting17:27
*** sacharya has joined #openstack-meeting17:27
*** mkerrin has left #openstack-meeting17:30
*** bdpayne has quit IRC17:35
*** jbrogan has quit IRC17:41
*** mestery has quit IRC17:42
*** Nate_ has quit IRC17:42
*** ladquin has joined #openstack-meeting17:44
*** beagles_brb is now known as beagles17:44
*** shri has joined #openstack-meeting17:46
*** cp16net|away is now known as cp16net17:49
*** mestery has joined #openstack-meeting17:50
*** eharney has quit IRC17:50
*** stevemar2 has joined #openstack-meeting17:51
*** mikal__ has joined #openstack-meeting17:52
*** stevemar has quit IRC17:52
*** garyk has quit IRC17:52
*** cdub_ has quit IRC17:52
*** mikal has quit IRC17:52
*** dosaboy has quit IRC17:52
*** sdake has quit IRC17:52
*** cdub has quit IRC17:52
*** lcheng has quit IRC17:52
*** lifeless has quit IRC17:52
*** toanster_ has quit IRC17:52
*** ttx has quit IRC17:52
*** uvirtbot has quit IRC17:52
*** sdake has joined #openstack-meeting17:52
*** lcheng has joined #openstack-meeting17:53
*** cdub has joined #openstack-meeting17:53
*** dosaboy has joined #openstack-meeting17:53
*** garyk has joined #openstack-meeting17:53
*** lifeless has joined #openstack-meeting17:53
*** cdub_ has joined #openstack-meeting17:53
*** toanster has joined #openstack-meeting17:53
*** adrian17od has joined #openstack-meeting17:54
*** stevemar2 has quit IRC17:56
*** ttx has joined #openstack-meeting17:56
*** ttx has joined #openstack-meeting17:56
*** stevemar has joined #openstack-meeting17:57
*** Changbin_ has joined #openstack-meeting17:59
*** krtaylor has quit IRC18:00
*** krtaylor has joined #openstack-meeting18:00
*** jcru|away is now known as jcru18:00
*** garyk has quit IRC18:02
*** Changbin_ has quit IRC18:03
*** SergeyLukjanov has joined #openstack-meeting18:03
*** beagles is now known as beagles_back_asa18:03
*** beagles_back_asa is now known as beagles_backasap18:03
*** Changbin has joined #openstack-meeting18:03
*** johnthetubaguy has quit IRC18:05
*** cp16net is now known as cp16net|away18:05
*** lloydde has quit IRC18:07
*** anteaya has quit IRC18:07
*** novas0x2a|laptop has quit IRC18:12
dosaboyis there swift-dev meeting today?18:12
notmynameyes18:12
notmynamein 45 minues18:12
dosaboygotcha ;)18:12
dosaboyi'm not UTC anymore18:13
*** dontalton has quit IRC18:15
*** cp16net|away is now known as cp16net18:17
*** glikson has quit IRC18:19
*** sean_s has joined #openstack-meeting18:21
*** lloydde has joined #openstack-meeting18:21
*** anniec has joined #openstack-meeting18:21
*** glikson has joined #openstack-meeting18:21
*** anniec_ has joined #openstack-meeting18:22
*** anteaya has joined #openstack-meeting18:23
*** garyk has joined #openstack-meeting18:26
*** tomoiaga has left #openstack-meeting18:27
*** gyee has quit IRC18:27
*** davidhadas has joined #openstack-meeting18:29
*** krtaylor has quit IRC18:29
*** uvirtbot has joined #openstack-meeting18:31
*** krtaylor has joined #openstack-meeting18:31
*** dwcramer has quit IRC18:32
*** jcru has quit IRC18:33
*** jcru has joined #openstack-meeting18:35
*** novas0x2a|laptop has joined #openstack-meeting18:35
*** dwcramer has joined #openstack-meeting18:38
*** cody-somerville has quit IRC18:41
*** vkmc has quit IRC18:42
*** lloydde has quit IRC18:43
*** amyt has quit IRC18:47
*** amyt has joined #openstack-meeting18:47
*** stevemar has quit IRC18:52
*** sudorandom has joined #openstack-meeting18:52
*** garyk has quit IRC18:53
*** dhellmann has joined #openstack-meeting18:54
*** cody-somerville has joined #openstack-meeting18:54
*** stevemar has joined #openstack-meeting18:55
*** glange has joined #openstack-meeting18:55
*** dfg has joined #openstack-meeting18:59
*** krtaylor has quit IRC19:00
*** otherwiseguy has joined #openstack-meeting19:00
notmynameswift meeting time19:00
*** krtaylor has joined #openstack-meeting19:00
notmyname#startmeeting swift19:01
openstackMeeting started Wed May  1 19:01:24 2013 UTC.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
*** clayg has joined #openstack-meeting19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: swift)"19:01
openstackThe meeting name has been set to 'swift'19:01
notmynamehi all. welcome to our first meeting since the portland summit19:01
*** bdpayne has joined #openstack-meeting19:02
notmynameI don't have a huge agenda this week, but I'd like to talk about 1) summit follow up 2) swift API and 3) blueprints19:02
notmynamesot to start with...19:02
notmyname#topic summit follow up19:02
*** openstack changes topic to "summit follow up (Meeting topic: swift)"19:02
notmynameHow was the summit for you? what was good or bad? what would you like to see different in the next one?19:03
*** amyt has quit IRC19:03
*** amyt has joined #openstack-meeting19:03
davidhadasNeed 2 days (or more ) next time19:03
davidhadas(instead of 1)19:03
*** gholt has joined #openstack-meeting19:03
creihtI would have liked to see the discussion times more around actuall dev of swift rather than findings or showing off tools19:04
notmynamedavidhadas: agreed, but I'm not sure that could have been predicted based on previous tech sessions submitted19:04
swifterdarrell++ on more sessions for swift19:04
creihtif you want to discuss findings, or show off tools, then those should be done in the other sessions (like what hp did for their perf stuff)19:04
davidhadasnotmyname: you askd about next time - this was no critic19:04
*** diogogmt has quit IRC19:05
davidhadasbut the talk about what needs to be developed to benchmark swift was good19:05
notmynamecreiht: good feedback. I'd like to see gholt talk about sssync at a summit ;-)19:05
creihtnotmyname: well don't tell me that :)19:05
davidhadasI'd like to see gholt19:06
davidhadas:)19:06
dfgi'm looking at him right now- its not that cool19:06
dfg:)19:06
clayg:)19:06
creihthaha19:06
davidhadasdfg: The mistory man19:06
dfghe does wear a cape...19:07
shrithis was my first openstack summit. Loved the sessions on swift. Would've loved a session on getting started with swift development19:07
notmynameI think we can try to get some more talks about swift code. how do you think that would look?19:07
claygcreiht: so two talks specifically that I *enjoyed* that fit into the "findings" bucket was KT & Seagate, I also really liked the unsession stuff about more dev... I hope next time we can just make more time for both19:07
swifterdarrellshri: notmyname: that'd be a great break-out session on a 2nd or 3rd day which was well-advertised the first day19:07
notmynameshri: glad you could come. we had one at the san diego summit be ran out of space in this one. maybe an unconference session on that would be good?19:07
*** danwent has joined #openstack-meeting19:08
davidhadasSuch talks about code shoudl be apart from the design meetings - not instead19:08
creihtclayg: I'm not saying they were bad talks, I'm just saying given how the format is they would be better suited for the other sessions19:08
davidhadasdesign meetings were very good  - too short and too little19:08
shrinotmyname: yeah.. that would be good19:08
notmynameI heard a suggestion for basic hackathon-style tracks at the summit. eg show up and you have a bugfix in master at the end of the day19:08
torgomaticthe rooms need some whiteboards; it's hard to discuss when your only tool is a slide projector19:08
creihtSeveral people comminucated to me that the would have liked to see more design oriented sessions during the design part of the summit for swift19:09
claygdavidhadas: creiht: notmyname: in past summits, I've found the hallway track was often better at talking code just because of all the noise in the rooms?  There'd be like 30 people... and sometimes it's hard to keep everyone on topic...19:09
shrii attended one session on getting started with openstack development, not swift development19:09
notmynamehistorically, we've had trouble with the design style sessions with swift.19:09
*** prometheanfire has joined #openstack-meeting19:09
creihtthey are difficult all around (the other teams have the same issues)19:10
davidhadasclayg: agree - but....  its hard to get all the right pepole at the same time in the halllway19:10
creihtdavidhadas: ++19:10
clarkbshri: fwiw bootstrappign at the openstack level should be sufficient to get you going. we have intentionally made it so that moving across projects is easy to do19:10
creihtmore so as the number of active contributors increases19:10
shriI see19:10
litong@notmyname, I think that the session that you gave on Swift update and what is next is always good and useful and serve a good purpose to level the field.19:11
litong+recognize Sam being the top contributor, that was very nice.19:11
notmynamelitong: ya, the state of the project is fun. I enjoy it, and I'm glad you did. but that's completely separate from the tech tracks :-)19:12
shrialso, i liked the swift sessions because there was lot of interaction and discussions. they weren't about a couple of speakers talking and rest of us simply consuming.19:12
notmynameso what I'm hearing is that we need more time and we need more design/code talks19:12
notmynameshri: +119:12
claygnotmyname: +119:13
*** krtaylor has quit IRC19:13
davidhadas+219:13
swifterdarrellyup19:13
creihtpreference should be given to design/code talks durring the design part of the summit19:13
swifterdarrelland also to prioritize sessions for design/code if space is tight19:13
torgomaticnotmyname: +119:13
*** rnirmal has joined #openstack-meeting19:13
shrinotmyname: +119:13
clayghrmm... I'm definately *not* saying that design/code session should be a priority19:13
notmynameshri: FYI http://swiftstack.com/blog/2013/02/12/swift-for-new-contributors/19:13
swifterdarrellit may be debatable, but it was said ;)19:14
claygbut if everyone else feels that way that should definately put that out there - I liked the sessions we had, and the unconference19:14
*** krtaylor has joined #openstack-meeting19:14
claygI'd like more time, so we can have more space for some of the stuff that happened in the unconference19:14
*** dolphm has quit IRC19:15
shrinotmyname: cool. Will go through this in more details.19:15
claygnotmyname: can you just go ahead and make everyone happy cause that would be great...19:15
*** cp16net is now known as cp16net|away19:15
swifterdarrellya, the ideal would be time enough for showing off cool tools and findings *and* actual code design discussions19:15
notmynameclayg: working on it. (we still haven't voted in a meeting for you)19:15
adrian17odI wasn't at this summit but weren't the sessions selected based on votes?19:15
notmynameadrian17od: no19:16
notmynamewell, if you consider my input as the only vote... ;-)19:16
adrian17odIf we want to prioritise more dev/design sessions that would mean leaving that system.19:16
creihtmy only argument is that the tools and findings should be in the other talk tracks19:16
notmynamegood feedback. thansk19:16
creihtadrian17od: the other tracs are voted on, then there are secret teams of people that select which talks make it19:17
notmynameya, I think the other tracks were voted. the tech tracks (for all projects) are up to the respective PTL19:17
adrian17odI see.19:17
notmynameany other comments about the summit or input on changes?19:18
notmynamebefore we move on19:18
davidhadaswell about the chocolates...19:18
creihtotherwise I do agree with clayg that the content of most of the discussions was good19:18
notmyname#topic swift API19:19
*** openstack changes topic to "swift API (Meeting topic: swift)"19:19
claygwe should have one!19:19
notmynameI'm sure there are strong feelings on this topic19:19
claygmeh19:20
creihtSOAP19:20
notmynamethe current state is that we have a pretty good API. it's very stable. but there are a few warts, and the state of middleware is somewhat fuzzy19:20
notmynameie, is middleware part of the api or not19:20
swifterdarrellcan we just wait for the OpenStack API As A Service project?19:20
creihtfuzzy wuzzy was a middleware19:20
notmynameI'm not proposing that we decide this now19:20
davidhadasnotmyname: this is a big issue19:20
torgomaticsome is, some isn't?19:20
notmynameyes19:20
davidhadastorgomatic: which part is?19:21
*** zzs has joined #openstack-meeting19:21
swifterdarrellI liked the distinction of API 1.1 being some incremental changes to core stuff (fixing the warts)19:21
notmynameindeed19:21
swifterdarrellThat's probably something with broad support19:21
swifterdarrellanything regarding middleware is going to be more contentious19:21
dfgbtw- before i forget I'm completely rewriting how bulk delete and expand archive are going to work.19:21
notmynamebut overall, we need to first have a sense of what the api is before we can even figure out what 1.1 is19:22
notmynamedfg: oh goody19:22
torgomaticdavidhadas: tempurl maybe? I dunno, I'm just throwing that idea out there19:22
notmynamedfg: I'll come back to you ;-)19:22
claygbut asside from what... quoting etags did we really identify anything that should be changed in v1.1?19:22
notmynamethere are 2 APIs in swift: internal and external19:22
dfgya- i'm not expecting anyone to really care, hopefully19:22
creihtthere were quite a few things19:22
*** jtomasek|gone has quit IRC19:22
creihtclayg: but I can't remember off the top of my head19:22
davidhadasWe need order in the middleware - this is not a trivial issue. But we probably need to have mandatory middleware as a first filter which is actualy part of Core Swift19:23
notmynamethe external api is what clients can use (defined [in part] at http://docs.openstack.org/api/openstack-object-storage/1.0/content/)19:23
swifterdarrellclayg: I don't remember the details but I felt like there were about 3 or 4 little things19:23
notmynamethe docs site incidentally calls that the object storage 1.0 api spec19:23
claygcreiht: yeah i sorta remember something on the etherpad... but then a lot of stuff we couldn't agree... and then I don't know if there was a final list of like "purposed changes to v1.1"19:24
notmynamealthough it's certainly not something that we code to. it's more something that's written based on what's in the code19:24
creihtclayg: yeah I think the next step would be to take that and start on a blueprint19:24
*** lloydde has joined #openstack-meeting19:24
notmynamewell, I think the first step is to make sure we have an answer to what swift 1.0 is19:24
davidhadasQ  - do we treat the small changes from 1.0 to 1.1 as a API change that requires us to support both?19:25
creihtdavidhadas: absolutely19:25
claygnotmyname: wow, so that page opens with auth v1.0 specification, and we can't even get x-storage-token deprecated properly!19:25
davidhadascreiht: than why do it?19:25
creihtbackwards compatability?19:25
creihtclients are still going to be using v1.0 for quite some time19:25
creihtor why do the clean up?19:26
davidhadascreiht: but from now on to start supporting to versions - seems more pain than not doing any change19:26
*** krtaylor has quit IRC19:26
*** ndipanov has quit IRC19:26
creihtsure there will be extra work19:26
*** krtaylor has joined #openstack-meeting19:26
creihtbut if nobody sees value in cleaning up the api, then there is an argument to be made for not doing it19:26
claygdavidhadas: I think part of the value comes from defining the layout and abstractions *needed* to support different versions - part of a pre-req for v2.019:26
notmynamedavidhadas: ya, but it doesn't have to be hugely painful eg: if api_version > 1.0: etag = '"%s"' % etag19:27
notmynameclayg: yes19:27
*** eglynn has quit IRC19:27
notmynamecreiht: absolutely. no need to find extra work to do. we've got enough as-is19:27
notmyname(but I think an API cleanup is beneficial to us all and thing we should do it)19:28
davidhadasOk - it all depends on the details - but I doubt if it makes sense - unless we gain something significant with it and if not  - it should all be delayed to 2.019:28
davidhadas(or  - better so - we ne dto find ways to add it without disrupting the clients and without getting info if ver == 1.019:28
notmynameI think the todo items are to 1) decide about middleware and 2) define what the 1.0 api is (based on the first answer)19:29
notmynamewhich comes down to, "who's going to do it?"19:30
davidhadasnotmyname: can you detail "1"?19:30
creihtdavidhadas: yeah I'm not fond of adding a lot of speghetti if code for different api versions19:30
creihtthere are other ways to handle it19:30
*** sandywalsh has quit IRC19:30
notmynamedavidhadas: as an example, is the staticweb part of the official API? if a cluster doesn't use it, is it really a swift cluster? what about public containers?19:31
davidhadascreiht: yeh - either it is a disruptive change with real value (going to 2.0) or it is not  - so keep the API and extend it - cleanup semms like neigher19:31
*** eharney has joined #openstack-meeting19:31
notmyname(public containers is a difference in eg rackspace's swift product and what's in "vanilla swift"19:31
*** krtaylor has quit IRC19:31
davidhadasnotmyname: so would this lead to code moving from middleware to core?19:32
notmynamedavidhadas: no19:32
claygwell about the chocolates...19:32
davidhadasclayg: that too long... :)19:32
claygI really don't want "is it implemented in middleware" to be a pre-req for "is it core"19:32
notmynamesomething written as middleware is an implementation detail. eg catch_errors is vital, but it's implemented as middleware19:32
*** vkmc has joined #openstack-meeting19:32
claygif it's *easier* to add a feature in middleware that's where it should go19:32
claygoh heh :)19:33
notmyname"core" to me is "in the source tree"19:33
*** krtaylor has joined #openstack-meeting19:33
notmyname(which has implications for a "contrib" section, but I digress...)19:33
notmynameso how do we answer these questions? how do you want to do it?19:33
davidhadasmy poimnt before is that middleware is a big problem as it always come before the core and we do not know how to "wrap it" with core code19:33
davidhadasE.g.19:33
notmynamea mailing list seems that it will invite too many cooks into the kitchen19:34
creihtMaybe we need source code amnesty to ensure a proper data democracy19:34
notmynameIRC is hard to get everyone together19:34
adrian17odSeems to me like the first job is to write up the API specification for 1.019:34
notmynameadrian17od: yes19:34
*** dontalton has joined #openstack-meeting19:34
davidhadasIf we want to filter our ilegal headers (that middleware can send, but a client is not allowed to) we have no way to ensure that.19:34
notmynamewe could have this dicussion on the openstack wiki19:34
*** gyee has joined #openstack-meeting19:35
adrian17odThe discussion needs to happen around a doc so the wiki sounds like a good place19:35
*** danwent has quit IRC19:35
notmynameanyone object to discussing the api definition on the openstack wiki?19:35
notmynamewait, shoudl we vote here?19:35
notmynameclayg: ?19:35
* creiht sighs19:36
notmynamecreiht: not helpful. what's your concern?19:36
davidhadasI like the idea on working with Etherpad even when we are not in the same room19:36
creihtI just don't think you are going to get a lot of useful collaboration on a wiki19:36
adrian17odThe alternative is gerrit?19:37
*** beagles_backasap is now known as beagles19:37
davidhadascreiht: how about virtual design session(s) with Etherpad and IRC19:37
notmynamedavidhadas: I like etherpad, but I don't like how you can't tell who said what even a day after the discussion (ie after people leave the page)19:37
litongwhy can't we treat the api specification doc just like any other patch. anyone care can voice with comments.19:38
notmynameand a virtual design session has the problem of scheduling19:38
swifterdarrellwhat does Etherpad give you that a wiki doesn't?  real-time editing, lack of formatting, and a bunch of distracting colors?19:38
notmynamecreiht: what woudl you prefer to a wiki page?19:38
*** portante has joined #openstack-meeting19:38
*** anniec_ has quit IRC19:38
creihtnm19:38
claygcreiht: but.. but... you LEAD the api discussion at teh summit!19:39
claygI'm all hoping you had the plan over here :'(19:39
creihtand then it got off in the weeds with specs and such19:39
claygahhh...19:39
creihtI just wanted to clean things up19:39
davidhadasswifterdarrell: a chance to get pepole attention for a while on a problem  - in other words a chance to brainstorm19:39
creihtand there seems to not be a lot of political will for that19:39
creihtso it's notmyname's call19:39
claygfor the clean up?  I think that is totally in the list of 2 things to be done?19:40
claygoh... maybe i read that wrong19:40
torgomaticI dunno, a cleanup in core code plus a recrappification middleware sounds like a decent enough approach to me19:40
notmynamecreiht: I think there is a strong desire to make things better. but I don't think we can do that responsibly in a global community of deployers and contributors without first defining what it is we are actually changing19:41
creihtnotmyname: ok then go do that, then I'll see about changing stuff :)19:41
claygI think in my mind I put "creiht | clayg: yeah I think the next step would be to take that and start on a blueprint" on my list19:41
*** cdub_ has quit IRC19:41
swifterdarrelldavidhadas: IRC is a decent online place to have a real-time conversation and a wiki is a decent place to store formatted information multiple people can edit;  I see Etherpad as a failure to attempt to combine those both?  But that's just my personal opinion.19:41
notmynamedavidhadas: would you object too strongly in a wiki doc?19:42
creihtclayg: well that *was* my next plan of action19:42
davidhadasnotmyname: no objections19:42
*** sandywalsh has joined #openstack-meeting19:42
claygnotmyname: what about using that doc you linked as a starting point?19:42
swifterdarrellwiki + irc seems good to me; I mean your problem will be getting people to care and actively participate more that it'll be what tools to use19:43
notmynameI'll put together a starting doc on the openstack wiki and send an email when it's done19:43
swifterdarrellif you have people caring and participating, they'll use whatever tools work19:43
*** pnavarro has joined #openstack-meeting19:44
davidhadastorgomatic: I learn a new word every day   :) "recrappification"19:44
creihtlol19:44
davidhadasthat is awsome19:44
torgomaticI make up a new word every day, so we'll get along great. :)19:44
davidhadasgood19:44
swifterdarrell...for when the initial crapification wasn't bad enough...19:44
notmynameok, so moving on to 2 small things19:45
notmyname#topic blueprints19:45
*** openstack changes topic to "blueprints (Meeting topic: swift)"19:45
notmyname(for the record, I really don't think blueprints are all that great)19:45
creihtthere are no small things left in swift :)19:45
notmynameblueprints are what we have to help let others know what's going on inside of swift19:46
swifterdarrellnotmyname: I'll go on record as agreeing with that.19:46
creihtyeah we can vote on that!19:46
*** vipul is now known as vipul|away19:46
notmyname:-)19:46
notmynameso I'm asking you to use them.19:47
notmynameThe goal is that you add one for stuff you are doing and then target it to havana. This allows people external to your org know what's going on and what to expect when. It also has the side benefit of promoting Swift (indirectly) by showing constant activity.19:47
notmynameso please use blueprints. at least with a short note saying "hey, I'm working on this"19:47
notmynamefor example, dfg should make a blueprint about his bulk middleware refactoring19:48
notmyname:-)19:48
brianclineyeah, I usually end up digging through the bug list because a lot of existing blueprints are pretty thin19:48
notmynamedfg: I told you I'd come back to you about that19:48
brianclineand review.*19:48
swifterdarrellthen you reference the bp in the commit message and it helps reviewers understand the context of why the whizzbang should be connected to the frombulator instead of the wackyjigg?19:48
dfgya- i could do that i guess...19:48
notmynamedfg: thanks19:48
creihtI look forward to the recrapification blueprint19:48
dfgoh- you were being serious?19:48
dfg:)19:48
creihtlol19:48
notmynametorgomatic: I don't think there's one for the threadpool stuff19:49
notmyname#topic other19:49
*** openstack changes topic to "other (Meeting topic: swift)"19:49
torgomaticnotmyname: there sure isn't. I don't like blueprints since they lack both comments and notify-on-edit, but I can throw one up anyway19:50
davidhadasThis is a good topic19:50
notmynameit's come up a few times in the past week, so I'll mention it here. If you want to stay involved in IRC conversations, IRC bouncers are a great thing. I recommend http://znc.in19:50
*** SpamapS has joined #openstack-meeting19:50
creihtor a shell somewhere an irssi19:50
notmynametorgomatic: I completely agree re blueprints19:50
claygirssi o/19:50
briancline+1 for irssi in a tmux session19:50
notmynameanything else for anyone?19:51
*** ryanpetrello has quit IRC19:51
claygnotmyname: yeah can you ask in some sort of "openstacky" meeting how we can go about making blueprints useful?19:51
creihtthere were some comments about that recently on the mailing list19:51
clayglike.. do other projects use them successfully?  HOW?19:51
claygcreiht: notmyname is like my personal hacker news for the mailing list19:51
clayghe must not have upvoted that thread for me19:51
notmynameclayg: I'll ask around again19:52
brianclinenotmyname: not 100% swift but I'm curious what kind of effort there is currently behind moderating and pushing the ask.* site more19:52
* clayg goes to ask how to use blueprints19:52
notmynamereed: want to comment in here?19:53
*** randallburt has joined #openstack-meeting19:53
* reed reading19:53
notmynamereed: re ask.o.o19:53
litong@notmyname, I would like to ask about the two ctrl-C to end swift client process/threads. wondering how everybody feels about that.19:53
notmynamelitong: let's take that to #openstack-swift19:53
litongk.19:54
brianclineit seems like a terrific resource as more and more people start to use it, but I've noticed it could use some help with retagging some of the questions that come in, editing when someone pastes in code/config/output blocks without formatting it into a block, etc.19:54
reedbriancline, ask.o.o needs more moderators19:54
notmynamereed: what about migrating answers content?19:54
notmynamereed: or auto-moderating ATCs for the project they've contributed to?19:54
brianclinegranted they're little things, but they make a huge difference when perusing for questions to chime in on19:54
reednotmyname, at the moment there is no concrete action item for that, it's very very hard to do19:54
reednotmyname, explain 'automoderating'19:55
reedoh, make them moderators?19:55
*** dontalton has quit IRC19:55
notmynamereed: IIRC, I have about 1 karma on ask.o.o19:55
notmynameya that19:55
reedI can make you a moderator right now19:55
*** therve has joined #openstack-meeting19:55
reedwho else?19:55
*** pnavarro has quit IRC19:56
reedhttps://ask.openstack.org/about/ has some suggestions on what the questions and answers should look like19:56
notmynamereed: is it organized per project or across all of openstack?19:56
*** shardy has joined #openstack-meeting19:56
brianclineme too -- so far I haven't found enough yet that I can usefully chime in on, so I've no powers yet to make those kinds of small tweaks to help make it useful in other ways19:56
brianclinein terms of karma19:56
reedit's a generic Q&A site for openstack, it has tags that you can export as RSS19:56
reedand it has email push capabilities: you can subscribe to 'interesting tags' and get email notifications of new questions tagged interesting19:57
notmynamereed: my first response would be people who have answered the launchpad questions in swift (we've had great response from swift devs for LP answers)19:57
notmynameany other quick questions in the last 2 minutes of our time?19:58
*** zaneb has joined #openstack-meeting19:58
reedI've looked into the 'how to import Q&A from LP' and I found the task very complex19:58
*** jrodom_ has joined #openstack-meeting19:58
notmynamethanks everyone for attending this week's meeting. see you in 2 weeks19:59
reedleft me wondering if it makes sense to spend lots of resources to move content from there19:59
notmyname#endmeeting19:59
*** jrodom_ has quit IRC19:59
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"19:59
openstackMeeting ended Wed May  1 19:59:14 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-05-01-19.01.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-05-01-19.01.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-05-01-19.01.log.html19:59
*** jrodom_ has joined #openstack-meeting19:59
*** ccrouch has joined #openstack-meeting19:59
shardy#startmeeting heat20:00
openstackMeeting started Wed May  1 20:00:10 2013 UTC.  The chair is shardy. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** krtaylor has quit IRC20:00
*** openstack changes topic to " (Meeting topic: heat)"20:00
openstackThe meeting name has been set to 'heat'20:00
SpamapSo/20:00
shardy#topic rollcall20:00
*** openstack changes topic to "rollcall (Meeting topic: heat)"20:00
randallburthithere20:00
SpamapSo/ again :)20:00
shardy:)20:00
*** krtaylor has joined #openstack-meeting20:00
jpeelerhere20:00
wirehead_Good afternoon/ evening / morning / night / teatime20:00
zanebhowdy20:00
sdakehi20:01
thervehi20:01
*** portante has left #openstack-meeting20:01
*** alexheneveld has joined #openstack-meeting20:01
*** prometheanfire has left #openstack-meeting20:01
shardystevebaker, asalkeld?20:01
asalkeldhi20:01
*** tspatzier has joined #openstack-meeting20:01
kebrayhello20:01
shardyOk, cool hi all20:02
*** gholt has left #openstack-meeting20:02
shardy#topic Review last week's actions20:02
*** openstack changes topic to "Review last week's actions (Meeting topic: heat)"20:02
SpamapSIIRC stevebaker is on holiday all week20:02
shardy#link http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-04-24-20.00.html20:02
shardySpamapS: thanks, forgot that20:02
shardySo there are two actions:20:03
shardyeveryone to review havana BPs20:03
*** jrodom has quit IRC20:03
*** alexheneveld has quit IRC20:03
shardyWell come to BP discussion in a minute, so perhaps we'll skip that :)20:03
shardys/Well/We'll20:03
shardysomeone to create workflow-library wiki page20:03
*** alexheneveld has joined #openstack-meeting20:03
*** spzala has quit IRC20:03
shardyDid anyone do that?20:03
*** ryan_rs has joined #openstack-meeting20:04
kebrayhttps://wiki.openstack.org/wiki/Convection does this count?20:04
asalkeldno :(20:04
harlowjai have some pieces of it20:04
asalkeldwhew20:04
zanebI thought someone was supposed to do it ;)20:04
harlowjahttps://wiki.openstack.org/wiki/StructuredStateManagementDetails20:04
kebrayIf it's for the library… there is an ether pad started by Josh.20:04
*** cdub_ has joined #openstack-meeting20:04
kebrayAh, yes!20:04
kebrayPerfect harlowja20:04
shardy#link https://wiki.openstack.org/wiki/Convection20:04
harlowjait is slightly nova 'centric' but the general principles apply20:04
shardy#link https://wiki.openstack.org/wiki/StructuredStateManagementDetails20:04
*** radix has joined #openstack-meeting20:04
harlowja#link https://wiki.openstack.org/wiki/StructuredStateManagement20:04
shardyOk, looks like we can all start looking at those, thanks harlowja and kebray20:05
*** dolphm has joined #openstack-meeting20:05
harlowjaalso that one, i have started putting some of the base into nova, https://review.openstack.org/#/c/27869/ also20:05
harlowjaat least pieces of it to get moving20:05
harlowjaif we can fast-line the move to oslo then this could be put in there20:05
*** adrian17od has quit IRC20:05
harlowjathen we can try to make some base objects that work for as many projects as possible20:06
*** sandywalsh has quit IRC20:06
*** mgiles has joined #openstack-meeting20:06
*** vipul|away is now known as vipul20:06
shardyharlowja: sounds good, perhaps we can all start looking at this over the next week20:06
*** fsargent has joined #openstack-meeting20:06
harlowjathat'd be much appreciated20:06
shardy#action all to take a look at harlowja's wiki page and patch20:06
harlowjashardy there are also other workflow libraries that are interested to look at (at least the code/design)20:07
harlowjahttps://wiki.openstack.org/wiki/NovaOrchestration/WorkflowEngines20:07
harlowjafrom previous work, none of them handle the distributed case, but good to get ideas from20:07
shardyharlowja: Ok, there's the wider investigation, and also to see if/how we can consume this stuff in Heat20:08
shardyLet's continue this on the ML or in #heat if that's Okay20:08
harlowjashardy agreed, many efforts happening at once :)20:08
harlowjakk20:08
zanebtbh I see the distributed thing as the main issue20:08
shardy#topic Blueprint review for Havana, task assignment20:08
*** openstack changes topic to "Blueprint review for Havana, task assignment (Meeting topic: heat)"20:08
harlowjazaneb agreed :)20:08
zanebwhat we have already implemented in heat does the workflow part fine20:08
zaneb(for our purposes)20:08
harlowjazaneb sure, but the distributed+workflow parts are something all projects can benefit from i think20:09
*** krtaylor has quit IRC20:09
asalkeldyes, we need the locking20:09
harlowja*and liveness20:09
asalkeld(for scaling)20:09
zanebmy point was that a library that doesn't handle the locking doesn't buy us anything we couldn't write ourselves20:10
zanebanyway, back to the topic :)20:10
harlowjawell there a fundamental things that change depending on how the locking & livness is done, thats where it gets tricky20:10
shardy#link https://blueprints.launchpad.net/heat/havana20:10
shardylet's move on ;)20:10
harlowja:)20:11
shardySo I've been trying to beat the BP plan into shape20:11
shardyWe have some new BPs related to the Providers proposal zaneb made20:11
shardy#link https://blueprints.launchpad.net/heat/+spec/provider-resource20:11
shardy#link https://blueprints.launchpad.net/heat/+spec/json-parameters20:12
shardy#link https://blueprints.launchpad.net/heat/+spec/stack-metadata20:12
shardy#link https://blueprints.launchpad.net/heat/+spec/attributes-schema20:12
shardy#link https://blueprints.launchpad.net/heat/+spec/resource-template20:12
*** Dug1 has joined #openstack-meeting20:12
shardyzaneb: are youy planning to do this work, or are we looking for volunteers?20:12
*** dfg has left #openstack-meeting20:12
zanebvolunteers ;)20:13
asalkeldthose look well glued together20:13
*** vbannai has joined #openstack-meeting20:13
zanebI can help though20:13
randallburtI think we have some folks that can do those20:13
randallburtlater this week or early next20:13
zanebI don't have a firm plan for what I want to work on in Havana yet20:13
shardyOk, so I've made the heat-api-dsl BP depend on these20:13
*** clayg has left #openstack-meeting20:14
shardyrandallburt: if you can assign some names to these, that would be great, and work with zaneb to define the details of what has to be done20:14
randallburtshardy: not sure if its a hard dep, since we're still designing but I can see the point20:14
randallburtshardy:  will do20:14
zanebI'll start filling in the dependencies between those tasks20:14
shardyrandallburt: it was more of a "lets do these first" kind of thing, but feel free to remove if you disagree ;)20:14
*** bdpayne has quit IRC20:14
randallburtshardy:  kk. can we get an action for me so I won't forget?20:15
randallburtto assign folks, that is20:15
SpamapSless dependencies = more winning IMO :)20:15
shardy#action randallburt assign names to new BPs linked above20:15
*** dprince has quit IRC20:15
randallburtthanks20:15
*** mrutkows has joined #openstack-meeting20:15
shardySpamapS: point is I think we need to get this initial work done before we can sensibly proceed to the next step of the whole DSL discussion20:16
*** bdpayne has joined #openstack-meeting20:16
shardydoes anyone strongly disagree that we should do what Zane proposed, then see what else we're missing?20:16
asalkeldalso if we have to put our name against a bp, can we try be good about setting the state of the bp20:16
shardyasalkeld: +10020:16
*** tpatil has joined #openstack-meeting20:16
* shardy has done a lot of LP clicking this week ;)20:17
asalkeldso we can grab other bp if we have time20:17
shardyneed to look into ttx's scripts20:17
*** jrodom_ has quit IRC20:17
* asalkeld don't like this idea of sticking names to bp so early20:17
*** m4dcoder has joined #openstack-meeting20:17
randallburtasalkeld:  +120:18
shardyasalkeld: Ok, that's fine, if we want to leave stuff unassigned, but with the high priority stuff I was under the impression people wanted to get started on it20:18
SpamapSI tend to think the assignee of the BP is its manager, not necessarily the one who will do all the work.20:19
alexheneveldshardy: i think zane's proposal is a good direction but i'd really like to see more in the blueprints to better understand some of the details20:19
*** andrew_plunk has joined #openstack-meeting20:19
*** sandywalsh has joined #openstack-meeting20:19
shardyalexheneveld: which is exactly why I'm proposing we get some people to take ownership of them and do that work20:19
alexheneveldquid pro quo is we'd like to help ofc :)20:19
zanebI can maybe go through the blueprints and add details20:19
*** glange has left #openstack-meeting20:20
shardyzaneb: that would be excellent :)20:20
zanebshardy: feel free to add an action for me20:20
*** dontalton has joined #openstack-meeting20:20
shardy#action zaneb to add details to Provider BPs20:20
shardyOk, anything else BP related?20:20
*** dontalton2 has joined #openstack-meeting20:21
alexheneveld+1 excellent zaneb20:21
randallburtshardy: I can't assign bps. do I need to send you a list of names?20:21
shardyrandallburt: ping me and we'll work that out20:21
shardy#topic havana-1 milestone - need to target BPs and bugs20:22
*** openstack changes topic to "havana-1 milestone - need to target BPs and bugs (Meeting topic: heat)"20:22
*** ryanpetrello has joined #openstack-meeting20:22
randallburtwill do20:22
shardy#link https://wiki.openstack.org/wiki/Havana_Release_Schedule20:22
asalkeldshardy, when is h1?20:22
asalkeldthx20:22
shardy#link https://launchpad.net/heat/+milestone/havana-120:22
shardyasalkeld: 30th May20:22
shardynot much time :)20:22
asalkeldyea20:23
shardySo we need to figure out what bugs and BP's we can realistically target, since there's loads of bugs and not many BPs20:23
asalkeldnot many bps?20:24
*** anniec has joined #openstack-meeting20:24
shardyasalkeld: Only two are targetted to h120:24
SpamapSthats pretty normal I think20:24
asalkeldo, thought you meant in general20:24
SpamapSearly on fix some bugs, reorganize things, etc, before the more intense BP work happens20:24
SpamapSBPs tend to span several milestones20:25
zanebadded a third :)20:25
*** dontalton has quit IRC20:25
shardySpamapS: sure, I just want to get things somewhat representative of what's actually happening20:25
shardyso I don't get in trouble at the release meetings ;)20:25
shardy#action everyone to target bp's likely to land in next 2-3 weeks to havana-120:26
asalkeldk20:26
shardyAlso if there are bugs which need bumping to h-2, please do (e.g jpeeler you have a big backlog of VPC related stuff)20:26
*** cp16net|away is now known as cp16net20:26
jpeeleryeah i'll fix it up20:27
shardyI just realized I missed the first agenda item, oops20:27
shardylet's do it now :)20:27
shardy#topic Stable Branch/update/maintenance policy20:27
*** openstack changes topic to "Stable Branch/update/maintenance policy (Meeting topic: heat)"20:27
shardySo this came from a discussion in #heat20:28
shardyregarding what master should work with, as we've previously done stuff like conditional imports to maintain compatibility with older openstack versions20:28
asalkeldso is the plan now to rely on stable branch?20:29
*** m4dcoder_ has joined #openstack-meeting20:29
shardyasalkeld: that's basically the question20:30
SpamapSSo, I'm not sure that accurately describes the problem.20:30
SpamapSWhats at question is not maintaining backward compatibility with older openstack versions.20:30
*** m4dcoder has quit IRC20:30
SpamapSWe *must* do that20:30
*** ryanpetrello has quit IRC20:30
asalkeldreally?20:30
SpamapSthe issue is whether or not to depend on libraries that exist, but are not necessarily available on older platforms20:31
SpamapSWhat I take issue with is that we are treating the presence, or lack thereof, of say, quantumclient, as a signal that we should use quantum or not.20:31
*** ayoung is now known as ayoung-afk20:31
shardySpamapS: we don't necessarily have to do that in master, that's what the stable branches are for20:31
SpamapSThis is not a stable branch issue yet....20:31
zanebthe issue is how do we allow operators to select optional built-in plugins20:32
asalkeldwell we need to talk to older clients20:32
SpamapSI'm suggesting that if you can get heat, from master, you can get quantumclient. Even if you're not going to use it.20:32
SpamapSAnd this makes Heat more stable, as now it will be able to speak to quantum as soon as the catalog dictates that it do so.20:32
asalkeldso you want a config option to define the builtin catalog?20:33
*** lloydde has quit IRC20:34
SpamapSzaneb: the catalog dictates what you should be using.20:34
SpamapSasalkeld: no, keystone tells us "we have a quantum endpoint" or not.20:34
asalkeldbut still maybe the admin doen't want heat to use it20:35
*** lloydde has joined #openstack-meeting20:35
zanebas I said the other day, I am +2 on using keystone endpoint list to figure it out20:35
*** glikson has quit IRC20:36
shardyzaneb: Ok, but that would still require e.g folsom users to install e.g the grizzly client libraries?20:36
SpamapSasalkeld: I'm not sure there is a scenario where an admin says "use that keystone, but ignore the endpoints available", but I acknowledge that there may be one.20:36
zanebasalkeld: that sounds like an unusual case... they can always delete the plugin(s)20:36
SpamapSshardy: Why is it controversial to say "if you are installing havana's heat, you must also install havana-heat's dependencies" ?20:36
asalkeldjust saying if we have a catalog idea, use it20:36
therveso, what's the value of conditionally import clients?20:37
zanebshardy: client libraries are theoretically not versioned on the same cadence as core^W integrated projects20:37
shardySpamapS: because we know that we have existing users who are (or at least were) using master Heat with older openstack versions20:37
*** MarkAtwood has joined #openstack-meeting20:37
*** MarkAtwood has joined #openstack-meeting20:37
therveshardy, can they use newer client libraries though?20:37
SpamapSI am trying to understand the reason Heat wants to use the presence of the software as anything other than an indicator that you can use it.20:37
shardytherve: I guess that is true, it's something we've previously avoided though20:38
asalkeldthe problem is accessing new features when they are not backed20:38
SpamapSshardy: and we promised to them that we'd never add new dependencies?20:38
asalkeldnew client/old service20:38
shardySpamapS: This is the point, we've not made any formal promises, or even really discussed it20:38
SpamapSshardy: by all rights, we are already misrepresenting things by listing quantumclient et. al in tools/pip-requires20:38
shardyuntil now ;)20:38
zanebI hate pip-installing stuff over/around rpm packages, but I will live with it. What I don't want to do is make all these services show up as resource types even if you can't actually use them20:38
shardyzaneb: +1, and +120:39
SpamapSzaneb: right, but thats a problem if you have accidentally installed quantumclient.. isn't it?20:39
*** sean_s has quit IRC20:39
asalkeldother way around20:39
shardySounds like the catalog suggestion is the solution to the second problem20:40
zanebso keystone catalog solves second problem, at the expense of first problem which is annoying but not a big deal20:40
shardySpamapS: well with your prosal everyone will always have to install quantumclient..20:40
shardyproposal20:40
*** patrocinio has joined #openstack-meeting20:40
SpamapSyes, they will, and so we should provide them means to turn off quantum in their configuration. We already have that means though, in the form of the keystone catalog of endpoints.20:41
asalkeldI think we need our own version of a catalog20:41
asalkelduser catalog, builtin catalog20:41
zanebplease, no more config options ;)20:41
shardySpamapS: but our resource visibility isn't currently affected by the keystone catalog20:41
SpamapSOk I don't really agree with the need for that, but I don't think it is harmful.20:41
SpamapSshardy: Actually thats something else I'm confused by. What is listing resources? Is that a client call I haven't run into yet?20:42
zaneblisting resources?20:42
asalkeldwe need a resource-type-list20:42
zanebthere is an API call to get a list of resource types20:42
*** lindj has quit IRC20:42
asalkeldreally20:42
zanebin the ReST API20:42
zanebasalkeld: added it myself ;)20:42
asalkeldwell done20:43
shardySpamapS: currently it's about a graceful failure when a resource is not backed by a service, but in the future we've been talking about a resource catalog, ref zane's Provider proposal20:43
zanebasalkeld: stevebaker's idea iirc20:43
alexheneveldnice20:43
SpamapSRight, so I'm thinking the presence of client libraries is a really inconvenient and inaccurate way to predict whether or not the service is available.20:44
therveSpamapS, +120:44
shardyOk, shall we follow up on this via SpamapS bug #117400520:44
zanebasalkeld: next step is full schema - https://blueprints.launchpad.net/heat/+spec/resource-properties-schema20:44
uvirtbotLaunchpad bug 1174005 in heat "swiftclient, quantumclient, and cinderclient, are not optional" [Undecided,New] https://launchpad.net/bugs/117400520:44
SpamapSThere are 2 issues, and I think it will help if we can separate them.20:44
SpamapSright, the bug about the client libs not being optional is just one of maintenance and backward compatibility20:44
SpamapSthe other one is I think unreported and talks about more accurately providing a list of available resources.20:45
asalkelddon't see why swiftclient is required20:45
shardySpamapS: sounds like we need another BP ;)20:45
SpamapScrap20:45
SpamapSwe do20:45
* SpamapS will take it since I'm on about it20:45
shardy#action SpamapS to raise BP re available resources20:46
shardyOk, should we move on?20:46
asalkeld15min20:46
shardy#topic Feature proposal deadline20:46
*** openstack changes topic to "Feature proposal deadline (Meeting topic: heat)"20:46
SpamapSasalkeld: don't see why swiftclient isn't required. The day you add a swift endpoint, your heat servers should be able to talk to it. I see no reason to hold back on a simple python library. :-P20:46
SpamapSanyway, yes lets move on :)20:46
shardy#link http://lists.openstack.org/pipermail/openstack-dev/2013-April/007823.html20:46
shardyWhat do people think about aligning with what nova are doing ref BP proposal deadlines?20:47
harlowjaseems like a good idea20:47
shardyMaybe not such an issue for us being a smaller project, but seems like a good idea20:47
zanebIf anybody proposes a patch so large it will take 2 weeks to review, it should get -2 anyway imho20:47
kebraywhat do we gain from deciding that now?20:47
*** markvan has quit IRC20:48
shardykebray: we get to chime in on that thread and say "we'll do that too", so people will know what the plan is20:48
zanebsmall patches, incremental changes, this issue will never come up20:48
randallburtwe gain you not making me scrable two weeks before ff kebray ;)20:48
shardyzaneb: +1000 ;)20:48
*** jasond has joined #openstack-meeting20:48
kebray:-)  ok ok20:48
shardyOk, sounds like most are agreed then, lets go to open disucussion for the last 10mins?20:49
shardy#topic Open discussion20:49
*** openstack changes topic to "Open discussion (Meeting topic: heat)"20:49
SpamapSreason to do BP proposal deadlines is also just to keep the work focused on specs early in the cycle, so dev time happens well before FF.20:49
asalkeldhow about "if you propose a feature close to freaze, we might not merge"20:49
randallburtso, its fairly insignificant atm, but can I get eyes on https://review.openstack.org/#/c/27934/?20:50
wirehead_That's almost common-sense.20:50
asalkelddepending on ... stuff20:50
shardyasalkeld: this is basically just quantifying/documenting that20:50
zanebrandallburt: mixes spaces and tabs, -1 ;)20:50
randallburtand sorry, didn't mean to publish that one, but based on convo's yesterday, that's how we want to start evolving hot20:51
randallburtzaneb:  yikes! sorry about that.20:51
randallburtwill fix20:51
*** markvan has joined #openstack-meeting20:51
asalkeldI got not found20:51
zanebasalkeld: remove the ?20:51
shardyrandallburt: thanks for posting, I had a quick look, will post comments later20:51
randallburtasalkeld:  might have forgotten to add you20:51
asalkeldgot it now - "?"20:52
shardyI think refining the syntax through gerrit will be better than etherpad etc20:52
alexheneveldrandallburt: great starting this20:52
randallburtthanks20:52
*** egallen has joined #openstack-meeting20:52
randallburtI'm still under other commitments for a few more days but hope to have more drafts soon-ish20:52
randallburtand with consistent spacing to boot. ;)20:52
shardy#link https://review.openstack.org/#/c/27934/20:53
*** jcru is now known as jcru|away20:53
tspatzierrandallburt: I had a quick look and will also provide comments soon20:53
* kebray is working diligently to free randallburt's schedule.20:53
*** egallen has quit IRC20:53
asalkeldrandallburt, interesting part is how config/userdata gets into the instance20:53
randallburtasalkeld:  agreed. starting small, though ;)20:53
asalkeldyip20:54
asalkeld5 min left20:54
shardyanything else?20:54
*** dwcramer has quit IRC20:54
harlowjajoin my orchestration meeting tommorow!20:54
harlowja:)20:54
asalkeldtime?20:54
Changbinwhen is the time?20:54
harlowja2000UTC, taking over the previous sandy orchestration meeting20:54
*** shri has left #openstack-meeting20:55
harlowja#link https://wiki.openstack.org/wiki/Meetings#Orchestration_team_meeting20:55
Changbincool20:55
*** jcru|away is now known as jcru20:55
shardyharlowja: will try to make it :)20:55
harlowjacool20:55
harlowjato many meetings to go to :-P20:55
shardyanything else from anyone?20:56
*** egallen has joined #openstack-meeting20:56
shardyOk, thanks all20:56
shardy#endmeeting20:56
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"20:56
openstackMeeting ended Wed May  1 20:56:37 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-05-01-20.00.html20:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-05-01-20.00.txt20:56
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-05-01-20.00.log.html20:56
*** therve has left #openstack-meeting20:57
*** radix has left #openstack-meeting20:57
*** tspatzier has quit IRC20:57
*** jasond has left #openstack-meeting20:58
*** Changbin has quit IRC20:58
*** egallen_ has joined #openstack-meeting20:59
*** Changbin has joined #openstack-meeting20:59
*** alexheneveld has quit IRC21:00
*** Changbin has quit IRC21:00
*** egallen has quit IRC21:00
*** egallen_ is now known as egallen21:00
*** Changbin has joined #openstack-meeting21:01
*** changbl has joined #openstack-meeting21:01
*** lindj_ has joined #openstack-meeting21:02
*** jrodom has joined #openstack-meeting21:02
*** dripton has quit IRC21:02
*** sudorandom has left #openstack-meeting21:02
*** m4dcoder_ has left #openstack-meeting21:03
*** dripton has joined #openstack-meeting21:03
*** dwcramer has joined #openstack-meeting21:04
*** dripton has quit IRC21:04
*** dripton has joined #openstack-meeting21:06
*** mrutkows has left #openstack-meeting21:15
*** sarob_ has joined #openstack-meeting21:16
*** lindj_ has quit IRC21:16
*** ayoung-afk is now known as ayoung-soapbox21:16
*** ayoung-soapbox is now known as ayoung21:16
*** ryan_rs has quit IRC21:19
*** sarob_ has quit IRC21:20
*** diogogmt has joined #openstack-meeting21:20
*** stevemar has quit IRC21:21
*** mdenny has joined #openstack-meeting21:22
*** ayoung is now known as ayoung-kidz21:23
*** wirehead_ has left #openstack-meeting21:26
*** mgiles has quit IRC21:32
*** bdpayne has quit IRC21:33
*** bdpayne has joined #openstack-meeting21:35
*** roampune_ has joined #openstack-meeting21:40
*** topol has quit IRC21:40
*** mikal__ is now known as mikal21:42
*** roampune has quit IRC21:43
*** roampune_ has quit IRC21:44
*** sacharya has quit IRC21:44
*** davidhadas has quit IRC21:45
*** litong has quit IRC21:46
*** amyt_ has joined #openstack-meeting21:46
*** amyt has quit IRC21:47
*** amyt_ is now known as amyt21:47
*** egallen has quit IRC21:48
*** anniec has quit IRC21:49
*** davidh__ has joined #openstack-meeting21:49
*** dontalton has joined #openstack-meeting21:50
*** randallburt has left #openstack-meeting21:51
*** boris-42 has quit IRC21:51
*** dontalton2 has quit IRC21:51
*** changbl has quit IRC21:52
*** markvan has quit IRC21:54
*** jrodom has quit IRC21:56
*** jrodom has joined #openstack-meeting21:56
*** dwcramer has quit IRC21:57
*** stevemar2 has joined #openstack-meeting22:00
*** diogogmt has quit IRC22:03
*** anteaya has quit IRC22:04
*** markvan has joined #openstack-meeting22:04
*** patrocinio has quit IRC22:06
*** lbragstad has quit IRC22:07
*** salv-orlando has quit IRC22:07
*** cdub_ has quit IRC22:09
*** tpatil has quit IRC22:09
*** cdub_ has joined #openstack-meeting22:10
*** radez is now known as radez_g0n322:11
*** roampune has joined #openstack-meeting22:11
*** esker has quit IRC22:13
*** esker has joined #openstack-meeting22:13
*** maoy has quit IRC22:17
*** ivasev has quit IRC22:18
*** zzs has quit IRC22:19
*** esker has quit IRC22:19
*** zzs has joined #openstack-meeting22:20
*** dhellmann has quit IRC22:24
*** roampune has quit IRC22:25
*** sacharya has joined #openstack-meeting22:25
*** rnirmal has quit IRC22:26
*** armax has left #openstack-meeting22:26
*** jrodom has quit IRC22:27
*** anniec has joined #openstack-meeting22:27
*** anniec has joined #openstack-meeting22:27
*** markvan has quit IRC22:32
*** eharney has quit IRC22:32
*** jrodom has joined #openstack-meeting22:32
*** hemna is now known as hemnafk22:33
*** markpeek has quit IRC22:35
*** stevemar2 has quit IRC22:37
*** flaper87 has quit IRC22:37
*** vkmc has quit IRC22:38
*** SergeyLukjanov has quit IRC22:43
*** dolphm has quit IRC22:45
*** flwang has quit IRC22:50
*** kebray has quit IRC22:51
*** vipul is now known as vipul|away22:57
*** amyt has quit IRC22:59
*** otherwiseguy has quit IRC23:00
*** dolphm has joined #openstack-meeting23:00
*** fnaval_ has quit IRC23:00
*** mdenny has quit IRC23:01
*** woodspa has quit IRC23:02
*** salv-orlando has joined #openstack-meeting23:03
*** dolphm_ has joined #openstack-meeting23:04
*** dolphm has quit IRC23:06
*** jrodom has quit IRC23:08
*** jcru has quit IRC23:08
*** salv-orlando has quit IRC23:12
*** changbl has joined #openstack-meeting23:16
*** sacharya has quit IRC23:23
*** garyTh has quit IRC23:23
*** cdub_ has quit IRC23:24
*** dontalton has quit IRC23:30
*** markwash has quit IRC23:32
*** gyee has quit IRC23:37
*** stevemar has joined #openstack-meeting23:37
*** flwang has joined #openstack-meeting23:43
*** jaypipes has quit IRC23:44
*** otherwiseguy has joined #openstack-meeting23:47
*** sacharya has joined #openstack-meeting23:47
*** matiu has quit IRC23:47
*** matiu has joined #openstack-meeting23:47
*** matiu has joined #openstack-meeting23:47
*** vipul|away is now known as vipul23:48
*** nati_ueno has joined #openstack-meeting23:48
*** dwcramer has joined #openstack-meeting23:48
*** lloydde has quit IRC23:48
*** stevemar has quit IRC23:52
*** ozstacker has quit IRC23:58

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