16:00:09 #startmeeting nova 16:00:10 Meeting started Tue May 25 16:00:09 2021 UTC and is due to finish in 60 minutes. The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:13 The meeting name has been set to 'nova' 16:00:18 o/ 16:00:19 o/ 16:00:23 \o 16:00:30 \o 16:00:33 lets soo how many of us got the memo :) 16:00:37 /soo/see 16:00:40 o/ 16:01:23 o/ 16:01:42 #topic Bugs (stuck/critical) 16:01:47 no critical bug 16:01:52 #link 9 new untriaged bugs (-3 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 16:02:09 s/-3/+1/ sorry i forget to update that number 16:02:20 still we are pretty OK regarding the triage backlog 16:02:52 is there any specific bug we need to talk about today? 16:03:55 #topic Gate status 16:04:03 We have one gate issue reported by lyarwood #link https://bugs.launchpad.net/nova/+bug/1929446 16:04:04 Launchpad bug 1929446 in OpenStack Compute (nova) "check_can_live_migrate_source taking > 60 seconds in CI" [Undecided,New] 16:04:47 * gibi haven't looked into it yet 16:05:05 ok so that could be just a slow node? 16:05:26 but we might also need to consider should it use teh long rpc timeout 16:05:28 I don't know how frequent it is and lyarwood is not around 16:06:27 anyhow if somebody has time to check it a bit deeper then talk to Lee about it 16:06:57 good luck for finding the reason 16:07:13 if the agent is pasueing 16:07:39 it could be doe to an internal lock like the libvirt proxy issue we had before 16:07:42 o/ 16:08:28 but ya it wont be striat forward to see why it stoped for ~82 seconds 16:09:00 would be nice to see how frequently we are hittig this issue. If it is infrequent then I might ignore it :) 16:09:20 making that a long call rpc is just going to hide why that is happening, 16:09:26 and if it shouldn't, I'm not sure that's good 16:09:38 maybe it makes a blocking libvirt call? 16:09:45 dansmith: and also it is still tight to the sync API response 16:10:01 dansmith: that is what i was wondering regardign the libvirt proxy apis 16:10:02 ah, well, in that case definitely not 16:10:22 sean-k-mooney: yeah I think there are some cases where libvirt can get hung up and then we block, IIRC 16:10:43 there were i think we fixed the ones we knew of but there could be others 16:10:51 right, I mean.. bugs. 16:11:12 im not sure how to sech for this in kibana though 16:11:32 probably don't need to hold up the meeting for this tho 16:11:39 true 16:11:43 OK, moving on 16:11:55 Placement periodic job status #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly 16:11:57 they are green 16:12:15 is there any other gate issue we need to talk about? 16:13:08 oh one more thing. the default ovs->ovn switch in devstack has been merged again 16:13:14 https://review.opendev.org/c/openstack/devstack/+/791436 16:13:21 so we might see failure 16:13:32 as far as I know neutron got hit by it 16:14:15 if no other gate issue then 16:14:21 #topic Release Planning 16:14:30 Today is a spec review day. I see good progress on the spec reviews. Keep it coming! 16:15:00 we have M1 on Thursday. I think the only work we have is to approve the lib release patches if any 16:15:40 any othe release related topic? 16:15:47 I am still composing spec for POST servers on host, should be ready after 1 hr or so. 16:16:08 gmann: ack 16:16:12 gmann: ack, no worries, we only do spec freeze at M2 16:16:30 yeah just to get the review flow in spec day :) 16:16:31 and we do not have a propsal freeze anymore 16:16:46 :) 16:17:14 #topic Stable Branches 16:17:21 copyying elod's summary 16:17:27 stable/train branches were tagged with train-em today ( https://review.opendev.org/790761 ) 16:17:32 wallaby..rocky branches gates should be OK (merged patches in rocky, train, wallaby since the last meeting) 16:17:37 queens and pike gate not yet fixed (the devstack patch that fixed rocky's gate fails with some unit tests on queens and pike - https://review.opendev.org/791248 ) 16:17:40 EOM 16:18:06 one thing to note 16:18:06 I'll try to investigate the queens patch failure 16:18:14 elod: thanks 16:18:22 (and pike) 16:18:28 os-vifs stable gates are broken due to lower-constratins and hack/pep8 rules issues 16:18:37 im going to try and fix those if i can 16:18:53 elod: for unit test fix https://review.opendev.org/c/openstack/devstack/+/792048 16:19:00 elod: this needs to be backported 16:19:05 sean-k-mooney: I've fixed several like that, so if you need help... :) 16:19:22 elod: ill ping you if i get stuck 16:19:26 gmann: oh, thanks! I'll backport it then! 16:19:41 sean-k-mooney: ++ 16:19:59 maybe one more thing, 16:20:22 I am planning to propose (multiple) ocata-eol patches 16:20:36 as nova gate is broken for ~ a year 16:20:44 elod: did, and for queens/rocky I will cap the nodeset as they should not be running on Focal there https://review.opendev.org/q/Ie002faf4c96ac7f207207a481c057b8df0289e6c 16:21:48 gmann: thanks! 16:22:20 anything else on stable? 16:22:42 I think that's it from me 16:23:36 #topic Sub/related team Highlights 16:23:40 Libvirt (bauzas) 16:23:53 nothing to report, sir. Quiet period. 16:24:01 thanks 16:24:02 #topic Open discussion 16:24:06 we have two topics 16:24:11 (artom) Follow up on the IRC meeting schedule change. 16:24:20 (I'm not sure this is not just a remainder from last week) 16:24:25 Doh, forgot to take that off the wiki 16:24:28 That was for last week 16:24:31 ack 16:24:34 I have one addendum 16:24:56 #link http://lists.openstack.org/pipermail/openstack-discuss/2021-May/022684.html 16:25:14 Sam requested a chinees friendly meeting slot 16:26:10 restoring the bi weeksly alternet slots or an addtional one 16:26:13 If I chair a meeting once a month on Thurday 8:00 UTC, how many of you would join.(looking at folks from EU) 16:26:22 ? 16:26:33 sean-k-mooney: I think it would be an additional slot 16:27:12 gibi: am if iwas in an NA/Aisa frindly slot i would be more likely to join :) so i doubt i will be tere unless i did not sleep well 16:27:23 Too early for me, I'm afraid. I'm rarely concious at that point. I could show up if explicitly requested but that would be about it 16:27:51 oh, wait - that's 9am during the summer 16:28:06 I'd be around for that (during the summer) 16:28:07 well for the rest of this year 16:28:26 we are ment to nolonger have daylight saving across europe next year right 16:28:37 I wouldn't count on it 16:28:55 oh is it? 16:29:00 gibi: If it was 9:00 UTC I could reliably be there, fwiw 16:29:24 but 08:00 UTC would work until October or whenever the clocks change 16:29:53 lyarwood has a kid and would gladly be there at 06:00 UTC, I'm sure :P 16:29:59 :P 16:30:10 bauzas: any view from you? 16:30:18 haven't we said last week that we could have some kind of open session ? 16:31:09 bauzas: we might not repeate the todays agenda, but have just is-there-any-topic-for-today agenda point 16:31:31 http://eavesdrop.openstack.org/meetings/nova/2021/nova.2021-05-20-16.00.log.html#l-120 16:31:42 bauzas: were you thinking of just doing it in the nova channel rahter then a dedicated meeting room? 16:32:19 can I use \#startmeeting in nova? 16:32:26 i think so 16:32:28 yes, 16:32:28 I think you can 16:32:31 we do for QA 16:32:31 coo 16:32:32 l 16:32:32 i have seen other channels do it 16:32:32 tc meetings happen in -tc 16:32:39 yeah tc too 16:32:47 sean-k-mooney: yup 16:32:50 bauzas: 9:00 UTC is better for you too? 16:32:51 like TC does https://governance.openstack.org/tc/#meeting-office-hour 16:33:33 that would be 17:00 in china 16:33:34 gibi: well, I'd need to go to a school around 9.20UTC every week in the summer time 16:33:45 so end of day but not late 16:33:56 but I don't want to not accept it because of me 16:34:09 hence the office hour 16:34:21 You don't not want to refuse to not decline it? 16:34:23 OK, so you could be with us for the first 15 minutes? 16:34:32 gibi: yup, I can 16:34:35 cool 16:34:39 artom: indeed 16:35:00 then lets try 9:00 UTC once a month, on #openstack-nova with an office hour style 16:35:17 (y) 16:35:26 which day ? 16:35:34 Tuesdays ? 16:35:36 Tueday does not work for me 16:35:46 Thursday would be better 16:36:09 and what about Mondays ? 16:36:11 maybe jsut do another poll 16:36:37 bauzas: Monday works 16:36:37 I'd prefer to have this kind of office hour be close to a nova meeting 16:36:41 9am on a monday you masochist :P 16:36:53 sean-k-mooney: ah, right 16:36:59 a poll would probably be best 16:37:03 9:00 UTC is 11:OO CEST ;) 16:37:04 ill be asleep most likely so dont work around me 16:37:05 people need to move to France, I guess 16:37:15 actually, I'll propose this 16:37:19 since we won't capture everyone here 16:37:26 OK, I will set up a poll 16:37:34 (also, I've a meeting a 9:15 Mondays already so that wouldn't work) 16:37:40 (joking, just in case people think about it :p ) 16:37:56 moving on as we have another topic 16:37:57 another meeting, yay \o/ 16:38:03 (gmann) Nova feedback on Freenode situation 16:38:04 http://lists.openstack.org/pipermail/openstack-discuss/2021-May/022675.html 16:38:04 the only thing ill say is if you want to avoid bank holidays mid week is best and not the first week in the month 16:38:49 sean-k-mooney: that depends on the country ;) 16:38:50 on Freenode discussion, this is etherpad to provide nova option #link https://etherpad.opendev.org/p/feedback-on-freenode 16:39:07 I've seen this etherpad :( 16:39:17 to be clear, some projects want to leave freenode right now, without letting the current situation settle or have our infra in place on another network 16:39:25 this is to get feedback from project for TC to decide the next step 16:39:28 I'm hoping nova will vote to just "wait and see" for the moment 16:39:29 looks like someone advocated 16:39:43 dansmith: +1000 for me 16:39:49 I too vote for "wait and see" 16:39:58 we can vote 16:40:06 #startvote there it goes :p 16:40:07 Only the meeting chair may start a vote. 16:40:19 #help startvote 16:40:21 well its more come to a concenus 16:40:28 do we need a formal vote? 16:40:33 I don't think so 16:40:34 nah, was kidding 16:40:48 if we do, then fine, but if nobody objects to wait-and-see ... 16:40:49 I have no hard opinion. freenode still works for me 16:40:50 yeah, not needed as such 16:40:54 cool 16:41:00 do people have other concerns ? 16:41:01 please object loudly if you want to move now 16:41:08 yup 16:41:16 i think if the majroity start moving we shoudl 16:41:24 who ? 16:41:32 as far as I understand infra is preparing for the move even if we chose to wait 16:41:36 to not split thing but im already conented to both upstream and downstream irc networks 16:41:38 I only saw *some* folks wanting to move 16:41:45 so havign a third is not realy a big deal to me 16:41:49 but I'm not sure we have consensus on moving 16:41:54 sean-k-mooney: I think we should only move if the TC and infra people decide to move en masse 16:42:03 ++ 16:42:06 dansmith: that would be my preference also 16:42:08 totally agreed 16:42:11 yeah, my only concern is that if other (significant) projects did start moving, I'd like to go with 16:42:12 the question at the moment is which projects are going to leave without waiting or coordinating 16:42:19 otherwise, I don't care 16:42:26 looks the ship sailed for some of them 16:42:34 tehre have been stament made by some that they will stop using irc for contibutig if we do not move by the end of the week 16:42:52 i will miss them but im not inclidned to move as a result of such statements 16:42:56 well 16:43:20 not the best way to get people on-board, that :) 16:43:23 I understand why people would want to move, but they also need to think about other contributors 16:43:40 and at least we would need to continue using Freenode for a lot of time 16:43:41 stephenfin: or even.. the right way to ensure they're *not* on board :) 16:43:43 it seem ironic and kolla would like to move 16:43:51 move now 16:43:54 touché 16:43:57 just in case some contributors don't see emails 16:44:22 what i might suggest is we start keeping the oftc nova channle open for now but keep freenode as our main channel until it plays out in the TC 16:44:24 gibi: I assume you need to give a vote on behalf of everyone? 16:44:28 as PTL 16:44:35 yes 16:44:38 sean-k-mooney: please, no 16:44:45 based on the above discussion it is Option 1 for nova. 16:44:51 sean-k-mooney: I think we should avoid that.. infra is holding the channel 16:44:54 and I will add that to the etherpad 16:44:58 sean-k-mooney: we need one single channel and we need to redirect folks to the official channel 16:44:59 gibi: thanks! 16:44:59 wfm 16:45:02 sean-k-mooney: yeah that create confusion 16:45:06 dansmith: ok 16:45:07 gibi: +1 16:45:23 bauzas: well i was suggstign redirecting them to freenode for now 16:45:24 thanks. gibi can you please add it to etherpad too. 16:45:36 gmann: I will 16:45:37 ah you mentioend that 16:45:38 sean-k-mooney: I don't see the need 16:45:38 thanks 16:45:45 sean-k-mooney: nothing changes 16:45:58 bauzas: i guess empty channel speaks for its self 16:46:16 but then, two people could discuss 16:46:26 and that's how you split a community 16:46:30 dansmith: do you know if infra has set the topic on those chanels to somehthin glike project X currenlty uses freenode 16:46:51 sean-k-mooney: no, but they're working on making their bots even work over there, so that would be a good first thing when they're ready 16:47:17 ok cool 16:47:38 I don't think they even have a way to delegate ops because their bots need to be modified to work with OTFC's nickserv, etc as I understand it 16:48:23 is there anything else for today/ 16:48:24 ? 16:48:47 nothing from me. 16:49:04 not form me 16:49:18 then thanks for joining 16:49:25 \o 16:49:27 #endmeeting