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
>> hi all
>>
>> many of our tools uses messages from betawiki because they are
>> translated in many languages.
>> But this messages must be synchronized and I think it's not very
>> economically if every user/tool do that self. Because of that I
>> propose
>> to create one database for all users which will be sync periodically.
>
>A database with one table per user? Sounds good.
>
>> What do you think? Are any other users interested for such a db?
>
>I would be interested.
>
>> Greetings,
>> Luxo
>
>Pietrodn
>powerpdn(a)gmail.com
I thought not one table per user, but rather one table for all messages.
On betawiki are a lot messages e.g.
http://translatewiki.net/wiki/MediaWiki:Abusefilter-revert-title/en.
So I would make a table something like
+
----------+------------------------+-----------------------------------------------------+
| LANG | MESSAGE |
TEXT |
+
----------+------------------------+-----------------------------------------------------+
| en | Abusefilter-revert-title | Revert all changes by
filter $1 |
+
----------+------------------------+-----------------------------------------------------+
| de | Abusefilter-revert-title | Alle Änderungen durch
Filter $1 rückgängig machen |
+
----------+------------------------+-----------------------------------------------------+
| fr | Abusefilter-revert-title | Révoquer toutes les
modifications par le filtre $1 |
+
----------+------------------------+-----------------------------------------------------+
the messages which will be synced should be one a list which every
ts-user can edit, so that it's easy for every user to add the messages
he requires.
--Luxo
Hello,
perhaps this would be a good moment to transfer Geohack to a regular
mediawiki-extension on the main servers.
I hear this was also the plan of brion vibber before he go.
Who we need to ask now for this?
I don't know why but I have no access to geohack-scripts anymore.
So I can't do anything.
Greetings Kolossos
river wrote:
> Hi,
>
> As announced two months ago, we are planning to EOL the stable server in
> favour of multi-maintainer projects on the normal Toolserver. The following
> projects are still running on the stable server:
>
> * geohack
> * wma
> * delinker
>
> We intend to repurpose the hardware currently used for the stable server to
> provide redundancy database replication, but this can't happen until all
> projects have migrated off the stable server.
>
> - river.
>
>
>
Hello all,
while I was under the shower today, I got the following weird idea: We have
several interwiki-bots on the toolserver, that do more or less the same, but
by different ts-users. Some bots run old versions of the software, some stop
for unknown reason and were never restarted (properly because the ts-user
left) and some just work how they should. Often I read in the wikimedia-
projects (most time in my homewiki dewp of corse), that there are problems
with a bot (because it add a wrong interwiki-link again) and the users don't
know how to contact the bot-owner and what they should do.
So my idea: Amalgamate all interwiki-bots (in the same programming-language of
corse) into 1 multi-maintainer-project. The advantages would be, that we would
use lesser resources, the bot-maintainer could work together, they could use a
database together, it would be easier for wikimedia-project-user to contact us
(in jira for example or with a mailinglist), if something is wrong, it would
be easier to contact the bot-software-maintainer and so on.
Any thoughts about that? Good idea or a "you had too much hot water in the
shower"-idea?
Sincerly,
DaB.
--
wp-blog.de
Hello all,
for an important kernel-update, nightshade will reboot around 23 o'clock UTC.
The downtime should be short, but all running programms on nightshade will of
corse stop. So please make sure that they restart after the reboot or move
them temporary to willow (caution. solaris! ;)).
I can give no link to a jira-ticket, because jira is down since yesterday. I
will send a email after the reboot to inform you all.
Sincerly,
DaB.
--
wp-blog.de
Hi,
Over the next couple of weeks we will be making some changes to the way that
wiki databases work on the Toolserver.
Currently, each cluster (s1..s6) has only a single Toolserver slave. (For
example, s1 is on yarrow and no other server). We will be adding an
additional server to each cluster, so each cluster has two servers. The
existing server will be designated the 'standard' server, and the new server
will be a 'fast' server.
The standard server can be used as it is now, with no changes. The 'fast'
server will be the same as the standard server, with two exceptions:
* creating user databases will not be allowed
* queries running longer than 60 seconds will be automatically killed
The intent here is that by preventing long running queries on the fast
server, replication lag will be much less likely, and queries that need the
most up-to-date data, which are usually also fast queries, will be able to
use the fast server.
If either server fails, its queries will be redirected to the other server.
So, if the s1 fast server fails, all fast queries will go to the standard
server. If the standard server fails, all queries will go to the fast
server.
If you want your queries to run on the standard server, you do not need to
do anything. The current server for each cluster, where the existing
'sql-sX' aliases point, will become the standard server.
if you want your queries to run on the fast server, you should connect to
'sql-sX-fast' instead of 'sql-sX'. You cannot connect to the fast server
using DNS aliases; you must use the sql-sX aliases.
Currently, no fast servers are available, so all sql-sX-fast aliases point
to the standard server. The first cluster to get a fast server will be s1,
which I hope will happen next week. One cluster will not get its fast
server until all projects have finished migrating from the stable server, as
the stable server host will be converted into the 3rd fast server.
- river.
Hi,
Our trained monkeys have been working non-stop for the last week on a new
piece of software for the Toolserver: the jobserver. This software is now
ready for testing.
The jobserver is an alternative to cron/phoenix for starting long-running
jobs. Instead of having to invoke phoenix regularly in cron, you can
instead add your job to the jobserver, and it will be (re)started
automatically, even if the server crashes or reboots.
This is still very much pre-alpha, but I've installed the jobserver on
willow for testing. You can read more about the jobserver and how to use it
on the wiki:
<https://wiki.toolserver.org/view/Jobserver>
Please report any problems on the wiki page. While you should feel free to
use and test the jobserver as much as you want, do remember that it may
still have serious problems that result in your jobs not running when you
expect, or maybe worse.
In the future the jobserver will have additional functionality, including
scheduled jobs (to replace cron with a single integrated solution). If you
have any other feature requests, you should list them on the wiki.
- river.
Hi,
Tonight I will upgrade the web server software on wolfsbane. Total downtime
for the upgrade should be around 5 minutes. There will be no user-visible
changes.
This issue is being tracked in JIRA as MNT-177.
- river.
Hello all,
on saturday night, I will install all non-critical updates of debian-packages
on nightshade. This time, twisted will be updated too and it will have a major
release jump from 8 to 9.
If you use twisted, please read the changelog (I attached a copy to the
maintaince-ticket) and check if there could be problems. If you found a
problem, please leave me a notice and I will delay the update until you can
fix the problem with your code.
The update will also affect some other packages (for details, see maintaince-
ticket), but there should be no problems AFAIS.
The maintaince-ticket is at https://jira.toolserver.org/browse/MNT-174.
Sincerly,
DaB.
--
wp-blog.de
Hi,
The above two wikis will be dropped from the cluster, as they are obsolete.
They have already been removed from the toolserver.wiki table.
- river.