Changes for page Announcements

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

From version 66.1
edited by hbpadmin
on 2021/06/01 12:40
Change comment: There is no comment for this version
To version 77.1
edited by chaney08
on 2021/07/12 12:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.hbpadmin
1 +XWiki.chaney08
Content
... ... @@ -1,18 +1,16 @@
1 -(% class="wikigeneratedid" %)
2 -=== Maintenance Monday 7th June 8AM CEST ===
1 +=== **Openshift issues (09-07-2021) (Resolved)** ===
3 3  
4 -All services provided by virtual machines running on Openstack and Openshift at CSCS will be down for the preparation of the new updated Openstack server.
3 +The Openshift service has gone down. As the Collaboratory Lab and the Image service both rely on this service, they are currently unavailable. We are investigating this issue and it will be resolved as soon as possible. We apologise for any inconvenience caused.
5 5  
6 -This will include all of Collaboratory 1 and 2, the Swift object storage, the EBRAINS authentication among many others. The following services will not be affected: HBP and EBRAINS web servers, supercomputing services, and services running on the 4 other Fenix sites (unless they depend on one of the above services).
5 +**UPDATE 12-07-2021 : **The issue seems to be with the Openstack servers. It is also affecting a few more VMs aside from the Openshift service. The infrastructure team is looking into it.
7 7  
8 -The intervention is expected to fit within a time window of 3.5 hours. If it is shorter, the Collaboratory will come back up with a "Maintenance completed" banner. There is a small risk that the intervention may exceed 3.5 hours.
7 +**UPDATE 12-07-2021 : **Openshift servers have been fixed and all services should be back up and running, thank you for your patience.
9 9  
10 -=== EBRAINS services technical difficulties ===
9 +=== **Collaboratory Lab restart ( 15-06-2021)** ===
11 11  
12 -Most EBRAINS services are currently experiencing technical difficulties. Please bear with us as we work on resolving these issues. This involves Collaboratory 1, Collaboratory 2 and other EBRAINS services.
13 -\\The issues occurring at the moment are the result of unexpected network issues due to network maintenance ongoing at CSCS.
11 +The Collaboratory lab will be restarted for the purpose of changing a few background configurations.
14 14  
15 -=== Collaboratory User Group (UG) meeting ===
13 +=== **Collaboratory User Group (UG) meeting** ===
16 16  
17 17  The UG meeting is a great way to stay informed about recent and upcoming changes to the Collaboratory as well as making your voice and ideas heard directly by the developers. If you are interested in attending this meeting, or know someone who is interested, please feel free[[ to join these meetings>>https://wiki.ebrains.eu/bin/view/Collabs/collaboratory-user-group/Joining%20the%20group/]]
18 18  
... ... @@ -19,6 +19,12 @@
19 19  If you would like to see new features or feel certain functionality is required to improve the Collaboratory, please [[join the Collaboratory user group>>https://wiki.ebrains.eu/bin/view/Collabs/collaboratory-user-group/Joining%20the%20group/]], once joined, please do not hesitate to [[make your suggestions>>https://drive.ebrains.eu/lib/aac38e36-4bd9-48ee-9ae6-b876a65028aa/file/Collaboratory%20User%20Group%20-%20Suggestion%20box.docx]].
20 20  
21 21  
20 +=== **Drive issue (Resolved 14-06-2021)** ===
21 +
22 +There is currently an issue that prevents the Drive option from appearing in new collabs. Although you can still create new collabs and can access all of the other functionality provided, you will not have access to the Drive by default. You can request a Drive be manually added to your collab via support.
23 +\\We apologise for any inconvenience this causes. 
24 +
25 +
22 22  === **Drive issue (Solved)** ===
23 23  
24 24  Users have reported issues trying to access the drive. This is something we are aware of and trying to fix as soon as possible. This issue seems to be an Openshift problem.