Deploy using Azure Portal | Pure CBS on Azure
Deploying Cloud Block Store
The following steps will provide guidance on deploying a Cloud Block Store managed application using the the Azure Portal GUI.
See this list of supported regions to confirm Cloud Block Store availability.
To deploy Cloud Block Store using the Azure CLI, see steps in the Cloud Block Store Deployment and Configuration Guide for Azure using Azure CLI KB article.
To deploy Cloud Block Store using Terraform, see steps in the Cloud Block Store Deployment with Terraform KB article.
Note: The followings steps reflects deployment of Cloud Block Store versions 6.1.4 or higher which no longer deploys a public load balancer. Therefore it is mandatory that there is internet access for the Cloud Block Store system network interface in order to successfully deploy. See the Internet Access section within the prerequisites KB article.
Deploy Cloud Block Store from the Azure Marketplace.
1. Log into the Azure “Marketplace”.
2. In the Marketplace search bar, search for “cloud block store”.
3. Click on the Pure Cloud Block Store (Product Deployment) tile. Note that the subscription listing is used for purchasing licenses.
4. Click Create.
5. Complete the required fields. An example screenshot is provided for additional guidance below.
a. Select the desired Subscription.
b. Select the desired Resource group in which you want the Cloud Block Store managed application to reside.
c. Select the desired Region you want to deploy your Cloud Block Store managed application.
Note: It is highly suggested that this region matches the region of your Resource Group in selection b. The deployment may occasionally fail if they do not match.
d. Select the desired Cloud Block Store model.
e. Select the desired Availability Zone.
Note: Some zones may not have the required Azure backend storage available, which is required for Cloud Block Store. To find out which zone in your specific Azure subscription has Ultra SSDs (for V20MUR2 and V10MUR2 CBS Model) or Premium V2 SSD (for V20P2R2 CBS Model), run the following command from the Azure CloudShell or locally with Azure login to your subscription:
For Ultra SSDs (for V20MUR2 and V10MUR2 CBS Model)
- Azure PowerShell
Get-AzComputeResourceSku | where {$_.ResourceType -eq “disks” -and $_.Name -eq “UltraSSD_LRS”}
- Azure CLI
az vm list-skus --resource-type disks --query "[?name=='UltraSSD_LRS'].{Region:locationInfo[0].location, Zones:locationInfo[0].zones}"
Premium V2 SSD (for V20P2R2 CBS Model)
- Azure PowerShell
Get-AzComputeResourceSku | where {$_.ResourceType -eq “disks” -and $_.Name -eq “PremiumV2_LRS”}
- Azure CLI
az vm list-skus --resource-type disks --query "[?name=='PremiumV2_LRS'].{Region:locationInfo[0].location, Zones:locationInfo[0].zones}"
f. Enter the desired Array Name for the Cloud Block Store VM instance.
g. Enter your Company Domain Name. This can be changed later.
Example: purestorage.com
h. Enter the Cloud Block Store License key.
g. (Optional) Enter comma separated email addresses of recipients who wish to receive Purity alerts.
h. (Optional) If you wish to log in via SSH with the default pureuser username, an SSH public key can be provided here.
Note: Alternatively, after deployment you can also log into the Cloud Block Store GUI (HTTPS) and manually add the SSH key to the desired user login.
i. (Optional) If you intend to use this CBS Array with Fusion, check this box.
Read this article for guidance on deploying CBS Arrays for Fusion in Azure.
j. Enter the desired Application Name of your Cloud Block Store managed application.
k. (Optional) You can change the name of the Managed Resource Group if desired.
Example:
6. Click Next: Managed Identity.
7. Enter the User Managed Identity Resource Id created for the array. The steps on how to create, assign roles, and get the resource Id are under Prerequisites section.
8. Click Next: Network.
9. Complete the Network fields. Cloud Block Store has four network interfaces (system, management, iSCSI, replication) and will need a Virtual Network (VNet) and subnet assigned.
Note:
- You must select the same VNet for all four interfaces. However, the interfaces can reside in the same or different subnet within the VNET. See the Networking Prerequisites article for network option diagrams in the prerequisites document.
- Ensure the subnet you select for the System interface has internet access. Example via NAT Gateway or Azure Firewall. See network Internet Access section in the prerequisites document for options to configure internet access.
10. Click Next: Tags.
11. Add any desired tags for this deployment.
12. Click Next: JIT Configuration.
13. Ensure that you select Yes to enable Just in Time (JIT) remote access. (MANDATORY)
This is a mandatory requirement to ensure JIT access is enabled. Without JIT, your CBS instance cannot be Non-disruptively Upgraded (NDU).
You cannot change this option once it is set so it is very important that it is enabled at deployment.
14. Optionally click on the Customized JIT configuration button. This option allows you to select additional users or groups of users who can approve Just in Time (JIT) requests from Pure Support.
- Select Manual mode
- Click Add Approver
c. On the right-hand side, search and select user(s) whom you wish to be approvers for JIT requests from Pure Support.
d. Click Save.
15. Click Next: Review + create.
16. Read and check the box to acknowledge the terms and conditions.
17. Review your parameters and click Create.
18. Cloud Block Store will now be deployed into your desired resource group, VNet, and subnets. The deployment should be completed within 20 minutes depending on the region.
Note: It may take a few minutes after deployment completes for the Cloud Block Store to initialize and be ready.
Removing Cloud Block Store
To properly terminate and remove a Cloud Block Store instance, run the two CLI commands provided below. The proper steps will ensure that the Cloud Block Store instance removal is reflected accurately and accounted for in the Pure-as-a-Service subscription on Pure1.
Prerequisites:
- All Cloud Block Store volumes and snapshots must be deleted and eradicated prior to termination of a Cloud Block Store instance. This includes Protection Group snapshots.
- All connected arrays and targets must be disconnected from any type of Purity replication.
- Cloud Block Store instance must able to phone home. This ensures the Cloud Block Store instance is properly de-registered in the Pure-as-a-Service subscription.
Once the prerequisite array state has been achieved, the following steps will terminate and remove the Cloud Block Store instance.
- Using SSH, log into the Cloud Block Store instance management port.
Note: See the Viewing the Cloud Block Store IP Addresses in Azure Portal section for the management port IP address.
- Run the following command:
purearray factory-reset-token create
Example
purearray factory-reset-token create Name Token MyCloudBlockStore 4109498
- A token will be provided in the output. Make a note of the token value.
- Run the following command with the token from the previous command.
purearray erase --factory-reset-token <token> --eradicate-all-data
This allows the Cloud Block Store instance to communicate with Pure1 prior to deleting itself.
Example
purearray erase --factory-reset-token 4109498 --eradicate-all-data Name MyCloudBlockStore
- Important: Wait about 5 minutes and proceed delete the Cloud Block Store managed application.
Note: Cloud Block Store manage application deletion takes about 10-15 minutes to completely remove all the underlying resources.
For new arrays deployed with version 6.4+
In version 6.4, Pure has introduced auto-on SafeMode™ protection for volumes on a new array. This would prevent removing all the objects protected by default in the array. Therefore, customers can only perform CBS deletion with Pure Support involvement.
The screenshot below shows the Default Protection Groups under Protection > Array.
You can see that the default protection group pgroup-auto is ratcheted.
Prerequisites before requesting Pure support:
- All Cloud Block Store volumes and snapshots must be deleted and eradicated prior to termination of a Cloud Block Store instance. This includes Protection Group snapshots. Note: you won't be able to eradicate snapshots under the default
pgourp-autoor destroy the protection group itself. - All connected arrays and targets must be disconnected from any type of Purity replication.
- Cloud Block Store instance must be able to phone home. This ensures the Cloud Block Store instance is properly de-registered in the Pure-as-a-Service subscription.
- The last step is to enable Remote Assist.
Once the prerequisite array state has been achieved, request Pure Support and ask for decommissioning the array.