| tonyb | the RH folks that care about os-net-config tried to continue with hosting it on opendev but the appetite seemed low so they went elsewhere | 07:29 |
|---|---|---|
| tonyb | Alos mnasiadka meeting in roughly 30mins right? | 07:30 |
| mnasiadka | Ah right | 07:31 |
| mnasiadka | tc-members - meeting in ~28 minutes | 07:32 |
| tonyb | mnasiadka: I didn't mean to nag, more confirming I have the correct date. | 07:35 |
| mnasiadka | tonyb: it’s correct - but it’s 8:35 AM - so pardon my non-focus :) | 07:35 |
| tonyb | lol of course | 07:36 |
| mnasiadka | #startmeeting tc | 08:00 |
| opendevmeet | Meeting started Tue Nov 18 08:00:16 2025 UTC and is due to finish in 60 minutes. The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:00 |
| opendevmeet | The meeting name has been set to 'tc' | 08:00 |
| mnasiadka | Welcome 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. | 08:00 |
| mnasiadka | Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee | 08:00 |
| mnasiadka | #topic Roll Call | 08:00 |
| tonyb | o/ | 08:00 |
| mnasiadka | o/ | 08:00 |
| gtema | o/ | 08:00 |
| mnasiadka | courtesy-ping: gouthamr, noonedeadpunk, frickler, spotz[m], cardoe, bauzas | 08:02 |
| mnasiadka | #topic Last Week's AIs | 08:04 |
| mnasiadka | Analyze user survey results | 08:04 |
| mnasiadka | We need a volunteer for this - if there are none - it will get moved to TC tracker (in the hope somebody wants to pick it up later) | 08:05 |
| mnasiadka | Assuming no volunteers - will move it to the tracker after the meeting | 08:06 |
| gtema | I can't see for myself what can be useful in that data in that form | 08:06 |
| tonyb | I'm curious what analysis there is for us to do? but happy let it move to the tracker | 08:06 |
| mnasiadka | Me neither, but it seems usually somebody from the TC did an analysis and published that | 08:07 |
| mnasiadka | #link https://governance.openstack.org/tc/user_survey/analysis-2023.html | 08:07 |
| mnasiadka | As an example | 08:07 |
| gtema | it feels like a yet another survey where nobody has really idea what is this good for | 08:07 |
| gtema | slaweq was preparing this overview if I recall correctly | 08:08 |
| tonyb | I can see it's value for the foundation and for the TC in very specific cases | 08:08 |
| mnasiadka | I personally feel the user survey has too many possible fields to fill out or the input is a bit vague (e.g. you can choose ‘Ansible’ as your deployment tool) | 08:08 |
| gtema | the results analysis should be done by the people who came with those questions | 08:09 |
| mnasiadka | Oh it surely should | 08:09 |
| mnasiadka | But let’s move that to the tracker for now | 08:09 |
| mnasiadka | Our discussion doesn’t really help in finding a solution for the analysis | 08:09 |
| mnasiadka | Next one - Draft TC resolution on os-net-config handover (gouthamr) | 08:09 |
| mnasiadka | #link https://review.opendev.org/c/openstack/governance/+/967463 (2025-11-17 Retirement and Handover of the `os-net-config` Project) | 08:09 |
| tonyb | I'll add my views to the review but in general I don't think there's alot for the 3 of us on that one? | 08:11 |
| gtema | indeed | 08:11 |
| mnasiadka | Yeah, I just commented on this | 08:11 |
| mnasiadka | Let’s move forward | 08:11 |
| mnasiadka | Propose document change to redirect os-net-config docs link to git repo README (gouthamr) | 08:12 |
| mnasiadka | No need to discuss that | 08:12 |
| mnasiadka | Ok, next one is | 08:12 |
| mnasiadka | Rework FIPS goal objectives and testing requirements (volunteer needed, move to tracker if no-one interested) | 08:12 |
| mnasiadka | I personally have no interest in FIPS, given it’s for one country - is there any volunteer interested in FIPS? If no - we’ll move that to the tracker (given no traction/interest to date) | 08:13 |
| gtema | oh lol - move everything to tracker ;-) | 08:13 |
| tonyb | get that ^^ man a beer/coffee! | 08:14 |
| mnasiadka | And then we send the tracker to /dev/null? lol | 08:14 |
| tonyb | :D | 08:14 |
| gtema | correct - that was a not-expressed thought | 08:14 |
| mnasiadka | Well, let’s keep it recorded - but if there’s no interest - we can’t really do anything | 08:14 |
| mnasiadka | Next one | 08:15 |
| mnasiadka | Update/document procedure to preserve project appointment history (tonyb) | 08:15 |
| mnasiadka | tonyb: any updates? | 08:15 |
| * tonyb has no recollection of this item | 08:15 | |
| mnasiadka | Hmm, that’s interesting - I think it came up regarding the recent telemetry PTL switch | 08:16 |
| tonyb | Can we add a meta-AI for me to figure out what it is and then either do it or correct the AI | 08:16 |
| tonyb | Sounds plausible | 08:16 |
| mnasiadka | No other option - I’ll leave it in AIs on the wiki :) | 08:17 |
| tonyb | \o/ | 08:17 |
| mnasiadka | Next one is: Clarify and document AI/LLM policy/instructions for Project Team Guide | 08:17 |
| mnasiadka | But cardoe (who’s name is against the AI in the wiki) is not here | 08:17 |
| mnasiadka | So let’s move on | 08:17 |
| mnasiadka | Investigate adding ""archived"" state to retired PyPI projects (volunteer needed, move to tracker if no-one interested) | 08:18 |
| tonyb | I can look at that. I'm not 100% certain of the value but I can look at the technical aspects | 08:18 |
| mnasiadka | #link https://blog.pypi.org/posts/2025-01-30-archival/ | 08:18 |
| mnasiadka | This looks like something new this year in pypi | 08:19 |
| gtema | I personally like very much when projects on github are explicitly marked archived | 08:19 |
| mnasiadka | tonyb: thanks | 08:19 |
| gtema | it gives a clear signal - keep away | 08:19 |
| mnasiadka | I’m not sure how different is retired vs archived in pypi | 08:19 |
| mnasiadka | But that’s probably for tonyb to find out :) | 08:20 |
| gtema | yeah | 08:20 |
| tonyb | Hopefully is adds a banner like "this project is read-only" similar to github and others | 08:20 |
| mnasiadka | That would be nice, I agree | 08:20 |
| mnasiadka | Ok, that’s all of the AIs from last week | 08:20 |
| mnasiadka | #topic Monasca Retirement | 08:20 |
| mnasiadka | #link https://review.opendev.org/q/hashtag:%22monasca-retirement%22+(status:open%20OR%20status:merged) | 08:21 |
| mnasiadka | The repository cleanup patches need to be merged. However, openstack/monasca-api and openstack/monasca-events-api are failing with zuul errors. | 08:21 |
| mnasiadka | It's possible older stable and unmaintained branches need to be deleted too, to fix the cleanup on master. Need some help from the release team or TaCT SIG on how to proceed | 08:21 |
| mnasiadka | That’s status from gouthamr | 08:21 |
| mnasiadka | tonyb: It seems that the foundation member you mentioned hasn’t really acted - do you have any more information on that? | 08:22 |
| tonyb | give me the AI I can look at it from a TaCT POV | 08:22 |
| gtema | it upsets me how a single item can hold the whole community for 4-5 month now already? Just kill it and let people move forward, why are we taking so long on making an action | 08:22 |
| gtema | sorry, this was rhetoric | 08:23 |
| mnasiadka | gtema: I agree the time to do it was long time ago, so let’s at least not stall it this time - I’ll try to help gouthamr in progressing that | 08:23 |
| mnasiadka | tonyb: AI granted :) | 08:23 |
| tonyb | mnasiadka: It looks like *if* they're going to use it it wont be for 12months | 08:23 |
| mnasiadka | Ah, *if*, then I don’t think we should really still wait. | 08:23 |
| mnasiadka | Ok then, going forward | 08:24 |
| mnasiadka | #topic TC Tracker, PTG Follow up | 08:24 |
| mnasiadka | #link https://etherpad.opendev.org/p/tc-2026.1-tracker (Technical Committee activity tracker - 2026.1) | 08:24 |
| tonyb | Yup I thought we'd agreed to retire monasca I'm sorry if I was holding things up by mistake | 08:25 |
| noonedeadpunk | oops | 08:25 |
| * noonedeadpunk completely forgot about morning one | 08:25 | |
| mnasiadka | There’s the OpenStack Survey improvements topic there - I feel we should try to work for the data (that usually come from manual analysis) to be visible in a more dynamic way (maybe on the user survey webpage or something similar) | 08:25 |
| mnasiadka | The deadline for submitting questions to survey is 1st Dec 2025 - for these that are interested | 08:26 |
| mnasiadka | There’s also an etherpad with TC PTG summary | 08:27 |
| mnasiadka | #link https://etherpad.opendev.org/p/oct2025-ptg-os-tc-summary | 08:27 |
| mnasiadka | And a mail by gouthamr to the openstack-discuss ML | 08:27 |
| mnasiadka | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/RX3MZE33GEDV5JDHORZKRUKVDP47UMLJ/ | 08:27 |
| mnasiadka | tonyb: looking at tracker L119 and L124 - seems you have some AI in there - although I don’t know what needs to be done | 08:28 |
| tonyb | mnasiadka: I do, I just haven't done it | 08:28 |
| mnasiadka | noonedeadpunk: no worries, no AIs on you (yet) ;-) | 08:29 |
| mnasiadka | tonyb: thank you for the update :) | 08:29 |
| tonyb | LOL | 08:29 |
| mnasiadka | Ok then, to next topic | 08:29 |
| mnasiadka | #topic Python PTI and test runner guidance | 08:29 |
| mnasiadka | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/3V3CNPQLB77SKFVLZ6LXJ5NPNYWW4QFD/ | 08:29 |
| gtema | mdasiadka and noonedeadpunk: wrt PQC, I am supporting that to a certain extend and wanted to drop passlib (a completely dropped lib) from our requirements and noticed that it is now only used in the deployment toolings | 08:29 |
| mnasiadka | (Request for guidance on improving Python PTI doc to include pytest for Horizon plugins testing) | 08:29 |
| gtema | would you be open still getting rid of it? Well, it is not a question honestly - this must be done. Period. | 08:30 |
| mnasiadka | gtema: Sure, happy to do it in Kolla-Ansible - can you maybe start an openstack-discuss ML thread pointing to the repositories using it and we could track it that way? | 08:31 |
| gtema | https://opendev.org/openstack/-/code?q=passlib&search_mode=exact | 08:31 |
| mnasiadka | #link https://codesearch.opendev.org/?q=passlib&i=nope&literal=nope&files=&excludeFiles=&repos= | 08:31 |
| gtema | but sure, I can start the thread and prepare change dropping it from requrements | 08:32 |
| noonedeadpunk | gtema: looking at codesearch, osa does not need it | 08:32 |
| gtema | right, but who is openstack/openstack-ansible-ops? | 08:32 |
| noonedeadpunk | but bifrost on other hand seems tro rely on it? | 08:33 |
| tonyb | gtema: I think that the openstack-ansible SIG? | 08:33 |
| gtema | and who nowadays owns openstack/deb-* repos | 08:33 |
| noonedeadpunk | yeah, osa. but you can drop it and let it fail :) | 08:33 |
| gtema | ah, ok | 08:33 |
| noonedeadpunk | or well. I can clean it up later this week | 08:33 |
| gtema | thanks. | 08:34 |
| noonedeadpunk | I think openstack-ansible-ops is not actually following requirements framework anyway | 08:34 |
| gtema | Sorry for the delayed message that broke the topic boundary | 08:34 |
| noonedeadpunk | it's pile of operator tooling, half of which should be refactored or dropped at this point anyway | 08:34 |
| mnasiadka | K-A only uses passlib[bcrypt] for generating passwords, we can surely use something else | 08:35 |
| mnasiadka | gtema: any recommendations? ;-) | 08:35 |
| noonedeadpunk | we use haslib I think | 08:35 |
| gtema | bcrypt is what keystone uses by default, but today the modern recommendation is to use argon2 | 08:36 |
| noonedeadpunk | not sure if it's better | 08:36 |
| gtema | hashlib is bad, you should be using salt based hashing. In germany this is a requirement on the governmental level | 08:36 |
| gtema | #link https://argon2-cffi.readthedocs.io/en/stable/ | 08:37 |
| noonedeadpunk | salt hashing for random password generator? | 08:37 |
| gtema | this is what people should be using today | 08:37 |
| mnasiadka | Ok, I’ll have a look in argon2 | 08:37 |
| gtema | whenever you store password hash in the DB it must be salt based hashing | 08:37 |
| noonedeadpunk | can you supply a salted password to keystone when creating a service user? | 08:37 |
| gtema | not the salted password - the salted hash of the password | 08:38 |
| noonedeadpunk | but how you'd call openstack.cloud.identity_user with that? | 08:39 |
| gtema | bcrypt is still safe, but argon is more future proof | 08:39 |
| noonedeadpunk | or, `openstack user create`? | 08:39 |
| gtema | noonedeadpunk - nothing changes on the password logic itself, only when you store the hash in the DB you should be applying salt to it - it has nothing to do with ansible modules for openstack | 08:40 |
| noonedeadpunk | yes, but there's no database. And for storage it's supposed that Ansible Vault will be used | 08:40 |
| noonedeadpunk | But you need to generate passwords in more or less plain text so that they could be supplied to services to create db/keystone/rabbitmq/etc users | 08:41 |
| noonedeadpunk | so in context of deployment tools salting is irrelevant I'd assume | 08:41 |
| tonyb | ... Can we move this to after the meeting. It's valuable but also a tangent. | 08:41 |
| noonedeadpunk | ++ | 08:41 |
| gtema | here there is nothing what we can do so far - those passwords stay in plain text in config files | 08:41 |
| mnasiadka | Ok, let’s move it after meeting | 08:42 |
| mnasiadka | And get back to the original topic - pytest for Horizon plugins | 08:42 |
| noonedeadpunk | mnasiadka: fwiw https://opendev.org/openstack/openstack-ansible/src/branch/master/scripts/pw-token-gen.py - the thing we have | 08:42 |
| gtema | wrt pti I would like to recall the discuss thread of Clark - we should establish a platform for reviewing old rules | 08:42 |
| gtema | I think I have expressed my opinion in multiple threads clear enough | 08:43 |
| * noonedeadpunk need to get time to finally respond to these threads | 08:43 | |
| gtema | and the horizon folks themselves made a summary of the discussions to clarify their next steps | 08:44 |
| mnasiadka | I agree with gtema - but I think this needs more people than 4 on a TC meeting - especially that noonedeadpunk is not up to date with the thread | 08:45 |
| gtema | sure | 08:45 |
| noonedeadpunk | I read it, I just never managed to respond as so many things to cover.... | 08:45 |
| mnasiadka | Ok, I’ll leave that for the next meeting | 08:45 |
| mnasiadka | To the next topic... | 08:45 |
| mnasiadka | #topic oslo.wsgi | 08:45 |
| mnasiadka | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/IW2ZMYXGZQFPSLJRVT5OKFFX7XRGM2FF/ | 08:46 |
| gtema | not sure what is expected to be discussed here | 08:46 |
| mnasiadka | TL;DR - there’s a proposal to create oslo.wsgi - all of the information is in the thread | 08:46 |
| gtema | go for it, but do not make it a MUST | 08:46 |
| noonedeadpunk | I think there was a general agreement that it's a good idea? | 08:46 |
| tonyb | I feel like that's squarely in the oslo teams perview | 08:46 |
| mnasiadka | tonyb: ++ | 08:47 |
| tonyb | We can reply with "match the import and governance patches" which is all I can see as being missing? | 08:48 |
| mnasiadka | So I guess there’s nothing to discuss, the thread replies from Oslo team and others indicate it’s a good idea - so I assume the requestor will follow up with governance patches | 08:48 |
| mnasiadka | Moving forward | 08:48 |
| mnasiadka | #topic A check on gate health | 08:48 |
| mnasiadka | Is there anything worth mentioning? | 08:48 |
| tonyb | I can't think of anything. | 08:49 |
| tonyb | gerrit and gitea have been updated in the last week | 08:49 |
| tonyb | but they both went well | 08:49 |
| mnasiadka | Ok then, happy to hear that | 08:50 |
| mnasiadka | #topic Open Discussion and Reviews | 08:50 |
| tonyb | We (infra-root) "discovered" a cool new zuul feature in the process | 08:50 |
| *** elodilles_pto is now known as elodilles | 08:51 | |
| tonyb | I don't have anything for Open Discussion | 08:51 |
| gtema | which is it? | 08:51 |
| mnasiadka | tonyb: cool? Which is? | 08:51 |
| tonyb | gtema: You can pause the scheduler, so that if gerrit is unavailable it wont trigger a merge failure and then force those commits to be re-tested | 08:52 |
| noonedeadpunk | oh, nice | 08:52 |
| tonyb | It helps in a very narrow window but when it does it saves hours of "recheck" | 08:52 |
| gtema | I haven't had merge failures often. It is usually a regular timeouts recheck madness | 08:53 |
| mnasiadka | tonyb: ah, that’s what happened with my patch when it was “ready to submit” during some Zuul restart window ;-) | 08:53 |
| noonedeadpunk | when you restart gerrit or upgrade gerrit - that really helpful indeed | 08:53 |
| tonyb | Yeah this is really for when gerrit is down/unavailable | 08:53 |
| tonyb | mnasiadka: That's different but similar | 08:54 |
| mnasiadka | ack | 08:54 |
| mnasiadka | Ok then, I see no open discussion topics | 08:54 |
| mnasiadka | Thank you all for attending, see you next week in the regular timeslot | 08:55 |
| mnasiadka | #endmeeting | 08:55 |
| opendevmeet | Meeting ended Tue Nov 18 08:55:04 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 08:55 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tc/2025/tc.2025-11-18-08.00.html | 08:55 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2025/tc.2025-11-18-08.00.txt | 08:55 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2025/tc.2025-11-18-08.00.log.html | 08:55 |
| tonyb | Thanks all | 08:55 |
| gtema | thanks, see ya | 08:55 |
| mnasiadka | noonedeadpunk: Now we can continue the keystone/salts/passwords/whatever topic ;-) | 08:55 |
| gtema | sure, but in 5 min I need to jump to next meeting | 08:55 |
| gtema | but is then available 20 min later | 08:55 |
| gtema | s/is/am/ | 08:56 |
| noonedeadpunk | yeah. I think we were just talking about different things | 09:01 |
| noonedeadpunk | as there's nothing to store for us in salted manner, as there's no db for osa | 09:01 |
| noonedeadpunk | the db is vars files containing secrets that are to be written to service dbs | 09:01 |
| gtema | yes, I think so. Unless you store passwords somewhere on the FS to be able to validate whatever user passes (like the /etc/passwd) - you are good | 09:13 |
| frickler | meh, I totally missed that we have the early time slot this week, did take extra care to reserve the evening even if I'm mostly not around | 09:56 |
| frickler | regarding monasca, I did plan to look at the retirement patches and force-merge them if necessary. only noticed last week that they were un-wip-ed | 09:57 |
| frickler | for FIPS, if there is no interest in continuing with the goal, maybe someone has interest to do the opposite and mark the goal as terminated? and possibly clean up broken jobs? | 09:58 |
| bauzas | oh shit, missed the TC meeting :( | 10:48 |
| bauzas | TheLounge can provide me some notifications but if I don't see them, I forget them :( | 10:49 |
| mnasiadka | That’s completely fine everybody from EU is complaining about regular meeting time, but the one time in the month we all forget about it (and I remembered about it only because gouthamr reminded me about it) :) | 10:58 |
| bauzas | I'll just add the ICS file in my google agenda | 11:00 |
| bauzas | just in case people don't know : https://meetings.opendev.org/#Technical_Committee_Meeting | 11:01 |
| cardoe | Yeah I’m not gonna make the EU timed ones. It’s 2am to 3am for me. | 13:39 |
| fungi | just a quick follow-up on the password hashing discussion, salted (and peppered) hashes are still an outdated notion. use a key derivation function (kdf) with adjustable multi-round options and padding and such | 15:03 |
| fungi | (algorithms like bcrypt and argon2 are kdfs, so that's fine, it's more a matter of terminology) | 15:05 |
| clarkb | ya I was kind of hoping for more engagement on whether or not we think it is a good idea to formalize the 'evolution' process more concretely | 16:02 |
| clarkb | I don't think the actual mechanics of the process matter, but do believe performing some sort of sanity checking and updates as necessary is likely to be important | 16:02 |
| fungi | also, in the spirit of chesterton's fence, make sure any rule you're seeking to get rid of or replace is thoroughly understood first. don't take something away until you are clear on why it was implemented and what benefit it provided/still provides | 16:05 |
| fungi | openstack has a tradition of avoiding the addition of red tape and bureaucracy unless there's sufficient solid benefit to more than offset it, so looking at the history of a particular decision and getting a grasp of why it was made at the time is necessary if you want to avoid rediscovering problems we already solved | 16:07 |
| mnasiadka | I think that discussion needs to wait for next Tue - to have a proper quorum on the meeting… | 16:17 |
| clarkb | ack. Its a holiday week in the US (particularly thursday and friday), but I should be around tuesday and can discuss further then | 16:18 |
| clarkb | holiday week next week; not this week | 16:18 |
| mnasiadka | I’m not from the OpenStack historian society - but will the evolution require us to dig out old decisions that are not centrally stored? | 16:27 |
| clarkb | I think right now its mostly just a prompt to talk through these concerns. My personal perspective is that I think we as a community need to be more self deterministic and make decisions that work for the community arther than letting things happen and being forced to make changes. | 16:28 |
| clarkb | I think in general a lot of decisions have been reasonably well recorded (the historical data largely being in TC documents in git and gerrit for example) | 16:28 |
| fungi | mnasiadka: my usual tools for researching these decisions is git and gerrit, looking at the discussions in gerrit changes that implemented those choices and subsequent references to sources like tc meeting logs or mailing list posts | 16:31 |
| mnasiadka | Ack, just trying to understand if we have a list of decisions in mind | 16:32 |
| clarkb | for me the big ones that have come up recently are the PTI (and which platforms we map to the PTI eg centos stream) and which languages we accept. Golang was added and today we have zero code written in golang that we maintain aiui (so less even than a qusetion about rust, but its clear golang hasn't been effective imo). But also things like translation tooling (whcih is | 16:34 |
| clarkb | currently being actively modified but again due to forced decision making) | 16:34 |
| fungi | but basically anything documented in the governance repo is fair game to revisit if people feel something there is getting in the way | 16:35 |
| fungi | the pytest vs unittest decision in the pti falls into that category too based on recent discussion about horizon maintainers disagreeing with the that expectation | 16:36 |
| clarkb | and we can go further into things like wsgi which in our world really became uwsgi. There are multiple alternatives to wsgi now with a whole host of options in terms of server choice too | 16:37 |
| clarkb | eventlet was adopted far and wide, though I'm not sure if this was ever really official beyond the decision to update nova from twisted | 16:37 |
| clarkb | I think there is value in consistency for developers, operators, and users. But there is also value in being able to use appropriate tools for specific problems. That balance is likely to shift over time so I'm suggesting that we think about this balancing act more explicitly rather than only in reaction to emergencies | 16:40 |
| spotz[m] | o/ | 17:06 |
| spotz[m] | Well poo I had it on my calendar starting now! | 17:06 |
| fungi | you probably wouldn't have wanted to join a 2am meeting anyway | 17:11 |
| clarkb | I definitely didn't | 17:17 |
| fungi | would have been midnight for you, i think | 17:20 |
| clarkb | Peter Coyote had me falling asleep just after 10pm | 17:22 |
| * gouthamr catches up | 18:32 | |
| gouthamr | thank you for running the meeting mnasiadka \o/ | 18:32 |
| gouthamr | frickler: thanks for offering help with the 'problematic' monasca repos | 18:33 |
| gouthamr | i do like that tonyb made it, but hopefully, you folks can too.. remember though, going into the end of the year, a few meetings may be canceled. | 18:33 |
| gouthamr | you folks: for anyone that can reasonably get to their computer without having to douse themselves in caffiene | 18:34 |
| fungi | i bathe in the stuff, but 3am is a struggle... too late to not be too late, while too early to not be too early | 18:35 |
| gouthamr | :D | 18:35 |
| fungi | i can mostly convince myself to wake up at 4am now and then, but intentionally staying awake until 3am doesn't really happen at my age | 18:36 |
| fungi | it's insane to think back to the days of my youth when i'd go out clubbing until they kicked us out, then find 3am breakfast at an all-night diner, and get home with just enough time to shower and stagger into the office | 18:38 |
| * gouthamr feels like a long time ago, but didn't | 19:02 | |
| gouthamr | i was a regular at Cookout :P | 19:02 |
| gouthamr | omg fungi, if this is any close: https://www.outerbanksvoice.com/2025/11/08/cook-out-opens-its-doors-in-kdh/ | 19:05 |
| fungi | yeah, they had a line around the block | 19:05 |
| fungi | that's only a few miles from my house | 19:06 |
| gouthamr | hahaha, that's true for every day at 3am in Clemson, and probably lots of other places | 19:06 |
| gouthamr | very nice! | 19:07 |
| fungi | i don't know how long it'll survive here though, the local community isn't very fond of national chains and the 10x population swing between tourist season and off-season means restaurant businesses need to be able to adapt and staff up and down seasonally | 19:07 |
| clarkb | here in portland we had Le Bistro Montage. They are only a food cart now but once upon a time they had a restaurant under a bridge in the industrial area and were open all night | 19:07 |
| gouthamr | always need for that, we sleep too early | 19:09 |
| opendevreview | Goutham Pacha Ravi proposed openstack/openstack-manuals master: Re-direct tripleo docs to repos https://review.opendev.org/c/openstack/openstack-manuals/+/967617 | 22:06 |
| opendevreview | Goutham Pacha Ravi proposed openstack/governance master: 2025-11-17 Retirement and Handover of the `os-net-config` Project https://review.opendev.org/c/openstack/governance/+/967463 | 22:45 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!