Customer Driven Purity Upgrades for Everpure Cloud Dedicated for AWS

Everpure Cloud Dedicated for AWS

Audience

Public

Technology Integrations

Amazon Web Services (AWS)

Source Type

Documentation

In version 6.6.6 of Everpure Cloud Dedicated for AWS, a new feature allows customers to upgrade to a new version of Purity without needing to contact Everpure support. The upgrade process is seamless and can be performed via the Everpure CLI or REST API. This KB article will guide you through the steps to set up an Everpure Cloud Dedicated array for Customer-Driven Upgrades (CDUs) and the process for executing an upgrade.

Note: If a Everpure Cloud Dedicated array is running non-reducible workloads (workloads with data reduction ratio of 1:1) with smaller block size (e.g. 4k, 32k), please refer to the following article before upgrading the Array to Everpure Cloud Dedicated Purity Version 6.8.6 or higher - go to article

There are a few important notes and caveats to be aware of for Customer-Driven Upgrades:

Beginning with Purity version 6.6.6, the methodology described here is the supported upgrade path for all Everpure Cloud Dedicated upgrades.
Customers can request that their upgrade be executed by Everpure Technical Services as before via opening a ticket with Everpure Technical Services.
If a Purity upgrade being driven by the customer experiences a failure on the Everpure Cloud Dedicated, automatic rollback is not supported via CDU. In the event this occurs, please open a ticket with Everpure Technical Services for assistance.
Customer-Driven Upgrades are not supported with ActiveCluster. If you are using ActiveCluster in your Everpure Cloud Dedicated setup, please reach out to Everpure Technical Services for assistance.

Important: Do not use the reconfigure_paws.py script without EE/ENG approval. Please open a ES JIRA, input your analysis then escalate to request approval from the Escalation Engineering and Everpure Cloud Dedicated Engineering teams to use the script.

Important: Double-check the Auto Download feature is disable in the Everpure Cloud Dedicated GUI under Settings > Software.

Log in to the CLI for your Everpure Cloud Dedicated instance using an SSH utility like PuTTY.

If you deployed Everpure Cloud Dedicated with an SSH key, you can use that key to log in as pureuser. Alternatively, you can create an array administrator role on Everpure Cloud Dedicated under Settings > Access and use the username and password combination to log in, or an SSH key.

Run the following command to see what Purity versions are available to upgrade to:

puresw list --catalog

Example output:


Name        Release Family  Version    Upgrade Path      Details
Purity//FA  6.6             6.6.8      6.6.7->6.6.8         -

Download the desired version of Purity to the array. This typically takes about 5 minutes to complete. In the below example, we are downloading Purity version 6.6.8:

puresw download --version 6.6.8 Purity//FA

Example output:

Name        Version   Status  Progress  Details
Purity//FA  6.6.8     new     -         Pure1 cloud is building upgrade package. This will take up to 5 minutes to complete.

Optionally, run a check to confirm that the Everpure Cloud Dedicated array has all the required prerequisites for the upgrade to be successful. To run that check, execute the following command:
```
puresw upgrade start --mode check-only --version 6.6.8 Purity//FA
```
Status of an upgrade or an upgrade check can be seen by executing the following command:
```
puresw list
```
If a check fails, Everpure Cloud Dedicated will output an error message. Below is an example of the error message you will can receive as an example:
You can see further details about a failed upgrade check by running:
```
puresw upgrade show-step-detail
```

There are a few different modes to be aware of when upgrading. Note that all modes will execute pre-checks prior to execution and provide a warning if a pre-check fails.

The below code samples show a specific version of Purity (6.6.8). You will need to replace this variable with the specific version of Purity you are upgrading to.

Important: one-click upgrade mode is deprecated and will be removed in future versions. Please don't use this mode anymore.

Interactive upgrade mode - should be utilized when the customer wishes to watch the upgrade closely and provide responses at different stages of the upgrade for it to proceed.
```
puresw upgrade start --mode interactive --version 6.6.8 Purity//FA
```
Interactive mode progress can be queried by running the puresw list command. At a few certain points in the upgrade process, you will be prompted to execute a command in order to continue the upgrade process.
Semi-interactive upgrade mode - it will pause in case of the upgrade checks fail and will require user interaction in order to proceed. When the upgrade is paused, semi-interactive mode acts like interactive mode unless the user retries a step, in which case the upgrade continues automatically if no checks fail.
```
puresw upgrade start --mode semi-interactive --version 6.6.8 Purity//FA
```
Semi-interactive mode progress can be queried by running the puresw list command.

Note: Please note that during a Purity upgrade, all VDrives are upgraded one by one in a non-disruptive way. This operation can take longer, the progress of upgrading VDrives can be monitored via puresw CLI command:

puresw upgrade list --name Purity//FA --nvp
[{'Software Name': 'Purity//FA', 'Plan': '6.8.3->6.10.0', 'Mode': 'interactive', 'Start Time': '1756603201018', 'End Time': '', 'Current Step ID': '02bd8e8a-4f4a-4484-bd7e-d8eafe2c2930', 'Status': 'installing', 'Progress': '0.16', 'Details': 'Waiting for firmware upgrade of virtual drives to finish - 0/7 done'}]
...
puresw upgrade list --name Purity//FA --nvp
[{'Software Name': 'Purity//FA', 'Plan': '6.8.3->6.10.0', 'Mode': 'interactive', 'Start Time': '1756603201018', 'End Time': '', 'Current Step ID': '02bd8e8a-4f4a-4484-bd7e-d8eafe2c2930', 'Status': 'installing', 'Progress': '0.45', 'Details': 'Waiting for firmware upgrade of virtual drives to finish - 6/7 done'}]
...