| *** bauzas4 is now known as bauzas | 02:07 | |
| opendevreview | Goutham Pacha Ravi proposed openstack/security-doc master: Add OSSN-0095: OVN security group rules with address groups https://review.opendev.org/c/openstack/security-doc/+/985734 | 03:41 |
|---|---|---|
| sean-k-mooney | gouthamr: https://review.opendev.org/c/openstack/devstack/+/985735 so i have a hacky seriese that swap out pip for uv in devstack | 10:57 |
| sean-k-mooney | its not terrirble but needs work | 10:57 |
| sean-k-mooney | but last night i pushed that dnm to turn it on and use python 3.14 | 10:58 |
| sean-k-mooney | one of the benifits of using uv is i cna have it provide effectivly any python interpertor on any distop | 10:58 |
| sean-k-mooney | https://zuul.opendev.org/t/openstack/buildset/da24501f7c384e448209691fa86eb5e0 | 10:59 |
| sean-k-mooney | so there are failures and at least one issue witht he novnc proxy | 10:59 |
| sean-k-mooney | but several of the jobs also passed | 10:59 |
| sean-k-mooney | i.e. tempest-ipv6-only https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_833/openstack/833846ede07649d28e8a498e53dfa9f0/testr_results.html | 11:00 |
| sean-k-mooney | or swift-dsvm-functional https://ef81aef4c6916aa88fc4-0a0d2e256244e0f6c0db62d1482e6a6c.ssl.cf2.rackcdn.com/openstack/d04052cc032a4009b464c37bf5275a1f/testr_results.html | 11:03 |
| sean-k-mooney | because that serise is using uv to provide the python inteperator and all python packages it also works the same across distos | 11:04 |
| sean-k-mooney | im going to push a dnm ot nova to tirger its jobs with 3.14 to get a better picture of where we stand but this at least shows openstack is fucntional enough to boot vms and stack with python 3.14 | 11:07 |
| sean-k-mooney | even if we have some bugs to fix | 11:07 |
| bauzas | gouthamr: I'm afraid the TC session about AI on Friday @15.40pm UTC will be busy | 12:09 |
| bauzas | we have lots of conversations around the new agentic-worflows project | 12:09 |
| bauzas | while the contrib guidelines could take precedence (but those should IMHO be discussed at the board level) | 12:10 |
| sean-k-mooney | bauzas: the ortingally inte of the ptg topic was intende to be "should we have any ai related files in teh repo and shoudl we create a common repo for agentic tools" | 12:11 |
| sean-k-mooney | so not really implemation detail sof the agentic-workflows repo itself | 12:11 |
| bauzas | then we need to book another timeslot for the project itself discussions | 12:12 |
| sean-k-mooney | sure | 12:12 |
| bauzas | but we don't have any placeholder for it | 12:12 |
| sean-k-mooney | but that why i ask that we dont creat any content in the repo until after the ptg | 12:12 |
| bauzas | that's a chicken-and-egg problem (again) | 12:13 |
| sean-k-mooney | i want use to have the converation fo if it shoudl be doen and how before creatign the repo | 12:13 |
| sean-k-mooney | its not | 12:13 |
| bauzas | how can I book a room ? simple question that I even don't have the answer | 12:13 |
| sean-k-mooney | we could just point to the project on github and the gerrit reviews in teh repo | 12:13 |
| sean-k-mooney | #<name> book <room name> in #openinfra-events | 12:14 |
| sean-k-mooney | where name is the track name | 12:14 |
| bauzas | thank you, I was knowing it :) | 12:14 |
| bauzas | but which would be the track name given we don't have any official project already ? | 12:15 |
| sean-k-mooney | im not sure if the bot cares so you can try #openstack-agentic-workflows | 12:18 |
| bauzas | the bot will care | 12:20 |
| bauzas | the tracks have to be approved | 12:21 |
| bauzas | I can surely talk to diablo_rojo or other #openinfra-events cores to ask them to create another track if that helps | 12:22 |
| bauzas | but fwiw, that's not that simple | 12:22 |
| sean-k-mooney | looks like thr tact sig does not have a track | 12:29 |
| bauzas | no they don't | 12:29 |
| bauzas | the list of tracks are basically the ones in https://ptg.opendev.org/etherpads.html | 12:30 |
| sean-k-mooney | im not really sure we will have time for a deep proejct specific topic by the way | 12:30 |
| sean-k-mooney | or at least fienidn a slot will be hard thar works for every eone | 12:30 |
| fungi | sean-k-mooney: bauzas: i can add a track if you need | 12:53 |
| * gouthamr wakes up and reads scrollback | 13:10 | |
| bauzas | fungi: if you can create a track, that would be nice so we could discuss about some internal chances after the TC topic | 13:11 |
| bauzas | changes* | 13:11 |
| gouthamr | could this wait beyond the week? | 13:12 |
| gouthamr | asking because i think people would like to participate, but could be signed up for all the fun elsewhere | 13:13 |
| opendevreview | Goutham Pacha Ravi proposed openstack/security-doc master: Add OSSN-0095: OVN security group rules with address groups https://review.opendev.org/c/openstack/security-doc/+/985734 | 14:01 |
| cardoe | Do we have Golang as a permitted runtime in OpenStack? I'm looking at https://governance.openstack.org/tc/reference/runtimes/2026.1.html | 14:03 |
| fungi | cardoe: https://governance.openstack.org/tc/reference/pti/golang.html and https://governance.openstack.org/tc/resolutions/20170329-golang-use-case.html may be relevant | 14:06 |
| fungi | there was an intent to permit go development, but the two go-based projects people were working on never came to fruition for various reasons so there currently are none in openstack | 14:07 |
| fungi | whether it's permitted is somewhat academic at this point, as any likely support that was put in place 9 years ago is almost certainly bitrotten at the moment so it would be a good idea to discuss specifics among the tc | 14:08 |
| fungi | there was basically no incentive to keep up the details from a pti perspective without any actual projects to exercise and inform them | 14:09 |
| gouthamr | fungi: clarkb: some helpful launchpad folks fixed up all the team ownership concerns we had: https://answers.launchpad.net/launchpad/+question/824113 | 17:21 |
| gouthamr | everything seems to be owned by openstack-admins now.. i'll use this as my source and run another check: https://opendev.org/openstack/project-config/src/branch/master/gerrit/projects.yaml | 17:22 |
| clarkb | great. that seems like the best possibile outcome? | 17:23 |
| gouthamr | we sought ownership transfer for retired teams as well (so we can own their cleanup if any) | 17:24 |
| gouthamr | yes! a couple of todos: | 17:28 |
| gouthamr | - write up the launchpad tracker configuration tribal knowledge in the project team guide, useful for new projects | 17:28 |
| gouthamr | - think through cleanup for retired/deprecated stuff | 17:28 |
| fungi | gouthamr: sounds great! i guess if somebody can put together a list of changes we need openstack-admins members to make to any of those (like adding current ptls and setting them as administrators), i'm happy to work through them | 17:28 |
| gouthamr | oh, yes that too | 17:29 |
| fungi | though one thing that would really help is knowing the ptls' lp usernames, it's not always obvious and sometimes vague as to which account is the actual person | 17:30 |
| gouthamr | fungi: i'll ask for that on openstack-discuss.. mnasiadka (https://launchpad.net/~mnasiadka) wanted access to the magnum teams (https://launchpad.net/~magnum-drivers, https://launchpad.net/~magnum-ui-drivers) | 17:30 |
| fungi | most of the time i can get by on educated guesses or tracking down a bug they interacted with on the correct project, but if people have non-unique names the risk increases that i'll pick the wrong lp account | 17:31 |
| * gouthamr chuckles at non unique names | 17:31 | |
| fungi | i can take care of the magnum ones now | 17:31 |
| mnasiadka | Yay | 17:31 |
| fungi | mnasiadka's lp account is easy to find, compared to many | 17:32 |
| fungi | mnasiadka was already a member and administrator on magnum-drivers, but i've added him to magnum-ui-drivers now similarly | 17:34 |
| gouthamr | ty! | 17:34 |
| mnasiadka | Thanks! | 17:43 |
| fungi | but of course! | 17:46 |
| frickler | I stumbled across https://launchpad.net/~openstack-ossg earlier today, that also looks like it could do with some refreshing | 18:47 |
| fungi | yes, it's hopefully no longer relevant | 18:48 |
| fungi | i did finally make a long-overdue change to the https://launchpad.net/ossn project to stop sharing private security bugs with ~openstack-ossg | 18:49 |
| fungi | recently | 18:49 |
| fungi | back in the ossg days when that was set up, we didn't anticipate writing ossns in secret, the idea was that anything that was getting an ossn drafted should already be public | 18:51 |
| fungi | but tha was somewhat tribal knowledge, and in more recent years people have added ossn bugtasks to embargoed reports of suspected vulnerabilities | 18:52 |
| fungi | i guess it's still the driver for https://launchpad.net/ossp-security-documentation which is the tracker for openstack/security-doc | 18:57 |
| opendevreview | Goutham Pacha Ravi proposed openstack/security-doc master: Add OSSN-0095: OVN security group rules with address groups https://review.opendev.org/c/openstack/security-doc/+/985734 | 20:51 |
| * gouthamr was finally taking the maintainers' survey.. | 21:34 | |
| * gouthamr there's a question: "How many times did you refer to your project’s Contributor Guide over the most recent release cycle?*" and it has only one choice: 0 | 21:34 | |
| gouthamr | fungi: don't suppose that's a clever joke :D | 21:34 |
| fungi | it's a nagging bug in the survey platform that ildikov has been unable to find a solution to | 21:34 |
| fungi | every time we think it's fixed, it comes back | 21:35 |
| gouthamr | oh :( i don't remember if the last one had this question | 21:35 |
| fungi | it seems like surveymonkey doesn't like multiple-choice answers that start with digits for some reason, though it's still unclear since some of the possible workarounds didn't... workaround | 21:36 |
| gouthamr | oh, workaround is to switch the choices to "Never", "Sometimes (<10 times)", "A lot (>10 times)"? | 21:37 |
| fungi | yeah, i think we tried something like that, i can't recall what happened though | 21:38 |
| gouthamr | ack, will ignore this question and move on.. | 21:40 |
| opendevreview | Goutham Pacha Ravi proposed openstack/security-doc master: Use upper-constraints for tox environments https://review.opendev.org/c/openstack/security-doc/+/985897 | 21:45 |
| opendevreview | Merged openstack/security-doc master: Add OSSN-0095: OVN security group rules with address groups https://review.opendev.org/c/openstack/security-doc/+/985734 | 21:58 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!