Changes for page Announcements
Last modified by hbpadmin on 2025/01/09 12:12
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. mmorgan1 +XWiki.chaney08 - Content
-
... ... @@ -1,130 +1,60 @@ 1 -=== **Maintenanceofmultipleservices (2021-11-11 to 2021-11-19)**===1 +=== Collaboratory 2 release (2021-03-30) === 2 2 3 - Wearemigratingthelast of our services away from an oldcloud infrastructure.TheserviceswillbetakendownithernWednesdayNovember17 from8:00CET forupto12 hours.3 +The release going ahead on the 30th March will contain numerous upgrades and fixes throughout the Collaboratory Drive, Wiki and Lab. 4 4 5 -We are facing issues with the recovery of some services on the new cloud infrastructure. At this point the issues seem to be linked to a network problem. 6 6 7 - Theservices which willbetakendownclude:6 +Note: This will cause all running containers to be reset. 8 8 9 -* Collaboratory Bucket (% style="color:#2ecc71" %)**DONE** 10 -* Knowledge Graph Search and API (% style="color:#e74c3c" %)**ONGOING** 11 -* OpenShift servers which includes: (% style="color:#e74c3c" %)**ONGOING** 12 -** Collaboratory Lab, 13 -** image service, 14 -** atlas viewers, 15 -** simulation services (NEST desktop, TVB, Brain Simulation Platform) 8 +=== Collaboratory User Group (UG) meeting === 16 16 17 -The following servicesmayalsobe brought downon the same daysoratsome other timebeforeFridayNovember19:10 +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 -* EBRAINS Docker registry, (% style="color:#2ecc71" %)**DONE** 20 -* the Forum linked from the Collaboratory Wiki, (% style="color:#2ecc71" %)**DONE** (may have login issues) 21 -* the Education website. (% style="color:#2ecc71" %)**DONE** 12 +=== Wiki update (2021-03-02) === 22 22 23 - We apologizefor the inconvenience. Westrive tomake interruptions as short aspossible.14 +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. 24 24 25 -=== **Technical difficulties on the Drive (2021-11-03)** === 26 26 27 - TheDrivehasexperiencedsometechnicaldifficultiesoverthe past weeksbymultiplesues.17 +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]]. 28 28 29 -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//. 30 30 31 - Thecloud 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 datedNov 2 with stale data from Oct 20.Severalbackup issues stacked on top of this problem. We have been able to recover a backup which was madeonthe night of Sunday Oct 31 to Monday Nov 1. We are verifyingthat we cannot identifyissues with this data before we reopen access to the Drive. **Somedata 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 Nov2around noon. Many countries had a bank holiday on Nov1so for many users, the data loss should be of a few hours on Nov2.20 +=== EBRAINS ticketing system (2021-03-02) === 32 32 33 -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: 22 +(% class="wikigeneratedid" %) 23 +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. 34 34 35 -* Review of the backup procedures on the Drive server which will be extended to all EBRAINS services which we manage. 36 -* Request notification from the underlying infrastructure when service accounts reach the limit imposed by their storage quota. 37 -* Improve the identification of production servers to reduce the risk of the operations team misidentifying which servers are running production service. 38 -* Improve our procedure for communication about such incidents. 39 39 40 - (% style="color:#16a085"%)**The Drive service is up again. We have recovered all the data that we could. The Drive is working normallyagain. Wewill be performing a Drive upgrade ASAP.check theWiki bannerfor more information.**26 +=== OnlyOffice license issue === 41 41 42 - Additionally, theCollaboratory teamwill be looking into mirroring servicesonto more than one Fenix sitetoreduce down timewhen incidents occur. Thistask will be morechallengingforsomeservicesthanfor others;it mightnotbemateriallyeasiblefor some services,but we will beanalysingpossibilitiesfor each Collaboratoryservice.28 +We are aware that some users are getting issues when trying to use OnlyOffice similar to the following image~: 43 43 44 - === **Maintenanceon2021-10-19** ===30 +[[image:1613726704318-340.png]]. 45 45 46 - Dueto migration to new hardware,various EBRAINS serviceswill be downfor upto 1hour while theseservices andtheirdata aremigrated.PleaseSeeour[[Releases>>doc:Collabs.the-collaboratory.Releases.WebHome]]pagefor moreinformationonur release.32 +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. 47 47 48 -=== **Infrastructure failure on 2021-10-04** === 49 49 50 - Afailure on the Openstack infrastructure at the Fenix site which hosts most of our services has brought down many EBRAINS service this morning before 9 AMCEST. A second eventlater in the morning at the same Fenix sitebrought down most otherEBRAINS services. The infrastructure was brought back online in the afternoon and we have been reactivating services as quicklyaspossible. Some issues arestill beingaddressedat the infrastructure level [17:00CEST].35 +=== Collaboratory 2 release (2021-02-17) === 51 51 52 -We apologize for the inconvenience and thank all users for their understanding. 37 +The release going ahead on 17th February has the following enhancements. 38 + 53 53 54 -=== **SSL Certificates expiring September 30th** === 40 +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. 41 +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. 42 +1. Seafile file system is being increased 55 55 56 - OurSSL certificates are produced by Let's Encrypt. One of their root certificates is expiring on September 30. This may cause issues forccesstoAPI services, especiallyfromolder browsers. You can findmore informationaboutthese changes atthe following links :44 +=== Collaboratory 1 maintenance === 57 57 58 -* [[https:~~/~~/letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/>>url:https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/]] 59 -* [[https:~~/~~/letsencrypt.org/certificates/>>url:https://letsencrypt.org/certificates/]] 46 +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. 60 60 61 -As mentionedinthe abovelinks,if youareusingoneofourAPIs, you shouldtakethe followingstepsto preventissues:48 +As a reminder the Collaboratory 1 services are deprecated and will be shut down in September 2021. 62 62 63 -* You must trust ISRG Root X1 (not just DST Root CA X3) 64 -* If you use OpenSSL, you must have version 1.1.0 or later 50 +If you encounter issues with Collaboratory 1 after Friday 12:00 CET, please contact [[https:~~/~~/ebrains.eu/support>>url:https://ebrains.eu/support]] 65 65 66 -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/]] 52 +(% class="wikigeneratedid" id="H" %) 53 +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. 67 67 68 -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/]]. 69 69 70 -=== **Collaboratory 1shutdown(2021-09-02)**===56 +=== SSL certificates (2020-12-04) === 71 71 72 -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. 73 - 74 -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. 75 - 76 -NOTE: You are currently viewing Collaboratory 2, which will not be shut down. 77 - 78 -=== **Openshift issues (2021-07-09) (Resolved)** === 79 - 80 -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. 81 - 82 -**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. 83 - 84 -**UPDATE 2021-07-12: **The Openstack issue has been fixed. Services should be back up and running. Thank you for your patience. 85 - 86 -=== **Collaboratory Lab restart (2021-06-15)** === 87 - 88 -The Collaboratory lab will be restarted for the purpose of changing a few background configurations. 89 - 90 -=== **Collaboratory User Group (UG) meeting** === 91 - 92 -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/]] 93 - 94 -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]]. 95 - 96 - 97 -=== **Drive issue (Resolved 2021-06-14)** === 98 - 99 -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. 100 -\\We apologise for any inconvenience this causes. 101 - 102 - 103 -=== **Drive issue (Solved)** === 104 - 105 -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. 106 - 107 -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. 108 - 109 -**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. 110 - 111 -**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. 112 - 113 -This issue has been resolved, please let support know if you encounter any issues with the lab. Thank you for your understanding. 114 - 115 -We apologise for any inconvenience this has caused 116 - 117 -=== OnlyOffice license issue (Resolved) === 118 - 119 -We are aware that some users are getting issues when trying to use OnlyOffice similar to the following image~: 120 - 121 -[[image:1613726704318-340.png]]. 122 - 123 -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. 124 - 125 - 126 -=== SSL certificates (2020-12-04) (Resolved) === 127 - 128 128 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. 129 129 130 130 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. ... ... @@ -132,7 +132,7 @@ 132 132 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]]. 133 133 134 134 135 -=== Files locked in the Drive (2020-09-30) (Resolved)===65 +=== Files locked in the Drive (2020-09-30) === 136 136 137 137 A few users have reported issues in saving OnlyOffice edits to the Drive of a collab. 138 138