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
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
following the implementation of the Solaris login server (willow), we are
planning to move the web server, wolfsbane, to this platform. compared to the
previous change on the web server (from Apache to ZWS), we don't expect this to
require as much effort from users. for example, there is no need to change
your htaccess or rewrite rules, because we will be using the same web server
software.
for most tools (e.g. simple CGI or PHP scripts), there will be no need to
change anything. in order of likelihood, the most common problems will be:
* missing modules (for PHP/Perl/Python)
* missing libraries (for C/C++)
* different versions (e.g. PHP 5.3 vs 5.2, Python 2.6 vs 2.5)
* OS differences
if you find missing modules or libraries, please file a request on JIRA to have
these installed. for version differences, normally no changes will be
required; if any are required, they will be documented in the release notes for
the language in question, and should be easy to do. in extreme cases (where
converting to the new version would be very difficult), we may be able to
install old versions of the affected software.
there are unlikely to be many people affected by OS differences; this would
only happen if your tool calls external programs, which is uncommon. if you
encounter a problem of this sort and can't solve it yourself, you can ask for
help on IRC or the mailing list. there are some notes about Linux->Solaris
migration on the TS wiki at <https://wiki.toolserver.org/view/Using_Solaris>.
there will be a one month test / migration period, during which you can test
the web server on willow. to do this, replace "toolserver.org" in your tool's
URL with "willow.toolserver.org", for example:
http://willow.toolserver.org/~jsmith/mytool.php
this will last until Wednesday, 19 August, at which point wolfsbane will be
converted.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkpolUwACgkQIXd7fCuc5vL2EgCgmG45stK/gAuTQS48mSAumkPL
svkAnRV66vax/6j+Mrq5E/1/YsF4ESoq
=lwH6
-----END PGP SIGNATURE-----
Earlier this spring, there was some talk, perhaps within the newly
founded Wikimedia Norway chapter, to set up a common server in
Norway for analysing database dumps and running bot scripts, i.e.
a toolserver with everything except the database replication.
Did this happen? Are there a bunch of such servers around the
world today? Is there a list of such servers? Should we
encourage people to do this, or should we try to concentrate work
(and pool resources) to the (real / German) toolserver?
Concentrating to fewer servers has the advantage that people can
get a single account there, and join each project that is already
there. Distributing over multiple, independent servers has the
advantage of offloading the central server. It might also seem
like an attractive project for a new Wikimedia chapter, since a
server of their own looks like an achievement in itself. But it
is also a waste of resources to maintain separate servers, if
these resources could instead be pooled.
--
Lars Aronsson (lars(a)aronsson.se)
Aronsson Datateknik - http://aronsson.se
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
at some point either today or over the weekend i will be reimporting s1. the
server holding s1 will be reinstalled at the same time. there will be a few
hours of downtime while the new database is imported, then some replication
lag.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkpzDysACgkQIXd7fCuc5vLBhgCeL+W3m6bdLYJKU4pxmL8X6Tax
nqIAniBi5hCTamr/v933mEAy0MLhNxLC
=UOp1
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
in the past we provided the login.toolserver.org alias, which pointed at the
login server. we have decided to deprecate this alias, because:
1. it didn't really work, since changing login server requires much more work
than just changing an alias.
2. now we have two login servers, it's not clear which 'login' should refer to.
to avoid breaking anything, we will leave the alias in place, but i suggest
updating any uses of it to refer to a particular login server (nightshade or
willow).
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkpldMIACgkQIXd7fCuc5vJKFwCfRiFThpcVMWt/9Hbk8XU7nBLN
+VYAniFNrOE6vkHV/v6QAhBBYfNJimDC
=bi5p
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
i've just upgraded FishEye (the SVN repository viewer) to version 2.0. FishEye
is now bundled with Crucible, Atlassian's code review tool. if you have a
multi-maintainer project, this might be interesting to you.
if you'd like to use this, the Crucible user's guide is at
<http://confluence.atlassian.com/display/CRUCIBLE/Crucible+User's+Guide>
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkpzJDAACgkQIXd7fCuc5vKQJQCeJPOucLQQtbvOI3ZA7x9a/en2
zkAAoLjjpCiHnFvpOf4VjA9cewctnOWZ
=e2eP
-----END PGP SIGNATURE-----
Hello,
I'm looking for any kind of tool which would take the XML dump (most probably the pages-meta-current.xml.bz2, at least the pages-articles.xml.bz2) and would return the list of page titles (or alternatively/configurably page ids) of pages containing given string.
Does anybody have such (kind of) tool and is willing to share? Both command line or webpage interface are OK.
Thank you.
Danny B.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Happy SysAdminDay to all Toolserver's admins! :-D
Thank you for your hard work.
http://www.sysadminday.com/
"I'm Outlaw Pete,
I'm Outlaw Pete,
Can you hear me?"
Pietrodn
powerpdn(a)gmail.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAkpzPX8ACgkQ36hWg9C8ELH3xQCgrqpGJjD2Q58yIQjyJYg3z7u0
xPoAn12e7K/tG0mVlVq4O/uVU9EC5uQE
=8ghW
-----END PGP SIGNATURE-----