- 25-04-24Periodic maintenance cooling system BIT-2BCD
- 22-04-24Periodic maintenance cooling system BIT-2A
- 18-04-24Maintenance diesel tanks power generators BIT-2A
- 15-04-24Periodic maintenance cooling system BIT-1
- 11-04-24Maintenance computair units BIT-2A
- 09-04-24Maintenance computair units BIT-2C
- 08-04-24Maintenance computair units BIT-2B
- 05-04-24Firewall Maintenance
- 04-04-24Periodic maintenance fire detection and suppression systems BIT-2A and BIT-2BCD
- 04-04-24Maintenance diesel tanks power generators BIT-2A
Maintenance Ceph storage cluster
04-07-2019 00:00:00
- 04-07-2019 07:00:00
Subject: Maintenance Ceph storage cluster
Urgency: Planned
Affected services:
- Virtualisation platforms
- Shared storage
- Shared hosting
- MSSQL instances
Expected impact:
- Reduced redundancy
Customer intervention required: No
Reference number: 163268
Summary:
On Thursday July 4th between 00:00 hrs and 07:00 hrs engineers from BIT perform maintenance on the Ceph storage cluster. The cluster will be upgraded with software updates.and performance.
Details:
We do not expect noticeable impact on the cluster during this maintenance. The cluster will be upgraded node by node. When upgrading the nodes we will wait for a fully healthy status of the cluster (Ceph HEALTH_OK), before starting the upgrade of the next node. The cluster has been designed to be upgraded while being in use (live upgrading). However every upgrade comes along with (extra) risks, therefore we do these upgrades during maintenance windows. We don't expect any impact on availability or services which make use of the cluster.
Urgency: Planned
Affected services:
- Virtualisation platforms
- Shared storage
- Shared hosting
- MSSQL instances
Expected impact:
- Reduced redundancy
Customer intervention required: No
Reference number: 163268
Summary:
On Thursday July 4th between 00:00 hrs and 07:00 hrs engineers from BIT perform maintenance on the Ceph storage cluster. The cluster will be upgraded with software updates.and performance.
Details:
We do not expect noticeable impact on the cluster during this maintenance. The cluster will be upgraded node by node. When upgrading the nodes we will wait for a fully healthy status of the cluster (Ceph HEALTH_OK), before starting the upgrade of the next node. The cluster has been designed to be upgraded while being in use (live upgrading). However every upgrade comes along with (extra) risks, therefore we do these upgrades during maintenance windows. We don't expect any impact on availability or services which make use of the cluster.