Thursday, 2025-12-11

dviroelsean-k-mooney: https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/970472 this was the conflict in the other plugin patch, not sure why it didn't failed before, only now in 2025.2 patch.00:32
dviroels/conflict/syntax error00:33
*** haleyb is now known as haleyb|out00:43
sean-k-mooneydviroel: ah the experimental jobs. ya thats odd that it was not an issue before but ok i guess it didnt faul intally because we had not merged the change in the watchre repo at the time but that is just a guess02:10
opendevreviewMerged openstack/watcher-tempest-plugin master: Fix experimental job names after refactoring watcher jobs  https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/97047206:14
opendevreviewchandan kumar proposed openstack/watcher-dashboard master: [poc] Add Selenium-based E2E testing framework  https://review.opendev.org/c/openstack/watcher-dashboard/+/97057306:28
opendevreviewchandan kumar proposed openstack/watcher-dashboard master: [poc] Add Selenium-based E2E testing framework  https://review.opendev.org/c/openstack/watcher-dashboard/+/97057307:11
opendevreviewchandan kumar proposed openstack/watcher-dashboard master: [poc] Add Selenium-based E2E testing framework  https://review.opendev.org/c/openstack/watcher-dashboard/+/97057307:16
opendevreviewchandan kumar proposed openstack/watcher-dashboard master: [poc] Add Selenium-based E2E testing framework  https://review.opendev.org/c/openstack/watcher-dashboard/+/97057308:14
opendevreviewAlfredo Moralejo proposed openstack/watcher stable/2025.2: Make VM migrations timeout configurable and apply reasonable defaults  https://review.opendev.org/c/openstack/watcher/+/96948308:23
opendevreviewAlfredo Moralejo proposed openstack/watcher stable/2025.2: Make VM resize timeout configurable with migration defaults  https://review.opendev.org/c/openstack/watcher/+/96987708:23
amoralejfor some reason https://review.opendev.org/c/openstack/watcher/+/969370 didn't trigger the gate pipeline, I suspect adding another +W will work08:25
opendevreviewchandan kumar proposed openstack/watcher-specs master: Add spec for improving watcher-dashboard testing  https://review.opendev.org/c/openstack/watcher-specs/+/97022008:38
tkajinamamoralej, isn't that because of https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/969366 in depends-on ?08:40
amoralejtkajinam, damn, i missed that obvious08:41
amoralejactually, we don't need it anymore08:41
opendevreviewAlfredo Moralejo proposed openstack/watcher master: update unit tests for nova_helper module  https://review.opendev.org/c/openstack/watcher/+/96937008:42
amoralejthanks tkajinam 08:42
tkajinam:-)08:50
opendevreviewchandan kumar proposed openstack/watcher-dashboard master: [poc] Add Selenium-based E2E testing framework  https://review.opendev.org/c/openstack/watcher-dashboard/+/97057308:55
opendevreviewAlfredo Moralejo proposed openstack/watcher master: Skip migrate actions in pre_condition phase  https://review.opendev.org/c/openstack/watcher/+/96669909:18
opendevreviewJoan Gilabert proposed openstack/watcher master: Fix zone migration dst pool and type selection  https://review.opendev.org/c/openstack/watcher/+/96471809:56
opendevreviewchandan kumar proposed openstack/watcher-specs master: Add spec for improving watcher-dashboard testing  https://review.opendev.org/c/openstack/watcher-specs/+/97022010:06
opendevreviewchandan kumar proposed openstack/watcher-dashboard master: [poc] Add Selenium-based E2E testing framework  https://review.opendev.org/c/openstack/watcher-dashboard/+/97057310:24
opendevreviewJoan Gilabert proposed openstack/watcher master: Fix zone migration dst pool and type selection  https://review.opendev.org/c/openstack/watcher/+/96471811:16
dviroelsean-k-mooney: hey o/  - can you revote on this https://review.opendev.org/c/openstack/watcher/+/968779 - I added a temp alias for aetos job, since aetos project has this job running in their pipeline too11:41
dviroeli plan to backport this https://review.opendev.org/c/openstack/aetos/+/970468 too once we merge the 2025.2 change11:43
amoralejWatcher meeting is starting in 15 minutes, remember to add your topics to the agenda in https://etherpad.opendev.org/p/openstack-watcher-irc-meeting11:45
sean-k-mooneydviroel: sure done11:48
dviroelty11:48
opendevreviewDouglas Viroel proposed openstack/watcher-specs master: Add spec for Audit Pipeline feature  https://review.opendev.org/c/openstack/watcher-specs/+/96984011:57
amoralejmeeting time!12:01
amoralej#startmeeting Watcher meeting 11-Dec-202512:01
opendevmeetMeeting started Thu Dec 11 12:01:51 2025 UTC and is due to finish in 60 minutes.  The chair is amoralej. Information about MeetBot at http://wiki.debian.org/MeetBot.12:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:01
opendevmeetThe meeting name has been set to 'watcher_meeting_11_dec_2025'12:01
amoralejwho is around today?12:02
rlandyo/12:02
morenodo/12:02
jgilabero/12:02
dviroelo/12:02
amoralejcourtesy ping: sean-k-mooney chandankumar 12:03
chandankumaro/12:03
amoralejlet's start with the agenda12:04
amoralej#link https://etherpad.opendev.org/p/openstack-watcher-irc-meeting#L2312:04
amoralej#topic new blueprint for improving watcher-dashboard testing12:04
amoralej#link https://blueprints.launchpad.net/watcher/+spec/watcher-dashboard-unit-integration-testing12:05
amoralej#link https://review.opendev.org/c/openstack/watcher-specs/+/97022012:05
chandankumaramoralej: I will take it from here12:05
amoralejsure, go ahead12:05
chandankumarAs per the last month irc meeting on Updates on Pytest vs PTI discussion topic12:05
chandankumarhttps://meetings.opendev.org/irclogs/%23openstack-watcher/%23openstack-watcher.2025-11-13.log.html#openstack-watcher.2025-11-13.log.html#t2025-11-13T12:21:5012:05
chandankumar We have to propose a spec for ui testing for watcher-dashboard. 12:05
chandankumarhttps://review.opendev.org/c/openstack/watcher-specs/+/970220 12:06
chandankumarthis spec propose the layout for watcher-dashboard api/dashboard unit testing based on django test framework and it's wrapper in horizon as well as integration/e2e test based on selenium/playwright.12:06
chandankumarwe also have to do a poc for both selenium and playwright.12:06
chandankumarBelow is the poc code for the same. 12:07
chandankumarThe only assumption is that chromium-browser needs to be installed locally. I had issues with firefox gecko driver so went with chromium.12:07
chandankumar970353: [poc]Add Playwright-based E2E testing framework | https://review.opendev.org/c/openstack/watcher-dashboard/+/97035312:07
chandankumar970573: [poc] Add Selenium-based E2E testing framework | https://review.opendev.org/c/openstack/watcher-dashboard/+/970573 patchset 4 working locally12:07
chandankumarThe commit message of both poc contains how to run locally. 12:07
chandankumarIt will generate screenshots in watcher-dashboard repo for each UI interaction.12:07
sean-k-mooneyo/12:08
chandankumarboth poc tests creating audit template, create audit, check for action plan and then delete it as a user workflow12:08
chandankumarHere is my analysis of both the tools: https://gist.github.com/raukadah/a1fe328770af6ddeb860c255632d1b0212:09
chandankumarI am still trying to make selenium one working in ci.12:09
sean-k-mooneyso ironic had to swap to using firefox to get it to work in ci i think12:10
amoraleji understand manila-ui has selenium job running?12:10
chandankumaramoralej: yes, 12:10
amoralejwith chromium?12:10
chandankumaramoralej: i copied the horizon integration tests playbook and modified some of them for chromium12:10
chandankumarsean-k-mooney: I will check the ironic one12:11
chandankumarhere is the playwright one https://zuul.opendev.org/t/openstack/build/dc5ea2f364fd42fb9a43b2011980c67a12:11
sean-k-mooneyhttps://review.opendev.org/c/openstack/ironic/+/96143412:11
chandankumarplaywright has alll the batteries like browser driver bundled in it12:12
chandankumarwe can install it in runtime12:12
amoralejit'd be good to be aligned with other jobs, I guess12:12
sean-k-mooneyon the packaging side we woudl jsut use it form pypi proably via devstack in the job12:12
chandankumarplaywright test log: https://zuul.opendev.org/t/openstack/build/dc5ea2f364fd42fb9a43b2011980c67a/log/job-output.txt#3027612:12
sean-k-mooney"playwright"12:12
sean-k-mooneyi.e. we woudl likely avoid using the disto version12:13
chandankumarhttps://zuul.opendev.org/t/openstack/build/dc5ea2f364fd42fb9a43b2011980c67a/log/job-output.txt#30228 - playwright installing needed drivers12:13
chandankumarplaywright is not packaged in rpm based distro, installing it from pypi works fine with chromium12:13
amoralejalso, it's not in https://github.com/openstack/requirements/blob/master/global-requirements.txt12:14
sean-k-mooney correct adding it is soemthing we will have to do but that not hard12:14
amoralejyep12:14
sean-k-mooneychandankumar: how did you find working with each solution12:14
chandankumarfor firefox, it complains about missing libraries and it does work with the current libraries of Fedora 4312:14
sean-k-mooneyyou provided a summary of the capablity12:14
sean-k-mooneybut DX wise what did you think of the developer experince12:15
chandankumarplaywright one is easier to work as it's documentation with examples is very nice12:15
chandankumarone can start writting by just following the doc12:15
chandankumarin terms of debugging also, it have nice support12:15
sean-k-mooneythat was my perceptiohn form readign the docs but i did not have time to try doing it12:15
chandankumarif a user does not know playwright , they can use playwright codegen12:16
amoraleji was about to ask about codegen12:16
amoralejit works fine? i like that12:16
chandankumarhttps://gist.github.com/raukadah/10297ff008efbcb17308eec8a17ef62512:16
sean-k-mooneythe ohter thing of note is there is a playwright mcp and api is better trained on playwright12:16
sean-k-mooneyso i thihnk tooling wise that is a +12:17
chandankumar"playwright codegen http://10.0.78.89/dashboard/auth/login/ --target=python -o test.py"12:17
sean-k-mooneyhttps://gist.github.com/raukadah/10297ff008efbcb17308eec8a17ef625 is the output of the code gen?12:18
chandankumarsean-k-mooney: yes12:18
chandankumarit will open a browser with url, we need to navigate and we can tweak elements it will generate the code12:19
sean-k-mooneydid it auto add cliong on audit templates aund using dbumy values12:19
sean-k-mooneyoh12:19
sean-k-mooneysorry12:19
sean-k-mooneythat was it recordign you doing that12:19
chandankumarit was recording what I was doing on the ui12:19
sean-k-mooneyso it popped open a broser and recoreded all the step you did and created a file to do that12:20
sean-k-mooneyya that is very nice12:20
chandankumaryes correct12:20
amoralej+1 i like that :)12:20
sean-k-mooneyobviulsy you would need to go in an dadd some asserts but the fact it does the boler plat for the navigation is very helpful12:20
amoralejyes12:21
chandankumarhttps://github.com/seleniumbase/SeleniumBase another selenium project, which have something like codegen but I have not tried it12:21
sean-k-mooneyplaywright also has built in suport for using webkit too without needing a fully browser12:21
chandankumarI tried it with browser and headless mode, we have screenshots in both cases12:22
sean-k-mooneythe webkit verison can run headless i bleive and work on mac also as a stand in for safari testing12:22
chandankumarplaywright creates a zip file with all the data for further debugging and tracing12:23
sean-k-mooneynot that i care too much about testing this in every possibel combinition just noting that it supprot all 3 major browser engines (chromn, firefox and webkit)12:23
chandankumargood point, I will add this criteria in my spec12:23
sean-k-mooneychandankumar: i belive it can also create a video file of failed tests but i have not looked at that in detail12:23
chandankumarsean-k-mooney: video file one I have not tested it12:24
sean-k-mooneychandankumar: well it snot so much a critiva but i like that its not a limitation12:24
sean-k-mooneyi.e. it doesnt only work with one browser12:24
chandankumarit was downloaidng ffmpeg-linux. but I need to check that one12:24
chandankumarfrom ci log https://zuul.opendev.org/t/openstack/build/dc5ea2f364fd42fb9a43b2011980c67a/log/job-output.txt#3027612:25
chandankumarwe can see the debug in realtime what playwright is doing12:25
sean-k-mooneyright so form watching some youtube videos on it i belive you can set it up to recored the browser session and save it as an mp4 or simialr when a test fails so you can then review it12:25
chandankumarI will try that12:25
sean-k-mooney i know it has a screenshot mode which seleinam also supprot too fro smaller output12:26
sean-k-mooneythose baseiclly take sceenshot when they are makign assert or they detect changes12:26
chandankumarwe need to tell the test when to take screenshot12:27
sean-k-mooneyack12:27
amoralejwe don't have the screenshots in the logs in https://zuul.opendev.org/t/openstack/build/dc5ea2f364fd42fb9a43b2011980c67a/log/12:27
amoralejright?12:27
chandankumaryes, I have not collected it12:27
sean-k-mooneywe would have to copy them in the job ya12:27
sean-k-mooneywhich we can do12:27
amoralejyep12:27
chandankumarI will update the spec with browser support, screenshot collection in ci log and video output after failure12:28
amoralejone question about the process, https://review.opendev.org/c/openstack/watcher-specs/+/970220/ is about creating the poc and establishing the comparison and the goal12:28
sean-k-mooneychandankumar: so i need to look at both implementions12:28
amoralejso i understand can/should be approved without need of finishing the pocs, right?12:29
chandankumaramoralej: good question, I was about to ask for the same12:29
amoralejor want to add the result of the decission i nthe same spec?12:29
sean-k-mooneybut what your geneal recommendation. can we get that codeifed into the spec12:29
sean-k-mooneyamoralej: i woudl liek use to document the reaosn why we choose one or the other in the spec and put the non selected one in the alternitives12:30
amoralejack, works for me12:30
sean-k-mooneywe shoudl also refence https://opendev.org/openstack/watcher-specs/src/branch/master/specs/2026.1/approved/testing-and-codequality.rst12:31
sean-k-mooneyor rahter make sure its consitent12:31
chandankumarin inital version of the spec, I have added the code in the spec itself https://review.opendev.org/c/openstack/watcher-specs/+/970220/2/specs/2026.1/approved/improve-watcher-dashboard-ui-testing.rst12:31
chandankumarsean-k-mooney: sure will add it to reference12:32
sean-k-mooneychandankumar: im just bring that up as the deictory stucutre was propsoed in https://opendev.org/openstack/watcher-specs/src/branch/master/specs/2026.1/approved/testing-and-codequality.rst12:32
sean-k-mooneyto make room for the addtion of ui tests12:32
sean-k-mooneyso we shoudl make sure https://review.opendev.org/c/openstack/watcher-specs/+/970220/5/specs/2026.1/approved/improve-watcher-dashboard-ui-testing.rst#77 fits with that12:33
sean-k-mooneyi think it does12:33
sean-k-mooneydo we have more on this topic for today12:34
chandankumarnope12:34
amoralejthanks chandankumar 12:34
amoralejlet's move to the next topic12:34
chandankumarthank you sean-k-mooney amoralej for inputs!12:34
amoralejgreat progress on this!12:34
sean-k-mooneyok lets revisit next week and also review the spec asnc12:34
dviroelchandankumar++12:34
amoralej#topic Meeting schedule proposal -> 202612:34
amoralejrlandy, you want to present this topic?12:35
rlandyyep - I added that ... so we have a lot of vacation over the next couple of weeks12:35
rlandyThe proposal is to have the meeting next week12:35
rlandyskip the week of the 25 and the 1st12:35
rlandyresume on the 8th12:35
dviroel+1 on dec 18th be the last meeting of this year12:35
sean-k-mooney+112:36
jgilaber+1 to the plan12:36
chandankumar+112:36
sean-k-mooneythat is what i was thinkign looking at my calandar too12:36
amoralej+112:36
rlandyok - I can chair the meeting on Jan 8th since dviroel asked12:36
rlandyamoralej, that is all I had there - thank you12:36
amoralej#agreed Watcher meetings on Dec 25th and Jan 1st will be cancelled12:37
amoralej#agreed Watcher will resume regular meeting schedule on Jan 8th12:37
amoralejlet's move on12:37
amoralej#topic Audit Pipeline spec proposal12:37
dviroelo/12:38
dviroelI would like to highlight that there is a new spec proposal12:38
dviroelwe can further discuss the details in the spec itself if folks agree12:38
dviroelthis is already a second version of the proposal12:38
dviroel#link https://review.opendev.org/c/openstack/watcher-specs/+/96984012:38
dviroelthe first proposal was building a solution reusing all existing resources and apis, which ended to be using apis out of their real scope12:39
dviroelnow we have a second version with the following proposal:12:39
dviroel1) extend audit-template to include strategy input parameters (this will allow us to use templates to build a pipeline of strategies)12:39
dviroel2) a new audit pipeline resource, which accepts multiple audit-templates as input, to build a pipeline 12:40
dviroel3) a mutable data cluster model that updates its resources states/properties between strategy executions12:40
dviroel4) a new planner that merges multiple solutions to build a single optimize action plan12:40
dviroelthese are the most important changes proposed12:40
dviroelwe may have some corner cases not covered there yet12:41
dviroelif we start to agree on a initial proposal, I may start a small poc based on that too12:41
dviroeli request that you folks take a look in this spec's proposal and see if is a reasonable proposal and if we are missing something to cover there12:42
sean-k-mooneyat a very high level that sound more reasonable and inlien with the existing data model12:42
sean-k-mooneybut the detail of 3 and 4 are were the complication will lie12:42
sean-k-mooney1 i thikn is independtly useful12:43
amoralejyep, from api pov looks better12:43
jgilabersounds reasonable and I still need to go through the spec, but does the mutable data model cover the metrics?12:43
amoralejin 1, we could add that also for regular audits from audittemplates ?12:43
sean-k-mooneyso i think even if we completed that in this cycle that woudl eb nice, we may want to have that be its own mini spec and just proceed with that in parallel12:44
dviroelamoralej: yes we can12:44
amoralejok12:44
sean-k-mooneyso for 1 i woudl call it default_parmaters and allow the current parmater in teh audit to overried the template12:45
dviroelack, we can spli, since the success of the audit-template changes don't depends on the pipeline feature12:45
sean-k-mooneythat would allwo use to reuse it for any audit type12:45
sean-k-mooneydviroel: we dont nessisarly ned to split the spec althoguh we can12:45
sean-k-mooneyi just think we could split the impemetion and deliver the template changes first12:45
sean-k-mooneyto avoid one big reivew at the end of the cycle12:46
dviroelack, sure, that can be added to this spec too.12:46
dviroelas a 1st phase work items12:46
chandankumarDoes it also require changes in watcher-dashboard ?12:46
sean-k-mooneyit will eventually12:47
amoralejyep12:47
sean-k-mooneyi am not sure that has to hapen in the same cycle12:47
amoralejand new microversion12:47
chandankumarok12:47
dviroelack, it would be a next phase12:47
sean-k-mooneyyes 2 new microveriosn more then likely if we split it12:47
amoralejwe could have one microversion only for 1, so it's independent12:47
dviroelbut yeah, I am not covering that in the spec 12:47
sean-k-mooneyright so microverion to add the parmeter to the template 12:48
sean-k-mooneyand a secodn one for the new pipeline resouces12:48
amoralej+112:48
dviroel+1 better to have 2 microversions12:48
sean-k-mooneywhat we woudl want to compelt htis cycle is the cli supprot12:49
sean-k-mooneyso watcher client extneion to use the new api resouce12:49
dviroel+112:49
amoralejdviroel, we can keep discussing in the spec? or you'd like to highlight something else on the topic?12:51
dviroelright, so 3) and 4) are the more complicated part and I request you folks to take a look12:51
dviroelbut we don't need to discuss here right now, yes12:51
amoralejok, thanks12:51
dviroelwe can continue in the patch itself12:51
amoralejlet's move to the reviews12:52
amoralej#topic reviews12:52
dviroelor ping me in the channel for any further question12:52
dviroeltks amoralej 12:52
amoralej#link https://review.opendev.org/c/openstack/watcher/+/97044012:52
sean-k-mooneyyou spec goes 1,2,4,5  by the way :P12:52
amoralej#link https://review.opendev.org/c/openstack/watcher-dashboard/+/97044612:52
amoralejso that's about ruff12:52
sean-k-mooneyah thats what i just added12:52
amoralejyep12:53
* dviroel sean-k-mooney oops :)12:53
sean-k-mooneyya so takashi notice that on the oslo side and in our defintions12:53
sean-k-mooneywe dont have E5 the line lenght check enabled12:53
sean-k-mooneynow for us that is currently intentional12:53
sean-k-mooneybecause we are suign autopep8 to do the formating and linelenght enforcement12:53
sean-k-mooneybut i kind of wanted to check in and see how people felt on 2 topics converging on ruff for evetything, and if we dont for now fi we want to enable the lenght check in ruff12:55
sean-k-mooneyeven if autopep8 is already doing it12:55
sean-k-mooneyone thing that i notcied when reviewing tkajinam's patch was https://github.com/openstack/watcher/blob/master/tox.ini#L13912:55
sean-k-mooneythe *sqlalchemy/alembic/versions/*12:55
sean-k-mooneypart is disabling style checkign for the alembic migrations12:56
sean-k-mooneywhic i dont know of a good reason to do i think its just there historically12:56
amoralejlikely12:57
amoralejso, i'd be inclined to accept those patchs even if we are still using autopep812:58
sean-k-mooneyim still plannign to add the pre-commit hooks an ruff check to all repos this cycle as we dicussed in the ptg. ill proably try and do that next week12:58
jgilaberI'm +1 on both topics, I've tried the ruff formatter locally and I like it12:58
sean-k-mooneybut i wanted to float the idea of adopting ruff for evertything later in teh cycle and choosing when and see how peopel felt12:59
jgilaberto enable it we'll need to do it in a few patches I guess, it will result in quite a lot of changes12:59
amoralejwill it require many changes in code format?12:59
sean-k-mooneyamoralej: that i need to check but its just running the tool13:00
sean-k-mooneythe approch i was takign was use ruff check to adress all lint issues13:00
sean-k-mooneyso that swapign to ruff for formating shoudl just be whitespace changes for the most part13:00
amoralejwe are out of time13:01
sean-k-mooneyi was thinkign of either doign it just after stable/2026.1 is created and master is start of 2026.2 or at milestone 213:01
sean-k-mooneyya we dont need to decied now13:01
amoralejstarting of next release in master looks like a good idea, imo13:02
sean-k-mooneyif we are ok  with the E5 checks for now we can just review them and loop back to this later13:02
dviroel+1 on E513:02
sean-k-mooneyya i wanted to fidn a time where we woudl not be conflicitng with tryign to get work complete or the code released13:02
sean-k-mooneycool that all i had on that13:02
amoralejthanks13:03
amoralejso, wrt the bug triage, we have some bugs, but in some of them there are already patches or discussion ongoing13:03
amoralejso i guess we can keep working on them asynchronously and discuss in next meeting if needed13:04
dviroel+113:04
amoralejI'd like to highlight https://bugs.launchpad.net/watcher/+bug/2134534 which i sent patch https://review.opendev.org/c/openstack/watcher/+/970396 if you have a chance13:04
amoraleji expect it to be an easy fix13:05
amoralejso we have volunteer to chair next meeting already13:05
sean-k-mooneyoh ya that looks like a clear bug13:06
amoralej#info dviroel will chair next meeting13:06
dviroel:)13:06
amoralejyes, i found it while working in the service_monitor for the applier13:06
amoralejso, i think we can close the mtg here13:06
sean-k-mooneyi just set it to high since we are out of time because of the sacling implication but fee free to update it to medium if you think high is not correct13:07
sean-k-mooneysince you have a patch can you assign it to yourself13:07
amoraleji think high is good13:07
amoralejso thank you for joining!13:08
amoralej#endmeeting13:08
opendevmeetMeeting ended Thu Dec 11 13:08:16 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:08
opendevmeetMinutes:        https://meetings.opendev.org/meetings/watcher_meeting_11_dec_2025/2025/watcher_meeting_11_dec_2025.2025-12-11-12.01.html13:08
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/watcher_meeting_11_dec_2025/2025/watcher_meeting_11_dec_2025.2025-12-11-12.01.txt13:08
opendevmeetLog:            https://meetings.opendev.org/meetings/watcher_meeting_11_dec_2025/2025/watcher_meeting_11_dec_2025.2025-12-11-12.01.log.html13:08
morenodthanks amoralej!13:08
jgilaberthanks amoralej!13:08
dviroelamoralej++13:08
chandankumaramoralej++13:10
opendevreviewAlfredo Moralejo proposed openstack/watcher master: Refactor service monitor for decision-engine  https://review.opendev.org/c/openstack/watcher/+/97061213:10
opendevreviewAlfredo Moralejo proposed openstack/watcher master: Assign hostname to ActionPlan when picked-up  https://review.opendev.org/c/openstack/watcher/+/97061313:10
opendevreviewAlfredo Moralejo proposed openstack/watcher master: Add service monitor for the Applier service  https://review.opendev.org/c/openstack/watcher/+/97061413:10
opendevreviewMerged openstack/watcher stable/2025.2: Consolidate and improve Zuul CI job definitions  https://review.opendev.org/c/openstack/watcher/+/96877913:13
amoralejsean-k-mooney, jgilaber i lost your votes in https://review.opendev.org/c/openstack/watcher/+/969370 by fixing the commit message13:14
opendevreviewchandan kumar proposed openstack/watcher-dashboard master: [poc] Add Selenium-based E2E testing framework  https://review.opendev.org/c/openstack/watcher-dashboard/+/97057313:14
opendevreviewchandan kumar proposed openstack/watcher-dashboard master: [poc] Add Selenium-based E2E testing framework  https://review.opendev.org/c/openstack/watcher-dashboard/+/97057314:09
opendevreviewDouglas Viroel proposed openstack/watcher-tempest-plugin master: Consolidate and improve Zuul CI jobs for stable branches  https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/97037814:13
tkajinamo/ I wonder if https://review.opendev.org/c/openstack/watcher-dashboard/+/955652 can get some attention ? json format support is being removed from oslo.policy soon14:24
sean-k-mooneyoh are we not using yaml in the daashbaord already14:24
sean-k-mooneysure ill take a look later14:24
opendevreviewchandan kumar proposed openstack/watcher-dashboard master: [poc] Add Selenium-based E2E testing framework  https://review.opendev.org/c/openstack/watcher-dashboard/+/97057314:30
tkajinamsean-k-mooney, thanks !15:03
opendevreviewJoan Gilabert proposed openstack/watcher-specs master: Add specification for migrating Watcher to OpenStackSDK  https://review.opendev.org/c/openstack/watcher-specs/+/96802315:27
opendevreviewAlfredo Moralejo proposed openstack/watcher master: Refactor service monitor for decision-engine  https://review.opendev.org/c/openstack/watcher/+/97061215:58
opendevreviewAlfredo Moralejo proposed openstack/watcher master: Assign hostname to ActionPlan when picked-up  https://review.opendev.org/c/openstack/watcher/+/97061315:58
opendevreviewAlfredo Moralejo proposed openstack/watcher master: Add service monitor for the Applier service  https://review.opendev.org/c/openstack/watcher/+/97061415:58
opendevreviewDouglas Viroel proposed openstack/watcher-tempest-plugin master: Consolidate and improve Zuul CI jobs for stable branches  https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/97037816:53
opendevreviewDouglas Viroel proposed openstack/watcher-tempest-plugin master: Consolidate and improve Zuul CI jobs for stable branches  https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/97037817:06
dviroeljgilaber: sean-k-mooney: next ci job refactoring is 2025.1 patch https://review.opendev.org/c/openstack/watcher/+/969137  (I still can't get the tempest-plugin change work with a depends on it)17:26
opendevreviewDouglas Viroel proposed openstack/watcher-tempest-plugin master: Consolidate and improve Zuul CI jobs for stable branches  https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/97037817:32
*** haleyb is now known as haleyb|out17:43
opendevreviewDouglas Viroel proposed openstack/watcher stable/2024.2: [stable-only] Consolidate and improve Zuul CI job definitions  https://review.opendev.org/c/openstack/watcher/+/97038519:46
opendevreviewIvan Anfimov proposed openstack/watcher-specs master: Remove url tags from README  https://review.opendev.org/c/openstack/watcher-specs/+/97069520:38
opendevreviewIvan Anfimov proposed openstack/watcher-specs master: Remove url tags from README  https://review.opendev.org/c/openstack/watcher-specs/+/97069520:38

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