Deployment values
The following deployment values can be used to configure the Storage Scale cluster instance on IBM Cloud®.
Mandatory deployment values
The following are the mandatory deployment values used to configure the Storage Scale cluster instance on IBM Cloud®:
| Value | Description | Is it required? | Default value |
|---|---|---|---|
ibmcloud_api_key |
Provide the IBM Cloud API key for the account where the IBM Storage Scale cluster will be deployed, this is a required value that must be provided as it is used to authenticate and authorize access during the deployment. For instructions on creating an API key, see Managing user API keys. | Yes | Null |
storage_gui_username |
GUI username to perform system management and monitoring tasks on the storage cluster. Note: Username should be at least 4 characters, (any combination of lowercase and uppercase letters). | Yes | "" |
storage_gui_password |
The storage cluster GUI password is used for logging in to the storage cluster through the GUI. The password should contain a minimum of 8 characters. For a strong password, use a combination of uppercase and lowercase letters, one number, and a special character. Make sure that the password doesn't contain the username and it should not start with a special character. | No | "" |
existing_resource_group |
Specify the name of the existing resource group in your IBM Cloud account where cluster resources will be deployed. By default, the resource group is set to 'Default.' In some older accounts, it may be 'default,' so verify the resource group name before proceeding. If the value is set to "null", the automation will create two separate resource groups: 'workload-rg' and 'service-rg.' For more information, see Managing resource groups. | Yes | Default |
remote_allowed_ips |
To ensure secure access to the IBM Storage Scale cluster via SSH, you must specify the public IP addresses of the devices that are permitted to connect. These IPs will be used to configure access restrictions and protect the environment from unauthorized connections. To allow access from multiple devices, provide the IP addresses as a comma-separated list in the format: ["169.45.117.34", "203.0.113.25"]. Identify your current public IP address, you can visit: https://ipv4.icanhazip.com. | Yes | None |
ssh_keys |
Provide the names of the SSH keys already configured in your IBM Cloud account to enable access to the Storage Scale nodes. The solution does not create new SSH keys, so ensure you provide existing ones. These keys must reside in the same resource group and region as the cluster being provisioned.To provide multiple SSH keys, use a comma-separated list in the format: ["key-name-1", "key-name-2"]. If you do not have an SSH key in your IBM Cloud account, you can create one by following the instructions SSH Keys. | Yes | Null |
zones |
Specify the IBM Cloud zone within the chosen region where the IBM Storage scale cluster will be deployed. A single zone input is required, (for example, ["us-east-1"]) all the cluster nodes will all be provisioned in this zone. For more information, see Zones. | Yes | ["us-east-1"] |
volume_storages |
Configures the boot and block volumes for each instance. Boot volumes use the SDP profile by default but can be changed to a general-purpose profile if required by the workload. If the boot volume profile is set to general-purpose, the IOPS value should be set to 0 or null, as IOPS are not supported for that profile. Block volumes are always created with the SDP profile to maintain performance standards. You can specify optional boot volume settings (profile, size, IOPS), while block volume capacity and IOPS are mandatory. Both volume types support an optional auto-grow feature that allows disk size to increase automatically when needed through automation. | Yes | [{# Boot Volume boot_volume_profile = "sdp" boot_volume_size = 100 boot_volume_iops = 3000 # IOPS is not applicable for general-purpose profile boot_volume_disk_grow = false # Block Volume block_volume_capacity = 500 block_volume_iops = 20000 block_volume_disk_grow = false}] |
Optional deployment values
The following are the optional deployment values used to configure the Storage Scale cluster instance on IBM Cloud®:
| Value | Description | Is it required? | Default value |
|---|---|---|---|
ibm_customer_number |
IBM Customer Number (ICN) used for Bring Your Own License (BYOL) entitlement check and not required if storage_type is evaluation, but must be provided if storage_type is VSI or bare-metal. Failing to provide an ICN will cause the deployment to fail to decrypt the packages. For more information on how to find your ICN, see What is my IBM Customer Number (ICN)?. | No | Null |
cluster_prefix |
Prefix that is used to name the IBM Cloud resources that are provisioned to build the Storage Scale cluster. Make sure that the prefix is unique, since you cannot create multiple resources with the same name. The maximum length of supported characters is 64. Preifx must begin with a letter and end with a letter or number. | No | Null |
vpc_name |
Provide the name of an existing VPC in which the cluster resources will be deployed. If no value is given, the solution provisions a new VPC. For more information, see IBM Cloud VPC docs. You
can also choose to use existing subnets under this VPC or let the solution create new subnets as part of the deployment. If a custom DNS resolver is already configured for your VPC, specify its ID under the dns_custom_resolver_id input value. |
No | Null |
vpc_cidr |
Provide an address prefix to create a new VPC when the vpc_name variable is set to null. VPC will be created using this address prefix, and subnets can then be defined within it using the specified subnet CIDR blocks. For
more information on address prefix, see Setting IP ranges. |
No | "10.241.0.0/18" |
bastion_instance |
Bastion node functions as a jump server to enable secure SSH access to cluster nodes, ensuring controlled connectivity within the private network. Specify the configuration details for the bastion node, including the image and instance profile. Only Ubuntu 22.04 stock images are supported. | No | {image = "ibm-ubuntu-22-04-5-minimal-amd64-8 " profile = "cx2-4x8"} |
login_subnets_cidr |
Provide the CIDR block required for the creation of the login cluster private subnet. Single CIDR block is required. If using a hybrid environment, modify the CIDR block to avoid conflicts with any on-premises CIDR blocks. Since the login subnet is used only for the creation of login virtual server instances, provide a CIDR range of /28. | No | "10.241.16.0/28" |
deployer_instance |
A deployer node is a dedicated virtual machine or server instance used to automate the deployment and configuration of infrastructure and applications for HPC cluster components. Specify the configuration for the deployer node, including the custom image and virtual server instance profile. | No | {image = "hpcc-scale-deployer-v2" profile = "mx2-4x32"} |
client_subnets_cidr |
Provide the CIDR block required for the creation of the client private subnet. Single CIDR block is required. If using a hybrid environment, modify the CIDR block to avoid conflicts with any on-premises CIDR blocks. Ensure the selected CIDR block size can accommodate the maximum number of scale client nodes expected in your cluster. For more information on CIDR block size selection, see Choosing IP ranges for your VPC. | No | "10.241.50.0/24" |
compute_instances |
Specify the list of virtual server instances to be provisioned as compute nodes in the cluster. Each object includes the instance profile (machine type), number of instances (count), OS image to use, and an optional filesystem mount path. This configuration allows customization of the compute tier to suit specific performance and workload requirements. The profile must match a valid IBM Cloud VPC Gen2 instance profile format. A minimum of 3 compute nodes is required to form a cluster, and a maximum of 64 nodes is supported. For more information, see Instance Profiles. | No | [{profile = "cx2-2x4" count = 0 image = "hpcc-scale6000-rhel810-v1" filesystem = "/gpfs/fs1"}] |
client_instances |
Specify the list of virtual server instances to be provisioned as client nodes in the cluster. Each object includes the instance profile (machine type), number of instances (count), OS image to use. This configuration allows customization of the compute tier to suit specific performance and workload requirements. The profile must match a valid IBM Cloud VPC Gen2 instance profile format. For more information, see Instance Profiles. | No | [{ profile = "cx2-2x4" count = 0 image = "ibm-redhat-8-10-minimal-amd64-10"}] |
compute_subnets_cidr |
Provide the CIDR block required for the creation of the compute private subnet. Single CIDR block is required. If using a hybrid environment, modify the CIDR block to avoid conflicts with any on-premises CIDR blocks. Ensure the selected CIDR block size can accommodate the maximum number of scale compute nodes expected in your cluster. For more information on CIDR block size selection, see Choosing IP ranges for your VPC. | No | "10.241.0.0/20" |
compute_gui_username |
GUI username to perform system management and monitoring tasks on the compute cluster. The Username should be at least 4 characters, (any combination of lowercase and uppercase letters). | No | "" |
compute_gui_password |
Password for logging in to the compute cluster GUI. Must be at least 8 characters long and include a combination of uppercase and lowercase letters, a number, and a special character. It must not contain the username or start with a special character. | No | "" |
storage_subnets_cidr |
Provide the CIDR block required for the creation of the storage private subnet. Single CIDR block is required. If using a hybrid environment, modify the CIDR block to avoid conflicts with any on-premises CIDR blocks. Ensure the selected CIDR block size can accommodate the maximum number of scale storage nodes expected in your cluster. For more information on CIDR block size selection, see Choosing IP ranges for your VPC. | No | "10.241.30.0/24" |
storage_instances |
Specify the list of virtual server instances to be provisioned as storage nodes in the cluster. Each object includes the instance profile (machine type), number of instances (count), OS image to use, and an optional filesystem mount path. This configuration allows customization of the storage tier to suit specific storage performance cluster. The profile must match a valid IBM Cloud VPC Gen2 instance profile format. A minimum of 2 storage nodes is required to form a cluster, and a maximum of 64 nodes is supported. For more information, see Instance Profiles. | No | [{ profile = "bx2-32x128" count = 2 image = "hpcc-scale6000-rhel810-v1" filesystem = "/gpfs/fs1" }] |
storage_baremetal_server |
Specify the list of bare metal servers to be provisioned for the storage cluster. Each object in the list specifies the server profile (hardware configuration), the count (number of servers), the image (OS image to use), and an optional filesystem mount path. This configuration allows flexibility in scaling and customizing the storage cluster based on performance and capacity requirements. Only valid bare metal profiles supported in IBM Cloud VPC should be used. A minimum of 2 baremetal storage nodes is required to form a cluster, and a maximum of 64 nodes is supported For available bare metal profiles, see Baremetal Profiles. | No | [{profile = "cx2d-metal-96x192" count = 2 image = "hpcc-scale5232-rhel810-v1" filesystem = "/gpfs/fs1"}] |
protocol_subnets_cidr |
Provide the CIDR block required for the creation of the protocol private subnet. Single CIDR block is required. If using a hybrid environment, modify the CIDR block to avoid conflicts with any on-premises CIDR blocks. Ensure the selected CIDR block size can accommodate the maximum number of protocol nodes expected in your cluster. For more information on CIDR block size selection, see Choosing IP ranges for your VPC. | No | "10.241.40.0/24" |
protocol_instances |
Specify the list of virtual server instances to be provisioned as protocol nodes in the cluster. Each object in the list includes the instance profile (machine type), the count (number of instances), the image (OS image to use). This configuration allows allows for a unified data management solution, enabling different clients to access the same data using NFS protocol.This input can be used to provision virtual server instances (VSI). If persistent, high-throughput storage is required, consider using bare metal instances instead. Ensure you provide valid instance profiles. Maximum of 32 VSI or baremetal nodes are supported. For more information, see Instance Profiles. | No | [{ profile = "cx2-32x64" count = 2 image = "hpcc-scale5232-rhel810-v1"}] |
colocate_protocol_instances |
Enable this option to colocate protocol services on the same virtual server instances used for storage. When set to true, the storage nodes will also act as protocol nodes for reducing the need for separate infrastructure. This can optimize resource usage and simplify the cluster setup, especially for smaller environments or cost-sensitive deployments. For larger or performance-intensive workloads, consider deploying dedicated protocol instances instead. | No | True |
filesystem_config |
Specify the configuration parameters for one or more IBM Storage Scale (GPFS) filesystems. Each object in the list includes the filesystem mount point, block size, and replica settings for both data and metadata. These settings determine how data is distributed and replicated across the cluster for performance and fault tolerance. | No | [{filesystem = "/gpfs/fs1" block_size = "4M" default_data_replica = 2 default_metadata_replica = 2 max_data_replica = 3 max_metadata_replica = 3}] |
filesets_config |
Specify a list of filesets with client mount paths and optional storage quotas (0 means no quota) to be created within the IBM Storage Scale filesystem. | No | [{client_mount_path = "/mnt/scale/tools" quota = 0},{client_mount_path = "/mnt/scale/data" quota = 0}] |
afm_instances |
Specify the list of virtual server instances to be provisioned as AFM nodes in the cluster. Each object in the list includes the instance profile (machine type), the count (number of instances), the image (OS image to use). This configuration allows you to access remote data and high-performance computing needs.This input can be used to provision virtual server instances (VSI). If persistent, high-throughput storage is required, consider using bare metal instances instead. Ensure you provide valid instance profiles. Maximum of 16 AFM nodes is supported. For more information, see Instance Profiles. | No | [{profile = "bx2d-32x128" count = 0 image = "hpcc-scale5232-rhel810-v1"}] |
afm_cos_config |
Provide details for the Cloud Object Storage (COS) instance, including information about the COS bucket, service credentials (HMAC key), AFM fileset, mode (such as Read-only (RO), Single writer (SW), Local updates (LU), and Independent
writer (IW)), storage class (standard, vault, cold, or smart), and bucket type (single_site_location, region_location, cross_region_location). Note: The afm_cos_config can contain up to 5 entries. For more
information, see Endpoints and storage locations. |
No | [{afm_fileset = "afm_fileset" mode = "iw" cos_instance = "" bucket_name = "" bucket_region = "us-south" cos_service_cred_key = "" bucket_storage_class = "smart" bucket_type = "region_location"}] |
dns_instance_id |
Specify the ID of an existing IBM Cloud DNS service instance. When provided, domain names are created within the specified instance. If set to null, a new DNS service instance is created, and the required DNS zones are associated with it. | No | Null |
dns_custom_resolver_id |
Specify the ID of an existing IBM Cloud DNS custom resolver to avoid creating a new one. If set to null, a new custom resolver will be created and associated with the VPC. Note: A VPC can be associated with only one custom resolver. When using an existing VPC, if a custom resolver is already associated and this ID is not provided, the deployment will fail. | No | Null |
dns_domain_names |
DNS domain names are user-friendly addresses that map to systems within a network, making them easier to identify and access. Provide the DNS domain names for IBM Cloud HPC components: compute, storage, protocol, client, GKLM, and PPNLB. These domains will be assigned to the respective nodes that are part of the scale cluster. | No | {compute = "comp.com" storage = "strg.com" protocol = "ces.com" client = "clnt.com" gklm = "gklm.com" ppnlb = "strgscale.private"} |
enable_cos_integration |
Set to true to create an extra cos bucket to integrate with scale cluster deployment. | No | True |
cos_instance_name |
Provide the name of the existing COS instance where the logs for the enabled functionalities will be stored. | No | Null |
enable_vpc_flow_logs |
This flag determines whether VPC flow logs are enabled. When set to true, a flow log collector will be created to capture and monitor network traffic data within the VPC. Enabling flow logs provides valuable insights for troubleshooting, performance monitoring, and security auditing by recording information about the traffic passing through your VPC. Consider enabling this feature to enhance visibility and maintain robust network management practices. | No | True |
override |
Override default values with custom JSON template. This uses the file override.json to allow users to create a fully customized environment. |
No | False |
override_json_string |
Override default values with a JSON object. Any JSON other than an empty string overrides other configuration changes. | No | Null |
enable_ldap |
Set this option to true to enable LDAP for IBM Storage Scale, with the default value set to false. | No | False |
ldap_basedns |
The dns domain name is used for configuring the LDAP server. If an LDAP server is already in existence, ensure to provide the associated DNS domain name. | No | "ldapscale.com" |
ldap_server |
Provide the IP address for the existing LDAP server. If no address is given, a new LDAP server will be created. | No | Null |
ldap_server_cert |
Provide the existing LDAP server certificate. This value is required if the ldap_server variable is not set to null. If the certificate is not provided or is invalid, the LDAP configuration may fail. For more information on
how to create or obtain the certificate, see existing LDAP server certificate. |
No | Null |
ldap_admin_password |
The LDAP admin password must be 8 to 20 characters long and include at least two alphabetic characters (with one uppercase and one lowercase), one number, and one special character from the set (!@#$%^&*()_+=-). The password must not contain the username or any spaces. [This value is ignored for an existing LDAP server]. | Yes | Null |
ldap_user_name |
Custom LDAP User for performing cluster operations. Note: Username should be between 4 to 32 characters, (any combination of lowercase and uppercase letters).[This value is ignored for an existing LDAP server]. | No | "" |
ldap_user_password |
The LDAP user password must be 8 to 20 characters long and include at least two alphabetic characters (with one uppercase and one lowercase), one numeric digit, and at least one special character from the set (!@#$%^&*()_+=-). Spaces are not allowed. The password must not contain the username for enhanced security. [This value is ignored for an existing LDAP server]. | Yes | "" |
ldap_instance |
Specify the list of virtual server instances to be provisioned as ldap nodes in the cluster. Each object in the list defines the instance profile (machine type), the count (number of instances), the image (OS image to use). This configuration allows you to customize the server for setting up ldap server. The profile must match a valid IBM Cloud VPC Gen2 instance profile format. For more information, see Instance Profiles. | No | [{profile = "cx2-2x4" image = "ibm-ubuntu-22-04-5-minimal-amd64-5"}] |
scale_encryption_enabled |
Encryption ensures that data stored in the filesystem is protected from unauthorized access and secures sensitive information at rest. To enable the encryption for the filesystem. Select true or false. | No | False |
scale_encryption_type |
To enable filesystem encryption, specify either 'key_protect' or 'gklm'. If neither is specified, the default value will be 'null' and encryption is disabled. | No | Null |
gklm_instances |
Specify the list of virtual server instances to be provisioned as GKLM (Guardium Key Lifecycle Manager) nodes in the cluster. Each object in the list includes the instance profile (machine type), the count (number of instances), and the image (OS image to use). This configuration allows you to manage and securely store encryption keys used across the cluster components. The profile must match a valid IBM Cloud VPC Gen2 instance profile format. A minimum of 2 and maximum of 5 gklm nodes are supported. For more information, see Instance Profiles. | No | [{profile = "bx2-2x8" count = 2 image = "hpcc-scale-gklm4202-v2-5-3"}] |
scale_encryption_admin_password |
Specifies the administrator password for GKLM-based encryption. This is required when encryption is enabled for IBM Spectrum Scale (GPFS) and the encryption type is set to 'gklm'. The password is used to authenticate administrative access to the Guardium Key Lifecycle Manager (GKLM) for managing encryption keys. Ensure the password meets your organization's security standards. | Yes | Null |
key_protect_instance_id |
Provide the ID of an existing IBM Key Protect instance to be used for filesystem encryption in IBM Storage Scale. If this value is provided, the automation will use the existing Key Protect instance and create a new encryption key within it. If not provided, a new Key Protect instance will be created automatically during deployment. | No | Null |
storage_type |
Select the Storage Scale file system deployment method. Note: The Storage Scale VSI and evaluation type deploys the Storage Scale file system on virtual server instances, and the persistent type deploys the Storage Scale file system on bare metal servers. | No | "scratch" |
observability_atracker_enable |
Activity Tracker Event Routing to configure how to route auditing events. While multiple Activity Tracker instances can be created, only one tracker is needed to capture all events. Creating additional trackers is unnecessary if an existing Activity Tracker is already integrated with a COS bucket. In such cases, set the value to false, as all events can be monitored and accessed through the existing Activity Tracker. | No | False |
observability_atracker_target_type |
All the events will be stored in either COS bucket or Cloud Logs on the basis of user input, so customers can retrieve or ingest them in their system. | No | "cloudlogs" |
sccwp_service_plan |
Specify the plan type for the Security and Compliance Center (SCC) Workload Protection instance. Valid values are free-trial and graduated-tier only. | No | "free-trial" |
sccwp_enable |
Set this flag to true to create an instance of IBM Security and Compliance Center (SCC) Workload Protection. When enabled, it provides tools to discover and prioritize vulnerabilities, monitor for security threats, and enforce configuration, permission, and compliance policies across the full lifecycle of your workloads. To view the data on the dashboard, enable the cspm to create the app configuration and required trusted profile policies. For more information, see CSPM. | No | False |
cspm_enabled |
Cloud Security Posture Management (CSPM) is a set of tools and practices that continuously monitor and secure cloud infrastructure. When enabled, it creates a trusted profile with viewer access to the App Configuration and Enterprise services for the SCC Workload Protection instance. Make sure the required IAM permissions are in place, as missing permissions will cause deployment to fail. If CSPM is disabled, dashboard data will not be available. For more information, see CSPM. | No | True |
app_config_plan |
Specify the IBM service pricing plan for the app configuration. Allowed values are 'basic', 'standardv2', 'enterprise'. | No | "basic" |
skip_flowlogs_s2s_auth_policy |
Skip auth policy between flow logs service and COS instance, set to true if this policy is already in place on account. | No | False |
existing_bastion_instance_name |
Provide the name of the bastion instance. If none given then new bastion will be created. | No | Null |
existing_bastion_instance_public_ip |
Provide the public ip address of the bastion instance to establish the remote connection. | No | Null |
existing_bastion_security_group_id |
Specify the security group ID for the bastion server. This ID will be added as an allowlist rule on the HPC cluster nodes to facilitate secure SSH connections through the bastion node. By restricting access through a bastion server, this setup enhances security by controlling and monitoring entry points into the cluster environment. Ensure that the specified security group is correctly configured to permit only authorized traffic for secure and efficient management of cluster resources. | No | Null |
existing_bastion_ssh_private_key |
Provide the private SSH key (named id_rsa) used during the creation and configuration of the bastion server to securely authenticate and connect to the bastion server. This allows access to internal network resources from a secure entry point. Note: The corresponding public SSH key (named id_rsa.pub) must already be available in the ~/.ssh/authorized_keys file on the bastion host to establish authentication. | No | Null |
bms_boot_drive_encryption |
Enable or disable encryption for the boot drive of bare metal servers. When set to true, the boot drive will be encrypted to enhance data security, protecting the operating system and any sensitive information stored on the root volume. This is especially recommended for workloads with strict compliance or security requirements. Set to false to disable boot drive encryption. | No | False |
enable_sg_validation |
Enable or disable security group validation. Security group validation ensures that the specified security groups are properly assigned. | No | true |
login_security_group_name |
Provide the existing security group name to provision the bastion node. If set to null, the solution will automatically create the necessary security group and rules. If you choose to use an existing security group, ensure it has the appropriate rules configured for the bastion node to function properly. | No | Null |
storage_security_group_name |
Provide the security group name to provision the storage nodes. If set to null, the solution will automatically create the necessary security group and rules. If you choose to use an existing security group, ensure it has the appropriate rules configured for the storage nodes to function properly. When using existing security groups, you must provide the corresponding group names for all other associated components as well. | No | Null |
compute_security_group_name |
Provide the security group name to provision the compute nodes. If set to null, the solution will automatically create the necessary security group and rules. If you choose to use an existing security group, ensure it has the appropriate rules configured for the storage nodes to function properly. When using existing security groups, you must provide the corresponding group names for all other associated components as well. | No | Null |
client_security_group_name |
Provide the security group name to provision the client nodes. If set to null, the solution will automatically create the necessary security group and rules. If you choose to use an existing security group, ensure it has the appropriate rules configured for the storage nodes to function properly. When using existing security groups, you must provide the corresponding group names for all other associated components as well. | No | Null |
gklm_security_group_name |
Provide the security group name to provision the gklm nodes. If set to null, the solution will automatically create the necessary security group and rules. If you choose to use an existing security group, ensure it has the appropriate rules configured for the storage nodes to function properly. When using existing security groups, you must provide the corresponding group names for all other associated components as well. | No | Null |
ldap_security_group_name |
Provide the security group name to provision the ldap nodes. If set to null, the solution will automatically create the necessary security group and rules. If you choose to use an existing security group, ensure it has the appropriate rules configured for the storage nodes to function properly. When using existing security groups, you must provide the corresponding group names for all other associated components as well. | No | Null |
login_subnet_id |
Provide ID of an existing subnet to be used for provisioning bastion/deployer node. This is required only when deploying into an existing VPC (i.e., when a value is provided for vpc_name). When specifying an existing subnet,
ensure that a public gateway is attached to the subnet to enable outbound internet access if required. Additionally, if this subnet ID is provided, you must also provide subnet IDs for all other applicable components (e.g., storage ,
compute, client, protocol, gklm) to maintain consistency across the deployment. |
No | Null |
compute_subnet_id |
Provide ID of an existing subnet to be used for provisioning compute nodes. This is required only when deploying into an existing VPC (i.e., when a value is provided for vpc_name). When specifying an existing subnet, ensure
that a public gateway is attached to the subnet to enable outbound internet access if required. Additionally, if this subnet ID is provided, you must also provide subnet IDs for all other applicable components (e.g., storage , protocol,
client, login, gklm) to maintain consistency across the deployment. |
No | Null |
storage_subnet_id |
Provide ID of an existing subnet to be used for storage nodes. This is required only when deploying into an existing VPC (i.e., when a value is provided for vpc_name). When specifying an existing subnet, ensure that a public
gateway is attached to the subnet to enable outbound internet access if required. Additionally, if this subnet ID is provided, you must also provide subnet IDs for all other applicable components (e.g., compute , protocol, client, login,
gklm) to maintain consistency across the deployment. |
No | Null |
protocol_subnet_id |
Provide ID of an existing subnet to be used for protocol nodes. This is required only when deploying into an existing VPC (i.e., when a value is provided for vpc_name). When specifying an existing subnet, ensure that a public
gateway is attached to the subnet to enable outbound internet access if required. Additionally, if this subnet ID is provided, you must also provide subnet IDs for all other applicable components (e.g., storage , compute, client, login,
gklm) to maintain consistency across the deployment. |
No | Null |
client_subnet_id |
Provide ID of an existing subnet to be used for client nodes. This is required only when deploying into an existing VPC (i.e., when a value is provided for vpc_name). When specifying an existing subnet, ensure that a public
gateway is attached to the subnet to enable outbound internet access if required. Additionally, if this subnet ID is provided, you must also provide subnet IDs for all other applicable components (e.g., storage , compute, protocol, login,
gklm) to maintain consistency across the deployment. |
No | Null |
tie_breaker_baremetal_server_profile |
Specify the bare metal server profile type name to be used for creating the bare metal Tie breaker node. If no value is provided, the storage bare metal server profile will be used as the default. For more information, see bare metal server profiles and Tie Breaker Node. | No | Null |
scale_management_vsi_profile |
The virtual server instance profile type name to be used to create the Management node. For more information, see Instance Profiles. | No | "bx2-8x32" |
enable_private_path_nlb |
When set to true, provisions a private path Network Load Balancer that enables CES (NFS) storage access for the cluster. The private path integrates with the Scale NFS nodes to provide a secure, high-performance method of delivering file storage to clients within the same VPC, ensuring direct and efficient access to the CES storage nodes. | No | false |
protocol_instance_eth1_mtu |
Specifies the MTU value for the protocol instance on eth1. When Private Path NLB (PPNLB) is enabled, the MTU must be set within the supported range of 1500 to 8500; values above 8500 will cause cluster mount operations to fail. When PPNLB is disabled, the MTU can use the default value of 9000. | No | 9000 |