Am Mittwoch, 31. Mai 2017, 09:09:12 CEST schrieb Lars Vogdt:
Am 30. Mai 2017 14:19:37 MESZ schrieb Christian
[cross-post - please reply only on one of the
Please consider sending separate emails, using the reply-to feature of
your mua or simply put the other lists (that you want to inform, but
not have discussions) in bcc next time. That is way less complicated
for all the others and might result in one thread on only one mailing
list, if done right.
I never tried if our MLs accept mails if the list isn't in To or CC, but
I slightly doubt ;-)
Having all replies on one mailinglist? Well, nice try - but all attemps
I've seen failed and ended up in more cross posts and/or discussions on
the "wrong" list because people aren't subscribed to the "right"
Therefore I took the "whatever ML, but only one please" way which worked
surprisingly well. (Actually, your mail was the only one with me in CC,
everybody else did a list-reply to one ML.)
The feedback I received so far looks good - the most serious complaint
was that the login no longer happens automatically if you are logged in
on another *.opensuse.org page. I wouldn't consider this a showstopper
(it's a known and expected change from switching to openID), but if
someone wants to improve it, that's more than welcome ;-)
There was also the idea of a responsive design. Any volunteers?
This is something that takes more time, so it has to happen after the
wikis get updated - but starting the work now isn't a problem.
BTW: What about https://progress.opensuse.org/issues/15906
You never answered after my comment...
Oh, and I noticed a possible issue with the github integration extension
which will need some more testing.
visited the Heroes talk at the openSUSE Conference already
know - there is visible progress on the wiki update and I have a
*test* wiki running :-)
Great news! Can we see an article about this on news.opensuse.org
Not for the call for testing, but I'll make sure to have an article
there when the first production wiki gets updated ;-)
I also have a few topics that will end up on my blog and on planet.o.o,
for example about packaging MediaWiki extensions. I'll of course include
a link to en-test.o.o there ;-)
also something that isn't too new - the database dump I used
to setup the test wiki ;-) It's from last August, so please don't
worry about the outdated content ;-)
What about newer dumps - or even some automated ways of getting them?
IMHO that should help not only for testing but also for the real
migration (now and for later version upgrades).
That's the theory.
In practise, it takes too much time. Importing the dump takes quite some
time (the database dump is 2.5 GB), and running the MediaWiki database
update script took about 15 minutes IIRC. So updating daily would result
in too much downtime for a very small gain IMHO.
Also, only a few people have access to the servers in Provo, and they
are already busy enough, so I don't want to put superfluous load on them.
(If someone really has some free minutes - we have enough open tickets
for everybody ;-)
My plan is:
- get the mediawiki_1_27* packages from home:cboltz:infra into the
- get the missing parts into salt
- get a database on the mysql cluster (actually one for each wiki)
- let salt setup the VMs (elasticsearch, Apache+Mediawiki)
- when everything is in place, get the latest database dump and uploaded
files and do a test migration
- fix whatever breaks (hopefully nothing ;-)
- do the real migration some days later (which includes setting the
current wiki to read-only mode before getting the database dump and
Speaking about going productive:
- should the storage for the wiki (especially uploaded images) be inside
the VM or somewhere else?
- what about daily backups? Can I get them "for free" or do I have to do
something for it? (Something like rsnapshot is probably a good idea -
the uploaded files have very few changes.)
- what about daily database dumps/backups?
At the same
time, remember that it is a test instance, so any changes
you do will be lost when I re-import the database dump for whatever
It's it possible to add this as a banner to every page?
Good idea, done.
visitors may wonder why it's en-test.o.o instead of
now. That name change is caused by a funny problem with our SSL
certificate - *.opensuse.org doesn't match something with an
additional dot, and en.test.o.o had such a dot ;-)
"funny" is not the right wording here, as it works as designed... ;-)
Well, it's the first time I hit this problem - I rarely had to work with
wildcard certificates before. So yes, it works as designed, but it still
was a bit surprising to me ;-)
I mean, hey, the certificate says *.o.o, not [^.]*.o.o ;-)
Brauchst Du die sig noch? Ich hab sie nämlich gerade
JA!! *uff* ich hab sie noch!!! :)
[> Christian Boltz und David Haller in suse-linux-faq]
To unsubscribe, e-mail: heroes+unsubscribe(a)opensuse.org
To contact the owner, e-mail: heroes+owner(a)opensuse.org