17:00:19 #startmeeting ironic 17:00:20 Meeting started Mon Mar 12 17:00:19 2018 UTC and is due to finish in 60 minutes. The chair is TheJulia. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:21 o/ 17:00:23 The meeting name has been set to 'ironic' 17:00:24 o/ 17:00:29 o/ 17:00:35 Everyone ready for an ironic meeting? :) 17:00:45 o/ 17:00:45 o/ 17:00:47 o/ 17:01:13 Our agenda can be found on the wiki, as always! 17:01:15 #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting 17:01:34 o/ 17:01:48 We've got a number of items on the agenda today, partially since we cancelled last week with people still traveling or handling jet lag from the PTG. 17:01:56 o/ 17:01:59 #topic Announcements / Reminder 17:02:31 I started a poll to help give us an idea of a meeting time more friendly to APAC attendees, I'll look at the results some time this week so there is still time to vote! 17:02:40 #link https://doodle.com/poll/6kuwixpkkhbwsibk 17:03:30 thx TheJulia 17:03:42 #info jroll has rejoined ironic-core 17:03:48 Nguyen Hai proposed openstack/ironic-specs master: Change ironic-specs webpage from oslosphinx to openstackdocstheme https://review.openstack.org/552007 17:04:01 #info The Rocky Cycle priorites review has been posted, please review ASAP. 17:04:16 #link https://review.openstack.org/#/c/550174 17:04:17 patch 550174 - ironic-specs - Add Rocky Priorities 17:04:36 wb jroll! 17:04:37 o/ 17:04:45 He's back! 17:04:49 #info TheJulia wrote up a summary of our PTG discussions and sent it to the mailing list. 17:04:51 #link http://lists.openstack.org/pipermail/openstack-dev/2018-March/128085.html 17:04:56 And he still has it! :) 17:05:12 +1 on jroll being back! :) 17:05:46 TheJulia: ty ^^^ 17:05:58 TheJulia: you've been busy. thx for the great summary! 17:06:26 #info There is no longer a oneview CI. TheJulia following up with a contact at HPE to determine the next step(s). 17:06:46 :-( 17:06:50 sigh 17:07:23 Does anyone else have anything they would like to announce or remind us of? 17:08:11 Is anyone here to accept the award on jroll's behalf? ;) 17:08:39 jlvillal: I thought he said he would have been back today... I guess maybe vacation captured him 17:09:01 Okay, I guess we can move on 17:09:01 It is a good way to miss a meeting :) 17:09:05 jlvillal: ++ 17:09:20 #topic Review action items from previous meeting 17:09:30 #info No action items from last week's meeting. 17:09:34 That was easy ;) 17:09:53 Ilya Etingof proposed openstack/virtualbmc master: multiprocess server, ZMQ-based management cli tool https://review.openstack.org/488874 17:09:57 Moving on... 17:10:06 #topic Subteam status reports 17:10:23 #link https://etherpad.openstack.org/p/IronicWhiteBoard 17:10:45 Our whiteboard needs some cleaning.... Lots of cleaning 17:10:57 That or we could just burn it with fire and migrate to storyboard 17:11:02 But that is a topic for later. 17:11:37 i suspect we'd still want the whiteboard 17:11:52 Yeah, agreed. 17:12:35 Without priorities agreed upon, I'm hesitant to update the whiteboard to reflect those new priorities. 17:13:15 I think we can delete the Ansible deploy interface from the list 17:13:54 TheJulia: traits support planning isn't in list of priorities 17:14:07 good point 17:14:12 * TheJulia updates python3.5 17:14:15 Good Morning Ironic'ers 17:14:23 nor is routed network support? 17:14:27 or rescue mode 17:14:35 but the status of those is still useful 17:14:54 TheJulia: is it possible to migrate to storyboard this week? 17:14:57 Looks like there were some rescue patches still oustanding, we should likely get those landed this week. 17:15:23 rloo: migration might take a couple days, I started a test on friday and it got a few hundred bugs in before my cats knocked the computer over.... 17:15:30 TheJulia: at least migrate what we have in the etherpad, to storyboard, before deleting from etherpad? 17:16:05 I think we should get the data into storyboard first, I'll try to get that machine back up and give folks access to it so they can look and see how our data looks in storyboard 17:16:16 #action TheJulia to get us a taste of storyboard 17:18:39 We still need to get the updated client out before we can finish rescue, but that should be soon-ish 17:19:39 bfournie: sambetts: w/r/t routed networks, is there anything that needs to be done that is still pertinent on the whiteboard? 17:19:42 and the nova part -- i suspect that's probably the hardest part that is outstanding 17:19:58 Yeah, and the issue of client calls and api versions... :\ 17:20:21 TheJulia: OH :-( 17:21:09 rloo: I'm going to look at the client in nova this week... likely with something tasty, and see how hard or easy it is going to be to switch it all over. 17:21:39 dtantsur: any update for Reference architecture stuffs? 17:21:52 TheJulia: nothing yet, making my way to it 17:23:23 * TheJulia updates some notes 17:24:43 I think we're good to proceed... although someone is adding things somewhere :) 17:25:19 * rloo just updated the sighup stuff 17:25:24 Thanks rloo 17:25:43 Everyone ready to move on? 17:25:48 yep 17:25:54 ++ 17:26:11 #topic Deciding on priorities for the coming week 17:27:15 Around line 146 17:27:22 Highest priority that I see is... well.. priorities 17:27:23 rocky priorities. we should aim to get that done when, friday? 17:28:03 Friday is a good goal for that 17:28:19 I can revise it again today since It looks like we've identified points of contact for all of the items 17:28:59 I'm adding "remaining rescue patches" since we should have a client release today 17:29:04 hopefully 17:30:34 pas-ha: were you able to get a list of patches together for graphical console related things? 17:31:57 #action TheJulia to clean-up the whiteboard further this week 17:32:22 TheJulia, shall i list remaining rescue patches? 17:32:40 hshiina: I was going to do that after the meeting, but your welcome to do so 17:33:00 Really, I think that is it for priorities this week unless someone has something else 17:33:54 I'm working through driver comp follows ups as well 17:33:55 How about an email coordinating a discussion about lifecycle managment? 17:33:57 TheJulia, sure. i'll do. 17:34:00 but may be not worth calling priorities 17:34:08 rpioso: Good point, that is on my calendar for thursday :) 17:34:16 Awesome! 17:34:36 dtantsur: okay 17:35:04 BIOS spec? 17:35:23 hmmm 17:35:32 I thought it landed for some reason, looking 17:35:48 nope 17:35:49 https://review.openstack.org/#/c/496481/ 17:35:50 patch 496481 - ironic-specs - Hardware interface for BIOS configuration 17:36:45 it's very close 17:36:56 hshiina: mgoddard_: w/r/t bios spec: do you feel that the changes can be performed as a follow-up at this point? 17:37:47 TheJulia: I need to spend a couple of quiet hours with it. 17:38:10 rpioso: acknowledged 17:38:15 I need to re-review that one too since many changes have been made since the ptg 17:38:40 Okay, I think we're good for this week, just everyone keep in mind that I will be inquiring about various things throughout the week as I clean up some of the whiteboard. 17:38:46 Time to move on? 17:39:20 ++ 17:39:25 #topic Appointing a bug triaging lead for the coming week 17:39:38 Anyone up for spending time with launchpad this week? 17:39:53 I'll do it! 17:40:01 mjturek: Awesome! Thanks! 17:40:26 #action mjturek to lead bug triaging for the next week. 17:40:35 Moving on to discussion then! 17:40:40 #topic Discussion 17:40:43 FYI: Easy and needed (IMHO) patch up for review. https://review.openstack.org/#/c/552042/ Thanks rloo for catching it :) 17:40:44 patch 552042 - ironic - multinode, multitenant grenade votes in gate 17:41:30 I have one discussion item today. Storyboard! 17:41:33 #link https://docs.openstack.org/infra/storyboard/migration.html 17:42:18 We've talked about it in person, and I believe the concerns were linking from gerrit, blueprints (which is covered by the link (there is no blueprint migration)) 17:43:36 I think linking from gerrit works via Story: 17:43:38 As I understand it, linking from gerrit to storyboard will be addressed later on, so the easy click that we have now to bugs might be a little bit of a headache. 17:43:40 (or something like that) 17:43:52 and we don't have blueprints \o/ 17:44:06 oh yes, it is Story: 17:44:08 or Task: 17:44:09 \o/ 17:44:14 #link https://docs.openstack.org/infra/manual/developers.html#development-workflow 17:44:52 so looks like we're in a good position to migrate? 17:44:53 Oh, and tags do appear to migrate as I understand it, that is easy to verify on my test instance. 17:45:10 Indeed, I would just prefer to get my test instance back up and see how long it takes :) 17:45:44 If there are no objections, we can proceed forth with it???? 17:46:02 other than getting a test instance stood up and generally accessible to see what our data looks like 17:46:22 * TheJulia is taking silence as agreement 17:46:36 the peice thats currently in progress from infra is storyboard to gerrit links 17:46:58 e.g. if you push a patch adding the link to the story to the patch 17:47:16 from the story to the patch * 17:47:39 ah, hmm, this is a nice feature to have for sure 17:47:41 I think we can live with that for now, typically we're going from the patch to launchpad, not the other way around 17:48:02 hi TheJulia, sorry I missed your call - in another meeting currently. My major concerns with the BIOS spec have now been addressed - the main one outstanding is the requirement for an object layer. That seems like something we ought to get agreement on, but happy with a follow up to document it 17:48:23 mgoddard_: thanks! 17:48:53 * TheJulia hears crickets 17:49:16 If there is nothing else, we can move to open discussion or wrap up the meeting 17:50:28 #topic Open Discussion 17:50:52 Anyone have anything they would like to discuss? 17:51:01 I was wondering if I could get some eyes on a patch set I've had sitting around for a bit =) https://review.openstack.org/#/c/429836/ 17:51:02 patch 429836 - ironic - Add OpenBMC class for accessing nodes using OpenBMC 17:51:46 baha: do we have an RFE approved for that? 17:51:57 dtantsur yep it's the OpenBMC driver RFE 17:52:02 we have an approved spec 17:52:09 ah, cool, I'll put it on my list 17:52:18 added to my list too 17:52:18 Thanks! 17:52:29 thanks dtantsur sambetts 17:52:34 do you plan on a 3rdparty CI? 17:53:04 we haven't started work on one 17:53:11 mjturek: and it certainly misses a release note :) 17:53:12 but we could extend the powerkvm ci for it 17:53:29 baha: yeah we should add a reno 17:53:33 mjturek: the spec says that is how it will be tested 17:53:46 mmm, and this particular patch does not add any hw types, does it? 17:53:56 dtantsur: it is a follow-up to add the hw types 17:54:00 otherwise it would be a 1600 line patch 17:54:11 I have a mixed feelings about that, but okay 17:54:16 2x 800 line patches 17:54:17 :) 17:54:44 mjturek: then the release note should go to the patch that exposes something, not to this one. sorry for confusion. 17:55:05 cool makes sense 17:55:12 https://review.openstack.org/#/c/403835/ is the other patch, and does need a reno 17:55:12 patch 403835 - ironic - OpenBMC Hardware Type 17:55:23 TheJulia so 3rd party ci before it merges? 17:55:42 TheJulia: 800 + 20, no? 17:55:54 mjturek: We have traditionally allowed for up to six months to pass before it needs to be in place 17:56:12 yep, it can merge first, but please do not delay the 3rdparty CI 17:56:20 * dtantsur wonders how xclarity CI is doing 17:56:31 crushil: ^^^ 17:56:35 :) 17:56:47 TheJulia dtantsur okay baha and I can start working that 17:56:52 I think that is it for today folks, if nobody has anything else? 17:56:59 mjturek: awesome 17:57:02 * dtantsur has nothing 17:57:33 crickets 17:58:02 * TheJulia hears crickets 17:58:03 Thanks everyone! 17:58:07 thanks TheJulia 17:58:13 thanks 17:58:35 #endmeeting