!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

390 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.120 Servers

Load older messages


SenderMessageTime
28 Jan 2025
@jfly:matrix.orgJeremy Fleischman (jfly)

dgrig, you've correctly identified the state of things. The summary at the top of https://github.com/NixOS/infra/issues/485 is accurate. We need to set up some alerts for the mailserver. I just haven't taken the time to familiarize myself with prometheus and the blackbox alerting we have set up on pluto. I don't think there's a lot of work remaining there.

Here's an idea that feels low risk: we could set up this new mailserver to send emails alongside our existing improvmx account. That would let us start to test out this arrangment without breaking any existing send accounts.

23:26:19
@jfly:matrix.orgJeremy Fleischman (jfly)

For receiving, we have to either:

  • complete the rollout
  • OR, use improvmx to set up additional mailing lists

Do you have a sense of the timeline you're working on here?

23:27:10
@jfly:matrix.orgJeremy Fleischman (jfly)

team members receiving emails to a team's nixos.org address (should be somewhat easy to keep up to date who's in the recipient list, ideally eventually auto-synced with whatever mechanism is available for managing teams)

This is news to me. Is this github teams? Or something TBD that'll be used for sign-on to our new grist service?

23:28:40
@winter:catgirl.cloudWinterimprovmx can send emails already23:28:41
@jfly:matrix.orgJeremy Fleischman (jfly)yes, that's also definitely an option. i was just thinking this could be a nice, low-risk opportunity to test out the new mailservef23:29:05
@jfly:matrix.orgJeremy Fleischman (jfly)* yes, that's also definitely an option. i was just thinking this could be a nice, low-risk opportunity to test out the new mailserver23:29:06
@winter:catgirl.cloudWinter“reliable delivery” != “low-risk” ;)23:29:17
@winter:catgirl.cloudWinter * 23:29:49
@winter:catgirl.cloudWinter
In reply to @jfly:matrix.org

team members receiving emails to a team's nixos.org address (should be somewhat easy to keep up to date who's in the recipient list, ideally eventually auto-synced with whatever mechanism is available for managing teams)

This is news to me. Is this github teams? Or something TBD that'll be used for sign-on to our new grist service?

he means github teams || whatever alternate mechanism exists, if any, which i’m pretty sure the answer is “no” to
23:30:04
@jfly:matrix.orgJeremy Fleischman (jfly)Sure, I just mean it would be nice to test with 1 brand new send address rather than all of them. But totally acknowledge there's risk here, and an annoyingly hard one to anticipate ahead of time.23:30:44
@dgrig:erethon.comdgrig

I don't have an exact timeline, but I think it would be around sometime next week.

If improvmx can send emails then it's good enough for this usecase now I think and there's no need to worry about potential issues with the new setup.

23:37:21
@dgrig:erethon.comdgrigHaving said that, I'm happy to help with setting up alerting/monitoring for the new server, so let me know if you want to pair on this or if I should draft a PR if you think it's helpful!23:38:21
@jfly:matrix.orgJeremy Fleischman (jfly)Great, that's definitely the safest option, then.23:41:13
@jfly:matrix.orgJeremy Fleischman (jfly) Hopefully @fricklerhandwerk:matrix.org has a login account and can help you out? (I don't) 23:41:21
@winter:catgirl.cloudWinteri’ve been given the relevant info and was going to get it set up later today :)23:41:50
29 Jan 2025
@hexa:lossy.networkhexaupgrading all macs to 15.301:21:17
@hexa:lossy.networkhexaall done01:44:13
@vcunat:matrix.orgVladimír ČunátIt's annoying me quite a bit: https://github.com/NixOS/nixpkgs/issues/37479205:59:37
@joerg:thalheim.ioMic92 hexa (signing key rotation when): Maybe I can deploy the staging hydra and this buildbot master/worker into one hetzner machine and use the ofborg builder as remote builder. 15:01:28
@hexa:lossy.networkhexahuh15:02:05
@joerg:thalheim.ioMic92hetzner cloud15:02:06
@hexa:lossy.networkhexaofborg builder?15:02:12
@hexa:lossy.networkhexajust reuse the nix-community buildbot, I don't mind15:02:37
@hexa:lossy.networkhexaas you said, we don't reuse the results15:02:48
@hexa:lossy.networkhexavault.nixos.org updated to include the latest security updates15:07:14
@joerg:thalheim.ioMic92Ok. Will have a chat with zowoq. I might need to add one little feature into buildbot to allow to whitelist orgs.15:03:44
30 Jan 2025
@sarcasticadmin:matrix.orgsarcasticadmin changed their display name from sarcasticadmin to Rob - KM6LBU.03:01:46
@sarcasticadmin:matrix.orgsarcasticadmin changed their display name from Rob - KM6LBU to sarcasticadmin.03:02:59
@ofalvai:matrix.orgofalvai joined the room.19:48:37
31 Jan 2025
@sinan:sinanmohd.comsinan changed their display name from sinan to Sinan (comfy).02:54:41

Show newer messages


Back to Room ListRoom Version: 6