Wednesday, 2025-01-22

*** mhen_ is now known as mhen02:15
opendevreviewBiser Milanov proposed openstack/tempest master: test_instances_with_cinder_volumes: Make sure attachments in guest are correct  https://review.opendev.org/c/openstack/tempest/+/93963308:59
opendevreviewJoel Capitao proposed openstack/devstack master: lib/glance: Migrate Glance to WSGI module path  https://review.opendev.org/c/openstack/devstack/+/93270209:25
opendevreviewJoel Capitao proposed openstack/devstack master: Support CentOS Stream 10  https://review.opendev.org/c/openstack/devstack/+/93725109:25
opendevreviewJoel Capitao proposed openstack/devstack master: Support CentOS Stream 10  https://review.opendev.org/c/openstack/devstack/+/93725110:50
opendevreviewBiser Milanov proposed openstack/tempest master: test_instances_with_cinder_volumes: Make sure attachments in guest are correct  https://review.opendev.org/c/openstack/tempest/+/93963311:11
chandankumarHello gmann! I wanted to take about a new project: prometheus devstack plugin.13:42
chandankumarSince #openstack-qa office hour will be very late for me. I will drop the message here. 13:42
chandankumarRecently I have started working on watcher project. In watcher, we are about to add prometheus as a datasource https://review.opendev.org/c/openstack/watcher/+/934423. Currently we were installing prometheus from sg-core devstack plugin repo. The same plugin is used in ceilometer repo.13:43
chandankumarWatcher project also needs to install node exporter and pushgateway. We proposed patch to sg-core repo https://github.com/openstack-k8s-operators/sg-core/pull/14 to add pushgateway support (needed for watcher-tempest-plugin to push custom metrics). But sg-core repo is meant for holding sg-core related stuff.13:43
chandankumarSince multiple projects are now using prometheus. So they suggested me to create prometheus devstack plugin and keep all prometheus projects installation and configuration there.13:43
chandankumarBefore creating the repo, I wanted to check with #openstack-qa team. Who can take care of managing the prometheus devstack plugin repo? It would be #openstack-qa or telemetry team.13:43
chandankumarI will keep an eye on the reply here. Thank you!13:44
chandankumargmann: I have added it under openstack-qa office hour agenda. rlandy or malinga will be there to discuss the same. thank you!14:02
rlandythanks chandankumar 14:05
toskyI can't answer as I'm not a core, but there are examples of devstack plugins whose management is shared: iirc devstack-plugin-ceph has both people from some of the affectes projects (manila, cinder for sure) AND also QA people14:07
toskysame for devstack-plugin-nfs, which has both cinder-core and devstack-core in its core reviewer group14:08
toskyso I suspect the answer will be along the line of "both telemetry and QA team"14:08
rlandythanks for the input tosky 14:18
chandankumarthank you tosky for the suggestion!14:35
chandankumarprometheus devstack plugin will be used by both telemetry and watcher project. 14:37
chandankumarWe will remove existing prometheus bits from sg_core repo.14:37
sean-k-mooney the orgial proposal in the watcher ptg was to add the prometious supprot to core devstack14:39
sean-k-mooneybut if the prefernce is a plugin like the ceph one14:39
sean-k-mooneythen that works equally well14:40
fricklerwith the declining number of devstack reviewers, having a plugin that can mostly be maintained by interested stakeholders sounds like a better solution to me, too14:45
sean-k-mooneyif nothing else it allwos a wider set of core reviewers14:57
sean-k-mooneywe can add the devstack, telemetry and watcher core groups to teh plugin core group14:58
sean-k-mooneywithout needign to do that on devstack itself 14:58
sean-k-mooneychandankumar: are you goign to propose a patch to the project-config repo to create it?14:59
chandankumarsean-k-mooney: yes, I will do that tomorrow!15:00
sean-k-mooneyfrom the governace repo poitn of view i think puting it under QA makes the most sence https://github.com/openstack/governance/blob/master/reference/projects.yaml#L207215:01
sean-k-mooneybut its a devstack plugin so we are not really going to do release of it so that more so it can be in the openstack namespace then anything else15:01
sean-k-mooneythe nfs one is there basically for that reason https://github.com/openstack/governance/blob/master/reference/projects.yaml#L215315:02
sean-k-mooneyonce the proejct-config change is proposed you shoudl propsoe a patch to the governace repo to add it too15:02
chandankumarsean-k-mooney: sure, thank you for the links!15:11
*** gthiemon1e is now known as gthiemonge15:58
opendevreviewBalazs Gibizer proposed openstack/devstack master: Follow up for creating parent dir for config files  https://review.opendev.org/c/openstack/devstack/+/93982516:05
opendevreviewJoel Capitao proposed openstack/devstack master: Support CentOS Stream 10  https://review.opendev.org/c/openstack/devstack/+/93725116:51
opendevreviewAshish Gupta proposed openstack/tempest master: Add host filtering for test_aggregate_add_existent_host and test_aggregate_remove_host_as_user tests  https://review.opendev.org/c/openstack/tempest/+/93976617:04
rlandysean-k-mooney: are we settled here with the solution "we can add the devstack, telemetry and watcher core groups to the plugin core group"?17:40
rlandyI'll still attend the meeting but the discussion/decision looks to be taken already? 17:40
sean-k-mooneyi think thats a resonable starting poitn. so how i woudl do this is add 1 or 2 people that will be maintianing the plugin directly to a new devstack-promethus-core group adn add the other 3 core groups as fallback17:42
sean-k-mooneythere is no direct expectation for the core grops of the ohter project ot review the new plugin but they would have the opertunity too17:43
rlandyok it's still on the meeting agenda - if no objections  - you can go forward - thanks17:43
sean-k-mooneyover time we can either add the active popel direcly and dropt the included groups or leave it17:43
gmann#startmeeting qa18:00
opendevmeetMeeting started Wed Jan 22 18:00:55 2025 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
opendevmeetThe meeting name has been set to 'qa'18:00
gmann#link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours18:01
gmanntoday agenda ^^18:01
gmannwho all here today18:01
rlandyo/18:01
gmannrlandy: hi18:02
gmannlet's go through the regular items first and then we can discuss about devstack new plugin18:03
mtemboHello 18:03
gmannmtembo: hi18:03
gmann#topic Announcement and Action Item (Optional)18:03
gmannnothing for this weel18:03
gmannweek18:03
gmann#topic Priority Items progress18:03
gmann#link https://etherpad.opendev.org/p/qa-epoxy-priority18:04
gmannthere is no significant progress on items so we can check it next time18:05
gmann#topic OpenStack Events Updates and Planning (Optional)18:05
gmannno event planned in near future but we do have next cycle election coming  18:06
gmann#link https://governance.openstack.org/election/18:06
gmannif there is no candidate for qa PTL role, we either go for DPL model or I will see if I can help as PTL role in next cycle18:07
gmann#topic Gate Status / Fix Checks18:07
gmann#link https://review.opendev.org/q/label:Review-Priority%253D%252B2+status:open+(project:openstack/tempest+OR+project:openstack/patrole+OR+project:openstack/devstack+OR+project:openstack/grenade)18:07
gmannnothing is tagged as urgent fix but afaik I did not see any blocker here18:07
gmann#link Changes with Review-Priority == +118:08
gmann#topic Changes with Review-Priority == +118:08
gmann#link https://review.opendev.org/q/label:Review-Priority%253D%252B1+status:open+(project:openstack/tempest+OR+project:openstack/patrole+OR+project:openstack/devstack+OR+project:openstack/grenade)18:08
gmannthere is one review tagged as priority, I will check today18:08
gmann#topic Periodic jobs Status Checks18:08
gmannPeriodic stable full: 18:09
gmann#link https://zuul.openstack.org/builds?pipeline=periodic-stable&job_name=tempest-full-2023-2&job_name=tempest-full-2024-1&job_name=tempest-full-2024-218:09
gmannall green here18:09
gmannPeriodic stable slow:18:09
gmann#link https://zuul.openstack.org/builds?job_name=tempest-slow-2024-2&job_name=tempest-slow-2024-1&job_name=tempest-slow-2023-218:09
gmannPeriodic extra tests:18:09
gmann#link https://zuul.openstack.org/builds?job_name=tempest-full-2024-2-extra-tests&job_name=tempest-full-2024-1-extra-tests&job_name=tempest-full-2023-2-extra-tests18:09
gmannPeriodic master: 18:09
gmann#link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic18:10
gmannit seems tempest-full-test-account-no-admin-py3 job failing consistently 18:11
gmannDetails: {'type': 'PolicyNotAuthorized', 'message': 'rule:create_network is disallowed by policy', 'detail': ''}18:11
gmannsome neutron rbac policy changed which we might need to check here18:12
gmannI will try if I can find some time to debug it this week18:12
gmannDistros check:18:12
gmannCentos 9: https://zuul.openstack.org/builds?job_name=tempest-full-centos-9-stream&job_name=devstack-platform-centos-9-stream&skip=018:12
gmannDebian: https://zuul.openstack.org/builds?job_name=devstack-platform-debian-bookworm&skip=018:12
gmannRocky: https://zuul.openstack.org/builds?job_name=devstack-platform-rocky-blue-onyx18:12
gmannJammy: https://zuul.opendev.org/t/openstack/builds?job_name=devstack-platform-ubuntu-jammy-ovn-source&job_name=devstack-platform-ubuntu-jammy-ovs&job_name=devstack-platform-ubuntu-jammy&skip=018:12
gmannNoble: https://zuul.opendev.org/t/openstack/builds?job_name=devstack-platform-ubuntu-noble&job_name=devstack-platform-ubuntu-noble-ovn-source&job_name=devstack-platform-ubuntu-noble-ovs&skip=018:12
gmannc9s job which is nv is failing some time which I can say not stable18:13
gmannother job is ok, they are failing sometime but not consistently 18:14
gmannalso, I will noble job from this list as we are now testing every job on Noble18:14
gmann#topic Open Discussion18:15
gmannrlandy/chandankumar: Ownership of prometheus devstack plugin (repo creation review will be sent after that). Context18:15
gmannrlandy: please go ahead18:15
rlandythanks gmann18:15
rlandyI think we pretty much have a suggestion18:15
rlandyper sean-k-mooney and chandankumar's discussion18:16
rlandy""we can add the devstack, telemetry and watcher core groups to the plugin core group"18:16
rlandyif there are no objections, we can go forward18:16
rlandygmann: ^^ you thoughts?18:16
gmannI read the log18:16
rlandyfor recording ...18:17
rlandyprometheus devstack plugin will be used by both telemetry and watcher projec18:17
rlandyso ownership spreads teams18:17
gmannfirst of all we have to understand what exactly meaning of adding a new project under QA. 18:17
gmannEvery project (I will say subproject) under QA are maintained by their own core member team. Like tempest, devstack, grenade all have their own core group even some/many of them overlap with same people but idea if to maintained them by their team18:18
gmannsimilar way if we add any devstack plugin, we need to have a separate plugin team to maintain it 18:18
gmannseeing it is related to devstack setup it is all ok to add it under QA project governance but ownership and maintaining responsibility needs to be taken care by this plugin team18:19
rlandy(adding a bit more context): https://meetings.opendev.org/irclogs/%23openstack-qa/%23openstack-qa.2025-01-22.log.html ... I think the general understanding is that some combination of the two teams will look after it18:19
rlandybut the general structure will be under QA18:20
gmannfor example, if plugin is active now and later we do not have any maintainer to maintain it then we might need to retire it as current QA team cannot maintaint it18:20
rlandyunderstood18:20
gmannThis is same for all other devstack plugin18:20
gmannrlandy: yeah, we create the core group from both project or any other project also18:21
rlandy+118:21
gmannbut my suggestion is to add a explicit list instead of adding watcher core or telemetry core group itself18:21
gmannand this plugin list can grow if someone other than these two project show interest18:22
rlandyI am not sure how the telemetry group is organized but we will pass on your recommendation18:22
rlandywe are working closely with them now18:22
gmannrlandy: yeah, maybe we can start with some of you there and then you can check if other member would like to join18:23
gmannperfect than 18:23
rlandyok - thank you gmann 18:23
gmannas next step, please start the repo creation and propose the governance change to add this under QA with separate group of maintainer18:23
gmannplease let me know if any help you need in that18:24
gmannalso, frickler is not here at this time but he can also give input on this18:24
rlandywill do - this will start tomorrow18:24
gmannI just ready his feedback in log so we all good here18:25
gmannrlandy: perfect18:25
gmannanything else18:25
rlandynot from our side18:26
gmannthanks rlandy and chandankumar18:26
gmannI do not see any other topic in agenda, but I will keep it open for couple of min if anything else18:27
gmannlet's close if nothing else, thanks everyone for joining18:29
gmann#endmeeting18:29
opendevmeetMeeting ended Wed Jan 22 18:29:24 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:29
opendevmeetMinutes:        https://meetings.opendev.org/meetings/qa/2025/qa.2025-01-22-18.00.html18:29
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/qa/2025/qa.2025-01-22-18.00.txt18:29
opendevmeetLog:            https://meetings.opendev.org/meetings/qa/2025/qa.2025-01-22-18.00.log.html18:29
opendevreviewAshley Rodriguez proposed openstack/devstack-plugin-ceph master: Remove standalone nfs-ganesha  https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/93990719:52
sp-bmilanovsean-k-mooney: re: https://review.opendev.org/c/openstack/tempest/+/939633 when you say that LUN devices do not have a `/dev/block/<DEV>/serial`, do you mean that the file is empty or that is missing entirely? If it is missing, the way the check is done now will waste ~2minutes of time before it reverts to the previous behaviour (relying on the Nova/libvirt mapping)19:55
sean-k-mooneyi dont know. so qemu does not allow you to pass a serial, im not sure if the device file will exisit with a seiral coming form the storage backend or if the file will be entirly missing20:01
sean-k-mooneysp-bmilanov: if you have a devstack env with lvm cinder you could modify this test https://github.com/openstack/tempest/blob/bd02c7355cb6bf327d109ef01f79c13cd2b263c6/tempest/api/compute/volumes/test_attach_volume.py#L469 to check20:02
sp-bmilanovah, nice, will check it out later20:09
sean-k-mooneyi suspect it might be there btu it will have a serial form the storage backend20:12
sean-k-mooneythe specific code you are changing is not impacted by htis20:12
opendevreviewRajat Dhasmana proposed openstack/devstack stable/2024.2: Update glance image size limit  https://review.opendev.org/c/openstack/devstack/+/93991721:11
whoami-rajatgmann, kopecmartin hey, thanks for your reviews on the devstack change, here is the backport for 2024.2 https://review.opendev.org/c/openstack/devstack/+/93991721:11
gmannwhoami-rajat: ack, will check after gate result21:18
whoami-rajatthanks!21:20
-opendevstatus- NOTICE: The Gerrit service on review.opendev.org will be offline momentarily for a restart to put some database compaction config changes into effect, and will return within a few minutes22:54

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