spamassassin-sysadmins mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin A. McGrail" <>
Subject Onboarding, Documentation, etc.
Date Mon, 08 May 2017 22:13:15 GMT
Dave and Bryan, below is my latest attempt at the how to information for 

Can one of you please take on incorporating this into the wiki?

Apache SpamAssassin SysAdmin How-To

NOTE: This was written in April of 2017 to help modernize our system records

- Other records: See - This document 
will likely be used to replace that page.

- Wiki Access:

Write access to the wiki is to anyone who has created a login name on 
the wiki
whose name has been added to the page

Write access to that page is to anyone whose wiki login name has been 
added to

- Members of SA SysAdmins (SASA):
Dave Jones -
Kevin A. McGrail - 703-798-0171 -
Bryan Vest -

- Who's in Charge?
The PMC.  There is no leadership hierarchy in the SpamAssassin SysAdmins.

NOTE: As with any ASF role, if you follow The Apache Way, you should 
feel empowered to Just Do It (TM Nike)

For a SysAdmin, your solution works (Merit), it's well documented (Open) 
and supports the project (Community), you're good to go though as a 
SysAdmin you need to realize we have control over private data.  All 
SASA members have been asked to follow the LISA Code of Ethics.

Tenants we Follow:
   - The Apache Way, Shane Curcuru's post on this are a good point:
   - LISA/Sage Code of Ethics,

Important Resources:

   The ASF Infrastructure (Infra) Jira: - Sign up at Jira 
isn't single sign on enabled.

   SpamAssassin Bugzilla:

Short-hand Notes:
   There are a lot of acronyms, even those that might be basic that will 
be defined here if we find there is confusion to make it easier to bring 
new sysadmin's onboard to make many hands make light work.

     Apache Software Foundation (ASF)
     Bugzilla (BZ)
     Apache SpamAssassin (SA)
     PMC (Project Management Committee)
     SVN (SubVersioN)

Mailing Lists:
   - There is a dedicated SASA Mailing list  Additionally, our machines largely 
support the Rule QA process so should be 
subscribed to.

   - There are legacy shared credentials.  These must be encrypted and 
stored in SVN.

- To sudo to root, you need to use OPIE - See

DNS for
- The server creates DNS entries on the fly so we do not use the ASF 
infrastructure for DNS.  We have a hidden master that pushes to 
Hyperreal and Sonic
   Contact for HyperReal is Brian Behlendorf
   Contact for Sonic is

The information located here: is the current
configuration information you will need.

- Project Machines

This is a short description of the machines involved including those 
that USED to exist and why.

- - shows this was 
likely a solaris box that I had access to when zones died and I had to 
recover data.
- - DIED - was replaced with spamassassin-vm
- - deprecated by Infra
- - deprecated by Infra

- - Donated by Sonic
- - Ubuntu box to replace spamassassin-vm and zones2

- Other Aliases: buildbot, ruleqa (there might be more).

Also, this is an ASF box for all committers:

- aka People - This used to handle various build and 
devel related tasks. for ssh (It appears that 
minotaur is not the proper server anymore.  I used per 
some links that Sidney sent.  ( and 
resolve to the same IP.)

- Backups:

There are no backups of these machines save what is stored in SVN or 
that KAM has made.

Specifically, what backups does KAM have as of 2017/05/08:

   - - N/A
   - aka colo - Backup on KAM's Crashplan
   - (NOTE: Aka People) - N/A
   - - Backup on KAM's Crashplan
   - - Backup on KAM's Crashplan - Mar 15, 
2017 - There is also a backup on sa-vm1 in /x1.
   - - Backup on KAM's Crashplan from 
Approximately Jun 2015 last backup.  Also have an Rsync copy from June 
3, 2015 on PCCC TalonJR machine - And there is also a copy on sa-vm1 in /x1

- Ubuntu?

Ubuntu is the ASF Infrastructures OS of choice.  Supporting others is 
not an option at this time.

- How to get access to each machine: (current as of 4/28/17)
   - Open a Jira ticket with the availid of the person(s) you want to 
have access. Note if they need sudo access or not.
   - User self maintains their ssh-key at
   - NOTE: if sudo access was requested, run and sets up 'ortpasswd'

- Why all the boxes?

The resources for Masscheck can be very intensive on CPU, Ram and disk 
I/O intensive.  Over the years, many boxes have been consolidated, 
donated, lost, replaced, moved under ASF Infrastructure or just fell 
over and sank into the swamp.

- Some boxes are just names for other boxes Sonic has scripts set up to archive 
collected spam to that server.

KAM Goals for SysAdmin:

- For KAM, Apache SpamAssassin is a framework for writing goals. I 
deliver goals to prove the code works but I don't view that the project 
has to provide rules.  Others may disagree but I don't see the value in 
masscheck, ruleqa, etc. when there is not enough people using the data.

- Once you have an account on Minotaur/Home/People, goto and make a duplicate for you.  NOTE: This is 
documented SOMEWHERE but no idea where.

GOAL: Get it so I have your PGP key and put the signature for your PGP 
key into

- You need access to for 
sysadmin, dns and site.
- In the ASF, we use http for read-only access to a repo and https for 
read-write.  So if you are trying to checkout and modify a repo, make 
sure you are using https://

Encrypted SVN:
- If you can, document things in the Wiki at  If something is 
sensitive, encrypt it and store it on the repo and 
reference it on the Wiki.

The systems use One Password In Everything (OPIE) to elevate your access 
via sudo.  Some resources: 

How to Onboard someone as a SysAdmin:

- A PMC Member nominates a new SASA member as a committer since we store 
items in SVN for configs
NOTE: If they later produce code, they should request that permission 
from the PMC.

- If the vote is successful, they then follow all the normal committer 
guidelines to get them an Apache ID including an appropriate committer 

- Once they have an Apache ID, they should:

   - SASA Member signs up for an Infra Jira account at!default.jspa?
   - SASA Member adds an SSH public key to
   - Add your PGP public key.
   - Create an account on our Wiki
   - Email
   - Email and ask for karma to access 
sa-vm1 with sudo access
   - Email and ask for your account to 
be added to and
   - Start looking at under infrastruction

- Someone with Karma needs to:
   - Approve request to sysadmins mailing list
   - Add them to ContributorsGroup and AdminGroup on Wikki
   - Open a JIRA ticket at similar to INFRA-14045 to 
get them access to our box

Kevin A. McGrail
Asst. Treasurer, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project	

View raw message