Skip to content

Deploy EVE-NG (HyOps Blueprint)

Purpose: Deploy a working EVE-NG foundation using a repeatable blueprint run.
Owner: Platform engineering
Trigger: Lab platform bring-up, baseline refresh, or controlled environment rebuild
Impact: Consumes shared SDN/NetBox authority, builds Jammy template image (if needed), provisions an EVE-NG VM, configures EVE-NG
Severity: P2
Pre-reqs: Proxmox init completed for the environment, vault decrypt working, NetBox authority is ready (authoritative IPAM), Ansible deps installed, EVE-NG target is Ubuntu 22.04.
Rollback strategy: Destroy affected modules with the same overlays, or rebuild the VM from a clean baseline.

Context

This runbook executes the blueprint:

  • Blueprint: onprem/eve-ng@v1
  • Location: hybridops-core/blueprints/onprem/eve-ng@v1/blueprint.yml

Preconditions and safety checks

  • Installed hyops (via install.sh) can be run from any working directory.
  • Source-checkout usage should export HYOPS_CORE_ROOT=/path/to/hybridops-core.
  • Correct environment selected (--env dev|staging|prod).
  • Secrets available via shell env or runtime vault:
  • EVENG_ROOT_PASSWORD
  • EVENG_ADMIN_PASSWORD
  • EVE-NG VM must be Ubuntu 22.04 (Jammy). HyOps enforces this during preflight/apply.

NetBox foundation is required for IPAM:

  • This blueprint allocates the EVE-NG VM IP from NetBox (no hardcoded per-VM IPs) and consumes the shared SDN authority state.
  • By default, HyOps expects NetBox authority in --env shared. If it is not ready yet, run:
hyops blueprint deploy --env shared --ref onprem/bootstrap-netbox@v1 --execute

This also seeds the shared SDN foundation and NetBox IPAM/inventory datasets consumed by this blueprint.

Install/update Ansible runtime deps for the env:

# If you installed via install.sh (default runs setup-all), this is already done.
# To (re)install Ansible Galaxy deps for an env:
hyops setup ansible --env dev

Steps

  1. Validate and plan
hyops blueprint validate --ref onprem/eve-ng@v1
hyops blueprint plan --ref onprem/eve-ng@v1
  1. Preflight
hyops blueprint preflight --env dev \
  --ref onprem/eve-ng@v1
  1. Execute
hyops blueprint deploy --env dev \
  --ref onprem/eve-ng@v1 \
  --execute

hyops blueprint deploy --execute now runs a blueprint preflight gate first. If contracts/resolution fail, execution stops before the first module step. Use --skip-preflight only for controlled break-glass runs.

During long module phases, HyOps prints:

  • progress: logs=... (active driver log file)
  • progress: phase=preflight|apply|destroy|...
  • periodic heartbeat lines for long-running streamed commands

Optional tuning:

export HYOPS_PROGRESS_INTERVAL_S=30
  1. Verify
cat $HOME/.hybridops/envs/dev/state/modules/platform__onprem__eve-ng/latest.json

Verification

Success indicators:

  • status is ok
  • outputs.eveng_url is present
  • outputs.cap.lab.eveng is ready

References