Prerequisites
- Bootstrap completed with all dependency groups passing
- Hosts configured with SSH connectivity to all target nodes
- Configuration saved with networking, storage, and service settings
- Images loaded and available in the local registry
Deployment Wizard
The Operations wizard guides you through four steps to execute any deployment action. Each step validates input before allowing you to proceed.Select Action
Select the deployment action to execute from the available categories: Deploy, Manage, Backend, or Advanced. Each action is described with its purpose and expected duration.
Select Target Hosts
Select which servers to target:
- All Hosts — execute across the entire cluster
- Specific Hosts — select individual servers via a checklist
- Host Patterns — target groups such as all compute nodes or all storage nodes
Select Services (Optional)
Narrow the scope to specific cloud services or deploy all enabled services. Selecting individual services is useful for targeted reconfiguration or troubleshooting without affecting the rest of the cluster.
Run Deployment
Review the action summary and click Run to execute. Destructive actions (Stop, Destroy) require explicit confirmation before execution begins.
Available Actions
- Deploy
- Manage
- Backend
- Advanced
Actions for initial deployment and readiness validation.
Additional deploy actions are available via the command selector: Deploy Bifrost
(bare-metal provisioning service) and Deploy Servers (provision bare-metal servers
through Bifrost). These are not shown as wizard cards but can be selected from the
action dropdown.
Command Modifiers
Actions in the Operations wizard support optional modifiers that control execution behavior.Live Terminal
Every action execution streams full terminal output in real time, providing complete visibility into each playbook task as it runs.Real-Time Metrics
Live counters for task success, warnings, failures, and overall completion percentage update as each task finishes.
Searchable History
All task output is archived and searchable. Filter by task name, host, or status to quickly locate specific events across long deployment runs.
Understanding Terminal Output
Understanding Terminal Output
Each line in the terminal represents an Ansible task. Tasks display their target host, task name, and result status:
- ok — Task completed successfully, no changes needed
- changed — Task completed successfully and modified the system
- failed — Task encountered an error (deployment may continue or stop depending on the task)
- skipped — Task was not applicable to the current configuration
Quick Guide
Quick Guide
The Operations tool includes a Quick Guide button that opens a recommended workflow tutorial. This guide walks through the standard deployment sequence and explains when to use each action.
Recommended Workflow
Follow this sequence for a successful first deployment. Each step must complete without errors before proceeding to the next.Run Prechecks
Execute Prechecks against all target hosts. This validates port availability, service connectivity, configuration consistency, and Docker readiness across the cluster.
Fix Reported Issues
Review any failures or warnings from the Prechecks output. Common issues include missing Docker configuration, incorrect NIC assignments, and port conflicts. Resolve every failure before continuing.
Run Deploy
Execute the Deploy action against all hosts. This provisions every enabled cloud service as Docker containers, configures HAProxy load balancing, and starts all services.
Deployment duration scales with cluster size and network speed. A 3-node cluster typically completes in 30-45 minutes. Larger clusters with 10+ nodes may take up to 90 minutes.
Run Post-Deploy
Execute Post-Deploy to create the admin user account, default tenant networks, base compute flavors, and initial project structure. This step finalizes the environment for production use.
Verify via Dashboard and CLI
Log in to the Xloud Dashboard (
https://connect.<your-domain>) with the admin credentials created during Post-Deploy. Verify that all services are listed and operational.Verify service endpoints
All services report status up — the deployment is complete and operational.
Troubleshooting
Prechecks report port conflicts
Prechecks report port conflicts
Cause: Another service or previous deployment remnant is using a port required by a cloud service.Resolution: Identify the conflicting process using
ss -tlnp | grep <port> on the affected host. Stop or remove the conflicting service. If a previous deployment was not fully destroyed, run Destroy before redeploying.Deploy fails with image pull errors
Deploy fails with image pull errors
Cause: Container images are not available in the local registry, or Docker cannot reach the registry.Resolution: Return to the Images tool and verify that all required images are loaded and pushed to the local registry. Confirm that
docker-registry:4000 is listed as an insecure registry in the Docker daemon configuration on every node.Post-Deploy fails to create admin user
Post-Deploy fails to create admin user
Cause: The Xloud Identity service is not yet fully initialized when Post-Deploy runs.Resolution: Wait 30-60 seconds after Deploy completes before running Post-Deploy. The identity service needs time to complete database migrations and start accepting requests. Re-run Post-Deploy after the brief delay.
Next Steps
Management
Create users, projects, quotas, and credentials for your deployed cloud
Cloud Fleet
View the interactive topology map of your deployed infrastructure