19:02:14 #startmeeting ironic 19:02:15 Meeting started Mon Jun 3 19:02:14 2013 UTC. The chair is devananda. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:02:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:02:18 The meeting name has been set to 'ironic' 19:02:20 romcheg: wow must be getting late in your neck of the woods 19:02:36 so, agenda for the meeting is, as usual, in the wiki 19:02:43 #topic documentation 19:02:52 first an announcement -- our docs are live and auto built now 19:02:58 \o/ 19:02:58 #link http://docs.openstack.org/developer/ironic/index.html 19:03:13 martyntaylor: yup. Trying to combine meeting and sushi ;) 19:03:18 nice 19:03:34 there's a bug in PBR that is breaking the auto doc parts currently 19:03:36 #link https://bugs.launchpad.net/ironic/+bug/1186834 19:03:37 Launchpad bug 1186834 in pbr "auto-docs build incorrectly with pbr <= 0.5.11" [Undecided,New] 19:03:38 lovely 19:03:45 woot 19:04:03 not enough system architecutre pictures, haha 19:04:04 very nice docs.. +1 to all who had a hand in making them so nice 19:04:14 but please start trying to write good inline docs, and comment on reviews if they lack docs :) 19:04:29 as soon as mordred tags another PBR release, we should have autodocs :) 19:04:36 cool 19:04:46 any questions on docs? 19:05:26 harlowja: yea, we need architecture / diagrams ... 19:05:30 ;) 19:05:43 ok, moving on kinda quickly 19:05:47 #topic meetup? 19:05:56 yes 19:05:57 i raised the question informally last week 19:06:08 where? 19:06:13 should we try to ge tothether and hack / sort things out / etc? 19:06:17 and if so, whena nd wehere? 19:06:27 hmmm 19:06:29 should we? yes 19:06:53 ideas so far are NYC and Amsterdam 19:06:56 I'll be arranging a location for the CI bootcamp June 27/28 in NYC 19:07:14 we obviously can't share hte same room - but overall logistics could theoretically be shared 19:07:22 +1 for Amsterdam 19:07:33 +1 for hawaii 19:07:34 I would love to do a boot camp with CI 19:07:53 didn't know that was a possibility 19:08:04 i'd like to to be ;) 19:08:11 *it to be 19:08:13 would be like going to the emerald city 19:08:36 emerald city eaiset for /me 19:08:37 hawaii! 19:08:41 harlowja: we have a good group from EU that i would like to include, so hawaii is probably not going to work ... 19:08:49 ah, durn 19:09:21 im in europe and dont care about haeaii:) 19:09:45 martyntaylor: since you're taking on a lot of the API stuff, i would like to see you included 19:09:50 so far romcheg likes Amsterdam, I would like NY and no one else has identified they would like to attend 19:10:11 I'm in Ukraine and getting a visa to the US is a pain for me :) 19:10:18 romcheg: I hear that 19:10:42 mordred: any change CI would boot camp in Amsterdam? 19:10:43 harlowja: what's the likelyhood of you making it to NYC for a couple days? 19:10:47 no 19:10:50 hmmmm 19:10:54 mordred: had to ask 19:10:59 anteaya: fair. :) 19:11:00 not so likely, but i can try to ask 19:11:08 anteaya: we're doing NYC because I'm sick of travel 19:11:13 devananda: I'll certainly ask about it, I would imagine Amsterdamn would be a lot easier to justify 19:11:17 mordred: hah! you? 19:11:22 mordred: ah yes, that is well understood 19:11:23 devananda: :) 19:11:34 devananda let me get back to u on that 19:11:46 martyntaylor: k, please let me know. 19:12:10 martyntaylor: also, iirc, jayg is east-coast-US, so if you couldn' tmake it to NYC, could jayg? 19:12:19 can we do a show of hands of who is considering attending? 19:12:27 o/ 19:12:36 actually 19:12:41 let's break this in half 19:12:51 show of hands for those who could attend US east coast 19:12:54 \o 19:12:58 \o 19:13:06 * NobodyCam could 19:13:44 anyone else? 19:13:48 not much of a boot camp with just 3 of us 19:14:10 I'd still like to meet you though NobodyCam 19:14:14 devananda: quite possib ly 19:14:42 ok, thanks 19:14:49 show of hands for those who could attend amsterdam? 19:14:50 \o 19:15:08 \o 19:15:14 * NobodyCam could also 19:16:17 \o 19:16:25 hi 19:16:32 it seems that, besides myself and NobodyCam and gherivero, we have 1 definite for NYC and 2 definite for Amsterdam 19:16:35 dprince: hi! 19:16:35 19:16:47 o/ sorry i'm late 19:17:34 mordred: is this the same bootcamp as the infra stuff? 19:17:44 lifeless: are you saying hello or is your hand in the air saying you could attend an ironic bootcamp in Amsterdam? 19:18:20 dprince: we're discussing having an overlapping ironic bootcamp in NYC 19:18:25 dprince: I was suggesting that we potentially co-locate infra bootcamp and ironic meeting - as arranging space for two meetings is about the same effort as for one 19:18:42 ++ sounds like a wonderful idea 19:19:15 mordred: if I can't attend the ironic bootcamp can I crash the CI one? 19:19:19 anteaya: bit of column a, bit of column b. My travel stuff is weird :) 19:19:36 lifeless: very good 19:20:21 so maybe lifeless for Amsterdam 19:21:18 so as much as I'd like to accomodate everyone, it seems like NYC is simpler 19:21:23 and can get enough folks 19:21:43 if we can get jayg there, that'll cover the API side 19:21:51 romcheg: is applying for a VISA a possibility? 19:22:19 It is. Not sure if I can get a visa in time 19:22:29 understood 19:22:36 they don't make it easy 19:22:59 mordred: is that ^ something you or the foundation could help with, and in time? 19:23:04 When exactly do you plan to meet up? 19:23:23 IIRC, June 27 - 29 are the CI bootcamp dates 19:23:24 jayg: we are talking about a potential meetup 19:23:28 romcheg: another time, how much advance notice to you need in order to apply for a VISA? 19:23:34 devananda: if we're talking visas, probably no 19:23:36 jayg: in NYC 19:23:43 mordred: ack :( 19:23:44 devananda: BUT - it's always worth asking the foundatoin about it 19:24:00 jayg: not sure if you can make it? 19:24:05 let me know if you want me to start a thread 19:24:10 devananda: if not we could always do a hangout or something similar 19:24:24 hangout would likely work better for me 19:24:41 you do realize they redesigned the hangouts 19:24:51 rendering them unusable for my needs 19:24:51 so we can also do hangouts any time 19:25:21 anteaya: unusable how? 19:25:25 I can make a webex meeting if that is helpful. 19:25:30 you have to be signed on to google+ to receive the call 19:25:33 like skype 19:25:46 I used to be able to start an empty hangout and share the url 19:26:04 so the async factor has been sharply reduced from what I can see 19:26:06 * jayg has never used a hangout w/o being signed in, didnt realize it was not always like that 19:26:27 so perhaps I am the only one who noticed a difference 19:26:41 we are sidetracking 19:26:42 so, i think we've side tracked - i'm happy to webex or hangout to knowledge share, but let's take that up after the meeting :) 19:27:06 anteaya: 2 months. But I will ask the embassy about urgent visas 19:27:14 i'm going to go forward with plans for crashing infra's bootcamp, and let's all try to get there if we can 19:27:16 romcheg: okay, thanks 19:27:24 yay 19:27:28 and let's try to capture what we do for thsoe who can't make it 19:27:32 yes 19:27:48 moving on 19:27:53 since there are a few more big things to talk about 19:28:01 #topic stuff in progress 19:28:12 we have a whole bunch of new BPs :) 19:28:18 some big, some small 19:28:27 mostly i want to call out these 4 areas of work 19:28:30 - DB object model 19:28:35 - API & RPC implementation 19:28:40 - image utils refactoring from nova/cinder 19:28:42 - PXE driver 19:28:58 as outstanding things before Ironic becomes minimally functional 19:29:25 martyntaylor seems to have a handle on the API parts 19:29:43 anything you'd like to say? questions, comments, etc? 19:30:00 devananda: we are blocked on the db model object 19:30:10 I am keen to work on that 19:30:13 ah, i see 19:30:20 romcheg: on the api, or the db object model? 19:30:29 Object model 19:30:45 romcheg: great. dansmith implemented this in Nova -- feel free to port his work to Ironic 19:30:46 we can still play around with the other things, like adding routes etc... but really we can't make a great deal of process until we get that piece 19:31:07 once that is done, there is a ton of stuff that can be done in parrallel 19:31:11 ok 19:31:19 so actually, i can probably port that in a day or less. 19:31:22 devananda: was about to start working on that 19:31:49 o/ i'm back 19:31:49 i also have plenty else to do :) 19:32:01 romcheg: so please post your work to gerrit early, so we can iterate quickly and unblock martyntaylor 19:32:15 #action romcheg to port db object model 19:32:21 Ok 19:32:29 other than that 19:32:59 I hope I've broken down the work load into sizable chunks so much so that if anyone has any free cycles they can pick up the odd task here and there 19:33:29 martyntaylor: i'm going to go through today and condense those blueprints... 19:33:40 for reference, a blueprint doesn't have to be assigned to you for you to work on it 19:33:49 eg, one BP could encompass multiple "work items" 19:34:14 devananda: ah sure 19:34:14 it just indicates who is the primary contact for that work 19:34:17 I see 19:34:47 my appologies my launchpad skills are not up to scratch, I'm more used to things like Redmine and JIRA 19:34:52 so if others want to work on the API, at this point, they should probably be talking to you regardless of what BP they have assigned to them (or not) 19:34:57 sure 19:35:14 martyntaylor: no worries :) it's a different tool, and has its limitations ... 19:35:23 GheRivero: niec work on the glance image utils. any estimation of how much more there is to do? 19:35:32 NYC and amsterdam are about equal for me 19:36:02 1 or 2 days top if everything goes smoothly 19:36:07 awesome! 19:36:34 so after that, i'll start helping with the PXE driver work 19:37:01 any more questions/comments about the open blueprints, ongoing work, etc, before I move on? 19:37:24 looking for reviews on https://review.openstack.org/#/c/30935/ 19:38:23 ok, moving on 19:38:28 #topic task flows 19:38:39 so, this bears a little explanation before we discuss 19:38:45 #link https://etherpad.openstack.org/ironic_driver_api 19:39:02 i jotted down some (lengthy) notes about the issue 19:39:15 workflows, nice 19:39:16 tl;dr is that the nova baremetal driver implemented 2 types of "sub drivers" 19:39:20 power and deployment 19:39:32 i followed that model when laying out the skeleton for ironic 19:39:48 but it's looking pretty clear that it doesn't address the needs of most vendor-extensions 19:40:31 what vendor-extentions does nova bare-metal drivers support now? 19:40:37 anteaya: none 19:40:40 s/driver/drivers 19:40:40 interesting 19:41:17 another approach that may work better is to use workflows 19:41:21 *really likes how this workflow stuff is being thought ahead of time :) 19:41:30 *thought about* 19:41:42 devananda thx u thx u 19:42:15 harlowja: well, there's a good idea under here 19:42:40 def 19:42:46 i dont like complicating ironic more than is necessary, but we also need to support different work flows for all the things 19:43:06 agreed 19:43:06 changing the RAID config with IPMI+PXE will be a radically different workflow than doing the same thing with iLO or DRAC 19:43:29 19:43:36 19:43:37 the current approach of putting that logic inside the ManagerService, calling down to the drivers via the current API, doesn't seem to work 19:43:54 because the assumption taht different drivers will follow the same work flow is flawed 19:43:57 they wont 19:44:20 deploying an image via iLO doesn't require 2 reboots, for example 19:44:27 that's a pretty significant difference 19:44:43 that shouldn't be exposed outside of the Ironic API, at least not in my opinion 19:44:49 ya, its a nice ideal to have (the one api ideal) but i agree that its never really reality 19:45:12 lifeless: i imagine you'll also have thoughts on all this (if you're around) 19:45:56 harlowja: i dont think the API clients should need to do different things depending on the driver that Ironic is using 19:46:12 harlowja: that'd be like expecting nova clients to send different commands for Xen vs. libvirt :) 19:46:15 agreed, its internal to ironic, which is fine, but has to be flexible in ironic 19:46:21 yea 19:46:56 and that begs the question of how flexible, haha 19:47:08 devananda: I am; sec - catching up 19:47:31 harlowja: so my idea is roughly sketched at the end of that etherpad 19:47:51 workflows are created for known sets of drivers 19:47:56 ya, can u describe the weighting stuff 19:48:12 devananda: I had assumed that the deploy driver would take a ref to the power driver instance. 19:48:25 lifeless: yes, it does that today 19:48:26 devananda: and so could do whatever it wanted, whether thats one power on or three. 19:48:42 devananda: or vendor specific can just do $whatever and ignore the power driver 19:49:42 lifeless: current model doesn't seem to work if one driver does it all (eg, iLO) 19:50:42 devananda: At a guess, that means you don't have enough control passed to the driver 19:50:58 devananda: the workflow thing might be good, but it seems orthogonal to thise specific point? 19:51:49 harlowja: idea about weights: each Driver's pubic method can be queried whether it can act on a given Node (ie, if it's got all the configuration, and whether current state prevents it) 19:52:17 hmmm, don't call that method, haha 19:52:44 and if multiple drivers happen to both be capable, manager picks the "best" one 19:52:54 eg, PXE driver requires reboot to do $foo, but iLO doesn't 19:53:09 kk, makes sense 19:53:12 devananda: So, I need to see code where this is a problem. 19:53:19 devananda: I don't understand why it matters at all 19:53:46 lifeless: at the manager level, "deploy this image" is 19:54:04 control_driver.prepare 19:54:09 power_driver.boot 19:54:14 control_driver.deploy 19:54:26 power_driver.reboot 19:54:38 19:54:43 devananda, huh? why would you use power_driver to reboot after deploy? 19:54:51 devananda, wouldn't the deploy just do reboot internally? 19:55:02 5 minute warrning bell 19:55:03 jbjohnso: it does that today, actually, but we ran into an issue with some HW 19:55:18 jbjohnso: reboot from in-ramdisk occasionally got stuck.... 19:55:23 devananda, reboot -f? 19:55:28 :) 19:55:28 devananda, or reboot? 19:55:33 devananda, not kidding, fyi 19:55:36 not sure atm 19:55:45 devananda, we went to 'reboot -f' 19:55:56 devananda, which resolved a lot of weirdness in corner cases 19:55:58 so the same thing applies to "set this BIOS setting" 19:56:14 PXE driver must: prepare. reboot. deploy special ramdisk. unprepare. 19:56:21 iLO driver would just: send message to iLO 19:56:42 devananda: so I'm saying at the manager level it shoudl be 19:56:57 devananda: control_driver.deply(image_ref, node_ref, power_driver_instance) 19:57:00 devananda: -done- 19:57:03 yea 19:57:10 devananda: and that your problem is you are violating the control driver abstraction today. 19:57:20 devananda: for which the fix is simple :). 19:57:27 devananda: now, you'll tell me why I'm wrong! 19:57:41 perhaps after your meeting :) 19:57:57 let's continue this in #-ironic if fokls want to 19:58:02 #topic open discussion 19:58:05 we have 2 minutes left :) 19:58:09 tick tock :> 19:59:00 so maybe more writeup will help here :) 19:59:05 and maybe some small code examples? 19:59:29 possibly 19:59:35 i'll add stuff to the etherpad 19:59:40 thanks everyone! 19:59:46 #endmeeting