Changes for page Announcements

Last modified by hbpadmin on 2025/01/09 12:12
From version 87.1
edited by mmorgan
on 2021/11/04 01:08
Change comment: There is no comment for this version
To version 55.1
edited by hbpadmin
on 2021/04/29 13:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.mmorgan
1 +XWiki.hbpadmin
Content
... ... @@ -1,106 +1,117 @@
1 -(% class="wikigeneratedid" %)
2 -=== **Technical difficulties on the Drive (2021-11-03)** ===
1 +=== **Drive issue** ===
3 3  
4 -The Drive has experienced some technical difficulties over the past weeks caused by multiple issues.
3 +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.
5 5  
6 -A reboot of the Drive server due to a hardware failure revealed an issue in the communication between the Lab and the Drive. A container is started for each Lab user who opens the Lab in their browser to run their notebooks. That container remains active by default well beyond the end of the execution of the notebook and the closing of the browser tab running the Lab, unless the users explicitly stop their container. Those containers were causing unusually high traffic to the Drive. We identified the problem and found a solution with an upgrade of the tool which the Drive is based on. We have had to shift the deployment date for this fix multiple times but we will be announcing the deployment date ASAP. In the meantime **we ask Lab users to kindly stop their servers** from the JupyterLab menu when they are not actively working in the Lab. This is done from the JupyterLab menu: //File > Hub control panel > Stop my server//.
5 +Until this is resolved, users will have issues accessing any functionality that requires Drive access. This mainly concerns the Lab and to a less extant, any service that requires access to the drive.
7 7  
8 -The cloud infrastructure that the Drive is running on is being upgraded and the Drive service had to be moved to the newer servers. An incorrect management command of the server caused the migration of the data to be launched twice, with the second transfer overwriting production data dated Nov 2 with stale data from Oct 20. Several backup issues stacked on top of this problem. We have been able to recover a backup which was made on the night of Sunday Oct 31 to Monday Nov 1. We are verifying that we cannot identify issues with this data before we reopen access to the Drive. **Some data loss is expected** for data stored on the Drive after that backup and before we put up a banner asking users, as a precaution, not to add new data to the Drive on Tuesday Nov 2 around noon. Many countries had a bank holiday on Nov 1 so for many users, the data loss should be of a few hours on Nov 2.
7 +**Potential fix: **We believe we have identified the issue and will be bringing the Lab service down for up to an hour at 10pm CEST on April 28th as we attempt to deploy this fix. All current Notebooks will be killed during this downtime. - Unfortunately this fix has not worked and we are looking at other solutions at the moment.
9 9  
10 -We sincerely apologize for the problems incurred. We appreciate that the service we provide must be trustworthy for our users. We are taking the following actions to ensure that similar problems do not happen again:
9 +**Potential fix 2: **We have another small release that should fix the issue at 13:30 CEST Today. All currently running notebooks will be killed during this downtime.
11 11  
12 -* Review of the backup procedures on the Drive server which will be extended to all EBRAINS services which we manage.
13 -* Request notification from the underlying infrastructure when service accounts reach the limit imposed by their storage quota.
14 -* Improve the identification of production servers to reduce the risk of the operations team misidentifying which servers are running production service.
11 +This issue has been resolved, please let support know if you encounter any issues with the lab. Thank you for your understanding.
15 15  
16 -We hope to have the Drive service up again sometime Thursday Nov 4.
13 +We apologise for any inconvenience this has caused
17 17  
18 -Additionally, the Collaboratory team will be looking into mirroring services onto more than one Fenix site to reduce down time when incidents occur. This task will be more challenging for some services than for others; it might not be materially feasible for some services, but we will be analysing possibilities for each Collaboratory service.
15 +=== **Collaboratory 2 release (2021-04-28)** ===
19 19  
20 -=== **Maintenance on 2021-10-19** ===
17 +**Due to the problem described in the "Drive issue" announcement, the Collaboratory release was delayed from 27th April to the 28th April**
21 21  
22 -Due to migration to new hardware, various EBRAINS services will be down for up to 1 hour while these services and their data are migrated. Please See our [[Releases >>doc:Collabs.the-collaboratory.Releases.WebHome]]page for more information on our release.
19 +**Collaboratory.Wiki**
23 23  
24 -=== **Infrastructure failure on 2021-10-04** ===
21 +* The new "Bucket" menu is now available in all collabs
22 +* Various UI fixes.
23 +* Collapsible macro styles have been updated.
24 +* Fixed some issues with our Search functionality.
25 +* Favourite collabs API has been developed for future integration into the UI.
26 +* Added a report button to collabs, you can now report unused or inappropriate collabs.
27 +* Issue for some users getting permission denied messages when they should not has been resolved.
25 25  
26 -A failure on the Openstack infrastructure at the Fenix site which hosts most of our services has brought down many EBRAINS service this morning before 9 AM CEST. A second event later in the morning at the same Fenix site brought down most other EBRAINS services. The infrastructure was brought back online in the afternoon and we have been reactivating services as quickly as possible. Some issues are still being addressed at the infrastructure level [17:00 CEST].
29 +**Due to team members being on vacation, the Collaboratory.Lab release will instead go ahead on Monday 3rd May.**
27 27  
28 -We apologize for the inconvenience and thank all users for their understanding.
31 +**Collaboratory.Lab**
29 29  
30 -=== **SSL Certificates expiring September 30th** ===
33 +* Nueron installation has been fixed and updated to latest version.
34 +* The "Copy shareable link" button should now work without manual intervention.
31 31  
32 -Our SSL certificates are produced by Let's Encrypt. One of their root certificates is expiring on September 30. This may cause issues for access to API services, especially from older browsers. You can find more information about these changes at the following links :
36 +=== **Collaboratory 2 release (2021-04-13)** ===
33 33  
34 -* [[https:~~/~~/letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/>>url:https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/]]
35 -* [[https:~~/~~/letsencrypt.org/certificates/>>url:https://letsencrypt.org/certificates/]]
38 +**Collaboratory.Wiki**
36 36  
37 -As mentioned in the above links, if you are using one of our APIs, you should take the following steps to prevent issues:
40 +* The new "Bucket" menu will be available in every new collab created, and will be rolled out to existing collab's in the coming days.
41 +* Users logged into the wiki, should now automatically be logged into the lab in an iFrame instead of needing to login again.
38 38  
39 -* You must trust ISRG Root X1 (not just DST Root CA X3)
40 -* If you use OpenSSL, you must have version 1.1.0 or later
43 +=== **Collaboratory 2 release (2021-03-30)** ===
41 41  
42 -If you access our services via a browser, please ensure that you are using a modern browser,  you can find more information here : [[https:~~/~~/letsencrypt.org/docs/certificate-compatibility/>>url:https://letsencrypt.org/docs/certificate-compatibility/]]
45 +The release going ahead on the 30th March will contain numerous upgrades and fixes throughout the Collaboratory Drive, Wiki and Lab.
43 43  
44 -If you are using an older device, you may no longer be able to access our services correctly, for a list of non-compatible devices please see [[https:~~/~~/letsencrypt.org/docs/certificate-compatibility/>>url:https://letsencrypt.org/docs/certificate-compatibility/]].
47 +**Collaboratory.Drive**
45 45  
46 -=== **Collaboratory 1 shutdown (2021-09-02)** ===
49 +* Incorrect name formats are now automatically fixed
50 +* Improvements to Automated tests.
47 47  
48 -Collaboratory 1 is shutting down Wednesday September 8th. As such, please ensure you have [[migrated>>https://wiki.ebrains.eu/bin/view/Collabs/collaboratory-migration/Tutorial/Migrate%20your%20data/]]  your data to Collaboratory 2. You can view our [[handy guide>>https://wiki.ebrains.eu/bin/view/Collabs/collaboratory-migration/Tutorial/Overview/]] on what data is migrated by our tools, as well as what is not covered by the semi-automated tools.
52 +**Collaboratory.Lab**
49 49  
50 -If you follow the above links, you will also find recorded migrathons, where you can find a lot of information to help you migrate your data. If you encounter any issues or problems while migrating your data, please contact [[EBRAINS support>>https://ebrains.eu/support/]] and we will get back to you as soon as possible.
54 +* Current Notebook image was rebuilt with extra extensions.  These are :  nbgitpuller,ipywidgets, jupyterlab-plotly, jupyter-matplotlib
51 51  
52 -NOTE: You are currently viewing Collaboratory 2, which will not be shut down.
56 +**Collaboratory.Wiki**
53 53  
54 -=== **Openshift issues (2021-07-09) (Resolved)** ===
58 +* The "Favourite" button was moved to the top right of a collab page.
59 +* New API added, this will allow users to get the Collab(CollabObject) via the DriveId - [[More information>>https://wiki.ebrains.eu/bin/view/Collabs/the-collaboratory/Technical%20documentation/For%20Developers/Collaboratory%20API/]]
60 +* Highlighted Collabs is now a responsive design.
61 +* Improvements to Automated tests.
55 55  
56 -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.
63 +Note: This release will cause all running containers to be reset.
57 57  
58 -**UPDATE 2021-07-12: **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.
65 +=== Collaboratory User Group (UG) meeting ===
59 59  
60 -**UPDATE 2021-07-12: **The Openstack issue has been fixed. Services should be back up and running. Thank you for your patience.
67 +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/]]
61 61  
62 -=== **Collaboratory Lab restart (2021-06-15)** ===
69 +=== Wiki update (2021-03-02) ===
63 63  
64 -The Collaboratory lab will be restarted for the purpose of changing a few background configurations.
71 +As well as numerous bug fixes and small improvements to the Wiki, we are also upgrading the current version of XWiki(Version 10.11.9) to the most recent version of XWiki (Version 12.10.2). We are also adding a few fixes to its integration in the Wiki front end . A new feature was added: a new "Like" (Represented by a [[image:https://a.slack-edge.com/production-standard-emoji-assets/13.0/google-medium/2764-fe0f.png||alt=":heart:"]]) feature that is now available on Collab pages. For now, it can be used to show support and approval for any Collab page you like and use, in the future, we will be expanding upon this functionality. 
65 65  
66 -=== **Collaboratory User Group (UG) meeting** ===
67 67  
68 -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/]]
69 -
70 70  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]].
71 71  
72 72  
73 -=== **Drive issue (Resolved 2021-06-14)** ===
77 +=== EBRAINS ticketing system (2021-03-02) ===
74 74  
75 -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.
76 -\\We apologise for any inconvenience this causes. 
79 +(% class="wikigeneratedid" %)
80 +The categories of tickets are being aligned to the description of [[services on the EBRAINS.eu website>>https://ebrains.eu/services/]]. We are using this opportunity to also upgrade the ticketing system to a more recent version.
77 77  
78 78  
79 -=== **Drive issue (Solved)** ===
83 +=== OnlyOffice license issue ===
80 80  
81 -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.
85 +We are aware that some users are getting issues when trying to use OnlyOffice similar to the following image~:
82 82  
83 -Until this is resolved, users will have issues accessing any functionality that requires Drive access. This mainly concerns the Lab and to a less extant, any service that requires access to the drive.
87 +[[image:1613726704318-340.png]].
84 84  
85 -**Potential fix: **We believe we have identified the issue and will be bringing the Lab service down for up to an hour at 10pm CEST on April 28th as we attempt to deploy this fix. All current Notebooks will be killed during this downtime. - Unfortunately this fix has not worked and we are looking at other solutions at the moment.
89 +We are working on this issue and will have it fixed as soon as possible, thank you for your patience and we apologise for any inconvenience caused.
86 86  
87 -**Potential fix 2: **We have another small release that should fix the issue at 13:30 CEST Today. All currently running notebooks will be killed during this downtime.
88 88  
89 -This issue has been resolved, please let support know if you encounter any issues with the lab. Thank you for your understanding.
92 +=== Collaboratory 2 release (2021-02-17) ===
90 90  
91 -We apologise for any inconvenience this has caused
94 +The release going ahead on 17th February has the following enhancements.
95 +
92 92  
93 -=== OnlyOffice license issue (Resolved) ===
97 +1. Mounting a new "Shared" drive for the ability to easily share links from Seafile. So going forward, any links that need to be shared should be generated in the "Shared " drive. The original "/drive" will be kept so it does not break any of the already existing links.
98 +1. OnlyOffice is being upgraded to the latest version. This should solve the issue listed below in the "Files locked in the Drive " section. The section will remain temporarily until it is verified this issue is fully fixed.
99 +1. Seafile file system is being increased
94 94  
95 -We are aware that some users are getting issues when trying to use OnlyOffice similar to the following image~:
101 +=== Collaboratory 1 maintenance ===
96 96  
97 -[[image:1613726704318-340.png]].
103 +Collaboratory 1 services will be down from 18:00 CET [[(my timezone)>>https://everytimezone.com/s/4a9daa55]] Thursday Jan 7 for maintenance. The services are being re-hosted from the EPFL/BBP infrastructure to the Fenix infrastructure. The OIDC authentication service will be reactivated first (within 30 minutes); all other services will follow in the evening. Once the Collaboratory 1 services are back online, you may find that files added to the storage within the last days do not initially appear. This will be remedied overnight as we synchronize the storage. Thank you for your patience and understanding.
98 98  
99 -We are working on this issue and will have it fixed as soon as possible, thank you for your patience and we apologise for any inconvenience caused.
105 +As a reminder the Collaboratory 1 services are deprecated and will be shut down in September 2021.
100 100  
107 +If you encounter issues with Collaboratory 1 after Friday 12:00 CET, please contact [[https:~~/~~/ebrains.eu/support>>url:https://ebrains.eu/support]]
101 101  
102 -=== SSL certificates (2020-12-04) (Resolved) ===
109 +(% class="wikigeneratedid" id="H" %)
110 +The re-hosting was completed on Thursday evening. Some services relying on the Collaboratory 1 may need to be restarted to take into account the new DNS entries. Please notify [[support>>https://ebrains.eu/support]] of any issues you identify.
103 103  
112 +
113 +=== SSL certificates (2020-12-04) ===
114 +
104 104  Our SSL Certificate provider (Let's Encrypt) has been using new certificates to sign our SSL certificates as described on their [[website>>https://letsencrypt.org/certificates]]. This requires updates on our servers and on your web browsers. The updates on your web browsers often go unnoticed by the user but in some cases your browser may inform you that it needs to fetch a new certificate. You can accept this safely; most browsers don't even mention it to the user.
105 105  
106 106  Note that this is not the same as accepting an exception in your browser because of a bad certificate. Accepting such exceptions can put your data and credentials at risk of a person-in-the-middle attack.
... ... @@ -108,7 +108,7 @@
108 108  We believe we have addressed all the issues that may arise from this change in SSL certificates. If you experience any issue, especially when accessing EBRAINS APIs, don't hesitate to contact [[support>>https://ebrains.eu/support]].
109 109  
110 110  
111 -=== Files locked in the Drive (2020-09-30) (Resolved) ===
122 +=== Files locked in the Drive (2020-09-30) ===
112 112  
113 113  A few users have reported issues in saving OnlyOffice edits to the Drive of a collab.
114 114