bulli server list --output jsonList current fleet
Get the latest inventory before any maintenance action.
[ System Admin Experience ]
Operate bare metal with clear daily tooling
Bullionet gives SysAdmin teams direct lifecycle actions, maintenance runbooks, and operational consistency across environments.
daily operations
# maintenance runbook
bulli server list --output json
bulli server power-off edge-api-02
bulli server reinstall edge-api-02 --os ubuntu-24.04
bulli server power-on edge-api-02
# validate health checks and traffic
[ Operations Command Set ]
Concrete runbook commands
Build clear maintenance and recovery routines around a stable command surface.
bulli server power-off --hostname edge-api-02Graceful power off
Prepare a node for maintenance intervention.
bulli server power-on --hostname edge-api-02Power on after intervention
Bring the node back into service after checks.
bulli server reinstall --hostname edge-api-02 --os ubuntu-24.04Reinstall clean image
Reset a compromised or drifted host quickly.
bulli server get --hostname edge-api-02Verify final state
Confirm host status and metadata after operations.
[ Simple SysAdmin Procedures ]
Daily operations that stay clear and repeatable
Use these procedures to reduce guesswork during maintenance and incident windows.
01
Safe reboot during maintenance window
You must reboot a production node with controlled risk.
•List current fleet status and identify exact target host before action.
•Run controlled power action and confirm the host returns to expected state.
•Validate service checks and document the intervention summary.
Expected result: node rebooted with service continuity and auditable trace.
02
Clean reinstall after drift
A server drifted from baseline and needs a predictable rebuild.
•Capture current host metadata and backup-required context before reinstall.
•Run reinstall with approved OS baseline and controlled lifecycle steps.
•Power on, validate readiness, and confirm host rejoined expected inventory.
Expected result: host restored to clean baseline without manual improvisation.
03
Fast replacement after hardware issue
A host shows instability and requires quick replacement workflow.
•Provision replacement server with matching plan, location, and network tags.
•Validate replacement health before moving workload traffic.
•Decommission old host only after replacement and checks are complete.
Expected result: stable replacement online and risky host retired safely.
[ Operations Layer ]
Run infrastructure without friction
Use practical controls for maintenance, recovery, and lifecycle tasks without operational dead-ends.
Lifecycle controls
Power-cycle, reinstall, and recover servers through a predictable interface.
Standardized maintenance routines
Execute recurring operational actions with repeatable steps.
Environment-level consistency
Keep staging and production aligned with common configuration patterns.
Reduced escalation overhead
Resolve common operations directly instead of relying on long support loops.
[ Runbook Model ]
Keep operational knowledge executable
Transform repetitive operations into reusable technical runbooks.
Maintenance runbooks
Define clear procedures for patch windows and controlled interventions.
Incident response flows
Execute fast remediation steps with minimal context switching.
Recovery playbooks
Prepare standardized restore actions for critical infrastructure components.
[ Operational Security ]
Control access and reduce operational risk
Apply practical access and execution boundaries aligned with production constraints.
Scoped tokens
Grant only the permissions needed for each operational scope.
Action traceability
Keep an auditable track of lifecycle and maintenance actions.
Safer automation boundaries
Use explicit rules so scripts and agents remain predictable in production.
