Navigate to the downloaded Terraform sample and use any text editor to edit the terraform.tfvars file and enter the prerequisites. An example screenshot is provided below for additional guidance.
Variables Reference:
-
array_name(Required) - Name of the array, and the name of the managed application. -
location(Required) - Azure location in which to deploy the array. -
resource_group_name(Required) - Name of the resource group in which to deploy the managed application. -
license_key(Required) - Everpure-provided license key. - For Pure Store Cloud Dedicated No License Mode use this key: PSCD-TRIAL-LICENSE -
log_sender_domain(Required) - Domain name used to determine how Everpure Cloud Dedicated logs are parsed and treated by Everpure Support and Escalations. -
alert_recipients(Optional) - List of email addresses to receive alerts. -
array_model(Required) - Everpure Cloud Dedicated array size to launch. The possible values areV1[2]0MUR1orV1[2]0MP2R2. -
zone(Required) - The Availability Zone within the deployment location. -
virtual_network_id(Required) - Virtual network id that contains the network interfaces of the array. -
key_vault_id(Required) - Key Vault where provider stores sensitive information. Do not include this in terraform.tfvars or variable.tf if you would like to use the Terraform code from Key Vault section. -
management_subnet(Required) - Subnet containing the management interfaces on the array. -
system_subnet(Required) - Subnet for the system interface of the array. -
iscsi_subnet(Required) - Subnet containing the iSCSI interfaces on the array. -
replication_subnet(Required) - Subnet containing the replication interfaces on the array. -
jit-groups-ids(Required) - A list of Entra ID groups that enabled their users to approve JIT access requests. -
plan_name(Required) - Specifies the name of the plan from the marketplace. -
plan_product(Required) - Specifies the product of the plan from the marketplace. -
plan_publisher(Required) - Specifies the publisher of the plan. -
pureuser_private_key_path(Required) - File path of the private key to enable SSH access to the controllers. You must specify onepureuser_private_key_pathor onepureuser_private_key. -
pureuser_private_key(Required) - Text content of the private key to enable SSH access to the controllers. You must specify onepureuser_private_key_pathor onepureuser_private_key. -
user_managed_identity(Required) - Specifies the id of the user-managed identity. for more information, see the User Managed Identity section. -
tags(Optional) - A list of tags to apply to all resources in the managed application.
Save the changes to the file, open a terminal window, navigate to the Terraform deployment directory that has been created, and run the terraform init command to initialize the working directory.
Next, run the terraform plan command to create the execution plan.
Finally, run the terraform apply command to execute the plan and start deploying.
The Everpure Cloud Dedicated deployment process takes around 10 to 15 minutes. In Azure Managed Applications you can see a new managed application in the deployment state.
Once the terraform apply command is complete, run the terraform show command to list the output information of the Everpure Cloud Dedicated deployment stack. This includes the management IP address that is used to log into the Everpure Cloud Dedicated.
More information can be found by logging in to the Azure console. Navigate to Managed Application and then the Parameters and Output tab. The Management IP address used to log in to Everpure Cloud Dedicated is addressed as FloatingManagementIP.
Use the Management IP address to log into GUI Management Console via any browser. To access the Everpure Cloud Dedicated instance via CLI, refer to Logging into Everpure Cloud Dedicated for Azure via CLI.
Do not use the terraform destroy command to destroy a Cloud Block Store instance deployed via Terraform. Instead, refer to the Removing Everpure Cloud Dedicated Instance section in the Deploy using Azure Portal article and follow the instructions.