Infrastructure Maintenance
Scheduled events are planned maintenance tasks that can affect one or more of your virtual machines (VMs).
To ensure a transparent process and allow you to plan ahead, a communication is sent to impacted customers at key stages of each maintenance:
-
Two weeks before maintenance (depending on the event), an initial notification is sent to inform customers of the nature of the upcoming maintenance, the potentially affected services, and the estimated duration of the intervention.
-
One week before maintenance (depending on the event), a reminder is sent to remind customers of the date of the intervention.
-
At the beginning of maintenance, a notification is sent to specify the details of the intervention and any temporary disruption to services.
-
At the end of maintenance, a communication confirms that the intervention has ended and that service is fully restored, completing the follow-up.
A scheduled event can have one of the following codes:
-
System-reboot: VMs will be affected by software upgrade or hardware maintenance.
-
System-maintenance: VMs will be affected by network or power maintenance, and may be temporarily unavailable.
To know which VMs are affected by a scheduled event, see Getting Information About Your VMs > Status.
TINA Upgrade
When a new version of our Cloud orchestrator TINA is available, maintenance is planned to install it in all Regions of the OUTSCALE infrastructure. These maintenance tasks are planned in the following order:
-
us-west-1
-
ap-northeast-1
-
us-east-2
-
eu-west-2
-
cloudgouv-eu-west-1
An email is sent to impacted customers:
-
(cloudgouv-eu-west-1 only) Two weeks before maintenance
-
One week before maintenance
-
At the beginning of maintenance
-
At the end of maintenance
|
To receive notifications, remember to update the email address associated with your account. For more information, see Modifying Your Personal Information and Password. |
A TINA upgrade takes two hours for each Region. During this maintenance, the APIs are unavailable for 30 minutes. This downtime causes a 503 HTTP code when requesting the API and when connecting to Cockpit.
Hypervisor Maintenance
To keep the infrastructure up-to-date and ensure top-quality service, we regularly plan hardware maintenance on hypervisors in all our Regions.
Impacted customers automatically receive a support ticket two weeks before maintenance, including the list of their impacted VMs.
If these VMs are still in the running state during maintenance, they will be automatically stopped.
To prevent this, we strongly recommend stopping and starting the VMs before the date of the maintenance. This automatically transfers them to another hypervisor in the same Region that will not be affected by maintenance. You can transfer your VMs to another hypervisor as soon as you receive the maintenance notification email. For more information, see Stopping and Starting VMs.
|
If you do not transfer your VMs, they will be force stopped during maintenance, which causes an interruption of the applications they contain and may damage your data. If your VMs have non-persistent configurations, the applications may not restart properly. |
|
To receive notifications, remember to update the email address associated with your account. For more information, see Modifying Your Personal Information and Password. |
Service Maintenance
Maintenance events for OUTSCALE services are scheduled year round.
An email is sent to impacted customers to inform them of actions taken on the service:
-
Two weeks before maintenance
-
One week before maintenance
-
At the beginning of maintenance
-
At the end of maintenance