Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Aug 15, 2019 - 14:00 UTC
Scheduled
As part of our ongoing improvement initiatives, we will be kicking off our storage upgrade programme in AU11 (New_Zealand MCP 2.0) 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 AU11 (New_Zealand MCP 2.0) 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 on August 16th at 2 AM New Zealand Standard Time (August 15, 2019 14:00 UTC). The change is expected to take several hours to take effect across all existing Cloud Servers.
CloudControl Change Id: OEC-11589 Time: August 16th at 2 AM New Zealand Standard Time (August 15, 2019 14: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: