• v0.2.2 3880311e36

    v0.2.2
    ci / derle (push) Successful in 22s
    Stable

    ilker released this 2026-11-16 20:22:43 +01:00 | 1 commits to main since this release

    v0.2.2 - clusters across the nodes of a Proxmox cluster

    A Proxmox VE that is one node of a Proxmox cluster no longer means one
    node. Setup lists the cluster's nodes and asks which ones clusters may use
    (PVE_NODES); the rest are never touched. Compute nodes are spread over
    the chosen nodes. Heads stay on PVE_NODE, where the template is, so no
    shared storage is needed. With more than one node the SDN zone becomes
    vxlan, with every node a peer and an MTU of 1450 that guests are given
    through virtio; setup remakes a simple zone only while no cluster uses
    it, and hpcod verify checks the nodes and the zone. Before this, discovery
    already saw every node and placement could pick any of them, while the
    template, the snippets and a simple zone only worked on one: a cluster
    could land where it could not be built.

    Run on the simulated Proxmox with the zone forced to vxlan: a two-node
    test cluster built and ran a job, both compute NICs came up at 1450, and a
    full 1450-byte frame passed between them while 1451 did not. Traffic
    between two real Proxmox nodes has not been tested; the lab has one.

    Also

    • Setup's step list keeps to its columns on narrow terminals, and the
      check says "1 warning", not "1 warnings".
    • The documented install works on a fresh host: it now downloads the
      release, checks SHA256SUMS, sets the execute bit and runs
      sudo ./hpcod setup. Before, it said sudo hpcod setup, which is not
      found until setup has installed itself.
    • The documentation was brought in line with what is built: section 02
      installs hpcod from scratch, and the hand-built lab moved to section 10.
    Downloads
  • v0.2.1 355c6d4c59

    v0.2.1 Stable

    ilker released this 2026-11-16 18:35:37 +01:00 | 8 commits to main since this release

    v0.2.1 - v0.2.0 rebuilt with Go 1.27.4

    GO-2026-6859: a race in net/http's MaxBytesReader can crash an HTTP/1
    server, and the portal is one. The v0.2.0 binaries were built with Go
    1.27.3; these are built with 1.27.4. x/crypto moves to v0.59.0 (GO-2026-5932,
    not called by hpcod). Nothing else changes. See CHANGELOG.md.

    Downloads
  • v0.2.0 8556a50e94

    v0.2.0
    ci / derle (push) Failing after 34s
    Stable

    ilker released this 2026-11-16 18:25:07 +01:00 | 11 commits to main since this release

    v0.2.0 - one binary installs the control plane

    hpcod now installs itself. Copy the binary to a Debian 13 or Ubuntu 24.04
    host and run sudo hpcod setup: a full-screen installer that signs in to
    Proxmox before asking anything else, offers its nodes and datastores, runs
    every step with its output live, checks the result and offers a test
    cluster. The roles, the Terraform module, the schema and the application
    catalogue are inside the binary.

    • hpcod verify: each fact checked by using it.
    • hpcod selftest: the smallest real cluster, a job run on it, taken down.
    • Closed networks: its own name-constrained CA and its own DNS.
    • A simulated Proxmox in QEMU on the same host, to try it without one.

    Proven end to end on a simulated Proxmox (Proxmox VE 9): install, Proxmox
    preparation by root's password, head template, verify READY, and a test
    cluster that ran srun on its compute node. Not yet run: setup against a
    bare-metal Proxmox, and the token path against a real API.

    See CHANGELOG.md and hpcod/DEPLOY.md.

    Downloads