• v0.2.0 a43ca82785

    v0.2.0
    CI / agent (push) Successful in 3s
    CI / site (push) Successful in 2s
    CI / go (push) Successful in 36s
    release / release (push) Successful in 30s
    Stable

    gitea-actions released this 2026-10-28 20:02:57 +01:00 | 63 commits to main since this release

    Note (2026-10-30): the commissioning image (commissioning-*) was removed from this release: it let three lab SSH keys log in as root on commissioning machines. Build one with bootstrap.sh --build-image, or use the image of v0.3.0 or later.

    Second release: install from scratch, network model and region/rack split, external IPAM
    (NetBox), a certificate authority with delegation, many power drivers, IPv6, and a web UI and
    console for fleets.

    Added

    • Machine tags (MAAS-style): manual tags per machine, auto tags from match rules over the
      inventory ({{ gt .Node.GPUs 0 }}), re-evaluated at commissioning and when a tag changes.
    • Tags carry a cloud-init fragment merged into deployment user-data (deploy/tags/gpu-nvidia.yaml
      installs the NVIDIA driver on GPU nodes) and extra overlays for stateless nodes.
    • rollcall tag, rollcall tags, rollcall list -tag, deploy tag:NAME / power tag:NAME
      fan-out; tags column, editor and definitions panel in the web UI; ?tag= filter on the API.
    • Web UI redesigned for fleets: sidebar navigation (Overview, Machines, Jobs, Tags, Profiles,
      OS images), state/tag filter chips, search, sorting and paging, multi-select with bulk
      power/deploy/assign/tag/re-commission/release, machine detail with tabs, dialog-driven
      actions, fleet-wide /api/v1/events and /api/v1/jobs, ?token= sign-in for bookmarks.
    • Physical location per machine (building, room, rack, unit, asset tag): rollcall location,
      CSV import matched by id/serial/MAC/node name with dry run, rack definitions with height,
      list -rack/-room/-building, location column and chips in the UI, Racks page with
      elevation views, bulk "Set location…", .Node.Rack etc. in templates and tag rules.
    • Terminal console: a bare rollcall in a terminal opens a full-screen UI in the llmgw style
      (Bubble Tea): overview, machines with filter/selection/bulk actions, machine detail, racks
      with elevation, jobs, events, tags, profiles, OS images; connect screen that saves
      ~/.config/rollcall/client.json, which the CLI also reads; rollcall tui -dump renders one
      screen. First Go tests (console rendering and keys).
    • Network model after MAAS: fabrics, VLANs, subnets, IP ranges (dynamic/reserved/static) and
      IPAM; addresses already in use are adopted. rollcall fabric|vlan|subnet|range|ip.
    • Interface layouts (physical, bond, VLAN; NICs by selector) per machine or per tag; deployment
      writes cloud-init network-config and udev name rules into the image; release frees addresses.
      rollcall layout, rollcall net show|set.
    • Region/rack split: rollcall rack (dnsmasq state, per-MAC PXE files, BMC commands, image cache,
      node API proxy) long-polls the region; the region runs an embedded rack controller.
      deploy/install-rack.sh, rollcall controllers, rollcall dhcp.
    • dnsmasq configuration generated from the model, restarted only when it changes and rolled back
      if dnsmasq does not come back.
    • Web UI: Network page (rack controllers, subnets with ranges and usage, layouts), network tab per
      machine, layout action; console: Network page, network section, layout action.
    • Certificate authority on the region (llmgw-style): HTTPS listener with an auto-renewed region
      certificate, admin_http policy, /ca.pem; rack controllers enroll with one-time join codes
      (rollcall controller join-code, rollcall rack join) and use mutual TLS, renewing their
      certificate themselves; removal revokes; deployed machines and overlays trust the CA;
      rollcall ca show|issue; the console trusts a CA on first connect after showing its fingerprint.
    • Power drivers: ipmi, redfish, idrac, ilo, supermicro, xcc, openbmc, proxmox, manual, run on the
      rack controller; Redfish auto-detection after commissioning; rollcall bmc, BMC editing in the
      web UI and console. Lab Redfish emulator with iDRAC/iLO/generic profiles.
    • IPv6: subnets, IPAM, dual-stack default layout, per-family default routes, dnsmasq RA/DHCPv6,
      AAAA host records, IPv6 listen addresses and URLs, IPv6 in the commissioning inventory.
    • External IPAM authority (NetBox driver): allocation registers each address in NetBox first and
      skips addresses others hold there; ownership by tag + rollcall_machine custom field; releases
      and a periodic reconcile create, fix and delete only Rollcall-owned records; dns_name per address
      for DNS sync; delegated prefixes (rollcall ipam prefixes|import); rollcall ipam [sync -dry],
      /api/v1/ipam.
    • Web UI: network topology drawing (region, external IPAM, rack controllers, one bus per VLAN with
      its subnets, machines wired to every VLAN they have an address on; large groups collapse) on the
      Network page and, compact, on the Overview. Overview redesigned: fleet state bar, per-rack counts,
      attention list incl. IPAM sync, capacity and free pool, OS, hardware, BMC drivers, locations, tags,
      recent deployments.
    • CA delegation: new roots allow one level of intermediates; rollcall ca intermediate NAME -permit DOMAIN,CIDR [-csr FILE] signs a name-constrained intermediate (for an ACME server such as Caddy's
      acme_server); rollcall ca rotate -yes replaces a root that cannot delegate; tag fragment
      deploy/tags/acme-cert.yaml fetches and renews a node certificate with certbot.
    • Rack controllers update themselves to the region's version: checksum- and version-checked
      download over mutual TLS, installed by a root path unit with automatic rollback;
      rack_binaries for other architectures, auto_update to opt out; versions in
      rollcall controllers and the web UI.
    • Addresses on secondary subnets with a gateway get their own routing table and a source rule in
      network-config, so replies from a storage or tenant VLAN leave through that VLAN's gateway.
    • With admin_http other than allow, browsers that open the web UI over HTTP are redirected to
      HTTPS (nodes keep HTTP for images and the agent).
    • Admin client certificates: rollcall admin-cert request NAME (key stays on the client, CSR only),
      list, revoke; the region accepts them as admin over HTTPS; CLI/console use them from
      client.json, the web UI works without a token when the browser presents one (.p12 written).
    • deploy/bootstrap.sh: a region on a fresh Debian 13 host. Day 0 needs nothing about the network:
      packages, PostgreSQL, TFTP tree, config, services and a verified commissioning image, the region
      reachable on its management address with no DHCP or subnets. Run again with --iface once the
      provisioning network is known: server address updated, subnet with ranges, DHCP, optional NAT.
    • rollcall net discover: per interface link, speed, addresses and implied subnets, switch/port/VLAN
      from LLDP, DHCP servers that answer, neighbours, and what to do with it.
    • commission_append follows server_url when left empty.
    • rollcall doctor: checks configuration, database, listeners, certificates, TFTP files, image
      checksums, dnsmasq, DNS as machines see it, clock, foreign DHCP servers on the provisioning
      network (DHCPDISCOVER probe), rack controllers, OS images and IPAM, with what to do.
    • rollcall version; CD-built binary carries git describe.
    • Release notes from CHANGELOG.md.

    Fixed

    • RHEL-family deployments (Rocky, Alma, CentOS) did not trust the Rollcall CA: cloud-init's
      ca_certs ran update-ca-certificates there and failed. The CA now goes into the image's trust
      anchors and a bootcmd rebuilds the store with the distribution's tool.
    • A deploy whose power command was lost (rack or region restarting) stayed pending forever and the
      event looked like a success: power errors are now part of the event (pxe boot failed), and a
      job the machine has not started within job_start_timeout (default 30m, room for servers that
      take 4-5 minutes to POST) fails with a hint.
    • CentOS Stream 9 image URL (the 502 was a missing file name).
    • Rack controllers' dnsmasq had no upstream DNS on Debian (it looks for a resolvconf file that is
      usually missing) and refused every name outside the cluster domain; the generated configuration
      now forwards to systemd-resolved's stub (keeping split DNS) or the host's resolv.conf servers.
    • Virtual BMC addresses are configured in netplan on the lab PXE server (they were lost on a
      network reconfigure, which made every BMC call fail).
    • Commissioning console no longer shows a failing autologin (noautologin).

    Commits: v0.1.0...v0.2.0

    • Release 0.2.0
    • cloud-init final_message: no $hostname (not expanded there; warned on every deploy)
    • Deployments trust the CA on RHEL-family systems too
    • Lost power commands are visible; jobs not started in job_start_timeout fail
    • os-sources: correct CentOS Stream 9 image name (the 502 was a missing file)
    • Install guide, release bundles, publishable commissioning image
    • Day-0 install without a network plan; rollcall net discover
    • From-scratch install: deploy/bootstrap.sh and rollcall doctor
    • admin-cert request: refresh the stored CA for the same region (it may have been rotated)
    • Admin client certificates as an alternative to the admin token
    • Web UI over plain HTTP redirects to HTTPS when admin_http forbids HTTP
    • network-config: policy routing for addresses on secondary subnets with a gateway
    • Rack controllers update themselves to the region's version
    • dnsmasq: forward outside names (systemd-resolved stub or resolv.conf)
    • CA delegation: name-constrained intermediates, root rotation, ACME node certificates
    • Web UI: network topology drawing; richer Overview
    • ipam: a subnet domain names records only inside the authority's zone
    • External IPAM authority: NetBox driver, ownership, reconcile
    • Region as certificate authority, BMC power drivers, IPv6
    • Network model, IPAM, interface layouts and the region/rack split (MAAS-style)
    • Terminal console: bare rollcall in a terminal opens a full-screen UI (llmgw style)
    • ui: machines table scrolls horizontally on narrow screens; shorter model/serial cells
    • ui: fix undefined location filter variable on the Machines page
    • Physical location: building / room / rack / unit / asset tag
    • Web UI redesigned for datacenter fleets
    • Machine tags (MAAS-style), changelog-driven release notes
    • deploy workflow: version stamp from git describe
    Downloads