Everpure Cloud Dedicated Release Notes v6.8.2

Overview

Replacing CosmosDB component with Table Storage in Azure Storage
New maximum capacity for V10 model

Azure Storage Account Changes

Starting with Everpure Cloud Dedicated version 6.8.2, we are replacing the CosmosDB database component in Everpure Cloud Dedicated on Azure with an Azure Table Storage component.This architectural update will lower costs for all Everpure Cloud Dedicated arrays and facilitate Everpure Cloud Dedicated deployments in highly utilized Azure regions, even when CosmosDB resources may be temporarily unavailable due to capacity constraints.

Starting with version 6.6.10, Everpure Cloud Dedicated arrays have utilized an Azure Storage Account resource for the Blob storage sub-service. Beginning in version 6.8.2, the Everpure Cloud Dedicated array will also use the Table storage sub-service within the same Azure Storage Account resource. No other changes to the Azure Storage Account will be made, and the resource will remain private within your virtual network.

We are committed to ensuring a smooth transition for all Everpure Cloud Dedicated users. Please review your network configurations, especially in environments with complex networking, to ensure seamless connectivity to the Azure Table Storage service.

New Capacity Points for V10MP2-R2 model

Starting with Everpure Cloud Dedicated version 6.8.2, the number of capacity points for V10MP2-R2 model were increased from three to nine. Now it is possible to get up to 98TiB of raw storage capacity (71.14 TiB usable).

The new capacity points are available only for V10MP2-R2 model.

Impact to New Deployments – What changes

No CosmosDB Service endpoint (Microsoft.AzureCosmosDB) on the system subnet is required anymore. Instead of that, please make sure the Microsoft.Storage service endpoint is enabled on the subnet. More details about changes to Service Endpoints can be found on Azure Networking Requirements - Service Endpoints.

In case of deployments into some complex networking, make sure the hostname *.table.core.windows.net is accessible via the HTTPS (443) port from the system subnet. More details can be found on Option 2 - Configuring Azure Firewall (or 3rd party firewall appliance).

Performing an Upgrade to Version 6.8.2

This change introduces minimal networking modifications:

For deployments without NSGs or firewalls in place: If your Everpure Cloud Dedicated deployment is in a virtual network without an NSG or firewall, no further action is needed. The migration will be handled automatically as part of the Purity upgrade process.
For deployments with complex networking: Before starting Purity upgrade process, please ensure that the hostname *.table.core.windows.net is accessible via HTTPS (port 443) from the system subnet. More details can be found on Option 2 - Configuring Azure Firewall (or 3rd party firewall appliance).

After the upgrade, you can remove any rules or Service Endpoints that were previously configured to enable communication with the CosmosDB service. The CosmosDB resource will be automatically decommissioned and removed as part of the upgrade process.

If you have any questions or require assistance, our support team is ready to help. Refer to the official documentation or contact your Everpure representative for further guidance.

Stay tuned for more updates as we continue to enhance Pre Storage Cloud Dedicated for Azure for optimal performance and cost efficiency.

Internal notes

Why did we make such a change in architecture?

Switching to Table Storage provides several benefits:

Simplicity: Table Storage meets the requirements of Everpure Cloud Dedicated without relying on advanced features of CosmosDB.
Cost Efficiency: This change reduces costs, saving customers approximately $250 per month per PCD array.
Improved Availability: The CosmosDB service is an advanced Azure resource, however, the Table Storage has a much lower probability of capacity constraints in Azure, ensuring smoother deployments and scalability.

By transitioning to Table Storage, we align Everpure Cloud Dedicated architecture with the needs of our customers while improving cost efficiency and operational reliability.

The change to Table Storage doesn't have any impact on the Everpure Cloud Dedicated performance.

Impact for CDU on existing Everpure Cloud Dedicated arrays

When a customer initiates a Customer-Driven Upgrade, the upgrade script starts with a test, if a Table storage is reachable – it creates a temporary table storage resource and checks if the Table storage is reachable from the current networking. When it's not reachable, the upgrade script will notify the user and interrupt the upgrade process.

Once the upgrade process is completed, the CosmosDB resource within the Everpure Cloud Dedicated array gets automatically removed.