Hi back from vacation for the first day - and reading this gives me the impression that I should stay away for longer... ;-) On Mon, 19 Jun 2017 22:43:07 +0200 Christian Boltz wrote:
TL;DR Everything is ready from my side, when can we do it? ;-))
Congratulations!!!
So, what do we need to really do the wiki update and migration? - review of the salt code
I guess this is mainly something for Theo?
- review of the mediawiki and elasticsearch packages
Looks ok to me. Should those packages be merged/moved into openSUSE:infrastructure? IMHO they are not conflicting and can be handled completely independent even there (without the need to have another repo to maintain/watch).
- 42.3 JeOS images [1]
Fine with me (as I said: the one who does, decides)... ;-)
- a new VM for the wiki (apache etc.). Note that this VM needs to access the internet to fetch RSS feeds and files from github
Do you already know which external pages need to be reached? Should we open just Port 80 and 443? => I would love to keep the wiki machine as protected as possible, so while it is possible to NAT everything, I would more go for NAT just what is needed..
- a new VM for elasticsearch, ideally only reachable from the wiki VM
In Theory easily possible by connecting the two machines directly together. But I'm asking myself if we might need another VM if the search takes too long? Or we play with just another VLAN for this... Suggestions welcome.
- a mysql database for each wiki on the galera cluster (ideally with names like wiki-en and usernames == database name)
Brings me to the question who is currently maintaining the DB-Cluster as master admin?
- optional: a "master" mysql user which can be used to create all the wiki-* users and databases
From my point of view as former DB-Admin: no.
- the latest wiki database and files from Provo. For the real (non-test) move, we also need to set $wgReadOnly in Provo to make the current wiki read-only while we move it.
Something for mmaher or rbrown?
- some configuration on login.o.o for each wiki (similar to what we have for en-test.o.o already)
It's not only login.o.o - haproxy needs adaptions, too.
- a backup concept, even if we hopefully never need it ;-) I'd propose - daily database dumps
should be done already on the cluster. The question might be if you want to have a backup on the machine itself, too. This should be easily doable with the credentials of the wiki-database user.
- daily backups of /srv/www/ which basically contains the uploaded files (+ some small config files etc.). Maybe rsnapshot would be a good solution since 99% of the uploaded files don't change.
Who should be able to access the backups? What about another virtual disk on the VM that can be used as backup disk (with whatever tool you like)? Daily snapshots of all the disks are enabled already on the filer.
"Really soon" means: We have 36 days left until the 42.3 release, and I'd like to do the wiki update before that - ideally two weeks before the release (= in ~3 weeks) because doing such a major change on release day would be insane.
I know there are quite some dependencies, but I hope everybody involved with one of the requirements will have some time to help with his/her part.
BTW: Does the wiki also sent Emails? Maybe you can setup a coordination meeting to get the main people behind this project and start the organizational stuff?
[1] As I already wrote in my "42.3 JeOS" mail two weeks ago, I'd like to use Leap 42.3 from the beginning, even if it's still under development. I'll happily help to create the JeOS image if someone creates the openSUSE:infrastructure:Images:openSUSE_Leap_42.3 project in OBS and gives me permissions.
done. Just play along on openSUSE:infrastructure:Images:openSUSE_Leap_42.3 with kind regards, Lars -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org