!zghijEASpYQWYFzriI:nixos.org

Hydra

343 Members
99 Servers

Load older messages


SenderMessageTime
25 Mar 2024
@k900:0upti.meK900
In reply to @darkwater4213:matrix.org
For RISC-V? Does the main instance of Hydra compile for RISC-V?
It doesn't really matter for what, it just does normal Nix remote builds
05:11:45
@k900:0upti.meK900 hydra.n.o doesn't build RISCV because we don't have the hardware for it 05:12:01
@rick:matrix.ciphernetics.nl@rick:matrix.ciphernetics.nl
In reply to @darkwater4213:matrix.org
How feasible is self-hosting a Hydra instance? Say I want to deploy to a whole bunch of RISC-V thin clients... I already know what packages I want to be compiled, so is there a way to configure Hydra to only build and serve those? Or am I fundamentally messengering something about Hydra?
With nixpkgs or the flake it's easy to host, providing you're running nixos or don't mind running a VM with nixos. There's definitely a way to configure hydra to build a specific set of packages, that's what it's built to do. I wouldn't really say it's overkill, it's a convenient way to keep up to date with nixpkgs and building what you need from it for what platform you want
08:37:03
27 Mar 2024
@admin:nixos.org@admin:nixos.org joined the room.13:25:28
Room Avatar Renderer.13:25:56
@admin:nixos.org@admin:nixos.org left the room.13:26:01
30 Mar 2024
@magic_rb:matrix.redalder.orgmagic_rb

i seem to be having issues with hydra not serving static files

4#124: *13849359 upstream timed out (110: Connection timed out) while reading response header from upstream, client: , server: hydra.redalder.org, request: "GET /static/js/jquery/jquery-ui-1.10.4.min.js HTTP/2.0", upstream: "http://127.0.0.1:8666/static/js/jquery/jquery-ui-1.10.4.min.js", host: "hydra.redalder.org", referrer: "https://hydra.redalder.org/project/dotfiles"
2024/03/30 21:26:30 [error] 124#124: *13849359 upstream timed out (110: Connection timed out) while reading response header from upstream, client:, server: hydra.redalder.org, request: "GET /static/js/moment/moment-2.24.0.min.js HTTP/2.0", upstream: "http://127.0.0.1:8666/static/js/moment/moment-2.24.0.min.js", host: "hydra.redalder.org", referrer: "https://hydra.redalder.org/project/dotfiles"
2024/03/30 21:26:30 [error] 124#124: *13849359 upstream timed out (110: Connection timed out) while reading response header from upstream, client: , server: hydra.redalder.org, request: "GET /static/fontawesome/css/all.css HTTP/2.0", upstream: "http://127.0.0.1:8666/static/fontawesome/css/all.css", host: "hydra.redalder.org", referrer: "https://hydra.redalder.org/project/dotfiles"
2024/03/30 21:26:30 [error] 124#124: *13849359 upstream timed out (110: Connection timed out) while reading response header from upstream, client: , server: hydra.redalder.org, request: "GET /static/js/popper.min.js HTTP/2.0", upstream: "http://127.0.0.1:8666/static/js/popper.min.js", host: "hydra.redalder.org", referrer: "https://hydra.redalder.org/project/dotfiles"
2024/03/30 21:26:30 [error] 124#124: *13849359 upstream timed out (110: Connection timed out) while reading response header from upstream, client: , server: hydra.redalder.org, request: "GET /static/css/tree.css HTTP/2.0", upstream: "http://127.0.0.1:8666/static/css/tree.css", host: "hydra.redalder.org", referrer: "https://hydra.redalder.org/project/dotfiles"
2024/03/30 21:26:30 [error] 124#124: *13849359 upstream timed out (110: Connection timed out) while reading response header from upstream, client: , server: hydra.redalder.org, request: "GET /static/images/emojione-check-2714.svg HTTP/2.0", upstream: "http://127.0.0.1:8666/static/images/emojione-check-2714.svg", host: "hydra.redalder.org", referrer: "https://hydra.redalder.org/project/dotfiles"
2024/03/30 21:26:33 [warn] 125

