Tuesday, 2024-08-13

*** bauzas_ is now known as bauzas00:01
ttxgmann: thanks!07:11
*** bauzas_ is now known as bauzas07:13
opendevreviewGuillaume Boutry proposed openstack/election master: Add Guillaume Boutry candidacy for Sunbeam 2025.1 PTL  https://review.opendev.org/c/openstack/election/+/92617708:36
*** jroll00 is now known as jroll008:42
opendevreviewJames Page proposed openstack/election master: Add James Page as candidate for OpenStack Charms PTL  https://review.opendev.org/c/openstack/election/+/92618008:50
*** bauzas_ is now known as bauzas09:37
slaweqhi gouthamr I will not be able to attend today's meeting because I am on PTO this week14:46
slaweqsee you next week14:46
gouthamrslaweq: ack; ty for letting me know15:14
*** gibi_ is now known as gibi16:27
opendevreviewHoai-Thu Vuong proposed openstack/governance master: Inactive state extensions: Monasca  https://review.opendev.org/c/openstack/governance/+/92391916:41
gouthamrtc-members: a gentle reminder that we're meeting here in ~45 minutes 17:14
gouthamr#startmeeting tc 18:00
opendevmeetMeeting started Tue Aug 13 18:00:49 2024 UTC and is due to finish in 60 minutes.  The chair is gouthamr. 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 'tc'18:00
gouthamrWelcome to the weekly meeting of the OpenStack Technical Committee. A reminder that this meeting is held under the OpenInfra Code of Conduct available at https://openinfra.dev/legal/code-of-conduct18:01
gouthamrToday's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee18:01
gouthamr#topic Roll Call18:01
noonedeadpunko/18:01
JayFo/18:01
dansmitho/18:01
gmanno/18:01
spotz[m]o/18:02
gtemao/18:02
gouthamrnoted absence: f r i c k l e r , s l a w e k 18:02
gouthamrperfect; we've everyone accounted for.. i do appreciate non TC members waving at us as well; please ignore the $topic if you'd like to say hi :D 18:03
gouthamrlets get started 18:04
gouthamr#topic Action Items from last week 18:04
gouthamrwe has an AI regarding Rocky Linux mirrors; i mentioned it in the TC summary email as a call for volunteers18:06
gouthamrthere was an AI to encourage leadership nominations; we've been doing this in several places18:07
funginext week will be better for getting some opendev collaboratory sysadmin input, i think. we've been a bit scattered last week and this week with folks travelling18:08
fungi(on the rocky mirroring discussion)18:08
gouthamr+1 fungi 18:08
gouthamrwe had another AI regarding deciding if "direct outreach" can be done in a way where the fairness of the election officials isn't diluted18:09
gouthamrdirect outreach would be required/helpful only where there are no PTL nominees for a project18:09
gouthamri think there's an acceptable solution here:18:10
gouthamr#link https://review.opendev.org/c/openstack/election/+/925873 (Add email template for direct reminder about nomination deadline)18:10
gouthamri think slaweq rethought this and instead of encouraging the existing PTL, this email reminder will go out to all project contributors 18:11
* gouthamr prefers this; and thinks it might help 18:11
noonedeadpunkI also didn't connect with Neil but also hardly around this week :(18:11
gouthamrcould others take a look as well?18:11
gouthamrnoonedeadpunk: ack; ty18:12
spotz[m]Neil as at Flock last week18:12
fungineil didn't seem to be around either, yeah18:12
gouthamrgmann: thanks for the review18:12
noonedeadpunkYup18:12
fungithough mnasiadka did chime in on the discussion at least18:12
spotz[m]I think he's at Devconf this week18:12
gouthamralright; that's all the AIs I was tracking.. anyone else got any?18:13
gouthamrwe'll chat about elections in a little bit18:14
gouthamr#topic A check on gate health18:14
dansmithI saw a number of typical fails this week, all volume-related but rechecks were moderately successful, which means things aren't too bad18:15
dansmithWe also merged some new image format tests and sample generation in devstack/tempest,18:16
gmann++18:16
gouthamrncioe18:16
dansmithwhich immediately started failing for nova's ceph job (because it doesn't actually ever see the image) and for the rocky jobs (because centos/rock's qemu and mkisofs are stripped down in terms of support)18:16
gouthamrnice*18:16
dansmithall of that is fixed (or in the gate to be fixed), but just FYI if any other fallout happens18:16
fungithere was a related discussion in #openstack-infra earlier today about whether we should switch the tox-py312 jobs from on-demand compiled python on debian-bullseye nodes to packaged python on the now available ubuntu-noble nodes, or whether it would be disruptive and should wait for after the release18:17
gmannpy312 job is non voting in this cycle so doing it now should not be issue even give more time to fix it when it become voting in next cycle18:17
fungiand also some jobs are still getting switched from running on ubuntu-focal to ubuntu-jammy (ran into release-related failures last week necessitating it, for example)18:18
gouthamroh; non devstack based jobs i presume? 18:18
JayFwell it's non-voting by default, are we sure no projects -- like SDKS -- are using it to gate against?18:18
dansmithgmann: agree, and better to be on noble anyway18:18
fungiclarkb was talking about possibly also switching the openstack tenant's default zuul nodeset from ubuntu-focal to ubuntu-jammy soon which might catch some more that haven't updated yet18:18
gouthamr++18:20
fungi#link https://review.opendev.org/922992 Switch the openstack-tox-py312* jobs to distro packages18:20
fungiin case anyone has feedback18:20
gouthamrthanks for the link, and the updates18:21
fungiyw18:21
gmannfungi: focal->jammy-  you mean to do this at zuul base job or specific to openstack-tox job ?18:22
gmannwe override the nodeset in openstack-tox and other job explicitly  18:22
fungigmann: the default nodeset in the base job, yes18:22
fungiso the impact is mainly going to be to jobs that don't inherit from openstack-tox18:22
funginor from devstack18:23
gmannyeah, should be ok I think as we do override the py version job with nodeset they are available by default18:23
fungiagreed, i don't think the impact will be widespread, just possibly surprising, especially for infrequently-run jobs18:24
gmannor we can do that in next cycle where we anyways need to move our testing to noble18:24
gmanneither way is ok for me18:24
fungithanks, i'll make sure to let him know once he's home18:24
gmannthanks18:24
gouthamrgmann: about that, were you planning on proposing a goal for this transition? or should we ask for volunteers interested in the effort? 18:24
gmannI will do that18:25
gmannone more info - with new oslo.policy 4.4.0 (enabling new RBAC by default), there are many projects failing on requirement u-c change, which I am fixing one by one https://review.opendev.org/q/topic:%22secure-rbac%22+status:open18:25
gmannbut if any project is missed and u-c change merge,  this is something help to fix those18:26
gmann#link https://review.opendev.org/c/openstack/requirements/+/92546418:26
gmannthis is requirement change18:26
gmannthis only impact projects have not enabled the new RBAC by default. cinder, tacker are two example18:27
gmannthat is all on this.18:28
gouthamrthanks gmann 18:28
gouthamron my end, devstack-plugin-ceph is finally merging changes to drop the old problematic package-based installation scripts18:29
gouthamr#link https://review.opendev.org/q/topic:%22cleanup-ceph-installer%22 (Cleanup ceph installer) 18:30
gouthamrthis stuff was propped up with borrowed beams and duct tape18:30
gouthamrbut, i'll be happy to help people doing devstack testing with ceph to move away from it18:31
gouthamr(it = installing ceph via packages and using scripts to run ceph on the devstack host)18:31
gouthamrany other updates/questions/concerns to share regarding the gate? 18:32
gouthamr#topic 2025.1 Elections18:33
gouthamrthe nomination period begins tomorrow (Aug 14th) at 23:45 UTC18:34
gouthamrhowever, based on prior feedback, we've pre-created directories, and you see PTL nominees already adding their nominations 18:34
gouthamrthe election officials (slaweq and ianchoi) will be sending out an email kicking off the nominations 18:35
gouthamrwe've four seats to fill here; if you're not considering running for re-election, i'd like to take a moment to thank you for your service on the OpenStack TC18:36
gouthamrif you are considering running for re-election, i'd like to thank you for your continued commitment 18:37
gouthamrthat's all i wanted to get in on $topic18:38
gouthamrdoes anyone have anything to share/add? 18:38
gouthamr#topic 2024.2 TC Tracker18:40
gouthamr#link https://etherpad.opendev.org/p/tc-2024.2-tracker (Technical Committee activity tracker)18:40
gouthamrone update i can note here is from thuvh on the monasca change18:41
gouthamr#link https://review.opendev.org/c/openstack/governance/+/923919 (Inactive state extensions: Monasca)18:41
gouthamranything else that needs to be brought up here, today?18:43
gtemanot from me18:44
spotz[m]not me18:44
gouthamrthank you; lets move on to open discussion18:45
gouthamr#topic Open Discussion and Reviews18:45
gouthamrthink we've been on top of reviews! thank you gmann for all the DPL transition patches18:46
fungiit may merit recalling the discussion last week about kolla's desire to integrate support for using hashicorp consul (a non-open-source software product). whether it posed any legal risks got discussed on the legal-discuss mailing list, but the outcome of that discussion has since been copied to openstack-discuss for further input (like whether the tc wants to place any limits on whether18:46
fungikolla should install non-open-source software in upstream tests, whether kolla can distribute pre-built container images containing non-open-source software, and so on)18:46
gmannnp!18:46
JayFHonestly, I don't like it but I think it's better to let that project team make that decision. 18:47
noonedeadpunkWell, we had quite some discussion about ability to have gpl2 licensed code for Ansible collections18:48
spotz[m]I don't care for it either because if folks don't a license they could be stuck18:48
noonedeadpunkAs there was a need to import Ansible livs18:48
fungi#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/TDHNR76BXRF6MJGRKOECM7H3CT5ICPZS/ LICENSE question - Openstack Masakari18:48
noonedeadpunkAnd the only proposed way back then was to manage under a sig18:48
noonedeadpunkWhich really results in slightly annoying situation right now18:49
noonedeadpunkSo if projects are allowed to do so, it would be interesting to re raise discussion about Ansible collections sig as well18:50
fungii'll note on the topic of gpl2 the concern was specific to license incompatibility with apache, but that has very recently been a topic of debate as well, and there are some legal opinions that there may not be any actual risks to combining apache and gpl2 licensed software18:51
noonedeadpunkBut bsl is not compatible either, is it?18:51
fungibut the kolla/masakari/consul discussion is something altogether different. gpl2 is an open source license, consul uses a non-open-source license18:51
* noonedeadpunk not a lawyer though18:52
gouthamri think using community resources to test a non-opensource license software should be discouraged; can kolla live without this? and are scripts to avoid consul usable (and shipped/supported)? 18:53
fungihow you combine them has some effect on whether you need the licenses to be compatible18:53
gouthamr#link: https://governance.openstack.org/tc/resolutions/20170530-binary-artifacts.html (2017-05-30 Guidelines for Managing Releases of Binary Artifacts) 18:53
noonedeadpunkThere's actually a proposal to masakari to use k8s for detecting compute state18:53
gouthamr(^ fungi pointed this out during the original discussion; thanks)18:53
noonedeadpunkIt's at blueprint stage right now, but it would eliminate need for consul there18:54
fungiyeah, the tc resolution on binary artifacts mainly just requires that the kolla team not claim openstack is supporting production use or claiming responsibility for the images they publish18:54
noonedeadpunkThough I kind of don't like either method for masakari... I really don't understand why they can't use some tooz driver for detecting if node is down18:55
gouthamr#link https://blueprints.launchpad.net/masakari/+spec/host-monitors-by-kubernetes (host monitor by kubernetes)18:55
noonedeadpunkAnyway...18:55
gmannnext item about testing runtime18:57
gmannTesting runtime for 2025.1 (SLURP release) is ready for review. Please check, or if needed, we can discuss it here also.  I have noted the diff from the previous cycle runtime in the commit-msg.  18:57
gmann#link https://review.opendev.org/c/openstack/governance/+/92615018:57
gmannas this is SLURP release, along with ubuntu noble as our default testing ditro version, we will keep testing the jammy also for smooth upgrade18:57
gmannand keeping py3.9 as min18:58
gmannI proposed job template also18:58
gmann#link https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/926152/118:58
noonedeadpunkI wonder if this hashi part can be in a separate repo from rest of the kolla?18:58
gmannthis is for upcoming stable/2024.218:58
gmann#link https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/926153/118:59
gmannand this for 2025.1 ^^18:59
noonedeadpunkJust to be able to govern it somehow differently from rest of the kolla as well as allow users to avoid using these bits18:59
gouthamrintertwined communication; fungi noonedeadpunk: maybe we can add this as a topic to the next week's meeting?18:59
funginoonedeadpunk: yes, one of the questions i asked and never got answered from the kolla end is whether it could be made to work with hashicorp's container images and/or whether the kolla team intends to redsitribute copies of consul in their own container images18:59
gtemawe do plan to ask project for dropping 3.8 though, right?18:59
fungigouthamr: yes, or just follow up on the mailing list in the meantime19:00
gouthamrperfect19:00
gmanngtema: yes, that is ongoing, I am going to push some in this cycle and start of next cycle19:00
gouthamrgmann: thank you for working on the PTI/runtime updates! 19:00
gouthamrwe're at the hour19:00
gmanngtema: but we will be able to drop that before m-1 of 2025.119:00
gtemagmann - perfect, thanks19:00
gouthamrfungi: thanks for bringing this up; i'll set a topic for next week; and we can gather some context as well 19:00
gouthamrthank you all for attending this meeting19:01
gouthamri'll see you here next week \o/19:01
gouthamr#endmeeting19:01
opendevmeetMeeting ended Tue Aug 13 19:01:22 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2024/tc.2024-08-13-18.00.html19:01
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2024/tc.2024-08-13-18.00.txt19:01
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2024/tc.2024-08-13-18.00.log.html19:01
spotz[m]Thanks gouthamr 19:01
gtemathanks19:01
*** bauzas_ is now known as bauzas19:09
*** bauzas_ is now known as bauzas19:46
opendevreviewMerged openstack/openstack-manuals master: Review "Tool support for image creation"  https://review.opendev.org/c/openstack/openstack-manuals/+/92365023:28
*** bauzas_ is now known as bauzas23:35

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