Thursday, 2025-01-16

marioshello folks do we have the irc meet? anyone else around? 12:01
mariosor did i get the time wrong ;)12:01
sean-k-mooneyo/12:01
rlandyyes - amoralej is the chair12:01
rlandywaiting a few for amoralej 12:01
mariosk i will run it today looks like some miscommunication? 12:01
rlandyotherwise we can start12:01
mariosmaybe amoralej something cam eup or whatever 12:01
amoralejdamn12:02
mariosi'll start it and he can continue if he comes later ?12:02
mariosah k 12:02
marioso/ 12:02
amoralejsorry i toitally forgot it12:02
rlandyyou ok to run it?12:02
amoralejsure12:02
jgilabero/12:02
mariosyou are 2 mins late i once forgot the whole thing ;)12:02
amoralejlemme create the mtg12:02
amoralejI whould have if you don't ping me :)12:02
dviroel:) 12:02
rlandythat's my job12:02
rlandythe ping nagger12:03
amoralej#startmeeting Watcher meeting - 2025-01-1612:03
opendevmeetMeeting started Thu Jan 16 12:03:21 2025 UTC and is due to finish in 60 minutes.  The chair is amoralej. Information about MeetBot at http://wiki.debian.org/MeetBot.12:03
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:03
opendevmeetThe meeting name has been set to 'watcher_meeting___2025_01_16'12:03
amoralejplease, add your topics to https://etherpad.opendev.org/p/openstack-watcher-irc-meeting12:03
marioso/ 12:04
amoralej#link https://etherpad.opendev.org/p/openstack-watcher-irc-meeting meeting agenda12:04
amoralejlet's start with the first topic12:04
amoralej#topic (rlandy): with Martin Kopec changing roles, we will need to new cores for watcher-tempest-plugin12:05
amoralejrlandy, you want to introduce the topic?12:05
rlandymartin has switched roles12:06
rlandyas such we will need to propose other cores for watcher-tempest-plugin12:06
rlandyin time12:06
rlandythis is just a team fyi12:06
mariosi think we have a general problem with lack of cores (basically we now have just one active core sean-k-mooney )12:07
mariosin the tempest-plugin case, until now we had martin as well (it is the exception) so here we are also down to one core 12:07
mariosfetching the group for reference... 12:07
sean-k-mooneywell realisticlaly until late december we didnt have any active cores12:08
sean-k-mooneyso martin has only been in the list for a few weeks and they were on pto for part of that12:08
sean-k-mooneyi added them on the 28th of november12:09
marios#info https://review.opendev.org/admin/groups/09a91d8e24af9ce44b80062c4851a1d2fa3d4d14 watcher-tempest-core gerrit group12:09
marios#info https://review.opendev.org/admin/groups/09a91d8e24af9ce44b80062c4851a1d2fa3d4d14,members watcher-tempest-core members 12:09
sean-k-mooneyso i was going to propos that we do a review of core membership the first week of febuary12:09
rlandy+112:10
dviroel+112:10
mariossounds good i think we have discussed doing this around this timeframe before (in the context of things not being able to merge in watcher and dashboard repos)12:10
sean-k-mooneymy plan was to review the review stats in https://openstack.biterg.io/app/dashboards and propsoe a set of potitla cores to each of the watcher group to the mailing list12:10
sean-k-mooneyif we want i can try and prepare that email before the next meeting 12:11
sean-k-mooneyand then we can wait for feedback and dicusss in the next meeting12:11
amoralej#agreed we will  do a review of core membership the first week of febuary12:12
sean-k-mooneyif there are no objects by the meeting after that on jan 30th12:12
sean-k-mooneyi can implemnt the changes12:12
sean-k-mooney*objections12:12
amoraleji guess that's a good plan12:12
amoralejso, we can move to next topic?12:13
amoraleji will open next one12:14
amoralej#topic (marios): update on prometheus datasource 12:14
mariosthanks amoralej 12:14
amoralej#link https://review.opendev.org/c/openstack/watcher/+/934423 12:14
mariosas discussed last week there were some requested changes around the auth options, making the fqdn_instance_map more like a cache with a rebuild & retry at least once 12:15
mariosthose and some other smaller bits where implemented now (including removing the 'prometheus_' prefix on the config options)12:15
mariosthere have been no further comments or requests yet and we have a +2 from sean-k-mooney and +1 from various other folks who have requested changes 12:16
mariosthanks again to everyone for all your suggestions and improvements.12:16
mariossince we have the core issue, I would propose that if there are no negative comments by end of next week we can merge it? 12:17
* marios checks date on the patch 12:17
marios(I discussed that bit about merge with sean-k-mooney privately already 12:17
sean-k-mooneyyep12:17
mariosyeah so i updated that jan 10th 12:17
amoralej+1 to merge it asasp12:18
sean-k-mooneyso for singlel core approval i want ot 1 leave time for other to review ideally at least 2 weeks12:18
mariosi'd say tomorrow is 1 week , so next friday sound good sean-k-mooney ? 12:18
sean-k-mooney2 see reviews form non cores with no objections12:18
amoralejbtw, i started some work to integrate that in a deployment tool and I'm already relying in the config options set in latest PS :)12:18
sean-k-mooneyand 3 adress it by buildign out the core team so it is not requried long term12:18
sean-k-mooney@marios yes the end of next week was what i had in mind so either after the next team meeting or fiday12:19
marios#info planning to merge https://review.opendev.org/c/openstack/watcher/+/934423 by next friday 24 unless there are objections12:20
mariosso amoralej has already started iterating with the instance work on top12:21
mariosi wouldn't want it slipping further into february to merge i mean 12:21
mariosthanks, that's all i had on this topic amoralej if there are no further comments we can move on? 12:21
amoralejactually my instance work is next topic :)12:21
amoralej#topic (amoralej) add instance metrics into prometheus datasource12:22
amoralej#link https://review.opendev.org/c/openstack/watcher/+/938893/12:22
amoralejthis is mainly a call for review12:22
amoralejGiven that the merge of previous one is approaching I'd like to also get this one reviewed when you have a chance12:22
mariosi think its already looking good amoralej thanks for jumping on that12:23
amoralejit is much simpler that the one adding the datasource so i hope will be faster to review12:24
sean-k-mooneythe main thing that i think is missing (and coudl be in a follow up patch) 12:25
sean-k-mooneyis i would like use to also extend the new tempest job to start testign with the new datasouce12:26
sean-k-mooneythat does require work in the tempest plugin but we shoudl at elast enabel/configure the new data source sooner rather then later once its merged12:26
mariosyes big +112:27
mariosamoralej: has been testing on his env with the datasource but we should get into ci asap 12:27
amoralejyes, +1 for me too12:27
sean-k-mooneyim ok to defer the decion on if we start doing that in https://review.opendev.org/c/openstack/watcher/+/938893 or a follow up patch12:27
amoralejas you said, I'd propose to make that follow up patch12:27
sean-k-mooneybut it would be nice to work on that before we merge it12:27
mariosyeah i think it can/should be different patch 12:28
rlandychandankumar is close to being able to add prometheus metrics in the plugin 12:28
sean-k-mooneyack12:28
rlandyso we should be able to extend the test shortly12:28
amoralejfor me it is a matter of time, if we can add it soon, no problem in including it into the patch12:28
sean-k-mooneyok we can defer this to gerrit review and see how the various efforts come togheter12:28
sean-k-mooneyi think we are generally in agreement on the direction12:28
dviroelyes12:29
amoralejok12:30
amoralejso that's it for this one12:30
amoralejmoving to next one12:30
amoralej#topic (rlandy) reminder bug triage continuation on Tuesday, January 21, 2025 12pm UTC (gmeet and IRC as sent on the ML)12:30
amoraleji guess this is just a reminder12:31
amoralej#info next bug triage session is on Tuesday, January 21, 2025 12pm UTC, details for anyone interested are in the mailing list12:31
mariosrlandy: did a great job running that but... do you want to do it again or would you like us to rotate?12:31
amoralej#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/5KZUHLXUOGTBXMQ4HERO52XB7I5A3HXI/12:32
mariosrlandy: do you want us to rotate the chair on that? ^^ 12:33
rlandyeither way12:34
rlandyI can finish off this one - and then next time we do it, someone else can take it12:34
rlandyie: I'll take this Tuesday's 12:34
mariossounds good thank you rlandy 12:34
marioswe should be able to get through a fair chunk after next meeting 12:34
marioswe had some overhead on the first one ;)12:35
amoralejbtw, i found a great exercise to keep learning about the status of watcher12:35
amoralejyep, we well go faster next time :)12:35
amoralej#topic next chair12:36
amoralejany volunteer to chair next meeting? i don't want to forget this time12:37
amoralej:)12:37
mariosi didn't do this for a while, but if there is someone who wants to/didn't go yet i will not fight you for it12:37
rlandylooks like it's yours marios 12:38
mariosyup12:38
amoralej#action marios will chair next meeting12:38
amoralej#topic open floor12:38
amoralejout of the ones in the agenda, is there some other topic you'd like to discuss ?12:39
sean-k-mooneyi have one minor update 12:39
sean-k-mooneynot in the adgeda12:39
* dviroel proposing myself for chair the meeting on 30th12:39
amoralejthanks dviroel 12:39
amoralejok, sean-k-mooney go ahead please12:39
sean-k-mooney#link https://bugs.launchpad.net/watcher/+bug/208671012:40
sean-k-mooneyi have been looking into ^ on and off for a while12:40
amoralejthat's an important one ...12:40
sean-k-mooneychattign to jayF yesterday i took a look at eventlet12:40
sean-k-mooneyand found that the behavior was changed in12:40
sean-k-mooney#link https://github.com/eventlet/eventlet/pull/93212:41
mariosi think this randomly fails in the -strategies job right ?12:41
sean-k-mooneyso i have filed12:41
sean-k-mooney#link https://github.com/eventlet/eventlet/issues/101412:41
sean-k-mooneymarios: no this is not realted to -straegies12:41
sean-k-mooneythat is a bug in the tempest plugin12:41
sean-k-mooneythe -stragies job failure is 12:42
sean-k-mooney#link https://bugs.launchpad.net/watcher-tempest-plugin/+bug/209085412:42
mariosthank you looking at that12:42
amoralejsean-k-mooney, so we need to wait on the eventlet patch, righ? not fix from watcher side ?12:42
sean-k-mooneyanyway my update is that the runtime error were previosusly asserts in eventlet prior to eventlet 0.36.012:42
sean-k-mooneyat least one of the new expction seams to have been incorrect to raise12:43
sean-k-mooneythe other exception may be valid and  may be a sqlachemy 2.0 issue12:43
sean-k-mooneyso right now its not clear if we will have to fix anything more in wathcer for this or if we will need to adress this in eventlet/sqlachmey12:44
sean-k-mooneyill continue to follow this and update folks btu that was what i wanted to highlight12:44
amoralejfreeze for non-client libs is Feb 17 - Feb 21, i hope it arrives on timme12:45
amoralejwe probably can manage it as some kind of exception otherwise12:45
sean-k-mooneyso its also unclear why we are seeign diffent behavior on 3.9 vs 3.1212:46
sean-k-mooneybut yes we will have to see how we proceed if we do not have a reolution by then12:46
sean-k-mooneyill also not that i woudl have expected this to also impact other services like nova12:47
sean-k-mooneythe fact its not impleis there is some watcher specific context to this12:47
sean-k-mooneywhich is why im gong to continue to look into this in paralle12:47
*** dviroel is now known as dviroel_brb12:47
amoralejas you said before, probably the specific thing is using APScheduler, right?12:48
sean-k-mooneyyes 12:48
sean-k-mooneyi did a review of which project use it in openstack12:48
sean-k-mooneythereare 512:48
sean-k-mooney3 are dead12:48
sean-k-mooneyzuul does not use eventlet12:48
sean-k-mooneyso watcher is the only "active" project with eventlet + apscheduler12:49
sean-k-mooneyi also think it required the sqlachemy datastore to be used with apscheduler too12:49
sean-k-mooneyim plannign to try and create a smaller repoducer with that combination today12:49
amoralejso, it'd make sense that the issue is in the combination... this is a hard one sean-k-mooney , thanks for investigating it12:49
sean-k-mooneya possibel PTG topic might be shoudl we remove/replace the usage of apschduler entirly12:50
sean-k-mooneythat not somethign i think we can do this cycle however. removbing eventlet woruld also be an optin but again too large to consider for 2025.112:51
sean-k-mooneyas a comunity it is somethign we shoudl evaluate however as long term apschduler is workign on a 4.0 relase that is not backwards comaptible12:51
amoralejwe probably can follow what other active projects with similar usecase are doing 12:52
sean-k-mooneyso we woudl have to do a large migration in the next cycle ot two anyway form 3.x12:52
amoralejwhat are the alternatives to apscheduler ?12:52
amoralejwhich projects may have a similar usecase ?12:53
sean-k-mooney:) good question. today we useign it for two things12:53
sean-k-mooney1 runing perodic tasks that done need to use it12:53
sean-k-mooneyand the contiious audit12:53
sean-k-mooneythe first usecase it easy to remvoe12:53
sean-k-mooneythe second is why it was added in the first place12:53
amoralejyeah12:53
sean-k-mooneythere is also a scalebality element12:54
sean-k-mooneycurrently its not clear if we can horizontally scale watcher12:54
sean-k-mooneyi.e. to distibute the continous audits between deamons12:54
sean-k-mooneyanyway i think we can take this out of the meeting 12:55
amoralejright12:55
amoralejbut it is an interesting conversation to have, out of the mtg :)12:55
amoralejalso, we only have 5 more minutes12:55
amoralejanything else you want to add before closing ?12:55
amoralejI am closing then12:57
amoralejThanks all for joining!12:58
rlandythank you amoralej 12:58
jgilaberthanks!12:58
mariosthanks all and thanks for running amoralej o/12:58
amoralej#endmeeting12:58
opendevmeetMeeting ended Thu Jan 16 12:58:23 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:58
opendevmeetMinutes:        https://meetings.opendev.org/meetings/watcher_meeting___2025_01_16/2025/watcher_meeting___2025_01_16.2025-01-16-12.03.html12:58
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/watcher_meeting___2025_01_16/2025/watcher_meeting___2025_01_16.2025-01-16-12.03.txt12:58
opendevmeetLog:            https://meetings.opendev.org/meetings/watcher_meeting___2025_01_16/2025/watcher_meeting___2025_01_16.2025-01-16-12.03.log.html12:58
*** dviroel_brb is now known as dviroel13:00
sean-k-mooneyjust an fyi i closed https://bugs.launchpad.net/watcher/+bug/2091696 as fix released because sqlachmey 2.0 supprot was added in 2024.2 (dalmation)13:05
rlandygmann: hello ... martin still has this open review:  https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/936837. It has a number of +1 votes. Please could we get your review/vote on it. thank you14:46
gmannrlandy: +2, lgtm18:25
sean-k-mooneyill try an loop back to it before i finish for today18:32
rlandygmann: thank you18:41

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