feat(firecracker): run the orchestrator control plane as a VM (Stage B, 1/n)
lint / lint (push) Successful in 2m18s
test / unit (pull_request) Successful in 1m23s
test / integration (pull_request) Successful in 29s
test / coverage (pull_request) Successful in 1m17s

First slice of Stage B: the orchestrator control plane runs as a
persistent Firecracker infra VM instead of a Docker container. The host
CLI reaches it over HTTP at the orchestrator link's guest IP; agent VMs
will reach its gateway ports (added next) over VM-to-VM routing.

- Dockerfile.orchestrator bakes the stdlib-only control-plane source
  (COPY bot_bottle) so the image is self-contained and runs from a built
  image with no runtime bind-mount — a guest VM can't bind-mount host
  source. (Build-from-source stays the default; a pull-from-registry mode
  lands later. The docker backend's dev bind-mount still overlays this.)
- util.build_base_rootfs_dir / inject_guest_boot take a `variant` +
  `init_script`, so the same orchestrator image is prepared two ways
  without a cache collision: the builder VM keeps the SSH-only agent init;
  the infra VM gets a control-plane PID-1 init.
- new firecracker/infra_vm.py: boot the infra VM on the orchestrator link,
  run `python -m bot_bottle.orchestrator` as PID 1, and poll /health.

Verified on a KVM host: infra VM boots, control plane answers
`GET /health -> 200 {"status":"ok"}` from the host over the TAP link.
Next: fold gateway_init (egress/git-gate/supervise) into the same VM,
then agent->gateway routing.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WBMWTEtQdJ4W5UrWuLHCck
This commit is contained in:
2026-07-16 12:34:51 -04:00
parent 73ee081c65
commit ebaa999c21
4 changed files with 231 additions and 8 deletions
+8
View File
@@ -49,6 +49,14 @@ ENV STORAGE_DRIVER=vfs \
# No third-party *Python* deps — the control plane stays stdlib only.
WORKDIR /app
# Bake the (stdlib-only) control-plane source so the image is
# self-contained — it runs from a built image, no runtime bind-mount.
# This is what the Firecracker infra VM boots (a guest can't bind-mount
# host source); the docker backend may still bind-mount /app for dev
# live-reload, which simply overlays this baked copy. `.dockerignore`
# keeps .git/docs/*.md out of the context.
COPY bot_bottle /app/bot_bottle
# Documentation only; lifecycle.py overrides the entrypoint to
# `python3 -m bot_bottle.orchestrator` with the runtime flags.
ENTRYPOINT ["python3", "-m", "bot_bottle.orchestrator"]