(Updated 2019/12/3)Virtual Server/Image Storage maintenance in Japan regions (JP1, JP2, P4, JP5)
Dec.3th,2019 Updated regarding JP1 Maintenance completion
Nov.19th,2019 Updated regarding JP2 Maintenance completion
Oct.30th,2019 Updated regarding JP4 Maintenance completion
Oct.9th,2019 Updated regarding JP5 Maintenance completion
Sep.17th,2019 Updated regarding Minor change of service behavior 6.
Sep. 2nd,2019 Published
Thank you for using NTT Communications Enterprise Cloud 2.0 (ECL2.0) service.
We will conduct Virtual Server infrastructure maintenance in Japan regions (JP1, JP2, JP4, JP5).
This maintenance is to improve service quality, especially of ECL2.0 Virtual Server infrastructure.
Thank you for your understanding.
The details are as follows:
JP1[Done], JP2[Done], JP4[Done], JP5[Done]
– JP5 (Tokyo 2nd Datacenter) region:[Done]
Oct/8/2019 (Tue) 11:00 (UTC) ~ Oct/9/2019 (Wed) 6:00 (UTC）
– JP4 (Tokyo 10th Datacenter) region:[Done]
Oct/28/2019 (Mon) 11:00 (UTC) ~ Oct/29/2019 (Tue) 6:00 (UTC）
– JP2 (Osaka 5th Datacenter / Osaka 1st Datacenter) region:[Done]
Nov/14/2019 (Thu) 11:00 (UTC) ~ Nov/15/2019 (Fri) 6:00 (UTC）
– JP1 (Saitama 1st Datacenter) region:[Done]
Nov/26/2019 (Tue) 11:00 (UTC) ~ Nov/27/2019 (Wed) 6:00 (UTC）
Regarding regions outside Japan, separate maintenance announcement will be provided.
Affected Services during maintenance window
- Affected service (Server and Network Service )
There will be no impact on service currently in use, such as Virtual Server interruption, disconnection of network service during maintenance.
Guest OS and applications on the virtual servers (ex. Connected by SSH) will be available without interruption.
- GUI (ECL2.0 portal) and APIs
During maintenance, the following GUI and API operations will be affected.
In respective regions, “Cloud Computing” and “Security” Control Panel will be unavailable for duration of maintenance.(Create / Read / Update / Delete)
There will be no impact on the regions where maintenance is not scheduled and announced.
* [Caution] Please note that if you stop the virtual server accidentally (ex. shut down on the guest OS), you cannot start the virtual server until the maintenance is completed.
As shown below, for each services a) All API operations, or b) Resource creation and few other functions, will be unavailable.
a) All API operations will be unavailable
Virtual Server, Image Storage, Firewall (vSRX, Brocade 5600 vRouter), Load balancer (NetScaler VPX), Network-type Security (Managed Firewall, Managed UTM, Managed WAF), Enterprise Cloud 2.0 Inter-Connectivity, Deployment Manager
b) Resource creation and few other functions will be unavailable
Service: Baremetal Server, Dedicated Hypervisor
The following functions will be unavailable:
– Creating server
– Generating ‘list servers’ of servers with image set as Request Parameter
– Generating ‘list servers detail’ of servers with image set as Request Parameter
The maintenance duration includes expected recovery time in case a failure occurs.
The maintenance itself is scheduled to be completed around 21:00(UTC).
Minor change of service behavior
- Pre-created port of virtual server will remain when deleting VM or detaching interface
In case where a VM (virtual server) is created using a port (NW interface) created in advance (before the VM), deleting the VM/detaching IF would
automatically delete the port on current service design. After this maintenance, the port will no longer be automatically deleted in such cases.
- The parameter to use HA function will be changed
So far, depending on the user choice made in VM creation phase regarding the use/non-use of HA function, “true” or “false” is set in the metadata value
“vmha” and users can configure it.
After this maintenance, in addition to “vmha”, “HA_Enabled” is used as a parameter of using HA function.
Although there is no impact on users, the parameter “vmha” will be deprecated.
Please use the parameter “HA_Enabled” after this maintenance.
- Error of detaching volume from the VM running
After this maintenance, if users try to detach a volume from a running VM, it may fail.
As described in the service descriptions, when detaching a volume from a VM, it is recommended to stop the VM before detaching the volume.
- Resolve known Issues
After this maintenance, the known issue in below URL will be resolved.
- Image Copy with AU1 region will be unavailable
After this maintenance, users will not be able to copy the image between the respective region and AU1 region.
* AU1 region has stopped to provide new tenants from January 8, 2019.
6. Behavior of the VM in which HA function is off
If the VM in which HA function is off is stopped due to a failure, users cannot start it by yourselves.
In such case, please contact our support, or delete or recreate the VM.
If there are any updates, we will announce on this page.