Dimension Data CloudControl Storage Upgrade Programme: Change to Existing Standard/High Performance/Economy Disks in NA9 (Ashburn)
Scheduled Maintenance Report for Dimension Data Public Cloud Status
The scheduled maintenance has been completed.
Posted 3 months ago. May 29, 2019 - 21:00 UTC
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted 3 months ago. May 29, 2019 - 09:00 UTC
As part of our ongoing improvement initiatives, we will be kicking off our storage upgrade programme in NA9 (Ashburn) to give a better, predictable and consistent experience when it comes to cloud storage performance. As part of the initiative, we are migrating the Standard/High Performance/Economy Disk Speeds in NA9 (Ashburn) to the new “Burstable” storage model.

As part of this effort, we will be making changes to ALL disks associated with ALL existing Cloud Servers that are using the Economy, Standard, and High Performance disk speeds.

The enablement will begin during the normal software upgrade window on May 29, 2019 starting at 17:00 UTC. The change is expected to take several hours to take effect across all existing Cloud Servers.

CloudControl Change Id: OEC-11398
Time 05:00 AM Eastern Daylight / 2:00 AM Pacific Daylight (9:00 UTC)
Expected Total Duration: Up to 12 Hours

For all NEW and EXISTING disks on all Cloud Servers using Economy, Standard, or High Performance disk speeds:

1. After the change, Disks will be allowed to burst only up the following IOPS and Throughput limits based on their disk speed:

ECONOMY: Greater of 100 IOPS or 0.5 IOPS/GB based on the size of the disk
STANDARD: Greater of 500 IOPS or 3 IOPS/GB based on the size of the disk
HIGH PERFORMANCE: Greater of 800 IOPS or 6 IOPS/GB based on the size of the disk

Throughput limit equal to the IOPS maximum x 16 KB (Kilobytes). This limit applies in addition to the above IOPS limit.

Example:: A 100 GB Disk using Standard Disk Speed will be assigned a 500 IOPS burstable maximum AND an 8,000 Kilobyte/second Throughput maximum (500 IOPS x 16 KB).

2. If the server is running when the change is implemented, the system will vMotion the server so that the changes take immediate effect. No restart is required. This is an improvement in behavior from previous locations where we have migrated to Burstable architecture.

However, if some issue prevents the system from successfully vMotioning the server, the server may require a restart before additional CloudControl actions can be made against the server.

For more information please refer to the following two articles:

Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds - https://docs.mcp-services.net/x/UwIu
How do I determine if my Server Requires a Restart Using REST API? - https://docs.mcp-services.net/x/QgSZ
Posted 4 months ago. May 03, 2019 - 18:54 UTC
This scheduled maintenance affected: NA - US East (Public CaaS NA9) and Dimension Data Public CaaS Portal NA.