Wednesday, 2012-11-21

*** etoews has joined #openstack-meeting00:03
*** almaisan-away is now known as al-maisan00:05
*** al-maisan is now known as almaisan-away00:06
*** ywu_ has quit IRC00:08
*** ywu_ has joined #openstack-meeting00:08
*** lloydde has quit IRC00:11
*** vipul is now known as vipul|away00:13
*** vipul|away is now known as vipul00:13
*** dendrobates has quit IRC00:16
*** ywu_ has quit IRC00:22
*** ywu_ has joined #openstack-meeting00:22
*** jdbarry has left #openstack-meeting00:27
*** dkehn is now known as dkehn_afk00:27
*** vipul is now known as vipul|away00:28
*** sarob_ has joined #openstack-meeting00:30
*** vipul|away is now known as vipul00:32
*** sarob has quit IRC00:32
*** ywu_ has quit IRC00:36
*** ywu_ has joined #openstack-meeting00:37
*** ywu_ has quit IRC00:37
*** ywu_ has joined #openstack-meeting00:37
*** ywu_ has quit IRC00:41
*** ywu_ has joined #openstack-meeting00:41
*** ijw11 has quit IRC00:43
*** stevebake has quit IRC00:46
*** lloydde has joined #openstack-meeting00:47
*** ddemir_ has joined #openstack-meeting00:51
*** jcooley is now known as jcooley_afk00:51
*** ywu_ has quit IRC00:52
*** ddemir_ is now known as ddemir00:52
*** ywu_ has joined #openstack-meeting00:52
*** ddemir has quit IRC00:57
*** afazekas has quit IRC01:00
*** patelna has quit IRC01:00
*** lloydde has quit IRC01:03
*** stevebake has joined #openstack-meeting01:04
*** ywu_ has quit IRC01:07
*** ywu_ has joined #openstack-meeting01:07
*** andrewbogott is now known as andrewbogott_afk01:12
*** ywu_ has quit IRC01:22
*** ywu_ has joined #openstack-meeting01:22
*** colinmcnamara1 has quit IRC01:22
*** jcooley_afk is now known as jcooley01:25
*** saurabhs has left #openstack-meeting01:25
*** sarob_ has quit IRC01:34
*** ywu_ has quit IRC01:36
*** ywu_ has joined #openstack-meeting01:36
*** ywu_ has quit IRC01:37
*** ywu_ has joined #openstack-meeting01:37
*** martine has joined #openstack-meeting01:38
*** zoumpis has joined #openstack-meeting01:38
*** salv-orlando_ has joined #openstack-meeting01:40
*** salv-orlando has quit IRC01:40
*** salv-orlando_ is now known as salv-orlando01:40
*** ddemir has joined #openstack-meeting01:40
*** salv-orlando has quit IRC01:41
*** salv-orlando has joined #openstack-meeting01:41
*** markmcclain has joined #openstack-meeting01:42
*** NobodyCam is now known as NobodyCam_afk01:44
*** stevebake has quit IRC01:52
*** anniec has quit IRC01:55
*** nati_ueno_2 has joined #openstack-meeting01:59
*** salv-orlando has quit IRC02:01
*** nati_ueno has quit IRC02:01
*** MarkAtwood has quit IRC02:02
*** almaisan-away has quit IRC02:07
*** almaisan-away has joined #openstack-meeting02:08
*** lloydde has joined #openstack-meeting02:08
*** nati_ueno has joined #openstack-meeting02:10
*** hemna has quit IRC02:11
*** nati_ueno_2 has quit IRC02:12
*** lloydde has quit IRC02:13
*** metral has quit IRC02:16
*** metral has joined #openstack-meeting02:16
*** dkehn_afk is now known as dkehn02:24
*** juice__ is now known as juice02:27
*** juice__ has joined #openstack-meeting02:28
*** maoy has quit IRC02:38
*** dkehn is now known as dkehn_zzz02:41
*** zoumpis has quit IRC02:41
*** Mandell has quit IRC02:42
*** juice__ has quit IRC02:46
*** juice_otg has joined #openstack-meeting02:46
*** danwent has quit IRC02:49
*** juice has quit IRC02:50
*** jcooley is now known as jcooley_afk02:50
*** jcooley_afk is now known as jcooley02:54
*** stevebake has joined #openstack-meeting02:58
*** rushiagr has joined #openstack-meeting02:59
*** jcooley is now known as jcooley_afk03:00
*** rushiagr1 has joined #openstack-meeting03:00
*** juice_otg has quit IRC03:00
*** stevebake has quit IRC03:03
*** rushiagr has quit IRC03:04
*** novas0x2a|laptop has quit IRC03:05
*** jcooley_afk is now known as jcooley03:08
*** colinmcnamara has joined #openstack-meeting03:10
*** stevebake has joined #openstack-meeting03:11
*** rushiagr1 has quit IRC03:19
*** ywu_ has quit IRC03:20
*** MarkAtwood has joined #openstack-meeting03:25
*** adjohn has quit IRC03:26
*** esp has joined #openstack-meeting03:31
*** esp has left #openstack-meeting03:33
*** nati_ueno has quit IRC03:37
*** vincent_hou has joined #openstack-meeting03:46
*** colinmcnamara has left #openstack-meeting03:53
*** samkottler|afk is now known as samkottler03:54
*** etoews has quit IRC03:56
*** colinmcnamara has joined #openstack-meeting03:57
*** jog0 has quit IRC04:03
*** samkottler is now known as samkottler|afk04:10
*** shang has joined #openstack-meeting04:22
*** novas0x2a|laptop has joined #openstack-meeting04:24
*** Mandell has joined #openstack-meeting04:36
*** rushiagr has joined #openstack-meeting04:39
*** ddemir has left #openstack-meeting04:42
*** adjohn has joined #openstack-meeting04:46
*** adjohn has quit IRC04:47
*** nati_ueno has joined #openstack-meeting04:59
*** jcooley is now known as jcooley_afk05:03
*** nati_ueno has quit IRC05:14
*** vincent_hou_ has joined #openstack-meeting05:15
*** vincent_hou_ has quit IRC05:15
*** koolhead17 has joined #openstack-meeting05:17
*** vincent_hou has quit IRC05:17
*** markmcclain has quit IRC05:34
*** colinmcnamara has quit IRC05:36
*** nati_ueno has joined #openstack-meeting05:37
*** garyk has quit IRC05:39
*** martine has quit IRC05:51
*** jcooley_afk is now known as jcooley05:56
*** koolhead17 has quit IRC06:08
*** nati_ueno has quit IRC06:11
*** adjohn has joined #openstack-meeting06:11
*** nati_ueno has joined #openstack-meeting06:12
*** adjohn has quit IRC06:13
*** garyk has joined #openstack-meeting06:38
*** reed has quit IRC06:38
*** adjohn has joined #openstack-meeting06:40
*** nati_ueno_2 has joined #openstack-meeting06:45
*** nati_ueno has quit IRC06:46
*** adjohn has quit IRC06:48
*** adjohn has joined #openstack-meeting06:49
*** juice_otg has joined #openstack-meeting06:51
*** eglynn has joined #openstack-meeting06:54
*** eglynn__ has quit IRC06:57
*** mikal has quit IRC06:58
*** mikal has joined #openstack-meeting06:59
*** jcooley is now known as jcooley_afk07:06
*** juice_otg has quit IRC07:08
*** jcooley_afk is now known as jcooley07:15
*** adjohn has quit IRC07:16
*** jcooley is now known as jcooley_afk07:17
*** adjohn has joined #openstack-meeting07:22
*** juice_otg has joined #openstack-meeting07:25
*** adjohn has quit IRC07:29
*** henrynash has joined #openstack-meeting07:36
*** juice_otg has quit IRC07:37
*** henrynash has quit IRC07:42
*** afazekas has joined #openstack-meeting07:48
*** reed has joined #openstack-meeting07:52
*** nati_ueno has joined #openstack-meeting07:52
*** nati_ueno_2 has quit IRC07:54
*** rafaduran has joined #openstack-meeting08:00
*** mikal has quit IRC08:10
*** jhenner has joined #openstack-meeting08:19
*** EmilienM has joined #openstack-meeting08:29
*** afazekas has quit IRC08:34
*** jhenner has quit IRC08:35
*** tr3buchet has quit IRC08:36
*** zbitter has joined #openstack-meeting08:47
*** afazekas has joined #openstack-meeting08:51
*** zaneb has quit IRC08:51
*** Razique has joined #openstack-meeting08:51
*** tr3buchet2 has quit IRC09:02
*** tr3buchet has joined #openstack-meeting09:05
*** davidkranz_ has joined #openstack-meeting09:06
*** davidkranz has quit IRC09:06
*** derekh has joined #openstack-meeting09:07
*** jhenner has joined #openstack-meeting09:10
*** darraghb has joined #openstack-meeting09:11
*** afazekas has quit IRC09:16
*** mikal has joined #openstack-meeting09:28
*** jhenner has quit IRC09:31
*** dendrobates has joined #openstack-meeting09:31
*** salv-orlando has joined #openstack-meeting09:32
*** henrynash has joined #openstack-meeting09:42
*** jhenner has joined #openstack-meeting09:46
*** Mandell has quit IRC09:47
*** afazekas has joined #openstack-meeting09:49
*** Razique has quit IRC09:53
*** mnewby has quit IRC09:56
*** mnewby has joined #openstack-meeting09:56
*** Razique has joined #openstack-meeting10:01
*** mnewby_ has joined #openstack-meeting10:03
*** mnewby has quit IRC10:05
*** mnewby_ is now known as mnewby10:05
*** ijw1 has joined #openstack-meeting10:12
*** ijw1 has quit IRC10:17
*** ijw1 has joined #openstack-meeting10:17
*** zbitter has left #openstack-meeting10:30
*** henrynash has quit IRC10:36
*** littleidea has quit IRC10:39
*** highthem has joined #openstack-meeting10:47
*** maurosr has joined #openstack-meeting11:06
*** highthem has quit IRC11:12
*** arbrandes has joined #openstack-meeting11:17
*** shengjie has quit IRC11:28
*** rushiagr has left #openstack-meeting11:41
*** Razique has quit IRC11:44
*** dwcramer has quit IRC11:57
*** jgriffith has quit IRC12:01
*** jgriffith has joined #openstack-meeting12:01
*** Razique has joined #openstack-meeting12:10
*** anniec has joined #openstack-meeting12:28
*** qiangq has joined #openstack-meeting12:41
*** qiangq has quit IRC12:42
*** anniec has quit IRC12:46
*** tongli has joined #openstack-meeting12:53
*** tongli has quit IRC13:03
*** dhellmann_ has joined #openstack-meeting13:08
*** samkottler|afk is now known as samkottler13:09
*** dhellmann has quit IRC13:10
*** dhellmann_ is now known as dhellmann13:10
*** samkottler is now known as samkottler|afk13:10
*** anniec has joined #openstack-meeting13:11
*** MarkAtwood has left #openstack-meeting13:16
*** vincent_ has joined #openstack-meeting13:23
*** dprince has joined #openstack-meeting13:23
*** bourke_ has joined #openstack-meeting13:26
*** huats_ has joined #openstack-meeting13:27
*** huats_ has quit IRC13:27
*** huats_ has joined #openstack-meeting13:27
*** sleepsonzzz has joined #openstack-meeting13:28
*** devcamca- has joined #openstack-meeting13:28
*** jd__- has joined #openstack-meeting13:29
*** brianr-a1ay has joined #openstack-meeting13:29
*** alaski_ has joined #openstack-meeting13:30
*** vincent_ is now known as vincent_hou13:30
*** anniec has quit IRC13:31
*** tasdomas` has joined #openstack-meeting13:32
*** radez_g0` has joined #openstack-meeting13:33
*** EmilienM_ has joined #openstack-meeting13:33
*** sdague_ has joined #openstack-meeting13:34
*** huats has quit IRC13:34
*** sdague has quit IRC13:34
*** EmilienM has quit IRC13:34
*** jd__ has quit IRC13:34
*** tasdomas has quit IRC13:34
*** anderstj has quit IRC13:34
*** bourke has quit IRC13:34
*** brianr-away has quit IRC13:34
*** radez_g0n3 has quit IRC13:34
*** devcamcar has quit IRC13:34
*** sleepsonthefloor has quit IRC13:34
*** alaski has quit IRC13:34
*** sleepsonzzz is now known as sleepsonthefloor13:34
*** jd__- is now known as jd__13:34
*** EmilienM_ is now known as EmilienM13:34
*** sdague_ is now known as sdague13:34
*** anderstj has joined #openstack-meeting13:35
*** anniec has joined #openstack-meeting13:36
*** cdub has quit IRC13:38
*** cdub has joined #openstack-meeting13:40
*** echohead has quit IRC13:43
*** echohead_ has joined #openstack-meeting13:43
*** echohead_ is now known as echohead13:43
*** reed has quit IRC13:44
*** spligak has quit IRC13:44
*** spligak has joined #openstack-meeting13:44
*** reed has joined #openstack-meeting13:46
*** dhellmann is now known as dhellmann-afk13:46
*** jcru has joined #openstack-meeting13:54
*** jcru has quit IRC13:54
*** jcru has joined #openstack-meeting13:54
*** fnaval has quit IRC14:08
*** ryanpetrello has joined #openstack-meeting14:11
*** arbrandes has quit IRC14:12
*** dkehn_zzz is now known as dkehn14:16
*** annegentle_ has joined #openstack-meeting14:20
*** roadTripper has joined #openstack-meeting14:24
*** littleidea has joined #openstack-meeting14:32
*** alaski_ is now known as alaski14:34
*** annegentle_ has quit IRC14:37
*** NobodyCam_afk is now known as NobodyCam14:41
*** fnaval has joined #openstack-meeting14:45
*** zoumpis has joined #openstack-meeting14:48
*** littleidea has quit IRC14:55
*** roadTripper has quit IRC14:56
*** rnirmal has joined #openstack-meeting14:56
*** roadTripper has joined #openstack-meeting14:56
*** anniec has quit IRC14:59
*** cdub has quit IRC15:01
*** andrewbogott_afk is now known as andrewbogott15:02
*** cdub has joined #openstack-meeting15:02
*** samkottler|afk is now known as samkottler15:03
*** Razique has quit IRC15:13
*** Razique has joined #openstack-meeting15:13
*** littleidea has joined #openstack-meeting15:16
*** vincent_hou has quit IRC15:17
*** jaypipes has joined #openstack-meeting15:19
*** ijw11 has joined #openstack-meeting15:21
*** danwent has joined #openstack-meeting15:22
*** ijw1 has quit IRC15:26
*** egallen has joined #openstack-meeting15:31
*** markmcclain has joined #openstack-meeting15:31
*** rushiagr has joined #openstack-meeting15:34
*** dhellmann-afk is now known as dhellmann15:34
*** j_king has joined #openstack-meeting15:35
*** juice_ has joined #openstack-meeting15:36
*** frankm_ has joined #openstack-meeting15:37
*** rushiagr has quit IRC15:38
*** ijw11 is now known as ijw15:40
*** jcooley_afk is now known as jcooley15:44
*** juice_ has quit IRC15:47
*** jcooley is now known as jcooley_afk15:49
*** ijw has quit IRC15:50
*** ijw1 has joined #openstack-meeting15:50
*** bswartz has joined #openstack-meeting15:50
*** cp16net is now known as cp16net|away15:50
*** cp16net|away is now known as cp16net15:50
*** rushiagr has joined #openstack-meeting15:51
*** avishay has joined #openstack-meeting15:56
*** juice_ has joined #openstack-meeting15:56
*** dtynan has joined #openstack-meeting15:56
avishayHi.  Is the meeting happening or canceled for Thanksgiving?15:59
*** winston-d has joined #openstack-meeting15:59
*** arbrandes has joined #openstack-meeting15:59
bswartzI'm pretty sure it's going forward15:59
bswartzthanksgiving is an american holiday, and cinder is a worldwide project16:00
jgriffithbswartz: You are correct good sir :)16:00
jgriffith#startmeeting cinder16:00
openstackMeeting started Wed Nov 21 16:00:32 2012 UTC.  The chair is jgriffith. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
openstackThe meeting name has been set to 'cinder'16:00
*** thingee has joined #openstack-meeting16:00
jgriffithHey everybody!!!16:00
jgriffiththingee: shouldn't you be asleep???16:01
*** jdurgin1 has joined #openstack-meeting16:01
jgriffithrussellb: hola16:01
jgriffithbswartz: morning16:01
thingeejgriffith: no sleep till brooklyn16:01
jgriffiththingee: NICE!!!!16:01
jgriffithalright, I don't have a ton of formal stuff on the agenda16:02
jgriffithJust one thing in fact....16:02
jgriffith#topic G1 status16:02
*** openstack changes topic to "G1 status"16:02
jgriffithSo the good news is that everything we targetted is in review except the driver stuff but that's on it's way16:02
*** dwn has joined #openstack-meeting16:02
jgriffithThe bad news is that I thought we had until Thursday...16:02
jgriffithBut I forgot to account for the repo lockdown we typically get the 3 days prior to release :(16:03
thingeeoh man16:03
jgriffithttx: has agreed to give us a day or two to catch up16:03
jgriffithI won't forget again, totally my bad16:04
jgriffithSo those of you that I've been bugging the heck out of since yesterday now you know why16:04
jgriffiththingee: It looks like all of your deliverables are ready to go just need reviews yes?16:04
*** avishay_ has joined #openstack-meeting16:04
*** redthrux has joined #openstack-meeting16:05
winston-dhi, all16:05
jgriffithMaybe we lost thingee16:05
jgriffithwinston-d: Howdy16:05
thingeejgriffith: so last night I got done with all the changes requested by people I talked to. Tests pass, I wanted to try things manually and I'm getting some funky results16:05
DuncanTI'm more than half way through the API v2 review without finding anything major16:05
jgriffiththingee: hmmm16:05
jgriffiththingee: need some help from any of us?16:05
avishay_Is the API set or is this just framework?16:06
thingeewell it's just weird stuff where it's the same change I'm bring into my test devstack instance, but it doesn't appear to care about the cinder client changes. for example I removed main method out of and it still works :)16:06
*** dhellmann is now known as dhellmann-afk16:07
jgriffiththingee: hrmm?16:07
thingeeremoved pyc files, reloaded cinder api server for the api its changes but no luck...going to play around with it some more16:07
*** jcooley_afk is now known as jcooley16:07
*** redthrux has quit IRC16:07
thingeeavishay_: framework16:07
*** redthrux has joined #openstack-meeting16:08
thingeeI updated the bp to reflect this and created bps for stuff people asked for16:08
jgriffiththingee: that's odd, devstack there's usually no loadin or anything typically for the client/shell16:08
*** cdub has quit IRC16:08
*** cdub has joined #openstack-meeting16:08
jgriffiththingee: Ok... let us know if we can help16:08
*** avishay has quit IRC16:08
jgriffithwinston-d: You're next on my list :)16:08
thingeeoh yeah, well this is for list-bootable volumes, so it involves api changes and client changes16:08
jgriffiththingee: Ohhh...16:09
*** jcooley is now known as jcooley_afk16:09
jgriffiththingee: Make sure you wrap service type around the api call in the shell16:09
avishay_thingee: thanks16:09
*** avishay_ is now known as avishay16:09
jgriffiththingee: although there shouldn't be a conflict in this case...16:09
winston-djgriffith, russellb has a good suggestion and i'm working on it.16:10
jgriffithwinston-d: Looks like russellb had a suggestion...16:10
jgriffithwinston-d: You finished my thought :)16:10
russellbi think that one needs to be bumped to after grizzly-116:10
russellbit's going to take a while to work that out16:10
jgriffithrussellb: winston-d fair16:11
jgriffithwinston-d: I'll leave it to you to tell me what you need there16:11
jgriffithwinston-d: the other one was the type scheduler16:11
jgriffithwinston-d: I thought we merged that one?16:11
jgriffithwinston-d: errr...sorry16:12
winston-djgriffith,  you mean volume RPC api versioning? yes, we merged it.16:12
russellbthe blueprint shows that the filter scheduler is the implementation of it16:12
jgriffithrpcc versions16:12
jgriffithwinston-d: Ok, I'll get the RPC versioning one updated/fixed16:13
winston-djgriffith, thx.16:13
jgriffithwinston-d: Do you agree with russellb that we should push the filter change out?16:13
jgriffithwinston-d: Or would you like some time to look at it before answering16:14
*** dolphm has joined #openstack-meeting16:15
winston-djgriffith, well, since the # of reviews it's got is very few, i agree that we push filter scheduler change.16:15
jgriffithwinston-d: fair enough...16:15
bswartzI'm working on reviewing that -- it's a lot of stuff though16:16
jgriffithbswartz: yes it sure is16:16
jgriffithalright... I'll leave it for now, but this afternoon I'll plan on retargetting unless something miraculous happens :)16:16
winston-dbswartz, yeah, already breaking out a lot needed changes (and had them merged).16:16
*** ehm has joined #openstack-meeting16:16
jgriffithThe other change is mate's XenServer fixes16:17
jgriffithI'd like to get this one wrapped up if we can16:17
jgriffithIt's been through most of the review process, just a recent upate for the new pep-816:18
DuncanTIt looked good to me, then PEP8 threw a strop... happy to approve as soon as it passes gating again16:18
jgriffithDuncanT: excellent16:18
jgriffithThe only other thing is the remainder of the volume driver changes16:18
jgriffithI started it last night, but rnirmal pinged me this morning and he's about got it done16:19
jgriffithso we should see that land later today and be able to button that up16:19
*** dolphm has quit IRC16:19
*** zoumpis has quit IRC16:19
jgriffithI won't speak to the changes until it's available, but I think we've talked about it enough that it shouldn't be a big surprise16:20
jgriffithalso we are planning to do some things to keep backward compat with specifying the driver16:20
jgriffithso it should be non-controversial16:21
jgriffithSo that's about it...16:21
avishayjgriffith: which volume driver changes?16:21
jgriffithavishay: the layout changes16:21
avishayjgriffith: OK16:21
jgriffithavishay: So it would look something like:  /volume/driver/san/xxx, xxx, xxx, xx16:21
avishayjgriffith: Yep16:22
jgriffithavishay: and volume/drivers/xiv, netapp.x, etc etc16:22
jgriffithI need folks to keep an eye on reviews today if they could please16:22
*** radez_g0` is now known as radez16:23
jgriffithWe need to make sure we get the G1 changes in16:23
jgriffith#topic open floor16:23
*** openstack changes topic to "open floor"16:23
ttxjgriffith: any chance that we could cut at the end of today ?16:23
jgriffithttx: I think if we bump the type scheduler work I think we can yes16:23
jgriffithttx: That's my plan anyway16:23
ttxthat's reasonable, defer early to focus on the rest16:23
jgriffithttx: yeah, it's pretty much ready but it's a very big change and I don't think we're comfortable rushing the reviews on it16:24
*** cdub has quit IRC16:24
ttxjgriffith: I'll be back 5 hours from now for a go/nogo16:24
jgriffithttx: fair... thanks!16:24
*** cdub has joined #openstack-meeting16:24
bswartzat the end of the last meeting I asked if we coudl add rushiagr to the core team -- it sort of got lost in the discussion16:24
ttxbut I won't cut the branch until tomorrow eu morning anyway16:24
jgriffithttx: yeah, but I'd like to have things stabilized so to speak by end of today :016:25
jgriffithI'm out tomorrow, travel tonight so my deadline is shorter :)16:25
jgriffithbswartz: You can nominate and propose using the standard method16:27
jgriffithbswartz: However I have the same response as I've had in the past16:27
bswartzis the standard method something other than proposing it in this meeting?16:27
*** egallen has quit IRC16:27
jgriffithbswartz: There are requirements/responsbilities associatd with core that need to be met16:27
jgriffithbswartz: proposing here is fine, or bring up a formal nomination via the mail list16:28
jgriffithbswartz: You should have noticed a number of these went out over the last week16:28
jgriffithbswartz: for a number of projects16:28
bswartzI have just yesterday sorted out my email list problems16:29
jgriffithbswartz: Understood16:29
jgriffithbswartz: So TBH I would -1 it anyway16:29
jgriffithrushiagr: no offense16:29
rushiagrjgriffith: its okay, I understand16:30
zykes-question, how's FC support going ?16:30
jgriffithrushiagr: If it's something you want to do keep plugged in, do reviews and submit bug fixes etc16:30
*** zoumpis has joined #openstack-meeting16:31
jgriffithrushiagr: I'd love to have you, and need core members so I don't want to discourage you at all16:31
jgriffithrushiagr: s/I'd/We'd/16:31
* jgriffith will try to find the guidelines wiki for core team membership16:32
rushiagrjgriffith: sure, i will definitely pay more attention to it16:32
jgriffithOf course if others have input by all means let's hear it16:32
thingeejgriffith: +116:33
winston-djgriffith, +116:34
jgriffithbswartz: Do you have a counter?16:34
bswartzno, Rushi will come up to speed on all the responsibilities eventually16:34
zykes-jgriffith: or anyone care to give a #fc status once this topic is done ?16:35
jgriffithjdurgin1: thanks16:35
jgriffithzykes-: sure...16:35
rushiagrbswartz: +1 :)16:35
jgriffithbswartz: rushiagr awesome16:36
avishayi would also like to queue up a topic on standardizing capability keys (see my comment on the filter scheduler patch)16:36
jgriffithavishay: Ok...  first zykes16:36
jgriffith#topic fc-update16:36
*** openstack changes topic to "fc-update"16:37
avishayjgriffith: I know how a queue works ;P16:37
jgriffithzykes-: I spoke with kmartin briefly last week16:37
jgriffithzykes-: They're *finally* making progress on getting some things through HP legal16:37
jgriffithzykes-: There's been a bit more detail added to the bp here:
jgriffithzykes-: We're hoping to start seeing some code next week16:38
jgriffithzykes-: First pass is management/attachment only16:38
jgriffithzykes-: No switch management or zoning support16:39
jgriffithzykes-: So that will all have to be done outside of OpenStack by an admin for the time being16:39
zykes-jgriffith: what will it be then ?16:39
jgriffithzykes-: So it's a driver to manage the storage devices of course, and the ability to FC attach to a compute host16:39
jgriffithzykes-: Brocade and other folks are involved so the topology extensions should come along16:40
jgriffithzykes-: I just haven't recieved any real updates on how that's going to look and who wins out of the gate16:40
jgriffithok... anything else on FC?16:41
* jgriffith doesn't have a ton there....16:41
jgriffithzykes-: We'll be hitting you up as soon as patches start to land :)16:42
*** arbrandes has quit IRC16:42
jgriffithzykes-: I'll expect some good reviews and some testing :)16:42
*** sandywalsh has joined #openstack-meeting16:43
avishayjgriffith: Yes16:43
zykes-be sure to do jgriffith !16:43
jgriffith#topic capability keys16:43
*** openstack changes topic to "capability keys"16:43
avishayBasically, I think there should be some documentation on the capability keys to make sure all drivers are using the same ones16:43
avishayE.g., if one uses "volume_size" and another "vol_size", the filter scheduler won't work too well16:44
winston-davishay, i have something RFC here, very rough but still:
jgriffithavishay: Yeah, we talked about that16:44
jgriffithAhh... rnirmal is on it!16:45
winston-drnirmal, beats me to it. :D16:45
*** Razique has quit IRC16:45
jgriffithavishay: That should address your concerns :16:45
avishayThank you all :)16:45
rnirmallets agree upon  the capabilities so that we can get the filter scheduler in .. winston-d has been on it for way too long16:45
rnirmalwinston-d: you really are patient16:45
jgriffithrnirmal: +1!!!!!!16:46
avishayI think we should agree on the set of capabilities that all drivers MUST implement, and there should also be a set that drivers could add (e.g., thin provisioning support, compression support, whatever)16:46
avishayThe second being capabilities with a high probability that multiple drivers will use16:46
jgriffithavishay: I see that as a next step16:47
winston-drnirmal, well, it is a big patch, so i don't want to be pushy.16:47
avishayOr maybe once one driver defines a capability, it goes in the document and other drivers should use the same name16:47
*** dprince has quit IRC16:48
rnirmalI think it's best to start off with basic capabilities and then have a section for specific capabilities like "extra specs"16:48
jgriffithrnirmal: agreed16:48
winston-davishay, totally agree. i tried to have something in LVM iSCSI driver as an example.16:49
*** jcru has quit IRC16:49
jgriffithI'd first like to settle on what we require to be reported (whether it's supported or not is irrelevant right now IMO)16:49
winston-davishay, rnirmal, for MUST implement capabilities right now, is just 'total_capacity_gb', 'free_capacity_gb', 'reserved_percentage'.16:49
avishaymaybe we just need to keep track of the keys being used and developers/reviewers make sure that new submissions use that list16:49
*** dolphm has joined #openstack-meeting16:50
winston-davishay, sure, i will definitely do that.16:50
DuncanTWhat does 'reserved_percentage' mean in this context?16:50
jgriffithavishay: I was thinking once we sort this out we actually implement a report capabilities method that's inheritted16:50
rnirmalprovisionable ratio16:50
jgriffithavishay: That way the keys are set, etc16:51
rnirmaldon't provision more than 80% of storage etc.... so reserved_percentage would be 20 in that case16:51
*** cdub has quit IRC16:51
DuncanTrnirmal: Ah, got you, cheers16:51
rnirmalwinston-d: is that the correct assumption16:51
avishayjgriffith: that could work16:51
*** cdub has joined #openstack-meeting16:51
jgriffithavishay: I still see your point about reviews, but that's a given IMO16:52
jgriffithavishay: Once we settle on what those keys are :)16:52
winston-drnirmal, that's right.16:52
*** ollie1 has joined #openstack-meeting16:53
*** jcru has joined #openstack-meeting16:53
avishayjgriffith: well even if IBM comes out with feature foobarbaz and i add a key for that, and a month later solidfire comes out with a similar feature, your driver should also use the same key of course16:53
jgriffithavishay: agreed16:53
jgriffithSo this is something that's always been a tough one IMO16:53
jgriffithI've proposed that to avoid some of this we set definitions in OpenStack16:54
*** eharney has joined #openstack-meeting16:54
avishayjgriffith: OK, so just some method to keep track of used keys would help developers and reviewers I think16:54
jgriffithEven if they don't map 1:1 to every vendor, each vendor can/should adapt16:54
*** littleidea has quit IRC16:54
jgriffithavishay: Agreed!16:54
avishayOK all agree :)16:55
jgriffithavishay: That's a requirment IMO and I had assumed that was a big part of what this first pass on this is all about16:55
avishayDo we have time to discuss read-only snapshot attachments?16:55
jgriffithavishay: I do, so long as noboby else has anything??16:55
*** dolphm has quit IRC16:55
avishay*crickets chirping*16:56
DuncanTI just want to say that volume-backup is stuck in HP legal land but should be clear soon and code will appear shortly after the blueprint; before G2 certainly16:56
jgriffithavishay: So I outlined my suggestion but you didn't like it :)16:56
*** littleidea has joined #openstack-meeting16:56
avishayjgriffith: I don't think I understood it :)16:56
jgriffithDuncanT: G2, must have :)16:56
avishayDuncanT: any link for volume-backup?16:57
*** cdub has quit IRC16:57
jgriffithavishay: Yeah, I tend to confuse people :)16:57
jgriffithavishay: So my proposal was thus (warning, it's not what you want) :)16:57
*** AlanClark has joined #openstack-meeting16:57
*** cdub has joined #openstack-meeting16:58
avishayjgriffith: I think a big step forward would be to allow (at least) read-only snapshot attachments.  Not all drivers support it (e.g., storwize/svc), but you can pass a "readonly" flag in QEMU for example.16:58
jgriffith* Implement restore snapshot (uses a snapshot to put a volume back to the state it was in when snap was taken)16:58
DuncanTavishay: detailed blueprint stuck with legal16:58
avishayDuncanT: OK16:58
*** koolhead17 has joined #openstack-meeting16:58
jgriffith* Implement clone volume (Makes a clone of existing vol, ready for use, no extra steps)16:58
jgriffithavishay: In addition to those, the only thing missing IMO is the R/O capabilities of the snapshot16:59
jgriffithavishay: I think this would be interesting/useful....16:59
jgriffithavishay: But it's also a big change16:59
avishayAnd the difference between a clone and snapshot?16:59
jgriffithavishay: a clone is a ready to use independent volume16:59
avishayBasically the implementation shouldn't matter, as long as the behavior is as expected, right?17:00
jgriffithavishay: So I liken it to virtual-box snapshots/clones17:00
DuncanTI'd rather get restore & clone in before we start looking at R/O mounts17:00
jgriffithavishay: Oh, absolutely17:00
jgriffithDuncanT: +117:00
jgriffithavishay: So my point as always, nothing's forever and nothings set in stone17:00
*** mattray has joined #openstack-meeting17:00
DuncanTclone = create snapshot; create volume from snap; delete snap?17:00
jgriffithavishay: I wouldn't close the door on R/O snaps, but I'd save it for later17:00
DuncanT(or suitably optimised version there of)17:01
jgriffithDuncanT: partially... no need for a snap in there17:01
jdurgin1DuncanT: I think the model needs to be backend specific there, since different definitions of snapshots/clones exist17:01
jgriffithDuncanT: unless that makes it more efficient17:01
jgriffithjdurgin1: +117:01
jgriffithwhich goes back to I don't care how it's implemented, just what it means17:02
jdurgin1we already have an api for 'clone from snapshot'17:02
DuncanTYeah, I meant that the above would achieve the same results17:02
jgriffithDuncanT: Yes!!!  +117:02
DuncanTGot you. +1 the idea then17:02
jgriffithso in reality we've all kinda done these things already to expose our features etc17:02
avishayjgriffith: I think the API should be documented well so that it's clear what a "volume" is and what a "snapshot" is17:02
jgriffithavishay: Yes, that's something I MUST DO17:02
*** ndipanov has quit IRC17:02
jgriffithavishay: I would've already done it but I haven't felt we reached a concensus :)17:03
jgriffithavishay: So these are G2 items that I'm most interested in BTW17:03
*** cdub has quit IRC17:03
avishayjgriffith: OK, no problem17:03
jgriffitha lot of this also needs the API V2 changes from thingee that's why I'm so hot to get them in for G117:03
DuncanTCurrently I don't think you can say more than "A cinder snapshot is a point in time reference or copy of a volume; the only thing you can do with it is clone it to one or more new volumes"17:04
avishayIs there any way to get the name of a volume/snapshot on the backend, or only through the DB?17:04
jgriffithThere's a ton of cool stuff for API V2 :)17:04
*** cdub has joined #openstack-meeting17:04
jgriffithDuncanT: Yes, but I want to change that :)17:04
DuncanTjgriffith: There be dragons ;-) Should be entertaining17:04
jgriffithDuncanT: :)17:04
jgriffithavishay: so that's something I have tussled with17:05
jgriffithavishay: The problem there is I don't know what ALL back-ends will support/do17:05
jgriffithavishay: So default ends up being DB17:05
avishayDuncanT: jgriffith: Let's say for backing up volumes, if I could attach read-only I could run the backup software in a guest17:06
jgriffithavishay: Of course it could be in base class as DB call and if a device can do it better...17:06
jgriffiththen they override it17:06
jgriffithDuncanT: Sure... but are you talking R/O volumes or snapshots?17:06
avishayDuncanT: jgriffith: But if not, I need to figure out the volume name from the DB and back it up from outside of OpenStack?17:06
jgriffithDuncanT: Or both :)17:06
* jgriffith fully anticipates a R/O attach of volumes 17:07
avishaysnapshots.  volumes seem less critical for R/O17:07
*** dhellmann-afk is now known as dhellmann17:07
jgriffithavishay: Unless you think of DuncanT 's idea of running abackup app in an instance :)17:07
DuncanTavishay: We leave the attach up to the diver, same as for nova-compute17:07
jgriffithavishay: So here's my plan....17:08
jgriffithavishay: Go with what I described earlier as a start17:08
jgriffithavishay: Then we can grow that and look at R/O snaps etc17:08
avishayDuncanT: what do you mean "leave the attach up to the driver"?17:08
DuncanTjgriffith: We currently only cover volumes, snapshots is the next job17:08
avishayjgriffith: OK, no problem :)17:08
jgriffithavishay: I'd rather make forward progress on what we can agree on than get bogged down in a detail17:09
jgriffithDuncanT: perfect17:09
jgriffithOk... I think we're finally ok witht hat one :)17:09
jgriffithNext week...17:09
avishayOK, thanks for the clarifications!17:09
jgriffithWe need to settle on a method for multi-backends17:09
DuncanTavishay: Once the blueprint / sample code is up I suspect it will all become clear... can I punt your question for a week or so please?17:09
jgriffithSo everybody think about that a bit the next few days if you could17:10
avishayDuncanT: sure17:10
jgriffithI'd like to reach an agreeement next week and see if we can roll it for G217:10
*** littleidea has quit IRC17:10
DuncanTI still strongly favour one manager process, one backend17:10
jgriffithAnybody have anything else (we're 10 minutes over already)17:10
jgriffithDuncanT: noted :)17:10
*** cdub has quit IRC17:10
* jgriffith is beginning to agree17:11
jgriffithalright... for those in the states, Happy Thanksgiving!17:11
avishaygood night/day all!17:11
DuncanTYou can pass 2 different config files and run 2 (or more) on one node17:11
jgriffiththose elsewhere... happy Thanksgiving anyway :)17:11
*** cdub has joined #openstack-meeting17:11
*** avishay has quit IRC17:11
DuncanTCheers John17:11
jgriffithThanks everybody... keep an eye on reviews for G1 items today please :)17:11
jgriffithsee yaaaaa17:11
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"17:12
openstackMeeting ended Wed Nov 21 17:12:02 2012 UTC.  Information about MeetBot at . (v 0.1.4)17:12
openstackMinutes (text):
*** bswartz has left #openstack-meeting17:12
*** dtynan has left #openstack-meeting17:12
*** winston-d has left #openstack-meeting17:12
*** rushiagr has left #openstack-meeting17:12
*** eharney has left #openstack-meeting17:12
*** lloydde has joined #openstack-meeting17:14
*** j_king has left #openstack-meeting17:21
*** garyk has quit IRC17:22
*** adjohn has joined #openstack-meeting17:25
*** sarob has joined #openstack-meeting17:32
*** Mandell has joined #openstack-meeting17:38
*** arbrandes has joined #openstack-meeting17:40
*** juice_ has quit IRC17:43
*** ryanpetrello has quit IRC17:51
*** anniec has joined #openstack-meeting17:53
*** koolhead17 has quit IRC17:54
*** esp has joined #openstack-meeting17:55
*** radez has quit IRC17:56
*** radez has joined #openstack-meeting17:56
*** sarob has quit IRC17:56
*** garyk has joined #openstack-meeting17:56
*** andrewbogott is now known as andrewbogott_afk17:56
*** sarob has joined #openstack-meeting17:56
*** anniec_ has joined #openstack-meeting17:59
*** derekh has quit IRC18:01
*** anniec has quit IRC18:02
*** anniec_ is now known as anniec18:02
*** markwash has quit IRC18:02
*** mattray has quit IRC18:02
*** markwash has joined #openstack-meeting18:04
*** dwn` has joined #openstack-meeting18:05
*** juice_otg has joined #openstack-meeting18:05
*** nati_ueno has quit IRC18:05
*** dwn` has quit IRC18:06
*** dwn has quit IRC18:06
*** juice_otg has quit IRC18:08
*** juice_otg has joined #openstack-meeting18:08
*** juice_otg has quit IRC18:10
*** jog0 has joined #openstack-meeting18:10
*** juice_otg has joined #openstack-meeting18:11
*** spligak has quit IRC18:12
*** ijw1 has left #openstack-meeting18:13
*** darraghb has quit IRC18:14
*** esp has quit IRC18:17
*** jdbarry has joined #openstack-meeting18:18
*** esp has joined #openstack-meeting18:18
*** davidkranz_ is now known as davidkranz18:18
*** zoumpis has quit IRC18:20
*** garyk has quit IRC18:20
*** annegentle_ has joined #openstack-meeting18:21
*** ryanpetrello has joined #openstack-meeting18:22
*** garyk has joined #openstack-meeting18:22
*** esp has quit IRC18:27
*** esp has joined #openstack-meeting18:29
*** annegentle_ has quit IRC18:29
*** nati_ueno has joined #openstack-meeting18:32
*** afazekas has quit IRC18:35
*** EmilienM has left #openstack-meeting18:39
*** juice_otg has quit IRC18:40
*** dkehn is now known as dkehn_brb18:42
*** juice_otg has joined #openstack-meeting18:42
*** ehm has left #openstack-meeting18:44
*** andrewbogott_afk is now known as andrewbogott18:45
*** dolphm has joined #openstack-meeting18:47
*** zul has quit IRC18:49
*** juice_ has joined #openstack-meeting18:50
*** ywu has quit IRC18:50
*** ywu has joined #openstack-meeting18:52
*** zul has joined #openstack-meeting18:55
*** colinmcnamara has joined #openstack-meeting18:55
*** juice_otg has quit IRC18:56
*** sarob has quit IRC19:01
*** samkottler is now known as samkottler|afk19:02
*** mattray has joined #openstack-meeting19:04
*** juice_ has quit IRC19:10
*** sarob has joined #openstack-meeting19:12
*** andrewbogott is now known as andrewbogott_afk19:15
*** jog0_ has joined #openstack-meeting19:15
*** jog0_ has quit IRC19:16
*** jog0_ has joined #openstack-meeting19:16
*** dolphm has quit IRC19:18
*** jog0 has quit IRC19:19
*** fnaval has quit IRC19:19
*** dkehn_brb is now known as dkehn19:20
*** jog0 has joined #openstack-meeting19:22
*** frankm_ has quit IRC19:28
*** stevebake has quit IRC19:35
*** fnaval has joined #openstack-meeting19:36
*** stevebake has joined #openstack-meeting19:37
*** jog0 has quit IRC19:37
*** jog0 has joined #openstack-meeting19:37
*** lcheng has joined #openstack-meeting19:40
*** lcheng has joined #openstack-meeting19:40
*** lcheng has joined #openstack-meeting19:40
*** shardy has joined #openstack-meeting19:46
*** rnirmal has quit IRC19:46
*** afazekas has joined #openstack-meeting19:49
*** jcooley_afk is now known as jcooley19:49
*** NobodyCam is now known as NobodyCam_brb19:54
*** kmartin has joined #openstack-meeting19:54
*** zaneb has joined #openstack-meeting19:59
stevebake#startmeeting heat20:01
openstackMeeting started Wed Nov 21 20:01:17 2012 UTC.  The chair is stevebake. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
openstackThe meeting name has been set to 'heat'20:01
asalkeldwell done stevebake20:01
asalkelddo we have some agenda?20:01
shardyOne item is, do we want to start posting an agenda before the meeting ;)20:02
asalkeldwe probably should20:02
asalkeldasalkeld, here20:02
*** jrd has quit IRC20:03
jpeelerjpeeler here. unsure if this is agenda worthy, but need input on caching feature work20:03
asalkeld#action shardy post agenda before meeting20:03
shardysure ;)20:03
zanebjpeeler: that is deinitely agenda-worthy IMO20:03
shardyI saw most other projects post something with a link to etherpad to openstack-dev20:03
stevebakeor a wiki page20:04
zanebalso, there was a discussion about native resource types that could go on the agenda20:04
shardystevebake: Yeah, either20:04
*** maurosr has quit IRC20:04
asalkeld#agenda image caching, native resource types20:04
asalkeldanything else come to mind?20:04
radezupdate on the webui20:04
shardyI'd like to discuss getting better visibility of functional tests20:05
stevebakerelease date20:05
shardyie the automated ones20:05
*** jhenner has quit IRC20:05
asalkeld#agenda image caching, native resource types, release date, webui, better visibility of functional tests20:05
zanebanything we agreed to in the project meeting20:05
zaneb(OpenStack project meeting)20:05
asalkeld#agenda image caching, native resource types, release date, webui, better visibility of functional tests, update on project meeting20:06
*** anniec has quit IRC20:06
asalkeldlets roll20:06
asalkeld#agenda  image caching20:06
zanebfwiw there is no #agenda command. and stevebake is the chair ;)20:06
asalkeld#topic  image caching20:06
stevebake#agenda image caching, native resource types, release date, webui, better visibility of functional tests, update on project meeting20:06
asalkeldfair enough20:06
jpeelerfirst off we actually have more wiki pages than i knew about20:06
stevebake#topic  image caching20:06
*** openstack changes topic to "image caching"20:06
Sl0wsorry Slow here too20:07
jpeelerthey don't really agree :/20:07
zanebstevebake: just add asalkeld as a chair20:07
zanebI think #chair asalkeld20:07
asalkeldjpeeler, should  be the master20:07
shardyjpeeler: prebuilding is just about baking a stack definition into a jeos isn't it?20:07
asalkelddelete the github page20:07
shardyOr an instace from a stack definition20:07
asalkeldshardy, can run it20:08
stevebake#chair stevebake asalkeld zaneb20:08
openstackCurrent chairs: asalkeld stevebake zaneb20:08
jpeeleroriginally i was thinking of it being a more of a hands off thing20:08
*** vipul is now known as vipul|away20:08
*** vipul|away is now known as vipul20:08
jpeelerbut that's probably way harder, so if we want to do the latter that's fine20:09
asalkeldso jpeeler have you prototyped so options?20:10
asalkeldso jpeeler have you prototyped some options?20:10
asalkeldwhat do you feel is the most practical option20:10
jpeelerpractical to the user?20:11
asalkeldto implement20:11
shardyI thought tomas got a basic heat-prebuild already working, but it's much more limited/manual/simple than what you're proposing with snapshots20:12
jpeelerheh, the second one is no doubt easier20:12
asalkeldwell another option could be a shardy type image building service20:13
jpeeleri have not prototyped beyond checking image copying to make sure the timing is feasible20:13
zanebthere is a third option perhaps20:13
asalkeldthat takes launch configes20:13
zanebhave the user explicitly create a snapshot (with a template) and allow them to instantiate copies of it using a new resource type20:13
asalkeldor it could be a manual cfn-snapshot call from in the userdata20:14
asalkeldand save some state "already-snapshotted" so it doesn't keep doing it20:15
asalkeldwell we should move on if thomas isn't here20:16
*** redthrux_is_miss has joined #openstack-meeting20:16
asalkeldmaybe discuss on ml20:16
shardywhat's driving the use-case btw?20:16
shardyother than fast==good?20:16
*** redthrux_is_miss is now known as Guest3062720:16
asalkeldwell steve was driving it20:16
jpeelerpretty sure that's it?20:16
*** Guest30627 has quit IRC20:16
zanebshardy: what more do you want? ;)20:16
jpeelermake demos look super awesome20:16
asalkeldmostly after trying the openshift template20:17
asalkeldwhich is super slow20:17
shardyThe problem with openshift was building everything from source20:17
shardyCheck out my screecast, it launches openshift in 30s20:17
*** derekh has joined #openstack-meeting20:17
asalkeldlets move on20:18
shardyIf their install-from RPM stuff was better documented, we could do that from a template (or via heat-prebuild or heat-jeos)20:18
*** derekh has quit IRC20:18
asalkeld#topic native resource types20:18
*** openstack changes topic to "native resource types"20:18
asalkeldzaneb, ?20:19
zanebshardy: ? ;)20:19
zanebso, the question was20:19
stevebakeSo, quantum resource type implementation are small and clean, since they are just thin wrappers around api20:19
*** redthrux has quit IRC20:19
zanebwhether we should introduce stuff like OpenStack::Nova::Instance20:19
zaneband if so should it be an extension of AWS::EC2::Instance20:20
stevebakeI'd like to at least try a nova instance resource type doing the same thing20:20
zanebor should it be something completely new and more OpenStack-y20:20
asalkeldwell if there is new value sure20:20
stevebakezaneb: right now I'm thinking separate implementations, with shared code refactored somewhere else20:20
zanebthis was in the context of jpeeler wanted to do something that was best implemented by adding some properties to the Instance type20:20
shardyI think we should keep non AWS resource stuff separate, in a separate OS:: namespace or something20:21
asalkeldthere is also min_count and max_count that would be neat20:21
asalkeld(for multiple creates)20:21
stevebakeIf the resource_ids match then we could mix and match resources in a template, but probably not recommended20:22
asalkeldI think in a seperate resource20:22
asalkeldnot reason not to work together20:22
stevebakeif the schema properties exactly match the underlying api that will ease the documentation burden20:22
asalkeldalso would be good to get the new format sometime20:22
stevebakeI might start playing with new format next20:23
asalkeldcool stevebake20:23
*** vipul is now known as vipul|away20:23
zanebso, that approach has merits: it means we're not stuck with the AWS schemas forever20:24
*** jhenner has joined #openstack-meeting20:24
stevebakefile extension bikeshedding, *.hml (Heat Markup Language) *.homl (Heat's Own Markup Language) ?20:24
zanebthe embrace-and-extend option also has merits though: it's a much easier transition path for users20:24
asalkeldwhy not just the actual type20:24
*** jhenner has quit IRC20:24
shardy+1, why not just use the extension (.yml?) which best describes the format?20:25
zanebmime type should be application/json, so I vote for .json (or .yml)20:25
zanebthat way web servers can infer the mime type20:25
shardyCan't be json, cos it's not, erm, json?20:26
zanebshardy: ?20:27
asalkeldzaneb, where the implementation starts diverging you will have to start a new resource20:27
shardyzaneb: You said "so I vote for .json"20:27
shardy+1 re .yaml20:27
zanebshardy: yeah, that's before I remembered we were moving to YAML20:27
stevebakeback to native types, we could write tools which transform cfn <-> native types in templates20:28
shardyWell, still be json for CFN API20:28
asalkeldstevebake, yea could be done in the api server20:28
zanebright, either is fine for templates that are actually in the JSON subset of YAML20:28
asalkeldwe better speed up 30min down20:29
stevebake#topic release date20:29
*** openstack changes topic to "release date"20:29
asalkeldok anyone got a link to the next release date?20:30
stevebakeOur next release could be a late grizzly-1 release, or a non-aligned one, or wait until grizzly-220:30
asalkeldI recon20:31
asalkeldwe could vote20:31
asalkeldwhat are the dates?20:31
zanebstevebake: what are the dates for those?20:31
zanebin 3 hours!20:32
asalkeldlets shoot for g2 :)20:32
zanebI think it makes sense to wait for the API stuff I am working on, and the cloudwatch stuff shardy is working on20:32
zanebI don't think that precludes us from doing a late g1 though20:33
stevebakethen do an interim December release?20:33
zanebThierry said that was ok20:33
asalkeldnot sure there is a point tho'20:33
asalkeldtakes up time20:33
*** NobodyCam_brb is now known as NobodyCam20:33
asalkeldand holidays20:33
*** novas0x2a|laptop has quit IRC20:34
stevebakewaiting for g-2 could make it a painful release20:34
*** jcooley is now known as jcooley_afk20:34
zanebwe do have to sort out the version numbering stuff before doing any more releases though20:34
shardystevebake: any particular reason why?20:34
asalkeldI think so zaneb20:34
stevebakeshardy: g-2 is a hard date, doing a release before could shake out issues which take a long time to fix, like functional tests20:35
asalkeldwell we could start in say 2 weeks to do bug fixing/testing20:35
zanebI'm ok with holding off until g220:35
shardyWell, we have the functional tests already, it's just none of us are looking at the results or running them ;)20:35
stevebakeok, lets tell the Project Meeting our next release is g-220:36
*** dprince has joined #openstack-meeting20:36
asalkeldhow long does a run take?20:36
zanebis there any way we can contribute those tests to tempest?20:36
zanebasalkeld: forever20:36
zanebgive or take20:36
shardyI think we really really need a way to get better visibility of the status20:37
asalkeldmaybe we could take turns running overnight20:37
zanebasalkeld: depends if they all pass20:37
zanebif they do, it's not too bad20:37
shardywe put so much effort into writing them and not really benefiting atm20:37
zanebfailures can take a couple of hours to detect20:37
stevebake#agreed Next release of Heat is January 10th, 201320:37
asalkeldcan you run them the tests separately?20:38
asalkeldso one test?20:38
asalkeldjust thinking if we each run one20:38
shardyasalkeld: yes, just nosetest -s20:38
asalkeldit will share the burden20:38
stevebake#topic better visibility of functional tests20:38
*** openstack changes topic to "better visibility of functional tests"20:38
shardyasalkeld: zaneb set up a fully automated test environment, why run them manually?!20:39
stevebakewho/when/what runs tempest currently?20:39
shardywe just need better visibility of the results20:39
asalkeldok, well lets do that then20:39
zanebthe test environment is broke at the moment20:39
asalkeldwe can't just post them somewhere and have a link from
stevebakeEmail and bot notifications would be nice. And a pony20:40
asalkeldzaneb, major pita maintaining function tests20:41
zanebbut we can't continue to have this stuff behind a firewall. we need to move it into tempest20:41
zanebyep, sure is20:41
asalkeldthat's why I suggested we all just run one20:42
zanebbiggest problem with that imo is that the heat-jeos image we need is unstable20:42
stevebakeQuantum recently did something with their devstack gating, maybe that is worth looking into20:42
asalkeldI see, that's not good20:42
zanebnot unstable as in bad, unstable as in the cfn-tools are changing all the time20:42
asalkeldwell we need to fix this somehow20:42
shardyzaneb: Latest jeos should always work with latest master tho, which I presume is what the automated tests use?20:43
zanebso we can't just build an image once for tempest and always test against that20:43
zanebshardy: automated tests do, but that's a PITA for tempest20:43
asalkeldzaneb,  fix is cfn tools reinstall themselves20:43
zanebsince it runs on VMs20:43
shardythe cfntools churn should stop soon anyway, but then we'll probably want some ostools variant, so more churn20:43
shardyasalkeld: We should package the cfntools as an RPM20:44
zanebI like the idea of installing the tools at launch time20:44
asalkeldjust do a github install20:44
asalkeldso once that is in, no problem20:44
zanebWhat Would Amazon Do?20:44
asalkeldrpm update <cfn>20:45
shardyzaneb: they install cfn-bootstrap RPM from their repo20:45
zaneblet's do that20:45
asalkeldstill need to run the pesky test tho'20:46
asalkeld13min left20:46
stevebake#topic webui20:46
*** openstack changes topic to "webui"20:46
radezThe conversion to python-heatclient is essentially done.20:46
radezI've just been waiting for the events command to be exposed before I screencast the latest.20:46
radezI have some ui functionality that displays events that will be pretty easy to convert, and that's all that's pending.20:46
radezIn the mean time I've been working on a couple concepts for new features.20:46
radez1. template catalogues (pulling already written templates from multiple sources, github and aws atm)20:46
radez2. eye candy enabled template designer (drag and drop and forms that render to a template)20:46
radezboth are coming along very well and are just about ready to do an inital screencast of them to show where they are in concept/development20:46
radezother thoughts on my plate20:47
radez1. moving onto LP (can I just do it, or is there a plan of some kind I need to follow?)20:47
radez2. I'm in my first week of trianing to get my RHCA next week (ie, absent from meeting)20:47
radez3. blueprints, kinda need more of a plan on where to go with this. I think this depends on #1 but up for feed back on what folks want to see.20:47
radezthoughts? questions?20:47
stevebakeradez: do you want coding help or users yet?20:47
zanebradez: I'm writing unit tests for events now. as soon as they are done (I expect tomorrow) I will post the patches.20:47
radezstevebake: users would be great20:47
asalkeldradez, just move to lp20:48
radezcoding help, I think i'm starting to have enough to use the help20:48
radezzaneb: asalkeld: cool thx20:48
stevebakemaybe devstack integration would be a good first step20:48
asalkeldgood idea20:48
radezstevebake: good though, I'll put that on my list20:49
asalkeldradez, awesome work btw20:49
radezthx, I look fwd to sharing another screencast20:49
asalkeldwhat about nati_ueno?20:49
radezhe's been consumed by quantum20:50
asalkeldI see20:50
radezso he hasn,t been able to code any20:50
zanebsounds painful20:50
asalkelddid you look at his code?20:50
radezbut he had some good work done that went into the template designer20:50
nati_uenoyeah, But I got one UX guy, so I may help something. may be20:50
radezso I think we'll benefit from his contribution20:50
asalkeldwell at least make a blueprint and share ideas20:51
nati_uenosorry I can't promise yet. but may be I can work :)20:51
radeznati_ueno: take a look at what I've started when you get a chance20:51
nati_uenoradez: gotcha20:51
radezI went with jsPlumb for now20:51
radezbut made good progress20:51
radezthat's it for me20:52
asalkeldnext topic?20:52
stevebake#topic update on project meeting20:52
*** openstack changes topic to "update on project meeting"20:52
asalkeldthat's it20:52
asalkeldso we are moving to openstack/20:53
asalkeldon the 2 dec20:53
stevebakeshould we move thermal too?20:53
asalkeldgood point, not sure20:53
asalkeldI have made the team  changes20:54
*** EmilienM has joined #openstack-meeting20:54
*** andrewbogott_afk is now known as andrewbogott20:54
stevebakemaybe we should just get those in first20:54
asalkeldthat the ci / project folks wanted20:54
asalkeldstevebake, those?20:54
stevebakeheat and python-heatclient only20:54
*** EmilienM has left #openstack-meeting20:54
asalkeldo, yea sure20:55
zanebif & when we were accepted into core, I would expect thermal to be maintained in the horizon tree. but not sure how that should work during incubation?20:55
asalkeldmight only do that once in core?20:55
radezI kinda expect to be consumed by horizon, but I don't know for sure20:55
asalkeldyea, github not a bad place for now20:56
stevebakeare there any outstanding launchpad process changes?20:56
asalkeldall good to go20:56
asalkeldnote all issues and wiki pages will probably go20:56
asalkeldso cleanup you pages20:56
stevebakeasalkeld: thanks for all that migrating, its a shitty job20:56
asalkeldwiki was the most tedious20:57
asalkeldno problem20:57
*** yjiang5 has joined #openstack-meeting20:57
*** dendrobates has quit IRC20:57
zanebstevebake: did anything come up in yesterday's meeting? I wasn't there this week20:57
asalkeldthe team stuff20:57
asalkeldI was there too20:57
stevebakenot really. we have a release date for them now20:57
asalkeldthat's right20:58
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"20:58
openstackMeeting ended Wed Nov 21 20:58:29 2012 UTC.  Information about MeetBot at . (v 0.1.4)20:58
openstackMinutes (text):
stevebakeooo, logs!20:58
asalkeldbeen a while20:58
asalkeldthanks all20:59
*** adjohn has quit IRC20:59
radezcya'll in two weeks20:59
*** radez is now known as radez_g0n320:59
*** zoumpis has joined #openstack-meeting20:59
nijaba#startmeeting Ceilometer21:00
nijaba#meetingtopic Ceilometer21:00
nijaba#chair nijaba21:00
nijabaATTENTION: lease keep discussion focussed on topic until we reach open discussion topic21:00
openstackMeeting started Wed Nov 21 21:00:01 2012 UTC.  The chair is nijaba. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
openstackThe meeting name has been set to 'ceilometer'21:00
*** openstack changes topic to " (Meeting topic: Ceilometer)"21:00
openstackCurrent chairs: nijaba21:00
*** torgomatic has left #openstack-meeting21:00
nijaba#topic actions from previous meeting21:00
*** openstack changes topic to "actions from previous meeting (Meeting topic: Ceilometer)"21:00
nijaba#topic jd and nijaba to start preparing a video demo of ceilometer21:01
*** openstack changes topic to "jd and nijaba to start preparing a video demo of ceilometer (Meeting topic: Ceilometer)"21:01
nijabano real progress there this week.  We clearly do not have much time to work on this at the moment.  I guess we'll have to postpone this a bit...21:01
nijabaunless anyone else wants to work on it21:01
nijabano volunteer?21:01
nijabaok moving on...21:01
nijaba#topic eglynn propose agent item on ceilo interaction for nova IRC meeting21:01
*** openstack changes topic to "eglynn propose agent item on ceilo interaction for nova IRC meeting (Meeting topic: Ceilometer)"21:01
eglynnso I proposed it to them, but they didn't bite21:02
eglynnsorry wrong topic!21:02
*** jcru has quit IRC21:02
*** adjohn has joined #openstack-meeting21:02
eglynnwe discussed the cilo/nova interaction at the nova weekly meeting21:02
eglynnand option 5 (a versioned stable lib wrapping th enova virt bit we need) was the preference of the nova folks21:03
eglynnprovisionally at least, pending the details being fleshed out21:03
nijabawho would own the lib? Ceilo?21:03
eglynnnova primarily21:04
eglynnwith ceilo contributions to it21:04
nijabaand who has the action to flesh out the details?21:04
eglynnso I've been trying to smoke out the versioning and releas emgmt implications21:04
eglynnI still have the action to flesh out21:04
*** cdub has quit IRC21:04
eglynn... and yjiang5 has some ideas also21:05
nijabashould you guys action yourselves on that?21:05
*** cdub has joined #openstack-meeting21:05
yjiang5yes, I did some investigate on the API21:05
asalkeldhi, bit late ...21:05
eglynn#action eglynn drive fleshing out of nova-virt API to completion21:05
nijabathanks eglynn21:05
asalkeldooo, eglynn is driving21:06
nijaba#topic nijaba to close survey and publish result prior to next meeting21:06
*** openstack changes topic to "nijaba to close survey and publish result prior to next meeting (Meeting topic: Ceilometer)"21:06
nijabaI did this via an email to the mailing list:21:06
nijabaWe'll have time to discuss this in a bit21:06
nijaba#topic asalkeld investigate diamond for use to generate stats21:06
*** openstack changes topic to "asalkeld investigate diamond for use to generate stats (Meeting topic: Ceilometer)"21:06
asalkeldso I had a look21:06
asalkeldbut not really good fit for ceilometer21:07
asalkeldbut good fit for diagnostic21:07
asalkeldor tracing21:07
asalkeldit's kinda like tach21:07
dhellmannany ideas we can steal for the multi-publishing changes?21:07
asalkeldwell it doen't have a concept of different rates21:07
asalkeldwhich would be neat21:08
nijabait would :)21:08
dhellmannwait, it does21:08
asalkeldso not really21:08
*** vipul|away is now known as vipul21:08
dhellmannI had a system set up here polling ceph at one rate and everything else at another rate21:08
dhellmannyeah, you can control that in the config file21:08
dhellmannI'll have to dig up the settings again, I deleted that vm21:09
asalkeldo, I meant more caching, aggregation21:09
dhellmannit controlls the polling rate, which is then the same as the publishing rate for those meters21:09
dhellmannoh, yeah, I think it assumes upstream does that21:09
nijabaI think what we want to find is the best way to minimize polling and intreations, rig21:10
asalkeldwe might want to sample often but publish less often21:10
*** dprince has quit IRC21:10
eglynnyep, say for CPU util21:10
jd__that's a point for transformer21:10
asalkeld(for monitoring)21:10
yjiang5that can be achieved through transfomer21:10
* jd__ high five yjiang5 21:10
eglynnthe transformer drops some samples on the floor, or?21:11
eglynn(to dial down the publishing rate)21:11
jd__eglynn: or use them to build a % value21:11
eglynn(or aggregates)21:11
jd__dropping shouldn't be a transformer feature itself21:11
eglynna-ha, OK21:11
eglynnthought yjiang5 menat using a transformer to step down the sample rate for fewer publishes ...21:12
yjiang5possibly we can have transfomer pipeline? some drop, some aggeragete ? possibly21:12
nijabaok, so should we have a topic on transformer design next week?21:12
eglynnyep, long thread in gerrit21:12
jd__not sure a meeting topic will fit21:13
nijabamaybe yjiang5 can prep soemthing?21:13
dhellmannyeah, we need something written up to talk about21:13
eglynn(gerrit highly unsuited to long discussions ...)21:13
yjiang5I would discuss on the ML firstly21:13
jd__the subject is so complex, async communication will work better as a first step21:13
nijaba#action yjiang5 to drive a topic on transformer next week meeting21:13
nijabatrike t21:14
nijabaastrike that then21:14
jd__#unaction !21:14
nijaba#rewind too21:14
nijaba#action yjiang5 to start a thread on transformer21:14
*** jdbarry is now known as jdbarry|away21:14
nijaba#topic eglynn propose IRC meetup with Synaps folks to discuss collaboration model21:15
* nijaba guess they did not bite :)21:15
*** openstack changes topic to "eglynn propose IRC meetup with Synaps folks to discuss collaboration model (Meeting topic: Ceilometer)"21:15
eglynnso I proposed it to them, but they didn't bite21:15
eglynnhowever they assure me they're continueing to discuss internally21:15
eglynnand will have a conclusion by week's end21:15
eglynn(apparently busy with a bunch of other stuff ...)21:15
jd__re-#action then?21:16
nijabaso, let's wait for their decision21:16
dhellmannso they didn't say no, but haven't said yes?21:16
nijaba#action eglynn to report on synaps' decision21:16
eglynnwill be wrapped up one way or the other this week21:16
nijaba#topic dhellmann to confirm with ttx that tarball job is correct21:16
*** openstack changes topic to "dhellmann to confirm with ttx that tarball job is correct (Meeting topic: Ceilometer)"21:16
dhellmannit was not, but has been fixed so it is now21:17
jd__\o/ thx21:17
nijabacool! thanks dhellmann21:17
nijaba#topic nijaba to transform bp-less features into bp21:17
nijabaSo I spent quite a bit of time on this, you can see the results at21:17
nijabaI also updated the roadmap page, but I think this is now truely redudant info and we should get rid of it, wdyt?21:17
*** openstack changes topic to "nijaba to transform bp-less features into bp (Meeting topic: Ceilometer)"21:17
*** sarob has quit IRC21:17
dhellmannthe infra team also added a gating job to ensure all of our contributors have signed the CLA21:17
eglynnyep, get rid, duplication is badness for this sort of stuff21:17
jd__nijaba: I hate duplicate21:17
* nijaba too21:17
dhellmannnijaba: maybe just erase the contents and point to launchpad? saves history...21:18
jd__let's kill the grizzly then!21:18
nijaba#action nijaba to get rid of roadmap page content to point to lp21:18
jd__otherwise good work nijaba :)21:18
eglynnyep, much neater!21:18
nijabaI guess that's it for last week's actions21:18
nijaba#topic Folsom stable update release?21:19
*** openstack changes topic to "Folsom stable update release? (Meeting topic: Ceilometer)"21:19
nijabaSo far, it seems that we have made some good progress that should not break the compatibility with Folsom and some of the bug fixes are somehow critical for production environments. What would you guys think if we were producing a Folsom stable update at the same time of the g2 milestone?21:19
dhellmannwe might even be able to say that g2 is compatible with folsom21:19
nijabathis may mean that we should wait until we commit breaking changes after that milestone, though21:19
eglynninteresting, do we have a stable/folsom branch?21:19
dhellmannjd__ has a patch under way to update the CI system to test changes against folsom21:20
jd__I agree with dhellmann on that21:20
nijabaeglynn: we don't but can have one21:20
dhellmannnijaba: yes, we do have a stable/folsom branch21:20
jd__stable/folsom should be a 2012.2.1 release with fix only, but I don't think this is what we want21:20
eglynncouldn't we create one, backport selected fixes to that and keep master trucking ahead?21:20
dhellmannwe made a branch right before ODS21:20
nijabadhellmann: ah... the 0.1 branch?21:20
dhellmannyeah, I thought we called it stable/folsom21:20
* dhellmann goes to git21:20
jd__selecting fix is going to be big grunt work :(21:20
asalkeldcp ceilometer-2012.g2 ceilometer-folsom21:21
jd__asalkeld: that would break the rule I think21:21
*** arbrandes has quit IRC21:21
dhellmannthe main issue with compatibility has been nova21:21
eglynnso the stable-maint criteria for backport selection are ... user-visible fix, low impact, low risk21:22
jd__it's saner to keep Folsom compatibility until g221:22
dhellmannso far we're compatible, so we could just merge master into the stable branch21:22
*** roadTripper has quit IRC21:22
jd__dhellmann: I don't think it's policy compliant /o\21:22
nijabaso, anyone against this?  It should be simple IIUC and don't break compat until g321:22
dhellmannoh, we have to pick individual patches?21:22
jd__dhellmann: oh yes we have to.21:22
eglynnso users expect stable releases to be minimal and contain carefully selected fixes21:23
jd__stable/folsom is meant to fix bugs like eglynn said21:23
nijabajd__: does this apply to inbation?21:23
dhellmannah, ok, that makes sense21:23
eglynnnot trunk chasing21:23
dhellmannwell, we could just say our g2 release is also compatible and not touch stable/folsom then21:23
jd__nijaba: the point of incubation is to act like others players, right? ;)21:23
nijabaincubation even?21:23
jd__dhellmann: I think it's the best option here21:23
nijabajd__: hmmmpfff...21:23
jd__I've already updated tox.ini to run unit tests against folsom and the -infra team is about to merge my change forcing gate checks againt Folsom21:24
jd__just say yes to this and it'll happen! ;)21:24
nijaba#agreed g2 should be declared folsom compatible21:24
dhellmannone other thing I have found is that our version of anyjson is not compatible with folsom, so I had to make a change for our internal packaging21:24
dhellmannit conflicts with the version folsom nova wants, IIRC21:24
jd__dhellmann: feel free to send a patch then :)21:24
eglynnyeah anyjson dependency caused issues before21:24
dhellmannunfortunately, changing it will break grizzly compatibility21:24
eglynn(nova, quantum etc. have a much older dep IIRC)21:25
jd__dhellmann: we can create a second pip-requires?21:25
dhellmannso we may actually need a branch at g2 for compatibility with just that change21:25
jd__let's update nova and quantum? ;)21:25
dhellmannthey're updated in grizzly already, I think21:25
eglynnyep they are21:25
jd__ah, ok21:25
dhellmannso grizzly is consistent, but newer than folsom21:25
dhellmannmaybe we need an unstable/folsom branch ;-()21:26
jd__dhellmann: what's the problem with supporting several anyjson on our side?21:26
dhellmannhmm, that might work21:27
dhellmann#action dhellmann test more lenient anyjson support for folsom and grizzly compatibility21:27
jd__dhellmann: if you need some help about that, ping me21:28
*** AlanClark has quit IRC21:28
jd__not sure you'll need, but I care about Folsom too21:28
nijaba#link as a reminder21:28
nijabag2 is jan 1021:28
dhellmannjd__: thanks, I'll let you know!21:28
nijaba#topic Discuss results of Poll21:29
*** openstack changes topic to "Discuss results of Poll (Meeting topic: Ceilometer)"21:29
nijabaso, did you have time to look at the results21:29
nijabaany action we need to take?21:29
jd__I look at the result, and I don't have any comment21:30
dhellmannthe first few high priority items were interesting21:30
jd__I think you set this in the blueprints priorities?21:30
dhellmannI promise I didn't stuff extra ballots!21:30
nijabaI set the priorities according to our internal vote, not the poll so far21:30
jd__nijaba: ok, not sure there's a big difference?21:31
dhellmanndoes anything in the results change our priorities? I think those internal changes would be great, but I agree with their current priority.21:31
asalkeld * I want to have monitoring information in a central place21:31
shardy+1 ;)21:32
*** juice_ has joined #openstack-meeting21:32
nijabaI think the horizon plugin suggestion showed that we forgot to input items that were already on the roadmap on which we did not vote21:32
dhellmannnijaba: good point21:33
nijabaso I added
dhellmannjd__: how's that prototype you were working on coming along?21:33
zykes-are you guys in on horizon integration atm ?21:33
nijabashould we set some medium prio on those?21:33
jd__dhellmann: prototype? on horizon? not me21:33
nijabazykes-: what do you mean?21:34
dhellmannjd__: you had some graphs, I thought that's what they were for21:34
nijabadhellmann: debug graphs, not plugin stuff yet21:34
jd__dhellmann: ah, nop, it's just a debug interface sending you html rather json when talking to ceilometer-api21:34
jd__s/rather/rather than/21:34
dhellmannjd__: ah21:34
nijabaand the horizxon plugin needs a user api first, I think21:34
jd__nijaba: yeah, probably21:35
nijabasecurity wise, I think it is a must21:35
jd__we could extend the API to user-API pretty easily now that we have Keystone21:35
zykes-nijaba: i'll save it for open-disc21:35
eglynna user API, as opposed to the existing REST API?21:35
nijabaok, so, set taht for medium prio?21:35
dhellmanneglynn: so a user can't see resource usage for someone else's stuff21:35
nijabaeglynn: yes, same api, but contrained to current tenant21:36
eglynna-ha OK, a non-admin-see-the-world API, got it21:36
dhellmannmy idea for that was just to update the api implementation to always add the tenant_id parameter to a query unless the user has admin21:36
dhellmannso the user api is the same as the admin api21:36
nijabadhellmann: on a differrent port or baed on admin status?21:36
dhellmannbased on the credentials we get from the keystone middleware21:36
nijabadhellmann: ok21:36
dhellmannI assume those are tucked into the request in a way that we can get to them21:37
jd__dhellmann: you mean only allow URI with <tenant id> in it?21:37
nijabadhellmann: feel free to fill in some details in
dhellmannjd__: no, allow any url, but internally always restrict by the current tenant_id even if the URL doesn't do that21:37
dhellmann#action dhellmann update user-api blueprint21:37
nijabadhellmann: thanks!21:37
jd__dhellmann: ah yes, good idea21:37
eglynnexactly, as nova does for non-admin queries21:38
yjiang5We are rebuilding the API server, will user-api depends on that/21:38
nijabaIntegrate with monitoring standards such as SNMP, CIM and SMI-S seems to big for this release, right?21:38
eglynnI would say so21:38
dhellmannnijaba: yes, way too big21:38
nijabawhat about ?21:38
*** juice_ has quit IRC21:38
jd__I didn't understand 2 of 3 of your stuff, so yes.21:38
dhellmannnijaba: that should be a small change to the api21:39
asalkeldsay this seems alot like a cw api21:39
* nijaba likes the jd__ test, similar to litmus, 21:39
nijababut better21:39
eglynnhow to auth?21:40
jd__asalkeld: probably21:40
eglynnadmin only?21:40
asalkeldpost + user stuff21:40
jd__eglynn: at least admin only as a first step would be great21:40
*** dendrobates has joined #openstack-meeting21:40
*** dendrobates has quit IRC21:40
*** dendrobates has joined #openstack-meeting21:40
eglynnjd__: cool21:40
jd__admin or special role21:40
asalkeldI am working on monitoring api21:40
eglynnasalkeld: native version of CW API?21:41
jd__as stated on the mailing list, this is something PaaS platforms are requesting21:41
asalkeldat some point we could work towards one api if it made sense21:41
asalkeldeglynn, ya21:41
*** sandywalsh_ has joined #openstack-meeting21:41
*** sandywalsh has quit IRC21:42
asalkeldthis a nice api too
nijabaso, should I mark this as approved/medium, low?21:42
*** AlanClark has joined #openstack-meeting21:42
*** yjiang5 has quit IRC21:42
nijaba#vote on prio for post meter? high, medium, low21:43
nijaba#startvote on prio for post meter? high, medium, low21:43
openstackBegin voting on: on prio for post meter? Valid vote options are high, medium, low.21:43
*** juice_ has joined #openstack-meeting21:43
openstackVote using '#vote OPTION'. Only your last vote counts.21:43
dhellmann#vote low21:43
eglynnasalkeld: measure_time resolution seems a little coarse21:43
nijaba#vote low21:43
asalkeld#vote low21:43
eglynn#vote low21:43
jd__#vote medium21:43
*** yjiang5 has joined #openstack-meeting21:44
nijabaanyone else?21:44
nijabaok, done21:44
openstackVoted on "on prio for post meter?" Results are21:44
openstackmedium (1): jd__21:44
openstacklow (4): nijaba, dhellmann, eglynn, asalkeld21:44
asalkeldeglynn, sure - I just meant the rest api21:44
eglynnasalkeld: but otherwise looks nice on a first read ...21:44
nijaba#startvote on prio for horizon and user api? high, medium, low21:44
openstackBegin voting on: on prio for horizon and user api? Valid vote options are high, medium, low.21:44
openstackVote using '#vote OPTION'. Only your last vote counts.21:44
nijaba#vote medium21:44
asalkeld#vote low21:44
jd__#vote medium21:45
yjiang5#vote medium21:45
jd__syntax error21:45
asalkeldI will be off for 10-15min (kids to school)21:45
eglynn#vote low21:45
dhellmann#vote low21:45
dhellmann(thanks, jd__)21:46
nijabacountdown to 10...21:46
openstackVoted on "on prio for horizon and user api?" Results are21:46
openstackmedium (3): jd__, nijaba, yjiang521:46
jd__then fireworks?21:46
openstacklow (3): dhellmann, eglynn, asalkeld21:46
*** annegentle_ has joined #openstack-meeting21:46
nijabaargh.. we have parity21:46
jd__ok let's say the PTL wins :->21:46
* nijaba feels empowered!21:46
nijabamedium it is then21:47
nijabaanything else on the poll?21:47
nijaba#topic Review blueprints and progress21:48
*** openstack changes topic to "Review blueprints and progress (Meeting topic: Ceilometer)"21:48
nijabaso for g2 we currently have21:48
dhellmannit looks like we only have one g2 blueprint not done, if I'm reading the list right21:48
dhellmannah, 221:48
nijabadhellmann: 2 actually21:48
nijabawe still have more than a month21:49
yjiang5anything left for db access?21:49
jd__let me check about db access21:49
nijabashould we be a bit more agressive?21:49
*** _0x44 has quit IRC21:49
jd__yeah, db access is removed EXCEPT from nova_notifier, but that doesn't matter since it's run INSIDE nova21:49
yjiang5I remember only the nova notifier21:49
*** _0x44 has joined #openstack-meeting21:49
jd__I think we should close this one21:49
nijabaenayone disagrees?21:50
dhellmannwhat is the status of removing db access from the nova compute agent?21:50
dhellmannwhen that lands, our notifier will break21:50
eglynnyep, good about the no-db-compute work21:50
eglynnthat's got a pretty long time horizon tho' AFAIK21:51
jd__dhellmann: done21:51
jd__no, the notifier is run by nova itself21:51
*** anniec has joined #openstack-meeting21:51
jd__not by ceilometer-something21:51
nijabaok, so I am marking it as implemented then21:51
*** anniec has quit IRC21:51
nijabaanyone cares to commit on another blueprint for g2?21:52
dhellmannjd__: I think some time during grizzly there won't be a database handle or settings available to the notifier plugin, either.21:52
dhellmannI think we should be conservative about adding things21:52
jd__dhellmann: ok, maybe, but I'd say that's another problem :)21:52
dhellmannwe have a lot of cleanup work to do, and figuring out the monitoring stuff is going to take a while, too21:52
*** anniec has joined #openstack-meeting21:52
dhellmannjd__: ok :-)21:53
*** yjiang5 has quit IRC21:53
eglynnyep, we can always add stuff opportunistically late in the cycle if by any chance we end up with loads of spare bandwidth21:53
nijabaeglynn, asalkeld: what about qpid testing?21:53
nijabathat should not be too risky21:53
eglynnnijaba: good question, I'll see if I can take that or hand it off21:53
nijabachange the target when you have a feel for it21:54
*** yjiang5 has joined #openstack-meeting21:54
eglynnnijaba: cool, will do21:54
nijabaso the only thing left is swift, and I thnk we should see progress soon21:55
jd__fingers crossed21:55
nijabadhellmann: you must be impatient on this one ;)21:55
*** AlanClark has quit IRC21:56
nijabaok, anything else on this?21:56
nijaba#topic Open discussion21:56
*** openstack changes topic to "Open discussion (Meeting topic: Ceilometer)"21:56
dhellmannI'm making good progress on the pecan & wsme work. I should have something to share next week, I think.21:57
nijabazykes-: you wanted to propose something?21:57
yjiang5dhellmann: cool21:57
nijabadhellmann: oh, cool. same as for eglynn for updating the bp21:57
dhellmann#action dhellmann update pecan port blueprint21:57
zykes-nijaba: fyi for people that care, StackSherpa is releasing a Java implementation of billing towards openstack, I'll be working with them on porting to Python21:58
zykes-meaning porting it over to Bufunfa that uses Ceilometer as source for one21:58
nijabazykes-: link?21:58
zykes-nijaba: Just talked to them a few mins ago21:58
zykes-they'll release a video tonight for it and java code opens next week21:59
nijabazykes-: is it open source?21:59
zykes-they sounded very keen on collaborating21:59
zykes-nijaba: it will be after what they said21:59
asalkelddhellmann, looked at the ceilometerclient yet?21:59
dhellmannasalkeld: not in depth :-(21:59
asalkeldwe need a ceiolmeterclient in openstack/21:59
asalkeldwith cli21:59
dhellmannit looked like yours was similar to the other libraries, right?21:59
zykes-nijaba: I can report next week :)22:00
yjiang5dhellmann: where is the tree of the client?22:00
asalkeldI tried to22:00
dhellmannoh, yeah, we should think about a blueprint for a cli22:00
zykes-they where supposed to opensource today but because of thanks giving they post poned22:00
nijabazykes-: please do and feel free to action youself22:00
asalkeldso happy to convert to a different format22:00
dhellmannyjiang5: asalkeld has one, and we have a little prototype at
dhellmannI think asalkeld's is more complete22:00
yjiang5dhellmann: thanks22:00
zykes-#action report status on Bufunfa / BillingStack port22:00
dhellmannasalkeld: have a link to yours handy?22:00
zykes-hmmms, :p22:00
nijabathanks zykes-22:01
asalkelddhellmann, do you have any examples of wsme+pecan22:01
dhellmannI got permission to release the dude open source, so we'll be working on that soon, too22:02
nijabaasalkeld: I think you just won an opp to write a matching bp :)22:02
dhellmannasalkeld: that's what I'm working on22:02
*** adjohn has quit IRC22:02
nijabadhellmann: \o/22:02
asalkeldso If I make a monitoring api I can start with wsme22:02
dhellmannI have our existing API working with pecan by itself, but the wsme parts are taking a little more time22:02
asalkeldI have started with flask22:02
*** adjohn has joined #openstack-meeting22:02
asalkeldif you have anything can you email it to me ?22:03
asalkeldo, cool22:03
dhellmanneverything is in the ceilometer_api dir for now (moving it into ceilometer package is on my list)22:03
dhellmannthere's no wsme there, yet22:03
dhellmanngive me a couple of days, I have a support request in :-)22:03
asalkeldseems like lots of directory clutter22:04
zykes-does it differ from flask much dhellmann ?22:04
dhellmannasalkeld: yeah, code generator, but it can be cleaned up a good bit22:04
dhellmannzykes-: it uses object dispatch22:04
dhellmannthe interesting file is
zykes-dhellmann: meaning ?22:04
nijabadhellmann: I think this should depend on having the user-api, though22:05
dhellmannnijaba: it will be fairly easy to add that feature to this when I'm done with the port22:05
dhellmannI am using v2 because of some changes to the API, so that can just be another change :-(22:05
nijabaso, who writes the bp?22:05
dhellmannoop, :-)22:05
dhellmannfor the user api?22:06
nijabadhellmann: for the cli22:06
zykes-adios peeps, will report back to you next week or later this week in #openstack-metering22:06
zykes-might have some updates before the weekend22:06
asalkeldI can make one if that helps22:06
* jd__ thinks it's getting late22:06
nijabaasalkeld: thanks22:06
dhellmannthat would be great, asalkeld, I'm running out of hours22:06
nijabajd__: me too22:06
yjiang5dhellmann: this pecan changes will not impact API format right?22:07
jd__yjiang5: I hope so for dhellmann's sake22:07
dhellmannyjiang5: some small changes, I think, but nothing major yet22:07
asalkeldwhat do you mean by format?22:07
dhellmannI'm trying to keep it the same22:07
dhellmannasalkeld: inputs and return values22:07
yjiang5I mean the API compatibility22:07
asalkeldI see22:08
asalkeldwell it's v222:08
dhellmannyjiang5: well, that's why I went with "v2" :-)22:08
asalkeldcan have big changes22:08
yjiang5dhellmann: great22:08
yjiang5asalkeld: big changes? ok.22:08
asalkeldI am just saying it could22:08
asalkeldas in it's version 222:08
yjiang5asalkeld: because of v2 :)22:08
nijabaok, so I think we are running over time and discussion can continue in our chan22:09
nijabawhat do you say we end the meeting?22:09
dhellmannone more thing22:09
dhellmannearlier today jd__ and I were talking in the main room and the idea of a bug day came up22:09
dhellmanndo we have enough bugs to make that worth-while?22:10
eglynn(^^^ general principals on what requires an API version bump)22:10
jd__for a day, probably22:10
dhellmanneglynn: thanks, I'll review that22:10
* eglynn likes bug squashing days22:10
dhellmannoh, we're way over time, sorry, I'm not looking at the clock22:11
eglynngood for team coherence as well as the obvious goal22:11
dhellmann something to discuss next week?22:11
*** jdurgin1 has quit IRC22:11
nijabaShould that be a week before the g2 misltone?22:11
nijaba#action nijaba to set topic for bug day at next meeting22:11
* dhellmann will have to look at a calendar to answer that22:11
nijabaanything else?22:12
nijaba30 sec countdown22:12
eglynnnowt from me ...22:12
asalkeldall good22:12
jd__all clear22:12
nijabathanks everyone22:12
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:12
openstackMeeting ended Wed Nov 21 22:12:43 2012 UTC.  Information about MeetBot at . (v 0.1.4)22:12
eglynn'night all22:12
openstackMinutes (text):
*** stevebake has quit IRC22:14
*** shardy is now known as shardy_afk22:26
*** dhellmann is now known as dhellmann-afk22:27
*** vipul is now known as vipul|away22:28
*** rnirmal has joined #openstack-meeting22:28
*** yjiang5 is now known as yjiang5-away22:29
*** vipul|away is now known as vipul22:29
*** stevebake has joined #openstack-meeting22:30
*** esp has left #openstack-meeting22:30
*** yjiang5-away has quit IRC22:35
*** nati_ueno has quit IRC22:50
*** andrewbogott is now known as andrewbogott_afk22:51
*** samkottler|afk is now known as samkottler22:52
*** AlanClark has joined #openstack-meeting23:01
*** dedis0 has joined #openstack-meeting23:03
*** cdub has quit IRC23:07
*** nati_ueno has joined #openstack-meeting23:12
*** nati_ueno has joined #openstack-meeting23:12
*** nati_ueno has quit IRC23:14
*** anniec has quit IRC23:15
*** AlanClark has quit IRC23:15
*** andrewbogott_afk is now known as andrewbogott23:17
*** zoumpis has quit IRC23:18
*** anniec has joined #openstack-meeting23:20
*** anniec has joined #openstack-meeting23:20
*** zoumpis has joined #openstack-meeting23:24
*** cdub has joined #openstack-meeting23:27
*** mattray has quit IRC23:27
*** vipul is now known as vipul|away23:33
*** vipul|away is now known as vipul23:34
*** vipul is now known as vipul|away23:36
*** vipul|away is now known as vipul23:37
*** jaypipes has quit IRC23:49

Generated by 2.14.0 by Marius Gedminas - find it at!