Hi Lars, ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, December 8th, 2021 at 9:39 PM, Lars Vogdt <lars@linux-schulserver.de> wrote:
Hi Attila
...and welcome! :-)
Thank you ::)
Am Tue, 07 Dec 2021 05:33:55 +0000
schrieb Attila Pinter adathor@protonmail.com:
I just would like to follow up the wiki update topic from IRC:
This week I would like to start playing with OBS, going to set up an
env for it and start looking into the wiki build. If you have any
advice throw it my way ;)
To give you something to start playing:
https://build.opensuse.org/package/show/home:lrupp:mediawiki/container-openS...
This is great, I just started to play with OBS (shameful, I know, but better later than never ^_^), and if I got that right we can build from OBS directly to registry-o-o. I think we can set up this project, might need an entrypoint of just shove everything in the Dockerfile and can get it over with fairly quickly.
I have a few pretty hectic weeks at work, but by the end of next week
I should be good to work on this project. If all goes well I can keep
on maintaining things going forward. If there is a deadline on this
please let me know so can try and prioritize things differently.
I know that Christian is not that happy with my solution (just taking
the mediawiki package from server:php:applications), as it just allows
one version of mediawiki, but that should not harm in a fully
containerized environment anyway. At the moment, I just see the benefit
in us not maintaining another application in parallel. (And in case
that we really want more than one mediawiki version on one system, I
hope we can at least find a temporary solution for any migration.) But
I'm happy to discuss this...
I think if we really need to we can host as many different versions as we need to. Don't see the use case why would we, but if we containerize things that will certainly help us in the future. Will also ease updating the application, and OBS can be used to build daily the container so we have no vulnerabilities in the container OS.
In case Christian agrees, the next steps would be:
1. https://build.opensuse.org/project/show/openSUSE:infrastructure:wiki
-> adjust all plugin packages to build and work successful with the
latest mediawiki package. Maybe, we can get rid of one of two of
these plugins, but I guess the packaging can happen in parallel to
the discussion of the usefulness of each single plugin.
2. Check the search functionality. As Christian said: the most critical
point here is elasticsearch. Good: the mediawiki foundation seems to
use elasticsearch in their installation as well, so this should see
long-term support. Bad: we might need a way to package and run the
'right' elasticsearch version.
Note: elasticsearch is currently running on other servers. So we
need a dedicated package/containers for this as well.
As much as I love containers and microservices I would try and avoid containerizing a monolith Java application like Elasticsearch. Christian mentioned this on IRC: "if I get https://www.mediawiki.org/wiki/Extension:CirrusSearch right, we'll need elasticsearch 6.8.x (actually "6.5.4 recommended", but let's try the latest 6.8.x instead of that even older version)". We could package Elasticsearch 6.8/6.5.4, and if memory serves well there are builds available from Elasticsearch to help this process. I think 6.8 will work for us fine, they rarely implement anything major between minor releases.
3. A new VM (at least has host for the containers or for the 'plain
packages') to test if everything works. We can use a plain install
for this step. Therefor testing can happen everywhere.
I plan to set up a local environment as well, but if we go for a new VM could that be on MicroOS? Transactional-updates and SELinux makes it pretty attractive. If it works out - even if we go with Leap - we could just flip the DNS record to point to this new VM in a blue-green deployment fashion?
4. Check and adjust the Salt setup. Again: testing can happen
everywhere...
5. Test migration: use a copy of the database(s) and local files to
finally test (and automate) the upgrade of all(!) wikis in one, big
step.
Note: all wikis are currently provided by a single mediawiki
installation.
Regards,
Lars