Changes for page Announcements
Last modified by hbpadmin on 2025/01/09 12:12
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,158 +1,117 @@ 1 -== ** Issueon the OpenShiftserver at CSCS (2021-12-28)** ==1 +=== **Drive issue** === 2 2 3 - TheEBRAINS OpenShift serverrunningatCSCS was detectedashavingcomedown. This issueaffectsalltheservicesrunningon thatOpenShiftserverincluding: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. 4 4 5 -* Collaboratory Lab, 6 -* image service, 7 -* atlas viewers, 8 -* simulation services (NEST desktop, TVB, Brain Simulation Platform) 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. 9 9 10 -We a re workingwith theCSCSteam toreactivate theserviceASAP.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. 11 11 12 - Wewillkeepupdatingthispagewithmore information as itcomesin.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. 13 13 14 - ==**IssueontheOpenShiftserver atCSCS(2021-11-24)**==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 - TheEBRAINS OpenShiftserverrunningatCSCS was detected as havingcomedownat 16:00 CEST. This issueaffectsallthe servicesrunning on that OpenShiftserverincluding:13 +We apologise for any inconvenience this has caused 17 17 18 -* Collaboratory Lab, 19 -* image service, 20 -* atlas viewers, 21 -* simulation services (NEST desktop, TVB, Brain Simulation Platform) 15 +=== **Collaboratory 2 release (2021-04-28)** === 22 22 23 - Weare workingwiththeCSCS teamandRedHat (provideroftheOpenStacksolutiononwhich OpenShiftruns)to reactivate theservice ASAP.17 +**Due to the problem described in the "Drive issue" announcement, the Collaboratory release was delayed from 27th April to the 28th April** 24 24 25 - The issue affected the central VM node of the OpenShift service. Restarting the VM required that we resolve multiple issues including restarting at the same IP address and unlocking the storage volumes ofthat VM. (% style="color:#16a085" %)The central node has now been restarted. The same issue has occurred on three other instances of OpenShift VMs. Theyhave been restarted too.OpenShiftis up and running again. The DNS redirection(s) to the maintenance page is being removed. The services should be operational again.19 +**Collaboratory.Wiki** 26 26 27 -(% style="color:#16a085" %)The root cause seems to be at the infrastructure level and RedHat is involved in analyzing that. 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. 28 28 29 - We willkeepupdating thispagewithmoreinformation as itcomes in.29 +**There was an issue during the release of the Lab, as such, the following has not yet been released and will be released on a different day.** 30 30 31 - ===**Maintenanceof multiple services (2021-11-11to2021-11-19)**===31 +**Collaboratory.Lab** 32 32 33 -We are migrating the last of our services away from an old cloud infrastructure. The production services were taken down on Wednesday November 17 and are now all back online. We will continue working on the non-production services, to return the services to the redundancy level prior to the migration, and various final tweaks. 33 +* Nueron installation has been fixed and updated to latest version. 34 +* The "Copy shareable link" button should now work without manual intervention. 34 34 35 - Pleasecontact [[support>>https://ebrains.eu/support]]aboutany new issues you identifyonourservices.36 +=== **Collaboratory 2 release (2021-04-13)** === 36 36 37 - The services which were migrated during this maintenance include:38 +**Collaboratory.Wiki** 38 38 39 -* Collaboratory Bucket (% style="color:#2ecc71" %)**DONE** 40 -* Knowledge Graph Search and API (% style="color:#2ecc71" %)**DONE** 41 -* OpenShift servers which includes: (% style="color:#2ecc71" %)**DONE** 42 -** Collaboratory Lab, (% style="color:#2ecc71" %)**DONE** 43 -** image service, (% style="color:#2ecc71" %)**DONE** 44 -** atlas viewers, 45 -** simulation services (NEST desktop, TVB, Brain Simulation Platform) 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. 46 46 47 -* EBRAINS Docker registry, (% style="color:#2ecc71" %)**DONE** 48 -* the Forum linked from the Collaboratory Wiki, (% style="color:#2ecc71" %)**DONE** (may have login issues) 49 -* the Education website. (% style="color:#2ecc71" %)**DONE** 43 +=== **Collaboratory 2 release (2021-03-30)** === 50 50 51 - Weapologizeforthe inconvenience andthankyouforyourunderstanding.45 +The release going ahead on the 30th March will contain numerous upgrades and fixes throughout the Collaboratory Drive, Wiki and Lab. 52 52 53 - ===**TechnicaldifficultiesontheDrive(2021-11-03)**===47 +**Collaboratory.Drive** 54 54 55 -The Drive has experienced some technical difficulties over the past weeks caused by multiple issues. 49 +* Incorrect name formats are now automatically fixed 50 +* Improvements to Automated tests. 56 56 57 - A reboot of the Drive server due to a hardware failure revealedan issue in the communicationbetween the Lab and the Drive. A containeris started foreach Lab user who opens the Lab in their browser to run their notebooks. That container remains active bydefault 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 askLabusers 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//.52 +**Collaboratory.Lab** 58 58 59 - Thecloud infrastructurehatthe Drive is runningon is being upgraded andtheDrive service had tobe moved tothe newer servers. Anincorrectmanagementcommand of theservercaused the migration of thedata tobe launched twice,withthesecondtransferoverwriting productiondata dated Nov 2 withstale data from Oct 20.Several backup issuesstacked on top of this problem.We have beenable to recover a backup which was made onthe night of Sunday Oct 31 to Monday Nov 1. Weare verifying thatwe cannotidentify issueswith this data before we reopen accessto theDrive. **Some dataloss is expected** for data stored on the Drive after thatbackupand before we putup a banner asking users,as a precaution, not to add new data to the Drive on TuesdayNov 2 around noon. Many countries had a bank holiday on Nov 1 so forny users,the dataloss shouldbe of a few hours on Nov 2.54 +* Current Notebook image was rebuilt with extra extensions. These are : nbgitpuller,ipywidgets, jupyterlab-plotly, jupyter-matplotlib 60 60 61 - We sincerely apologize for the problems incurred. Weappreciate that the service we provide mustbe trustworthy forour users.e are taking the following actions to ensure that similar problems do not happen again:56 +**Collaboratory.Wiki** 62 62 63 -* Reviewofthe backupproceduresontheDriveserver whichwill be extendedto allEBRAINS services which we manage.64 -* Requestnotificationfromtheunderlyinginfrastructurewhenrvicecountsreachthe limitmposed by theirtorage quota.65 -* Improve theidentificationofproductionserverstoreducetherisk of theoperationsteam misidentifying which serversarerunningproductionservice.66 -* Improve our procedureforcommunicationaboutsuch incidents.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. 67 67 68 - (% style="color:#16a085"%)**The Driveserviceis up again. We haverecovered all thedata that wecould. The Drive isworking normallyagain. Wewillbe performinga Drive upgrade ASAP.checkthe Wiki bannerformoreinformation.**63 +Note: This release will cause all running containers to be reset. 69 69 70 - Additionally,theCollaboratoryteam will be looking into mirroringservicesonto more thanone Fenix site to reducedowntimewhen incidents occur. This task will be more challengingfor some services than for others; it might not be materially feasible for some services, but we will be analysing possibilities for each Collaboratory service.65 +=== Collaboratory User Group (UG) meeting === 71 71 72 - ===**Maintenance on 2021-10-19** ===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/]] 73 73 74 - Dueto migrationto new hardware, various EBRAINS services will be down for upto 1 hour while these services andtheir data aremigrated. Please See our [[Releases >>doc:Collabs.the-collaboratory.Releases.WebHome]]pagefor more information on our release.69 +=== Wiki update (2021-03-02) === 75 75 76 - ===**Infrastructure failure on 2021-10-04**===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. 77 77 78 -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]. 79 79 80 - Weapologize forthe inconvenience andthankall usersfor their understanding.74 +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]]. 81 81 82 -=== **SSL Certificates expiring September 30th** === 83 83 84 - OurSSLcertificates are produced by Let's Encrypt. One of their root certificates is expiringon September 30. Thismaycause issues for accessto API services, especially fromolderbrowsers. You can find more information about these changes at the following links :77 +=== EBRAINS ticketing system (2021-03-02) === 85 85 86 - *[[https:~~/~~/letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/>>url:https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/]]87 - * [[https:~~/~~/letsencrypt.org/certificates/>>url:https://letsencrypt.org/certificates/]]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. 88 88 89 -As mentioned in the above links, if you are using one of our APIs, you should take the following steps to prevent issues: 90 90 91 -* You must trust ISRG Root X1 (not just DST Root CA X3) 92 -* If you use OpenSSL, you must have version 1.1.0 or later 83 +=== OnlyOffice license issue === 93 93 94 - If you accessourservicesviaa browser, please ensure thatyou are using a modern browser,you can find moreinformationhere: [[https:~~/~~/letsencrypt.org/docs/certificate-compatibility/>>url:https://letsencrypt.org/docs/certificate-compatibility/]]85 +We are aware that some users are getting issues when trying to use OnlyOffice similar to the following image~: 95 95 96 - If you are using an older device, youmay 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/]].87 +[[image:1613726704318-340.png]]. 97 97 98 - ===**Collaboratory1shutdown(2021-09-02)**===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. 99 99 100 -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. 101 101 102 - Ifyou follow theabove links, you will also findrecorded migrathons, whereyoucanfind a lot of information to help you migrateyour data. If you encounter any issuesorproblems while migrating your data, please contact [[EBRAINS support>>https://ebrains.eu/support/]] and we will get back to you as soon as possible.92 +=== Collaboratory 2 release (2021-02-17) === 103 103 104 -NOTE: You are currently viewing Collaboratory 2, which will not be shut down. 94 +The release going ahead on 17th February has the following enhancements. 95 + 105 105 106 -=== **Openshift issues (2021-07-09) (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 107 107 108 - TheOpenshift service has gone down. As theCollaboratoryLaband the Image service both rely onhis service, they are currently unavailable. We are investigating this issue and it will be resolved as soon as possible. We apologise for any inconveniencecaused.101 +=== Collaboratory 1 maintenance === 109 109 110 - **UPDATE2021-07-12:**Thesue seems tobewiththeOpenstackservers.It is alsoaffectingafewmoreVMsasidefrom theOpenshift service. The infrastructure teamislookingintoit.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. 111 111 112 - **UPDATE 2021-07-12: **The Openstackissue hasbeenfixed.Servicesshould bebackupandrunning.Thankyouforyourpatience.105 +As a reminder the Collaboratory 1 services are deprecated and will be shut down in September 2021. 113 113 114 - ===**CollaboratoryLabrestart(2021-06-15)**===107 +If you encounter issues with Collaboratory 1 after Friday 12:00 CET, please contact [[https:~~/~~/ebrains.eu/support>>url:https://ebrains.eu/support]] 115 115 116 -The Collaboratory lab will be restarted for the purpose of changing a few background configurations. 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. 117 117 118 -=== **Collaboratory User Group (UG) meeting** === 119 119 120 - TheUGmeeting is a greatway to stayinformed about recent and upcomingchangesto theCollaboratory aswell 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/]]113 +=== SSL certificates (2020-12-04) === 121 121 122 -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]]. 123 - 124 - 125 -=== **Drive issue (Resolved 2021-06-14)** === 126 - 127 -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. 128 -\\We apologise for any inconvenience this causes. 129 - 130 - 131 -=== **Drive issue (Solved)** === 132 - 133 -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. 134 - 135 -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. 136 - 137 -**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. 138 - 139 -**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. 140 - 141 -This issue has been resolved, please let support know if you encounter any issues with the lab. Thank you for your understanding. 142 - 143 -We apologise for any inconvenience this has caused 144 - 145 -=== OnlyOffice license issue (Resolved) === 146 - 147 -We are aware that some users are getting issues when trying to use OnlyOffice similar to the following image~: 148 - 149 -[[image:1613726704318-340.png]]. 150 - 151 -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. 152 - 153 - 154 -=== SSL certificates (2020-12-04) (Resolved) === 155 - 156 156 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. 157 157 158 158 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. ... ... @@ -160,7 +160,7 @@ 160 160 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]]. 161 161 162 162 163 -=== Files locked in the Drive (2020-09-30) (Resolved)===122 +=== Files locked in the Drive (2020-09-30) === 164 164 165 165 A few users have reported issues in saving OnlyOffice edits to the Drive of a collab. 166 166