- 01-04-25BIT as a Service
- 26-03-25Internetproviders verliezen rechtszaak over blokkeren websites
- 19-02-25BIT introduceert server-side e-mailfiltering met Sieve
- 06-02-25Shared hosting wordt opgefrist
- 28-11-24ECOFED uitgeroepen tot publieksfavoriet bij Computable Awards
- 21-11-24Een goede cloud heeft een kundige dirigent nodig
- 17-10-24ECOFED wint ICT Innovatieprijs Regio Foodvalley 2024
- 01-08-24BIT geeft kaarten weg voor F1 in Zandvoort
- 24-04-24Status.bit.nl in nieuw jasje!
- 12-04-24Nieuw bij BIT: GPU hosting
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.