[Service Disruption] Intersect availability zone Thursday 26 July 2018
Posted
about 6 years ago
by Glenn Satchell
Glenn SatchellAdmin
Users of the Intersect zone are advised that on Thursday 26 July there will be a series of rolling outages affecting most Intersect Nectar instances. These outages are part of regular maintenance.
All compute node will be patched and rebooted, and this requires downtime for the instances. The upgrade work will be performed progressively, with a number of compute nodes out of service at any one time. It is anticipated that each compute node will take about 1 hour.
The upgrade procedure for each node will be as follows:
1. All ACTIVE (i.e. running) NeCTAR instances on the compute node will be shut down. 2. The required updates will be done and the compute node will be rebooted. 3. All instances that were ACTIVE in step 1 will be restarted.
Advice:
* If your instances are providing services to end-users, plan an outage window, and announce it to them.
* Ensure that your critical instances have appropriate (and tested) backup / disaster recovery procedures, and that you have recent backups prior to the outage window.
* We recommend that you put your instances into SHUTDOWN state before the outage window, and then restart them yourself when notified. You should definitely do this if your instances are interdependent, or if they have to be restarted in a specific order.
* If you have instances that are surplus to requirements, please release the resources for other users to use. This is includes instances that have been in SHUTDOWN, PAUSED, STOPPED or ERROR state for a long time.
If you have any queries regarding this outage, please contact us by email:
support@ehelp.edu.au
We apologise sincerely for any inconvenience caused by this outage.
Users of the Intersect zone are advised that on Thursday 26 July there will be a series of rolling outages affecting most Intersect Nectar instances. These outages are part of regular maintenance.
All compute node will be patched and rebooted, and this requires downtime for the instances. The upgrade work will be performed progressively, with a number of compute nodes out of service at any one time. It is anticipated that each compute node will take about 1 hour.
The upgrade procedure for each node will be as follows:
1. All ACTIVE (i.e. running) NeCTAR instances on the compute node will be shut down.
2. The required updates will be done and the compute node will be rebooted.
3. All instances that were ACTIVE in step 1 will be restarted.
Advice:
* If your instances are providing services to end-users, plan an outage window, and announce it to them.
* Ensure that your critical instances have appropriate (and tested) backup / disaster recovery procedures, and that you have recent backups prior to the outage window.
* We recommend that you put your instances into SHUTDOWN state before the outage window, and then restart them yourself when notified. You should definitely do this if your instances are interdependent, or if they have to be restarted in a specific order.
* If you have instances that are surplus to requirements, please release the resources for other users to use. This is includes instances that have been in SHUTDOWN, PAUSED, STOPPED or ERROR state for a long time.
If you have any queries regarding this outage, please contact us by email:
support@ehelp.edu.au
We apologise sincerely for any inconvenience caused by this outage.
0 Votes
0 Comments
Login or Sign up to post a comment