Hi all
I'm happy to let you know that new hardware has been ordered by Wikimedia
Deutschland and will arrive probably in about two weeks. We will get two new
systems:
* A more powerful web server, to replace hemlock: Sun Fire X4150, 2x Quad-Core
Xeon, 8GB RAM, 2x73GB SAS HDD. The current web server only has two cores.
* Another database server, to be used for S1 (english wikipedia), so S1 and S3
no longer have to share a server: Sun Fire X4250, 2x Quad-Core Xeon, 32GB RAM,
16x146GB SAS RAID.
This should improve performance and give us some head space for growth. Once the
new servers arrive, S3 will be re-imported too, so we will have live data again.
Any ideas for names? To stay with the nightshade theme, how about Jurubeba and
Erubia? Or perhaps we go the "witches' weed" way, with Datura and Mandrake?
Henbane is taken, i think. Amanita sounds nice, too :)
A third server has been ordered, which will also be installed in Amsterdam, but
will not be part of the toolserver cluster. It's a storage server (X4540, 24TB
RAID) that will keep a live backup of all media files.
Cheers,
Daniel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
In the past some users have complained that we don't have a regular maintenance
policy, so it's difficult to plan long tasks around downtime. To solve this,
we will be implementing the following maintenance schedule:
https://wiki.toolserver.org/view/Maintenance_schedule
The main result of this is that there will be one period of downtime per month,
which users will be able to plan for in advance without needing maintenance
notices (since the next maintenance dates can be easily calculated).
This will not eliminate all unscheduled downtime, since there are sometimes
issues that need to be fixed immediately, but we hope it is an improvement over
the current situation.
We are also looking at ways to reduce the impact of maintenance (such as
reboots) in the future.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)
iEYEARECAAYFAkzEfjEACgkQIXd7fCuc5vKtrgCfZDJ+JzwKOwqi1YWpxCK6yrs1
nL8AnRzcNCvrzQS3gq81gtlhmF9+kB86
=S5cF
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Web services (JIRA, FishEye, MediaWiki) are currently offline while we move the
host machine (amaranth) to a different rack. This should take less than an
hour.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)
iEYEARECAAYFAkyrcBQACgkQIXd7fCuc5vK30QCZAWJK/32cfK8MFQpE93aZl7Vi
fjQAoJdRz7b56f54nXJ6W6LP9pYuloZ8
=HT0O
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
There was ~1.5 hours of replication lag on s4 (commons) on all servers,
starting around 1600h UTC, because Wikimedia upgraded the s4 master to MySQL
5.1, and trainwreck (our replication tool) does not understand the 5.1 binlog
format. I have now added support for this format, and replication has
restarted.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)
iEYEARECAAYFAkyrYD4ACgkQIXd7fCuc5vKVdACfVfToeIz7AojchllhyeiQyuUD
x5YAn2spR0SKgUMnXLkCJbojZTc6oIcA
=6l/o
-----END PGP SIGNATURE-----
Am I allowed to publish the list of top 20 contributors to a wiki over
the last 2 weeks? Its kind of like an editcount over a time period (it
just looks at the recentchanges table), but I don't think you'd be
able to deduce an editors lifestyle from it since:
*Most people in the top ten are so obsessive they're editing all the time
*This only gives the current week, so you can't really make
comparisons which is when you can start deducing life styles.
Anyways, so is this allowed, or would i need permission from everyone
on that list before publishing such a list.
--
-bawolff