22:05:18 #startmeeting horizon 22:05:19 Meeting started Tue Jun 25 22:05:18 2013 UTC. The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot. 22:05:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 22:05:22 The meeting name has been set to 'horizon' 22:05:28 hello folks 22:05:35 hi 22:05:36 hello 22:05:37 hello 22:05:41 #topic overview 22:06:05 hello 22:06:13 We're halfway through H2. Lots of stuff in progress and "needs code review". I think the overall progress is going well, but we definitely need to start getting stuff merged 22:06:41 hey 22:07:15 The only other general thing I have is that discussion on where UX discussions on the mailing list continues to go well, and I think another week there is probably good. Anyone with opinions should follow up on the thread. 22:07:31 let's just jump into blueprints 22:07:34 #topic blueprints 22:07:38 I'llgo first 22:07:44 I'm working on the heat code right now 22:07:54 I've gone through a few iterations and ultimately I think the simplest solution is gonna be best 22:08:41 we start with chosing a template (whether by URL, file, or direct input). that's one step in-and-of-itself. Everything else flows from that and it makes the next step of adding parameters, giving it a name, etc. nice and clean and self-contained. 22:08:53 I'm rewriting the code (again) to prove this out as we speak 22:08:59 but I think this'll be the final go-round for it 22:09:06 so that's very good 22:09:11 :) 22:09:22 Is this still using workflows? 22:09:23 Once I get that up for review I'm gonna check out the realtime proof-of-concept and sepnd some time with that 22:09:38 timductive: no, I've actually dropped it back to two simple forms which just chain one to the other 22:09:46 ok 22:10:11 timductive: with any luck I'll have code up for review by tomorrow 22:10:23 so, that's wht I've got. who else wants to go? 22:10:24 ok, great! I'll be sure to look at it 22:10:35 Mine is quick 22:10:41 go for it 22:10:46 gabrielhurley: so does this replace/update https://review.openstack.org/#/c/29478/ 22:10:58 david-lyle: update 22:11:10 much of the code is the same 22:11:19 mostly refactoring the UX 22:11:31 ok, will it be a different commit? 22:11:31 still working on the heat topology, I talked with Brad Jones about the d3js library and I'm using it as well 22:11:50 david-lyle: nah, I'm just gonna rebase it back into the same patchset 22:11:51 just wondering if we should -2 the existing until your code is up 22:11:58 oh, I suppose so 22:12:08 not that anyone's been desperately trying to merge it thus far 22:12:17 timductive: awesome! 22:12:28 I'm really excited to see that 22:12:36 I'm hoping to have a WIP up late this week 22:13:17 timductive: sounds perfect 22:13:32 :) 22:13:32 david-lyle: you wanna give some updates since you've got the most blueprints? 22:13:39 lcheng: you can go after david-lyle 22:13:56 sure 22:14:16 domain context is up and awaiting review 22:14:27 * gabrielhurley needs to look at that... 22:14:42 the region selection code has merged and the only thing left is managing multiple endpoints in the same region 22:15:09 still planning on starting rbac, got delayed a couple of days 22:15:30 okay. I expect that one to slip to H3 anyhow 22:15:44 yeah, I think it's a sizable effort 22:16:25 david-lyle: can you update https://blueprints.launchpad.net/horizon/+spec/multiple-service-endpoints to reflect that that's merged 22:17:20 oh, maybe that's updated correctly. I may've misread what you said just now 22:17:21 sure. should I split of the multiple endpoints in the same region to a separate blueprint? or just update the status 22:17:31 I think separate BPs would be good 22:18:02 ok, I will do that and mark the current one as complete 22:18:23 great 22:18:37 lcheng: I think you're up. 22:18:49 keystoneclient v3 auth has finally merged. Requesting for a release of keystoneclient so that we can consume it in openstack_auth. 22:18:50 jpich: I don't see Brooklyn around so maybe you can speak on ceilomter? 22:19:11 Dolph is currently out, ttx will do the release for this.. 22:19:11 lcheng: yep, you should have that tomorrow one way or the other 22:19:12 gabrielhurley: thanks for following this up on the release meeting. 22:19:17 no problem 22:19:36 I still need to update my old patch for openstack_auth to consume some of the goodies added in keystoneclient. :-) 22:19:56 yeah, now that it's actually landed in keystoneclient I'll make sure to get that in once you update it. 22:20:01 Hopefully will get it ready for review next week. 22:20:06 sounds good 22:20:09 gabrielhurley: Yep. He sent me an email about it today, the patch was updated based on the first round of feedback, I'll have another look during the week. I guess the next step will be to put it up on gerrit to give it more visibility and review the details more easily 22:20:20 jpich: great 22:20:31 It'd be great to get a first pass of that into H2 22:21:05 It would 22:21:53 anybody else wanna give updates? 22:22:01 * gabrielhurley doesn't know everyone's IRC handles offhand 22:22:17 cody-somerville: haven't heard from you in a bit... 22:23:01 gabrielhurley: Hey. Sorry. Been busy with conferences. 22:23:26 hi there. all good. any news, or "no news *is* the news"? 22:24:38 I don't have too much to share except that I haven't forgotten about my bp for H2. I also think there has been some good conversation started on the ml lately re: horizon. 22:25:29 cool. unless you strongly think you're gonna land something in H2 I'm gonna defer that BP to H3, but it's a big one so seeing code earlier in H3 is kind of a must 22:27:13 Going to be in Italy next week but going to try and find some time this week to determine what we can make actionable for H and what we can have lined up and ready to go for I. 22:27:21 sounds good 22:28:11 last call for blueprint updates. I'm gonna start bumping anything that's not started come next week. And that'll impact what fits in H3 as well. 22:29:44 oookay 22:29:48 #topic open discussio 22:29:56 #topic open discussion 22:30:11 questions? comments? 22:33:33 I have one general question about D3 charting 22:34:47 We are playing around with concepts for Horizon and playing with charts (e.g for usage consumption of resources in time). 22:35:06 So e.g. for this purpose is needed line chart 22:35:34 building it with pure D3 takes quite time and effort, so we were thinking about using some additional library 22:35:52 currently investigating good ones, but in general something like this: http://nvd3.org/ghpages/lineWithFocus.html 22:37:04 We'd like to bring this upstream, so I am just asking if there is any problem with bringing in some additional libraries on the top of D3 or if it is ok...? 22:37:54 (more thinking about one additional library, not set of different ones) 22:38:14 any thoughts? 22:39:00 I asked a similar question last week :) 22:39:34 timductive: ah, sorry, didn't notice that :-/ what was the conclusion? 22:39:49 jcoufal: things built on D3 or cool. there are tons of good d3 plugins 22:39:57 I just don't want a proliferation of different underlying libraries 22:40:11 *are cool 22:40:36 I'm sure there is a good line graph plug-in for d3 22:40:42 there are 22:40:47 yeah, definitely on top of D3 22:40:49 several of them 22:41:09 is nvd3 one? 22:41:16 perfect, that's all I needed to know 22:41:31 timductive: if you have some suggestion, will be happy to hear about some 22:41:58 jcoufal: I'll let you know if I find any 22:42:22 timductive: yeah, it is first we found somehow useful. Will let you know about our results 22:42:35 great, thank you guys 22:42:55 cool 22:42:59 have a great week folks 22:43:02 #endmeeting