12:00:54 #startmeeting Watcher IRC meeting, August 14, 2025 12:00:54 Meeting started Thu Aug 14 12:00:54 2025 UTC and is due to finish in 60 minutes. The chair is rlandy. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:00:54 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:00:54 The meeting name has been set to 'watcher_irc_meeting__august_14__2025' 12:01:09 o/ 12:01:12 Hi all 12:01:19 who else is around? 12:01:21 o/ 12:02:11 o/ 12:02:15 o/ 12:02:28 courtesy ping: sean-k-mooney chandankumar 12:03:41 jwysogla: hi - did you want to add an item to the agenda? 12:04:20 Not really. You have the topic about open reviews already and I have the Aetos datasource mentioned there. 12:05:04 ok - let's start 12:05:30 #topic: (dviroel [out]): Review Status Etherpad 12:05:44 #link: https://etherpad.opendev.org/p/watcher-flamingo-status 12:05:58 o/ 12:06:18 Note from dviroel: Please note that FF is in 2 weeks! Please review them :) 12:06:26 let's look at that 12:07:46 jwysogla: since you added links there, do you want to cover Aetos datasource status? 12:08:36 sure. The observabilityclient, for which I was waiting before is now released. The CI is passing. I got a first +2 from dviroel yesterday and I'm waiting for other reviews. 12:09:44 Important note though is, that tomorrow is my last working day in August. Which is quite unfortunate because of the FF. I'll try to do whatever I can to react on reviews today and tomorrow if I receive any. 12:10:38 o/ 12:10:40 That's about it from me regarding the Aetos datasource review. 12:10:45 ok - Is there someone else who will be picking this up - or we just wait on your return? 12:11:11 I don't have anybody who'd pick it up at the moment. 12:11:14 jwysogla: i wanted to do a second pass but i was leanign towards +2 before the rebase 12:11:31 i will likely proxy dougs +2 adn approve this later today or tomorrow 12:12:24 i still need to review the tempest test job logs but i did not see anything too concernign last time i looked to hopefully this will get merged this week 12:12:42 Alright. Thank you. 12:13:27 ok, thank you jwysogla 12:14:07 anything else anyone wants to highlight from the https://etherpad.opendev.org/p/watcher-flamingo-status? 12:15:11 moving on ... 12:15:24 #topic: (sean) PTL or DPL for 2026.1 (from previous meeting) 12:15:41 Notes ... 12:16:06 is anyone instrested in runing for PTL this cycle? 12:16:19 otherwise we will stay with the DPL 12:17:26 silence means we stay with DPL :) 12:17:32 +1 12:17:36 +1 12:17:41 +1 for DPL, I think it works well for us 12:17:56 +1 for DPL 12:18:17 alright so then we need to settle on 4 liaison roles 12:18:25 actully 3 12:18:34 apprently the tc liason is apporte dby the tc 12:18:38 and has to be a tc member 12:18:50 so we dont need to select that 12:19:08 and security? 12:19:31 is that staying as is or is up for reassignment? 12:19:34 that is selected by us and should be a member of the watcher-coresec team 12:20:10 that up for reassignment but i would like to keep it to dan and myself unless dan want to step back 12:20:56 ok - so that leaves us with release and tact-sig 12:21:07 and it looks like some combination of: 12:21:19 dviroel, jgilaber_ and chandankumar are volunteering 12:21:51 note: we can decide this finally next week 12:23:18 oh wait - that was last week's note 12:23:31 scratch that 12:23:56 ya so sicne we are going with the dpl model we do not need to stricly ahve nomination before the 20th 12:24:23 however the revert to ptl patch is up so this or early next week we shoudl submit the patch to reaffirm the dpl model and specify the liasons 12:24:36 then each liason shoudl +1 it to confirm there agreement 12:24:41 after that the tc will merge it 12:24:49 dviroel, jgilaber_ and chandankumar can you discuss your preferences between yourselves - and let's aim to have the nominations ready next week 12:25:12 dviroel will be back on monday 12:25:54 sean-k-mooney: anything more we need to cover on this topic? 12:25:57 yep if two of ye want to do release and the other be added to trac-sig that also fine i can remove myself as the secondary release liason 12:26:14 ther is technially no limit but i was listign myself there more to help the new one then anything else 12:26:54 so ya let leave folks discsio it themeslve on monday and try and finalise the list before the next meeting 12:27:03 +1 12:27:03 we can move on unless others have questions 12:28:03 ok ... moving on 12:28:21 #topic: Start collecting PTG topics for Gazpacho PTG 12:28:35 #link: https://releases.openstack.org/gazpacho/schedule.html) 12:28:49 October 27 to 31, 2025 we’ll have a virtual PTG to plan the 2026.1 Gazpacho release 12:29:15 so this is not currently urgent but we need to start getting our thoughts together on that 12:29:27 iiuc noisy neighbor is one 12:30:23 any concerns or questions on this topic? 12:30:23 the state of datastores shoudl be anohter 12:30:33 we have a couple of related topics 12:30:52 basiclly now that monasca is being retired will we pull forward the removal to 2026.1 12:31:22 what is the long term plan for the promethus datasoruce once aetos is supproted 12:31:38 shall we deprecate in 2026.1 or supprot longer term 12:32:00 same with gnoicci. 12:32:35 so having a session be it 30mins or an hour to discuss that at the ptg i think woudl be good at the start of a new SLURP release 12:33:39 we also shoudl have a seesion on the untested integrations and experimtal features, i.e which we keep/repomve, which we want to build out ci for and what dead code can we elimiante 12:34:08 for example there is glance supprot in watcher but i belive it is not sued anymore 12:34:18 there is ironic support with no testing 12:34:33 so we need to decisn on what to do with those 12:35:37 i dont know if other have other topics they have beeing tinging about but i agree we shoudl start building a list 12:35:39 also, we still have the standing topic of managing multiple decision-engine and appliers, we could have a session to discuss the approach to follow 12:35:58 ya that woudl be a good topic for sure 12:36:09 yes - we need a place to start keeping a running list 12:36:23 even if we dont take action on some of those next cycle 12:36:42 having a high level plan and direction on some or all of those topic will help with future cycles 12:36:50 +1 12:36:55 we can either keep a temp list on our meeting note or I can start a new etherpad 12:38:18 let use https://etherpad.opendev.org/p/watcher-2026.1-ptg 12:38:41 +1 12:38:47 ill copy in the boiler plate at the top but we can use that for the ptg and intial planning 12:38:57 thank you sean-k-mooney 12:39:17 please add any further items there 12:39:43 moving on ... 12:39:50 #topic: reviews 12:40:09 chandankumar; those look like your reviews, do you want to take this? 12:40:14 yes 12:41:34 I was poking around continuous audit. I have written docs around continous audit https://review.opendev.org/c/openstack/watcher/+/957098 and improving its coverage in watcher-dashboard https://review.opendev.org/c/openstack/watcher-dashboard/+/957232 as well as on tempest side https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/956004? 12:41:38 Please have a look 12:42:13 here is the generated continuous audit doc https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_3bb/openstack/3bbd7d63fcda461baa3535dd8827849c/docs/user/continuous_type_audit.html 12:42:18 thank you! 12:43:14 thank you chandankumar 12:43:27 anything further on reviews? 12:44:16 only comment really is we are getting close to FF 12:44:25 so ingenreally we shoudl not be starting new work 12:44:32 adn focus on completing what is in flight 12:44:46 once we hit FF it will be bugfix only until RC1 12:45:06 then after RC1 we can resume low impact feature devleopemnt for 2026.1 12:45:27 wrt the skipped feature, i sent a patch to watcherclient, the only missing part is watcher-dashboard, i hope to send it in this cycle 12:46:04 that is ok, have you considered the openstack sdk changes as part of this work 12:46:19 or will that also be next cycle 12:47:07 nop :( 12:47:29 lemme take a look to check the required changes 12:47:33 ill add a ptg topic about deprecating the python binding in the watcherclient 12:47:52 its ok to extend tehm for now but evenually the watcer client repo should only be the osc plugin 12:48:01 and all python api bining logic shoudl be in the sdk 12:49:08 newbie question, is there any support for watcher in openstacksdk at all? 12:49:23 i was just lookign and the answer seams to be no 12:49:37 so agian this is a next cycle problem 12:49:41 perhaps the one after 12:49:42 that's also my guess 12:50:51 ill add a ptg topic but it looks like there will be more work there then i was hoping 12:50:59 so we dont need to rush into it 12:52:07 anything more on reviews? 12:53:02 moving on ... 12:53:16 #topic: bug triage 12:53:30 #link: https://bugs.launchpad.net/watcher/+bug/2119629 12:53:42 Errors appear in decision-engine logs when notification is enabled and new vms are created 12:53:46 needs triage 12:54:34 looks like it is triaged? 12:54:57 we triaged that last week i think 12:55:13 #link: https://bugs.launchpad.net/watcher/+bug/2119957 12:55:22 Zone Migration Strategy should avoid api calls to other services 12:55:42 this one is in New state 12:55:51 logged by dviroel 12:56:20 rlandy: the first on is the one i triaged offlinec 12:56:40 and the second is the one we talked about last week and agreed to file a new bug for 12:56:58 yes, we can move it to triaged, i think 12:57:01 i would say that a medium severity performance issue but sicne it works today its not higher 12:57:29 ok - updated 12:57:48 last one for today ... 12:57:53 #link: https://bugs.launchpad.net/watcher/+bug/2120586 12:58:05 NovaHelper doesn't properly compares Nova's API microversion 12:58:33 ouch 12:59:13 dviroel is already assigned to the bug 13:00:37 ya so watcher and the watcher tempest operoarts done use microversion prperly at all 13:00:51 but this is also clearly a bug as you cant use floats likethat 13:00:58 there are a few libs for this 13:01:14 i think we are ment to use microversion_parse to handel this 13:01:21 but i need to check with stephen 13:01:25 ah, right 13:01:40 i was checking in oslo.utils, but likely in microversion_parse there is something 13:01:53 stephenfin works on oslo and shift ofn stack and i knwo they are trying to deprecate/remove a few of the options we use today 13:02:07 so i want to see what the current guidance is before we start doing it 13:02:27 https://github.com/openstack/microversion-parse 13:02:31 thats is part of oslo 13:02:44 but im just not sure if its the one we shoudl be using today 13:03:08 it proably is but ill ask him later 13:03:19 thank you sean-k-mooney ... perahps we can continue on channel as dviroel is currently out we are over time? 13:03:37 ill leave a comment on the bug 13:03:46 +1 13:03:54 #topic: volunteers for to chair next meeting 13:03:57 but we can triage this as valid and low 13:04:26 i can take it 13:04:33 thank you amoralej 13:04:44 thank you all 13:04:51 closing out 13:05:05 #endmeeting