T279303 Migrate OTRS CE 6 to Znuny LTS fork (original) (raw)
Migrate OTRS CE 6 to Znuny LTS fork
- Edit Task
- Edit Related Tasks...
- Create Subtask
- Edit Parent Tasks
- Edit Subtasks
- Merge Duplicates In
- Close As Duplicate
- Edit Related Objects...
- Edit Commits
- Edit Mocks
- Mute Notifications
- Protect as security issue
The Wikimedia Foundation will migrate its instance of OTRS Community Edition 6 to a maintained FOSS fork, Znuny LTS. The patch consists of rebranding, it's graphics and text changes to re-mark the software under its new name. The risk here is low, the migration is expected to go relatively quickly and painlessly.
The migration is scheduled to take place from 07:00-09:00 UTC on 13 April, OTRS/Znuny LTS will be inaccessible to agents during that time. Once complete, agents should be able to log in an resume work as normal. There will be no functional changes to the user interface or experience at this time.
Related Changes in Gerrit:
Event Timeline
Keegan triaged this task as Medium priority.
@akosiaris I assume the usual process of emails being held in queue during the migration will occur? My other question, we can assure people that if something happens this is easy to roll back and there's no direct risk of data loss, correct? (naturally there's risk involved in everything, I'm checking our tolerances).
@akosiaris I assume the usual process of emails being held in queue during the migration will occur?
Yes.
My other question, we can assure people that if something happens this is easy to roll back
Yes, this is easy to rollback. With major version bumps (e.g. 5.x -> 6.x) aside, the upgrade process never really had difficult to revert steps like database schema upgrades.
and there's no direct risk of data loss, correct? (naturally there's risk involved in everything, I'm checking our tolerances).
As you mention, there's always risk. From what I 've seen this upgrade isn't going to touch anything in the database, so I would be very surprised if something like that where to happen, but I can't 100% guarantee 0 data loss.
That being said, we do take backups so total loss is avoidable. If somehow the upgrade manages to irrevocably corrupt the database, we do have the ability to revert to a state a couple of days old.
Sounds good, thank you.
If we need help from Znuny we can open a ticket with them at support@znuny.com.
I am gonna be bold and resolve this as it pertains to the actual migration and that part seems to have gone quite well. I am pretty sure we have a ton of followup work, especially regarding relabelling/rebranding, but let's track all those in their own respective tasks.
I am gonna be bold and resolve this as it pertains to the actual migration and that part seems to have gone quite well. I am pretty sure we have a ton of followup work, especially regarding relabelling/rebranding, but let's track all those in their own respective tasks.
Yes, thank you, that's the intention.
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits