15:00:11 #startmeeting ironic 15:00:11 Meeting started Mon Mar 9 15:00:11 2020 UTC and is due to finish in 60 minutes. The chair is TheJulia. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:14 The meeting name has been set to 'ironic' 15:00:15 Greetings everyone! 15:00:16 o/ 15:00:17 o/ 15:00:18 o/ 15:00:20 \o 15:00:21 o/ 15:00:22 o/ 15:00:23 Welcome to our weekly agenda! 15:00:26 o/ 15:00:26 err, meeting! 15:00:30 o/ 15:00:32 Well this meeting is going off wonderfully already 15:00:41 o/ 15:00:50 o/ 15:00:54 \o 15:00:57 Our agenda can be found on the wiki, as always 15:00:58 \o 15:00:59 #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting 15:01:08 #topic Announcements / Reminders 15:01:34 #info Rocky has entered extended maintenance and no more releases will be performed. 15:01:58 o/ 15:02:08 #info This week is R-9, so we're beginning to run out of time for this cycle. 15:02:15 oh, again? 15:02:55 #info Reviewers, please spend some time reviewing, we have a number of items people are pushing on and I'm sure everyone will appreciate some additional reviews 15:03:15 dtantsur: 3 weeks until non-client library freeze 15:03:35 so, metalsmith, sushy and ironic-lib 15:03:43 dtantsur: Realisticaly we'll need to cut our release in 6 weeks. 15:03:47 I guess sushy is particularly active 15:03:51 yeah 15:04:18 Merged openstack/bifrost master: Prepare to switch CentOS 8 job voting again https://review.opendev.org/703954 15:04:23 and feature freeze in around 4 weeks, I guess? 15:04:31 I was hoping to have a write-up of the mid-cycle posted by now, but haven't quite gotten to it 15:04:48 dtantsur: realistically yeah 15:05:00 TheJulia: if you share an etherpad/gdoc with me, we can work on the contents together 15:05:19 I can help if necessary also o/ 15:05:26 dtantsur: that being said, if there is limited scope or sufficient confidence in a feature I'm less concerned about a hard/formal feature freeze 15:05:43 Much appreciated guys, expect a link later today :) 15:05:52 yeah, I'm not advocating for a hard freeze, rather a soft freeze as previously 15:05:52 ack 15:05:58 dtantsur: ++ 15:06:09 Does anyone else have anything to announce this week? 15:06:34 Seems we had no action items so we can skip that section of the meeting 15:06:50 ++ 15:07:02 Are we good to proceed onward!? 15:07:07 let's 15:07:16 choo-choo! 15:07:27 #topic Review sub-team status reports 15:07:34 #link https://etherpad.openstack.org/p/IronicWhiteBoard 15:08:02 Starting at line 298. 15:09:09 I've not had spoons to work on the whitepaper, but the doc is there. Hopefully the next month will be nice and quiet! 15:09:22 I don't think I've got anything for the whitepaper in the end :( 15:09:23 * arne_wiebalck hopes that, too 15:10:04 we need to copy and attribute some content sadly. We expected people proposing content to do so... that was hopeful I think. 15:10:10 I guess nobody wants to take the role of the editor 15:10:42 Anyway, moving on! 15:10:47 dtantsur: thanks for the update on deploy steps! 15:11:00 the node retirement item can be closed, no? 15:11:01 np, it's fun to work on :D 15:11:11 tzumainn awesome progress on multitenancy! 15:11:12 arne_wiebalck: the sdk patch hasn't merged yet 15:11:17 TheJulia, thanks! 15:11:19 or has it? 15:11:24 tzumainn++ 15:11:24 arne_wiebalck: the openstacksdk patch is not merged yet, but it should be today 15:11:28 I think it has. 15:11:42 almost, ok 15:11:47 in the gate \o/ 15:12:25 Reviews of https://review.opendev.org/#/c/672780/ would be much appreciated! 15:12:25 patch 672780 - ironic-specs - Update L3 based deployment spec - 36 patch sets 15:12:27 I need to fix one small thing in the functional test, but will do in a follow-up 15:13:11 nice, thanks! 15:13:21 stevebaker is not aorund, but I'm wondering if we've reached a forward path on the wsme work? 15:13:28 s/aor/aro/ 15:13:43 I haven't seen new patches on that topic 15:14:58 Looks like the software raid patches are ready for review 15:15:05 I rebased and tested the UEFI RAID patches on real h/w. 15:15:25 Yes, are good to go from my POV. 15:15:46 arne_wiebalck: the standalone raid tests are failing on the ironic patch, so something might be breaking it on that patch 15:16:10 Are we basically good python3 wise for this cycle? 15:16:22 TheJulia: ah, the ironic one? 15:16:27 arne_wiebalck: yeah 15:16:50 TheJulia, mostly 15:16:53 python 3.. has someone checked what is happening in the metalsmith CI? 15:17:10 I think we're missing still some stuff 15:17:15 tenks 15:17:40 tenks has patches ready to go 15:17:52 mgoddard, yeah =) 15:17:57 mgoddard: could you add it to the whiteboard? :) 15:18:02 https://review.opendev.org/#/c/695881 and https://review.opendev.org/#/c/710100 15:18:03 patch 695881 - tenks - CentOS 8 support - 20 patch sets 15:18:04 patch 710100 - tenks - Bump ansible version constraints to >=2.7,<2.10 - 5 patch sets 15:18:06 TheJulia: sure 15:18:07 dtantsur: I was going to check metalsmith, didn't have time today 15:18:11 Thanks! 15:18:15 nice, thanks 15:18:41 and we're still waiting for the fix to centos8 libvirt pkg for bifrost, somewhat related 15:19:01 So cross-project wise, one thing to raise awareness. The nova team found an issue with the hash ring logic. Turns out someone renamed one of their machines after the deployment was already online to something with mixed case. 15:19:32 I noticed we kind of had a similar bug around conductor start-ups, so I put up a patch for that. Since nobody has reported it, I'm not too worried about getting the fix merged quickly. 15:20:07 oh. interesting (or not) :-( 15:20:08 TheJulia:do you have a link to a bug? 15:20:10 Anyone have anything else to ask questions about on the list or note status ? 15:20:27 arne_wiebalck: https://review.opendev.org/#/c/711680/ 15:20:28 patch 711680 - nova - Lowercase ironic driver hash ring and ignore case ... - 3 patch sets 15:20:39 TheJulia: thanks! 15:21:07 https://review.opendev.org/#/c/711765/ <-- what I posted after looking at our code 15:21:07 patch 711765 - ironic - Make reservation checks caseless - 2 patch sets 15:21:53 Are we good to proceed ? 15:21:59 ++ 15:22:13 Harald Jensås proposed openstack/ironic master: Additional IP addresses to IPv6 stateful ports https://review.opendev.org/700002 15:22:13 #topic Deciding on priorities for the coming week 15:22:26 #link https://etherpad.openstack.org/p/IronicWhiteBoard 15:22:36 Line 165 15:23:44 iurygregory: looks like the IPE patches merged, is there anything else needed for that right now? 15:24:29 TheJulia, I have some backports to stable/train, and I noticed that we don't have the documentation for the ipe (I'm working on it) 15:25:21 iurygregory: Thanks, and thanks for noting the backports 15:25:43 I really hope folks have some review bandwidth this week. :( 15:25:58 TheJulia, I just added the patches in "Potential candidates for backport" 15:26:15 Are we good with the list of patches today? 15:26:28 what does the 'for the next meeting' mean? 15:26:30 I guess we can remove the "For the next meeting" line? 15:26:34 L 227 15:26:41 rloo: stuff that I proposed earlier today 15:26:50 heh, thx dtantsur 15:26:55 Removed 15:27:04 quick question wrt backports. now that rocky is extended maintenance. 15:27:19 i see at L244, 'agreed... to take fixes to stein'. 15:27:19 rloo: sure 15:27:39 i'm not sure when 'last week' was. But is that the agreement? 15:28:04 I'm not sure either, but my take would be that backports to any non-EM releases are recommended, Rocky and Queens are optional 15:28:13 ++ 15:28:18 non-EM releases are Train and Stein 15:28:33 Pike and Ocata are likely dead already, and nobody has bothered with them for a while 15:28:50 i'm good with that. if no disagreements, i'll update that wording and link to this discussion. 15:29:05 rloo: thanks for spotting that! 15:29:10 rloo++ 15:29:30 Are we good to proceed to discussion items? 15:29:40 Riccardo Pittau proposed openstack/metalsmith master: [DNM] Testing CI https://review.opendev.org/711935 15:29:41 * dtantsur is good 15:29:45 ++ 15:30:16 #topic Discussion 15:30:27 We have a single topic, which relates to what we were just actually talking about! 15:30:39 yay 15:31:08 dtantsur inquires if we should keep the ocata and pike branches in Extended Maintenance or stop supporting them completely as in closing the stable branches and no longer accepting patches for those branches. 15:31:48 what do other projects do? 15:31:54 good question 15:31:59 (ok, nova!) 15:32:09 my heros. ha ha. 15:32:11 * dtantsur looks at nova 15:32:26 I see that nova still has stable/ocata 15:32:28 if we're not going to to backports, why should we keep them open? 15:32:55 how does it hurt to keep them open? 15:32:55 rpittau: Well right now, it is up to us if we want to accept patches on those branches 15:32:57 on the other hand, they have pretty recent patches to ocata: https://review.opendev.org/#/q/project:openstack/nova+branch:stable/ocata 15:33:00 we just won't cut the EM brancehs 15:33:03 branches 15:33:07 rloo: it doesn't, maybe just wrong messaging 15:33:42 The thing we kind of need to keep in mind is that it is OKAY to drop test jobs if they are a burden for EM branches 15:33:42 like, I'm not going to revive the CI on Pike and Ocata. If anybody wants to - be my guest :) 15:33:50 i suppose if some bug comes up that someone really wants fixed, and if it eg coincides with a nova patch in ocata? 15:33:54 extended maintenance means that there are community members maintaining it 15:33:58 i thought we already turned off CI for pike and ocata. 15:33:59 Like EM grenade tests, we didn't need anymore. 15:34:10 this is also related if we care about holding the configurations in ironic-tempest-plugin e.g. https://github.com/openstack/ironic-tempest-plugin/blob/0cbe05eff6b1618e0cba700e246680f91e029832/ironic_tempest_plugin/config.py#L55 15:34:19 ah, right, iurygregory raises a good point 15:34:23 https://github.com/openstack/ironic-tempest-plugin/blob/0cbe05eff6b1618e0cba700e246680f91e029832/ironic_tempest_plugin/config.py#L216 15:34:46 ironic-tempest-plugin is branchless, so in theory it has to support all open branches 15:35:00 I've heard something about neutron (?) capping their tempest plugin 15:35:01 I guess we need to keep queens compatibility 15:35:16 rpittau: the TC's intent is that the branches in EM are open for largely non-core community maintainers to submit patches to. 15:35:22 RH has business interest in queens, so I'm up for keeping it alive for now 15:35:26 can we change the rules so that the plugin only supports... (what?) branches? 15:35:36 I'm all for saying "if it is in EM, we no longer need it in tempest" 15:35:50 yeah, what TheJulia sez ^^! 15:35:51 that will mean that the tempest jobs will no longer pass there 15:36:01 OR we'll have to cap the plugin (which is not entirely impossible) 15:36:02 TheJulia: I understand that, just thinking even if we have patches submitted but no core reviewing or taking care of the CI, well..... 15:36:18 and this ^^^ 15:36:36 maintaining CI for 4 releases is already an humungous job 15:36:51 oh yes 15:36:52 dtantsur: well, is the burden of keeping CI working worth it. At some point only unit tests are going to work for some of these branches no matter what we do and how many hours we pour into them 15:36:54 Merged openstack/bifrost master: Do not use tests as filters https://review.opendev.org/711815 15:36:59 humongous* 15:37:10 TheJulia: right, but then have do we merge something there? 15:37:22 I'm not going to +2 a change that doesn't pass at least some testing 15:38:08 If we want to hold the requirement of some integration tests working, then where do we cut that off at? 15:38:20 Dmitry Tantsur proposed openstack/bifrost stable/train: Do not use tests as filters https://review.opendev.org/711938 15:38:55 dtantsur: I think the TC expectation was that at some point really old branches that would never be released again may only end up with unit testing 15:38:59 but that it is also up to each team 15:39:16 let's just cut them off then. there aren't enough people here to maintain all that, and if we won't +2 if there are no tests, then no use. Is that how everyone feels, no one will +2 w/o (functional) tests? 15:39:16 I'm kind of neutral and all for reducing pain 15:39:32 realistically, we don't see a lot of patches there 15:39:38 (to put it mildly) 15:39:52 if there was a strong interest in e.g. ocata, I would probably force myself into maintaining it 15:40:11 so.. maybe turn off. leave proposed patches around. people can merge those to their local copies? 15:40:15 but the last patch was proposed to ocata in August 15:40:28 rloo: that was also the expected intent at some point 15:40:33 i mean if we can' guarantee that a patch works, we don't want to +2. so it is going to be people-beware... 15:40:58 I don't think there is strong interest in maintaining ocata... nor really pike 15:41:12 exactly 15:41:17 so whatever reduces the pain, I'm all for 15:41:30 we can make it a documentation issue: document which branches we maintain to which extent 15:41:34 similar to releases.o.o 15:41:43 is it worth talking to nova to get their viewpoint on why they added changes to ocata recently? wow, just looking now, and it was quite recent. 15:42:19 maybe just somebody cares to? :) 15:42:36 maybe there was an interest downstream 15:43:11 * rloo continues to be impressed with nova 15:43:16 note that ironic had been a fast-moving project until very recently 15:43:26 dtantsur: I say we update the docs, we drop tests to minimal on those branches, we document we're not intending to merge anything to those branches, and move on 15:43:43 fwiw, we are using ocata downstream but I don't expect changes to be backported to that... 15:43:45 maybe even skip dropping tests. if somebody wants to fix them - cool! 15:43:55 dtantsur: cool! Love it! 15:44:31 rloo: at that point, I guess you've got downstream branches already and most fixes are environment/local need specific 15:45:01 TheJulia: i make us feel the pain of being on an old branch by manually backporting things that we need... 15:45:31 * TheJulia wonders if there is a movie reference that is appropriate... 15:46:30 Anyway, I'm all for minimal pain, lets just document stance and move on. 15:46:55 Since we have no RFEs listed nor the Baremetal SIG has anything listed, I suggest we go directly to Open Discussion 15:47:23 #action dtantsur to document supported branches 15:47:34 dtantsur: thanks! 15:47:37 unless somebody beats me to it 15:47:43 so we support till queens right? =) 15:47:49 iurygregory: yeah 15:48:03 awesome =) 15:48:50 to be clear, we were talking about ocata & pike, right? 15:48:55 * iurygregory updates ironic-tempest-plugin since ocata will be no longer supported 15:49:11 rloo: yep 15:49:29 ok, wanted to make sure 'til queens' included queens :) 15:49:38 :) 15:49:39 rloo, yeah =) sorry 15:49:47 \o/ 15:49:56 If there are no objections, Open Discussion time? 15:50:18 let's open the open discussion 15:50:25 openly 15:50:55 #topic Open Discussion 15:50:59 So how is everyone?!? 15:51:23 oh gosh.... reserve question ? 15:51:30 lol 15:51:34 Worried, tired. Nothing new :) 15:51:50 *sigh* I know that feeling 15:52:43 one thing I have, I'm switching the jbos in ironic to dib but there is an issue with ironic-tempest-ipa-wholedisk-bios-agent_ipmitool that really bugs me, I was thinking to leave it to tinycore until we can figure that out ? 15:52:59 do you have a clue what is happening there? 15:53:13 On a plus side, hopefully I can stop taking tamiflu in a few days. 15:53:24 dtantsur: https://4ae2de5d02c97f2930b7-ff2d888c3307ad9718a14b305143c473.ssl.cf2.rackcdn.com/710278/13/check/ironic-tempest-ipa-wholedisk-bios-agent_ipmitool/419eb12/controller/logs/ironic-bm-logs/node-0_console_2020-03-05-16%3A01%3A18_log.txt 15:53:26 that's an improvement! 15:53:44 oh 15:53:49 yeah :/ 15:53:52 rpittau: I seem to recall that DIB-built images hate having >1 NICs 15:54:05 Mark Goddard proposed openstack/tenks master: WIP: Support linux bridge in addition to OVS https://review.opendev.org/711682 15:54:06 can it be the cause here? 15:54:17 I recall setting NIC number to 1 for these jobs 15:54:24 Iury Gregory Melo Ferreira proposed openstack/ironic-tempest-plugin master: Change default driver https://review.opendev.org/711941 15:54:29 maybe, I see it's failing checking for 2 macs 15:54:30 That is... alarming 15:54:46 could lookup be broken? 15:54:57 mmm 15:55:06 Merged openstack/ironic master: Expose allocation owner to additional policy checks https://review.opendev.org/707307 15:55:08 mm, yeah, the NIC problem would manifest itself as "no route to host" or something like that 15:55:19 404 from lookup smells fishy 15:55:34 very fishy 15:55:50 I think I'll split the patch anyway, we can move forward with the others, they look fine 15:55:58 ++ 15:56:02 yeaahh 15:56:03 it is supposed to split on a command and look them up individually... at least that is what I remember of it 15:56:14 broken lookup doesn't explain why only this job fails 15:56:20 moving most of the jobs is awesome already... 15:56:59 rpittau: splitting soudns like a good idea because we could also be increasing hypervisor load with some of the job changes 15:57:14 TheJulia: exactly 15:58:54 wrapping up? 15:59:04 Yup, Does anyone have anything else? 15:59:41 Thanks everyone! Have a wonderful week! 15:59:45 thank you! 15:59:49 TheJulia: ty 15:59:49 thanks! 15:59:51 ty 16:00:24 #endmeeting