docker-otrs
docker-otrs copied to clipboard
juanluisbaptiste
Migrating to Znuny
Due to OTRS community edition no longer available, Znuny has made a statement to support OTRS 6 with newer versions under the new name.
Source: https://forums.otterhub.org/viewtopic.php?f=53&t=42228 https://www.znuny.org/why https://github.com/znuny/znuny
Any comment on this? Are there any plans of migrating to znuny instead of staying with the now-dead OTRS 6?
Hi @sjal ,
Well this was something that I saw coming for some time now, OTRS AG has not been very transparent with that would happen with the future of the community edition, after OTRS 8 was released and there wasn't a community edition ver 7 I supposed that version had come to an end and we would have to wait for the official announcement, that has now happened.
So yes, I will support znuny too, as soon as I can.
Cool, great :)
OTRS 7 was supposed to be open sourced November 2020 - which obviously never happened. Glad to hear you're planning to support Znuny
Hi @fajfer I have pushed on juanluisbaptiste/znuny:latest a first version using the znuny release for testing.
I'm still unsure if I should update juanluisbaptiste/otrs to the znuny branch so current users also get the updated versions as currently znuny is an LTS release of OTRS community edition, so there will not be any breaking changes. Or stop maintaining the otrs branch and switch development to the znuny branch.
The issue with the first option is that branding has been changed from ((OTRS)) Community Edition to ZNuny LTS so it could confuse users, but is just a cosmetic change. The other option is to maintain both for some time and then when the znuny repo is better known as the alternative stop maintaining the otrs repo and stick with znuny only.
WDTY ?
@juanluisbaptiste Without reading all of your detailed documentation, it is important to make sure the System Configuration is rebuild properly and the update script is always executed:
-
bin/otrs.Console.pl Maint::Config::Rebuild --cleanup- remove old, deprecated settings which are not present in any of the install files in Kernel/Config/Files/XML/, see also https://github.com/znuny/Znuny/issues/12 as an example -
scripts/DBUpdate-to-6.plshould take care of all other tasks which need to be performed even after a patch level upgrade
I think we should let everyone who doesn't follow these stuff that OTRS they were using is now deprecated. We could keep znuny as separate branch to try to stabilize it (I can help out with the tests, I'm almost done struggling with my thesis but I'm a daily OTRS user). I leave the choice entirely to yourself, obviously, as you're the owner of the repo. What I would do, is implement deprecation warnings, keep master for a while with warnings on the deprecation until our version of the Znuny image is stable (while allowing others to test it) and then after you're happy with it just make it the new master. I wouldn't really then bother with implementing new features to the deprecated branch at all
@juanluisbaptiste Without reading all of your detailed documentation, it is important to make sure the System Configuration is rebuild properly and the update script is always executed:
* `bin/otrs.Console.pl Maint::Config::Rebuild --cleanup` - remove old, deprecated settings which are not present in any of the install files in Kernel/Config/Files/XML/, see also [znuny/Znuny#12](https://github.com/znuny/Znuny/issues/12) as an example
I was not aware of this command, I don't remember seeing it on the official docs but I can add it.
* `scripts/DBUpdate-to-6.pl` should take care of all other tasks which need to be performed even after a patch level upgrade
This script is run both when doing minor or major upgrades when doing the database upgrade.
Hey,
* `bin/otrs.Console.pl Maint::Config::Rebuild --cleanup` - remove old, deprecated settings which are not present in any of the install files in Kernel/Config/Files/XML/, see also [znuny/Znuny#12](https://github.com/znuny/Znuny/issues/12) as an example
Added. I also have been testing the upgrade from OTRS and everything is going fine! the only thing I noticed is that ftp.otrs.org is down, so the Package Manager is not working and takes a lot of time to load while it times out with this error on the log output:
Message: Can't perform GET on https://ftp.otrs.org/pub/otrs/misc/packages/repository.xml: 500 Can't connect to ftp.otrs.org:443
otrs_1 |
otrs_1 | RemoteAddress: 172.19.0.1
otrs_1 | RequestURI: /otrs/index.pl?Action=AdminPackageManager
otrs_1 |
otrs_1 | Traceback (94):
otrs_1 | Module: Kernel::System::WebUserAgent::Request Line: 221
otrs_1 | Module: Kernel::System::Package::_Download Line: 3583
otrs_1 | Module: Kernel::System::Package::PackageOnlineRepositories Line: 1341
otrs_1 | Module: Kernel::Modules::AdminPackageManager::Run Line: 1526
otrs_1 | Module: Kernel::System::Web::InterfaceAgent::Run Line: 1135
otrs_1 | Module: ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler Line: 38
otrs_1 | Module: (eval) (v1.99) Line: 207
otrs_1 | Module: ModPerl::RegistryCooker::run (v1.99) Line: 207
otrs_1 | Module: ModPerl::RegistryCooker::default_handler (v1.99) Line: 173
otrs_1 | Module: ModPerl::Registry::handler (v1.99) Line: 32
@rkaldung I don't know if it is temporal or not but really I think they just removed it so it needs to be updated with Znuny FTP address.
Apart from that the upgrade went fine ! Tomorrow I will start working on updating the README file with information about the switch.
@juanluisbaptiste The latest release contains the fixed URL pointing to download.znuny.org
@kordianbruck excellent, I will update the beta image.
Updated and new images being built.
@fajfer did you test the znuny beta image?
Hey, yes I have in the testing environment. I've used the newest image also but generally have no problems whatsoever - they seem to work flawlessly but since Znuny is (for now) mostly security updates it was kinda expected
I'm planning to update my company's OTRS to Znuny this weekend, haven't tested this on fresh install but I'm going to do it this weekend as well
@fajfer how went your migratoin ? I have migrated other of my customers with no issues.
I'm sorry I have not finished the switch but I will work on this over these weekend.
Hey, I forgot I did the migration actually, which might be a good sign.
No hurry whatsoever about the switch, wishing you a blessed and holy Easter!
Ok I added a notice to the README file letting now that we now use the znuny release and pushed new images using it.
Hi @rkaldung and @fajfer , I noticed that now Znuny started releasing a new version with new features since 6.1.x. I updated the image to the LTS release (v6.0.36), but I plan to support both. The master branch will use the new 6.1.x release and znuny_6_0_x branch will be used for the LTS version.
I'll let you know when this is ready, probably for next week.
Hallo,
I am still running juanluisbaptiste/otrs:6.0.28
- Can the Znuy image be used for production already?
- Are there any migration steps to be noticed?
Thanks for your great work!
@rdxmb yes, you can use it without issues, but I still only support the LTS release, the latest release is 6.0.36.
I haven't had time to work with the new Znuny versions yet (6.1.x), which have new features.
@rdxmb yes, you can use it with issues, but I still only support the LTS release, the latest release is 6.0.36.
@juanluisbaptiste What are the issue? Maybe I can help.
@rkaldung with the LTS version none, with the new releases, lack of time to work on it :disappointed:
Oops now I get what you meant, it should have been without issues, I just updated my answer.
Hello @juanluisbaptiste , I see that https://hub.docker.com/layers/juanluisbaptiste/otrs has tags like 6.0.36 and 6.0.37 , while https://hub.docker.com/r/juanluisbaptiste/znuny/tags has only older images
I'm still unsure if I should update juanluisbaptiste/otrs to the znuny branch
So you decided to push the znuny-Images to https://hub.docker.com/layers/juanluisbaptiste/otrs ?
Kind regards and thanks again for your great work with this project.
As the tagging process of versioned images is a manual process I'm only tagging the images from juanluisbaptiste/otrs, and znuny only has an auto-build of the master branch. I have deleted the 6.0.32 and 0.33 tags on juanluisbaptiste/znuny for now to avoid confusions.
As the tagging process of versioned images is a manual process I'm only tagging the images from
juanluisbaptiste/otrs, and znuny only has an auto-build of the master branch. I have deleted the 6.0.32 and 0.33 tags onjuanluisbaptiste/znunyfor now to avoid confusions.
At some point I will have to do it the other way around or work on automating those tagged builds for both repos.
I also started to work on supporting the new znuny versions, today I sync'ed the znuny_6_0_x branch with master, and built the latest 6.0.38 release from there, that way master now can be used for the new releases and znuny_6_0_x will be used for LTS releases only. I also did a rebuild of master with znuny 6.2.1 and it seems to work fine with no modifications to the image, so I will be pushing that release shortly, but first I need to update the documentation too.
The main issue now is that I do not have many time to work on this, since I switched jobs some months ago I'm not using this images any more so I have less time to work on them, any help would be appreciated.
Thanks for your answer and the transparent information. I will check if I can support this project.
Hi, I started to upgrade Znuny image to last version. I will push with PR, but I don't know when, I have no time too ;)
++
Le mar. 9 nov. 2021 à 10:06, Marc Bihlmaier @.***> a écrit :
Thanks for your answer and the transparent information. I will check if I can support this project.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/juanluisbaptiste/docker-otrs/issues/104#issuecomment-963949686, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACLNNXEYFBB5L7KLVYLKYW3ULDQCPANCNFSM4WHJH3IQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
