17:00:12 #startmeeting ironic 17:00:13 Meeting started Mon Nov 6 17:00:12 2017 UTC and is due to finish in 60 minutes. The chair is dtantsur. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:17 The meeting name has been set to 'ironic' 17:00:21 o/ 17:00:23 o/ 17:00:59 hi all! I wonder if we're going to have more than 2 people 17:01:11 dtantsur: I don't know. We have three now 17:01:14 Maybe rloo will join :) 17:01:35 We did have the end of daylight savings time in the US. So instead of a 10am meeting for me, it is now a 9am meeting. 17:01:58 yeah, happened to us a week ago 17:02:03 o/ 17:02:05 let us give folks a bit moar time 17:02:30 * pas-ha pours coffee 17:02:49 o/ 17:03:19 o/ 17:04:06 #topic Announcements / Reminder 17:04:09 * jlvillal votes to start :) 17:04:13 o/ 17:04:20 the forum is happening :) I hope people are enjoying Sydney 17:04:30 has anyone seen any recording? I could not find them this morning 17:04:53 #info Ironic Pike 9.1.2 was FINALLY released 17:05:08 #info ironic and ironicclient Queens releases to follow this week, hopefully 17:05:44 anything else? 17:06:38 #topic Review action items from previous meeting 17:06:46 #link http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-10-30-17.00.html 17:06:57 vdrok: how was the bug triage? 17:07:11 dtantsur: was good hopefully :) 17:07:24 wrt zuulv3 - the etherpad is up to date. need folks to review. 17:07:27 I see the bug number decreasing, this is good 17:07:51 I've noticed that legacy jobs need A LOT OF clean up 17:08:08 dtantsur: yup :-( 17:08:31 anyway, let's finish with copy-paste first 17:08:33 dtantsur: but it'll be beautiful after the clean up. Something to look forward to :) 17:08:38 right :) 17:08:38 yeah. in theory, most of the things there should be rewritten, to use the new "builders" 17:08:52 I was starting to work on a check script to parse the zuul v3 files and try to find any errors. 17:08:56 Well obvious errors. 17:09:27 #topic Review subteam status reports 17:09:41 btw, ironic has been tagged: supports-rolling-upgrade 17:09:41 this is what we're doing already, right? :) 17:09:48 rloo++ yes 17:10:02 #link https://etherpad.openstack.org/p/IronicWhiteBoard line 141 17:10:36 vdrok: thx for reducing the bug count! 17:10:37 we're nearly done with the first essential priority, please keep reviewing ;) 17:10:43 * vdrok checks stable branch status 17:10:50 well, I guess it involves Nova part too 17:12:36 rloo: thanks for keeping track of the zuulv3 :) 17:13:02 vdrok: yw, the faster we get that done, the less time I need to spend time keeping track of it ;) 17:13:12 very true 17:13:17 vdrok: then there's the 'clean up' part! 17:13:47 should be easy as well. rewrite to new style jobs can take more effort 17:14:41 i'm done with subteam stuff. guessing it'll be quiet this week too? 17:15:04 yeah, just updated the links to our call summary re traits 17:15:08 everyone done? 17:15:30 Does ironic-inspector use the tempest stuff in ironic? 17:15:47 I'm around line 292, trying to update the list of projects want to have done. 17:15:48 jlvillal: yes 17:16:03 I mean, it's using ironic tempest plugin as a basis for its own 17:16:09 and it uses bits of the jobs, I guess 17:16:28 dtantsur: Okay. To be on the safe side, we should get inspector done before ripping it out of ironic. 17:16:41 and we had decided that the new tempest repo would be for ironic and inspector and ..? 17:16:56 jlvillal: I believe so, yes 17:17:03 Speaking of which, would like to get the script patch merged: https://review.openstack.org/#/c/489762/ :) 17:17:07 rloo: one repo, yes, but that's the next step 17:17:27 * jlvillal looks hopefully at vdrok regarding https://review.openstack.org/#/c/489762/ 17:18:00 jlvillal: will take a look :) 17:18:09 * dtantsur looks at jlvillal looking at vdrok 17:18:21 * vdrok looking 17:18:21 moving on? :) 17:18:27 heh 17:18:41 #topic Deciding on priorities for the coming week 17:19:11 dtantsur: for the ironic release, there's nothing we're waiting on? 17:19:24 rloo: reno clean up is still needed 17:19:25 * milan_ <3 https://review.openstack.org/#/c/489762/6/tools/make-tempest-plugin-repo.sh@105 17:19:31 feature-wise, I think, we're good 17:19:47 dtantsur: oh yeah. and actually, are they doing releases this week, given the summit going on? 17:19:55 this one https://review.openstack.org/419439 is looking good, and is the only thing left to close the huge upgrade rfe 17:20:14 rloo: I doubt it. but I want to request it and move on :) 17:20:26 dtantsur: ok, let's get that done then. 17:21:11 vdrok: ++. I'd +2 it myself :) 17:21:38 milan_: :) 17:21:44 heh 17:22:03 okay, the priorities 17:22:17 I think the list is good as it is, as nothing was done (sigh) to completion 17:22:43 opinions? 17:22:59 and vdrok's suggestion above? :) 17:23:11 aha 17:23:37 seems dtantsur has to put a +2 :D 17:23:47 I'm good with adding it, I hope the ironic CLI thing merges soon 17:23:59 how's the list looking? 17:24:14 dtantsur: on my list; if i hadn't had to do the zuul v3 tracking, would have been reviewed sooner. :D 17:24:27 zuul happens when it happens 17:24:29 :) 17:24:46 list is good with me, thx. 17:25:15 moving on in 3... 17:25:19 2... 17:25:23 1... 17:25:31 #topic Appointing a bug triaging lead for the coming week 17:25:44 any vict^Wvolunteer? 17:26:22 forest of hands :) 17:26:25 I can do it this week 17:26:45 I'm not sure a lot of triaging is left, maybe I'll try fixing/reviewing something bug-related 17:26:57 #action dtantsur to lead bug triaging/fixing/closing this week 17:27:07 #topic Open discussion 17:27:19 yeah, I've found most of the old bugs set to incomplete, so they'll expire soon if noone replies there 17:27:27 nice 17:27:44 let's merge dnsmasq filter on inspector? ;) 17:27:57 oh, that looks great! 17:28:16 where do I +2? :D 17:28:25 vdrok: shoudl we ask about those functional test patches? 17:28:38 vdrok, lol anywhere on the pull request would be great! :D 17:28:42 vdrok: or did we decide? I can't remember 17:28:49 rloo: which ones? 17:28:51 ah 17:28:56 vdrok: i think the client ones. 17:29:01 vdrok: for ironic CLI 17:29:05 sorry, I forgot. lemme find some links 17:29:09 milan_: I think you have been using github ;) Pull request :) 17:29:27 jlvillal, guilty as charged :D 17:29:28 so, there are a bunch of patches to do functional tests for ironic CLI. given that we've deprecated it, how much effort do we want to put into those patches/tests? 17:29:51 the folks that submitted those patches are no longer around. 17:30:08 best effort? 17:30:17 and i wasn't that happy with one of the patches. don't know if we should just land since it is a test, or spend time cleaning up. 17:30:22 like, I don't see point in reviewing them, but I also don't see any harm in somebody landing 17:30:35 rloo: -1 and move on? 17:30:45 yeah, one of examples https://bugs.launchpad.net/python-ironicclient/+bug/1555680 17:30:46 Launchpad bug 1555680 in python-ironicclient "Add CLI tests to check JSON response body" [Low,Triaged] 17:31:02 I vote for minimal effort to 'ironic' client. Due to deprecation. 17:31:08 some of them were not started, or patches are abandoned. I was thinking if we need to close those 17:31:45 ok, let's just close them, make sure there are equivs though for OSC CLI? 17:31:47 to be honest, these are not the valid bugs 17:32:05 that's my feeling as well 17:32:13 but this is subjective. I don't like a new bug for every test people feel we could add.. 17:32:29 I'm happy with closing them, but leaving valid patches up 17:32:42 bugs are a good way to track 'things-to-do', but yeah, not each separate test. 17:32:44 okie. I'll go through them tomorrow 17:32:58 dtantsur: I am growing to like more and more the idea that bugs should be for user visible changes/issues. Though use that as a guideline, there would be exceptions of course. 17:33:23 But a bug for each test is way overboard. 17:33:28 thanks vdrok 17:33:49 if there were a prize, vdrok would win it, for reducing the # bugs :) 17:34:02 a beer in DUB? :) 17:34:08 jlvillal: well, some projects don't merge any patch without a bug reference 17:34:12 ++ 17:34:16 :) 17:34:20 that was for the beer :) 17:34:24 hopefully I'll make it ! 17:34:30 vdrok: I'd like a reference for user-visible and otherwise important changes 17:34:38 but not for things like a new test or a typo in a docstring.. 17:34:48 yeah, I agree 17:35:02 that's why I was thinking about closing them:) 17:35:31 vdrok: dtantsur ++ on bugs 17:36:19 also would be good to go through all the old rfes we have, but it's going to take more time 17:36:34 yep 17:36:38 and old approves specs 17:36:43 * approved 17:37:13 good to review rfes too :D 17:37:45 and all patches. TOOMUCHTODO 17:38:50 hehehe 17:39:07 okay, anything else to discuss? 17:39:42 rloo, crickets ;) 17:39:54 grasshoppers... 17:40:03 lol 17:40:24 thanks all 17:40:31 Bye all! 17:40:32 20 minutes are yours :) 17:40:34 \o 17:40:34 #endmeeting