- 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
30-10-2020 00:00:00
- 30-10-2020 07:00:00
Urgency: Planned
Affected services:
- Virtual machines
- Shared storage
- Shared hosting
- MSSQL instances
Expected impact: None
Customer intervention required: No
Reference number: 170743
Summary:
On Friday October 30th between 00:00 hrs and 07:00 hrs engineers from BIT will perform maintenance on the Ceph storage cluster. Ceph messenger version 2 protocol will be activated on the cluster (besides version 1).
Details:
Ceph messenger version 2 protocol will be activated on the cluster (besides version 1). This protocol comes with a couple of enhancements. Applications that are able to use this new protocol will do so by default (port 3300). We do not expect noticeable impact on the functioning of the cluster during this maintenance. However, every upgrade comes with (extra) risks, therefore the configuration change will take place during a maintenance window.
Affected services:
- Virtual machines
- Shared storage
- Shared hosting
- MSSQL instances
Expected impact: None
Customer intervention required: No
Reference number: 170743
Summary:
On Friday October 30th between 00:00 hrs and 07:00 hrs engineers from BIT will perform maintenance on the Ceph storage cluster. Ceph messenger version 2 protocol will be activated on the cluster (besides version 1).
Details:
Ceph messenger version 2 protocol will be activated on the cluster (besides version 1). This protocol comes with a couple of enhancements. Applications that are able to use this new protocol will do so by default (port 3300). We do not expect noticeable impact on the functioning of the cluster during this maintenance. However, every upgrade comes with (extra) risks, therefore the configuration change will take place during a maintenance window.