Reminder: 3 day outage affecting all NeCTAR instances in Pawsey-01: 2015-10-30 to 2012-11-02

Follow

You are reminded that all NeCTAR instances in the NeCTAR Pawsey-01 availability zone will be shutdown and inaccessible for up to 3 days, starting at 18:00 (Brisbane time) on Friday 30th of October.

The owners of all affected instances were informed by email on Friday 10th October; see below for the full announcement.

See also: https://portal.pawsey.org.au/docs/Pawsey_Maintenance/2015-10-31data

 


 

Subject: NeCTAR Research Cloud outage affecting your instances
 
 
Dear NeCTAR Research Cloud User,
This email is to inform you of a scheduled outage to the NeCTAR Research Cloud.
DURATION: 3 days 0 hours
START TIME: 2015-10-30 16:00:00 AWST
END TIME: 2015-11-02 16:00:00 AWST
DESCRIPTION:
A 3 days 0 hours outage is required to perform essential maintenance on cloud infrastructure at the pawsey-01 availbility zone. Only instances in the pawsey-01 availability zone will be affected. The upgrade will bring further stability and increased performance to this availability zone.
IMPACT:
All instances in the pawsey-01 availability zone will be shut down and will be inaccessible during the outage. Instances will NOT be destroyed, only shut down. This zone will be offline during the outage period and no requests to the zone will be processed. Users have the option of relocating instances to other availability zones prior to the outage. At present there is reasonable spare capacity across the cloud to start instances elsewhere, however this capacity may decrease as the outage date approaches.
ACTION REQUIRED:
  • It is recommended that users complete their own backups, snapshots or otherwise copy data to somewhere other than the pawsey-01 zone
  • Once backups are complete, it is recommended that users detach volumes and shut down their own instances. If a user is unable to do so, the instances will be shut down at the outage start time
  • Ensure that the above items are completed well in advance of the outage start time
  • After the outage, users will be required to restart their own instances
Have more questions? Submit a request

Comments

Powered by Zendesk