Changes for page Announcements

Last modified by hbpadmin on 2025/01/09 12:12

From version 162.1
edited by hbpadmin
on 2022/10/20 10:30
Change comment: There is no comment for this version
To version 168.1
edited by hbpadmin
on 2022/12/13 18:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,3 +1,25 @@
1 +=== **Collaboratory Lab on Juelich not working** ===
2 +
3 +The JSC cluster is currently in a bad state. As such, the Lab instance on JSC is not useable. We are attempting to restore access as soon as possible.
4 +
5 +=== **Colloboratory Bucket is currently full** **(2022-11-03)(Done)** ===
6 +
7 +The quota for the Collaboratory Bucket is currently full, we are in the process of increasing this limit and will restore service as soon as possible. In the meantime, you can still download and view files that are stored in the Bucket.
8 +\\INFO: Quota has been increased and service has been restored.
9 +
10 +=== **Six EBRAINS services will experience a short downtime (2022-10-27) (Done)** ===
11 +
12 +The following 6 services will experience a short downtime today in order for us and the infrastructure team at CSCS to consolidate the status of the corresponding servers. We plan to stop the services one after the other for an estimated 5 minutes each during a 30-minute window (see banner). The services are:
13 +
14 +1. Collaboratory IAM: authentication of users
15 +1. Knowledge Graph Search
16 +1. Neuroglancer: for the 3D visualisation of brain images
17 +1. PLUS: an HBP internal project coordination tool
18 +1. An internal tool for monitoring the EBRAINS platform which is not user facing
19 +1. A deprecated service which we are maintaining to improve the user experience of a few users
20 +
21 +The maintenance on each of these services has been completed.
22 +
1 1  === **EBRAINS infrastructure causing issues with the Drive (2022-10-19) (Fixed)** ===
2 2  
3 3  The Drive is currently down due to another issue at CSCS. We are working on getting this resolved as soon as possible. We will be checking with CSCS on their root cause analysis and see that steps are taken to avoid the recurrence of such an issue.