Thursday, 2026-07-16

opendevreviewDavid proposed openstack/watcher-dashboard master: Add HTTPS certificate error handling for Playwright tests  https://review.opendev.org/c/openstack/watcher-dashboard/+/99606909:04
opendevreviewDavid proposed openstack/watcher-dashboard master: Use ID-based selector for login button  https://review.opendev.org/c/openstack/watcher-dashboard/+/99621509:06
opendevreviewDavid proposed openstack/watcher-dashboard master: Add Playwright tests to validate goals and strategies  https://review.opendev.org/c/openstack/watcher-dashboard/+/99606709:06
opendevreviewDavid proposed openstack/watcher-dashboard master: Use ID-based selector for login button  https://review.opendev.org/c/openstack/watcher-dashboard/+/99621509:09
jgilaberHi all! IRC meeting starting in ~1 hour add your topics to the agenda https://etherpad.opendev.org/p/openstack-watcher-irc-meeting#L3112:01
opendevreviewMerged openstack/watcher-dashboard master: Add HTTPS certificate error handling for Playwright tests  https://review.opendev.org/c/openstack/watcher-dashboard/+/99606912:08
opendevreviewMerged openstack/watcher-dashboard master: Use ID-based selector for login button  https://review.opendev.org/c/openstack/watcher-dashboard/+/99621512:08
jgilaber#startmeeting watcher13:00
opendevmeetMeeting started Thu Jul 16 13:00:31 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:00
morenodo/13:00
jgilabercourtesy ping: dviroel amoralej  sean-k-mooney chandankumar rlandy13:01
amoralejo/13:01
dviroelo/13:01
rlandyo/13:01
jgilaberlet wait another minute and we'll get started13:01
jgilaberyou can add topics to the agenda in the meantime https://etherpad.opendev.org/p/openstack-watcher-irc-meeting#L3113:02
jgilaberlet's start with the first topic13:03
jgilaber#topic Priority Label is on13:03
chandankumaro/13:03
jgilaber#link https://review.opendev.org/c/openstack/project-config/+/99588613:03
jgilaberI guess dviroel added this?13:03
dviroeloh yeah13:04
jgilaberthe patch merged and the label is avilable now13:04
jgilaberI don't think we've used it yet?13:04
dviroelyes, we can already set a priority to changes in watcher repois13:04
dviroelbut yeah, I didn't use it yet13:04
dviroelso for higher priority changes we can start using it13:04
dviroelwhich I don't think we have one atm13:05
dviroelbut yeah, just to mention that 13:05
amoralejhow can we set it?13:05
dviroelsince we decided this a few meetings ago13:06
sean-k-mooneyo/13:06
sean-k-mooneyamoralej: you shoudl just be able to set it when you click reply13:06
dviroelamoralej: you should see below your vote options13:06
sean-k-mooneyin gerrit the same as when you leave +/-113:06
amoralejI see it now, thanks!13:06
sean-k-mooneyit will break your musel memory however13:06
sean-k-mooneyso be prepared to think your +w'ing something or +2ing ad set the priorty instead13:07
sean-k-mooneydefinetly not speakign for experince in nova...13:07
jgilaberthanks dviroel, any other comment before moving on?13:09
dviroelno, just to mention that is available now 13:09
dviroelthanks13:09
jgilaberack, next topic13:09
jgilaber#topic Watcher releases for stable branches done13:10
jgilaber#link https://review.opendev.org/c/openstack/releases/+/99594213:10
jgilaberwe merged the patch to publish a milestone 2 release of the stable branches13:10
jgilaberfor all of them13:10
jgilaberthere is a bit more detail on the patch, just wanted to highlight it here13:10
dviroelnice jgilaber++13:10
dviroelack, the security patch got in all, which is great13:11
jgilaberso I believe we can continue unless there are questions?13:11
dviroels/got/got merged13:11
dviroel++13:11
jgilaberok, moving to reviews13:12
jgilaber#topic Reviews13:12
amoralejthanks jgilaber 13:12
jgilaber#link https://etherpad.opendev.org/p/watcher-2026.2-status13:12
jgilaberthis is the status etherpad where we have a good list of patches up for review13:12
jgilaberdoes anyone want to higlight anything?13:13
dviroeli would call out the initial part of audit pipeline feature13:13
jgilaber#link https://etherpad.opendev.org/p/watcher-2026.2-status#L4013:13
dviroelwhich is the default_parameters for audit-template13:13
dviroel#link (core) 993453: Add default_parameters support to Audit Templates | https://review.opendev.org/c/openstack/watcher/+/99345313:14
dviroel#link (client) 993661: Add default_parameters support to Audit Template | https://review.opendev.org/c/openstack/python-watcherclient/+/99366113:14
dviroel#link (tempest) 993672: Add API tests for audit template default_parameters | https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/99367213:14
dviroelthese 313:14
amoralejI just came back from pto but i will review it 13:14
dviroelthey can be merged earlier, before all audit-pipeline feature proposal13:14
jgilaberI saw those and have them in my review list as well13:15
jgilaberbut I might get to them next week13:15
dviroelthe rest of the patche can wait a bit, until we get all ready13:15
dviroelthey are partially validated, and may required changes based on the core functionality work13:15
dviroelbut if you have cycles, are good for a initial review too13:15
dviroelbut lets focus first in the 3 mentioned above13:16
dviroelthanks amoralej jgilaber 13:16
jgilabersounds good dviroel, any questions on this patches?13:16
jgilaberok, moving to morenod's dashboard patches13:17
jgilaberwe have three, but the first two are already merged13:17
jgilaber#link https://review.opendev.org/c/openstack/watcher-dashboard/+/99606713:17
jgilaberthat is the remaining one13:17
dviroeli am reviewing it now yeah13:18
jgilaberdo you want to highlight anything morenod?13:18
morenodthanks dviroel13:18
morenodjust what we talked last week13:18
morenodI did updated the https one to always check https by default on zuul jobs13:18
morenodthe var will be available for us to disable it on our local labs, but jobs will verify https13:19
dviroel++13:19
jgilaber+1, that seems like a good default, thanks for working on this13:19
jgilaberthat was the last point in the agenda, do we have any last minute topic to discuss?13:20
chandankumarI have two watcher-dashboard reviews that needs attension13:21
jgilabersure, go ahead chandankumar 13:21
chandankumar976594: Add Playwright integration test for skip action workflow | https://review.opendev.org/c/openstack/watcher-dashboard/+/976594 - skip action workflow test13:21
chandankumarAnd another one is 996062: Address review comments on Playwright E2E framework | https://review.opendev.org/c/openstack/watcher-dashboard/+/996062 - it is a follow up13:22
chandankumarfrom the playwright poc review feedback13:22
dviroeladding them to the end of the review etherpad13:24
dviroelnot sure if were there already13:24
jgilaberwas going to suggest that as well thanks dviroel 13:24
dviroeltogether with morenod one13:24
chandankumarthat's it from my side! thank you!13:24
jgilaberok, looks like we've reached the end of the agenda, since dviroel++ volunteered to chair next week13:26
jgilaberany last minute comment before closing?13:26
sean-k-mooneysorry a littel distacted with a downstream conversation in parralel13:27
dviroeljgilaber++ thanks for chairing the last 2 meetings13:27
sean-k-mooneyim reading back periodicly13:27
morenodthanks jgilaber++13:27
jgilaberno problem sean-k-mooney do you want to raise anything before we close?13:27
jgilaberwe've had a short agenda today13:28
jgilaberclosing then, if something comes up we can always chat in the channel13:29
jgilaberthanks all for attending!13:29
jgilaber#endmeeting13:29
opendevmeetMeeting ended Thu Jul 16 13:29:19 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:29
opendevmeetMinutes:        https://meetings.opendev.org/meetings/watcher/2026/watcher.2026-07-16-13.00.html13:29
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/watcher/2026/watcher.2026-07-16-13.00.txt13:29
opendevmeetLog:            https://meetings.opendev.org/meetings/watcher/2026/watcher.2026-07-16-13.00.log.html13:29
amoralejThanks jgilaber for chairing!13:31
sean-k-mooneyamoralej: os while you were away i was reflecting on the funtional testing13:31
amoralejand? :)13:31
sean-k-mooneyi see your point13:31
amoralejabout any specific part?13:31
sean-k-mooneyin nova we normally want to model no trivial nova toplogy and we want to do that programticly for nova13:32
sean-k-mooneybut for the fixture that emulate cidner and neutron13:32
sean-k-mooneywe startd form a baseline of static dicts in memory with some helper fucniton and classes aorund that13:32
sean-k-mooneyamoralej: so in watcher its constnet to treat nova the way nova treats neutoron13:32
sean-k-mooneyits a external service that we can have a reletively static toplogy for13:33
sean-k-mooneyand as such codifying it move via data then impertivly is ok13:33
amoralejso, you mean about expressing topologies as dicts, right?13:35
dviroelright, but for watcher, the nova/cinder content is the non trivial topology that we need to handle13:37
dviroeli think that for more complex scenarios, the dicts are hard to read/maintain13:37
amoralejso, what'd you propose? using some kind of classes instead?13:40
dviroelyes, something that would generate a topology. Otherwise, how would we test in larger topologies? I don't think that upload a large json/xml would be a good option.13:47
dviroeli'm thinking on scaling tests in the future13:47
dviroeli also how we could easily modify existing test topologies13:48
dviroelif we want to add sche_hints info, i would need to update all existing topologies around, like we do for the xml (or try to do at least)13:48
dviroelwe could still support simple dicts as input I think, but would be good to have a way to generate larger ones, that would make our life easier to maintain them13:50
amoralejSo "something that would generate a topology", what do you mean? that's beyond the fact of using simple freeform dicts or Server, Instance, Volume, etc... objects13:57
amoralejright?13:57
amoralejyou mean expressing the topology description instead of each element?13:58
dviroelyes, i could think on using objects only, that would allow us to build topologies using python loops for example14:06

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