this is from a nginx remote proxy, in the browser the page just times out

20:30:19
@magic_rb:matrix.redalder.orgmagic_rbhydra itself doesnt log anything, im also not running this on nixos, but the module was copied from nixos mostly20:32:00
@magic_rb:matrix.redalder.orgmagic_rbi dont see why it would be failing the serve21:11:17
@magic_rb:matrix.redalder.orgmagic_rbinterestingly reloading the page doesnt mark them ass missing? hydra isnt closing connections properly?21:22:57
@magic_rb:matrix.redalder.orgmagic_rb * interestingly reloading the page doesnt mark them as missing? hydra isnt closing connections properly?21:23:44
@magic_rb:matrix.redalder.orgmagic_rbi also got to do something to speed up the DB because clicking on one of my systems takes 20 seconds to load, its 6.5k store paths21:26:28
@magic_rb:matrix.redalder.orgmagic_rb * i also got to do something to speed up the DB because clicking on one of my systems takes 20 seconds to load, its 6.5k build steps21:27:24
31 Mar 2024
@fack:cyberia.club@fack:cyberia.club left the room.00:05:01
2 Apr 2024
@lotte:chir.rs@lotte:chir.rs changed their profile picture.06:58:30
@lotte:chir.rs@lotte:chir.rs changed their profile picture.07:36:25
3 Apr 2024
@rick:matrix.ciphernetics.nl@rick:matrix.ciphernetics.nlManaged to fix a ca-derivations issue with hydra: https://github.com/NixOS/hydra/pull/137421:08:45
4 Apr 2024
@stablejoy:matrix.org@stablejoy:matrix.org joined the room.06:09:42
@fabaff:matrix.orgfabaff changed their display name from Fabian Affolter to fabaff.08:40:33
@darkwater4213:matrix.orgdarkwater4213

How feasible would it be to run Hydra as a distributed system? Say I had a few dozen or maybe even a hundred or more thin clients (ARM or RISC-V or whatever). Is it theoretically possible for Hydra to be distributed among those clients (assuming they're all on the same overarching network, of course) so none of them is doing much work or for long, but the whole thing is entirely bootstrapped (reminiscent of IPFS)?

And because this is distributed across an entire fleet, you can do some crazy Gentoo-level optimization... the prospect is very exciting indeed.

08:56:09
@darkwater4213:matrix.orgdarkwater4213Imagine: serverless fleet management. MDM... without a manager.08:56:34
@k900:0upti.meK900What do you even mean by "distributed system"?08:56:41
@k900:0upti.meK900Hydra is not a generic orchestrator like k8s08:56:49
@k900:0upti.meK900It builds stuff08:56:51
@k900:0upti.meK900If you don't need to build stuff, or need more than to build stuff, Hydra will not solve your problem08:57:03
@darkwater4213:matrix.orgdarkwater4213Distributed computation has been around since the 90's (at least). I'm asking how feasible it would be to distribute the computation necessary for Hydra. My theorycrafting brain says that the compilation would be the easy part, the orchestration and delivery would be more difficult. Delivery (that is, finding what unit in the fleet has a given resource and then pushing it out to all the units) seems like it'd be a good job for IPFS, but orchestration seems more difficult. Any ideas?08:59:39
@k900:0upti.meK900You are saying long words that don't mean things09:00:06
@k900:0upti.meK900What "computation necessary"?09:00:11
@k900:0upti.meK900 What do you actually want to do? 09:00:15
@darkwater4213:matrix.orgdarkwater4213
In reply to @k900:0upti.me
Hydra is not a generic orchestrator like k8s
I think you misunderstand. I'm not trying to treat Hydra as an orchestration tool. I'm asking how feasible it would be to orchestrate a large fleet of relatively low-resource clients (think along the lines of a generic tablet) to effectively function as a single Hydra instance or, barring that, multiple Hydra instances orchestrated by some distributed system I haven't come up with yet.
09:01:40

Show newer messages


Back to Room ListRoom Version: 6