You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Preflight mass-checks buildbot

The preflight mass-check buildbot is up and running at http://buildbot.spamassassin.org/preflight/ .

Every time something is checked into SVN, this will wake up and immediately start running mass-checks using that latest code and rules.

The corpus it mass-checks is split in a certain way so that results will be available very quickly – typically in under 10 minutes – with increasing quantities of results becoming available as time elapses.

Progress of the mass-checks are visible on [http://buildbot.spamassassin.org/preflight/ the Buildbot 'waterfall']; as they complete, their results become visible on the RuleQaApp.

The preflight mass-check corpus

This corpus is built from a selection of mail rsync'd up from various people; it's then "smoothed out" into several subsets. These use differing amounts of mail, starting with a small set of mail in the "mc-fast" chunk, and gradually increasing until we get to the largest block in "mc-slower". This division means that early "fast" results can arrive quickly, with less to scan, and as time goes on, more and more of the "slower" slaves complete their mass-checks and upload the results.

What happens during the preflight buildbot process

[http://buildbot.spamassassin.org/preflight/ As you can see], there are four steps performed by each buildbot slave, as follows:

Update: This performs an 'svn update' to load the latest code.

Configure: runs 'perl Makefile.PL' and 'make' to compile the rules.

Test: the mass-check takes place here. This is usually the time-consuming part.

Configure; a final summarisation step; first off, a 'FAST FREQS REPORT' is output, the HitFrequencies from the mass-check. Next, the logs from the mass-check are copied to a safe location, and the 'corpus-hourly' script run to generate various reports from them for the RuleQaApp. The URL for viewing the results in the RuleQaApp is printed prominently.

Administrivia: how the corpus is laid out

The filesystem layout of the corpora rsynced up to the server, is like this:

/home/bbmass/rawcor/WHO/TYPE/FOLDER

"WHO" is the person who submitted it via rsync, e.g. "doc", "jm", "zmi".

Under that, we have "TYPE", which is either "ham" or "spam".

Under that, "FOLDER", which is whatever the person feels is appropriate. For example, I use date-stamped dirs here. It is also possible to use mboxes, as long as they are files and their filename ends in ".mbox".

Then, the script 'populate_cor' is run from cron periodically to rebuild the mass-checkable corpus from this. It attempts to 'smooth out' the multiple corpora into several new corpora, named "mc-fast", "mc-med", "mc-slow", "mc-slower", matching the buildbot slave names at http://buildbot.spamassassin.org/preflight/ .

It does this by:

  • extracting mboxes into mail directories of one file per message
  • creating symbolic links to those files in new corpus directories
  • for each new corpus dir, creating a 'targets' file for mass-check listing what files it's created for that corpus.

It attempts to use one person's corpus per each output corpus, but seeing as there's usually a glut of spam and a limited quantity of ham, it's not always anywhere near a one-to-one correlation. All the same, by looking at [http://buildbot.spamassassin.org/bbmass/corpus_makeup.txt the logs from the build process], you can see where the correlations lie.

The output looks like this on-disk:

/home/bbmass/tmpfs/cor/CORPUSNAME/TYPE/LINKNAME

Each "CORPUSNAME" directory corresponds to one of the slave names, "mc-fast", "mc-med", etc. Under that, we have "TYPE", which is either "ham" or "spam". Next, "LINKNAME". This is a readable filename for the symbolic link, which gives the reader an idea of where the message came from in the source corpora.

Uploading corpora

This is done via rsync.

Give somebody on the PMC a shout, since they have privileges to create an rsync area for you to upload stuff to. (If you're on the PMC, just SSH in and copy over a tarball yourself! or create yourself an rsync account using a random password.)

Once they've done this, they'll send you the username and password; you can then sync your files like so:

  export RSYNC_PASSWORD=$YOURPASS
  rsync -vr /path/to/your/files \
      rsync://$YOURUSER@rsync.spamassassin.org/mailcorpus_$YOURUSER

(where $YOURPASS, $YOURUSER, $YOU are whatever the PMC guy mailed to you.)

It's important that you have 2 dirs in the /path/to/your/files directory,
ham and spam. Any files ending in .mbox inside those dirs will be treated as UNIX mbox-format files; any other files will be treated as individual messages (one message per file).

Administrivia

Some stuff for PMC people hacking on this...

Admin: Creating a new rsync area for someone to upload corpora

sudo vi /etc/rsyncd.conf

add something like this to the end, changing "CORPUSUSER" to the username you want to give out:

[mailcorpus_CORPUSUSER]
        path = /home/bbmass/rawcor/CORPUSUSER
        read only = false
        auth users = CORPUSUSER
        secrets file = /home/corpus-rsync/secrets

CORPUSUSER="[username you want to give out]"
cd /home/bbmass/rawcor/
mkdir $CORPUSUSER
chmod 1777 $CORPUSUSER

Then create a random password string, and add a line to /home/corpus-rsync/secrets with $CORPUSUSER and that password.

Finally, let the submitter know their new username and password.

Admin: Creating a new buildbot slave to perform mass-checks

I don't see us needing to do this anytime soon, but it's worth recording. Here's the commands that do this, run in the zone.

PASSWORD=[randompassword]
NAME=mc-new

sudo mkdir -p /home/bbmass/slaves/$NAME
sudo chown bbmass /home/bbmass/slaves/$NAME

cd /home/bbmass/slaves/$NAME
sudo su bbmass -c \
         "mktap buildbot slave --basedir /home/bbmass/slaves/$NAME \
         --master buildbot.spamassassin.org:9988 --name $NAME \
         --passwd $PASSWORD --usepty=0"

echo $PASSWORD > $HOME/pwd
sudo mv $HOME/pwd /home/buildbot/pwds/$NAME
sudo chown buildbot /home/buildbot/pwds/$NAME
sudo chmod 600 /home/buildbot/pwds/$NAME

sudo vi /home/buildbot/bots/bbmass/master.cfg

        [search for mc-fast and add new lines/entries for $NAME]

sudo vi /etc/init.d/buildbot 

        [search for mc-fast and add new lines/entries for $NAME]

(history: this was planned at RulesProjBuildBot)

  • No labels