12:01:22 <dviroel> #startmeeting watcher
12:01:22 <opendevmeet> Meeting started Thu Sep 25 12:01:22 2025 UTC and is due to finish in 60 minutes.  The chair is dviroel. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:01:22 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:01:22 <opendevmeet> The meeting name has been set to 'watcher'
12:01:35 <dviroel> hi all, who is around today?
12:01:41 <amoralej> o/
12:01:48 <morenod> o/
12:02:26 <dviroel> courtesy ping list: jgilaber sean-k-mooney chandankumar rlandy
12:02:31 <rlandy> o/
12:03:04 <dviroel> let's start with today's meeting agenda
12:03:25 <dviroel> #link https://etherpad.opendev.org/p/openstack-watcher-irc-meeting#L28 (Meeting agenda)
12:03:31 <dviroel> feel free to add your own topics to the agenda
12:04:04 <dviroel> #topic Announcements
12:04:18 <dviroel> lets check our release schedule
12:04:26 <dviroel> OpenStack Flamingo Schedule
12:04:34 <dviroel> #link https://releases.openstack.org/flamingo/schedule.html
12:04:54 <dviroel> we are at  R-1 week
12:05:10 <dviroel> which means that we are 1w from the release
12:05:33 <dviroel> since we don't have any critical bug/fix
12:05:53 <dviroel> for watcher, the RC1 will be our final release for flamingo
12:06:22 <dviroel> once is released, we can start backporting other fixes to 2025.2 and older releases
12:06:35 <dviroel> the ones that we recently merged
12:06:54 <dviroel> any questions on that?
12:07:27 <dviroel> ok, next announcement
12:07:55 <dviroel> the vPTG - which will happen on October 27-31
12:08:14 <dviroel> registrations are open
12:08:15 <dviroel> at
12:08:29 <dviroel> #link https://ptg.openinfra.org/
12:08:37 <dviroel> and we need to define our slots
12:08:57 <dviroel> the recommendation is:
12:09:06 <dviroel> cross team meetings should happen on Monday-Tuesday
12:09:17 <dviroel> while ndividual team should happen between Wednesday-Friday
12:09:38 <dviroel> but is up to us to decide which slots we want to use
12:10:02 <dviroel> I was thinking on following the recommendation and get Wed, Thu and Fri (backup day)
12:10:19 <dviroel> but we can also work with Tue-Wed-Thur
12:10:34 <dviroel> I added an initial proposal in the agenda
12:11:10 <dviroel> we can discuss more next week, once we have more folks around too
12:11:20 <amoralej> what's the reason for Wed-Fri recommendation?
12:11:48 <dviroel> mon-tuesday would used for cross teams discussions
12:12:05 <dviroel> which can drive to individual team discussions next
12:12:24 <dviroel> and also to avoid conflicts
12:12:34 <amoralej> ok, got it
12:12:56 <dviroel> but not sure if everybody will follow those rules too
12:13:06 <dviroel> not rules, recommendations
12:13:33 <amoralej> I was thinking Tue-Thu would be better but that recommendation looks reasonable
12:13:41 <amoralej> so Wed-Fri lgtm
12:14:11 <dviroel> ack, Tue-Thu sounds good, I think that most of the teams also prefer that, in case more slots are needed, we would still have Friday
12:14:37 <dviroel> any conflict on Tue could be moved to Wed, Thu or even Fri
12:14:45 <amoralej> +1
12:14:53 <dviroel> so yeah, Tue-Thu sounds nuice
12:15:09 <dviroel> I like to use the monday to plan the week too
12:15:20 <dviroel> and check all other teams topics
12:15:51 <amoralej> wrt cross-teams meeting, it may be good to have one with telemetry team? at least, i'm not sure if i understood properly their plans wrt gnocchi backend i.e.
12:16:42 <amoralej> or maybe it is clear but i'm just not aware
12:17:24 <dviroel> ack, we may also join some other topics that are related with watcher too, like aetos related yes
12:17:51 <amoralej> yep
12:18:09 <dviroel> and our planning Etherpad is here
12:18:11 <dviroel> #link https://etherpad.opendev.org/p/watcher-2026.1-ptg
12:18:46 <dviroel> which I can work to split the topics in the slots that we reserve
12:19:06 <dviroel> so feel free to add any if you want to
12:19:58 <dviroel> anything else wrt to PTG?
12:20:22 <dviroel> that was my last announcement
12:21:22 <dviroel> ok, next topic
12:21:24 <dviroel> #topic Reviews
12:21:36 <dviroel> there was no specific review in the list
12:21:50 <dviroel> but I was looking at our 2025.2 review focus etherpad
12:22:00 <dviroel> #link https://etherpad.opendev.org/p/watcher-flamingo-status
12:22:30 <dviroel> I think that we merged most of the bugfixes listed there too
12:22:45 <dviroel> we merged lot os fixes for zone_migration
12:22:57 <dviroel> and lots of improvements for the dashboard
12:23:25 <dviroel> I will add a couple of open reviews here:
12:23:31 <dviroel> Doc updates
12:23:34 <dviroel> 957098: Add user guide for continuous audits | https://review.opendev.org/c/openstack/watcher/+/957098
12:23:43 <dviroel> tempest improvements:
12:23:53 <dviroel> 957222: Add basic datamodel list tests | https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/957222
12:23:53 <dviroel> 956116: Add tests for extended compute datamodel | https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/956116
12:24:29 <dviroel> I started working on refactoring some of our tempest tests:
12:24:37 <dviroel> 961762: Organize strategy tests and remove duplicated tests | https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/961762
12:24:37 <dviroel> 960310: Refactor execute_strategy method into smaller helpers | https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/960310
12:24:53 <chandankumar> dviroel: https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/956116 have merge conflict, may be rebase can fix it
12:25:10 <dviroel> this refactor will improve how we validate the generated action plan and actions
12:26:19 <dviroel> chandankumar: ok, i will check, i can rebase both
12:26:27 <dviroel> since it has a parent that is also open
12:27:16 <chandankumar> thanks!
12:27:16 <dviroel> there is a couple of open reviews for the dashboard too:
12:27:17 <dviroel> https://review.opendev.org/q/project:openstack/watcher-dashboard+is:open
12:28:05 <dviroel> any other review that you folks want to bring?
12:28:53 <dviroel> ok, lets move on
12:29:09 <dviroel> #topic Bug triage
12:29:25 <dviroel> we had a bug to revisit from previous week
12:29:45 <dviroel> but we need Joan to give us more information
12:29:58 <dviroel> it seems that he has new information about that
12:30:09 <dviroel> this one:
12:30:10 <dviroel> https://bugs.launchpad.net/watcher/+bug/2125060 (Storage_model fails to create pool from cinder notification with some storage backend)
12:30:26 <dviroel> so lets move to next week agenda, and we can revisit again
12:30:39 <dviroel> but I triaged to Medium alreadu
12:30:41 <amoralej> +1
12:30:52 <dviroel> we can check if needs to change that
12:31:19 <dviroel> ther is one bug that needs triage too
12:31:33 <dviroel> #link https://bugs.launchpad.net/watcher/+bug/2121807 watcher-api sometimes does not respond
12:32:55 <dviroel> there is a file with more info
12:33:41 <dviroel> ok so 14.0 is epoxy, right?
12:34:11 <amoralej> yes
12:34:40 <amoralej> apparently something introduced in epoxy created this
12:34:57 <amoralej> and the bug reports it when disabling keystone auth
12:36:30 * dviroel looking at the configuration provided
12:38:01 <dviroel> not sure how to proceed here, I think that there is a lot of things to consider there
12:38:49 <dviroel> but we would need to try to reproduce to help there
12:38:51 <amoralej> i'd recomend to run it with some wsgi server
12:39:01 <amoralej> gunicorn, httpd, etc...
12:40:33 <dviroel> yeah
12:40:42 <dviroel> it is also running on python 3.13
12:42:11 <dviroel> I think that we can raise some question in the LP bug
12:42:26 <dviroel> and see if the issue is still real
12:42:33 <amoralej> yes, and provide some initial recomendations
12:42:40 <dviroel> and discuss more in following weeks
12:43:30 <dviroel> ok, that was the only bug untriaged I think
12:43:37 <dviroel> at least from the newest ones
12:43:54 <dviroel> any other bug that you folks want to discuss?
12:44:52 <dviroel> ok, we are done for the topics today then
12:45:21 <dviroel> we can focus on our PTG topics for the following weeks
12:45:34 <dviroel> and backports
12:45:47 <dviroel> #topic Volunteers to chair next meeting
12:46:03 <dviroel> I can take again
12:46:10 <dviroel> unless someone wants too
12:47:05 <dviroel> ok
12:47:15 <dviroel> i think we can wrap up earlier today
12:47:25 <dviroel> thanks folks
12:47:27 <dviroel> we will meet again next week
12:47:38 <morenod> thanks dviroel++ !
12:47:39 <dviroel> thank you all for participating
12:47:46 <amoralej> thanks for chairing dviroel++
12:47:49 <dviroel> #endmeeting