Skip to content

Verify Authoritative On-Prem Foundation

Execution context: Run this procedure from a terminal where hyops --help succeeds. If HybridOps.Core is not installed, complete the Quickstart. For deployment support, use GitHub Discussions.

Intent

  • Purpose: Confirm the shared network baseline and the authority required by downstream platform operations.
  • Trigger: Pre-demo validation, post-change validation, or routine confirmation before downstream rollout.
  • Impact: Verifies the network baseline, selected inventory authority, and operation-admission result.
  • Severity: P2
  • Rollback: Verification only. If the foundation is unhealthy, stop downstream rollout and reconcile NetBox or SDN first.

Preconditions

  • The shared on-prem foundation has already been deployed.
  • The management subnet is reachable from the verification host.

Verify NetBox state

hyops show module platform/onprem/netbox --env shared

Expected:

  • status=ok
  • cap.ipam.netbox: ready
  • netbox_url is published
  • netbox_api_url is published

Verify SDN state

hyops show module core/onprem/network-sdn --env shared

Expected:

  • status=ok
  • zone_name: shybzone
  • the current VNet and subnet outputs are present

Verify operation authority

hyops blueprint preflight \
  --env shared \
  --ref onprem/authoritative-foundation@v1

For each authority-dependent step, confirm that the preflight result records:

  • logical_authority: primary_ipam
  • capability: inventory_ipam
  • the selected binding and safe instance or endpoint identity
  • an admitted result and verified state
  • no token, password, or embedded credential

Stop if the binding is missing, stale, unhealthy, unreachable, or does not support the required capability.

Verify the selected authority service

Read the published netbox_url from module state, then check that endpoint:

curl -fsSI <netbox_url>

Expected:

  • the endpoint responds
  • the root path redirects to the NetBox login flow

Optional browser confirmation

Open:

  • the netbox_url published by module state

What to confirm:

  • NetBox is reachable on the shared management lane
  • the login surface is present and ready for use as the authoritative inventory UI

References