05:00:19 #startmeeting ironic 05:00:20 Meeting started Tue May 12 05:00:19 2015 UTC and is due to finish in 60 minutes. The chair is devananda. Information about MeetBot at http://wiki.debian.org/MeetBot. 05:00:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 05:00:23 The meeting name has been set to 'ironic' 05:00:43 good evening/morning/afternoon! 05:00:47 o/ 05:00:55 o/ 05:01:00 o/ 05:01:04 as usual, the agenda is posted on the wiki, here 05:01:06 o/ 05:01:08 #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting 05:01:11 o/ 05:01:15 o/ 05:01:42 #topic announcements 05:01:47 o/ 05:02:10 hm... seems like folks are still trickling in. I'll give it another minute 05:03:08 presumably, everyone is gearing up for the summit next week 05:03:31 +1 05:03:40 +1 05:03:49 There's a summit next week?!? 05:03:51 :-P 05:03:52 in light of that, BadCub is trying to arrange a dinner and has asked folks to respond on the summit etherpad 05:03:55 mrda: :P 05:04:26 #link https://etherpad.openstack.org/p/liberty-ironic-design-summit-ideas 05:04:31 if you'll be there and think you might want to attend an ironic team dinner, please see "IRONC DINNER" section of https://etherpad.openstack.org/p/liberty-ironic-design-summit-ideas 05:05:01 also, though I didn't put it on the agenda as it just came up today 05:05:02 devananda: I will not attend next summit 05:05:18 the discussion of our meeting times was raised this morning (well, my morning) 05:05:34 so I started a poll and would like to get everyone's responses 05:05:38 devananda; will you attend the dinner? 05:05:40 #link http://lists.openstack.org/pipermail/openstack-dev/2015-May/063818.html 05:05:47 #link http://goo.gl/forms/nvbWdOZMFY 05:06:02 pshige: depending on when it is -- I'll certainly try. 05:06:30 that's it for my announcements (we'll talk about summit specifics in a bit) 05:06:31 monday evening? 05:06:39 * mrda has already responded to the meetings discussion 05:06:47 #topic subteam status reports 05:07:18 I do not see any updates on the subteam status report section of the etherpad 05:07:35 devananda: I updated iRMC status 05:07:36 giving a few minutes if anyone here has updates ... otherwise, I'm happy to skip this 05:07:49 devananda: please find it 05:07:51 naohirot: oh! how did I miss that 05:08:05 devananda: :) 05:08:42 #info iRMC vmedia deploy driver status: code is up for review 05:08:57 devananda: I won't attend to vancuver, so please check if iRMC direction is okay or not 05:09:00 devananda: regarding ilo driver 3rd party ci, we are almost done with all hp-internal stuffs for enabling it (need to complete it before enabling it) 05:09:18 naohirot: if you have links to the review(s), please put them on the etherpad. 05:09:28 devananda: sure! 05:09:29 but still some minor things left so likely will complete it before summit 05:09:32 naohirot: easy way to do that is to make sure all the reviews have the same "topic" and then post a link to that search 05:09:46 rameshg87: fantastic 05:10:14 #info iLO 3rd party CI making good progress and might be done by the summit 05:10:36 devananda: okay, I try to device gerrit search URL somehow 05:10:48 lintan: oh - since you're here, I tested the AMT driver today and found a bug -- https://bugs.launchpad.net/ironic/+bug/1454018 05:10:48 Launchpad bug 1454018 in Ironic "AMT driver fails on set-boot-device" [Medium,Triaged] 05:11:56 going to do the next section out of order 05:12:07 #topic Nova virt driver for Ironic 05:12:35 mikal raised an email last week re: how many open bugs we have in the nova.virt.ironic driver 05:12:45 OK, I will have a look at it 05:12:47 and yea, i think we haven't been paying enough attention to it 05:13:02 So I know that jlvillal has volunteered to look after this, but I'm also willing to keep an eye on it. 05:13:17 jlvillal seems to have volunteered to be our liaison for it -- 05:13:31 I will be attending the Nova meeting on Thursday. 05:13:34 mrda: awesome, and yea, you have some experience in that code already ;) 05:13:37 since mikal will bug me, and since I go the original code merged 05:13:39 yeah 05:13:49 thank you both 05:13:50 mrda, More help sounds good to me 05:14:07 So I might attend the alt meeting jlvillal, if you want to take the main one 05:14:17 then we cover all the meetings \o/ 05:14:32 please don't hesitate to poke me about things. A lot of that is originally my code, too, and some of the bugs are actually pretty serious (and old) 05:14:41 *about the nova virt driver things 05:14:45 devananda: no worries there 05:14:49 mrda, Okay on meetings. I will try to attend both. 05:14:50 we will bug you :P 05:15:18 #info jlvillal and mrda volunteered to tag-team the nova meetings so we'll have better coverage of nova bugs moving forward 05:15:39 any other comments/question on that before moving on? 05:15:49 I am also hoping that having a better relationship will help us get code merged in faster. 05:15:58 jlvillal: ++ 05:16:03 We sometimes seem to have difficulty getting reviews when we do post patches. 05:16:46 something for us to work on improving, indeed 05:17:22 #topic stable branch of python-ironicclient 05:17:31 rloo posted this question, but she's not here 05:18:19 she's asked me about the patches which have been posted to stable/kilo of python-ironicclient and this is what I've previously explained 05:18:23 but it's good to put it in a meeting 05:18:33 #info The purpose of the stable/kilo branch on the client is to lock down dependencies for CI testing of the stable/kilo branch of the server - not limit functionality. It's not a separate release that we expect users to consume. 05:19:08 I'm happy to discuss now if it's not already clear to folks :) 05:20:02 ... ok, moving on 05:20:06 #topic summit planning 05:20:08 devananda: so in simple words, we won't backport things to stable/* branch, right ? 05:20:14 #undo 05:20:15 Removing item from minutes: 05:20:33 rameshg87: for the client - that is my understanding, yes 05:20:40 okay 05:20:51 #topic summit planning 05:21:02 two big things to call out 05:21:33 #info Neutron is having a session on ML2 extension for bare metal -- specifically for ML2 extension authors 05:22:02 #info Ironic is *also* having a session on ML2 extensions, but more specifically for the ironic<->neutron<->nova integration 05:22:29 do you have the titles handy? 05:22:37 there really wont be titles 05:22:45 oh 05:23:19 working sessions will all have a single title: "$project: work session" 05:23:56 * naohirot rloo is lady, I didn't know that :) 05:24:28 devananda: do you know when neutron will discuss this 05:24:30 ? 05:24:42 Wednesday May 20, 2015 4:30pm - 5:10pm 05:24:43 https://etherpad.openstack.org/p/YVR-neutron-ironic 05:24:50 cool, thnx 05:25:03 * rameshg87 wonders what YVR stands for 05:25:12 Vancouver airport 05:25:14 rameshg87: that's the airport code for Vancouver :) 05:25:18 oh :) 05:25:38 also, cinder is having a discussion about our integration there -- Wednesday, May 20 • 5:20pm - 6:00pm 05:26:16 devananda: anything about better horizon integration ? 05:26:17 we haven't gotten a track with Nova to discuss the virt driver, or (lack of) HA Nova compute 05:26:30 so as it stands now, we'll be hosting that 05:26:55 rameshg87: nothing afaik -- however, krotscheck has been working on some JS UI work for us which he might be able to show 05:27:00 we should all go to that session > neutron,cinder 05:27:22 and JoshNang too i saw somewhere 05:28:18 take a look at the top of the summit pad -- there are links to each of the individual session pads 05:28:21 #link https://etherpad.openstack.org/p/liberty-ironic-design-summit-ideas 05:28:29 though not all of them have content yet, they will soon 05:28:39 rameshg87: yes, it is better that horizon add ironic plugin for us 05:29:18 rameshg87: there is existing hourizon ironic plugin path, but for long time, no progress 05:29:31 Haomeng: yeah, it has been missing 05:29:40 rameshg87: yes 05:30:38 * rameshg87 has 1 item for open discussion 05:31:01 I'm happy to move on to open discussion at this point 05:31:08 #topic open discussion 05:31:16 we can certainly continue talking about the summit, too 05:31:36 i raised a review for adding ilo drivers support in lib/ironic of devstack 05:31:37 https://review.openstack.org/#/c/174733/ 05:31:56 however i got a comment saying hardware-specific stuffs should be out of devstack tree 05:32:20 isn't it reasonable to have upstream driver stuffs in lib/ironic of devstack ? 05:32:59 hm, not really. that would make devstack unmanageably large and hard to maintain 05:33:11 rameshg87: devstack supports loading plugins from other repositories 05:33:30 have you looked at how have other services (eg, cinder, neutron) have done this? 05:33:44 devananda: ah no. 05:34:04 * rameshg87 notes to take a look at it 05:34:19 but devananda major part of code can be reused in this way 05:35:19 devananda: the bulk of changes in lib/ironic in my review are 1) to create distro-images for deployment from diskimage-builder (cirros might not work on real hardware) 05:35:23 2) to create deploy iso (which will re-usable for drivers like irmc) 05:35:51 devananda: the only ilo specific thing in there is how we enroll the node (-d rameshg87: refactoring it so that the common parts for enabling hardware testing are preserved and isolated would be helpful 05:36:19 rameshg87: yes, it's reusable 05:37:11 rameshg87: I think we should also make the hardware-specific bits pluggable or able to read ENV vars 05:37:25 so that the jenkins job can pass in the right info for each test environment 05:37:54 devananda: okay 05:37:56 devananda: so refactor out the hardware-specific bits 05:38:01 that way, the code in devstack is generic and consistent, and the variations are only in the test job configuratoin 05:38:24 devananda: and keep the rest in devstack (like actual distro-image creation and stuffs), right ? 05:38:30 yup! 05:38:38 okay..will go in that path 05:38:48 Can we assume next week's meeting will be canceled due to the summit? 05:38:59 jlvillal: yes 05:39:13 * mrda taking over again 05:39:15 mrda, Thanks 05:39:24 mrda: :) 05:39:41 hi devananda, 05:39:44 and last time the meeting after summit was cancelled too 05:39:47 rameshg87: also, do you have docs on how to use devstack w/ real hardware? 05:40:02 devananda: no i don't have 05:40:14 devananda: may be i can put forward a documentation on ipmi with real image bits 05:40:24 I check the bug and it looks like because of the version of pywsman, the minimal one is 2.4.10 05:40:40 rameshg87: hm, ok. seems like an area of code you are close to -- perhaps you could find some time to doc it :) 05:40:56 devananda: sure 05:41:02 * rameshg87 notes as action item 05:41:30 rameshg87: thanks! 05:41:46 lintan: oh, interesting. please respond on the bug ,and I'll try to reproduce later 05:42:37 * rameshg87 wonders if we should poke 3rd party driver libraries to support python 3 05:43:01 rameshg87: +1 :-) 05:43:16 devananda: debian folks filed a bug on proliantutils to support python 3. may be we should ping third party maintainers to consider this. 05:43:27 devananda,sure I will 05:43:50 rameshg87: I tested scciclient with py34 and worked Okay. 05:44:02 we just fixed python 3 stuffs for proliantutils and enabled a gate job :) 05:44:19 naohirot: oh great :) 05:44:21 #info third party libraries should begin gating on py34 support soon, now that the server support for py34 is complete 05:45:53 I also have an item for open discussion. 05:46:03 pshige: it's open :) 05:46:09 Ironic documentation integrated with OpenStack manuals needs a volunteer to liason with Docs folks 05:46:11 pshige: no need to ask if you can ask 05:46:18 https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation 05:46:19 pshige: !! yes we do :) 05:46:31 Docs is important for me so I will do if nobody is willing. 05:46:42 Will it be decided at the summit meetup? 05:47:11 pshige: not much of a decision to make. no one else has volunteered 05:47:24 pshige: do you have familiarity with openstack-docs project and tools? 05:47:48 a little 05:48:15 but I would like to try 05:48:40 pshige, jlvillal - also, fwiw, generally speaking cross-project liaisons are drawn from the core review team, based on the understanding that they are more involved in the project and have some amount of history within it 05:49:35 devananda, Ah I didn't know that. I had asked on the IRC channel about volunteering and didn't hear any objections or anyone else wanting to volunteer at the time. So I volunteered... 05:50:08 that said, I'm happy that you both volunteered - and happy to help facilitate both of your efforts 05:50:25 Thank you :) 05:50:28 rather have eager people working on things that interest them than no one at all :) 05:50:41 and I'm sure you'll get to know everyone quickly enough ;) 05:50:57 Thank you 05:52:19 anyone have anything else, or shall we wrap up a little early? 05:53:00 ok then! thanks everyone! 05:53:03 thanks devananda 05:53:12 see (most of) you at the summit! 05:53:14 Thanks and ciao! 05:53:14 thanks devananda 05:53:17 thanks! 05:53:18 good day/good night everyone 05:53:25 ood day/good night everyone:) 05:53:29 good night 05:53:35 thanks devananda 05:53:36 #endmeeting