Skip to content

backlog(B-0770): GL.iNet Comet Pro IP-KVM integration — remote BIOS-to-cluster-member; zero-physical-access bring-up + repair#5056

Closed
AceHack wants to merge 1 commit into
mainfrom
otto-cli/b0770-comet-pro-ip-kvm-remote-bios-cluster-bringup-2026-05-25
Closed

backlog(B-0770): GL.iNet Comet Pro IP-KVM integration — remote BIOS-to-cluster-member; zero-physical-access bring-up + repair#5056
AceHack wants to merge 1 commit into
mainfrom
otto-cli/b0770-comet-pro-ip-kvm-remote-bios-cluster-bringup-2026-05-25

Conversation

@AceHack

@AceHack AceHack commented May 26, 2026

Copy link
Copy Markdown
Member

Aaron 2026-05-25 adding PC 2 with GL.iNet Comet Pro IP-KVM. YES — complete remote setup including BIOS is possible: HDMI capture (see) + USB HID injection (type) + USB mass-storage emulation (present ISO as virtual USB; no physical stick needed) + ATX power control + REST/WebRTC API.

Composes with B-0754 (zero-typing first-boot runs in virtual-USB-mounted ISO) + B-0760 (USB-as-repair-tool fully remote) + B-0757 (mDNS auto-discovery) + B-0743 (consent floor at Comet-Pro plug-in) + B-0765 (ServiceTitan route — Comet Pro IS the existing IP-KVM standard).

Extends Zeta from home-lab to distributed/colo/edge/unattended deployments.

…o-cluster-member; zero-physical-access cluster bring-up + repair

Aaron 2026-05-25 mid-iter-2-test-prep: PC 2 is being added with
GL.iNet Comet Pro for remote BIOS-to-cluster-member setup. 'see
if you can do complete remote setup even bios stuff.'

Yes — Comet Pro provides everything needed: HDMI capture (see
BIOS), USB HID injection (type into BIOS), USB mass-storage
emulation (present ISO as virtual USB; no physical USB needed
on PC 2), ATX power control, web UI + REST + WebRTC API.

Composes with cluster-install substrate: B-0754 zero-typing
first-boot runs unchanged inside virtual-USB-mounted ISO; B-0760
USB-as-repair-tool fully composed with remote delivery; B-0757
mDNS auto-discovery extends to Comet Pros; B-0743 'I execute,
you fingerprint' consent floor moves to Comet-Pro-plug-in event
(operator's once-per-node physical-presence) with subsequent ops
agent-driven under that consent.

Per ServiceTitan route (B-0765): Comet Pro is the existing IP-KVM
standards interface Zeta plugs into. Per B-0763 vendor-swap:
alternative IP-KVM devices (BliKVM, PiKVM, JetKVM, NanoKVM,
Tinypilot) fit the same Zeta wrapper shape.

Extends Zeta's deployment reach from 'home-lab where Aaron walks
to each node' to 'distributed infrastructure where Aaron's
physical presence is the exception.' Same substrate; vastly
larger deployment surface (colo / edge / remote / unattended).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings May 26, 2026 00:47
@AceHack AceHack enabled auto-merge (squash) May 26, 2026 00:47

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new P2 backlog row (B-0770) describing planned GL.iNet Comet Pro IP-KVM integration to enable fully remote BIOS-to-cluster-member bring-up and repair workflows, and updates the generated backlog index to include the new row.

Changes:

  • Added B-0770 per-row backlog document capturing problem/target/acceptance for Comet Pro-based remote bring-up + repair.
  • Updated docs/BACKLOG.md to include B-0770 in the P2 list.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File Description
docs/backlog/P2/B-0770-gl-inet-comet-pro-ip-kvm-integration-remote-bios-to-cluster-member-zero-physical-access-aaron-2026-05-25.md New backlog row detailing Comet Pro integration requirements, acceptance criteria, and composition with other cluster substrate items.
docs/BACKLOG.md Adds B-0770 to the P2 index list.

Comment on lines +10 to +14
depends_on:
- B-0754
- B-0760
composes_with:
- B-0743
expected-BIOS-state per node (boot order = USB-virtual then
NVMe; UEFI secure boot off for installer iteration; etc.)
— agent reconciles BIOS state at install time (composes
with B-0747 git-native per-machine state)
Comment on lines +151 to +153
JetKVM). Aaron picked Comet Pro; the wrapper is shaped per
B-0763 so alternative IP-KVM vendors plug in behind the same
operator-facing interface.
|---|---|---|
| Motherboard | TBD (Aaron to confirm) | BIOS vendor + BIOS-entry-key + UEFI secure boot policy |
| BIOS / UEFI | TBD | AMI / Phoenix / Insyde / Award |
| NVMe / SATA / HDD layout | TBD | per B-0754 greedy N-disk + B-0758 USB-persistent-OS triage |
@AceHack

AceHack commented May 26, 2026

Copy link
Copy Markdown
Member Author

Closing as substrate-recoverable per pr-triage-tiers.md Tier-3. Re-landed via #5092 (byte-identical B-0770 + regenerated index + pre-emptive MD032 fix). Cascade audit at tick 0410Z.

@AceHack AceHack closed this May 26, 2026
auto-merge was automatically disabled May 26, 2026 04:54

Pull request was closed

AceHack added a commit that referenced this pull request May 26, 2026
…e BIOS-to-cluster-member; zero-physical-access bring-up + repair (#5092)

Re-land of stale-DIRTY PR #5056 (Tier-3 per pr-triage-tiers).
Same B-0770 row from PR #5056 head 5ba1b02; BACKLOG.md regenerated;
pre-emptive MD032 fix (numbered list needs blank line above it).

Co-authored-by: Lior <lior@zeta.dev>
Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants