Dell Technologies – Resources

V1.9.0: powerflex_cluster resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_cluster (Resource)

This terraform resource is used to deploy the PowerFlex Cluster. We can Create and Delete the PowerFlex Cluster using this resource. We can also Import an existing Cluster of the PowerFlex.

Please consider the following points before using cluster resource.

For PowerFlex 4.x, the PowerFlex Manager must be installed as a prerequisite. The required packages should be uploaded to the PowerFlex Manager.
For PowerFlex 3.x, a Gateway server is a prerequisite. The required packages should be uploaded to the gateway. The Package resource can be used for uploading packages to the gateway.
Support is provided for creating, importing, and deleting operations for this resource.
In multi-node cluster deployments, when some of the component installations fail, the partial deployment will not be rolled back.
If you’ve separately installed any SDR, SDS, or SDC and connected it to the cluster and if you face any security certificate issues during the destroy process, you’ll have to manually accept the security certificate to resolve them.
During the destroy process, the entire cluster will be destroyed, not just specific individual resources. After destroy need to follow cleanup process.
ips attribute is used in minimal csv configuration whereas mdm_ips attribute is used in complete csv configuration.
For PowerFlex 4.x, there’s no need to mention allow_non_secure_communication_with_lia, allow_non_secure_communication_with_mdm, and disable_non_mgmt_components_auth. And, Rfcache is not supported.
To follow the installation process, you can refer to the Deployment Guide 3.x & Deployment Guide 4.x
NVMe over TCP is supported in PowerFlex 4.0 and later versions, therefore SDT deployment is not supported in PowerFlex 3.x.

Example Usage

/*
Copyright (c) 2023-2026 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Command to run this tf file : terraform init && terraform plan && terraform apply.
# Create, Read, Delete and Import operations are supported for this resource.

# Example for deploying cluster. After successful execution, 3 node MDM cluster will be deployed with 3 SDCs and 2 SDS.
resource "powerflex_package" "upload-test" {
  file_path = ["/root/powerflex_packages/PowerFlex_3.6.700.103_RHEL_OEL7/EMC-ScaleIO-lia-3.6-700.103.el7.x86_64.rpm",
    "/root/powerflex_packages/PowerFlex_3.6.700.103_RHEL_OEL7/EMC-ScaleIO-mdm-3.6-700.103.el7.x86_64.rpm",
    "/root/powerflex_packages/PowerFlex_3.6.700.103_RHEL_OEL7/EMC-ScaleIO-sds-3.6-700.103.el7.x86_64.rpm",
    "/root/powerflex_packages/PowerFlex_3.6.700.103_RHEL_OEL7/EMC-ScaleIO-sdc-3.6-700.103.el7.x86_64.rpm",
    "/root/powerflex_packages/PowerFlex_3.6.700.103_RHEL_OEL7/EMC-ScaleIO-sdr-3.6-700.103.el7.x86_64.rpm",
  "/root/powerflex_packages/PowerFlex_3.6.700.103_RHEL_OEL7/EMC-ScaleIO-sdt-3.6-700.103.el7.x86_64.rpm"]
}

resource "powerflex_cluster" "test" {

  depends_on = [powerflex_package.upload-test]

  # Security Related Field
  mdm_password = "Password"
  lia_password = "Password"

  # Advance Security Configuration
  allow_non_secure_communication_with_lia = false
  allow_non_secure_communication_with_mdm = false
  disable_non_mgmt_components_auth        = false

  # Cluster Configuration related fields 
  cluster = [
    {
      # MDM Configuration Fields 
      ips                  = "10.10.10.1",
      username             = "root",
      password             = "Password",
      operating_system     = "linux",
      is_mdm_or_tb         = "primary",
      mdm_ips              = "10.10.10.1",
      mdm_mgmt_ip          = "10.10.10.1",
      mdm_name             = "MDM_1",
      perf_profile_for_mdm = "HighPerformance",
      virtual_ips          = "10.30.30.1",
      virtual_ip_nics      = "ens192",

      # SDS Configuration Fields
      is_sds      = "yes",
      sds_name    = "sds1",
      sds_all_ips = "10.20.20.3", # conflict with sds_to_sds_only_ips,sds_to_sdc_only_ips
      # sds_to_sdc_only_ips      = "10.20.20.2", 
      # sds_to_sds_only_ips      = "10.20.20.1",
      fault_set                = "fs1",
      protection_domain        = "domain_1"
      sds_storage_device_list  = "/dev/sdb"
      sds_storage_device_names = "device1"
      storage_pool_list        = "pool1"
      perf_profile_for_sds     = "HighPerformance"

      # SDC Configuration Fields
      is_sdc               = "yes",
      sdc_name             = "sdc1",
      perf_profile_for_sdc = "HighPerformance",

      # Rfcache Configuration Fields
      is_rfcache               = "No",
      rf_cache_ssd_device_list = "/dev/sdd"

      # SDR Configuration Fields
      is_sdr   = "Yes",
      sdr_name = "SDR_1"
      sdr_port = "2000"
      # sdr_application_ips  = "10.20.30.1"
      # sdr_storage_ips      = "10.20.30.2"
      # sdr_external_ips     = "10.20.30.3" 
      sdr_all_ips          = "10.10.20.1" # conflict with sdr_application_ips, sdr_storage_ips, sdr_external_ips
      perf_profile_for_sdr = "Compact"

      # SDT Configuration Fields
      is_sdt      = "Yes"
      sdt_name    = "SDT_1"
      sdt_all_ips = "10.20.40.1"
    },
    {
      ips                     = "10.10.10.2",
      username                = "root",
      password                = "Password",
      operating_system        = "linux",
      is_mdm_or_tb            = "Secondary",
      protection_domain       = "domain_1"
      sds_storage_device_list = "/dev/sdb"
      storage_pool_list       = "pool1"
      is_sds                  = "yes",
      sds_name                = "sds2",
      is_sdc                  = "yes",
      sdc_name                = "sdc2",
      perf_profile_for_sdc    = "compact",
      is_rfcache              = "No",
      is_sdr                  = "No",
      is_sdt                  = "Yes"
      sdt_name                = "SDT_2"
      sdt_all_ips             = "10.20.40.2"
    },
    {
      ips                  = "10.10.10.3",
      username             = "root",
      password             = "Password",
      operating_system     = "linux",
      is_mdm_or_tb         = "TB",
      is_sds               = "No",
      is_sdc               = "yes",
      sdc_name             = "sdc3",
      perf_profile_for_sdc = "compact",
      is_rfcache           = "No",
      is_sdr               = "No",
      is_sdt               = "No"
    },
  ]
  # Storage Pool Configuration Fields
  storage_pools = [
    {
      media_type                              = "HDD"
      protection_domain                       = "domain_1"
      storage_pool                            = "pool1"
      replication_journal_capacity_percentage = "50"
    }
  ]
}

After the execution of above resource block, Cluster would have been created on the PowerFlex array. For more information, please check the terraform state file.

Schema

Required

cluster (Attributes List) Cluster Installation Details (see below for nested schema)
lia_password (String, Sensitive) Lia Password
mdm_password (String, Sensitive) MDM Password

Optional

allow_non_secure_communication_with_lia (Boolean) Allow Non Secure Communication With lia
allow_non_secure_communication_with_mdm (Boolean) Allow Non Secure Communication With MDM
disable_non_mgmt_components_auth (Boolean) Disable Non Mgmt Components Auth
id (String) ID
storage_pools (Attributes List) Storage Pool Details (see below for nested schema)

Read-Only

mdm_list (Attributes Set) Cluster MDM Details (see below for nested schema)
protection_domains (Attributes List) Cluster Protection Domain Details (see below for nested schema)
sdc_list (Attributes Set) Cluster SDC Details (see below for nested schema)
sdr_list (Attributes Set) Cluster SDR Details (see below for nested schema)
sds_list (Attributes Set) Cluster SDS Details (see below for nested schema)
sdt_list (Attributes Set) Cluster SDT Details (see below for nested schema)

Nested Schema for `cluster`

Required:

is_mdm_or_tb (String) Is Mdm Or Tb
operating_system (String) Operating System

Optional:

fault_set (String) Fault Set
ips (String) Use this field to assign a single IP address for all the MDM IP, MDM Mgmt IP, and SDS All IP. This option is useful when separate networks for data and management are not required.
is_rfcache (String) Is RFCache. The acceptable values are Yes and No. Default value is No.
is_sdc (String) Is Sdc. The acceptable values are Yes and No. Default value is No.
is_sdr (String) Is SDR. The acceptable values are Yes and No. Default value is No.
is_sds (String) Is Sds. The acceptable values are Yes and No. Default value is No.
is_sdt (String) Is Sdt. The acceptable values are Yes and No. Default value is No.
mdm_ips (String) MDM IP addresses used to communicate with other PowerFlex components in the storage network. This is required for all MDMs, Tiebreakers and Standbys.Leave this field blank for hosts that are not part of the MDM cluster.
mdm_mgmt_ip (String) This IP address is for the management-only network. The management ip is not required for Tiebreaker MDM, Standby Tiebreaker MDM and any host that is not an MDM.
mdm_name (String) MDMName
password (String, Sensitive) Password used to log in to the node.
perf_profile_for_mdm (String) Performance Profile For MDM
perf_profile_for_sdc (String) Performance Profile For SDC
perf_profile_for_sdr (String) Performance Profile For SDR
perf_profile_for_sds (String) Performance Profile For SDS
protection_domain (String) Protection Domain
rf_cache_ssd_device_list (String) List of SSD devices to provide RFcache acceleration for Medium Granularity data layout Storage Pools.
sdc_name (String) SDC Name
sdr_all_ips (String) SDR IP addresses to be used for communication among all nodes (including all three roles)
sdr_application_ips (String) The IP addresses through which the SDC communicates with the SDR.
sdr_external_ips (String) The IP addresses through which the SDR communicates with peer systems SDRs
sdr_name (String) SDR Name
sdr_port (String) SDR Port
sdr_storage_ips (String) The IP addresses through which the SDR communicates with the MDM for server side control communications.
sds_all_ips (String) SDS IP addresses to be used for communication among all nodes.
sds_name (String) SDS Name
sds_storage_device_list (String) Storage devices to be added to an SDS. For more than one device, use a comma separated list, with no spaces.
sds_storage_device_names (String) Sets names for devices.
sds_to_sdc_only_ips (String) SDS IP addresses to be used for communication among SDS and SDC nodes only.
sds_to_sds_only_ips (String) SDS IP addresses to be used for communication among SDS nodes. When the replication feature is used, these addresses are also used for SDS-SDR communication.
sdt_all_ips (String) SDT IP addresses used for both hosts communication and MDM communication (including both roles).
sdt_name (String) SDT Name
storage_pool_list (String) Sets Storage Pool names
username (String) The value can be either root or any non-root user name with appropriate permissions.
virtual_ip_nics (String) The NIC to which the virtual IP addresses are mapped.
virtual_ips (String) Virtual IPs

Nested Schema for `storage_pools`

Required:

media_type (String) Media Type

Optional:

compression_method (String) Compression Method
data_layout (String) Data Layout
external_acceleration (String) External Acceleration
protection_domain (String) Protection Domain
replication_journal_capacity_percentage (String) Replication Journal Capacity Percentage
storage_pool (String) Storage Pool
zero_padding (String) Zero Padding

Nested Schema for `mdm_list`

Read-Only:

id (String) ID
ip (String) MDM Node IP
mdm_ip (String) MDM IP
mgmt_ip (String) MGMTIP
mode (String) Mode
name (String) Name
role (String) Role
virtual_ip (String) Virtual IP
virtual_ip_nic (String) Virtual IPNIC

Nested Schema for `protection_domains`

Read-Only:

name (String) Name
storage_pool_list (Attributes List) Storage Pools (see below for nested schema)

Nested Schema for `protection_domains.storage_pool_list`

Read-Only:

compression_method (String) Compression Method
data_layout (String) Data Layout
external_acceleration (String) External Acceleration
media_type (String) Media Type
name (String) Name
replication_journal_capacity_percentage (Number) Replication Journal Capacity Percentage
zero_padding (String) Zero Padding

Nested Schema for `sdc_list`

Read-Only:

guid (String) GUID
id (String) ID
ip (String) SDC Node IP
name (String) Name

Nested Schema for `sdr_list`

Read-Only:

all_ips (String) All IP
application_ips (String) Application IP
external_ips (String) External IP
id (String) ID
ip (String) SDR Node IP
name (String) Name
port (Number) Port
storage_ips (String) Storage IP

Nested Schema for `sds_list`

Read-Only:

all_ips (String) All IP
devices (Attributes Set) Devices (see below for nested schema)
fault_set (String) Fault Set
id (String) ID
ip (String) SDS Node IP
name (String) Name
protection_domain_id (String) Protection Domain Name
protection_domain_name (String) Protection Domain Name
sds_only_ips (String) SDSOnly IP
sds_sdc_ips (String) SDSSDCIP

Nested Schema for `sds_list.devices`

Read-Only:

max_capacity_in_kb (Number) Max Capacity
name (String) Name
path (String) Path
storage_pool (String) Storage Pool Name

Nested Schema for `sdt_list`

Read-Only:

all_ips (String) All IP
discovery_port (Number) Discovery Port
host_only_ips (String) Host Only IP
id (String) ID
ip (String) SDT Node IP
name (String) Name
nvme_port (Number) NVMe Port
protection_domain_id (String) Protection Domain Name
protection_domain_name (String) Protection Domain Name
storage_only_ips (String) Storage Only IP
storage_port (Number) Storage Port

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2023-2026 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import existing cluster
terraform import powerflex_cluster.cluster_data "<MDM_IP>,<MDM_Password>,<LIA_Password>"

This will import the cluster instance using specified details into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_compatibility_management resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_compatibility_management (Resource)

This resource is used to set the compatibility management from the PowerFlex array.

Example Usage

/*
Copyright (c) 2024 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Command to run this tf file : terraform init && terraform plan && terraform apply.

// Resource to manage lifecycle
resource "terraform_data" "always_run" {
  input = timestamp()
}

# Example for setting compatibility management. After successful execution, device will be added to the specified storage pool
resource "powerflex_compatibility_management" "test" {
  # Required Path on your local machine to your gpg file ie(/example/path/secring.gpg)
  repository_path = "/example/path/example.gpg"

  // This will allow terraform create process to trigger each time we run terraform apply.
  lifecycle {
    replace_triggered_by = [
      terraform_data.always_run
    ]
  }
}

After the execution of above resource block, compatibility management would have been created on the PowerFlex array. For more information, please check the terraform state file.

Schema

Required

repository_path (String) Repository Path on your local machine to your compatibility gpg file ie: /example/example.gpg.

Read-Only

available_version (String) Available Version of the Compatibility Management Instance.
compatibility_data (String) Compatibility Data of the Compatibility Management Instance.
compatibility_data_bytes (String) Compatibility Data Bytes of the Compatibility Management Instance.
current_version (String) Current Version of the Compatibility Management Instance.
id (String) Unique identifier of the Compatibility Management Instance.
source (String) Source of the Compatibility Management Instance.

V1.9.0: powerflex_device resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_device (Resource)

This resource is used to manage the Device entity of PowerFlex Array. We can Create, Update and Delete the PowerFlex Devices using this resource. We can also import an existing device from PowerFlex array.

Caution: Device creation or update is not atomic. In case of partially completed create operations, terraform can mark the resource as tainted. One can manually remove the taint and try applying the configuration (after making necessary adjustments). If the taint is not removed, terraform will destroy and recreate the resource.

Note: Either storage_pool_name or storage_pool_id is required. But not both.

Note: Either sds_name or sds_id is required. But not both.

Note: If storage_pool_name is mentioned, we must specify either protection_domain_id or protection_domain_name but not both.

Example Usage

/*
Copyright (c) 2023-2026 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Command to run this tf file : terraform init && terraform plan && terraform apply.

# Example for adding device. After successful execution, device will be added to the specified storage pool
resource "powerflex_device" "test-device" {
  device_path            = "/dev/sdc"
  storage_pool_name      = "pool1"
  protection_domain_name = "domain1"
  sds_name               = "SDS_2"
  media_type             = "HDD" # HDD/SSD
}

After the execution of above resource block, device would have been created on the PowerFlex array. For more information, please check the terraform state file.

Schema

Required

device_path (String) The current path of the device. Cannot be updated.

Optional

device_capacity (Number) Capacity of the device in GB.
device_group_id (String) Device Group ID (Gen2 5.x only). Replaces storage_pool_id for Gen2 systems.
external_acceleration_type (String) External acceleration type of the device. Valid values are None, Read, Write, ReadAndWrite.
media_type (String) Media type of the device. Valid values are HDD, SSD.
name (String) The name of the device.
protection_domain_id (String) ID of the protection domain. Conflicts with protection_domain_name. Cannot be updated.
protection_domain_name (String) Name of the protection domain. Conflicts with protection_domain_id. Cannot be updated.
sds_id (String) ID of the SDS. Conflicts with sds_name. Cannot be updated. Deprecated in Gen2 5.x — use storage_node_id instead.
sds_name (String) Name of the SDS. Conflicts with sds_id. Cannot be updated. Deprecated in Gen2 5.x — use storage_node_id instead.
storage_node_id (String) Storage Node ID (Gen2 5.x only). Replaces sds_id for Gen2 systems.
storage_pool_id (String) ID of the storage pool. Conflicts with storage_pool_name. Cannot be updated.
storage_pool_name (String) Name of the storage pool. Conflicts with storage_pool_id. Cannot be updated.

Read-Only

device_capacity_in_kb (Number) Capacity of the device in KB.
device_original_path (String) Original path of the device.
device_state (String) State of the device.
id (String) The ID of the device.

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2023-2026 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import Protection Device by it's id
terraform import powerflex_device.device_data "<id>"

This will import the device instance with specified ID into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_device_action_v2 resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_device_action_v2 (Resource)

This resource is used to perform Gen2 device actions on PowerFlex systems (5.0+). Supported actions: activate, clear_error, set_capacity_limit.

Example Usage

/*
Copyright (c) 2024-2026 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied
See the License for the specific language governing permissions and
limitations under the License.
*/

# Commands to run this tf file : terraform init && terraform plan && terraform apply
# This resource performs actions on devices (Gen2 systems 5.0+)
# Supported actions: activate, clear_error, set_capacity_limit
# device_id and action are required
# capacity_limit_in_kb is required when action is set_capacity_limit

# Example: Activate a device
resource "powerflex_device_action_v2" "activate" {
  device_id = "0123456789abcdef"
  action    = "activate"
}

# Example: Clear device error
resource "powerflex_device_action_v2" "clear_error" {
  device_id = "0123456789abcdef"
  action    = "clear_error"
}

# Example: Set device capacity limit
resource "powerflex_device_action_v2" "set_capacity" {
  device_id            = "0123456789abcdef"
  action               = "set_capacity_limit"
  capacity_limit_in_kb = "10737418240" # 10TB in KB
}

output "device_action" {
  value = powerflex_device_action_v2.activate
}

Schema

Required

action (String) The action to perform. Valid values: activate, clear_error, set_capacity_limit.
device_id (String) The ID of the device to perform the action on.

Optional

capacity_limit_in_kb (String) Capacity limit in KB. Required when action is set_capacity_limit.

Read-Only

id (String) The identifier for this action resource.

V1.9.0: powerflex_device_group_v2 resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_device_group_v2 (Resource)

This resource is used to manage Device Groups on PowerFlex Gen2 systems (5.0+). Device Groups allow logical grouping of devices for management.

Example Usage

/*
Copyright (c) 2024-2026 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Commands to run this tf file : terraform init && terraform plan && terraform apply
# Create, Update, Delete is supported for this resource
# To import, check import.tf for more info
# protection_domain_id is required
# name is optional
# This resource is for PowerFlex Gen2 systems (5.0+)

# Example for creating a Device Group
resource "powerflex_device_group_v2" "create" {
  name                 = "demo-device-group-01"
  protection_domain_id = "202a046600000000"
}

output "device_group" {
  value = powerflex_device_group_v2.create
}

Schema

Required

protection_domain_id (String) The ID of the protection domain.

Optional

name (String) The name of the device group.

Read-Only

id (String) The unique identifier of the device group.
num_of_devices (Number) The number of devices in the device group.
status (String) The status of the device group.
usable_capacity_in_kb (Number) The usable capacity in KB.
used_capacity_in_kb (Number) The used capacity in KB.

V1.9.0: powerflex_fault_set resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_fault_set (Resource)

This resource is used to manage the Fault Set entity of the PowerFlex Array. We can Create, Update and Delete the fault set using this resource. We can also import an existing fault set from the PowerFlex array.

Example Usage

/*
Copyright (c) 2023-2024 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Command to run this tf file : terraform init && terraform plan && terraform apply
# Create, Update, Delete is supported for this resource
# To import , check import.sh for more info
# name and protection_domain_id is the required parameter to create or update 
# To check which attributes of the fault set can be updated, please refer Product Guide in the documentation


resource "powerflex_fault_set" "avengers-fs-create" {
  # Name of the fault set
  name = "avengers-fs-create2"

  # To create / update, protection_domain_id is required
  protection_domain_id = "202a046600000000"
}

After the execution of above resource block, fault set would have been created on the PowerFlex array. For more information, please check the terraform state file.

Schema

Required

name (String) Name of the Fault set
protection_domain_id (String) ID of the Protection Domain under which the fault set will be created. Cannot be updated.

Read-Only

id (String) ID of the Fault Set

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2023-2024 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import fault set by it's id
terraform import powerflex_fault_set.fs_import_by_id "<id>"

This will import the fault set instance with specified ID into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_firmware_repository resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_firmware_repository (Resource)

This resource is used to manage the Firmware Repository entity of the PowerFlex Array. We can Create and Update the firmware repository using this resource. As part of create operation, we can upload the compliance file and as part of update we can approve the unsigned files.We can also import an existing firmware repository from the PowerFlex array.

Example Usage

/*
Copyright (c) 2024 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Example for uploading compliance file. After successful execution, compliance file will be uploaded to the manager.
resource "powerflex_firmware_repository" "upload-test" {
  source_location = "https://10.10.10.1/artifactory/Denver/RCMs/SoftwareOnly/PowerFlex_Software_4.5.0.0_287_r1.zip"
  username        = "user"     # To be provided in case of CIFS share
  password        = "password" # To be provided in case of CIFS share
  approve         = true       # To be used to approve the unsigned file
  timeout         = 45         #controls that till what time the upload compliance will run
}

After the execution of above resource block, firmware_repository would have been created on the PowerFlex array. For more information, please check the terraform state file.

Schema

Required

source_location (String) Specfies the path from where it will download the compliance file. Cannot be updated.

Optional

approve (Boolean) Whether to approve the unsigned file or not.
password (String, Sensitive) Password is only used if specifying a CIFS share Cannot be updated.
timeout (Number) Describes the time in minutes to timeout the job.
username (String) Username is only used if specifying a CIFS share Cannot be updated.

Read-Only

default_catalog (Boolean) Whether this Firmware Repository is set to default or not.
disk_location (String) Disk location of the Firmware Repository
file_name (String) File Name
id (String) ID of the Firmware Repository
name (String) Name of the Firmware Repository

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2024 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import firmware respository by it's id
terraform import powerflex_firmware_repository.fr_import_by_id "<id>"

# After Import, username and password is not needed for approving the unsigned file in case of CIFS share. For approving the file in case of import, please refer the below config(change the value as per your use-case):
resource "powerflex_firmware_repository" "fr_import_by_id" {
  source_location = "https://10.10.10.1/artifactory/Denver/RCMs/SoftwareOnly/PowerFlex_Software_4.5.0.0_287_r1.zip"
  approve = true
  timeout = 45
}

This will import the firmware_repository instance with specified ID into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_mdm_cluster resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_mdm_cluster (Resource)

This resource can be used to manage MDM cluster on the PowerFlex array. Supports adding or removing standby MDMs, migrate from 3-node to 5-node cluster or vice-versa, changing MDM ownership, changing performance profile, and renaming MDMs.

Caution: MDM cluster creation or update is not atomic. In case of partially completed create operations, terraform can mark the resource as tainted. One can manually remove the taint and try applying the configuration (after making necessary adjustments). If the taint is not removed, terraform will destroy and recreate the resource.

Note: Use of MDM cluster resource requires the presence of the MDM cluster. The purpose of this resource is to update MDM cluster, not create or delete. Import operation is not supported for MDM cluster.

Example Usage

/*
Copyright (c) 2023-2024 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Command to run this tf file : terraform init && terraform plan && terraform apply.
# Create, Update, Read, and Delete operations are supported for this resource.
# For this resource, primary_mdm, secondary_mdm, tiebreaker_mdm and cluster_mode are mandatory parameters.
# While specifying primary_mdm, secondary_mdm and tiebreaker_mdm, id or ips is mandatory.
# For adding standby mdm, ips and role parameters are mandatory.
# To check which attributes of the MDM cluster resource can be updated, please refer Product Guide in the documentation

# Example for adding standby MDMs. Before adding standby MDMs, MDM package must be installed on VM with respective role. 
resource "powerflex_mdm_cluster" "test-mdm-cluster" {
  cluster_mode = "ThreeNodes" # ThreeNodes/FiveNodes
  primary_mdm = {
    id = "7f328d0b71711801"
  }
  secondary_mdm = [{
    id = "10912d8a5d412800"
  }]
  tiebreaker_mdm = [{
    id = "0e4f0a2f5978ae02"
  }]
  standby_mdm = [
    {
      ips  = ["10.xxx.xx.xxx"]
      role = "Manager" # Manager/TieBreaker
    },
    {
      ips  = ["10.yyy.yy.yyy"]
      role = "TieBreaker"
    },
  ]
}

# Example for changing MDM ownership. In this case, the id of the primary and secondary MDM will be swapped.
resource "powerflex_mdm_cluster" "test-mdm-cluster" {
  cluster_mode = "ThreeNodes"
  primary_mdm = {
    id = "10912d8a5d412800"
  }
  secondary_mdm = [{
    id = "7f328d0b71711801"
  }]
  tiebreaker_mdm = [{
    id = "0e4f0a2f5978ae02"
  }]
  standby_mdm = [
    {
      ips  = ["10.xxx.xx.xxx"]
      role = "Manager"
    },
    {
      ips  = ["10.yyy.yy.yyy"]
      role = "TieBreaker"
    },
  ]
}

# Example for switching cluster mode to 5 nodes from 3 nodes. The cluster mode will be FiveNodes. Previously added standby MDMs will be added as Secondary/TieBreaker MDM.
resource "powerflex_mdm_cluster" "test-mdm-cluster" {
  cluster_mode = "FiveNodes"
  primary_mdm = {
    id = "10912d8a5d412800"
  }
  secondary_mdm = [
    {
      id = "7f328d0b71711801"
    },
    {
      ips  = ["10.xxx.xx.xxx"]
      role = "Manager"
    },
  ]
  tiebreaker_mdm = [
    {
      id = "0e4f0a2f5978ae02"
    },
    {
      ips  = ["10.yyy.yy.yyy"]
      role = "TieBreaker"
    },
  ]
  standby_mdm = [
  ]
}

# Example for switching cluster mode to 3 nodes from 5 nodes. The cluster mode will be ThreeNodes. One of the active Secondary/TieBreaker MDM will be moved to standby MDMs.
resource "powerflex_mdm_cluster" "test-mdm-cluster" {
  cluster_mode = "ThreeNodes"
  primary_mdm = {
    id = "10912d8a5d412800"
  }
  secondary_mdm = [
    {
      id = "7f328d0b71711801"
    }
  ]
  tiebreaker_mdm = [
    {
      id = "0e4f0a2f5978ae02"
    }
  ]
  standby_mdm = [
    {
      ips  = ["10.xxx.xx.xxx"]
      role = "Manager"
    },
    {
      ips  = ["10.yyy.yy.yyy"]
      role = "TieBreaker"
    },
  ]
}

# Example for removing standby MDMs. In this case, standby_mdm will be empty list.
resource "powerflex_mdm_cluster" "test-mdm-cluster" {
  cluster_mode = "ThreeNodes"
  primary_mdm = {
    id = "10912d8a5d412800"
  }
  secondary_mdm = [
    {
      id = "7f328d0b71711801"
    }
  ]
  tiebreaker_mdm = [
    {
      id = "0e4f0a2f5978ae02"
    }
  ]
  standby_mdm = []
}

After the execution of the above resource block, the MDM cluster would become a 3-node cluster. For more information, please check the state file.

Schema

Required

cluster_mode (String) Mode of the MDM cluster. Accepted values are ThreeNodes and FiveNodes.
primary_mdm (Attributes) Primary MDM details. (see below for nested schema)
secondary_mdm (Attributes List) Secondary MDM details. (see below for nested schema)
tiebreaker_mdm (Attributes List) TieBreaker MDM details. (see below for nested schema)

Optional

performance_profile (String) Performance profile of the MDM cluster. Accepted values are Compact and HighPerformance.
standby_mdm (Attributes List) StandBy MDM details. StandBy MDM can be added/removed/promoted to manager/tiebreaker role. (see below for nested schema)

Read-Only

id (String) Unique identifier of the MDM cluster.

Nested Schema for `primary_mdm`

Optional:

id (String) ID of the primary MDM.
ips (Set of String) The Ips of the primary MDM.
name (String) Name of the the primary MDM.

Read-Only:

management_ips (Set of String) The management ips of the primary MDM.
port (Number) Port of the primary MDM.

Nested Schema for `secondary_mdm`

Optional:

id (String) ID of the secondary MDM.
ips (Set of String) The Ips of the secondary MDM.
name (String) Name of the the secondary MDM.

Read-Only:

management_ips (Set of String) The management ips of the secondary MDM.
port (Number) Port of the secondary MDM.

Nested Schema for `tiebreaker_mdm`

Optional:

id (String) ID of the tiebreaker MDM.
ips (Set of String) The Ips of the tiebreaker MDM.
name (String) Name of the the tiebreaker MDM.

Read-Only:

management_ips (Set of String) The management ips of the tiebreaker MDM.
port (Number) Port of the tiebreaker MDM.

Nested Schema for `standby_mdm`

Required:

ips (Set of String) The Ips of the standby MDM. Cannot be updated.
role (String) Role of the standby mdm. Accepted values are Manager and TieBreaker. Cannot be updated.

Optional:

allow_asymmetric_ips (Boolean) Allow the added MDM to have a different number of IPs from the primary MDM. Cannot be updated.
management_ips (Set of String) The management ips of the standby MDM. Cannot be updated.
name (String) Name of the the standby MDM.
port (Number) Port of the standby MDM. Cannot be updated.

Read-Only:

id (String) ID of the standby MDM.

V1.9.0: powerflex_nvme_host resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_nvme_host (Resource)

This resource is used to manage NVMe host from the PowerFlex array. We can Create, Update and Delete the PowerFlex NVMe host using this resource. We can also import an existing NVMe host from PowerFlex array.

Note:

NVMe over TCP is supported in PowerFlex 4.0 and later versions, therefore this resource is not supported in PowerFlex 3.x.

Due to certain limitations, updating the NVMe host in PowerFlex versions earlier than 4.6 is not supported

Example Usage

/*
Copyright (c) 2024 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Command to run this tf file : terraform init && terraform plan && terraform apply.
# Create, Update, Read, and Delete operations are supported for this resource.
# To import , check import.sh for more info
# nqn is the required parameter to create
# To check which attributes can be updated, please refer Product Guide in the documentation
# Please note that 
# 1. NVMe over TCP is supported in PowerFlex 4.0 and later versions, therefore this resource is not supported in PowerFlex 3.x.
# 2. Due to certain limitations, updating the NVMe host in PowerFlex versions earlier than 4.6 is not supported

# Example for adding NVMe host.
resource "powerflex_nvme_host" "test-nvme-host" {
  name              = "nvme_host_name"
  nqn               = "nqn.2014-08.org.nvmexpress:uuid:a10e4d56-a2c0-4cab-9a0a-9a7a4ebb8c0e"
  max_num_paths     = 4
  max_num_sys_ports = 10
}

After the execution of above resource block, NVMe host would have been created on the PowerFlex array. For more information, please check the terraform state file.

Schema

Required

nqn (String) NQN of the NVMe host. This attribute must be set during creation and cannot be modified afterwards.

Optional

max_num_paths (Number) Number of Paths Per Volume.
max_num_sys_ports (Number) Number of System Ports per Protection Domain.
name (String) Name of the NVMe host

Read-Only

id (String) ID of the NVMe host
system_id (String) The ID of the system.

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2023-2024 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import NVMe host by its id
terraform import powerflex_nvme_host.nvme_host_import_by_id "<id>"

This will import the NVMe host instance with specified ID into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_nvme_target resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_nvme_target (Resource)

This resource is used to manage NVMe target from the PowerFlex array. We can Create, Update and Delete the PowerFlex NVMe target using this resource. We can also import an existing NVMe target from PowerFlex array.
Note: Either protection_domain_id or protection_domain_name must be specified.

Caution: NVMe target creation or update is not atomic. In case of partially completed create operations, terraform can mark the resource as tainted. One can manually remove the taint and try applying the configuration (after making necessary adjustments). If the taint is not removed, terraform will destroy and recreate the resource.

Note:

Either protection_domain_name and protection_domain_id is required. But not both.

NVMe over TCP is supported in PowerFlex 4.0 and later versions, therefore this resource is not supported in PowerFlex 3.x.

To avoid potential issues, it is recommended to operate NVMe targets using the default ports.

Example Usage

/*
Copyright (c) 2024 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Command to run this tf file : terraform init && terraform plan && terraform apply.
# Create, Update, Read, and Delete operations are supported for this resource.
# To import , check import.sh for more info.
# name and ip_list attributes are required, and either protection_domain_name or protection_domain_id must be specified.
# To check which attributes can be updated, please refer Product Guide in the documentation
# Please note that NVMe over TCP is supported in PowerFlex 4.0 and later versions, therefore this resource is not supported in PowerFlex 3.x.
# To avoid potential issues, it is recommended to operate NVMe targets using the default ports.

# Example for adding NVMe target.
resource "powerflex_nvme_target" "test-nvme-target" {
  name                   = "nvme_target_name"
  protection_domain_name = "demo-pd"
  ip_list = [
    {
      ip   = "10.10.10.13"
      role = "StorageAndHost" #StorageAndHost, StorageOnly, HostOnly
    },
    {
      ip   = "10.10.10.14"
      role = "StorageAndHost" #StorageAndHost, StorageOnly, HostOnly
    }
  ]
}

After the execution of above resource block, NVMe target would have been created on the PowerFlex array. For more information, please check the terraform state file.

Schema

Required

ip_list (Attributes Set) List of IPs associated with the NVMe target. (see below for nested schema)
name (String) Name of the NVMe target

Optional

discovery_port (Number) The discovery port of the NVMe target (default: 8009).
maintenance_state (String) The maintenance state of the NVMe target. Active to trigger enter maintenance mode; Inactive to exit maintenance mode.
nvme_port (Number) The NVMe port of the NVMe target (default: 4420).
protection_domain_id (String) ID of the Protection Domain under which the NVMe target will be created. Conflicts with ‘protection_domain_name’. Cannot be updated.Note: Either protection_domain_id or protection_domain_name must be specified.
protection_domain_name (String) Name of the Protection Domain under which the NVMe target will be created. Conflicts with ‘protection_domain_id’. Cannot be updated.Note: Either protection_domain_id or protection_domain_name must be specified.
storage_port (Number) The storage port of the NVMe target (default: 12200).

Read-Only

authentication_error (String) The authentication error of the NVMe target.
fault_set_id (String) The fault set ID of the NVMe target.
id (String) ID of the NVMe target
mdm_connection_state (String) The MDM connection state of the NVMe target.
membership_state (String) The membership state of the NVMe target.
sdt_state (String) The state of the NVMe target.
software_version_info (String) The software version information of the NVMe target.
system_id (String) The ID of the system.

Nested Schema for `ip_list`

Required:

ip (String) NVMe Target IP.
role (String) NVMe Target IP role.

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2023-2024 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import NVMe target by its id
terraform import powerflex_nvme_target.nvme_target_import_by_id "<id>"

This will import the NVMe target instance with specified ID into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_os_repository resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_os_repository (Resource)

This resource is used to manage the OS Repository entity of the PowerFlex Array. We can Create ,Read and Delete the os image repository using this resource.

Example Usage

/*
Copyright (c) 2024-2026 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Command to run this tf file : terraform plan && terraform apply.

// Resource to manage lifecycle
resource "terraform_data" "always_run" {
  input = timestamp()
}

# Example for creating OS repository. After successful execution, OS Repository will be created.
resource "powerflex_os_repository" "test" {
  # Required Fields

  # Name of the OS repository
  name = "TestOsRepo"
  # Source path of the OS image
  source_path = "https://pathtoimage.iso"
  # Supported image types are redhat7, vmware_esxi, sles, windows2016, windows2019
  image_type = "vmware_esxi"

  // This will allow terraform create process to trigger each time we run terraform apply.
  lifecycle {
    replace_triggered_by = [
      terraform_data.always_run
    ]
  }
}

After the execution of above resource block, OS Repository would have been created. For more information, please check the terraform state file.

Schema

Required

image_type (String) Type of the OS image. Supported types are redhat7, vmware_esxi, sles, windows2016, windows2019
name (String) Name of the OS repository
source_path (String) Source path of the OS image

Optional

password (String, Sensitive) Password of the OS repository
repo_type (String) Type of the OS repository. Default is ISO
timeout (Number) Describes the time in minutes to timeout the job.
username (String) Username of the OS repository

Read-Only

base_url (String) Base URL of the OS repository
created_by (String) User who created the OS repository
created_date (String) Date of creation of the OS Repository
from_web (Boolean) Whether the OS repository is from the web or not
id (String) ID of the OS Repository
in_use (Boolean) Whether the OS repository is in use or not
razor_name (String) Name of the Razor
rcm_path (String) Path of the RCM
state (String) State of the OS repository

V1.9.0: powerflex_package resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_package (Resource)

This resource can be used to upload packages on a PowerFlex Gateway. We can add or remove packages from PowerFlex Gateway. Import functionality is not supported.

Note: This resource can be used to upload packages to a PowerFlex Manager (4.x) or Gateway Server (3.x). We can add or remove packages from PowerFlex Manager or Gateway. Import functionality is not supported.

Example Usage

/*
Copyright (c) 2023-2024 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Example for uploading packages. After successful execution, packages will be uploaded to the gateway.
resource "powerflex_package" "upload-test" {
  file_path = ["/root/powerflex_packages/PowerFlex_3.6.700.103_RHEL_OEL7/EMC-ScaleIO-lia-3.6-700.103.el7.x86_64.rpm",
    "/root/powerflex_packages/PowerFlex_3.6.700.103_RHEL_OEL7/EMC-ScaleIO-mdm-3.6-700.103.el7.x86_64.rpm",
    "/root/powerflex_packages/PowerFlex_3.6.700.103_RHEL_OEL7/EMC-ScaleIO-sds-3.6-700.103.el7.x86_64.rpm",
    "/root/powerflex_packages/PowerFlex_3.6.700.103_RHEL_OEL7/EMC-ScaleIO-sdc-3.6-700.103.el7.x86_64.rpm",
    "/root/powerflex_packages/PowerFlex_3.6.700.103_RHEL_OEL7/EMC-ScaleIO-sdr-3.6-700.103.el7.x86_64.rpm",
  "/root/powerflex_packages/PowerFlex_3.6.700.103_RHEL_OEL7/EMC-ScaleIO-sdt-3.6-700.103.el7.x86_64.rpm"]
}

After the execution of above resource block, package would have been uploaded on the PowerFlex Gateway. For more information, please check the terraform state file.

Schema

Required

file_path (List of String) The list of path of packages

Read-Only

id (String) The ID of the package.
package_details (Attributes Set) Uploaded Packages details. (see below for nested schema)

Nested Schema for `package_details`

Read-Only:

file_name (String) The Name of package.
label (String) Uploaded Package Minor Version with OS Combination.
latest (Boolean) Package Version is latest or not
linux_flavour (String) Type of Linux OS
operating_system (String) Supported OS.
sio_patch_number (Number) Package Patch Number.
size (Number) Size of Package.
type (String) Type of Package. Like. MDM, LIA, SDS, SDC, etc.
version (String) Uploaded Package Version.

V1.9.0: powerflex_peer_system resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_peer_system (Resource)

This resource is used to manage the Peer System entity of the PowerFlex Array. This feature is only supported for PowerFlex 4.5 and above. We can Create, Update and Delete the PowerFlex Peer Systems using this resource. We can also Import an existing Peer Systems from the PowerFlex array. Peer system refers to the setup where multiple MDM nodes work together as peers to provide redundancy and high availability. This means that if one MDM node fails, other peer MDM nodes can take over its responsibilities, ensuring continuous operation without disruptions

Known Limitations

Certificate Exchange on PFMP 5.1

The add_certificate = true parameter is not supported on PowerFlex Management Platform (PFMP) 5.1. The certificate exchange functionality requires SSH/scli commands which are incompatible with PFMP 5.1. Additionally, the REST API certificate trust endpoints (/api/trustHostCertificate/Mdm) return HTTP 500 errors on PFMP 5.1 and are not functional.

Workaround: Set add_certificate = false when using PFMP 5.1. The peer system can still be created and managed without certificate exchange. Certificate exchange must be performed manually via the PFMP UI or alternative methods.

Affected Versions: PFMP 5.1 (PowerFlex Gen2 with Core 5.1) Working Versions: PFMP 4.5, PFMP 4.6, PFMP 5.0 (PowerFlex Gen1)

Example Usage

/*
Copyright (c) 2024-2026 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

terraform {
  required_providers {
    powerflex = {
      source                = "registry.terraform.io/dell/powerflex"
      configuration_aliases = [powerflex.system_1, powerflex.system_2]
    }
  }
}

provider "powerflex" {
  alias    = "system_1"
  username = var.username_system_1
  password = var.password_system_1
  endpoint = "https://${var.endpoint_system_1}"
  insecure = true
  timeout  = 120
}

provider "powerflex" {
  alias    = "system_2"
  username = var.username_system_2
  password = var.password_system_2
  endpoint = "https://${var.endpoint_system_2}"
  insecure = true
  timeout  = 120
}

data "powerflex_protection_domain" "protection_domain_system_2" {
  provider = powerflex.system_2
  name     = var.protection_domain_name_system_2
}

data "powerflex_protection_domain" "protection_domain_system_1" {
  provider = powerflex.system_1
  name     = var.protection_domain_name_system_1
}


resource "powerflex_peer_system" "system_1" {
  provider = powerflex.system_1

  // This should be done in order to avoid a confict while sshing
  depends_on = [resource.powerflex_peer_system.system_1]
  ### Required Values

  # New name of the Peer System
  name = var.name
  # Peer System (System 2) ID
  peer_system_id = data.powerflex_protection_domain.protection_domain_system_2.protection_domains[0].system_id
  # List of Peer MDM Ips at the destination
  ip_list = var.mdm_ips_system_2

  ### Optional with defaults if unset


  # Add certificate flag, default: false. 
  # If true source_primary_mdm_information and destination_primary_mdm_information must be filled out in order to get and set the certificate
  #add_certificate = true

  # source_primary_mdm_information = {
  #   # Required fields
  #   ip = "1.2.3.4"
  #   ssh_username = "user"
  #   ssh_password = "pass"
  #   management_ip = var.endpoint_system_1
  #   management_username = var.username_system_1
  #   management_password = var.password_system_1
  #   # Optional field defaults to 22
  #   #ssh_port = "22"
  # }

  # destination_primary_mdm_information = {
  #   # Required fields
  #   ip = "1.2.3.4"
  #   ssh_username = "user"
  #   ssh_password = "pass"
  #   management_ip = var.endpoint_system_2
  #   management_username = var.username_system_2
  #   management_password = var.password_system_2
  #   # Optional field defaults to 22
  #   #ssh_port = "22"
  # }

  # Port of the Peer System Default: 7611
  #port = 7611
  # Sets the Performance Profile, Options (Compact, HighPerformance) Default: HighPerformance
  #perf_profile = "HighPerformance"
}

resource "powerflex_peer_system" "system_2" {
  provider = powerflex.system_2
  ### Required Values

  # New name of the Peer System
  name = var.name
  # Peer System (System 1) ID
  peer_system_id = data.powerflex_protection_domain.protection_domain_system_1.protection_domains[0].system_id
  # List of Peer MDM Ips at the destination
  ip_list = var.mdm_ips_system_1

  ### Optional with defaults if unset


  # Add certificate flag, default: false. 
  # If true source_primary_mdm_information and destination_primary_mdm_information must be filled out in order to get and set the certificate
  # add_certificate = true

  # source_primary_mdm_information = {
  #   # Required fields
  #   ip = "1.2.3.4"
  #   ssh_username = "user"
  #   ssh_password = "pass"
  #   management_ip = var.endpoint_system_2
  #   management_username = var.username_system_2
  #   management_password = var.password_system_2
  #   # Optional field defaults to 22
  #   #ssh_port = "22"
  # }

  # destination_primary_mdm_information = {
  #   # Required fields
  #   ip = "1.2.3.4"
  #   ssh_username = "user"
  #   ssh_password = "pass"
  #   management_ip = var.endpoint_system_1
  #   management_username = var.username_system_1
  #   management_password = var.password_system_1
  #   # Optional field defaults to 22
  #   #ssh_port = "22"
  # }

  # Port of the Peer System Default: 7611
  #port = 7611
  # Sets the Performance Profile, Options (Compact, HighPerformance) Default: HighPerformance
  #perf_profile = "HighPerformance"
}

After the execution of above resource block, the two PowerFlex Peer Systems will be connected. The user can then setup Replication Groups and Pairs in order to replicate volumes across powerflex systems. For more information, please check the terraform state file.

Schema

Required

ip_list (Set of String) List of ips for the peer mdm system.
name (String) Name of the peer mdm instance.
peer_system_id (String) Unique identifier of the peer mdm system.

Optional

add_certificate (Boolean) Flag that if set to true will attempt to add certificate of the peer mdm destination to source. This flag is only used during create.
destination_primary_mdm_information (Attributes) Only used if add_certificate is set to true during create. The destination primary mdm information to get the root certificate. (see below for nested schema)
perf_profile (String) Performance profile of the peer mdm instance.
port (Number) Port of the peer mdm instance.
source_primary_mdm_information (Attributes) Only used if add_certificate is set to true during create. The source primary mdm information to get the root certificate. (see below for nested schema)

Read-Only

coupling_rc (String) Coupling return code number of the peer mdm system.
id (String) Unique identifier of the peer mdm instance.
membership_state (String) membership state of the peer mdm instance.
network_type (String) Network type of the peer mdm system.
software_version_info (String) Software version details of the peer mdm instance.
system_id (String) Unique identifier of the peer mdm system.

Nested Schema for `destination_primary_mdm_information`

Optional:

ip (String) ip of the primary destination mdm instance.
management_ip (String) ip of the destination management instance.
management_password (String, Sensitive) password of the management instance.
management_username (String) ssh username of the destination management instance.
ssh_password (String, Sensitive) ssh password of the primary destination mdm instance.
ssh_port (String) port of the primary destination mdm instance.
ssh_username (String) ssh username of the destination primary mdm instance.

Nested Schema for `source_primary_mdm_information`

Optional:

ip (String) ip of the primary source mdm instance.
management_ip (String) ip of the source management instance.
management_password (String, Sensitive) password of the source instance.
management_username (String) ssh username of the source management instance.
ssh_password (String, Sensitive) ssh password of the source primary mdm instance.
ssh_port (String) port of the primary source mdm instance.
ssh_username (String) ssh username of the source primary mdm instance.

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2024-2026 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import Peer System by its id
terraform import powerflex_peer_system.example "<id>"

This will import the resource instance with specified ID into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_protection_domain resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_protection_domain (Resource)

This resource is used to manage the Protection Domain entity of the PowerFlex Array. We can Create, Update and Delete the protection domain using this resource. We can also import an existing protection domain from the PowerFlex array.

Caution: Protection Domain creation or update is not atomic. In case of partially completed create operations, terraform can mark the resource as tainted. One can manually remove the taint and try applying the configuration (after making necessary adjustments). If the taint is not removed, terraform will destroy and recreate the resource.

Example Usage

/*
Copyright (c) 2023-2024 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Example for creating protection domain. After successful execution, protection domain will be created on the cluster.
resource "powerflex_protection_domain" "pd" {
  # required paramaters  ======

  name = "domain_1"

  # optional parameters  ======

  active = true

  # SDS IOPS throttling
  # overall_io_network_throttling_in_kbps must be greater than the rest of the parameters
  # 0 indicates unlimited IOPS
  protected_maintenance_mode_network_throttling_in_kbps = 10 * 1024
  rebuild_network_throttling_in_kbps                    = 10 * 1024
  rebalance_network_throttling_in_kbps                  = 10 * 1024
  vtree_migration_network_throttling_in_kbps            = 10 * 1024
  overall_io_network_throttling_in_kbps                 = 20 * 1024

  # Fine granularity metadata caching
  fgl_metadata_cache_enabled      = true
  fgl_default_metadata_cache_size = 1024

  # Read Flash cache
  rf_cache_enabled          = true
  rf_cache_operational_mode = "ReadAndWrite" # Read/Write/ReadAndWrite/WriteMiss
  rf_cache_page_size_kb     = 16
  rf_cache_max_io_size_kb   = 32
}

After the execution of above resource block, protection domain would have been created on the PowerFlex array. For more information, please check the terraform state file.

Schema

Required

name (String) Unique name of the protection domain instance.

Optional

active (Boolean) Whether the PD should be in Active state. Default value is true.
fgl_default_metadata_cache_size (Number) Fine Granularity Metadata Cache size. Can be set only when fgl_metadata_cache_enabled is set to true.
fgl_metadata_cache_enabled (Boolean) Whether Fine Granularity Metadata Cache is enabled or not.
overall_io_network_throttling_in_kbps (Number) Maximum allowed IO for protected maintenance mode in KBps. Must be greater than any other network throttling parameter. The value 0 represents unlimited bandwidth. The default value is 0.
protected_maintenance_mode_network_throttling_in_kbps (Number) Maximum allowed IO for protected maintenance mode in KBps. The value 0 represents unlimited bandwidth. The default value is 0.
rebalance_network_throttling_in_kbps (Number) Maximum allowed IO for rebalancing in KBps. The value 0 represents unlimited bandwidth. The default value is 0.
rebuild_network_throttling_in_kbps (Number) Maximum allowed IO for rebuilding in KBps. The value 0 represents unlimited bandwidth. The default value is 0.
rf_cache_enabled (Boolean) Whether SDS Rf Cache is enabled or not. Default value is true.
rf_cache_max_io_size_kb (Number) Maximum IO of the SDS RF Cache in KB. Can be set only when rf_cache_enabled is set to true.
rf_cache_operational_mode (String) Operational Mode of the SDS RF Cache. Accepted values are Read, Write, ReadAndWrite and WriteMiss. Can be set only when rf_cache_enabled is set to true.
rf_cache_page_size_kb (Number) Page size of the SDS RF Cache in KB. Can be set only when rf_cache_enabled is set to true.
vtree_migration_network_throttling_in_kbps (Number) Maximum allowed IO for vtree migration in KBps. The value 0 represents unlimited bandwidth. The default value is 0.

Read-Only

fgl_default_num_concurrent_writes (Number) Fine Granularity default number of concurrent writes.
id (String) Unique identifier of the protection domain instance.
links (Attributes List) Underlying REST API links. (see below for nested schema)
replication_capacity_max_ratio (Number) Maximum Replication Capacity Ratio.
rf_cache_accp_id (String) ID of the RF Cache Acceleration Pool attached to the PD.
state (String) State of the PD.

Nested Schema for `links`

Read-Only:

href (String) Specifies the exact path to fetch the details.
rel (String) Specifies the relationship with the Protection Domain.

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2023-2024 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import Protection Domain by it's id
terraform import powerflex_protection_domain.pd_data "<id>"

This will import the protection domain instance with specified ID into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_replication_consistency_group resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_replication_consistency_group (Resource)

This resource is used to manage the Replication Consistency Group entity of the PowerFlex Array. This feature is only supported for PowerFlex 4.5 and above. We can Create, Update and Delete the PowerFlex Replication Consistency Group using this resource. We can also Import an existing Replication Consistency Group from the PowerFlex array.

Example Usage

/*
Copyright (c) 2024 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

terraform {
  required_providers {
    powerflex = {
      source                = "registry.terraform.io/dell/powerflex"
      configuration_aliases = [powerflex.source, powerflex.destination]
    }
  }
}

provider "powerflex" {
  alias    = "source"
  username = var.username_source
  password = var.password_source
  endpoint = var.endpoint_source
  insecure = true
  timeout  = 120
}

provider "powerflex" {
  alias    = "destination"
  username = var.username_destination
  password = var.password_destination
  endpoint = var.endpoint_destination
  insecure = true
  timeout  = 120
}

data "powerflex_protection_domain" "source_protection_domain" {
  provider = powerflex.source
  name     = var.source_protection_domain_name
}

data "powerflex_protection_domain" "destination_protection_domain" {
  provider = powerflex.destination
  name     = var.destination_protection_domain_name
}

resource "powerflex_replication_consistency_group" "example" {
  provider = powerflex.source
  ### Required Values

  # New name of the Replication Consistency Group
  name = var.name
  # Protection domain on the source machine
  protection_domain_id = data.powerflex_protection_domain.source_protection_domain.protection_domains[0].id
  # Protection domain on the destination machine
  remote_protection_domain_id = data.powerflex_protection_domain.destination_protection_domain.protection_domains[0].id
  # Destination System ID
  destination_system_id = data.powerflex_protection_domain.destination_protection_domain.protection_domains[0].system_id

  ### Optional with defaults if unset

  # Must be greater the 15 or less then 3600 (seconds) Default: 15
  #rpo_in_seconds = 15
  # Sets the Active state, Options (Active, Terminated) Default: Active
  #local_activity_state = "Active"
  # Sets the Volume Access Mode, Options (NoAccess, ReadOnly) Default: NoAccess
  #target_volume_access_mode = "NoAccess"
  # Pause Mode, Options (Resume, Pause) Default: Resume
  #pause_mode = "Resume"
  # Freeze State, Options (Unfrozen, Frozen) Default: Unfrozen
  #freeze_state = "Unfrozen"
  # Current Consistency Mode, Options (Consistent, Inconsistent) Default: Consistent
  #curr_consist_mode = "Consistent"
}

After the execution of above resource block, the Replication Consistency Group will be created between the two Peer Systems. The user can then add Replication Pairs to the RCGs in order to replicate volumes between systems. For more information, please check the terraform state file.

Schema

Required

destination_system_id (String) Replication Consistency Group Destination System ID
name (String) Replication Consistency Group Name
protection_domain_id (String) Replication Consistency Group Protection Domain ID
remote_protection_domain_id (String) Replication Consistency Group Remote Protection Domain ID

Optional

curr_consist_mode (String) Consistency Mode of the replication consistency group instance.
freeze_state (String) Freeze State of the replication consistency group instance.
local_activity_state (String) Local Activity State of the replication consistency group instance.
pause_mode (String) Pause Mode of the replication consistency group instance.
rpo_in_seconds (Number) Replication Consistency Group RPO in Seconds (min: 15, default 15, max: 3600)
target_volume_access_mode (String) Target Volume Access Mode of the replication consistency group instance.

Read-Only

abstract_state (String) Abstract State of the replication consistency group instance.
active_local (Boolean) Active Local of the replication consistency group instance.
active_remote (Boolean) Active Remote of the replication consistency group instance.
disaster_recovery_state (String) Disaster Recovery State of the replication consistency group instance.
error (Number) Error of the replication consistency group instance.
failover_state (String) Failover State of the replication consistency group instance.
failover_type (String) Failover Type of the replication consistency group instance.
id (String) Unique identifier of the replication consistency group instance.
inactive_reason (Number) Inactive Reason of the replication consistency group instance.
last_snap_group_id (String) Last Snap Group ID of the replication consistency group instance.
lifetime_state (String) Lifetime State of the replication consistency group instance.
peer_mdm_id (String) Replication Consistency Group Peer Mdm ID
remote_activity_state (String) Remote Activity State of the replication consistency group instance.
remote_disaster_recovery_state (String) Remote Disaster Recovery State of the replication consistency group instance.
remote_id (String) Remote ID of the replication consistency group instance.
remote_mdm_id (String) Remote MDM ID of the replication consistency group instance.
replication_direction (String) Replication Direction of the replication consistency group instance.
snap_creation_in_progress (Boolean) Snap Creation In Progress of the replication consistency group instance.
type (String) Type of the replication consistency group instance.

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2024 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import Replication Consistency Group by its id
terraform import powerflex_replication_consistency_group.example "<id>"

This will import the resource instance with specified ID into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_replication_consistency_group_action resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_replication_consistency_group_action (Resource)

This resource is used to execute actions on the Replication Consistency Group entity of the PowerFlex Array. This feature is only supported for PowerFlex 4.5 and above.

Example Usage

/*
Copyright (c) 2024 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

terraform {
  required_providers {
    powerflex = {
      source = "registry.terraform.io/dell/powerflex"
    }
  }
}

provider "powerflex" {
  username = var.username
  password = var.password
  endpoint = var.endpoint
  insecure = true
  timeout  = 120
}

// Resource to manage lifecycle
resource "terraform_data" "always_run" {
  input = timestamp()
}

data "powerflex_replication_consistency_group" "rcg_filter" {
  filter {
    name = [var.replication_consistency_group_name]
  }
}

resource "powerflex_replication_consistency_group_action" "example" {
  # Required

  # Id of the replication consistency group
  id = data.powerflex_replication_consistency_group.rcg_filter.replication_consistency_group_details[0].id

  # Action to be performed on the replication consistency group.
  # Options are Failover, Restore, Sync, Reverse, Switchover and Snapshot (Default is Sync)
  action = var.action

  // This will allow terraform create process to trigger each time we run terraform apply.
  lifecycle {
    replace_triggered_by = [
      terraform_data.always_run
    ]
  }
}

After the execution of above resource block, The selected Action will be preformed on the selected RCG. Each time the RCG Actions resource is run it will preform the action again. For more information, please check the terraform state file.

Schema

Required

id (String) Replication Consistency Group ID

Optional

action (String) Replication Consistency Group Action

V1.9.0: powerflex_replication_pair resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_replication_pair (Resource)

This resource is used to manage the Replication Pairs entity of the PowerFlex Array. This feature is only supported for PowerFlex 4.5 and above. We can Create, Update and Delete the PowerFlex Replication Pairs using this resource. We can also Import an existing Replication Pairs from the PowerFlex array. A replication pair involves a set of data on a source system being continuously copied to a target system. This typically applies to individual volumes, files, or objects.

Example Usage

/*
Copyright (c) 2024 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

terraform {
  required_providers {
    powerflex = {
      source                = "registry.terraform.io/dell/powerflex"
      configuration_aliases = [powerflex.source, powerflex.destination]
    }
  }
}

provider "powerflex" {
  alias    = "source"
  username = var.username_source
  password = var.password_source
  endpoint = var.endpoint_source
  insecure = true
  timeout  = 120
}

provider "powerflex" {
  alias    = "destination"
  username = var.username_destination
  password = var.password_destination
  endpoint = var.endpoint_destination
  insecure = true
  timeout  = 120
}

# Used to get the id of the source volume
data "powerflex_volume" "source_volume" {
  provider = powerflex.source
  name     = var.volume_name_source
}

# Used to get the id of the destination volume
data "powerflex_volume" "destination_volume" {
  provider = powerflex.destination
  name     = var.volume_name_destination
}

# Used to get the id of the replication consistency group
data "powerflex_replication_consistency_group" "source_replication_consistency_group" {
  provider = powerflex.source
  filter {
    name = [var.replication_consistency_group_name_source]
  }
}

# Commands to run this tf file : terraform init && terraform plan && terraform apply
# Create, Update, Delete is supported for this resource
# name, source_volume_id, destination_volume_id, replication_consistency_group_id are the required parameters to create or update
# Only pause_initial_copy can be updated to true or false

# Create Replication Pair
resource "powerflex_replication_pair" "example" {
  provider = powerflex.source
  # Required values
  name                             = "example-replication-pair"
  source_volume_id                 = data.powerflex_volume.source_volume.volumes[0].id
  destination_volume_id            = data.powerflex_volume.destination_volume.volumes[0].id
  replication_consistency_group_id = data.powerflex_replication_consistency_group.source_replication_consistency_group.replication_consistency_group_details[0].id
  # Optional values
  # pause_initial_copy = true # Pauses the replication pair (This will only work during the initial copy process), defaults to false
}

After the execution of above resource block, resource would have been created on the PowerFlex array. For more information, please check the terraform state file.

Schema

Required

destination_volume_id (String) Destination Volume ID
name (String) Replication Pair Name
replication_consistency_group_id (String) Replication Consistency Group ID
source_volume_id (String) Source Volume ID

Optional

pause_initial_copy (Boolean) Pause Copy of the replication pair instance.

Read-Only

copy_type (String) Copy Type for Replication Pairs only value is OnlineCopy
id (String) Unique identifier of the replication pair instance.
initial_copy_priority (Number) Initial Copy Priority of the replication pair instance.
initial_copy_state (String) Initial Copy State of the replication pair instance.
lifetime_state (String) Lifetime State of the replication pair instance.
local_volume_id (String) Local Volume ID of the replication pair instance.
peer_system_name (String) Peer System Name of the replication pair instance.
remote_capacity_in_mb (Number) Remote Capacity in MB of the replication pair instance.
remote_id (String) Remote ID of the replication pair instance.
remote_volume_id (String) Remote Volume ID of the replication pair instance.
remote_volume_name (String) Remote Volume Name of the replication pair instance.
user_requested_pause_transmit_init_copy (Boolean) User Requested Pause of the replication pair instance.

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2024 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import Replication Pair by its id
terraform import powerflex_replication_pair.example "<id>"

This will import the resource instance with specified ID into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_resource_credential resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_resource_credential (Resource)

This resource is used to manage Resource Credential entity of the PowerFlex Array. This feature is only supported for PowerFlex 4.5 and above. We can Create, Update and Delete the PowerFlex Resource Credentials using this resource. We can also Import an existing Resource Credentials from the PowerFlex array.

Example Usage

/*
Copyright (c) 2025-2026 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

terraform {
  required_providers {
    powerflex = {
      source = "registry.terraform.io/dell/powerflex"
    }
    local = {
      source  = "hashicorp/local"
      version = "2.5.2"
    }
    vault = {
      source  = "hashicorp/vault"
      version = "4.6.0"
    }
  }
}
// Used to grab the password
provider "vault" {
  address = "https://my-vault-server.com"
  token   = "some-token-value"
}

provider "powerflex" {
  username = "user"
  password = "password"
  endpoint = "https://example.com"
  insecure = true
  timeout  = 120
}

// Can grab secret from vault
# data "vault_generic_secret" "secret"{
#  path = "secret/instances"
# }

# Command to run this tf file : terraform init && terraform plan && terraform apply
# Create, Read, Delete and Import operations are supported for this resource

## Optional only needed if using ssh_private_key field
# data "local_file" "ssh_key" {
#   filename = var.ssh_private_key_path
# }

# Create Resource Credential
resource "powerflex_resource_credential" "example" {
  ## Required values for all credential types
  name     = var.name
  type     = var.type // Options: Node, Switch, vCenter, ElementManager, PowerflexGateway, PresentationServer, OSAdmin, OSUser
  username = var.username
  // Grab from variable file
  password = var.password
  ## Grab from vault 
  #password = "${data.vault_generic_secret.secret.data["password"]}"

  ## Required value for vCenter, ElementManager, OSUser
  #domain = var.domain

  ## Required value for PowerflexGateway
  #os_username = var.os_username
  #os_password = var.os_password

  ## Optional values for Node, Switch, ElementManager
  #snmp_v2_community_string = var.snmpv2_community_string

  ## Optional for Node
  #snmp_v3_security_level = var.snmpv3_security_level // Options "Minimal", "Moderate", or "Maximal"
  #snmp_v3_security_name = var.snmpv3_security_name
  #snmp_v3_md5_authentication_password = var.snmpv3_md5_auth_password // required for level "Moderate" and "Maximal"
  #snmp_v3_des_authentication_password = var.snmpv3_des_private_password // required for level "Maximal"

  ## Optional for Node, Switch, OSAdmin, OSUser
  #ssh_private_key = data.local_file.ssh_key.content
  #key_pair_name = var.key_pair_name
}

After the execution of above resource block, resource would have been created on the PowerFlex array. For more information, please check the terraform state file.

Schema

Required

name (String) Resource Credential name
password (String, Sensitive) Resource Credential password
type (String) Resource Credential type
username (String) Resource Credential username

Optional

domain (String) Resource Credential domain, used by types OSUser, ElementManager and vCenterCredential
key_pair_name (String) Resource Credential key_pair_name, can be used by types Node, Switch, OSAdminCrednetial and OSUserCredential. Is Required if ssh_private_key is set
os_password (String, Sensitive) Resource Credential os_password, used by types PowerflexGateway
os_username (String) Resource Credential os_username, used by types PowerflexGateway
snmp_v2_community_string (String) Resource Credential snmp_v2_community_string, used by types Node, Switch and ElementManager. If unset it will default to public
snmp_v3_des_authentication_password (String, Sensitive) Resource Credential snmp_v3_des_authentication_password, used by types Node when snmp_v3_security_level is set to Maximal
snmp_v3_md5_authentication_password (String, Sensitive) Resource Credential snmp_v3_md5_authentication_password, used by types Node when snmp_v3_security_level is set to Moderate
snmp_v3_security_level (String) Resource Credential snmp_v3_security_level, used by types Node. Minimal requires only snmp_v3_security_name, Moderate requires snmp_v3_security_name and snmp_v3_md5_authentication_password, Maximal requires snmp_v3_security_name, snmp_v3_md5_authentication_password and snmp_v3_des_authentication_password
snmp_v3_security_name (String) Resource Credential snmp_v3_security_name, used by types Node
ssh_private_key (String, Sensitive) Resource Credential ssh_private_key, can be used by types Node, Switch, OSAdminCrednetial and OSUserCredential

Read-Only

created_by (String) Resource Credential created_by
created_date (String) Resource Credential created_date
id (String) Unique identifier of the resource credential instance.
updated_by (String) Resource Credential updated_by
updated_date (String) Resource Credential updated_date

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2025-2026 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import resource credential by its id
terraform import powerflex_resource_credential.example "<id>"

This will import the resource instance with specified ID into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_resource_group resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_resource_group (Resource)

This resource is used to manage the ResourceGroup entity of the PowerFlex Array. We can Create, Update and Delete the PowerFlex ResourceGroup using this resource. We can also Import an existing ResourceGroup from the PowerFlex array.

Example Usage

/*
Copyright (c) 2024 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/


# Commands to run this tf file : terraform init && terraform plan && terraform apply
# Create, Update, Delete is supported for this resource
# To create / update, either template_id or firmware_id must be provided
# deployment_name and deployment_description are the required parameters to create or update
# other  atrributes like : nodes, port, deployment_timeout are optional 
# To check which attributes can be updated, please refer Product Guide in the documentation


# example 1: Resource Group Resource
resource "powerflex_resource_group" "Data" {
  deployment_name        = "Test-Create-U1"
  deployment_description = "Test Service-U1"
  template_id            = "453c41eb-d72a-4ed1-ad16-bacdffbdd766"
  firmware_id            = "8aaaee208c8c467e018cd37813250614"
  nodes                  = 0
  clone_from_host        = "pfmc-k8s-20230809-160"
  deployment_timeout     = 0
}


# example 2: Get Template ID and Firmware ID from Template Datasource

data "powerflex_template" "template_data" {
  template_names = ["Teample_Name"]
}

resource "powerflex_resource_group" "Data" {
  deployment_name        = "Test-Create-U1"
  deployment_description = "Test Service-U1"
  template_id            = tolist(data.powerflex_template.template_data.template_details)[0].id
  firmware_id            = tolist(data.powerflex_template.template_data.template_details)[0].firmware_id
  nodes                  = 3
  clone_from_host        = "pfmc-k8s-20230809-160"
  deployment_timeout     = 60
}

After the execution of above resource block, Resource Group would have been deployed on the PowerFlex Gateway. For more information, please check the terraform state file.

Schema

Required

deployment_description (String) Deployment Description
deployment_name (String) Deployment Name
firmware_id (String) Firmware ID
template_id (String) Published Template ID

Optional

clone_from_host (String) Resource to Duplicate From Host
deployment_timeout (Number) Deployment Timeout, It should be in multiples of 5
nodes (Number) Number of Nodes
servers_in_inventory (String) After Delete the Service, Servers in inventory Keep or Remove. Default value is Keep
servers_managed_state (String) After Delete the Service, Servers’s state Managed or Unmanaged. Default value is Unmanaged.

Read-Only

compliant (Boolean) Deployment Compliant Status
id (String) Deployment ID
status (String) Deployment Status
template_name (String) Service Template Name

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2024 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import Resource Group by it's id
terraform import powerflex_resource_group.data "<id>"

V1.9.0: powerflex_sdc_host resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_sdc_host (Resource)

This resource is used to manage the SDC entity of the PowerFlex Array. We can Create, Update and Delete the SDC using this resource. We can also import an existing SDC from the PowerFlex array.

Caution: SDC Host creation is not atomic. This resource sets parameters like name, etc. after SDC installation is complete. If that fails for any reason, Terraform, by default, will mark this resource as tainted and recreate it on the next apply. But these issues (caused by invalid inputs, network disruptions, etc.) do not require resource recreation (ie. SDC re-installation) to resolve. If one untaints this resource manually (by running terraform untaint <resource_name>) prior to applying again, this resource can start from where it left off and, if the cause of failure has been rectified, it can take incremental actions to set the necessary SDC parameters. So please untaint the resource before applying again if you want to prevent unnecessary SDC re-installations.

Example Usage

With ESXi

/*
Copyright (c) 2024-2026 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Command to run this tf file : terraform init && terraform plan && terraform apply.
# Create, Update, Read, Delete and Import operations are supported for this resource.
# sdc_details is the required parameter for the SDC resource.

# Example for adding an ESXi host as SDC.
# In this example, we are using passwordless ssh authentication using private key and host key.

# load the private key
data "local_sensitive_file" "ssh_key" {
  filename = "/root/.ssh/esxi_rsa"
}

# load the host key
data "local_sensitive_file" "host_key" {
  filename = "esxi_host_ecdsa_key.pub"
}

# generate a random guid. This is required only for ESXi hosts.
resource "random_uuid" "sdc_guid" {
}

resource "powerflex_sdc_host" "sdc" {
  ip = "10.10.10.10"
  remote = {
    user = "root"
    # we are not using password auth here, but it can be used as well
    # password = "W0uldntUWannaKn0w!"
    private_key = data.local_sensitive_file.ssh_key.content_base64
    host_key    = data.local_sensitive_file.host_key.content_base64
  }
  os_family = "esxi"
  esxi = {
    guid = random_uuid.sdc_guid.result
  }
  name         = "sdc-esxi"
  package_path = "/root/terraform-provider-powerflex/sdc-3.6.500.106-esx7.x.zip"
  # Optional all the mdms(either primary,secondary or virtual ips) in a comma separated list by cluster if unset will use the mdms of the cluster set in the provider block
  # clusters_mdm_ips = ["10.10.10.5,10.10.10.6", "10.10.10.7,10.10.10.8"] 
}

After the execution of above resource block, the ESXi host would have been added as an SDC to the PowerFlex array. For more information, please check the terraform state file.

With Linux

/*
Copyright (c) 2024-2026 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Command to run this tf file : terraform init && terraform plan && terraform apply.
# Create, Update, Read, Delete and Import operations are supported for this resource.
# sdc_details is the required parameter for the SDC resource.

# Example for adding an Linux host as SDC.
# In this example, we are using passwordless ssh authentication using private key and host key.

# load the private key
data "local_sensitive_file" "ssh_key" {
  filename = "/root/.ssh/linux_rsa"
}

# load the host key
data "local_sensitive_file" "host_key" {
  filename = "linux_host_ecdsa_key.pub"
}

# Example for adding an Linux host as SDC.
resource "powerflex_sdc_host" "sdc_linux" {
  ip = "10.10.10.10"
  remote = {
    user = "root"
    # we are not using password auth here, but it can be used as well
    # password = "password"
    private_key = data.local_sensitive_file.ssh_key.content_base64
    host_key    = data.local_sensitive_file.host_key.content_base64
  }
  os_family       = "linux"
  name            = "sdc-linux"
  use_remote_path = false
  package_path    = "/root/terraform-provider-powerflex/EMC-ScaleIO-sdc-3.6-700.103.Ubuntu.22.04.x86_64.tar" # For Ubuntu
  # package_path = "/root/terraform-provider-powerflex/EMC-ScaleIO-sdc-3.6-700.103.el7.x86_64.rpm" # For RHEL
  # Optional all the mdms (either primary,secondary or virtual ips) in a comma separated list by cluster if unset will use the mdms of the cluster set in the provider block
  # Removal of mdms is not supported for linux, if you wish to remove a cluster from the sdc please follow steps here: https://www.dell.com/support/kbdoc/en-us/000167031/how-do-i-remove-the-mdm-entry-from-the-sdc-as-displayed-in-the-output-of-drv-cfg-binary-in-query-mdms-on-the-sdc-on-windows-or-linux-os#:~:text=Resolution%201%20For%20Linux%20SDC%20host%2C%20open%20%2Fbin%2Femc%2Fscaleio%2Fdrv_cfg.txt,4%20Reboot%20Linux%20SDC%20host%20to%20apply%20changes.?msockid=0ee30a4c8e9f67f610c21ecc8f89664a
  # clusters_mdm_ips = ["10.10.10.5,10.10.10.6", "10.10.10.7,10.10.10.8"] 
}

After the execution of above resource block, the Linux host would have been addes as an SDC to the PowerFlex array. For more information, please check the terraform state file.

With Windows

/*
Copyright (c) 2024-2026 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Command to run this tf file : terraform init && terraform plan && terraform apply.
# Create, Update, Read, Delete and Import operations are supported for this resource.
# sdc_details is the required parameter for the SDC resource.

# Example for adding an Windows host as SDC.
# In this example, we are using passwordless ssh authentication using private key and host key.


# Example for adding an Windows host as SDC.
resource "powerflex_sdc_host" "sdc_windows" {
  ip = "10.10.10.10"
  remote = {
    user     = "username"
    password = "password"
    port     = 5985
  }
  os_family    = "windows"
  name         = "sdc-windows"
  package_path = "/root/terraform-provider-powerflex/EMC-ScaleIO-sdc-3.6-200.105.msi"
  # Optional all the mdms(either primary,secondary or virtual ips) in a comma separated list by cluster if unset will use the mdms of the cluster set in the provider block
  # Removal of mdms is not supported for windows, if you wish to remove a cluster from the sdc please follow steps here: https://www.dell.com/support/kbdoc/en-us/000167031/how-do-i-remove-the-mdm-entry-from-the-sdc-as-displayed-in-the-output-of-drv-cfg-binary-in-query-mdms-on-the-sdc-on-windows-or-linux-os#:~:text=Resolution%201%20For%20Linux%20SDC%20host%2C%20open%20%2Fbin%2Femc%2Fscaleio%2Fdrv_cfg.txt,4%20Reboot%20Linux%20SDC%20host%20to%20apply%20changes.?msockid=0ee30a4c8e9f67f610c21ecc8f89664a
  # clusters_mdm_ips = ["10.10.10.5,10.10.10.6", "10.10.10.7,10.10.10.8"]   
}

After the execution of above resource block, the Windows Server host would have been addes as an SDC to the PowerFlex array. For more information, please check the terraform state file.

Schema

Required

ip (String) IP address of the server to be configured as SDC.
os_family (String) Operating System family of the SDC. Accepted values are ’linux’, ‘windows’ and ’esxi’. Cannot be changed once set.
package_path (String) Full path (on local machine) of the package to be installed on the SDC.
remote (Attributes) Remote login details of the SDC. (see below for nested schema)

Optional

clusters_mdm_ips (List of String) List of MDM IPs (primary,secondary or list of virtual IPs) seperated by cluster, to be assigned to the SDC.Each string in the list is a set of Mdm Ips related to a specific cluster. These Ips should be seperated by comma I.E. [‘x.x.x.x,y.y.y.y’, ‘z.z.z.z,a.a.a.a’].
esxi (Attributes) Details of the SDC host if the os_family is esxi. (see below for nested schema)
linux_drv_cfg (String) Path to the drv_cfg for linux, defaults to /opt/emc/scaleio/sdc/bin/
name (String) Name of SDC.
performance_profile (String) Performance profile of the SDC. Accepted values are ‘HighPerformance’ and ‘Compact’.
use_remote_path (Boolean) Use path on remote server where SDC is installed. Defaults to false.
windows_drv_cfg (String) Path to the drv_cfg.exe config for windows, defaults to C:\Program Files\EMC\scaleio\sdc\bin\

Read-Only

guid (String) GUID of the HOST
id (String) The id of the SDC
is_approved (Boolean) Is Host Approved
mdm_connection_state (String) MDM Connection State
on_vmware (Boolean) Is Host on VMware
system_id (String) System ID of the Host

Nested Schema for `remote`

Required:

user (String) Remote Login username of the SDC server.

Optional:

certificate (String) Remote Login certificate issued by a CA to the remote login user. Must be used with private_key and the private key must match the certificate.
dir (String) Directory on the SDC server to upload packages to for Unix. Defaults to /tmp on Unix.
host_key (String) Remote Login host key of the SDC server. Corresponds to the UserKnownHostsFile field of OpenSSH.
password (String, Sensitive) Remote Login password of the SDC server.
port (String) Remote Login port of the SDC server. Defaults to 22.
private_key (String, Sensitive) Remote Login private key of the SDC server. Corresponds to the IdentityFile field of OpenSSH.

Nested Schema for `esxi`

Required:

guid (String) GUID of the SDC.

Optional:

verify_vib_signature (Boolean) Whether to verify the VIB signature or not. Defaults to true.

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2024-2026 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import SDC by it's IP address
terraform import powerflex_sdc_host.sdc "<ip>"

This will import the SDC instance with specified IP into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_sdc_volumes_mapping resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_sdc_volumes_mapping (Resource)

This resource can be used to map/unmap volumes to an SDC on the PowerFlex array. User can import an existing SDC and map volumes to it.

Caution: SDC Volume mapping creation or update is not atomic. In case of partially completed create operations, terraform can mark the resource as tainted. One can manually remove the taint and try applying the configuration (after making necessary adjustments). If the taint is not removed, terraform will destroy and recreate the resource.

Note: Either id or name is required. But not both.

Note: Either volume_id or volume_name is required. But not both.

Note: If there are existing volumes mapped to SDC, import the mappings first before performing any operation.

Example Usage

/*
Copyright (c) 2023-2024 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Command to run this tf file : terraform init && terraform plan && terraform apply.
# Create, Update, Delete is supported for this resource.
# To import, check import.sh for more info.
# To create/update, either SDC ID or SDC name must be provided.
# volume_list attribute is optional. 
# To check which attributes of the sdc_volumes_mappping resource can be updated, please refer Product Guide in the documentation
data "powerflex_sdc" "filtered" {
  filter {
    name = ["sdc-esxi-sdc-name"]
  }
}

resource "powerflex_sdc_volumes_mapping" "mapping-test" {
  # SDC id
  id = data.powerflex_sdc.filtered.sdcs[0].id
  volume_list = [
    {
      # id of the volume which needs to be mapped. 
      # either volume_id or volume_name can be used.
      volume_id = "edb2059700000002"

      # Valid values are 0 or integers greater than 10
      limit_iops = 140

      # Default value is 0
      limit_bw_in_mbps = 19

      access_mode = "ReadOnly" # ReadOnly/ReadWrite/NoAccess
    },
    {
      volume_name      = "terraform-vol"
      access_mode      = "ReadWrite"
      limit_iops       = 120
      limit_bw_in_mbps = 25
    }
  ]
}

# To unmap all the volumes mapped to SDC, below config can be used. After successful execution, all the volumes mapped to SDC will be unmapped.

resource "powerflex_sdc_volumes_mapping" "mapping-test" {
  id          = "e3ce1fb600000001"
  volume_list = []
}

After the execution of above resource block, two volumes would have been unmapped from SDC on the PowerFlex array. For more information, please check the terraform state file

Schema

Optional

id (String) The ID of the SDC.
name (String) The name of the SDC.
volume_list (Attributes List) List of volumes mapped to SDC. At least one of volume_id and volume_name is required. (see below for nested schema)

Nested Schema for `volume_list`

Optional:

access_mode (String) The Access Mode of the SDC. Valid values are ReadOnly, ReadWrite and NoAccess. Default value is ReadOnly.
limit_bw_in_mbps (Number) Bandwidth limit in MBPS. 0 represents unlimited bandwith. Default value is 0.
limit_iops (Number) IOPS limit. Valid values are 0 or integers greater than 10. 0 represents unlimited IOPS. Default value is 0.
volume_id (String) The ID of the volume.
volume_name (String) The name of the volume.

Import

Import is supported using the following syntax:

# Below are the steps to import sdc along with mapped volumes :
# Step 1 - To import a sdc , we need the id of that sdc
# Step 2 - To check the id of the sdc we can make use of sdc datasource . Please refer sdc_datasource.tf for more info.
# Step 3 - create a tf file with empty resource block . Refer the example below.
# Example :
# resource "powerflex_sdc_volumes_mapping" "resource_block_name" {
# }
# Step 4 - execute the command: terraform import "powerflex_sdc_volumes_mapping.resource_block_name" "id_of_the_sdc" (resource_block_name must be taken from step 3 and id must be taken from step 2)
# Step 5 - After successful execution of the command , check the state file.

# /*
# Copyright (c) 2023-2024 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import using SDC id
terraform import powerflex_sdc_volumes_mapping.sdc_mapping_import_by_id "<id>"

This will import the SDC instance with specified ID into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_sds resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_sds (Resource)

This resource is used to manage the Storage Data Servers entity of the PowerFlex Array. We can Create, Update and Delete the SDS using this resource. We can also import an existing SDS from the PowerFlex array.

Caution: SDS creation or update is not atomic. In case of partially completed create operations, terraform can mark the resource as tainted. One can manually remove the taint and try applying the configuration (after making necessary adjustments). If the taint is not removed, terraform will destroy and recreate the resource.

Note: Either protection_domain_name and protection_domain_id is required. But not both.

Example Usage

/*
Copyright (c) 2023-2024 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Commands to run this tf file : terraform init && terraform plan && terraform apply
# Create, Update, Delete is supported for this resource
# To import , check sds_resource_import.tf for more info
# To create / update, either protection_domain_name or protection_domain_id must be provided
# name and ip_list are the required parameters to create or update
# other  atrributes like : performance_profile, port, drl_mode, rmcache_enabled, rfcache_enabled, rmcache_size_in_mb are optional 
# To check which attributes can be updated, please refer Product Guide in the documentation

# Example for adding SDS. After successful execution, SDS will be added to the protection domain.
resource "powerflex_sds" "create" {
  name                   = "demo-sds-test-01"
  protection_domain_name = "demo-sds-pd"
  ip_list = [
    {
      ip   = "10.10.10.12"
      role = "sdsOnly" # all/sdsOnly/sdcOnly
    },
    {
      ip   = "10.10.10.11"
      role = "sdcOnly" # all/sdsOnly/sdcOnly
    },
  ]
}

# Example for adding SDS with fault set. After successful execution, SDS will be added to the protection domain and fault set.
resource "powerflex_fault_set" "test" {
  protection_domain_id = "202a046600000000"
  name                 = "demo_fault_set"
}

resource "powerflex_sds" "create" {
  name                   = "demo-sds-test-01"
  protection_domain_name = "demo-sds-pd"
  fault_set_id           = powerflex_fault_set.test.id
  ip_list = [
    {
      ip   = "10.10.10.12"
      role = "sdsOnly" # all/sdsOnly/sdcOnly
    },
    {
      ip   = "10.10.10.11"
      role = "sdcOnly" # all/sdsOnly/sdcOnly
    },
  ]
}

output "changed_sds" {
  value = powerflex_sds.create
}

After the execution of above resource block, sds would have been created on the PowerFlex array. For more information, please check the terraform state file.

Schema

Required

ip_list (Attributes Set) List of IPs to be assigned to the SDS. There must be at least one IP with all role or at least two IPs, one with role sdcOnly and the other with role sdsOnly. (see below for nested schema)
name (String) Name of SDS.

Optional

drl_mode (String) DRL mode of SDS
fault_set_id (String) Fault set id of SDS
performance_profile (String) Performance Profile of SDS. Valid values are Compact and HighPerformance. Default value is determined by array settings.
port (Number) Port of SDS
protection_domain_id (String) ID of the Protection Domain under which the SDS will be created. Conflicts with protection_domain_name. Cannot be updated.
protection_domain_name (String) Name of the Protection Domain under which the SDS will be created. Conflicts with protection_domain_id. Cannot be updated.
rfcache_enabled (Boolean) Rfcache enabled state of SDS
rmcache_enabled (Boolean) Rmcache enabled state of SDS
rmcache_size_in_mb (Number) Read RAM cache size in MB of SDS. Can be set only when rmcache_enabled is true.

Read-Only

id (String) The id of the SDS
is_on_vmware (Boolean) Is on vmware state of SDS
mdm_connection_state (String) Mdm connection state of SDS
membership_state (String) Membership state of SDS
num_of_io_buffers (Number) Number of io buffers of SDS
rmcache_frozen (Boolean) RMcache frozen state of SDS
rmcache_memory_allocation_state (String) Rmcache memory allocation state of SDS.
sds_state (String) State of SDS

Nested Schema for `ip_list`

Required:

ip (String) IP address to be assigned to the SDS.
role (String) Role to be assigned to the IP address. Valid values are all, sdcOnly and sdsOnly.

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2023-2024 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import SDS by it's id
terraform import powerflex_sds.sds_data "<id>"

This will import the SDS instance with specified ID into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_snapshot resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_snapshot (Resource)

This resource is used to manage the Snapshot of volumes on the PowerFlex Array. We can Create, Update and Delete the snapshots using this resource. We can also import an existing snapshot from the PowerFlex array.

Caution: Snapshot creation or update is not atomic. In case of partially completed create operations, terraform can mark the resource as tainted. One can manually remove the taint and try applying the configuration (after making necessary adjustments). If the taint is not removed, terraform will destroy and recreate the resource.

Note: Either volume_name or volume_id is required. But not both. In case of partial create/update operation, retention will not be set.

Example Usage

/*
Copyright (c) 2023-2024 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Commands to run this tf file : terraform init && terraform plan && terraform apply
# Create, Update, Delete is supported for this resource
# To import , check snapshot_resource_import.tf for more info
# To create / update, either volume_id or volume_name must be provided
# name is the required parameter to create or update
# other  atrributes like : access_mode, size, capacity_unit, lock_auto_snapshot, desired_retention, retention_unit, remove_mode are optional 
# To check which attributes of the snapshot can be updated, please refer Product Guide in the documentation

# Example for creating snapshot with mandatory params. After successful execution, snapshot will be created of the same size as volume.
resource "powerflex_snapshot" "snapshots-create" {
  name      = "snapshots-create"
  volume_id = "4577c84000000120"
}

# Example for creating snapshot with optional params. After successful execution, snapshot will be created with the specified size.
resource "powerflex_snapshot" "snapshots-create-01" {
  name          = "snapshots-create-epsilon"
  volume_id     = "4577c84000000120"
  access_mode   = "ReadWrite" # ReadOnly/ReadWrite
  size          = 16
  capacity_unit = "GB"                    # GB/TB
  remove_mode   = "INCLUDING_DESCENDANTS" # INCLUDING_DESCENDANTS/ONLY_ME
}


# General guidlines for furnishing this resource block 
# resource "powerflex_snapshot" "snapshots-create-1" {
# 	name = "<snapshot name>"
# 	volume_name = "<volume name>"
# 	access_mode = "<access mode options are ReadOnly/ReadWrite, default value ReadOnly>"
# 	size = "<size[int] associated with capacity unit>"
# 	capacity_unit =  "<capacity unit options are gb/tb, default value gb>"
# 	lock_auto_snapshot = "<lock auto snapshot, snapshot which are created by snapshot policy can be locked.>"
# 	desired_retention = "<desired retention[int] associated with retention unit>"
# 	retention_unit = "<retention unit options are hours/days, default value hours>"
# 	remove_mode = "<remove mode options are ONLY_ME/INCLUDING_DESCENDANTS, default value ONLY_ME>"
# }

After the execution of above resource block, snapshot would have been created on the PowerFlex array. For more information, please check the terraform state file.

Schema

Required

name (String) The name of the snapshot.

Optional

access_mode (String) The Access mode of snapshot. Valid values are ReadOnly and ReadWrite. Default value is ReadOnly.
capacity_unit (String) Unit of capacity of the volume. Must be one of GB and TB. Default value is GB.
desired_retention (Number) The minimum amount of time that the snapshot should be retained on the array starting at the time of apply. The unit is defined by retention_unit. Cannot be decreased.
lock_auto_snapshot (Boolean) lock auto snapshot
remove_mode (String) Remove mode of the snapshot. Valid values are ONLY_ME and INCLUDING_DESCENDANTS. Default value is ONLY_ME.
retention_unit (String) Retention unit of the snapshot. Valid values are hours and days. Default value is hours.
size (Number) Size of the snapshot. The unit of size is defined by capacity_unit. The storage capacity of a snapshot must be a multiple of 8GB and cannot be decreased.
volume_id (String) The ID of the volume from which snapshot is to be created. Conflicts with volume_name. Cannot be updated.
volume_name (String) The volume name for which snapshot is created. Conflicts with volume_id. Cannot be updated.

Read-Only

id (String) The ID of the snapshot.
retention_in_min (String) retention of snapshot in min
size_in_kb (Number) Size in KB

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2023-2024 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import Snapshot by it's id
terraform import powerflex_snapshot.ss_data "<id>"

This will import the snapshot instance with specified ID into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_snapshot_policy resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_snapshot_policy (Resource)

This resource is used to manage the Snapshot Policy entity of the PowerFlex Array. We can Create, Update and Delete the snapshot policy using this resource. We can also import an existing snapshot policy from the PowerFlex array.

Example Usage

/*
Copyright (c) 2024 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Command to run this tf file : terraform init && terraform plan && terraform apply
# Create, Update, Delete is supported for this resource
# To import , check import.sh for more info
# name, num_of_retained_snapshots_per_level, auto_snapshot_creation_cadence_in_min is the required parameter to create or update 


resource "powerflex_snapshot_policy" "sp" {
  name                                  = "snap-create"
  num_of_retained_snapshots_per_level   = [2, 6, 7]
  auto_snapshot_creation_cadence_in_min = 6
  volume_ids                            = ["edd2fb3100000007", "edd322270000000a"] # assigning or unassigning volumes to snapshot policy
  snapshot_access_mode                  = "ReadWrite"                              # Cannot be updated after creation. It only supports two values : ReadOnly / ReadWrite
  secure_snapshots                      = false                                    # Cannot be updated after creation
  #remove_mode = "Remove" #remove_mode is applicable while unassingning the volumes from the snapshot policy. It only supports two values : Remove / Detach
}

After the execution of above resource block, snapshot_policy would have been created on the PowerFlex array. For more information, please check the terraform state file.

Schema

Required

auto_snapshot_creation_cadence_in_min (Number) The interval in minutes between two snapshots in the policy.
name (String) Name of the Snapshot Policy
num_of_retained_snapshots_per_level (List of Number) List which represents the number of snapshots per retention level.

Optional

paused (Boolean) Indicates that the snapshot policy should paused or not. Default value is false.
remove_mode (String) When removing the source volume from the policy, user should choose how to handle the snapshots created by the policy. Valid values are ‘Remove’ and ‘Detach’. Default value is Detach.
secure_snapshots (Boolean) The auto snapshots will be created as secure. They cannot be edited or removed prior to their policy expiration time. Default value is false. Cannot be updated.
snapshot_access_mode (String) The Access mode of auto snapshot. Valid values are ‘ReadOnly’ and ‘ReadWrite’. Default value is ReadOnly Cannot be updated.
volume_ids (Set of String) List which represents the volume ids which is to be assigned to the snapshot policy.

Read-Only

id (String) ID of the Snapshot Policy.

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2023-2024 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import snapshot policy by it's id
terraform import powerflex_snapshot_policy.snapshot_policy_import_by_id "<id>"

This will import the snapshot_policy instance with specified ID into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_storage_node_v2 resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_storage_node_v2 (Resource)

This resource is used to manage Storage Nodes on PowerFlex Gen2 systems (5.0+). Storage Nodes are the Gen2 replacement for SDS.

Example Usage

/*
Copyright (c) 2024-2026 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Commands to run this tf file : terraform init && terraform plan && terraform apply
# Create, Update, Delete is supported for this resource
# To import, check import.tf for more info
# protection_domain_id is required
# name and ip_list are required parameters to create
# port and fault_set_id are optional
# This resource is for PowerFlex Gen2 systems (5.0+)

# Example for creating a Storage Node (Gen2 replacement for SDS)
resource "powerflex_storage_node_v2" "create" {
  name                 = "demo-storage-node-01"
  protection_domain_id = "202a046600000000"
  ip_list = [
    {
      ip   = "10.10.10.12"
      role = "all" # all/sdsOnly/sdcOnly
    },
    {
      ip   = "10.10.10.11"
      role = "sdcOnly" # all/sdsOnly/sdcOnly
    },
  ]
}

# Example for creating a Storage Node with fault set
resource "powerflex_fault_set" "test" {
  protection_domain_id = "202a046600000000"
  name                 = "demo_fault_set"
}

resource "powerflex_storage_node_v2" "create_with_fs" {
  name                 = "demo-storage-node-02"
  protection_domain_id = "202a046600000000"
  fault_set_id         = powerflex_fault_set.test.id
  port                 = "6611"
  ip_list = [
    {
      ip   = "10.10.10.13"
      role = "all"
    },
  ]
}

output "storage_node" {
  value = powerflex_storage_node_v2.create
}

Schema

Required

protection_domain_id (String) The ID of the protection domain.

Optional

fault_set_id (String) The ID of the fault set.
ip_list (Block List) List of IPs associated with the storage node. (see below for nested schema)
name (String) The name of the storage node.
performance_profile (String) The performance profile of the storage node.
port (String) The port number for the storage node.

Read-Only

id (String) The unique identifier of the storage node.
maintenance_state (String) The maintenance state of the storage node.
mdm_connection_state (String) The MDM connection state of the storage node.
membership_state (String) The membership state of the storage node.
num_of_devices (Number) The number of devices attached to the storage node.
software_version (String) The software version of the storage node.
state (String) The state of the storage node.
status (String) The status of the storage node.
total_capacity_in_kb (Number) The total capacity of the storage node in KB.
used_capacity_in_kb (Number) The used capacity of the storage node in KB.

Nested Schema for `ip_list`

Required:

ip (String) IP address.
role (String) Role of the IP. Valid values: SdsOnly, SdcOnly, All.

V1.9.0: powerflex_storage_pool resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_storage_pool (Resource)

This resource is used to manage the Storage Pool entity of the PowerFlex Array. We can Create, Update and Delete the storage pool using this resource. We can also import an existing storage pool from the PowerFlex array.

Caution: Storage Pool creation or update is not atomic. In case of partially completed create operations, terraform can mark the resource as tainted. One can manually remove the taint and try applying the configuration (after making necessary adjustments). If the taint is not removed, terraform will destroy and recreate the resource.

Note: Either protection_domain_name or protection_domain_id is required. But not both.

Example Usage

/*
Copyright (c) 2023-2026 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# terraform init && terraform plan && terraform apply
# Create, Update, Delete is supported for this resource
# To import , check storagepool_resource_import.tf for more info
# To create / update, either protection_domain_id or protection_domain_name must be provided
# name and media_type is the required parameter to create or update
# other  atrributes like : use_rmcache, use_rfcache, replication_journal_capacity, capacity_alert_high_threshold, capacity_alert_critical_threshold etc. are optional 
# To check which attributes of the storage pool can be updated, please refer Product Guide in the documentation

# Example for creating storage pool. After successful execution, storage pool will be created under a specified protection domain.
resource "powerflex_storage_pool" "sp" {
  name                         = "newstoragepool"
  protection_domain_name       = "domain1"
  media_type                   = "HDD" # HDD/SSD/Transitional
  use_rmcache                  = false
  use_rfcache                  = true
  replication_journal_capacity = 34
  zero_padding_enabled         = false
  rebalance_enabled            = false

  # Alert Thresholds
  # Critical threshold must be greater than high threshold
  capacity_alert_high_threshold     = 66
  capacity_alert_critical_threshold = 77

  # Protected Maintenance Mode Parameters
  # When the policy is set to "favorAppIos", then concurrent IOs and bandwidth limit can be set.
  # When the policy is set to "limitNumOfConcurrentIos", then only concurrent IOs can be set.
  # When the policy is set to "unlimited", then concurrent IOs and bandwidth limit can't be set.
  protected_maintenance_mode_io_priority_policy               = "favorAppIos" # favorAppIos/limitNumOfConcurrentIos/unlimited
  protected_maintenance_mode_num_of_concurrent_ios_per_device = 7
  protected_maintenance_mode_bw_limit_per_device_in_kbps      = 1028

  # Rebalance Parameters
  # When the policy is set to "favorAppIos", then concurrent IOs and bandwidth limit can be set.
  # When the policy is set to "limitNumOfConcurrentIos", then only concurrent IOs can be set.
  # When the policy is set to "unlimited", then concurrent IOs and bandwidth limit can't be set.  
  rebalance_io_priority_policy               = "favorAppIos" # favorAppIos/limitNumOfConcurrentIos/unlimited
  rebalance_num_of_concurrent_ios_per_device = 7
  rebalance_bw_limit_per_device_in_kbps      = 1032

  #VTree Migration Parameters
  # When the policy is set to "favorAppIos", then concurrent IOs and bandwidth limit can be set.
  # When the policy is set to "limitNumOfConcurrentIos", then only concurrent IOs can be set.
  vtree_migration_io_priority_policy               = "favorAppIos" # favorAppIos/limitNumOfConcurrentIos
  vtree_migration_num_of_concurrent_ios_per_device = 7
  vtree_migration_bw_limit_per_device_in_kbps      = 1030


  spare_percentage              = 66
  rm_cache_write_handling_mode  = "Passthrough"
  rebuild_enabled               = true
  rebuild_rebalance_parallelism = 5
  fragmentation                 = false
}

output "created_storagepool" {
  value = powerflex_storage_pool.sp
}

After the execution of above resource block, storage pool would have been created on the PowerFlex array. For more information, please check the terraform state file.

Schema

Required

media_type (String) Media Type of the storage pool. Valid values are HDD, SSD and Transitional
name (String) Name of the Storage pool

Optional

capacity_alert_critical_threshold (Number) Set the threshold for triggering capacity usage critical-priority alert.
capacity_alert_high_threshold (Number) Set the threshold for triggering capacity usage high-priority alert.
compression_method (String) Compression method for the Storage Pool (Gen2 5.x only). Valid values: None, Normal.
device_group_id (String) Device Group ID for the Storage Pool (Gen2 5.x only). Replaces direct device assignment.
erasure_coding_policy (String) Erasure Coding policy for the Storage Pool (Gen2 5.x only). Valid values: none, rs_2_1, rs_4_1.
fragmentation (Boolean) Enable or disable fragmentation in the Storage Pool
protected_maintenance_mode_bw_limit_per_device_in_kbps (Number) The maximum bandwidth of protected maintenance mode migration I/Os, in KB per second, per device
protected_maintenance_mode_io_priority_policy (String) Set the I/O priority policy for protected maintenance mode for a specific Storage Pool. Valid values are unlimited, limitNumOfConcurrentIos and favorAppIos
protected_maintenance_mode_num_of_concurrent_ios_per_device (Number) The maximum number of concurrent protected maintenance mode migration I/Os per device
protection_domain_id (String) ID of the Protection Domain under which the storage pool will be created. Conflicts with protection_domain_name. Cannot be updated.
protection_domain_name (String) Name of the Protection Domain under which the storage pool will be created. Conflicts with protection_domain_id. Cannot be updated.
protection_scheme (String) Protection scheme for the Storage Pool (Gen2 5.x only). Valid values: TwoPlusTwo, EightPlusTwo.
rebalance_bw_limit_per_device_in_kbps (Number) The maximum bandwidth of rebalance I/Os, in KB/s, per device
rebalance_enabled (Boolean) Enable or disable rebalancing in the specified Storage Pool
rebalance_io_priority_policy (String) Policy to use for rebalance I/O priority. Valid values are unlimited, limitNumOfConcurrentIos and favorAppIos
rebalance_num_of_concurrent_ios_per_device (Number) The maximum number of concurrent rebalance I/Os per device
rebuild_enabled (Boolean) Enable or disable rebuilds in the specified Storage Pool
rebuild_rebalance_parallelism (Number) Maximum number of concurrent rebuild and rebalance activities on SDSs in the Storage Pool
replication_journal_capacity (Number) This defines the maximum percentage of Storage Pool capacity that can be used by replication for the journal. Before deleting the storage pool, this has to be set to 0.
rm_cache_write_handling_mode (String) Sets the Read RAM Cache write handling mode of the specified Storage Pool
spare_percentage (Number) Sets the spare capacity reservation policy
use_rfcache (Boolean) Enable/Disable RFcache on a specific storage pool
use_rmcache (Boolean) Enable/Disable RMcache on a specific storage pool
vtree_migration_bw_limit_per_device_in_kbps (Number) The maximum bandwidth of V-Tree migration IOs, in KB per second, per device
vtree_migration_io_priority_policy (String) Set the I/O priority policy for V-Tree migration for a specific Storage Pool. Valid values are limitNumOfConcurrentIos and favorAppIos
vtree_migration_num_of_concurrent_ios_per_device (Number) The maximum number of concurrent V-Tree migration I/Os per device
zero_padding_enabled (Boolean) Enable/Disable padding policy on a specific storage pool

Read-Only

id (String) ID of the Storage pool

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2023-2026 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import storage pool by it's id
terraform import powerflex_storage_pool.storage_pool_import_by_id "<id>"

This will import the storage pool instance with specified ID into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_storage_pool_erasure_coding_v2 resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_storage_pool_erasure_coding_v2 (Resource)

This resource is used to configure Erasure Coding policy on Storage Pools for PowerFlex Gen2 systems (5.0+).

Example Usage

/*
Copyright (c) 2024-2026 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied
See the License for the specific language governing permissions and
limitations under the License.
*/

# Commands to run this tf file : terraform init && terraform plan && terraform apply
# This resource configures Erasure Coding policy on Storage Pools (Gen2 systems 5.0+)
# storage_pool_id and erasure_coding_policy are required
# Valid erasure_coding_policy values: none, rs_2_1, rs_4_1

# Example: Set Erasure Coding policy to rs_2_1
resource "powerflex_storage_pool_erasure_coding_v2" "rs2_1" {
  storage_pool_id       = "0123456789abcdef"
  erasure_coding_policy = "rs_2_1"
}

# Example: Set Erasure Coding policy to rs_4_1
resource "powerflex_storage_pool_erasure_coding_v2" "rs4_1" {
  storage_pool_id       = "0123456789abcdef"
  erasure_coding_policy = "rs_4_1"
}

# Example: Disable Erasure Coding (set to none)
resource "powerflex_storage_pool_erasure_coding_v2" "none" {
  storage_pool_id       = "0123456789abcdef"
  erasure_coding_policy = "none"
}

output "erasure_coding" {
  value = powerflex_storage_pool_erasure_coding_v2.rs2_1
}

Schema

Required

erasure_coding_policy (String) The erasure coding policy to set. Valid values: none, rs_2_1, rs_4_1.
storage_pool_id (String) The ID of the storage pool to configure erasure coding on.

Read-Only

id (String) The identifier for this resource.

V1.9.0: powerflex_system resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_system (Resource)

This resource is used to manage the cluster level operations of the PowerFlex Array. This resource supports Create, Update and Delete operations.

Example Usage

/*
Copyright (c) 2024 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Command to run this tf file : terraform init && terraform plan && terraform apply
# Create, Update, Delete is supported for this resource
# To import, check import.sh for more info
# restricted_mode is the required parameter

resource "powerflex_system" "test" {
  restricted_mode = "Guid"
  sdc_approved_ips = [
    {
      id  = "sdc_id1"
      ips = ["sdc_ip1", "sdc_ip2"]
    },
    {
      id  = "sdc_id2"
      ips = ["sdc_ip3"]
    },
  ]
}

After the execution of above resource block, system would have been created on the PowerFlex array. For more information, please check the terraform state file.

Schema

Required

restricted_mode (String) Restricted mode of the cluster. Accepted values are None, Guid, ApprovedIp.

Optional

sdc_approved_ips (Attributes List) Specifies list of SDC IPs. (see below for nested schema)
sdc_guids (List of String) Specifies list of SDC GUIDs.
sdc_ids (List of String) Specifies list of SDC IDs.
sdc_names (List of String) Specifies list of SDC names.

Read-Only

id (String) System ID

Nested Schema for `sdc_approved_ips`

Required:

id (String) SDC ID.
ips (Set of String) SDC IPs.

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2024 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import system
terraform import powerflex_system.test ""

# Another way to import system using system ID
terraform import powerflex_system.test "system_id"

This will import the system instance with specified ID into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_template_clone resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_template_clone (Resource)

This resource is only used to clone a template using the original template ID from the template needing to be cloned, with a unique name for the cloned template.

Example Usage

/*
Copyright (c) 2025-2026 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# terraform init && terraform plan && terraform apply
# Create, and read is supported for this resource

//gets original template id from sample templates
data "powerflex_template" "template" {
  filter {
    category = ["Sample Templates"]
  }
}

resource "powerflex_template_clone" "example" {
  template_name        = "Template Clone"
  original_template_id = data.powerflex_template.template.template_details[0].original_template_id
}

After the execution of above resource block, the Template will be cloned. For more information, please check the terraform state file.

Schema

Required

original_template_id (String) Template Clone Resources’s original template ID derived from the template needing to be cloned.
template_name (String) Template Clone Resources’s unique template name for the cloned template.

V1.9.0: powerflex_user resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_user (Resource)

This resource is used to manage the User entity of the PowerFlex Array. We can Create, Update and Delete the user using this resource. We can also import an existing user from the PowerFlex array.

Example Usage

/*
Copyright (c) 2023-2026 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# terraform init && terraform plan && terraform apply
# Create, Update, Delete is supported for this resource
# Import is supported.

# Example for creating user. After successful execution, user will be created with Monitor role. Below example works for PowerFlex version 3.6.
resource "powerflex_user" "newUser" {

  # name, role and password is the required parameter to create or update. Only role can be updated.
  name     = "terraform"
  role     = "Monitor" # Administrator/Monitor/Configure/Security/FrontendConfig/BackendConfig
  password = "Password"
}

# Example for creating user. After successful execution, user will be created with SystemAdmin role. Below example works for PowerFlex version 4.5.
resource "powerflex_user" "newUser" {

  # name, role and password is the required parameter to create or update. first_name and last_name are optional parameters in PowerFlex version 4.5.
  name     = "terraform"
  role     = "SystemAdmin" # Monitor/SuperUser/SystemAdmin/StorageAdmin/LifecycleAdmin/ReplicationManager/SnapshotManager/SecurityAdmin/DriveReplacer/Technician/Support
  password = "Password123@"
}

# Example for creating user. After successful execution, user will be created with LifecycleAdmin role. Below example works for PowerFlex version 4.6.
resource "powerflex_user" "test" {
  name       = "terraform"
  role       = "LifecycleAdmin" # Monitor/SuperUser/SystemAdmin/StorageAdmin/LifecycleAdmin/ReplicationManager/SnapshotManager/SecurityAdmin/DriveReplacer/Technician/Support
  password   = "Password123@"
  first_name = "terraform"
  last_name  = "terraform"
}

After the execution of above resource block, new user would have been created on the PowerFlex array. For more information, please check the terraform state file.

Schema

Required

name (String) The name of the user. For PowerFlex version 3.6, cannot be updated.
password (String, Sensitive) Password of the user. For PowerFlex version 3.6, cannot be updated.
role (String) The role of the user. Accepted values for PowerFlex version 3.6 ‘Administrator’, ‘Monitor’, ‘Configure’, ‘Security’, ‘FrontendConfig’, ‘BackendConfig’. Accepted values for PowerFlex version 4.5 are ‘Monitor’, ‘SuperUser’, ‘SystemAdmin’, ‘StorageAdmin’, ‘LifecycleAdmin’, ‘ReplicationManager’, ‘SnapshotManager’, ‘SecurityAdmin’, ‘DriveReplacer’, ‘Technician’, ‘Support’.

Optional

first_name (String) First name of the user. PowerFlex version 3.6 does not support the first_name attribute. It is mandatory for PowerFlex version 4.6.
last_name (String) Last name of the user. PowerFlex version 3.6 does not support the last_name attribute. It is mandatory for PowerFlex version 4.6.

Read-Only

id (String) The ID of the user.
system_id (String) The ID of the system.

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2023-2026 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import user by it's id
terraform import powerflex_user.user_import_by_id "<id>"

# import user by it's id - alternative approach by prefixing it with "id:"
terraform import powerflex_user.user_import_by_id "<id:id_of_the_user>"

# import user by it's name
terraform import powerflex_user.user_import_by_name "<name:name_of_the_user>"

This will import the User instance with specified ID into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_volume resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_volume (Resource)

This resource is used to manage the Volume entity of the PowerFlex Array. We can Create, Update and Delete the volume using this resource. We can also import an existing volume from the PowerFlex array.

Caution: Volume creation or update is not atomic. In case of partially completed create operations, terraform can mark the resource as tainted. One can manually remove the taint and try applying the configuration (after making necessary adjustments). If the taint is not removed, terraform will destroy and recreate the resource.

Note: Either protection_domain_name or protection_domain_id is required. But not both. Note: Either storage_pool_name or storage_pool_id is required. But not both.

Example Usage

/*
Copyright (c) 2023-2024 Dell Inc., or its subsidiaries. All Rights Reserved.

Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://mozilla.org/MPL/2.0/


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Command to run this tf file : terraform init && terraform plan && terraform apply
# Create, Update, Delete is supported for this resource
# To import , check import.sh for more info
# name, size is the required parameter to create or update
# other  atrributes like : capacity_unit, volume_type, use_rm_cache, compression_method, access_mode, remove_mode are optional 
# To check which attributes of the volume can be updated, please refer Product Guide in the documentation

# Example for creating volume. After successful execution, volume will be created with 8 GB size.
resource "powerflex_volume" "avengers-volume-create" {
  name = "avengers-volume-create"

  # To create / update, either protection_domain_id or protection_domain_name must be provided
  protection_domain_name = "domain1"

  # To create / update, either storage_pool_id or storage_pool_name must be provided
  storage_pool_name = "pool1"

  # The unit of size of the volume is defined by capacity_unit whose default value is "GB".
  size          = 8
  capacity_unit = "GB" # GB/TB

  use_rm_cache = true
  volume_type  = "ThickProvisioned"      # ThickProvisioned/ThinProvisioned volume type
  access_mode  = "ReadWrite"             # ReadWrite/ReadOnly volume access mode
  remove_mode  = "INCLUDING_DESCENDANTS" # INCLUDING_DESCENDANTS/ONLY_ME remove mode
}

After the execution of above resource block, volume would have been created on the PowerFlex array. For more information, please check the terraform state file.

Schema

Required

name (String) The name of the volume.
size (Number) Size of the volume. The unit of size is defined by capacity_unit. The storage capacity of a volume must be a multiple of 8GB and cannot be decreased.

Optional

access_mode (String) The Access mode of the volume. Valid values are ReadOnly and ReadWrite. Default value is ReadOnly.
capacity_unit (String) Unit of capacity of the volume. Must be one of GB and TB. Default value is GB.
compression_method (String) Compression Method of the volume. Valid values are None and Normal.
protection_domain_id (String) ID of the Protection Domain under which the volume will be created. Conflicts with protection_domain_name. Cannot be updated.
protection_domain_name (String) Name of the Protection Domain under which the volume will be created. Conflicts with protection_domain_id. Cannot be updated.
remove_mode (String) Remove mode of the volume. Valid values are ONLY_ME and INCLUDING_DESCENDANTS. Default value is ONLY_ME.
storage_pool_id (String) ID of the Storage Pool under which the volume will be created. Conflicts with storage_pool_name. Cannot be updated.
storage_pool_name (String) Name of the Storage Pool under which the volume will be created. Conflicts with storage_pool_id. Cannot be updated.
use_rm_cache (Boolean) use rm cache
volume_type (String) Volume type. Valid values are ThickProvisioned and ThinProvisioned. Default value is ThinProvisioned.

Read-Only

id (String) The ID of the volume.
size_in_kb (Number) Size in KB

Import

Import is supported using the following syntax:

# /*
# Copyright (c) 2023-2024 Dell Inc., or its subsidiaries. All Rights Reserved.
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://mozilla.org/MPL/2.0/
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# */

# import volume by it's id
terraform import powerflex_volume.volume_import_by_id "<id>"

This will import the volume instance with specified ID into your Terraform state.
After successful import, you can run terraform state list to ensure the resource has been imported successfully.
Now, you can fill in the resource block with the appropriate arguments and settings that match the imported resource’s real-world configuration.
Execute terraform plan to see if your configuration and the imported resource are in sync. Make adjustments if needed.
Finally, execute terraform apply to bring the resource fully under Terraform’s management.
Now, the resource which was not part of terraform became part of Terraform managed infrastructure.

V1.9.0: powerflex_volume_action_v2 resource

Mon, 01 Jan 0001 00:00:00 +0000

powerflex_volume_action_v2 (Resource)

This resource performs actions on volumes for PowerFlex Gen2 systems (5.0+). Supported actions: refresh, restore, map_to_host, unmap_from_host.

Example Usage

# Copyright (c) 2024-2026 Dell Inc., or its subsidiaries. All Rights Reserved.
#
# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     http://mozilla.org/MPL/2.0/
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# Refresh volume metadata
resource "powerflex_volume_action_v2" "refresh" {
  volume_id = "vol-abc123"
  action    = "refresh"
}

# Restore volume from a snapshot
resource "powerflex_volume_action_v2" "restore" {
  volume_id          = "vol-abc123"
  action             = "restore"
  source_snapshot_id = "snap-def456"
}

