19:00:24 #startmeeting Ironic 19:00:24 #chair devananda 19:00:25 Welcome everyone to the Ironic meeting. 19:00:25 Meeting started Mon Oct 27 19:00:24 2014 UTC and is due to finish in 60 minutes. The chair is NobodyCam. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:00:28 The meeting name has been set to 'ironic' 19:00:29 Current chairs: NobodyCam devananda 19:00:33 who's here 19:00:36 o/ 19:00:37 \o 19:00:41 Hello all, I'm from Fujitsu. I joined today to learn how the meeting is proceeding. Because I added a new topic, iRMC driver, for the next meeting. 19:00:41 o/ 19:00:42 hi 19:00:46 hi 19:01:03 hi all, devananda will be a few minutes late this morning 19:01:23 Of course the agenda can be found at: 19:01:23 #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting 19:01:32 #topic Greetings, roll-call and announcements 19:01:53 one week until we get to see each other f2f 19:02:11 woohoo! 19:02:14 o/ 19:02:15 sorry I'm late 19:02:20 o/ 19:02:27 anyone have any announcements of such 19:02:32 Welcome devananda :) 19:02:36 your nit late 19:02:43 not even 19:02:48 no announcements here 19:03:08 aside from the obvious "omg the conference is next week" general chaos :) 19:03:28 awesome.. okay at teh last meeting we decided to keep this meeting focused on summit topics 19:03:41 so I am bypassing the normal adgenda 19:03:55 o/ 19:04:16 we're so organized today, look, I even updated the wiki page to say that! 19:04:25 :) 19:04:28 heheheh 19:04:43 o/ late 19:04:45 so, in case anyone hasn't seen it, I did post the discussed summit sessions to the official places 19:04:48 #link http://kilodesignsummit.sched.org/overview/type/ironic 19:05:03 #topic "K" summit planning 19:05:11 #link http://kilodesignsummit.sched.org/overview/type/ironic 19:05:22 if folks want to discuss those, think there really needs to be changes to the main track agenda, now's the time to speak up 19:05:33 I'll give a few minutes for everyone to review 19:05:59 it doesn't show the operators' one. That's on Monday, right? 19:06:14 rloo: correct. in a different track 19:06:26 that link only lists the official "ironic" design track 19:06:34 not our sessions in other tracks, sessions of initerst to us, etc 19:06:34 rloo: this will: http://kilodesignsummit.sched.org/?s=ironic 19:06:57 ah, good link NobodyCam 19:07:05 thx NobodyCam. Now I know who devananda is ;) 19:07:14 lol 19:07:21 there are also some slots in other tracks that don't explicitly say "ironic" which are probably very interesting to some of you 19:07:42 nova scheduler discussions, in-project functional testing, docs, etc ... 19:07:56 I'm happy to discuss those now, provide links to the ones I know, if that would be helpful to folks? 19:08:05 cross project dependices? 19:08:19 well 0- not just yet. let's give a few more minutes for everyoneto review the main ironic sessions 19:08:29 would it be worth putting links in an etherpad or somewhere accessible when I'm at the summit? 19:08:53 rloo: I have found etherpads to be terrible references at a conference 19:09:02 they requrie a laptop; accessing them from my phone is bad 19:09:09 rloo: so I'd propose we sue https://docs.google.com/spreadsheets/d/1XBKdeDeGfaRYaThjIIoYRwe_zPensECnxsKUuqdoVmQ/edit#gid=101783491 for that 19:09:10 I keep getting kicked from them at the conf 19:09:10 devananda: ok. that's fine. I'll probably just follow the other ironic folks around anyway :) 19:09:12 tab 3 19:09:24 devananda: I'm not sure how flexible your sched is but there's overlap between your functional test session, nova's, and a similar qa session 19:09:32 google spreadsheet is easy to cache 19:09:51 mtreinish: indeed there is, thanks for pointing it out 19:10:23 I also need to bug mikal about it again when he's awake 19:10:27 mtreinish: my goal for the ironic session is to discuss hwo we want to implement it 19:10:45 whereas I imagine the qa session is broader and will inform what we talk about 19:11:08 however, time overlap with Nova is going to be tricky -- I'll need to see if mikal can reschedule his so that some of us can attend 19:11:48 devananda: yeah the qa is going to be more about how do we migrate from having everything functional black box be in tempest to more spread out in the projects 19:11:57 and what that means for tempest policy moving forward 19:12:58 functional testing of nova.virt.ironic and where that lives is going to be important as well, which is what mikal and I should figure out 19:13:09 mtreinish: when is the qa session? 19:13:30 devananda: the same time as the ironic and nova functional testing ones :) 19:13:46 http://kilodesignsummit.sched.org/event/9dbde26cced67b54d24176b746d3027e#.VE6ZZ3_tljE 19:13:54 oh haha 19:13:56 that's terrible 19:14:12 i didn't realize the TIME was the same too 19:14:50 why isn't the QA one in the cross-project track? 19:14:50 mtreinish: you can't bump that to thurs afternoon? 19:15:07 rloo: there is also a proposed cross project session for functional testing 19:15:20 rloo: this is more about the specifics of how we change tempest 19:15:28 er, i mean wed. afternoon 19:15:38 devananda: yeah I can move it around a bit 19:15:48 I just wanted to connect with you and mikal before I do that 19:16:03 mtreinish: ironic slots are wed. morning 19:16:28 ok, well that makes avoiding that conflict easy :) 19:16:45 indeed 19:16:58 that said, it also means there's no point in us talking about how irnoic will implement it on wed. morning 19:17:32 that would free up a slot for something else? 19:17:35 NobodyCam: yes 19:18:04 NobodyCam: the other angle on that session was going to be how we make Ironic more stand-alone (and thereby how we could test it in such a configuragion) 19:18:15 is it worth still having a session to go over that work? 19:18:49 devananda: I would love to test ironic standalone 19:19:04 devananda: well the qa track discussion should be somewhat independent 19:19:16 because it's more about the tempest policy around removing tests 19:19:25 devananda: and/or talk about how we want to do functional testing 19:19:29 and the criteria for new tests 19:19:31 I think it's worth a slot 19:19:55 devananda: yes i think so. if we have extra time we ca pick a secondary topic too 19:20:08 what you guys want to have for your in-tree testing should be fairly ironic specific 19:20:27 but I think that will be a largish topic on it own 19:20:49 mtreinish: more related to tempest-lib, then? 19:22:16 jroll, NobodyCam: cool. taht's my sense as well. I'll update the session title to clarify it 19:22:29 :) +1 19:22:45 devananda: yeah, I imagine the tempest-lib session will decide some of your internal implementation choices 19:22:59 I'm really hoping the cross project functional testing topic get's picked up 19:23:31 so we can decide on common framework stuff there and leave the tempest-lib conversation for more the implementation details in tempest->tempest-lib 19:24:48 mtreinish: ++ 19:25:08 are there other conflicts anyone's noticed? 19:27:49 (I'll take no answer to mean "no") 19:28:13 :) 19:28:19 #topic summit extra-curricular activities 19:28:36 this is the best part :P 19:28:47 I had raised the idea of a team dinner or BoF session a while back 19:28:53 before concrete schedules were known 19:29:36 Shrews: wants us to drink because he's not going to be there 19:30:17 I'm going to be unfortunately busy thurs night with the TC dinner 19:30:20 I'd prefer monday or tuesday for a team thing, personally 19:30:21 I'd love a team dinner, and for selfish personal reasons would like it to be any day but Wednesday :) 19:30:32 heh 19:30:38 dinner may be tuff with all the partys 19:30:41 wed. many of us are going to be busy 19:30:42 wednesday is the core reviewer party thing 19:30:48 jroll: right 19:31:15 monday or tuesday would probably be best. I can skip out on some of my obligations those nights 19:31:15 mon , tue, and wed are tuff 19:31:21 :) 19:31:33 JayF: Feel so hungry when hearing the dinner discussion. 19:31:44 would breakfest work? 19:31:59 I'd also be thrilled if ya'll get together w/o me 19:32:10 NobodyCam: breakfast may be the best option, schedule wise 19:32:28 how about tuesday morning? 19:32:37 I could do that 19:32:52 Assuming they have breakfast that doesn't consist of a bagutte and/or croissant 19:32:54 lol 19:33:17 tuesday morning is fine for me 19:33:17 can I get a quick count of folks who could make a tuesday 8am breakfast? 19:33:29 assuming Shrews doesn't make me drink at breakfast 19:33:35 \o 19:33:39 o/ 19:33:40 \o 19:33:50 * NobodyCam has been wanting creps for well over a month now 19:34:02 #vote should we have a tuesday morning 8am breakfast? 19:34:04 maybe (I like to sleep in) 19:34:05 o/ 19:34:10 rloo ++ 19:34:13 hmm. that didn't work 19:34:19 maybe 19:34:23 sleeping is overrated :P 19:34:40 #startvote should we have a tuesday morning 8am breakfast? 19:34:41 Begin voting on: should we have a tuesday morning 8am breakfast? Valid vote options are Yes, No. 19:34:43 Vote using '#vote OPTION'. Only your last vote counts. 19:34:48 #vote Yes 19:34:49 there we go 19:34:49 Yes 19:34:50 #vote Yes 19:34:56 #vote Yes 19:34:57 #vote Yes 19:34:57 #vote Yes 19:34:58 * JayF hands NobodyCam a #vote 19:35:03 lol 19:35:09 ty JayF 19:35:33 if you would prefer to have a team dinner, vote "no" 19:35:39 and I will do a seaprate vote for that 19:35:51 we could do both 19:35:55 I think we should attempt to have a team dinner, even if folks can't be there 19:36:03 #vote No 19:36:10 #vote No 19:36:37 (giving it another 30 seconds) 19:36:54 prefer dinner 19:37:04 wanyen: vote no then please 19:37:12 vote No 19:37:37 wanyen: you need to use a # mark, like "#vote no" 19:37:50 #vote No 19:37:55 :) 19:37:58 #endvote 19:37:59 Voted on "should we have a tuesday morning 8am breakfast?" Results are 19:38:28 ... 19:38:29 drum roll 19:38:41 must be a heavy db query 19:38:52 too many votes... takes longer... 19:38:57 lol 19:39:00 dramatic pause 19:39:02 IRC is tcp, right? 19:39:03 hehehhe 19:39:03 or maybe rabbit died 19:39:11 * devananda wonders if the bot died 19:39:14 Does the robot have a stuck lock? 19:39:35 * devananda counts by hand 19:39:48 yes: 5 no: 3 19:39:49 luv's tech 19:40:08 I would be ok with having both B and D 19:40:10 #startvote should we have a Monday evening gathering instead? 19:40:11 Begin voting on: should we have a Monday evening gathering instead? Valid vote options are Yes, No. 19:40:12 Vote using '#vote OPTION'. Only your last vote counts. 19:40:13 devananda: tht matches my log count 19:40:22 JayF: thanks 19:40:24 #vote yes 19:40:30 #vote yes 19:40:33 "instead is a weird word" 19:40:37 * JayF clarifies; he thinks we should have both 19:40:38 #vote yes 19:40:41 err. 19:40:46 "instead" is a weird word. 19:40:49 #vote yes 19:41:02 #vote no 19:41:05 #vote yes 19:41:19 #vote yes 19:41:21 :) 19:41:22 though I may not be ableto make it. but will try 19:41:25 #vote yes 19:41:29 #vote Yes 19:41:49 what else is happening monday night? 19:42:03 jroll: there's a booth crawl 5 - 7 or something like that 19:42:11 meh :) 19:42:15 and some companies have their internal/private get togethers at taht time 19:42:19 and hp employee party? 19:42:30 ++ 19:42:33 and at 8pm Mirantis is throwing the underground party 19:42:38 http://openstacksummitnovember2014paris.sched.org/event/5c3f044471d857d8cff5de124f838040 19:42:40 cool 19:43:15 Can we have dinner on other night? 19:43:29 wanyen: only other option for me is friday 19:43:38 breakfast might be the best option 19:43:39 #endvote 19:43:41 Voted on "should we have a Monday evening gathering instead?" Results are 19:43:41 I see 19:43:56 bot apparently does not want to tally our votes 19:44:08 lol it wants us to have both 19:44:18 votes for monday dinner: yes 8, no 1 19:44:25 that's a clear winner over breakfast 19:45:06 (and I was the only objection) 19:45:09 so monday night dinner it is 19:45:15 #agreed monday night team dinner in paris 19:45:57 fwiw, I'll be going to breakfast tuesday morning and folks are welcome to join me :P 19:46:06 jroll: ++ 19:46:29 are folks going to bail out of dinner if devananda doesn't show? 19:46:48 My only concern with devananda not showing 19:46:55 is that we might not go to a place I can eat :) 19:46:58 hah 19:47:10 I'd like to be there :) 19:47:10 I'm living on baguettes the entire time 19:47:18 and so excited to do so 19:47:19 jroll: poison! 19:47:20 pain au chocolat :D 19:47:22 :D 19:47:38 do ya'll want to do something more formal (like, reserve it in advance) 19:47:49 or just gather somewhere, wander off, and see what you find? 19:48:04 I think that's prudent, especially if you and I are both going to be there and need dietary considerations 19:48:08 i'd be up for the see what you find option 19:48:24 I think JayF should suggest something 19:49:03 rloo: I think someone who can read french should suggest something.... and tell me their rates for being my personal guide all week :P 19:49:13 JayF: ++ 19:49:19 lol 19:49:26 I think liver and onions might be gluten free 19:49:35 http://glutenfreemom.com/travel_gluten_free/paris/ 19:49:38 rloo: gravy starts with a roux 19:49:39 omg the meeting started already? :( damn DST 19:49:49 * lucasagomes will read the logs 19:49:56 lucasagomes: hi there! we assigned you everything :) 19:50:09 devananda, hah oh noes 19:50:18 lo 19:50:19 lol 19:50:32 people keep talking about DST, did it change in europe or? 19:50:40 yeah, it did yesterday 19:50:43 aha 19:50:44 but I forgot 19:50:48 it changes next week here I think 19:50:48 jroll: yes. US time is crazypants 19:50:55 time zones are crazypants 19:50:56 lucasagomes, lol 19:50:57 I hate them 19:51:00 utc all the things 19:51:04 ++ 19:51:09 jroll: tshirt that 19:51:11 (including people) 19:51:12 People in US get to escape DST 19:51:13 ha 19:51:20 because US switches while we're gone, and Paris already switched 19:51:22 and it's holiday here so, I wasn't paying much attention to time 19:51:26 so we just get slightly asymetric jet lag 19:51:30 jet lag will hit harder than DST :P 19:51:43 it seems like we're done with that particular discussion 19:51:50 indeed 19:51:54 yup move on 19:52:04 let's follow up with details of when/where via email (directly to folks, not on ML) 19:52:11 #topic open discussion 19:52:19 devananda: May I interrupt a little bit? I'd like to have some advice. 19:52:40 I'm preparing the blueprint for iRMC driver. Is there anything else I should do by the next meeting? 19:52:41 I'll be putting in the beginnings of a spec for node/hardware capabilities -> https://blueprints.launchpad.net/ironic/+spec/exposing-hardware-capabilities this afternoon, and anyone who wants to help expand on it or work on the implementation is very welcome to 19:52:43 I have a general question, how do we handle say blue prints assigned to someone who is not responding 19:53:02 other than getting the idea through hand helping reivew, I don't think I'll have time to give hardware capabilities the TLC it will need 19:53:15 naohirot: do you know our spec process? 19:53:25 so anyone who wants to spend some time on that particular topic, please LMK. I'll make sure the spec is linked into the channel before I leave work today 19:53:32 naohirot, submit a spec, and also next week I believe we won't have a meeting because of the summit 19:53:34 a little bit, I'm learning. 19:53:38 naohirot: we don't really need to talk about blueprints in meetings, we just get the spec approved and start coding :) 19:53:58 naohirot, https://github.com/openstack/ironic-specs/blob/master/README.rst 19:54:01 I know the next meeting is Nov. 17th 19:54:13 right 19:54:17 NobodyCam: we email them. if someone else wants to work on it and author is non responsive, propose a new BP, or ask me to unassign it 19:54:38 naohirot: once you have the spec up for review, we'll start looking at it... feel free to drop a link in #openstack-ironic as well :) 19:54:45 Unfortunately I cannot go to Paris. 19:54:46 devananda: this is in ref to cinder stuff 19:55:00 this = my question 19:55:04 jroll: Okay 19:55:24 I hope that the summit goes well. 19:55:32 :) 19:55:35 NobodyCam: I'd ping other cinder cores then, since that's a cinder issue 19:55:54 oh, minor announcement - I may not make the Nov 17th meeting 19:56:28 NobodyCam or lucasagomes - will either of you be able to lead that one? 19:56:37 I will probably be on a plane at that time 19:56:37 devananda, yup, no problem for me 19:56:44 lucasagomes: great, thanks 19:56:51 devananda: https://blueprints.launchpad.net/ironic/+spec/cinder-integration 19:57:17 * lucasagomes adds to the calendar 19:57:29 devananda: we got ya covered 19:57:37 JayF: if you're proposing a spec that you dont have time to implement, please indicate that lclearly in the "asignee" portion 19:57:57 we shouldn't approve the spec until someone steps up to work on tjhe code, IMO, but I can be convinced otherwise 19:58:00 devananda: absolutely will; this is w/r/t what we talked about last week 19:58:14 JayF: yup. and cheers for working on the spec. 19:58:15 devananda: and agree with you about finding someone to shepherd it before approval 19:59:12 NobodyCam, iLO driver team plan to look into cinder integration in L release 19:59:31 oh that's nice, boot from volumes? 19:59:41 NobodyCam: fwiw, https://wiki.openstack.org/wiki/Ironic/blueprints/cinder-integration 19:59:49 yes 19:59:50 looks like hemna wrote that up about a year ago 19:59:59 devananda: thats the soec I was reffering to 20:00:07 wanyen: are you working with Walter Boring on that? 20:00:29 oops, we're out of time! 20:00:35 :) 20:00:39 great meeting all 20:00:44 Devananda, not lately. We had a few meetings about that a while back. 20:00:49 thanks 20:00:50 thanks all -- can't wait to see you in Paris next week! 20:00:56 #endmeeting