Thursday, 2025-03-13

opendevreviewJamesLin proposed openstack/watcher-specs master: feat(spec): disable cold/live migration for host maintenance strategy  https://review.opendev.org/c/openstack/watcher-specs/+/94387303:27
mtembo#startmeeting Watcher IRC Weekly Meeting - 13 March 202512:00
opendevmeetMeeting started Thu Mar 13 12:00:33 2025 UTC and is due to finish in 60 minutes.  The chair is mtembo. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
opendevmeetThe meeting name has been set to 'watcher_irc_weekly_meeting___13_march_2025'12:00
mtemboo/ hello everyone12:02
rlandyo/12:02
dviroelo/12:02
marioso/12:02
chandankumaro/12:04
amoralejo/12:05
mtemboThank you for joining12:07
mtembowe shall start with todays agenda12:07
mtembo#link https://etherpad.opendev.org/p/openstack-watcher-irc-meeting12:07
mtembo#topic vPTG:12:08
mtembo#link Registration: https://ptg2024.openinfra.dev12:09
dviroelbtw, the link says 2024 but it actually points to 2025 registration12:10
mtembo#link ptg schedule: https://ptg.opendev.org/ptg.html12:11
dviroelmarios++ for booking slots for watcher12:12
mariosthanks dviroel was very easy just irc commands to the bot 12:12
mariosfor reference, the relevant irc channel for the ptg is #openinfra-events12:13
dviroelso we have monday, tuesday and wednesday, from 13:00 to 17:00 UTC scheduled12:15
dviroeli started to add topics to the official etherpad12:16
dviroel#link https://etherpad.opendev.org/p/apr2025-ptg-watcher12:16
dviroelI actually copy the ones from our meeting agenda, and already assigned 2 of them for myself12:17
dviroelso if you have interested on driving the discussion of one of these topics, or any other topic, please add your name at the topic name12:17
dviroelwe can also move topics around, and the the topic duration was just a initial proposal12:18
amoralejI can take the watcher-dashboard one12:19
dviroeli was just avoiding adding topics to wednesday for now, since we still don't have too much of them12:19
dviroelamoralej++12:19
dviroelnot sure if jneo8 wants to keep its topic at the ptg, so we can wait for a confirmation12:20
rlandydo you have anyone running the tech debt slot?12:20
rlandybecause we need that one12:20
dviroelsince jneo8 already started its spec and there is already some discussion about the design there12:20
amoralejalso, i wouldn't mind to take the one "Workflow/API related" in nobody else wants12:20
chandankumarI will take techdebt one12:20
rlandythank you chandankumar 12:21
dviroelthanks chandankumar and amoralej 12:21
rlandyso what's missing?12:21
chandankumarDo we need to combine all strategies one in a single one? or we need multiple volunteers there?12:21
rlandycross nova and strategies?12:21
rlandysean-k-mooney: did you want to runs one?12:22
amoralejwrt the watcher-dashboard one, i'd like to reschedule as some work on it may depend on decissions related to api changes12:23
dviroelchandankumar: from the meeting etherpad we defered a couple of topics to future ptgs, so only noisy neighbor stands on the ptg etherpad12:23
sean-k-mooneyam undecieded12:23
chandankumaryes correct12:23
amoralejah, sorry, forgot it, it already has an slot before :)12:23
sean-k-mooneyi will deffenitlly be poping in and out of both the nova and watcher ptg slots12:23
sean-k-mooneyso at least for that topci in the nova room ill lead it12:23
sean-k-mooneyon the watcher startige front the ones i was most interested in i think can wait till after the ptg12:24
sean-k-mooneyor later in the week12:24
sean-k-mooneyi.e. based on the feeback form nova i might have a followup for use to dicuss as a watcher group but we could do that via the spec if we proceed with it this cycle12:25
dviroel #link https://etherpad.opendev.org/p/nova-2025.2-ptg#L6112:25
dviroelfyi, the nova topic that sean-k-mooney mentioned12:26
sean-k-mooneysorry for missing the start of the meeting by the way12:26
sean-k-mooneyi was responding ot an email that is related to that topic12:26
dviroelsean-k-mooney: np12:26
sean-k-mooneya person has been recently asking about mem pressure/avpaiableity aware schduling12:27
sean-k-mooneys/avpaiableity/free/12:28
mtemboMoving on to the next topic...:12:29
rlandydviroel: checking with joan if he wants some involvement in the strategies discussion12:29
mtembo#topic Bug Triage:12:29
dviroelrlandy: ack, thanks12:29
mtembo#link https://bugs.launchpad.net/watcher-tempest-plugin/+bug/209973712:30
dviroeli openned this one against tempest-plugin, since I was hitting this issue more frequently with prometheus datasource12:31
dviroelthere were some patches merged to mitigate the issue, with a waiter  on compute model update, added to each test that creates instances and fake metrics12:32
dviroelshould we close this bug, from watcher-tempest-plugin pov?12:33
sean-k-mooneyhave you seen the failures reduce or stop12:33
dviroelno, i didn't see it happening again12:34
sean-k-mooneyideally the commit that was adding the weither woudl have had `Close-Bug: ####` or `Related-Bug: ####` in the commit12:34
sean-k-mooneyif we use those properly as we are ment to the it wil automaticlly get moved to fix released wehn it merges12:35
sean-k-mooneywell wehn the Close-Bug patch merges12:35
sean-k-mooneyso in this case i gues it didnt clsoe because only Related-Bug was used12:35
dviroelyes12:35
sean-k-mooneyso ya let fix the status and move on since the commeits are already properly linked in the history12:36
dviroel+112:36
mtembomoving to fix committed 12:37
sean-k-mooneywe do not use that12:37
sean-k-mooneywe only use fix released12:37
dviroeli already moved to fix released12:38
mtembo+112:38
mtembolink:     https://bugs.launchpad.net/watcher/+bug/2101054 12:38
sean-k-mooneycontext: in theory all openstack poject are reuqired to supprot direct install form master so we consider an patch to be released once its merged12:39
dviroelas discussed in the previous meeting, I create a new bug based on this one https://bugs.launchpad.net/watcher/+bug/209837412:39
dviroelsean-k-mooney: ack, thanks for the context12:40
sean-k-mooneyso last time we said there were kind of 2 bug12:40
sean-k-mooneyone is the key error in the stragy which may or may not have been a result of the model caching12:41
sean-k-mooneyand the other was an architeual problem with how continus audits are expressed12:41
sean-k-mooneyso i think https://bugs.launchpad.net/watcher/+bug/2101054  is valid and should be used to track the key error12:42
sean-k-mooneywe shoudl handle the instance not being in the workload_cache12:42
sean-k-mooneyin the workload_balance stagey or in general12:43
sean-k-mooneyso i woudl triage that as medium12:43
sean-k-mooneyhttps://bugs.launchpad.net/watcher/+bug/2098374 we discussed need more tought and perhasp api chagnes12:43
sean-k-mooneyso i think that is fine as is and we can revisit when we have more time12:44
dviroelagree, moved to triaged and Medium12:44
mtembo#link https://bugs.launchpad.net/watcher/+bug/209870112:45
sean-k-mooneyso that a feature request i think12:46
sean-k-mooneyso triaged and wishlist with the RFE tag?12:46
sean-k-mooneyi dont think it can do this today. in theory aggreate are not meent to schdulable like this in nova but watcher could comptue whihc host to use itslef and specify it so wtacher could supprot this12:47
dviroelyeah, AFAIK there is no way to that today 12:47
dviroels/to/to do12:48
sean-k-mooneyone thing the requestiong may not fully undersand is that aggreates can and often do overlap12:48
sean-k-mooneyso you cna have a single compute host in many aggreates at once12:48
sean-k-mooneyso when they say within the same aggreate if the currnt host has 5 aggrates is it the uniqe intersection fo all 5 or any host in any of the 512:49
sean-k-mooneyits not a tivial thing to do right when you take into account schduler hinit and otgher factors12:50
sean-k-mooneyso while i think watcher could do this it would not be high on my list to do in the short term12:50
sean-k-mooneyill leave a commenet and set it to triaged and wishlist if we agree and we can move on12:51
dviroelack, thanks sean-k-mooney 12:52
amoralejsean-k-mooney, for me to understand, nova can not force placement of a vm in a specific aggregate?12:52
amoralejs/placement/scheduling/12:52
sean-k-mooneycorrect it cannot12:54
sean-k-mooneyvms are not assocated with aggreated in nova12:54
sean-k-mooneycomptue nodes are12:54
amoralejbut via flavors metadata, i.e.12:54
sean-k-mooneyyou can use aggreate metadta and flavor extraspces and image propeteis to create assocation between those concepts12:55
sean-k-mooneybut the vm is only trasisitvly assocated with the aggreates12:55
amoralejok, so that's "indirect" assignment12:56
amoralejthat's what is in https://docs.openstack.org/nova/latest/admin/aggregates.html iiuc12:56
sean-k-mooneyright so aggreates are not ment to be visable in the api when schduling12:56
sean-k-mooneythat are internal to the scheduler12:56
sean-k-mooneybut they are not inteded to be refernce directly12:56
sean-k-mooneythink of them more as configuration for the filters 12:57
sean-k-mooneyand ways to map metadta to hosts12:57
amoralejbut in that case, we watcher ask nova to schedule the migration destination, it would do that12:57
sean-k-mooneyright if we specify a host12:57
amoraleji mean, if using that "indirect" way12:57
sean-k-mooneythen nova will evaluate if that host is approparte12:58
sean-k-mooneyand eter allow it or reject it12:58
amoralejso, if the user implements that in flavor and aggregate, they actually would get "kind of" what they are looking for in the bug12:59
sean-k-mooneyif you let nova chose the host yes12:59
mtemboso this goes to wish list 12:59
mtembo?12:59
sean-k-mooneyyes im leaving a comment and updating it12:59
amoralejif not, nova will not allow the migration and fail, i understand13:00
mtembothank you13:00
amoralejthanks for the clarification sean-k-mooney 13:00
mtembothank you all for todays meeting. 13:00
mtemboI will go ahead and end the meeting now. 13:01
mtembothank you 13:01
dviroelthanks mtembo o/13:01
chandankumarmtembo: ++ thank you for running the meeting :-)13:01
mtembo#endmeeting13:01
opendevmeetMeeting ended Thu Mar 13 13:01:49 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:01
opendevmeetMinutes:        https://meetings.opendev.org/meetings/watcher_irc_weekly_meeting___13_march_2025/2025/watcher_irc_weekly_meeting___13_march_2025.2025-03-13-12.00.html13:01
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/watcher_irc_weekly_meeting___13_march_2025/2025/watcher_irc_weekly_meeting___13_march_2025.2025-03-13-12.00.txt13:01
opendevmeetLog:            https://meetings.opendev.org/meetings/watcher_irc_weekly_meeting___13_march_2025/2025/watcher_irc_weekly_meeting___13_march_2025.2025-03-13-12.00.log.html13:01
rlandymtembo++ thank you13:01
opendevreviewOpenStack Release Bot proposed openstack/watcher stable/2025.1: Update .gitreview for stable/2025.1  https://review.opendev.org/c/openstack/watcher/+/94425313:51
opendevreviewOpenStack Release Bot proposed openstack/watcher stable/2025.1: Update TOX_CONSTRAINTS_FILE for stable/2025.1  https://review.opendev.org/c/openstack/watcher/+/94425413:51
opendevreviewOpenStack Release Bot proposed openstack/watcher master: Update master for stable/2025.1  https://review.opendev.org/c/openstack/watcher/+/94425513:51

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!