Tuesday, 2024-03-05

opendevreviewMerged openstack/election master: Update governance tag 0.16.0 to configuration  https://review.opendev.org/c/openstack/election/+/91068800:44
opendevreviewFelipe Reyes proposed openstack/election master: Add Felipe Reyes candidacy for OpenStack Charms  https://review.opendev.org/c/openstack/election/+/91114516:12
fricklerwow, that's ... quite late. I was actually going to ask jamespage about the lack of a candidate for that project16:38
jamespageoversight on deadlines - I nudged ;)16:39
JayFyeah, they'll have to be appointed tho16:46
spotz[m]Yeah Trove I think needs to be appointed as well17:09
spotz[m]I think I have 6 projects left on my no PTL list17:09
dansmithFYI, I might be a few minutes late to the meeting today17:44
dansmithof course the 8-hour arrival window for a service person just landed 10 minutes from now17:45
funginow that's service17:50
dansmithdon't get me started.17:51
dansmithit's a "come back and fix stuff you should have done the first time" appointment, so, yeah.17:51
JayFI had, during a meeting the other day, a person arrive during TC meeting despite explicit "You can arrive anytime but 10a-11a" instructions17:52
JayFIt's very much a product of the "you work from home == you're not working" attitude some folks have I think17:53
opendevreviewGhanshyam proposed openstack/governance master: Mark Murano project inactive  https://review.opendev.org/c/openstack/governance/+/90885917:53
dansmiththere's also definitely some "I don't have things scheduled to the minute, so I don't understand how life could work that way" aspect but yeah17:53
JayFtc-members:  https://us06web.zoom.us/j/87108541765?pwd=emlXVXg4QUxrUTlLNDZ2TTllWUM3Zz09 5 minute warning17:55
dansmithwhew, the ten minute warning was less than ten minutes, so I should be good, but if I disappear you'll know why17:57
JayF#startmeeting tc18:01
opendevmeetMeeting started Tue Mar  5 18:01:04 2024 UTC and is due to finish in 60 minutes.  The chair is JayF. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
opendevmeetThe meeting name has been set to 'tc'18:01
JayFWelcome 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-conduct.18:01
JayFToday's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee.18:01
JayF#info Today's meeting is being held primarily via video call. Action items and meeting minutes will be documented in IRC but for a full replay of the meeting, please visit the OpenStack TC youtube channel#info Today's meeting is being held primarily via video call. Action items and meeting minutes will be documented in IRC but for a full replay of the meeting, please visit the, where the recording will be uploaded soon.18:01
JayF#undo18:01
opendevmeetRemoving item from minutes: #info Today's meeting is being held primarily via video call. Action items and meeting minutes will be documented in IRC but for a full replay of the meeting, please visit the OpenStack TC youtube channel#info Today's meeting is being held primarily via video call. Action items and meeting minutes will be documented in IRC but for a full replay of the meeting, please visit the, where the recording will be uploaded soon.18:01
JayF#info Today's meeting is being held primarily via video call. Action items and meeting minutes will be documented in IRC but for a full replay of the meeting, please visit the OpenStack TC youtube channel18:01
JayF#link https://www.youtube.com/channel/UCBuGwBXOmWHydSE09RM84wQ18:02
JayF#topic Roll Call18:02
JayFo/18:02
gmanno/18:02
slaweqo/18:02
rosmaitao/18:02
dansmitho./18:02
JayF#info James Page absence noted on the agenda in advance18:03
JayFspotz[m]: 18:04
JayFAre you going to join us?18:04
spotz[m]o/ here but will be late joining video. Somewhere noisy and headset won’t connect18:04
JayFack18:04
JayF#topic Follow up on Action Items18:04
JayF#info JayF contacted Tony/Elod, they have a change up to add documentation about joining unmaintained group, then will send email.18:06
JayF#info JayF emailed mailing list about gate ram issues18:07
JayF#info Posted resolution to explicitly remove Murano from release https://review.opendev.org/c/openstack/governance/+/91043418:09
JayF#topic Gate Health Check18:10
JayF#info TheJulia identified an upstream dnsmasq crasher impacting Ironic. Ironic rolled back to 2.85 built via source to resolve. Working w/upstream Ubuntu and DNSMasq for a real fix.18:14
TheJuliaIt is also likely impacting neutron, there is nothing ironic specific there, really18:15
TheJuliaJFYI18:15
spotz[m]TheJulia: Designate too possibly?18:15
JayFYeah, I indicated the way to find it is by looking for the crashes in neutron-dhcp-agent18:15
TheJuliaif they are using dnsmasq and issue a SIGHUP at any time, yes18:15
JayF#info Jobs depending on CEPH were failing due to bad download location; fix was required to be forced-merged due to other instability.18:16
fungirelated to gate health, opendev is removing centos-7 nodes from zuul on march 15, and there are a number of projects that still have leftover cruft referencing centos-7 which will end up with zuul config errors when that goes away18:16
JayF#topic Testing runtime for 2024.2 release18:16
johnsomDesignate doesn't use dnsmasq18:16
JayFfungi: ack, thank you18:16
spotz[m]Thanks johnsom 18:19
JayF#info Some concerns, raised initially by Dan, around python 3.12 not being mentioned at all in the proposed testing runtime document. TC members generally understand 24.04 testing means python 3.12 testing, but we may need to be more explicit in the documentation.18:21
JayF#link https://review.opendev.org/c/openstack/governance/+/90886218:21
JayF#info Consensus is to add a "warning box" or similar construct to the document, indicating that python 3.12 needs work during cycle even if it's not going to be a part of the platform.18:30
JayF#topic Implementation of Unmaintained Branch Statuses18:31
rosmaitapatches are out for transitioning current EM branches to Unmaintained18:31
rosmaita#link https://review.opendev.org/q/topic:%22vwx-unmaintained%2218:31
rosmaitaprocess of becoming an Unmaintained core team member18:31
rosmaita#link https://review.opendev.org/c/openstack/project-team-guide/+/91081718:31
JayF#topic Muano inactivity and Caracal Release18:40
JayF#undo18:40
opendevmeetRemoving item from minutes: #topic Muano inactivity and Caracal Release18:40
JayF#topic Murano inactivity and Caracal Release18:40
JayF#link https://review.opendev.org/c/openstack/governance/+/91043418:40
JayF#link https://review.opendev.org/c/openstack/governance/+/90885918:40
JayF#info We need to land this today if we're landing it; so we can get the resolution on the books before RC deadline18:42
JayF#topic 2024 TC Tracker/PTG Planning18:42
JayF#info TC PTG planning etherpad will be created this week18:44
JayF#info TC PTG will be scheduled tentatively for the same time blocks as last cycle; pending confirmation with incoming-new-TC18:44
JayF#topic Open Discussion18:44
JayFAnyone with open discussion topics speak up quickly18:44
fungi#endmeeting19:03
opendevmeetMeeting ended Tue Mar  5 19:03:52 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:03
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2024/tc.2024-03-05-18.01.html19:03
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2024/tc.2024-03-05-18.01.txt19:03
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2024/tc.2024-03-05-18.01.log.html19:03
spotz[m]Sorry I didn’t make the video. Earbuds wouldn’t sync up with anything19:10
opendevreviewGhanshyam proposed openstack/governance master: Define testing runtime for 2024.2 release  https://review.opendev.org/c/openstack/governance/+/90886219:47
gmanntc-members ^^ another revision on testing runtime, please check19:48
gmanndansmith: I added it in top section, please check if that is ok now?  https://review.opendev.org/c/openstack/governance/+/908862/6/reference/runtimes/2024.2.rst#6119:50
JayFIs there *anyone at all* working on docs for OpenStack anymore? I don't mean in terms of like, keeping CI running, I mean, thinking about docs at an openstack-level?20:02
JayFGR-OSS is sponsoring a professional tech writing team to look into Ironic docs and make concrete improvement suggestions; and I want to ensure my assumption of "there's likely no specific doc writers upstream they can work with" is accurate20:02
clarkbI'm not aware of any full time docs folks20:03
fungii've not noticed any either20:03
JayFThat's what I figured. Just wanted to ask somewhere, publically, so if there was someone at least I tried :D 20:05
JayF(the goal is to get bite-sized pieces that are doable by MLH Fellows/Outreachy folks/part time contributors)20:05
JayF(the goal is to get bite-sized pieces that are doable by MLH Fellows/Outreachy folks/part time contributors since this is the reality)20:06
TheJuliaUpstream doc writers are typically "developers who care about docs" at this point20:19
fungior contributors who were told by reviewers that their change needed an accompanying docs update, at least20:22
TheJulia++20:23
frickleryes, but the global level docs like installation guide are extremely neglected I'd say20:24
TheJuliaat some point we have to ask, should severely neglected docs be "removed" or "re-framed" if they risk creating more noise than signal 20:25
fricklerby chance I started updating the contributor guide yesterday, because I noticed some old stuff like ethercalc still getting mentioned20:25
JayFThis is my understanding as well, and I know it's an openstack-wide problem but I doubt if I have the resources to impact it at that scope, which is why we're looking at Ironic right now20:25
opendevreviewNicolas Bock proposed openstack/project-team-guide master: Add section about transition  https://review.opendev.org/c/openstack/project-team-guide/+/91137520:25
TheJuliayeah, any effort to boil the ocean should look at reduction of scope first because the ocean scope is just... a lot20:26
clarkbthe top level scope might be easy to make impact in beacuse no one can say no right now :)20:26
fungisecurity guide is very stale too, sad to say20:26
TheJuliaclarkb: but many people can express specific opinions as well which can become a quagmire20:26
JayFI am explicitly scoping out top level for two reasons: 1) It's useless to fix top level if individual project docs are still bad and 2) As someone running the project, it's gotta be stuff I know. I know Ironic docs; I don't know the rest.20:28
JayFcan't let perfect be the enemy of good20:29
TheJulia++20:51
TheJulialooks like the standalone job is failing for separate reasons21:15
TheJuliamaybe we just non-vote it?21:15
JayFTheJulia: ECHAN?21:16
TheJuliayup21:17
TheJuliadoh!21:17
spotz[m]I did mention to the RDO team that the RPM instructions were way out of date, I'm hoping we can get them updated. We no longer have a User Guide I think the most recent was O release:(21:42
opendevreviewMerged openstack/governance master: Resolution: Remove Murano from 2024.1 release  https://review.opendev.org/c/openstack/governance/+/91043421:57
TheJuliaMaybe we're reaching the point an "installation" process needs to be entirely re-thought22:57
TheJuliasince the underlying interactions are radically shifting.22:57
clarkbI'm not sure we need to redo openstack ansible and kolla etc? maybe I'm misunderstanding the statement. If you mean update the installation docs then ya I could see that maybe they should just point to one of the installer docs isntead23:19
TheJuliaWell, to re-frame it, think of what is installation and how does that vary23:21
JayFTC meeting is uploading here: https://www.youtube.com/watch?v=lDTRbr5XPvs23:22
TheJuliawon't uniformly apply, really based upon perspective to solve the demand at hand23:22
JayFTheJulia: is it safe to say you mean23:22
JayFThere is no "OpenStack Install Guide"23:23
JayFthere is "Kolla-Ansible Install Guide" and "openstack-ansible install guide" "Charmed OpenStack Install Guide"  ... etc23:23
TheJuliayes23:23
JayFthe idea of a single install guide is extremely misleading23:23
TheJuliaand, individual project will still frame things from their own point of view23:23
TheJulia... at which point really the challenge is operational, not system architectural23:24
clarkbya I imagine that the top level docs might need to be more choose your own adventure style rather than trying to be complete in the sense of taking someone from server to openstack23:24
JayF[sad trombone sounds] The real problem is that there's nobody to even think about or do this work.23:26
JayFWe (GR-OSS) are doing what we can with the resources we have in trying to uplift Ironic's docs, if that's successful we might look at what a larger scope would look like23:26
JayFbut it doesn't matter what shape we want the documents to be; it matters what shape of documents we have enough eyeballs and hands to keep up to date, and right now that looks like "not much"23:27
TheJuliawhich sort of goes back to scope and the need to de-scope23:28
clarkband maybe some of this situation is a result of tools like osa and kolla largely working for people23:30
clarkbso there isn't demand that we have separate documentation23:30
TheJuliapossible23:31
fungistill, might be worth some intern time to rip out the existing install guide and replace it with links to osa, kolla, rdo, charmed openstack, debian oci...23:36
JayFBluntly; I think that's kinda wishful thinking given the number of useful, needed documents that are bitrotting.23:36
spotz[m]I think the way we have the install guide(one main page which sends you to the project install pages) is fine. What I think we're lacking these days is how to use the CLI , and maybe a little bit of Horizon) to do stuff23:36
JayFAt least from an Ironic perpsective23:36
JayF++ exactly, we have lots of doc needs that aren't being filled23:37
fungithe theory is that deleting outdated documentation nobody's going to update is less work than writing new documentation, but yes just letting it continue to sit there is even less work still23:38
TheJuliaOne of the recent thing I'm seeing is not even how to use, but people trying to push forward without actually actually stopping to look at the messages they get back23:38
JayFfungi: I specifically told the docs people we asked to do an evaluation (FWIW they are doing this for several CNCF projects, as well, under CNCF funding) that an answer of "this entire section needs to be mostly deleted" would be OK feedback23:39
spotz[m]You can still find stuff, it may not be totally up todate with anything new but if we haven't removed functionality it still has use23:39
clarkbspotz[m]: yes for stuff like boot nodes and make networks and all that I expect the dosc don't need a lot of changes23:39
fungiheck, i think the openstack certified administrator materials/exam still use a several-years-old release23:40
fungidocs that are still mostly correct because the software hasn't changed much is great, in my opinion. the problem is outdated docs which are misleading/dangerous because of how things have changed23:41
spotz[m]Last one I did was 3-4 years ago, when Mirantis did it's first version which was really their test with the COA name on it23:43
fungiterribly wrong docs are better deleted if they're not going to be corrected. mostly correct docs are better left up even if nobody has time to update them. the trick is figuring out which is which23:43
clarkbwithin the "core" services user interactions haven't changed a whole lot in the last 4-5 years.23:43
clarkbthere are of course exceptions for new features, and I bet deployment related stuff chagnes due to underlying changes in the systems openstack depends on23:44

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