| clarkb | in theory with a new attempt at fulfilling the request | 00:02 |
|---|---|---|
| clarkb | I guess we'll wait and see | 00:02 |
| opendevreview | OpenStack Proposal Bot proposed openstack/project-config master: Normalize projects.yaml https://review.opendev.org/c/openstack/project-config/+/905042 | 03:22 |
| frickler | the stuck job seems to have been run successfully now. I guess that gets a record for longest buildset duration https://zuul.opendev.org/t/openstack/buildset/1780890499394632aa7eeadde6de5af7 | 05:41 |
| opendevreview | Merged openstack/project-config master: Normalize projects.yaml https://review.opendev.org/c/openstack/project-config/+/905042 | 05:57 |
| opendevreview | Merged openstack/diskimage-builder master: Add san support to growvols https://review.opendev.org/c/openstack/diskimage-builder/+/903265 | 14:43 |
| clarkb | oh good I'm glad we could get that unstuck | 15:37 |
| opendevreview | Merged openstack/project-config master: [Neutron-tempest-plugin] Update Grafana Dashboard https://review.opendev.org/c/openstack/project-config/+/902184 | 16:19 |
| corvus | #status log increased project.zuul afs volume quota to 5gb | 16:31 |
| opendevstatus | corvus: finished logging | 16:31 |
| mtreinish | I've got a fairly random question, I had a couple of people asking me recently about https://opendev.org/opendev/mqtt_statsd as they had some interest in using it. If I wanted to revive the project and modernize it a bit what would be the best course of action? I'm just wondering if I should just fork it to somewhere else or push up a revert of the retirement commit to gerrit and go from there? | 18:33 |
| clarkb | mtreinish: I think the idea with the retirement commits was always that things could be revived if people showed up and wanted to revive things. Also happy for you to fork to github or whatever if you prefer | 18:34 |
| clarkb | basically the retirement commits are a way of communicating inactivity in a clear and direct manner while making it reversible | 18:34 |
| fungi | yeah, resumption is one revert (and maybe some boilerplate updates for things that have changed with ci jobs et cetera) away | 18:35 |
| mtreinish | ok sounds good, well I'll just revert and try to get everything working again. Lol, a lot is stale in it, the last real commit was ~7 yrs ago | 18:36 |
| fungi | let us know if you have questions | 18:36 |
| mtreinish | thanks | 18:37 |
| clarkb | also hi there! | 18:41 |
| clarkb | mtreinish: is reviving old code bases what you do when burried under feet of snow? | 18:41 |
| opendevreview | Matthew Treinish proposed opendev/mqtt_statsd master: Revert "Retire this repo" https://review.opendev.org/c/opendev/mqtt_statsd/+/905142 | 18:47 |
| mtreinish | clarkb: heh, well the rain just came in so the foot of snow is starting to disappear a bit | 18:54 |
| mtreinish | but yeah it's my happy place I guess :) | 18:59 |
| * frickler needs a bit of a break after tc meeting, will bbl | 19:01 | |
| fungi | ooh, we're famous: https://news.ycombinator.com/item?id=38929677 | 21:08 |
| * JayF puts on his influencer hat and paints his face orange | 21:10 | |
| JayF | TIME TO GET IN THERE! | 21:10 |
| fungi | the first comment makes it obvious that we don't provide any indication of how long we've been around | 21:11 |
| fungi | (under one name or another we're about as old as github) | 21:11 |
| fungi | github has about three years on us, but almost nobody had heard of them in 2010 | 21:12 |
| fungi | maybe this will translate into a larger peanut gallery for our openinfra.live episode next week | 21:14 |
| JayF | fungi: https://news.ycombinator.com/item?id=38932222 | 21:17 |
| JayF | fungi: I have edit on that for ~5m if anything is horrendous, if anything is only slightly wrong feel free to reply | 21:17 |
| TheJulia | JayF: well said | 21:20 |
| fungi | lgtm | 21:20 |
| * TheJulia waves hello at StevenK :) | 21:20 | |
| fungi | i also love how one of the comments is like "for some reason people won't stop using openstack" | 21:20 |
| JayF | fungi: I know I am often a voice that advocates for OpenStack to open portals up to other patterns of contribution (Github). I hope you all know that is never a reflection on how great a job you all do running infra (maybe is more of a reflection on how crap a job our whole community is at gaining mindshare :/) | 21:21 |
| fungi | oh i know! | 21:25 |
| opendevreview | Merged opendev/system-config master: Enable gitea delete_repo_archives cron job https://review.opendev.org/c/opendev/system-config/+/904874 | 21:27 |
| clarkb | tonyb: I think meetpad_jvb_xmpp_server is the variable that jvb's use to join the cluster | 21:39 |
| clarkb | tonyb: in playbooks/roles/jitsi-meet/templates/jvb-env.j2 we set XMPP_SERVER={{ meetpad_jvb_xmpp_server }} which causes that jvb to come up and connect to that xmpp server to determine the state of the cluster and join it. THere is also an auth password set in that file that I believe is necessary to connect successfully | 21:40 |
| clarkb | tonyb: if we want to do different clusters and then just swap dns over at once I think we need to have that value talk to a new server which would be possible by putting the jvb servers in two different groups. Or even just temporarily removing the extra jvb in production and only use it in the new setup. We can probably handle that load since there aren't any events relyign on the | 21:43 |
| clarkb | ptg in the near future | 21:43 |
| clarkb | that said I think we can just replace the jvb then replace the meetpad server and it'll be fine | 21:43 |
| tonyb | clarkb: thanks. at this point I'm not sure which is better testable. | 22:08 |
| tonyb | clarkb: I like the idea of both approaches for different reasons. | 22:09 |
| clarkb | tonyb: adding a new jvb is really low impact which makes that path attractive to me | 22:09 |
| clarkb | basically add it, then check logs to make sure it gets some calls eventually | 22:09 |
| clarkb | but now i must do a school run. back in a bit | 22:10 |
| tonyb | kk | 22:10 |
| clarkb | I didn't specify an election schedule for the first half of 2024 during the second half of 2023 election. THe nomination period then ran for 2 weeks from august 8 to august 22. Roughly 6 months after then is February 6 - 20, 2024 | 23:23 |
| clarkb | I think I'll propose February 6-20 for nominations and 21-28 for an election if we need one | 23:24 |
| clarkb | I don't think that conflicts with any major holidays or events (fosdem happens just prior). Please say somethign if I've missed anything important | 23:24 |
| clarkb | also appologies to Valentines day for considering it a non major holiday | 23:25 |
| tonyb | IIRC it's *likely* OpenStack elections will start on the 14th anyway. | 23:26 |
| fungi | sounds fine to me | 23:26 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!