grenadeandClaude Fable 5.1
b9e1d21ec9
quantus/miner#8. The miner is now deployed from this repo, not from lair/quantus's release-pinned workflow (lair/quantus#4 retires that half). - .gitea/workflows/deploy.yaml: build on cuda-13.0 (Fedora 43 like the hosts, and the runner with nvcc for #3) with the commit embedded, then per host in the matrix: sudoers preflight against deploy/infra-setup.sh, credentials copied from the node, miner.env rendered with the node's mesh IP resolved on the miner host, checksum-gated push of binary and unit, scoped firewalld rule for the exporter, restart only on change. Validate asserts the unit is active, --version carries this commit, the miner sees the matrix's device count, and miner_hashes_total advances within 120 s. If validate fails after a restart, the previous binary is restored. - deploy/: the unit, sysusers, firewalld service and env template moved verbatim from lair/quantus asset/, plus infra-setup.sh with the miner role (and two new cp grants for the rollback). Applied to benjy and quadbrat. - Matrix: benjy and quadbrat; beast present but commented out per the operating policy in #1. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CBgs2nSi4H2mdh8kD8vMX5
10 lines
432 B
XML
10 lines
432 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<service>
|
|
<short>quantus-miner-metrics</short>
|
|
<description>Quantus miner Prometheus exporter. The miner binds this on
|
|
0.0.0.0 unconditionally (crates/metrics: SocketAddr from [0,0,0,0]) — there is
|
|
no loopback option — so the firewalld rich rule scoped to the scrape host is
|
|
the only thing bounding who can reach it.</description>
|
|
<port protocol="tcp" port="9900"/>
|
|
</service>
|