Where?
The OVH dedi host

What?
A full reboot of the host

When?
2024-03-20

Impact?
All services on the host will be down till the reboot completes

Where?
OVH Dedicated server

What?
Updates to running virtual servers

When?
18th May 2023

Impact?
Services will be intermittent while virtual servers are restarted

Where?
OVH Dedicated host

What?
Update Proxmox to v7

When?
Wednesday 16th of March 2022

Impact?
All services on the Proxmox host will be offline till the update is complete

Where?
OVH Dedicated server

What?
Update to Proxmox to v8

When?
20th September 2023

Impact?
All services will be offline for the upgrade

Where?
OVH Dedicated host

What?
The internet firewall

When?
Wednesday 2nd of March 2022

Impact?
All services will unavailable till the update is complete

Where?
Proxmox Host at OVH

What?

• A full host reboot
• restart of all vms
• restart of all containers

When?
25/10/2023 at 20:30

Impact?
All services on my Proxmox Host will be unavailable till the reboot is complete

Incident: A test

Cause: not sure this works

Effect: nothing

Duration: none

Mitigation: some

Where?
Home

What?
Internet facing web server

When?
TBA

Impact?
All home web services will be offline till new server is up and running

Where?
The OVH dedicated host

What?
I will be rebuilding all vms in the host

When?
the week of the 10th June 2024

Impact?
All services will be intermittent while things get rebuilt

Where?
OVH Dedicated server

What?
Updates to running virtual servers

When?
11th May 2022

Impact?
Services will be intermittent while virtual servers are restarted

Where?
Home

What?
Migrate Nextcloud, its config, database and data to new dedicated host

When?
18/01/2022 from 19:30 - 22:00

Impact?
Nextcloud with be unavailable for the duration

Where?
Home

What?
The Jellyfin server

When?
TBA

Impact?
Jellyfin will be down till the new server has been build and Jellyfin installed and started

This is my Lemmy instance

This is hosted in OVH France, its a dedicated host that runs Proxmox and has about 6 virtual servers running on it

This is an IG Incident template. Please replicate this task to record details of a new incident. See the steps below:

1. Replicate this task.
2. Fill in the date and a quick summary in the Task Title
3. Set the correct Product and Project, make sure to mark the Category as IG Incident.
4. When replicating, be sure to assign the task to yourself, IG Group (Mayden) in the Group Users section (so that it's assigned to individuals), plus anyone else that should be involved. As a minimum, the new task should be assigned to Stefan.
5. Fill in the below ICED-M with as much detail as you can, when time allows.
6. Add the appropriate Tags to this task (for example IG - System Unavailable
7. If this is an iaptus incident, add details to the iaptus IG incidents and outages spreadsheet
8. If Mitigating Actions need to be performed, discuss with a relevant Product Owner to estimate and schedule that work.
9. Delete these instructions.

Incident:

Cause:

Effect:

Duration:

Mitigation:

Note: Please be sure to follow up when Mitigating Actions have been completed. If you think these have been done, please post this task to the #iggroup on Slack for them to close off the task as complete.