General Settings
General settings define a VDI/DaaS model’s cloud provider, the VM family or shape, and the provider-specific parameters that configure the underlying virtual machine. The wizard collects them in its early steps — provider selection, Model Selector, Credentials, Parameters, and (on the Custom path) Template. After creation, they are spread across the model editor’s General, Templates, and Parameters tabs.
Cloud Provider
Each model is tied to a single cloud provider or on-premises hypervisor, chosen in Step 1 of the wizard.
For the full list of supported providers and the prerequisites for each, see Supported Providers and Hypervisors.
Built-in vs Custom
The Model Selector step offers two paths:
| Option | What it does |
|---|---|
| Built-in Model | A pre-configured model that Cloud Manager provisions through Cybele-authored Terraform templates. Each built-in maps a specific use case (General Purpose, Demanding Workflows, Graphic Performance) to an appropriate VM family from the chosen provider — for example, OCI’s E Flex family under General Purpose, or OCI’s GPU shapes under Graphic Performance. The Terraform, the field set in the Parameters step, and the defaults are all Cybele’s; the underlying VM family is the provider’s. |
| Use custom configuration | Supply your own Terraform template. The wizard collects the input variables declared in the template and presents them as configuration fields. See Custom Terraform Templates. |
The available built-ins depend on the provider. Cloud Manager exposes built-in models for OCI (3 variants), Microsoft Azure (3), IONOS Cloud (3), AWS (3), Google Cloud Platform (3), VMware ESXi/Horizon (2), Microsoft Hyper-V (1), and Proxmox VE (1). Verge.IO and Oracle KVM (oVirt / OLVM) are supported via Custom Terraform templates only.
For VMware, Hyper-V, and Proxmox VE, instances are provisioned by cloning a Golden Image — a vCenter VM template, a VHDX file, or a Proxmox VM template respectively. See Golden Images.
Provider-Specific Parameters
The wizard’s Parameters step presents configuration fields that depend on the provider selected and on the specific built-in within that provider. Providers expose a stable core of common fields across their built-ins, plus a smaller set of built-in-specific fields that surface only when a particular built-in is chosen — for example, IONOS Cubes exposes a Cube type dropdown that the vCPU Server and Dedicated Cores built-ins don’t, and VMware’s General Purpose (Non-Persistent) adds a Data Persistency field absent from the Persistent variant.
The Admin password field is set at model creation time and applied to all instances provisioned from this model. If you rotate the password, update it in the model settings — the change does not apply retroactively to instances already deployed.
Oracle Cloud (OCI)
Three built-ins share the same field set: General Purpose, Demanding Workflows, and Graphic Performance. Only the Instance type (OCI Shape) default changes between built-ins.
| Field | Default | Description |
|---|---|---|
| Specify parent compartment | Off | Toggle. When on, the wizard reveals a Parent compartment OCID field where you supply the OCID of the parent compartment under which the new compartment is created. When off, the new compartment is created under the tenancy root. |
| Use Existing Compartment | Off | Toggle. When off, the wizard shows Compartment Name for the compartment to create. When on, Compartment Name becomes a selector for an existing compartment. |
| Compartment Name | (empty) | Name of the compartment Terraform creates (or, when Use Existing Compartment is on, the name of an existing compartment to use). |
| Availability Domain Number | 1 |
Availability domain index (1, 2, or 3). Dropdown. Three is the maximum in commercial OCI regions. |
| Instance type (OCI Shape) | GP: AMD Standard E4 Flex · DW: VM.Optimized3.Flex · GR: VM.GPU2.1 |
OCI shape that defines the compute family. Different default per built-in. |
| Use Custom Image | Off | Toggle. When off, the wizard shows the OS Image dropdown. When on, the dropdown is replaced by a Custom image OCID field. |
| OS Image | Windows Server 2022 |
Visible only when Use Custom Image is off. Pre-built Windows image. Dropdown. |
| Custom image OCID | (empty) | Visible only when Use Custom Image is on. OCID of a user-supplied custom image. |
| Oracle CPU | 1 OCPU (2 VCore) |
OCPU count for Flex shapes. Dropdown with 4 entries. Ignored on fixed (non-Flex) shapes. |
| Memory | 8 GB |
Memory in GB for Flex shapes. Dropdown with 8 entries. |
| Disk size | 60 GB |
Boot-volume size in GB. |
| Admin username | cybele |
Local administrator username. |
| Admin password | (empty) | Local administrator password. |
| Assign Public IP | Off | Toggle. When on, instances are provisioned with a public IP. |
| Install Thinfinity Agent | On | Toggle. When on, the Thinfinity Workspace Virtualization Agent is installed automatically as part of provisioning. Required for the broker to recognize the instance. |
| Set specific DNS | Off | Toggle. When on, the wizard reveals fields to configure DNS for the instance. When off, the instance uses the provider’s default DNS. |
| Join to a domain | Off | Toggle. When on, the wizard reveals the domain-join fields below. The post-deploy script consumes these values to join each provisioned VM to the specified Active Directory domain. |
| DC server address | (empty) | Visible only when Join to a domain is on. Address of the Active Directory domain controller. |
| Domain user with join permissions | (empty) | Visible only when Join to a domain is on. Username with permission to add machine accounts to the target domain (e.g., corp\domainjoin). |
| Domain user password | (empty) | Visible only when Join to a domain is on. Password for the domain user account. |
| Set distinguished name | Off | Visible only when Join to a domain is on. Toggle. When on, the wizard reveals a field to specify the LDAP distinguished name of the target OU into which the machine account will be created. When off, the machine account is created in the default Computers container. |
| Wait for the instance to be ready (seconds) | 300 |
Post-provisioning wait before Cloud Manager considers the VM usable. |
OCI credentials (tenancy_ocid, user_ocid, fingerprint, private_key, private_key_password) live in the Oracle Cloud Credentials step. The Quick Start: Deploy a VDI Pool walks through an Oracle Cloud deployment.
Microsoft Azure
Three built-ins (General Purpose (BasV2), Demanding Workflows (DasV5), Graphic Performance (NVas_v4)) share the same 8 fields; only the Machine size default changes between built-ins.
| Field | Default | Description |
|---|---|---|
| Admin username | cybele |
Local administrator username. |
| Admin password | (empty) | Local administrator password. Azure password complexity rules apply (minimum length and character classes). |
| Location | eastus |
Azure region. Dropdown with ~43 entries. |
| Resource group | MyResourceGroup |
Existing Azure Resource Group name to deploy into. |
| Machine | BasV2: Standard_B2as_v2 · DasV5: Standard_D2as_v5 · NVas_v4: Standard_NV4as_v4 |
Azure VM size SKU. Different default per built-in. |
| Disk type | Premium_LRS |
Managed-disk SKU: Premium_LRS, StandardSSD_LRS, Standard_LRS, etc. |
| Disk size | 128 |
OS disk size in GB. Dropdown: 128, 256, 512, 1024. |
| Image | (must select) | Windows Server marketplace image SKU. Dropdown with ~12 options. |
Azure credentials (subscription_id, tenant_id, client_id, client_secret) live in the Microsoft Azure Credentials step.
IONOS Cloud
Three built-ins are offered: Cubes, vCPU Server, and Dedicated Cores (Bare Metal). They share a common set of fields; each variant adds a few more.
Common Fields (All Built-ins)
| Field | Default | Description |
|---|---|---|
| Use Custom Image | Off | Toggle. When off, the wizard shows the Ionos Image name dropdown. When on, that dropdown is replaced by a custom image OCID field. |
| Ionos Image name | Windows Server 2025 |
Visible only when Use Custom Image is off. Windows image dropdown. |
| Datacenter location | Newark, New Jersey, USA |
IONOS datacenter region. Dropdown labeled by city. |
| Use Existing Datacenter | Off | Toggle. When off, the wizard shows the New Datacenter Name field for the IONOS virtual data center to create. When on, the wizard shows a selector for an existing data center instead. |
| New Datacenter Name | (empty) | Visible only when Use Existing Datacenter is off. Name of the IONOS virtual data center to create. |
| Use Existing LAN | Off | Toggle. When off, the wizard shows the New LAN Name field for the LAN to create. When on, the wizard shows a selector for an existing LAN instead. |
| New LAN Name | (empty) | Visible only when Use Existing LAN is off. Name of the LAN to create. |
| Public Access LAN | On | Toggle. When on, the LAN is created with public internet access. |
| Admin password (Only alphanumeric) | (empty) | Local administrator password set on each provisioned VM. The label’s parenthetical reflects the IONOS character constraint — only alphanumeric characters are accepted. |
| Wait for the instance to be ready (seconds) | 20 |
Post-provisioning wait before Cloud Manager considers the VM usable. |
Cubes Built-in (Extra Fields)
| Field | Default | Description |
|---|---|---|
| Cube type | Basic Cube S (2Core 4GB Disk120) |
Pre-defined Cube product that bundles CPU, RAM, and NVMe storage. Dropdown with 9 SKUs. |
vCPU Server Built-in (Extra Fields)
| Field | Default | Description |
|---|---|---|
| Server Cores | 2 |
vCPU count. Dropdown with 5 options. |
| Disk Volume Size | 80 |
Disk size in GB. Dropdown with 8 options. |
| Disk Type | HDD |
Storage tier: HDD or SSD. |
Dedicated Cores (Bare Metal) Built-in (Extra Fields)
| Field | Default | Description |
|---|---|---|
| CPU family | INTEL_ICELAKE |
Bare-metal CPU family. Dropdown: INTEL_ICELAKE, INTEL_SKYLAKE, AMD_OPTERON, etc. (4 options). |
| Server RAM | 4096 |
Memory in MB. Dropdown with 6 options. |
| Server Cores | 2 |
vCPU count. Dropdown with 7 options. |
| Disk Volume Size | 80 |
Disk size in GB. Dropdown with 8 options. |
| Disk Type | HDD |
Storage tier: HDD or SSD. |
IONOS credentials live in the IONOS Cloud Credentials step.
AWS (EC2)
Three built-ins (General Purpose (T2), Demanding Workflows (T3), Graphic Performance (P3)) share the same field set; only the Machine dropdown and Disk Size default differ by family.
| Field | Default | Description |
|---|---|---|
| Admin username | cybele |
Local administrator username injected into the Windows image. |
| Admin password | (empty) | Local administrator password. |
| Region | us-east-1 |
AWS region. Dropdown with ~28 entries. |
| Machine | T2: t2.medium · T3: t3.medium · P3: p3.2xlarge |
EC2 instance type. Dropdown of family-specific shapes (T2 lists t2.medium–t2.2xlarge; P3 lists p3.2xlarge–p3dn.24xlarge with NVIDIA Tesla V100 GPUs). |
| Disk Type | gp2 |
EBS volume type. Dropdown: sc1, st1, gp2, gp3, io1, io2. |
| Disk Size | T2/T3: 64 · P3: 128 |
Root EBS size in GB. Dropdown: 64, 128, 256, 512, 1024. |
| Image Name | Windows_Server-2022 |
Windows AMI family. Dropdown: 2022, 2019, 2016. |
VPC and subnet are wired automatically by the platform and do not appear in the wizard. AWS credentials (access_key, secret_key) live in the AWS Credentials step.
Google Cloud Platform
Three built-ins (General Purpose (E2), Demanding Workflows (N2), Graphic Performance (G2)) share the same 8 fields; only the Machine dropdown differs by family.
| Field | Default | Description |
|---|---|---|
| Admin username | cybele |
Local administrator username. |
| Admin password | (empty) | Local administrator password. |
| Region | us-central1 |
GCP region. Dropdown with ~40 entries. |
| Zone | a |
Zone suffix within the region (a, b, c). Combined with Region to form the full zone (e.g., us-central1-a). |
| Machine | e2-medium |
Predefined machine type. Each built-in advertises its own family enum (e2-*, n2-*, g2-*). |
| Image | windows-server-2022-dc-v20240711 |
Public Windows Server image. Dropdown: 2022, 2019, 2016 Datacenter. |
| Disk size | 128 |
Boot disk size in GB. Dropdown: 128, 256, 512, 1024. |
| Disk type | pd-standard |
Persistent disk type: pd-standard, pd-ssd, pd-extreme. |
GCP credentials (a JSON service-account key) live in the Google Cloud Platform Credentials step.
VMware (ESXi / Horizon)
Two built-ins are offered: General Purpose and General Purpose (Non-Persistent). Both share the same 9 core fields; Non-Persistent adds one extra field that toggles disk persistence.
Common Fields (Both Built-ins)
| Field | Default | Description |
|---|---|---|
| VM Name to clone | Win10cybele |
Name of the vCenter VM template that each instance is cloned from. Conceptually this is the model’s Golden Image. |
| Server Cores | 2 |
vCPU count. Dropdown with 7 options. |
| Server Memory | 4096 |
Memory in MB. Dropdown with 6 options. |
| Disk Volume Size | 60 |
Disk size in GB. Dropdown with 9 options. |
| Data Center Name | DC1 |
vCenter datacenter object name. |
| Cluster Name | C1 |
vCenter compute cluster within the datacenter. |
| Pool Name | Pool1 |
Resource pool name. |
| Data Store Name | datastore1 |
Datastore on which the clone is placed. |
| Network Name | VM32 |
Port-group / network label to attach the VM NIC. |
General Purpose (Non-Persistent) Extra Field
| Field | Default | Description |
|---|---|---|
| Data Persistency | No |
Dropdown (Yes / No) that controls the vSphere disk mode of the cloned VM. Yes sets disk_mode = persistent — changes survive reboots and snapshots behave normally. No sets disk_mode = independent_nonpersistent — changes are discarded on power-off, which is the typical configuration for non-persistent VDI. The wizard exposes the toggle as disk_modeOP and writes the chosen value into the Terraform disk_mode variable consumed by main.tf. |
VMware credentials (host, port, user, password, allow_unverified_ssl) live in the VMware Credentials step.
For VMware, the VM template must have the Thinfinity® Workspace Virtualization Agent installed and configured before it is converted to a template in vCenter. See Create a Golden Image.
Microsoft Hyper-V
Single built-in: General Purpose.
| Field | Default | Description |
|---|---|---|
| Image Location | D:\MODELS |
Path on the Hyper-V host where the source VHDX template lives. |
| Image Name | Win10cybele |
File name (without extension) of the source VHDX template. |
| Folder Location | D:\MODELS |
Destination folder on the Hyper-V host for new VHDX files. |
| Switch Name | New Virtual Switch |
Virtual switch name to attach the new VM’s NIC. |
| Admin Password | (empty) | Local administrator password applied to each cloned VM. The value is collected by the wizard but not consumed by the Hyper-V Terraform template — the underlying VHDX is expected to already have an Administrator account configured, and the password is applied by Cloud Manager’s post-deploy step rather than by Terraform. |
| Server Cores | 2 |
vCPU count. Dropdown: 1, 2, 4, 6, 8, 10, 12. |
| Server RAM | 2 GiB |
Memory. Dropdown: 1, 2, 4, 8, 16, 32 GiB. |
| Disk Type | SCSI |
Disk-controller type: IDE, SCSI, SAS. |
Hyper-V credentials (host, user, password) live in the Microsoft Hyper-V Credentials step.
The Hyper-V built-in provisions instances by cloning a prepared VHDX template located on the Hyper-V host — analogous to how VMware clones a vCenter VM template. See Golden Images.
Proxmox VE
Single built-in: General Purpose.
| Field | Default | Description |
|---|---|---|
| VM name to clone | Win10Cybele |
Source VM (template) name in Proxmox to clone. |
| Node name | proxmox |
Proxmox cluster node where the clone is placed. |
| Server cores | 2 |
vCPU count. Dropdown: 1, 2, 4, 6, 8, 10, 12. |
| Server memory | 8192 |
Memory in MB. Dropdown: 1024, 2048, 4096, 8192, 16384, 32768. |
| Disk volume size | 60 |
Disk size in GB. Dropdown with 9 options. |
| Data store name | local-lvm |
Proxmox storage name for the disk. |
| Network name | vmbr1 |
Linux-bridge name to attach the VM NIC. |
Proxmox credentials (pm_user, pm_password, Proxmox API URL) live in the Proxmox VE Credentials step.
The Proxmox built-in provisions instances by cloning a Proxmox VM template (a VM converted to template status on the Proxmox node) — analogous to how VMware clones a vCenter VM template. See Golden Images.
Verge.IO
Verge.IO uses Custom Terraform templates — Cloud Manager does not ship a built-in Verge.IO model. The Verge.IO model clones from a Verge.IO VM Recipe, which you reference from your template. The parameter fields shown in the wizard’s Parameters step are the input variables (variable blocks) declared in your template, optionally annotated with user-facing labels via a params_config.json file bundled alongside the template.
Typical Verge.IO parameters exposed by Custom templates include: target tenant or site, network selection, storage tier, clone options. The exact set depends on what your template author chooses to declare.
See Custom Terraform Templates for authoring guidance. Verge.IO credentials live in the Verge.IO Credentials step.
Oracle KVM (oVirt / OLVM)
Oracle KVM is supported via Custom Terraform templates. Supply a Custom Terraform template at model creation time — the parameter fields shown in the wizard’s Parameters step are the input variables (variable blocks) declared in your template, optionally annotated with user-facing labels via a params_config.json file bundled alongside the template.
Typical Oracle KVM parameters exposed by Custom templates include: target cluster, storage domain, vNIC profile, CPU/memory profile, cloud-init configuration. The exact set depends on what your template author chooses to declare.
See Custom Terraform Templates for authoring guidance. Oracle KVM credentials live in the Oracle KVM Credentials step.
Editing General Settings After Creation
To open the model editor, click the edit icon on the model in the left tree.
Changing the provider-specific parameters — including the Golden Image reference, VM family, or image ID — on a model that has active deployed instances does not automatically update those instances. To roll out changes to running instances, create a new model version, validate it in Testing or Staging, then promote to Production and reprovision. See Model Versioning.
See Also