17:00:01 #startmeeting ironic 17:00:02 Meeting started Mon Jan 30 17:00:01 2017 UTC and is due to finish in 60 minutes. The chair is jroll. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:04 o/ 17:00:05 o/ 17:00:06 o/ 17:00:06 The meeting name has been set to 'ironic' 17:00:10 O/ 17:00:10 o/ 17:00:15 o/ 17:00:16 o/ 17:00:17 welcome, everyone 17:00:21 o/ 17:00:25 o/ 17:00:26 o/ 17:00:27 o/ 17:00:30 o/ 17:00:33 o/ 17:00:34 o/ 17:00:36 o/ 17:00:38 o/ 17:00:38 o/ 17:00:44 as always, agenda: 17:00:46 * dtantsur|mtg will switch to this meeting soon, still finishing 17:00:47 o/ 17:00:54 #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting 17:01:04 #topic announcements and reminders 17:01:11 just a few things here 17:01:36 #info reminder to add to the PTG discussion list: https://etherpad.openstack.org/p/ironic-pike-ptg 17:01:38 #link https://etherpad.openstack.org/p/ironic-pike-ptg 17:01:59 #info we intend to feature freeze ironic/inspector/IPA this week, and release them next week 17:02:32 #info pike PTL elections open this week, we have 3 candidates, should be exciting :) 17:02:35 #link https://governance.openstack.org/election/ 17:02:38 more info there ^^ 17:02:51 good luck JayF, dtantsur|mtg, TheJulia :) 17:02:59 Thank you jroll 17:03:02 any other announcements/reminders? 17:03:05 may the best person win :) 17:03:17 even though you are all best in my book! 17:03:19 o/ 17:03:27 o/ 17:03:31 rloo: Thank you :) 17:03:47 if the best person wins, I might be in for a bit of electoral trouble ;0 17:03:50 rloo, ++ 17:04:38 does each project have different timings for PTL election? 17:04:51 soliosg: no, they're all at the same time 17:05:06 many do not have elections, though, as they only have one candidate 17:05:10 I received an email this weekend announcing the new PTL for docs 17:05:28 or maybe I misunderstood something :( 17:05:36 yes, many projects only have one candidate 17:05:38 if there are no elections (e.g. one candidate), the outcome is obvious 17:05:41 and so they must win 17:05:46 I see, thanks! 17:05:47 see https://governance.openstack.org/election/ 17:05:50 soliosg: only one person ran for ptl in docs i believe, so no need to vote 17:06:13 shall we move on to subteams? 17:06:26 #topic subteam status updates 17:06:37 * jroll updates things he knows about 17:06:59 o/ 17:07:31 o/ 17:08:42 did anyone get to reviewing node tags last week? how's that looking? 17:08:47 * dtantsur didn't 17:09:08 jroll: i did, i stopped after the first patch when it seemed to me the client part would not make it. 17:09:25 * jlvillal didn't. Was focused on driver composition 17:09:46 do we want to punt it to pike, or try to get it in this week? 17:09:50 jroll: cuz i had some comments with the first patch, and there were at least 2 more after that... 17:09:56 right 17:10:06 jroll: i think we should punt it. i could be wrong but i think the author is still on holiday 17:10:16 rloo: aha, right, forgot about that. +1 17:10:20 without a client change, it does not look THAT useful to land it right now 17:10:25 yup, chinese new year 17:10:41 Year of the Rooster. According to Overwatch ;) 17:11:16 jlvillal: yup 17:11:24 yay, soft power things are done! :) 17:11:36 yep, even nova part has landed 17:11:47 NMI stuff may even land in nova with an FFE 17:11:57 jroll, did they request one? 17:11:59 jroll: who is asking for the FFE? (has it been asked?) 17:12:06 dtantsur: dunno, but it's on nova's list nonetheless 17:12:10 Nova said on ML last week no FFEs 17:12:12 I'll ask matt, I didn't see that 17:12:21 and listed a small handful of patches that were the last to land in Ocata 17:12:25 https://etherpad.openstack.org/p/nova-ocata-feature-freeze 17:12:28 is where I see that 17:12:35 i thought matt is away but could be wrong 17:12:40 I'll clarify with matt or someone 17:12:42 he's in and out 17:13:03 nmi isn't a huge priority for us though 17:13:04 https://review.openstack.org/#/c/376548/ has 1x +2 17:13:18 rloo, yeah, I just like finished stuff :) 17:13:22 rloo: I agree, but the status is unclear, so I'm going to clarify. 17:13:31 * jroll is not pushing, just asking 17:13:34 dtantsur: don't we all! :D 17:13:40 I hope so :) 17:13:53 thx jroll, clarification is always good 17:13:59 (except for the driver composition - it never finishes..) 17:14:05 so, is there any feature work besides driver composition we want to get done this week? 17:14:11 seems everything is done or bumped to pike 17:14:22 let's get some bugs fixed? :) 17:14:34 jroll CI improvements? :) 17:14:40 well, yes, just sanity checking on feature work 17:14:58 yeah, and CI stuff 17:15:00 vsaienk0: maybe, depends on the thing, I want to be careful not to break CI right before release :) 17:15:14 just don't make anything voting and don't refactor too much 17:15:29 ++ 17:15:31 wrt portgroups, there are a few things not done yet. do we want to get them done (tempest tests, doc) in ocata? 17:15:49 rloo: yes, testing and docs isn't really "feature" work 17:15:53 (imo) 17:16:05 both can be (and often should be) backported 17:16:07 jroll: huh? aren't they part of the feature? 17:16:10 I'll get to docs this week 17:16:17 rloo: in terms of freezing. 17:16:28 jroll: oh yeah. i was just asking wrt ocata. 17:16:30 so yeah, driver composition is the only feature thing to get in before feature freeze, best I can tell 17:16:40 and then let's finish up docs, testing, fix some bugs 17:16:44 and call it a cycle :) 17:16:51 \o/ 17:16:57 ocd. ocata cycle done... 17:17:01 good plan! 17:17:03 sounds good to me 17:17:13 o/ 17:17:33 congrats all on a good cycle 17:17:46 mariojv: it ain't over yet :) 17:17:53 ^^ :P 17:17:54 yeah, we still can make it bad :D 17:18:07 okay, I listed quick priorities, I don't have particulars to list there 17:18:48 feel free to add links if you come across some high-priority bugs or whatever :) 17:19:08 wrt bug fixes and docs. could we have two volunteers maybe, to look into those two and let the rest of us know what we should be looking at? 17:19:12 Should we add the ironic-tempest-plugin repository work to the CI status section? 17:19:28 jlvillal, I'd wait until the PTG with any actions on that 17:19:29 jlvillal: we already agreed to wait for pike on that, so meh 17:19:35 rloo: yes, I'd love that 17:19:38 Okay 17:19:43 jlvillal, are we decided on it already ? If so yes 17:20:15 I wasn't sure if people wanted to have updates on what has been going on there. But can wait until PTG time :) 17:20:21 ^^ volunteers? you can apply here or elsewhere :) 17:20:33 rloo, I can look at bugs 17:20:42 I always look at them anyway :) 17:20:51 fwiw, i looked at the bugs/patches for the client release last week 17:20:52 I'll try to skim things but idk how much time I'll have to do so 17:20:54 dtantsur: thx! 17:20:59 I can do docs then :) 17:21:06 jroll has to focus on driver composition 17:21:31 thx vdrok! 17:21:42 thanks vdrok and dtantsur 17:21:46 anything else here? 17:22:19 #topic open discussion 17:22:43 Were there no RFEs to go over this week? Or is that usually after open discussion? 17:22:44 jroll: anyone. wrt ptg, is the plan to hold ironic things m-f all day? 17:22:54 oh, i mean wed-fri 17:23:07 FYI: 3 weeks until the PTG. 17:23:17 JayF: there were none on the agenda 17:23:36 rloo: I suspect people will leave friday night, as such, friday afternoon may be light[ 17:23:41 rloo: i thought friday afternoon would be left off for folks traveling, yeah that ^ 17:23:46 I'd like to talk friday morning at least 17:24:11 jroll, mariojv: good to know! that traditional friday 'meet up' may be different at the ptg i guess. 17:24:26 rloo: the whole thing will be less formal :) 17:24:38 regarding the ironic-tempest-plugin move to new repo 17:24:53 at some time we'll need a code freeze on ironic/ironic_tempest_plugin 17:25:03 jroll: right. 17:25:22 so, just keep in mind in case devs have patches that update ironic and ironic/ironic_tem... 17:25:29 huh, I'm not guessing with the tickets again :) in US it's usually till friday midday, and in EU it's usually whole afternoon? :) 17:25:43 soliosg: how much time is needed for this code freeze? 17:26:02 vdrok: dunno, it's first PTG, this is just what I guess will happen :) 17:26:06 soliosg: where are we/you tracking this. would be good to document this code freeze thing. 17:26:30 we'll try to sync-up code from ironic to ironic-tempest-plugin regularly 17:26:43 rloo: If and when it happens. Basically code that would have gone into openstack/ironic/ironic_tempest_plugin will instead go into openstack/ironic-tempest-plugin/ironic_tempest_plugin 17:26:44 why would we not "freeze" at the same time, as in whatever commit hash matches ironic when it is frozen? 17:27:12 since we're not doing this til pike, perhaps this is something to discuss later? 17:27:15 and have test runs, when the time comes, should be a matter of updating project-config to point to the new repo 17:27:29 soliosg: would help if you coudl write up something about the process/plan? 17:27:51 yeap, we should get to the details later, after ocata cycle ends 17:28:05 Agreed 17:29:06 crickets? 17:29:16 yep 17:29:18 anything else? 17:29:21 going once 17:29:25 twice 17:29:27 #endmeeting