- 24-04-24Status.bit.nl in nieuw jasje!
- 12-04-24Nieuw bij BIT: GPU hosting
- 25-03-24BIT breidt netwerkconnectiviteit uit met aansluiting op NL-ix^2
- 13-03-24No More Leaks: Samenwerken tegen cybercriminaliteit
- 03-03-24Geen verandering twee jaar na invoering sancties tegen Russische media: FOIC roept (wederom) op tot einde van ondemocratische censuur
- 29-01-24Onzichtbare upgrades
- 16-01-24BIT's Wido Potters wint Felipe Rodriquez Award voor inzet voor privacy
- 10-01-24BIT en partners zetten de koers voor een gedecentraliseerde Europese cloud met ECOFED-project
- 02-01-24Onze eigen stroom inkopen: de resultaten van 2023
- 24-11-23BIT Friday 2023
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.