YAML constructor (oVirt)
Step-by-step oVirt provider parameters and download of two YAML files.
This constructor helps you prepare YAML manifests to install a management cluster with the oVirt and compatible virtualization provider via ./shtil install-cli ovirt --yaml-path=….
The result is two files: CapovProviderConfig (provider) and CapovClusterConfig (cluster). For the full installation process and field reference, see the Open loop installation process or Closed loop installation process page (Installation with YAML tab).
Important: Values you enter (including passwords) are stored only in browser memory while you use this page. Data is not sent to the server and not saved—when you leave the page, the form resets.
On the Cluster step, you can set the Ingress mode, platform version, service list, provider overwrite, installation log file, and Ingress certificate type (self-signed, CA, TLS, or ACME). The ingressCerts block is written to the provider file; cluster.* parameters go to the cluster file. VM disk cloning is set on the provider instance and on node groups. Default is not written to YAML.
Reference: service groups
Below are the quick-install groups from Shturval repository services.
Enabled services lists only extra services on top of the default set: critical platform services and the Monitoring and Logging groups are enabled by default. An unknown service name is ignored. The minimal service set installs only critical platform services. When you select a service, the constructor adds its dependent CRDs if those CRDs are also disabled by default. CSI, NFS, Ceph, Multus, SR-IOV, and provider charts are not in this list: they cannot be added as extra services.
The management cluster receives incoming HTTP traffic through Gateway API by default. shturval-gateway-api-crds is a critical service. The external connections module (shturval-ingress-controller) is installed in absent mode.
| Group name | Service name | System name |
|---|---|---|
| Critical Services | Cluster network management | shturval-networking |
| Local storage | shturval-local-csi | |
| snapshotter operator | shturval-snapshotter | |
| Host Configuration Management | shturval-node-config | |
| Service Installation Management | shturval-services | |
| Cluster update | shturval-update | |
| Virtual IP (node configuration) | shturval-vip | |
| Virtual IP (service configuration) | shturval-vip-provider | |
| Local DNS | shturval-caching-dns | |
| TLS Certificate Management | shturval-cert-manager | |
| Delivery of root certificates | shturval-trust-manager | |
| External connections (Ingress) | shturval-ingress-controller | |
| CRD Gateway API | shturval-gateway-api-crds | |
| Critical management cluster services | Software Control Chart | shturval-backend |
| Graphical platform control module | shturval-frontend | |
| Authentication | shturval-auth | |
| Cluster API Provider | shturval-capi | |
| Client Cluster Manager | shturval-cluster-manager | |
| Management Cluster Services | Centralized storage of metrics | shturval-monitoring |
| Provider Basis Dynamix | shturval-capbd | |
| OpenStack Provider | shturval-capos | |
| Provider Shturval v2 | shturval-capsm | |
| vSphere Provider | shturval-capvs | |
| Provider oVirt | shturval-capov | |
| Yandex Cloud Provider | shturval-capy | |
| vCloud Director Provider | shturval-capvcd | |
| Monitoring | Metrics collection and monitoring management | shturval-metrics-collector |
| Visualization of metrics | shturval-dashboards | |
| Verifying Kubernetes API Certificates | shturval-cert-expiration | |
| Logging | Local log collection | shturval-log-collector |
| Backup and Restore | Backup and Restore | shturval-backup |
| Application Delivery | Application Service Deployment Management | shturval-rollouts |
| Continuous Application Delivery | shturval-cd | |
| Load Balancer | Node Load Distribution | shturval-descheduler |
| Information Security Tools | Application Configuration Analysis | shturval-policy-manager |
| Scanning container images | shturval-scanner | |
| Optional services not in groups | NFS operator | shturval-nfs-csi |
| Ceph CSI - Ceph File System | shturval-ceph-cephfs | |
| Ceph CSI - Ceph Block Device | shturval-ceph-rbd | |
| oVirt CSI | shturval-capov-csi | |
| CSI vSphere | shturval-capvs-csi | |
| vCloud Director CSI | shturval-capvcd-csi | |
| CSI OpenStack | shturval-capos-csi | |
| Search for nodes with hostport services | shturval-coreha | |
| Multiple network interfaces (Multus) | shturval-metacni | |
| IP assignment on Multus interfaces | shturval-metacni-ipam | |
| SR-IOV Operator | shturval-sriov | |
| Node problem detection | shturval-npd |
No services for the selected group
For the full chart list with versions and descriptions, see Shturval repository services.
YAML constructor (oVirt)
Walk through the steps to generate two YAML manifests: provider and cluster. Download the files and pass the combined manifest path to install-cli. Values stay in the browser only and are cleared when you leave the page.
Review the YAML and download the files. Data is not saved after you leave the page.
After downloading, merge both documents into one file with a --- separator, or pass the path to the combined manifest to install-cli:
./shtil install-cli ovirt \
--yaml-path="/home/admin/install.yaml" \
--bootstrap-license="YOUR-LICENSE"
You can also get the current field structure and comments with ./shtil install-cli ovirt example.