Files
oikos/.agents/skills/lifecycle-provision-node/SKILL.md
dtoro ebe1b95acf
Some checks failed
ci / build-test (push) Has been cancelled
ci / docker-build (push) Has been cancelled
ci / web (push) Has been cancelled
Desktop App / Build Linux (amd64) (push) Has been cancelled
Desktop App / Attach to Release (push) Has been cancelled
sync AGENTS.md tool list with MCP server (63 tools); fix 7 stale references in .agents/
2026-08-09 00:04:58 +02:00

1.6 KiB

name, risk_class, inputs, verification, docs_update_checklist, transition
name risk_class inputs verification docs_update_checklist transition
lifecycle-provision-node config_mutation
node_name
kind
storage_pool
grep 'state: provisioning' inventory.yaml
doc_page_stub
planned -> provisioning

Lifecycle: provision a node

Per seeds/ontology.yaml lifecycle.transitions. Policy note: provisioning nodes get a lifecycle override — config_mutation actions downgrade to reversible_low because nothing depends on the node yet (see seeds/policy.yaml lifecycle_overrides).

Requires (from ontology): inventory entry, IP reserved, storage pool chosen, doc page stub.

  1. Create the LXC/VM on its target Proxmox host (pct create / qm create), choosing the storage pool deliberately — record it as the storage: field once populated (Week 1 schema; not yet backfilled for existing nodes).
  2. Add the inventory entry: a hosts.<name>: block in seeds/inventory.yaml with state: provisioning, kind, host, pve_id, lan_ip, then oikos seed to ingest it. For anything that will self-enroll as a client afterward (see CLIENTS.md), the entity must exist in planned/provisioning state before bootstrap.sh runs there.
  3. Stub a document entity via MCP upsert_knowledge with kind: document and about set to the new entity slug — even a one-line "provisioning, see plan X" is enough to satisfy the transition requirement.
  4. Reserve the IP in DNS/DHCP notes if it's a fixed LAN address.

Next: lifecycle-activate-node.md.