20:15:58 #startmeeting tripleo 20:15:59 Meeting started Mon Sep 9 20:15:58 2013 UTC and is due to finish in 60 minutes. The chair is lifeless. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:16:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:16:02 The meeting name has been set to 'tripleo' 20:16:09 #topic agenda 20:16:16 bugs 20:16:16 Grizzly test rack status 20:16:16 CI virtualized testing progress 20:16:16 open discussion 20:16:17 is it enough to just do ^^ ? ;) 20:16:24 #topic bugs 20:16:31 Discussed earlier, see actual logs. 20:16:38 #topic Grizzly test rack status 20:16:44 end of september this becomes free 20:16:47 I might ask our users if we can cannablise part of it earlier 20:16:54 08:15 < SpamapS> Yeah it would be nice to have some hardware for the sprint 20:16:57 ok 20:17:00 08:15 < SpamapS> (hardware whose network configuration we know actually works I should say ;) 20:17:06 sorry for mootbot protocol fail there 20:17:24 SpamapS: yeah, thats a major aspect for me 20:17:34 #topic CI virtualized testing progress 20:17:55 so, I have an lxc config file that seems to work and the seed node running in lxc 20:18:24 process list shows I should have everything I need, but working to get over some hurdles actually accessing keystone (and so nova, glance, etc) 20:18:43 would you like some interactive debugging assistance? 20:18:46 notes still being tracked in the etherpad 20:18:49 #link https://etherpad.openstack.org/tripleobaremetallxc2013 20:18:54 I might need some, yeah 20:20:48 but once I get this done, I'll be patching boot-seed-vm and a few other scripts that need some tweaks to support lxc 20:21:13 that's pretty much it for now 20:21:35 cool 20:21:45 #topic open discussion 20:22:10 lifeless: you mentioned we're assured 5 slots for tripleo at the summit.. 20:22:24 yes 20:22:27 lifeless: what about Tuskar? Seems like we are all related 20:22:59 good question! 20:23:08 slots? 20:23:16 shadower: sessions 20:23:46 shadower: there are a fixed number of rooms, with blocked out time periods for programs 20:23:58 ~1hour discussions in rooms with projectors and smartish people :) 20:24:28 so, Tuskar doesn't get any time window as it's neither an official program, nor an incubated one. 20:24:48 I think it's entirely reasonable for us to share our 5 slots amongst all deployment discussions 20:25:14 I thought it had a perliminary go-ahead on incubation. 20:25:23 prelim even 20:25:27 so - Tuskar sessions proposals should be put in the tripleo stream 20:25:52 Ok agreed, particularly I think it is reasonable to devote a session to "what other programs need from tripleo" 20:26:22 SpamapS: no, Tuskar have self-organised to elect a PTL, but no request has been made of the TC to consider them. 20:26:40 * shadower wondered if he missed something 20:27:00 SpamapS: (and that would provoke substantial discussion given the current wording they put forward as a mission, since it's 99% overlap with the OpenStack Deployment program - tripleo - wording 20:28:24 SpamapS: which Monty alludes to in his email in the Savanna Incubation Request thread. 20:28:48 shadower: Missed something ? 20:29:10 lifeless: re: premilinary incubation go-ahead 20:29:50 do we have interest from any of the other programs in feeding requirements/features into tripleo? 20:30:12 Thats kind of what I'm getting at. I understand that tuskar is built on top. 20:30:23 SpamapS: yeah, - propose a session :) 20:30:34 But like, we had trove using our dib tools, and Heat could potentially start relying on o-c-c .. etc. etc. 20:30:42 lifeless: I will, wanted to hash it out here :) 20:31:03 SpamapS: it seems like a reasonable thing, but perhaps having tuskar specific sessions would be more productive 20:31:25 SpamapS: I worry that a 'come tell us your needs' session will be 10m of discussion and 40m of crickets 20:31:48 me too, hence my thinking Tuskar lumped in there would provide a forum but not waste our time 20:31:51 SpamapS: vs a 'lets work with Tuskar on the bootstrap / user admin / management stories' 20:32:12 shadower: I haven't seen an incubation request for Tuskar 20:32:46 shadower: the summit time allocation process is based on the programs & [legacy model] projects approved by the tc 20:32:52 lifeless: yeah, me neither and I'm not aware of any preliminary talks either 20:32:57 right 20:33:07 shadower: so this came up here in context of 'what about time slots to discuss tuskar things' 20:33:11 shadower: ack cool - same page. 20:33:16 yup 20:33:33 shadower: so I'm proposing that we advise folk interested in Tuskar sessions to submit them and put them in the TripleO stream. 20:33:44 I might see if ttx can rename that 'Deployment' as thats the actual program name. 20:33:51 And would avoid confusion. 20:34:00 Yeah, I'm not going to put one in myself. 20:34:12 shadower: what do you think? 20:34:21 lifeless: sounds great, thanks 20:34:28 The ones already in there are all the stuff I think we need to discuss internally to our program anyway. 20:34:37 (there are plenty of other things outside us that need discussing) 20:34:41 shadower: we only have 5 session slots, but we should be picking from the full set of sessions that would fit there. 20:34:51 lifeless: is this related to the talks whose abstract deadline was several weeks ago or is this something else? (the sessions) 20:34:57 shadower: something else 20:35:07 shadower: the technical design portion of the summit 20:35:26 shadower: http://summit.openstack.org/ 20:35:27 lifeless: right. Sorry, I've never been on one and didn't read up on it yet 20:35:52 lifeless: I'll bring it up on Tuskar's meeting tomorrow (hopefully more informed by then) 20:37:47 shadower: np; I've mailed thierry about changing the label for now 20:37:56 cool 20:38:28 ok 20:38:32 timing out the meeting in 1m 20:38:42 * SpamapS would like to get going actually 20:38:56 as in 'motion to end meeting early seconded' 20:39:07 thrid 20:39:10 third 20:39:55 #endmeeting