Thursday, 2026-07-09

opendevreviewDavid proposed openstack/watcher-dashboard master: Use ID-based selector for login button  https://review.opendev.org/c/openstack/watcher-dashboard/+/99621507:47
opendevreviewDavid proposed openstack/watcher-dashboard master: Add Playwright tests to validate goals and strategies  https://review.opendev.org/c/openstack/watcher-dashboard/+/99606707:47
opendevreviewDavid proposed openstack/watcher-dashboard master: Add Playwright tests to validate goals and strategies  https://review.opendev.org/c/openstack/watcher-dashboard/+/99606709:16
opendevreviewDavid proposed openstack/watcher-dashboard master: Add Playwright tests to validate goals and strategies  https://review.opendev.org/c/openstack/watcher-dashboard/+/99606709:59
opendevreviewDavid proposed openstack/watcher-dashboard master: Add Playwright tests to validate goals and strategies  https://review.opendev.org/c/openstack/watcher-dashboard/+/99606710:00
jgilaberHi! The watcher irc meeting will start in ~30 minutes, add your topics to the agenda https://etherpad.opendev.org/p/openstack-watcher-irc-meeting#L3112:30
jgilaber#startmeeting watcher13:00
opendevmeetMeeting started Thu Jul  9 13:00:46 2026 UTC and is due to finish in 60 minutes.  The chair is jgilaber. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
opendevmeetThe meeting name has been set to 'watcher'13:00
jgilaberHi! Who is around today?13:01
sean-k-mooneyacto/13:01
sean-k-mooneyo/13:01
morenodo/13:01
chandankumaro/13:01
jgilabercourtesy ping: dviroel amoralej rlandy13:01
rlandyo/13:01
jgilaberlet's give folks a minute and we can start13:01
jgilaberfeel free to add topics to the agenda meanwhile https://etherpad.opendev.org/p/openstack-watcher-irc-meeting#L3113:02
morenoddviroel and amoralej are out today13:02
jgilaberright, so everyone that usually attends is here13:02
jgilaberlet's get started13:02
jgilaber#topic Review Priority label proposal13:03
jgilaberthis one I guess it's from dviroel13:03
jgilaberhe proposed a patch to add the review prioiry label we discussed last week13:03
jgilaber#link https://review.opendev.org/c/openstack/project-config/+/99588613:03
jgilaberlet's try to review it to agree on the label and meaning for each vote13:04
jgilaberpersonally I think the current state captures well what we discussed in the last meeting13:05
sean-k-mooneyya i think its mergeable as is13:06
jgilaberany comment/question on this topic?13:06
sean-k-mooneytehre is the convertion inline baout the exact wording but i dont think we need ot bikeshed too much on this13:06
jgilaberagreed. We can discuss further in the patch if necessary, moving to the next topic13:08
jgilaber#topic Spec-related changes13:08
jgilaberwe have not merged the spec for preemptible instances 13:08
jgilaber#link https://review.opendev.org/c/openstack/watcher-specs/+/98717113:08
jgilaberwe're past the spec freeze, do we want to merge it for this cycle13:09
jgilaberI think the spec is in a good state to be merged13:09
sean-k-mooneyim currently reading it13:11
sean-k-mooneyi started just before the meeting13:11
sean-k-mooneyi think tis proably close enough that we can proceed with it13:11
sean-k-mooneythe fact the comment form the previosu iteration were not resolved makes it a little harder to review13:11
jgilaberyep, I had to do a bit of scrolling up and down to check some previous conversations13:12
jgilaberit looks like we can discuss further in the review and decide what to do there13:13
sean-k-mooneywell i normally change the base to the version where the comment was left13:13
sean-k-mooneybut ya i will +1 or +2 ocne im doen and we can check with doug later/tomrorow if we want to merge i think13:14
jgilabersounds good to me13:14
jgilabersecond patch13:14
jgilaber#link https://review.opendev.org/c/openstack/watcher-specs/+/99611413:14
jgilaberI pushed a patch adding the dir and files for 2027.1 specs13:14
jgilaberwe have a couple of open specs that we'll want to push there13:15
jgilaberit's just the usual change, just mentioning it here for visibility13:15
jgilaberI don't think we need to discuss much about it, if you see anything wrong with the patch, please flag it in the review13:16
jgilabermoving to the next topic13:16
jgilaber#topic Watcher Dashboard reviews13:16
jgilaberI think this one is from morenod?13:16
morenodyes13:16
morenodall three13:16
morenodfirst 2 are dependencies for running the tests on different environments13:16
morenodthe login one is about make tests working both upstream and downstream, login button is different, so with that change, it work on both13:17
morenodand the https is for envs installed with autosigned https certs13:17
morenodthe real one is the third, for checking that the name and the description of the goals and strategies is correct on the dashboard. I get them from the API and compare13:18
sean-k-mooneythe login button shoudl not be diffent as in it should have the same id13:19
sean-k-mooneyit can have diffent css13:19
sean-k-mooneybut we shoudl not be depenidng on the css13:19
morenodyep, that is what change does, use the ID instead of the text of the button13:19
sean-k-mooneyah cool13:19
sean-k-mooneydo you have links to those  for the meeting logs13:20
chandankumarwe also thought of going like this self.page.get_by_role("button", name=re.compile(r"Sign In|connect", re.IGNORECASE)).click(), but current fix is much easier13:20
sean-k-mooneywe shoudl avoid using names as it woudl break on translation13:21
jgilaberlinks for the patches13:21
jgilaber#link https://review.opendev.org/c/openstack/watcher-dashboard/+/99606913:21
jgilaber#link https://review.opendev.org/c/openstack/watcher-dashboard/+/99621513:21
sean-k-mooneyas a general patther we shoudl alwasy use the ids to select items where possibel13:21
jgilaber#link https://review.opendev.org/c/openstack/watcher-dashboard/+/99606713:21
sean-k-mooney*pattern13:21
morenodagree13:22
sean-k-mooneyits odd your gettign https erros by the way13:22
sean-k-mooneyi think the ignore is fine13:22
sean-k-mooneyits just odd becaue the ca that generates them in devstack should be in the cert store13:23
morenodit is disabled by default btw, you can enable it based on a parameter13:23
sean-k-mooneyand the same shoudl be ture for the certs generated by certmanager in our downstream13:23
sean-k-mooneyyep just noting that when you enable tls in devstack13:24
sean-k-mooneythen tools installed on the host shoudl trust the cert out of the box13:24
sean-k-mooneyim fine with the opt out13:24
sean-k-mooneybut in both our downstream nd upstream ci's it shoudl not be needed nor shoudl it really be needed for local dev but its ok if you dont wnat to enable tls ectra locally13:25
sean-k-mooneyi think we can move on13:27
morenodyep13:27
jgilaberok, moving on, thanks for working on this morenod!13:27
jgilaber#topic Bugs13:28
jgilaberwe have a new bug to triage13:28
jgilaber#link https://bugs.launchpad.net/watcher/+bug/216019513:28
jgilaberthis is valid and known, but it'll probably be too big in scope to be treated as a bug13:29
morenodI created this morning after the errors on the multicell job, but after talking to sean-k-mooney, we probably can close it, as it is not expected that watcher will work with multicell envs13:29
sean-k-mooneywatcher can but only if you use scopes13:29
sean-k-mooneywhich is why i was instient that scopes are part of the core api an must work for all stragies13:29
sean-k-mooneycross cell live migraiton is not a thing at least not today13:30
sean-k-mooneyand cross cell move oeprations are disbaled by default13:30
sean-k-mooneyso the only way to use watcher in a multi cell env13:30
sean-k-mooneyis to have all autid use scops and scope to host within a cell13:30
jgilabercould we add cell info to the model?13:31
morenodthe problem at this moment, is that nova do not provides cell info on the api13:31
sean-k-mooneycells are an internal nova sclaing mechanisum and are intentionl not expsoed via the api today13:31
morenodso we cannot detect cell config when executing the tests13:31
sean-k-mooneyaddign it would be non trivial13:31
sean-k-mooneyit would be possibel but likely take nova changes13:32
sean-k-mooneythe best way to do this would be to have nova's conductors enrole each compute node into a placement aggreate based on the cell they manage13:32
sean-k-mooneycomptue nodes are not ment ot know what cell they are in13:33
sean-k-mooneyso they cannot do that themselves13:33
sean-k-mooneythe info is in the cell mapping tablle in nova api db but its purly used inrenally13:33
jgilaberack, I see, then I think we can close this bug report with a comment summarizing this dicussion13:33
sean-k-mooneyits perhaps a pain point ot raise with the nova team in a future ptg13:33
sean-k-mooneyits not unfixable its just intenrally not expsoed today13:34
morenodwe can ask to create the same host aggregates than cells on multicell jobs, and assume that they are correct, and manage host aggregates as cells in the tests13:34
sean-k-mooneymorenod: that is a workaround yes13:34
sean-k-mooneythat is efectilly what i was suggestign automating in nova eventually13:35
sean-k-mooneymelwitt: just an fyi ^13:35
sean-k-mooneymorenod: jgilaber  for nwo we woudl ned to modify the testign and job config13:35
sean-k-mooneyto be able to supprot this13:35
sean-k-mooneyso it feel like it more hten a bug13:35
sean-k-mooneybut this is a limitation we do need to document upstream and downstream13:36
jgilaberagreed, we could keep it as a wishlist bug if we want to have some tracker until we work on it13:36
sean-k-mooneybut we have many other undocumented limaitons so its not unqiue in that respect13:36
sean-k-mooneyyes that sound good13:37
sean-k-mooneylets keep it wishlist for now13:37
jgilaberok, so I'll do that after the meeting if there is no objection13:37
jgilaberlast thing13:38
jgilaber#topic Volunteers to chair next week13:38
jgilaberany volunteer?13:38
rlandyI can't - have a meeting overlap - will check with dviroel if he can13:39
jgilaberI can do it next week again13:39
jgilaberok, so any last minute topic before closing?13:39
sean-k-mooneyam one but its not urgent13:40
jgilaberwe have the time if you want to raise it13:40
sean-k-mooneyi would like to add a minmial AGENT.md and weekly ubutnu-resolute job in the next few weeks13:40
sean-k-mooneyi havnt really had time to follow up on either but directionally are folks ok with that13:41
sean-k-mooneywe can obviously dicuss this more hwen more folks are around13:41
sean-k-mooneybut its something i was thinking of doing before the end fo the month13:41
jgilaberdid we discuss this for watcher in the PTG or was it a general discussion?13:42
jgilaberI'm +1 on the AGENT.md, the ubuntu job is to test the new version?13:42
sean-k-mooneywe discuss the ai tooling a little but not in depth13:42
sean-k-mooneyjgilaber: yep 13:42
sean-k-mooneyjgilaber: its to test 26.04 before it becomes the default next cycle13:43
sean-k-mooneyso weekly is enough for that13:43
sean-k-mooneyand python 3.14 as a sideffect13:43
jgilaberack, +1 to that as well, good to catch issues early13:43
jgilaberdo we test with 3.14 already?13:43
sean-k-mooneyin unit tests13:44
sean-k-mooneyi added 26.04 supprot to devstack about 2-3 weeks ago13:44
jgilaberok, that is good to hear, thanks for doing this work13:44
sean-k-mooneyso the basic job runs there but im hopign to add weekly/experimtal jobs to more repos 13:44
sean-k-mooneyhttps://review.opendev.org/c/openstack/nova/+/984540/513:45
sean-k-mooneythat is what the nova minimal ai scafold looks like13:45
sean-k-mooneyi and cinder https://review.opendev.org/c/openstack/cinder/+/99400713:45
sean-k-mooneyso im hoping to do the same form cybrog and watcher when i find the time 13:46
sean-k-mooneythe core idea is it stays very minimal wiht the actual guidence in the contibotr docs in human readable prose13:46
sean-k-mooneythis is work that someone else could also do13:47
jgilaberfrom a quick glance looks good, I have a similar setup locally, would be good to standarize13:47
sean-k-mooneyi just wanted to bring this up as a topic i would like to progress13:47
sean-k-mooneyfor now im still a littel reluctant to go mroe then that in the repo i.e. i dont think builidn skils in the repos is somethign we shoudl do yet13:49
sean-k-mooneybut ok i think we can wrap up13:49
jgilabersounds good, thanks!13:49
jgilaberif there is nothing else we cap wrap early and have 10 minutes back13:49
jgilaberthanks all!13:50
jgilaber#endmeeting13:50
opendevmeetMeeting ended Thu Jul  9 13:50:56 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:50
opendevmeetMinutes:        https://meetings.opendev.org/meetings/watcher/2026/watcher.2026-07-09-13.00.html13:50
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/watcher/2026/watcher.2026-07-09-13.00.txt13:50
opendevmeetLog:            https://meetings.opendev.org/meetings/watcher/2026/watcher.2026-07-09-13.00.log.html13:50
morenodthanks jgilaber!!13:51
melwittsean-k-mooney: ack on the nova stuff. I could see there being some "standard" things nova could do internally around cells since they can almost be assumed the hosts in a cell would be an their own aggregate (and additional smaller aggregates could be created around subsets of them by the cloud operator if they desired)16:20
sean-k-mooneyya i was thinkign of somehting along the lines of "auto_report_cell_aggreates=true"16:21
sean-k-mooneyand if we have a standard way to generate the uuid or hostaggate name16:22
sean-k-mooneythen watcher coudl discover either16:22
sean-k-mooneyassuming we didnt just exposee the cell mapping via the api to services/admins16:22
melwittyeah. that is also something to potentially consider16:23
sean-k-mooneywe do already schduler on this internally https://github.com/openstack/nova/blob/master/nova/scheduler/weights/cross_cell.py16:23
melwittI wonder why that didn't "save" the situation? is it not a default weigher or16:24
sean-k-mooneyall weigher are enabled by default16:25
sean-k-mooneybut the issue is that watcher seclects the host 90% of the time16:26
sean-k-mooneyrather then allowign nova too16:26
sean-k-mooneyand sicne watcher does not have this info it cant knwo if it going to succeed or even why it got a no valid host16:26
melwittoh yeah duh lol. watcher not using the nova scheduler16:27
sean-k-mooneyso the info is in the nova api db but there is no rest api for it, the condocor know implictly because it can look at its local cell db for host relathionp and nova scheuelr knows16:28
melwittright16:28
sean-k-mooneybut i dont think there exist a way today for anything esle to know16:28
melwittyeah I was just being dumb16:28
sean-k-mooneyno not at all you did what i do most of the time and assume nova is making the choice16:28
sean-k-mooneythis is porably a good dicsusion to start on the mailing list before the next ptg16:30
sean-k-mooneylike there a a number of ways to impove this but they all need nova changes16:30
sean-k-mooneyand there are pros and cons to each of the approches16:30
melwittyeah, always good to get it out there earlier so people can have a think on it16:30
opendevreviewMerged openstack/watcher master: Generate sample policy file in local directory  https://review.opendev.org/c/openstack/watcher/+/96148617:16
-Guest12850- NOTICE: The Gerrit service on review.opendev.org will be offline briefly one hour from now, at 21:00 UTC, while we rename a project.20:02
opendevreviewMerged openstack/watcher master: Remove redundant policy_file override  https://review.opendev.org/c/openstack/watcher/+/99417820:12
-Guest12850- NOTICE: The Gerrit service on review.opendev.org is going offline momentarily at 21:00 UTC while we rename a project, but will return within a few minutes.21:00

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