| 11 Oct 2024 |
 emily | In reply to @vcunat:matrix.org
No need to wipe the old machine too soon. And it seems unlikely that we'd want to revert completely. I think we should do whatever you think is best for Hydra out of trying an existing AArch64 machine and getting an EPYC to try. | 06:40:24 |
| emily | (without consideration of the costs, since they seem trivial compared to the potential benefit) | 06:40:42 |
 vcunat | Keeping it at x86 seems better in our current situation (less risks/complications). | 06:53:55 |
| vcunat | We might consider splitting it up. At least the queue-runner away from the public web (hydra.nixos.org). I don't feel too comfortable having the signing keys on same machine as a public web. I think these only communicate through the DB which is on a separate machine already. | 06:55:56 |
 fricklerhandwerk | In reply to @joerg:thalheim.io
@fricklerhandwerk:matrix.org: where is this security tracker deployed just now? I think it would help if Erethon would have a chat with us, so we can make sure it get integrated with the rest of the infra to some extent. http://sectracker.nixpkgs.lahfa.xyz/
Config here: https://github.com/Nix-Security-WG/nix-security-tracker/tree/main/staging
| 07:28:08 |
 Gaétan Lepage | Redacted or Malformed Event | 07:30:30 |
| fricklerhandwerk | In reply to @emilazy:matrix.org
I didn't get the impression that the infra team has a budget at all The infra team can get expenses reimbursed out of the foundation's regular budget. The problem is that in the past there was no process to do anything else. tomberek and I have been pushing to have discretionary budgets for teams, but there needs to be someone on the other end to make those decisions. | 07:30:34 |
| emily | gotcha | 07:33:51 |
| emily | In reply to @vcunat:matrix.org
We might consider splitting it up. At least the queue-runner away from the public web (hydra.nixos.org). I don't feel too comfortable having the signing keys on same machine as a public web. I think these only communicate through the DB which is on a separate machine already. maybe the website could continue being on the x86 server? | 07:34:24 |
| emily | or, right, the idea was to upgrade the x86 | 07:34:39 |
| emily | then maybe the site could move to one of the AArch64 boxes? :) | 07:34:48 |
| emily | btw, maybe should upgrade Hydra's Nix to 2.24 if it's moving to a new server anyway. since Hydra supports it now and it would solve that Nix bug that didn't get a fix backported because of only 2.18 and 2.24 being supported versions. | 07:51:44 |
 Mic92 | In reply to @emilazy:matrix.org
btw, maybe should upgrade Hydra's Nix to 2.24 if it's moving to a new server anyway. since Hydra supports it now and it would solve that Nix bug that didn't get a fix backported because of only 2.18 and 2.24 being supported versions. Yes. that was the plan. We recently fixed 2.24 support in hydra. | 07:59:38 |
| Mic92 | In reply to @fricklerhandwerk:matrix.org
http://sectracker.nixpkgs.lahfa.xyz/
Config here: https://github.com/Nix-Security-WG/nix-security-tracker/tree/main/staging
ok. Seems to be down just now. | 07:59:56 |
| emily | (btw I never realized that the cache signing key is on the machine that hosts the hydra.nixos.org site) | 08:00:49 |
| emily | (that terrifies me) | 08:00:52 |
| emily | (strong support for any plan that fixes that) | 08:01:35 |
| fricklerhandwerk | In reply to @joerg:thalheim.io
ok. Seems to be down just now. Yeah we're debugging it, there's some weird Django issues where some stupid script hangs itself to death | 08:04:49 |
 dgrig | In reply to @joerg:thalheim.io
@fricklerhandwerk:matrix.org: where is this security tracker deployed just now? I think it would help if Erethon would have a chat with us, so we can make sure it get integrated with the rest of the infra to some extent. I'm catching up with the channel now, for some reason Element didn't ping me about this mention (maybe because it was capitalized). Just want to point out that what fricklerhandwerk linked too is also Raito's work, don't want to take credit for it. At this point I'm not sure what's the best way to move forward, since it seems that Raito has already done a lot of the work needed to deploy this properly? | 08:05:26 |
| fricklerhandwerk | Mic92: back online | 08:06:32 |
| Mic92 | What is your expected update cadence? | 08:06:41 |
| Mic92 | dgrig: what is blocking you specifically? | 08:07:55 |
| dgrig | In reply to @joerg:thalheim.io
dgrig: what is blocking you specifically? I don't have a "blocker" per se from the nixos infra team. I've been experimenting locally with the security tracker and some other software that fricklerhandwerk wants deployed in an official namespace and manner. On the security tracker front I have some thing to figure out still, but for others (say Odoo if it's ok for us in the end) I want to sync with someone at some point on how we best want it deployed (i.e. does it belong on the non-critical infra, how do we want to backup the database, etc). | 08:21:11 |
| Mic92 | Sure. Do Thursday, 18:00 CEST the next week work for you? | 08:23:58 |
| Mic92 | * Sure. Does Thursday, 18:00 CEST the next week work for you? | 08:24:09 |
| dgrig | In reply to @joerg:thalheim.io
Sure. Does Thursday, 18:00 CEST the next week work for you? Yes, I've blocked all the nixos infra meetings in my calendar so I can attend them. | 08:24:39 |
| fricklerhandwerk | In reply to @joerg:thalheim.io
What is your expected update cadence? Hm, good question. That will depend on whether we get follow-up funding and how much, but say something between 1 week and 1 month | 08:25:23 |
| fricklerhandwerk | In reply to @fricklerhandwerk:matrix.org
Hm, good question. That will depend on whether we get follow-up funding and how much, but say something between 1 week and 1 month There is already automation in place to do continuous deployment to staging, and we'll re-use that for production. | 08:26:14 |
| Mic92 | What is s3 used for? | 08:29:56 |
| Mic92 | Just seems to be backup as far as I can see | 08:30:55 |
