19:00:01 #startmeeting Ironic 19:00:02 #chair devananda 19:00:02 Meeting started Mon Jan 13 19:00:01 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:02 Welcome everyone to the Ironic meeting. 19:00:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:00:05 The meeting name has been set to 'ironic' 19:00:06 Current chairs: NobodyCam devananda 19:00:24 Welcome back everyone 19:00:36 who's here for the ironic meeting 19:00:46 o/ 19:00:48 o/ 19:00:51 o/ 19:00:52 * devananda waves from Australia 19:00:52 o/ 19:00:52 \o 19:01:04 o/ 19:01:17 welcome everyone 19:01:30 o/ 19:01:34 o/ 19:01:44 o/ 19:01:53 #topic announcements 19:02:06 Icehouse release progress // graduation? 19:02:17 devananda: is that you? 19:02:36 well. it's all of us :) 19:02:54 :-p 19:03:03 tl;dr - the TC is going to be looking at all the incubated projects this week 19:03:10 to guage progress towards graduation 19:03:21 me:) 19:03:25 particularly to compare everything to the newly-approved guidelines 19:03:41 which, in case folks haven't seen them, are here 19:03:44 #link http://git.openstack.org/cgit/openstack/governance/tree/reference/incubation-integration-requirements 19:03:52 devananda: do you hae a link to the new guidelines? 19:04:00 devananda: nevermind 19:04:02 :) 19:04:39 i also want to remind / inform folks taht we, as a project, need to start being better about how we communicate our plans 19:04:54 which is done by targeting thigns (bugs, BPs, etc) towards releases and milestones 19:05:00 you can see what's targeted here: 19:05:02 #link https://launchpad.net/ironic/icehouse 19:05:03 and 19:05:13 #link https://launchpad.net/ironic/+milestone/icehouse-2 19:05:26 anyone should be able to set the "target" for bugs 19:06:05 with I2 coming up, I'd like to take a few minutes to review the targeted things, particularly BPs 19:06:10 and see if we need to retarget anything 19:07:03 #topic Blueprints for I2 milestone 19:07:16 let's jsut go down the list 19:07:25 dkehn: hi! 19:07:26 devananda: add-neutron-support is it really essential? 19:07:37 devananda: hi 19:07:49 dkehn: you've got a patch up for neutron. is there much more to do? 19:07:56 dkehn: or does it just need testing? 19:08:13 It just needs testing, as you can see 19:08:22 NobodyCam: without neutron support, tripleo won't be able to use ironic. so, IMO, yes. 19:08:34 dkehn: great. want to update the BP status? 19:08:35 devananda: ack 19:08:36 there is more tessting code that actual code, and I ran out of time to complete it all 19:09:02 I will be working on it but this week is the neutron sprint in Montreal 19:09:21 so there will be limited time to complete until I get back 19:09:27 assuming I get back 19:09:34 thats it 19:09:42 dkehn: taht's fine. I'll set it to "needs testing" :) 19:09:49 err, "needs code review", i mean 19:09:59 k 19:10:14 PXE driver BP... 19:10:20 has no one assigned. 19:10:30 that one landed long ago, but we're all jsut now testing it 19:10:37 devananda: I'll get it out of WIP then 19:10:53 anyone want to take point on that BP? GheRivero ? NobodyCam ? 19:11:05 I can take it 19:11:16 GheRivero: thanks 19:11:17 :0 faster then I 19:12:21 romcheg: around? 19:12:30 devananda: yup 19:12:33 devananda: we'll need to get the "get service url" working for that 19:12:37 sunjing: around? 19:13:00 romcheg: I think the "intelligent routing for RPC" BP is superceded by my consistent hash BP. what do you think? 19:13:17 jing is not around i think 19:13:22 I think we discussed that already :) 19:13:27 I agree with you 19:13:30 romcheg: k :) I'll close that BP 19:13:35 I will have something about "get service url" soon 19:13:46 GheRivero: W00t 19:13:47 devananda: thanks 19:13:49 :) 19:13:57 I'm also fixing the ironic-rootwrap 19:14:00 couple of problems with it 19:14:06 https://bugs.launchpad.net/ironic/+bug/1268696 19:14:06 GheRivero: great! I saw some discussion in channel about it 19:14:09 Launchpad bug 1268696 in ironic "On Ubuntu: /usr/local/bin/ironic-rootwrap: Executable not found: /sbin/iscsiadm" [Undecided,In progress] 19:14:10 https://bugs.launchpad.net/ironic/+bug/1268674 19:14:13 Launchpad bug 1268674 in ironic "ironic-rootwrap: No section: 'Filters'" [Undecided,In progress] 19:14:26 that's needed for pxe 19:14:46 lucasagomes: was that the reviews you just put up? 19:14:54 NobodyCam, yes 19:15:04 :) will look at after meeting 19:15:05 there's one more needed but on devstack 19:15:06 lucasagomes: ahh. IIRC, that has a different path 19:15:19 lucasagomes: don't forget to specify the milestone on those bugs :-) 19:15:29 rloo, +1 19:15:41 :) 19:16:21 devananda, I can try to answer your questions for sun jing for relate them to her. 19:16:28 devananda, yup it does... but as nova also does not use absolute paths on the filters 19:16:37 linggao: hi! 19:16:37 I think we might want to go with the same approach 19:16:45 hi 19:17:04 linggao: how's progress on the "use ipmitool for serial console" work? I've seen a patch up but haven't had time to test it yet 19:17:14 linggao: is that patch a complete implementation, or is there mroe to do? 19:18:13 lucasagomes: could you also set importance for your bugs? 19:18:18 devananda, from the conversation I had with her last wek, she has put the implementation for serial console using ipmitool in the patch. 19:18:30 devananda, +1 yes 19:19:16 lucasagomes: i trust that you can guage the importance of a bug -- and really, most of us should be able to triage bugs now :) 19:19:26 linggao: great! 19:19:31 linggao: i'll update teh BP 19:19:32 devanandan, she was going to change it to use the Console interface to start or stop the condole instead of puting them in the power on/off funcitions like nova did 19:19:44 but I am not sure they check that code in or not. 19:19:50 linggao: never mind -- nothing to update. it already has the right status :) 19:20:08 linggao: ah. it should indeed use the console interface now 19:20:17 sounds like it may not be complete by I2 then 19:20:22 devananda, right :) yea I need to take a better look at our bug list. I fixed the ones assigned to me awhile ago. 19:20:46 the to-do for that BP is to implement the console interface usng the ipminative, that will be done after icehouse 19:21:15 linggao: that's fine 19:21:32 ok, i'd like to move on, so we dont spend the whole meeting on BP's 19:21:37 thanks everyone :) 19:21:40 devananda: do the seamicro bp need to me tagged as i2 19:21:45 ok 19:22:06 NobodyCam: let's talk about the seamicro BPs in a bit 19:22:11 ack 19:22:12 they were jsut proposed a few days ago 19:22:26 #topic Tempest API tests 19:22:31 devananda, i will try to triage some bugs 19:22:42 I want to thank romcheg for all the work he did on this 19:22:45 I have exciting news about the test 19:23:04 But everyone already knows them :) 19:23:13 :) 19:23:17 :) 19:23:21 romcheg: hehe, but please, say it anyway :) 19:23:26 ok 19:23:30 great ;) 19:23:38 So everything got merged 19:24:00 awesome romcheg 19:24:06 good stuff :) 19:24:09 Tempest tests can be manually triggered for every ironic patch by leaving "check experimental" on review 19:24:09 congrats! 19:24:20 also, we will soon have tempest API checks in our gate, once this lands 19:24:23 #link https://review.openstack.org/#/c/65845/ 19:24:40 so every patch to Ironic will spin up devstack. expect jenkins to become slower ... 19:24:52 ieek 19:24:59 the same tests will also run for every tempest and devstack patch -- but in non-voting mode 19:25:34 inclouding pxe_ssh driver? 19:25:49 haomeng2: right now, this is only for exercising our API 19:26:02 ok got 19:26:05 it's an integration test -- make sure all the components of Ironic integrate with each other 19:26:06 haomeng2: agordeev1 is working on that 19:26:17 ok 19:26:24 functional test (can it actually DO a deployment) is being worked on still 19:26:31 I'm trying to help them since I got more familiar with infra 19:26:36 i'm hoping we haev that by I3 milestone 19:27:05 #topic Nova driver 19:27:25 NobodyCam: that's you - any announcements? besides how awesome it is? :) 19:27:33 :) I need to actually start writing tests 19:27:39 lol 19:27:42 heh 19:27:44 its getting there 19:28:10 i had a brief chat with a few nova folks at LCA -- as I thought, we'll need to split the patch up for it to land 19:28:19 still 100% but I think we worked out a way to map the drivers requirments so nova will know what each driver needs 19:28:29 oh ya 19:28:32 nice 19:28:41 nice 19:28:51 the full review is up at 19:28:57 would be that something that we might want our drivers to say as well? 19:28:58 looks for link 19:29:15 #link https://review.openstack.org/#/c/51328/ 19:29:18 lucasagomes: you mean in our /drivers/ api? 19:29:26 for example, by GET /drivers, would also return a list of the mandatory parameters 19:29:32 with an description etc 19:29:34 devananda, yes 19:29:35 lucasagomes: i think we talked about that early on. Yea, eventually I think they should 19:30:04 lucasagomes: yes I would like to make that dynamic 19:30:07 ah right, yea that would be very useful 19:30:29 lucasagomes: so that other clients can retrieve said list, then populate driver_info, then call validate to see if they got everything 19:30:37 but the good news is we are acryally calling deploy from the driver 19:30:55 lucasagomes: but nova will still need some static mapping there, I expect 19:31:41 I am would like feedback on the mapping and anyother bit of the driver 19:32:01 NobodyCam: one thing on building that review into a dib image that I learned last week 19:32:21 NobodyCam: you can tell dib to pull in a patch/rev via env vars now 19:32:23 just set this 19:32:30 export DIB_REPOLOCATION_nova=https://review.openstack.org/openstack/nova 19:32:33 export DIB_REPOREF_nova=refs/changes/28/51328/8 19:32:36 right, maybe having a bug ticket to implement that ( wishlist ) would be great, I can file that later 19:32:40 awesome 19:32:43 instead of hard-coding it in your element install script 19:32:51 lucasagomes: ++ 19:33:54 devananda: I can look at refactoring the element i have up in my repo 19:34:19 or I saw you may have started a new one 19:35:32 devananda: just dropped 19:36:01 are there anyquestions on the nova driver 19:36:11 * devananda switches to cellular 19:36:45 #topic functional testing 19:36:58 just a quick note here - i'll be talking with agordeev1 later today about this 19:37:06 and romcheg hopefully, too 19:37:18 +1 19:37:39 functional testing is a requirement for graduation, and we should have it in our gate ASAP. certainly no later than I3 19:37:55 #topic tripleo integration 19:38:03 again, just a quick note - 19:38:24 i think we can simplify the current walkthrough in our wiki 19:38:47 and merge most of that up into tripleo at this point 19:39:03 in fact, we will need to at some point have tripleo support both baremetal and ironic in parallel 19:39:08 with an ENV var to toggle it 19:39:14 so that folks using tripleo can migrate 19:39:43 NobodyCam: you've been maintaining that mostly, so once i'm back in the states, let's hash those changes out 19:39:55 devananda: I have had a hard time in the past getting env var thru the oOo revirew processs 19:40:07 devananda: ack 19:40:16 with 20 minutes left... 19:40:24 #topic SeaMicro proposals 19:40:42 Hi folks 19:40:47 Rohan here 19:40:49 hi! 19:40:54 Hi! 19:40:55 hi rohan 19:41:19 Seamicro is proposing ironic drivers for its products 19:41:21 k4n0: do you think you can have all that by i2 19:41:30 yes 19:41:44 working very hard on that 19:42:32 k4n0: i just saw your reply on the BP regarding the seamicro client lib 19:42:56 devananda: yes, does that sound ok? 19:43:00 k4n0: good stuff! I'm thrilled to see support for seamicro getting added 19:43:07 k4n0: yep, sounds fine 19:43:13 # link https://blueprints.launchpad.net/ironic/+spec/seamicro-power-driver 19:43:35 we will need talk about functional testing of drivers though 19:43:43 right 19:43:52 also: 19:43:56 #link https://blueprints.launchpad.net/ironic/+spec/seamicro-vendor-passthru-interface-implementation 19:44:18 k4n0: we (will) have the same requirement that Nova does -- all third-party drivers need functional testing on real hardware 19:44:26 Regarding to testing: I think we will have to chose the neutron's ways 19:44:35 k4n0: tripleo has been working on some specifications for how folks contribute it 19:44:46 * devananda looks for the link 19:44:52 romcheg: what do you mean exactly? 19:45:00 When vendors set up their own environment which is open for OpenStack CI 19:45:09 neutron has had a lot of difficulties in the past, but working on improving it... 19:45:28 Then we'll be able to run TripleO's periodic tasks againts that hardware 19:46:04 devananda: are the requirments for the hardware venders need to put up? 19:46:16 that would be helpful 19:47:46 NobodyCam: i haven't written them up specifically yet (on my list...) 19:48:06 but lifeless has written it up for tripleo, and I'd like to point fokls to that for the time being 19:48:17 will do 19:48:50 k4n0: broadly speaking, there are two kidns of testing which jenkins can support 19:48:53 voting and non-voting 19:49:14 infra has very strict requirements on things which can vote in the gate, since that will affect ALL projects 19:49:48 right, so where do the third party functional tests go? 19:49:49 we're still discussing exactly where in the matrix of possible tests vendor drivers need to fit for ironic 19:49:53 right :) 19:49:57 :) 19:49:58 ok 19:50:05 my current view is that it's the intersection of 19:50:10 *somewhere near the 19:50:13 something like turbo-hipster? 19:50:30 check + gate for all patches in Ironic 19:51:06 devananda: wouldn't that be too expensive for vendors? 19:51:31 romcheg: how else can we know taht some patch doesn't break support for that vendor? 19:51:54 romcheg: how else do we prevent regressions and ensure support for the things which are landed in trunk? 19:52:17 devananda: there's no other way I think :( 19:52:30 k4n0: what do you think? 19:52:47 k4n0: will you guys be able to test, at a minimum, all patches to ironic (both check and gate pipelines) 19:53:08 I think so, will need to check on this 19:53:16 ignoring for the moment that we're still working out bugs in our deploy process, and dont have functional tests written into devstack :) 19:53:32 Does neutron do the same? 19:53:41 k4n0: neutron is moving towards this model 19:53:54 k4n0: and nova is kicking out all the drivers which aren't doing this 19:54:02 :) ok, i can talk to my folks, get back to you on this 19:54:19 thanks :) 19:54:31 k4n0: any other questions for us? 19:55:14 we can get the blueprints in after i2 right? 19:55:29 i mean, do we have to wait till i3? 19:55:37 i was thinking maybe we should tag as i3 for now 19:56:12 k4n0: targeting a BP is just a way of communicating expectations 19:56:14 they can ofc land sooner 19:56:26 ok, we will try to finish sooner 19:56:37 i2 is good for now 19:57:01 k4n0: i'm fine with it targetted to i3 19:57:19 ok 19:57:40 k4n0: oh! also, here's the link for tripleo's requirements for additional regions -- not goign to be exactly the same as ours, but may be worth reading, particularly if you gys are also looking at tripleo support 19:57:44 #link https://wiki.openstack.org/wiki/TripleO/TripleOCloud/Regions 19:58:00 devananda: thanks ! 19:58:11 I am done with my questions 19:58:24 and we have two minutes 19:58:31 :) 19:58:34 thank you everyone, I will try to hang around every meeting :) 19:58:35 #topic open discussion 19:58:52 k4n0: great also hang out in channel too 19:58:55 k4n0: please join us in #openstack-ironic too 19:59:03 as for race condition problem 19:59:05 ohh cool, didnt know that channel 19:59:09 there are 3 links in agenda 19:59:13 k4n0: and thanks again -- I'm really thrilled to see SeaMicro contributing :) 19:59:14 #link https://bugs.launchpad.net/ironic/+bug/1259910 19:59:15 Launchpad bug 1259910 in ironic "race condition when changing node states" [Medium,In progress] 19:59:22 devananda: +1 19:59:33 I don't think we have time to talk about the race condition (1min left) 19:59:34 max_lobur: you put up a 19:59:37 poc today? 19:59:39 on that 19:59:50 devananda, could you take a look at that bug ticket when u get some free time? 19:59:55 lucasagomes: will do 20:00:02 NobodyCam, he did already 20:00:11 there's one patch fixing it using the thread approach 20:00:13 hae the link for the log 20:00:27 :) 20:00:27 lucasagomes: let's discuss the bug back in channel though 20:00:34 #link https://review.openstack.org/#/c/66368 20:00:35 + 20:00:38 great meeting every one 20:00:41 thanks everyone! 20:00:44 ty lucasagomes 20:00:45 thanks 20:00:47 :) 20:00:47 thanks! 20:00:50 thanks 20:00:52 tks 20:00:55 thanks 20:01:00 #endmeeting