# Map a volume to a host with read-write access
resource "powerflex_volume_action_v2" "map" {
  volume_id   = "vol-abc123"
  action      = "map_to_host"
  host_id     = "host-ghi789"
  access_mode = "READ_WRITE"
}

# Unmap a volume from a host
resource "powerflex_volume_action_v2" "unmap" {
  volume_id = "vol-abc123"
  action    = "unmap_from_host"
  host_id   = "host-ghi789"
}

Schema

Required

action (String) The action to perform. Valid values: refresh, restore, map_to_host, unmap_from_host.
volume_id (String) The ID of the volume to perform the action on.

Optional

access_mode (String) Access mode for map_to_host action. Valid values: READ_ONLY, READ_WRITE.
host_id (String) Host ID for map_to_host and unmap_from_host actions.
source_snapshot_id (String) Source snapshot ID for restore action.

Read-Only

id (String) The identifier for this resource.

Dell Technologies – Resources

V1.9.0: powerflex_cluster resource

powerflex_cluster (Resource)

Example Usage

Schema

Required

Optional

Read-Only

Nested Schema for cluster

Nested Schema for storage_pools

Nested Schema for mdm_list

Nested Schema for protection_domains

Nested Schema for protection_domains.storage_pool_list

Nested Schema for sdc_list

