-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
hello,
as you may have noticed, there is a shortage of spare time for the current toolserver admins, which means it takes a long time for requests to get done. i would like to add an additional admin (or several) to help the situation.
if you're interested, please drop me a mail. ideally, candidates will:
+ have been a member of a Wikimedia project for a long time, with some level of additional access (e.g. checkuser, OTRS, ...)
+ have an advanced knowledge of Unix (at least several years experience)
+ have experience with Linux or Solaris system administration in a production environment (another Unix would be okay if you're willing to learn something new)
+ have experience with MySQL database administration
+ be available on the toolserver IRC channel to help users (this isn't a requirement, but it would be helpful)
+ experience with these products/technologies would be an advantage: Apache; JIRA; PostgreSQL; Sun Web Server; Sun Directory Server / LDAP; GlassFish; Kerberos; StorageTek SAM-QFS; Veritas.
the job of a toolserver admin is to:
+ process user requests in the TS and SUPPORT projects in JIRA + create new user accounts + make sure the toolserver systems are working acceptably (for example, resolving performance problems with the system or broken tools) + participate in discussions about the future of the toolserver (for example, what hardware to buy, what additional services to offer, etc.)
please, no CVs (but a short description of your background/experience is fine). anyone who is accepted will be required to provide the Wikimedia office with proof of their real-life identity; please don't apply if you're not comfortable with that.
as this is a volunteer position, the amount of time you put into it is entirely up to you; but at a minimum, you should be willing to spend at least a couple of hours each week on the toolserver.
- river.
Heya,
I could give a hand.
River Tarnell wrote:
[...] ideally, candidates will:
- have been a member of a Wikimedia project for a long time, with some level of additional access (e.g. checkuser, OTRS, ...)
I'm an admin on en.wp, a clerk of the en.wp Arbitration Commitee, a member of the BAG, and I am an OTRS agent. I also obviously have way too much free time on my hands. :-)
- have an advanced knowledge of Unix (at least several years experience)
- have experience with Linux or Solaris system administration in a production environment (another Unix would be okay if you're willing to learn something new)
- have experience with MySQL database administration
I've been a sysadmin for a bit over 20 years, most of past 10 with Linux.
- be available on the toolserver IRC channel to help users (this isn't a requirement, but it would be helpful)
I spend way too much time on IRC already, might as well be productive. :-)
- experience with these products/technologies would be an advantage: Apache; JIRA; PostgreSQL; Sun Web Server; Sun Directory Server / LDAP; GlassFish; Kerberos; StorageTek SAM-QFS; Veritas.
I grok Apache, Jira, Pg, and Krb5. I'm familiar with Veritas. The rest I mostly know /of/.
as this is a volunteer position, the amount of time you put into it is entirely up to you; but at a minimum, you should be willing to spend at least a couple of hours each week on the toolserver.
I've already got a number of other tasks I do around the wmf, but I can certainly do a couple of hours of direct support work as well as idle in the ts channel to give a hand whenever I'm on IRC.
-- [[User:Coren]] Marc A. Pelletier
_______________________________________________ Toolserver-l mailing list Toolserver-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Do you have an idea, Mark, on how to improve the replication process in terms of hw or sw, especially for s3 replication?
Mashiah Davidson aka mashiah
2008/3/7, Marc A. Pelletier marc@uberbox.org:
Heya,
I could give a hand.
River Tarnell wrote:
[...] ideally, candidates
will:
- have been a member of a Wikimedia project for a long time, with some level of additional access (e.g. checkuser, OTRS, ...)
I'm an admin on en.wp, a clerk of the en.wp Arbitration Commitee, a member of the BAG, and I am an OTRS agent. I also obviously have way too much free time on my hands. :-)
- have an advanced knowledge of Unix (at least several years experience)
- have experience with Linux or Solaris system administration in a production environment (another Unix would be okay if you're willing to learn something new)
- have experience with MySQL database administration
I've been a sysadmin for a bit over 20 years, most of past 10 with Linux.
- be available on the toolserver IRC channel to help users (this isn't a requirement, but it would be helpful)
I spend way too much time on IRC already, might as well be productive. :-)
- experience with these products/technologies would be an advantage: Apache; JIRA; PostgreSQL; Sun Web Server; Sun Directory Server /
LDAP;
GlassFish; Kerberos; StorageTek SAM-QFS; Veritas.
I grok Apache, Jira, Pg, and Krb5. I'm familiar with Veritas. The rest I mostly know /of/.
as this is a volunteer position, the amount of time you put into it is entirely up to you; but at a minimum, you should be willing to spend at least a couple of hours each week on the toolserver.
I've already got a number of other tasks I do around the wmf, but I can certainly do a couple of hours of direct support work as well as idle in the ts channel to give a hand whenever I'm on IRC.
-- [[User:Coren]] Marc A. Pelletier
Toolserver-l mailing list Toolserver-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Toolserver-l mailing list Toolserver-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Mashiah Davidson wrote:
Do you have an idea, Mark, on how to improve the replication process in terms of hw or sw, especially for s3 replication?
I'd need to look into how it's currently being done in the first place; this isn't an aspect of the ts that I've fiddled with to date. Gimme a few days to look around and I'll see if I can think of something. :-)
-- Marc
On Fri, Mar 7, 2008 at 11:53 PM, Mashiah Davidson mashiah.davidson@gmail.com wrote:
Do you have an idea, Mark, on how to improve the replication process in terms of hw or sw, especially for s3 replication?
Mashiah Davidson aka mashiah
I'm not sure what answer you expect from Marc. More hardware is of course going to help but that is outside the range of the toolserver roots, as their primary responsibility is the software. As software River's trainwreck http://svn.wikimedia.org/viewvc/mediawiki/trunk/tools/trainwreck/ is used.
Bryan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Mashiah Davidson wrote:
Do you have an idea, Mark, on how to improve the replication process in
terms of hw or sw, especially for s3 replication? Another point is that currently the replication problems are mainly due to problems caused by the main Wikimedia servers. Replication usually works fine until something happens on the main servers (such as masters\slaves being switched or binlogs deleted) then everything breaks. Such problems are difficult to combat, presumably what is needed is better communication between the toolserver and main server teams -- outside the realms of hardware and software.
MinuteElectron.
Of course, I do not mean current s3 replication problems. The issue is that the replag value was too unstable during last period of time after new array has been plugged in.
The reason I'm asking is that according to original River's post roots are participating decision making for hw upgrades. So, the point here is do we really need to split s1 and s3 on different servers or there is an ability to speedup yarrow for better replication.
2008/3/8, MinuteElectron minuteelectron@googlemail.com:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Mashiah Davidson wrote:
Do you have an idea, Mark, on how to improve the replication process in
terms of hw or sw, especially for s3 replication?
Another point is that currently the replication problems are mainly due to problems caused by the main Wikimedia servers. Replication usually works fine until something happens on the main servers (such as masters\slaves being switched or binlogs deleted) then everything breaks. Such problems are difficult to combat, presumably what is needed is better communication between the toolserver and main server teams -- outside the realms of hardware and software.
MinuteElectron. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkfSYmkACgkQkJvUlhoE3wRrigCcDd8nyZDPUHnvCGKkekFFs+4d DhEAoJGv3gDoKQAwlTNB3rnjaEKwyNoT =jn+6 -----END PGP SIGNATURE-----
Toolserver-l mailing list Toolserver-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/toolserver-l
toolserver-l@lists.wikimedia.org