Planned Maintenance region TKY1 (Tokyo) from 2020-05-18 08.00 CEST Maintenance window ends: 2020-05-22 17.00 CEST AND 2020-05-25 08.00 CEST Maintenance window ends: 2020-05-29 17.00 CEST
2020-05-28 17:35 CEST: Work is done for today
2020-05-28 10:45 CEST: Work has started again
2020-05-26 17:35 CEST: Work is done for today
2020-05-26 08:10 CEST: Work has started again
2020-05-25 18:50 CEST: Work is done for today
2020-05-25 08:00 CEST: Work on the second week of Maintenance Window is started
2020-05-22 17:05 CEST: Work is done for today - W.21 is closed
2020-05-22 09:30 CEST: Work has started again
2020-05-21 18:45 CEST: Work is done for today
2020-05-21 09:40 CEST: Work has started again
2020-05-20 17:30 CEST: Work is done for today
2020-05-20 08:20 CEST: Work has started again
2020-05-19 18:50 CEST: Work is done for today
2020-05-19 08:15 CEST: Work has started again
2020-05-18 19:38 CEST: Work is done for today
2020-05-18 08:25 CEST: The maintenance window has been opened and work is ongoing.
Dear Valued Customer,
City Network would like to inform you that we have planned maintenance as scheduled below.
Customer Intervention MAY BE required.
Region/datacenter: OpenStack region TKY1 (Tokyo, Japan)
Maintenance window starts: 2020-05-18 08.00 CEST
Maintenance window ends: 2020-05-22 17.00 CEST
Maintenance window starts: 2020-05-25 08.00 CEST
Maintenance window ends: 2020-05-29 17.00 CEST
Throughout the maintenance window, a number of improvements will be implemented - from functionality to security
The major part of the scope is an OpenStack upgrade from Rocky to Train, which will offer certain new functions but
also address a list of known bugs. Some functions will improve seen to maturity level and Magnum (Container
Orchestration) in particular.
There will, in parallel, be work security wise to further increase protection and to address vulnerabilities.
Furthermore there will be improvements to operations automation and those improvement will allow a high flexibility
for us to operate the cloud more seamless. pinpointing time frames that could potentially involve a slightly higher risk of
minor disruption. Please note that there may be a shorter time frame, still to be defined, involving a brief disruption of runnings services
Our ambition is to carry out the majority of the maintenance window with little to no impact on running services
Expected customer impact:
Running virtual instances will be restarted in a controlled and timely manner, in order for proper security patching.
Customers using redundant setup and using anti-affinity should not experience disruption, as one compute node will
be dealt with at a time.
Customers are expected to ensure virtual instances (virtual servers) along with any services hosted on those, will
properly start up after a reboot of an virtual instance (virtual server).
The restart of the virtual instance (virtual server) will be attempted in a graceful manner with a 2 minutes grace period.
After the grace period, a forceful restart will be issued.
Besides the above reporter impacted, please expect a time frame of 15 minutes where total network outage is to be expected.
This part will be scheduled to off working hours Furthermore, Load Balancer as a Service v2 will be deprecated and removed
in the OpenStack Train release - why conversion of all existing LBaaSv2 services will be carried out throughout the maintenance.
Affected customers will be contacted individually with additional information.
Follow status at http://cnstatus.com for updates.
If you have further questions, please contact our support at email@example.com(opens in new tab).