19:00:15 #startmeeting Ironic 19:00:15 #chair devananda 19:00:16 Welcome everyone to the Ironic meeting. 19:00:16 Meeting started Mon Mar 10 19:00:15 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:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:00:19 The meeting name has been set to 'ironic' 19:00:20 Current chairs: NobodyCam devananda 19:00:29 who's here for the Ironic meeting 19:00:33 \o 19:00:34 \o 19:00:34 o/ 19:00:35 o/ 19:00:37 o/ 19:00:37 me 19:00:38 o/ 19:00:38 howdy :) 19:00:40 o/ 19:00:45 me 19:00:46 \o 19:00:56 hi all! 19:00:59 welcome all 19:01:01 Of course the agenda can be found at: 19:01:01 #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting 19:01:09 #topic Greetings, roll-call and announcements 19:01:17 I was missing you :) 19:01:19 it was great to see so many of you last week -- and for the rest, I look forward to seeing you in Atlanta 19:01:21 was great to see everyone at the sprint 19:01:31 :) 19:01:54 So I'm tagging along with the other Rackers 19:02:11 devananda: would you like to recap some if last week? 19:02:16 hopefully we can keep the meeting somewaht short today - i suspect some of us are still recovering from travel 19:02:18 new deploy agent? 19:02:19 NobodyCam: sure 19:02:30 and time change 19:02:41 so three things happened last week that I want to mention 19:03:12 feature freeze was tuesday, and ttx cut an I3 milestone of Ironic 19:03:50 we're following the general releace cycle, which means no more major features should land in tree until Juno opens 19:04:09 bug fixes, documentation, and integration work are all good things to work on 19:04:19 there's plenty of that to go around :) 19:04:30 :) 19:04:42 also 19:04:55 we talked with the rackspace team a bunch about their driver and deply agent 19:04:59 o/ 19:05:18 i sent an email to the list, so i won't recap much here 19:05:34 besides to welcome them to the meeting and the project 19:05:52 and say that i'm excited to have rackspace finally joining us :) 19:06:00 :) 19:06:01 lastly 19:06:19 adam_g and Shrews made a lot of progress with agordeev's devstack patch 19:06:24 and it seems to be quite functional now 19:06:36 Does Nova Ironic driver make to the icehouse? 19:06:42 nice! 19:06:49 awesome and welcome to the RS folks 19:06:53 I woud like to draw attention to the fact that we have pulled the ironic-nova driver into our tree. for those who have not seen it there yet 19:07:09 wanyen: ^^ 19:07:10 no 19:07:20 wanyen, the Nova Ironic Driver is now being developed in the Ironic tree 19:07:32 wanyen, we are going to push it to nova again on J 19:07:43 yes! 19:08:04 #link https://review.openstack.org/#/c/78002/ 19:08:15 oka, Thanks! 19:08:15 ty lucasagomes :) 19:08:21 NobodyCam: thanks for the reminder - and for those who want to know more, I mentioned that in my email t othe dev list as well 19:08:44 devananda, the guide agordeev created is still relevant or needs to be updated: https://etherpad.openstack.org/p/IronicAndDevstackAgain ? 19:08:47 anyone else have announcements / things to share from last week? 19:09:05 And if anyone needs any help with testing of the Nova Ironic Driver, I'd be more than glad to pitch in <-- tester/CI person 19:09:05 ifarkas: i believe taht etherpad is correct. last I saw, adam_g was updating it as he went 19:09:17 devananda, ok, thanks 19:09:17 other then BIG thank you's to HP and YAHOO! for hosting 19:09:18 dwalleck: yes! thanks! see that etherpad ^ 19:09:28 We did set up https://etherpad.openstack.org/p/IronicDocumentationTasks to coordinate work on documentation if that's useful to others 19:09:35 dwalleck: please chat with Shrews and adam_g in #openstack-ironic post meeting 19:10:02 #link https://etherpad.openstack.org/p/IronicDocumentationTasks 19:10:08 devananda, ifarkas: i question the correctness of that etherpad, atm 19:10:39 Shrews: ack ... well, it's an etherpad after all ... i'm sure someone will update it ;) 19:10:48 mainly because 70348 is not referenced anymore for some reason 19:11:14 ok, moving on then 19:11:17 #link https://review.openstack.org/#/c/70348/ 19:11:24 Shrews, devananda, right. the localrc file still checks out the gerrit branch for nova 19:11:38 ifarkas: ah. that's a problem 19:12:01 it also needs to set the virt_driver to a different value now taht the driver is in ironic's tree, not nova's 19:12:08 let's circle back to that in a bit 19:12:16 #topic what got postponed to Juno 19:12:37 a few blueprints got bumped last week 19:12:54 * devananda should have the links handy, but doesn't 19:13:04 windows / whole-disk image support 19:13:14 ipmitool console via shellinaboxd 19:13:22 HP iLO driver 19:13:25 ceilometer integration 19:13:39 19:13:59 devananda: topic question. if people what to continue to work ok blocked (-2'd) patches until J cycle opens can/should they push up new revs or hold off until J is open? 19:14:18 s/work ok/work on/ 19:14:20 NobodyCam: thanks for asking 19:14:35 I encourage folks to continue working on features taht didn't make it in 19:14:41 and pushing patches up if they want to 19:14:52 -2 won't get overridden anyway 19:14:56 I'll try to look now and then, if I see activity 19:15:00 +1 19:15:09 :) 19:15:16 gerrit will carry the -2 forward onto new patch sets, and I'll remove that as soon as Juno development opens 19:15:33 it is in no way a reflection on not wanting the contribution 19:15:42 devananda: thank you for the answer :) 19:15:43 just a matter of time -- we didn't have enough 19:16:14 it looks to me like the whole-disk-image support and ipmitool console support were pretty close 19:16:54 so I'm hoping we can keep those alive and land as soon as juno opens 19:17:10 any questions about postponed work? 19:17:20 when is J opened 19:17:40 #link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule 19:17:49 :) 19:18:05 IMBW, but I believe Juno is opened as soon as RC1 is branched 19:18:13 which would be the last week of March 19:18:45 we then maintain the RC branch for a few weeks and back-port fixes if an only of necessary 19:18:58 before the final reelease is cut ~ april 19th 19:19:29 any more questions? 19:19:54 #topic working towards RC 19:19:57 #link https://launchpad.net/ironic/+milestone/icehouse-rc1 19:20:02 very briefly 19:20:26 if you find or see a bug taht you think is essential to fix *now* 19:20:42 please bring it to the attention of a -core member 19:20:46 and we'll target to RC 19:20:52 that list is tracked at the link abovce 19:21:27 it's also the reference taht the release team has 19:21:28 just fwiw: I'm looking a few issues on Bug #1289048 19:21:38 and they won't release until everything targeted to RC is marked as fix-committed 19:22:02 #topic what to expect in Juno 19:22:29 another real quick point here -- besides the bumped BP's, what we do is largely up to all of you 19:22:36 so please go propose sessions for the design summit :) 19:22:58 devananda: do we have a session on the new deploy agent stuff? 19:23:15 NobodyCam: we haven't proposed any, afaik 19:23:16 would like to sink my teeth in to that :-p 19:23:18 #link http://summit.openstack.org/ 19:23:48 yeah, we'll put one up this week 19:23:57 jroll: awesome :) 19:23:59 NobodyCam, :P yeah we def need a section for that 19:24:05 jroll, nice 19:24:28 it looks like there's no ironic sessions at all right now? 19:24:47 unless there are any process questions about the summit or session proposals, i'd like to open the floor for general discussion soon 19:24:59 jroll: hmm... lemme check 19:25:15 open the gates~ :) 19:25:25 jroll: yea, none proposed yet 19:25:30 #topic open discussion 19:26:02 maybe the guys working on supporting disk image should propouse one, that would be an interesting one 19:26:13 or we can propose it ourselfs if needed 19:27:04 how summit session for Driver architecture for Chassis object ... 19:27:32 seems to me we don't have a good idea of what the chassis is currently doing / needed for 19:28:07 gah/ s/how summit/ how about a summit/ 19:28:20 devananda, regarding devstack, to what value does virt_driver need to be set in localrc? 19:28:37 ifarkas, http://paste.openstack.org/show/73053/ 19:28:38 jroll / JayF - by the summit, you guys will probably have the agent cleaned up a lot. I'd definitely encourage you to spend a few minutes presenting the work you've got and then let folks discuss their needs and see how it all fits together 19:28:50 I also think we should have a session on CI 19:28:52 here's a nova conf file pointing to the nova ironic driver in the ironic tree 19:28:54 both devstack and tripleo 19:29:11 I was thinking from a focus perspective, we'd want to get the agent+driver to fully working prototype state by the summit. 19:29:23 JayF: ++ 19:29:26 With a focus on having something working with ironic to demo at the summit 19:29:32 JayF: ++ :) 19:29:57 agreed :) 19:30:22 I think once we get the non-OS deps out and switch to testr, we'll be focusing on the features needed for finishing a prototype 19:30:47 JayF: expect a lot of interest in collaboration on it 19:30:59 assuming the ironic+devstack patch gets finished up this week, i was planning on starting to put together an etherpad tracking tempest coverage of ironic. what passes, whats busted, whats missing, etc. 19:31:18 adam_g: that is very much needed 19:31:22 adam_g: that would great 19:31:49 lucasagomes, thanks but I asked specifically regarding the localrc because devananda mentioned before that the virt_driver need to be set to something else 19:32:32 ifarkas, ah ack :) I think I missread that 19:32:34 ifarkas: note that scheduler_host_manager and compute_driver both have a prefix of "ironic." now 19:32:37 taht's the change 19:32:53 those classes are now in ironic.nova.* instead of nova.* 19:32:57 ifarkas: i saw your comments on the devstack patch, i will be poking closer at it today. i updated it on friday to set drivers accordingly 19:33:40 adam_g, devananda, cool, thanks 19:33:50 devananda, NobodyCam: http://summit.openstack.org/cfp/details/26 :) 19:34:04 devananda: I'll prob be poking at https://review.openstack.org/#/c/72969 in the next day or so 19:34:17 Add Ironic bits to _undercloud 19:34:38 NobodyCam: great 19:35:41 I think it's time that I did a massive cleanup of our white board :) 19:35:53 lol 19:35:56 #action devananda to clean up https://etherpad.openstack.org/p/IronicWhiteBoard 19:36:23 can we have a etherpad that lists all our etherpads 19:36:27 :-p 19:36:28 hehe 19:36:57 I have 9 open etherpads 19:37:07 https://wiki.openstack.org/wiki/Ironic#Etherpads 19:37:14 doh 19:37:34 a metapad might be better 19:37:36 heh 19:37:50 we could move that to the top of the white board,a nd just link that one from the wiki and IRC channel 19:37:52 I'll add what I have thats not listed 19:38:19 this works for me 19:38:24 devananda, yeah that will be good 19:38:31 was just looking for a place I could point folks to 19:38:34 k, will do after meeting 19:38:56 I see someone added an item to the agenda to talk about IPMI and gathering metrics fro mother devices 19:39:09 I'm not sure what that's about -- there's no link 19:39:37 unless it's a reference to ceilometer work that was abandoned early in icehouse? 19:40:37 devananda: I assue its "oob" metrics 19:40:51 assume even 19:41:13 do we know who added that? 19:41:13 lucasagomes: looks like you made the edit? 19:41:17 ah it was me 19:41:40 it's was more to start a brainstorm about whether ironic should collect metrics from other devices 19:41:45 and pass it to ceilometer 19:42:03 define "other devices" 19:42:26 Haomeng was implementing it for nodes in ironic, I think we mentioned that talking to him at some point 19:42:49 lucasagomes: i think that might change our mission statment. 19:43:07 devananda, any other device that ironic might touch, e.g disk arrays 19:43:16 NobodyCam, yeah I see that 19:43:28 e.g., NICs 19:43:58 lucasagomes: i dont see ironic doing configuration of non-compute resources (eg, SAN, switch, etc) 19:45:00 devananda, ack, but as talked ironic might touch these devices for e.g to update the os image on them 19:45:10 I've talked with a few people about whether or not Ironic could provision them -- right 19:45:18 cinder manages the storage array, but when it comes to provision a new image to it 19:45:21 but ironic's mission ends once the OS is installed 19:45:22 cinder talks to ironic which does it 19:45:29 and pass the control backs to cinder 19:45:33 Ironic can report status of those devices, e.g., link is up or down 19:46:24 wanyen: that might be a good topic for the summit, But see that type of reporting out side of Ironic's current scopr 19:46:26 wanyen: i believe lucasagomes is referring to flashing firmware / updating the operating system on a SAN or Switch, not monitoring individual NICs -- which is, IMO, even further from Ironic's mission statement 19:46:57 lucasagomes: here's the use case AIUI 19:47:04 * user talks to cinder to provision storage 19:47:06 Iwas referring to ceilometer and Ironic integration 19:47:12 * user talks to nova to request compute with that storage attached 19:47:19 devananda, I have a bp passed to me by sjing. it is firmware update. 19:47:20 * nova passes cinder vol info to ironic 19:47:33 * ironic attaches remote storage to hardware 19:47:39 Have you guys discussed it at the Hong Kong summit? 19:47:41 * ironic provisions image on hardware 19:47:42 (hi linggao ) 19:48:04 lucasagomes: so in that ^ I don't see Ironic as ever having touched cinder or the SAN directly 19:48:37 linggao: hi! we talked in HKG, but I think it was somewhat premature and no work has been done on firmware update 19:49:04 devananda, right, hmm yeah that makes sense 19:49:05 linggao: we'll need support for that at some point within the utility agent that JayF and jroll are working on 19:49:36 right sjing told me it depends on the utiliy ramdisk 19:49:38 linggao: and some common modeling in the REST and driver APIs so that firmware update is possible across many drivers 19:49:42 right 19:50:01 linggao: our team will be working on that soon, possibly before atlanta 19:50:30 linggao: do you have a link to the blueprint? 19:50:32 also, for the folks working or interested in that utility ramdisk 19:50:35 jroll, I saw utility-ramdisk bp is already in code-review status 19:50:37 it's not tied to the ironic release cycle 19:50:44 IOW, it's not under feature freeze :) 19:50:49 ^ 19:51:04 linggao: it's in "code review" to become an openstack project 19:51:15 jroll: as soon as you guys can finish the clean up, let's get it into gerrit so others can start collaborating with you guys 19:51:28 linggao: we should have a demo and most basic features available by atlanta 19:51:44 jroll: not that you need any encouragement on taht front ;) 19:51:44 https://review.openstack.org/#/c/79088/ we have it -1'd right now pending getting tests working happily 19:51:44 devananda: +1 19:51:46 but once that is merged we'll be in openstack/gerrit 19:52:00 #link https://review.openstack.org/#/c/79088/ 19:52:08 jroll: did I say that I'd set up the LP stuff for it? or have you guys? 19:52:17 jroll, that would be cool (demo) 19:52:33 devananda: as for the agent driver, my plan is to put up a patch for ironic to upstream it when juno opens 19:52:39 devananda: I'm not sure. JayF? 19:52:40 devananda: I recall hearing that 19:52:42 devananda: I think you said we'd use the ironic project? Although I'm not opposed to having the agent have it's own. 19:53:02 In fact it might make sense to keep it separated, especially if it's not going to be part of FF 19:53:11 different review teams, etc 19:53:19 +1 19:53:24 JayF: ++ 19:53:26 jroll: please put up a patch for the driver around the time that the agent repo is populated in gerrit 19:53:40 devananda: ok, we can do that 19:53:43 jroll, here is the bp https://blueprints.launchpad.net/ironic/+spec/firmware-update 19:53:45 devananda: If that's the route we want to go, I'd ask either to point me at a document telling me how to setup LP for it, or just do it 19:53:48 jroll: i'll promptly -2 it, but i'd still like to have a reference in gerrit :) 19:53:55 devananda: yep :) 19:53:58 thanks :) 19:54:25 jroll: we'll be continuing work on the driver, probably in gh with upstreaming of the patches as they're written, while waiting for juno to open, right? 19:54:26 #action devananda to check with infra re: separate LP thing for the agent, and set it up if needed 19:54:39 JayF: yes 19:54:55 jroll, are you saying your team will work on firmware update or I work on the update using the framework you team is working on? 19:55:04 JayF: we'll just be continually updating the gerrit review for our driver until ironic team is ready to look at it 19:55:04 at the tone there is 5 minutes left... beep 19:55:08 JayF: jroll: even one patch in gerrit with a link to GH would be enough to start -- just a reference point for now 19:55:27 devananda: ok 19:55:40 linggao: It's absolutely on the list of things we want to do. I don't know if that means you should do it now or if we'll get to it first. :) 19:55:52 linggao: if you'd like to work on it, go ahead. If you don't work on it, we will :) 19:56:26 I can see the firmware update being tricky 19:56:40 You're even welcome to submit a PR in via the github repo while we're waiting to get things fixed for it to merge over 19:56:45 #link http://github.com/rackerlabs/teeth-agent 19:56:48 ie if the otherboard only have windows based flashing tools 19:57:15 s/otherboard/motherboard/ 19:57:41 NobodyCam: honestly that hadn't even occurred to me. That could be rough. It'll help that we're doing plugable backends for hardware, so we might implement a sensible one for linux for the prototype, but leave room for folks who need that to implement it 19:58:22 JayF: ya that makes sense to me 19:58:28 right. I know how to do the firmware update for IBM hardware. Have to talk to folks on what is the general way to do it. 19:58:35 JayF: also the driver API for firmware updates will need to support other vendor's drivers which may do updates OOB 19:59:04 a summit session where folks sketch out how to do firmware udpates on different hardware might be good 19:59:15 devananda: ++ 19:59:18 start getting a picture of where the abstraction points are 19:59:21 less then one minute 19:59:22 what a common API will look like 19:59:22 etc 19:59:25 devananda, +1 19:59:33 indeed 19:59:44 we gotta start looking at promoting some methods in the vendor interface to core 19:59:49 lucasagomes: ++ 19:59:58 lucasagomes: want to toss an email to the list with some ideas on that? 20:00:11 lucasagomes: devananda thats a topic for summit track 20:00:12 devananda, yeah 20:00:20 time's up :) 20:00:23 thanks everyone! great meeting 20:00:27 thank you 20:00:28 I can send something to the list 20:00:33 thanks 20:00:36 #endmeeting