Configuration is the main settings interface for your entire cloud. All settings are saved to globals.yml --- the master deployment configuration file that controls every aspect of your environment. Instead of editing YAML manually, XDeploy provides forms, dropdowns, toggles, and validation across eight configuration tabs.
Prerequisites
Bootstrap completed on the deployment server
Hosts configured with verified SSH access
Network interface names identified on all target servers
Virtual IP (VIP) addresses planned for your management subnet
Log in to XDeploy (https://xdeploy.<your-domain>) on the deployment node using administrative access.Navigate to Configuration in the left sidebar. The configuration interface is organized into eight tabs, each handling a distinct area of your deployment settings.
XAVS Settings
Network
Storage
Load Balancer
Monitoring
Advance Features
Custom Config
Logs
The primary settings tab covering networking, domains, and TLS configuration. These settings form the foundation of your entire deployment.
Select the NIC used for management traffic. Auto-fills the Internal VIP field based on the selected interface subnet.
Internal VIP Address
Yes
Virtual IP for internal API calls. Floats between controllers via HAProxy for high availability.
External VIP Address
No
Public-facing VIP for external access and the Xloud Dashboard. Required only if external access is needed.
The Internal VIP is the single most important setting in your deployment. If it is wrong, nothing works. Ensure it is an unused IP address on the management subnet that does not conflict with any existing host.
Single (one NIC for all external traffic) or Multiple (per-host NIC mapping)
Neutron External Interface
The NIC used for provider networks and external VM connectivity
The selected external interface loses its current IP address after deployment. It is enslaved to a network bridge for provider traffic. Ensure this NIC name exists on all hosts that require external connectivity.
High availability for L3 and DHCP agents across multiple nodes
SR-IOV
OFF
Hardware-accelerated networking via Single Root I/O Virtualization
Feature toggles marked OFF are premium or specialized capabilities. Enable them based on your workload requirements. Each can be activated at any time via reconfiguration.
Configures Xloud Block Storage --- the persistent volume service for VM disks.
For production multi-node deployments, Xloud recommends Ceph RBD. It provides data replication across nodes, eliminating single points of failure for VM disks.
Configures the Xloud Load Balancer service for distributing network traffic across backend instances.
Master switch to enable the load balancer service across the deployment
Enabling the load balancer service deploys additional infrastructure components including controller agents and amphora VMs. Ensure sufficient compute capacity before enabling.
Configure the certificate authority parameters used for secure communication between the load balancer controller and amphora instances.
Field
Description
Country
Two-letter country code for the CA certificate (e.g., US)
State
State or province for the CA certificate
Organization
Organization name for the CA certificate
Org Unit
Organizational unit for the CA certificate
The ACTIVE_STANDBY topology provides high availability for load balancers at the cost of double the amphora resources. For production deployments, always use ACTIVE_STANDBY.
Configure observability, logging, and security monitoring for your cloud environment.
Feature
Default
Description
Enable Prometheus
OFF
Metrics collection from all cloud services and infrastructure
Enable Grafana
OFF
Visual dashboards for metrics visualization and analysis
Enable Central Logging
OFF
Aggregated log search and analysis across all nodes
Enable Security Suite
OFF
Integrated SIEM, vulnerability scanning, OS hardening, and security posture dashboard (visible when Central Logging is enabled)
Visible when Prometheus is enabled. Configure alert delivery channels.
Field
Description
SMTP Server
Mail server for email alert delivery
Alert Email
Recipient address for alert notifications
Webhook URL
HTTP endpoint for webhook-based alert delivery
Each channel includes a Test button to verify connectivity before deployment.
Configure at least one alert channel before deploying to production. Without alerts, critical infrastructure issues may go undetected.
Enable or disable premium and specialized services. Each toggle activates the corresponding service and its dependencies during deployment.
Feature
Default
Description
Enable KMS
OFF
When enabled, the Xloud Key Management service (Barbican) is deployed for secret storage, encryption keys, and certificate management
Enable Host HA
OFF
Enable high availability for hosts. Automatically detects and recovers from compute node failures by evacuating affected instances to healthy nodes.
Enable Dynamic Cluster Optimization
OFF
Enable the dynamic cluster optimization service for automated workload balancing, resource consolidation, and thermal management across the cluster
Enable DB Backup Utility
OFF
Enable the database backup utility for scheduled and on-demand backups of cloud service databases
Enable ProxySQL
OFF
Enable ProxySQL for database load balancing and query routing across multiple database replicas
Enable Disk Encryption
OFF
Enable disk encryption using key management for volume-level encryption at rest. Requires KMS to be enabled first.
Enable Insecure Registry
OFF
Enable custom Docker registry configuration (docker-registry:4000) for internal container image distribution
Enable Disk Encryption depends on Enable KMS. If KMS is not enabled, the disk encryption toggle has no effect. Enable KMS first, then enable disk encryption.
These are premium or specialized capabilities that are disabled by default. Enable them based on your workload requirements. Each feature can be activated at any time via reconfiguration and redeployment.
A raw YAML editor for deployment settings not covered by the other tabs. Content entered here is appended directly to globals.yml during deployment.
Field
Description
Custom Configuration
Raw YAML key-value pairs appended to the deployment configuration
Documentation
Free-text area for comments and notes about custom settings
Use Custom Configuration as an escape hatch. There are hundreds of deployment variables available in the underlying automation --- the other tabs cover the most common ones. Consult the xavs-ansible variable reference for the full list.
View the history of configuration changes --- what was saved, when it was saved, and what changed between versions.XDeploy automatically backs up the last 5 versions of your configuration. If a configuration change causes issues, you can review previous versions to identify what changed.