Nested Schema for sdr_list

Nested Schema for sds_list

Nested Schema for sds_list.devices

Nested Schema for sdt_list

Import

V1.9.0: powerflex_compatibility_management resource

powerflex_compatibility_management (Resource)

Example Usage

Schema

Required

Read-Only

V1.9.0: powerflex_device resource

powerflex_device (Resource)

Example Usage

Schema

Required

Optional

Read-Only

Import

V1.9.0: powerflex_device_action_v2 resource

powerflex_device_action_v2 (Resource)

Example Usage

Schema

Required

Optional

Read-Only

V1.9.0: powerflex_device_group_v2 resource

powerflex_device_group_v2 (Resource)

Example Usage

Schema

Required

Optional

Read-Only

V1.9.0: powerflex_fault_set resource

powerflex_fault_set (Resource)

Example Usage

Schema

Required

Read-Only

Import

V1.9.0: powerflex_firmware_repository resource

powerflex_firmware_repository (Resource)

Example Usage

Schema

Required

Optional

Read-Only

Import

V1.9.0: powerflex_mdm_cluster resource

powerflex_mdm_cluster (Resource)

Example Usage

Schema

Required

Optional

Read-Only

Nested Schema for primary_mdm

Nested Schema for secondary_mdm

Nested Schema for tiebreaker_mdm

Nested Schema for standby_mdm

V1.9.0: powerflex_nvme_host resource

powerflex_nvme_host (Resource)

Example Usage

Schema

Required

Optional

Read-Only

Nested Schema for `cluster`

Nested Schema for `storage_pools`

Nested Schema for `mdm_list`

Nested Schema for `protection_domains`

Nested Schema for `protection_domains.storage_pool_list`

Nested Schema for `sdc_list`

Nested Schema for `sdr_list`

Nested Schema for `sds_list`

Nested Schema for `sds_list.devices`

Nested Schema for `sdt_list`

Nested Schema for `primary_mdm`

Nested Schema for `secondary_mdm`

Nested Schema for `tiebreaker_mdm`

Nested Schema for `standby_mdm`

Nested Schema for `ip_list`

Nested Schema for `package_details`

Nested Schema for `destination_primary_mdm_information`

Nested Schema for `source_primary_mdm_information`

Nested Schema for `links`