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

Compare with Current View Page History

« Previous Version 5 Next »

Infrastructure Notes 2017+

This page was created in April of 2017 to help modernize our system records

This document will likely replace https://wiki.apache.org/spamassassin/DevelopmentStuff

Current Members

As of May 2017:
*Dave Jones - davej@apache.org
*Kevin A. McGrail - 703-798-0171 - kmcgrail@apache.org
*Bryan Vest - bvest@apache.org

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: http://theapacheway.com/
*LISA/Sage Code of Ethics, https://www.pccc.com/base.cgim?template=sage_code_of_ethics

Onboarding SA SysAdmins

=== Jira ==
The ASF Infrastructure (Infra) Jira: https://issues.apache.org/jira/secure/Dashboard.jspa Sign up at Jira isn't single sign on enabled.

SpamAssassin Bugzilla: https://bz.apache.org/SpamAssassin/

Wiki

*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 https://wiki.apache.org/spamassassin/ContributorsGroup
*Write access to that page is to anyone whose wiki login name has been added to https://wiki.apache.org/spamassassin/AdminGroup

2017+ Standards

*Apache.org standard of Ubuntu 16.04 LTS
*Cron entries should be in new standard locations /etc/cron.d, /etc/cron.daily, etc. and avoid using user's crontab
*Custom scripts should reside in /usr/local/bin if they are not direcly related to SpamAssassin processing that should be in /usr/local/spamassassin
*Symlink scripts from /usr/local/bin to /etc/cron.d, /etc/cron.daily, or /etc/cron.weekly. This provides easy discovery and future management by others on the sysadmins team.
*Scripts and cron entries should mail output to the sysadmins mailing list

Servers

Hostname

Function

Software

Configs/Location

Resource/URL

sa-vm1.apache.org

DNS Hidden Master

PowerDNS

/etc/powerdns/pdns.d/pdns.local.conf

spamassassin.org

 

NightlyMasscheck

Scripts

 

 

  • No labels