Looking at this second email made me realize I never saw a request for
Bryan to have access to the machine. Sorry Bryan, I think there are a
few steps being skipped.
My LONG email a few days ago* had the onboard process
* I am hoping one of you two will integrate this into the wiki so that
it has another pair of eyes on it.
Repeating the relevant item below so Bryan can test out the process and
we can identify missing steps, please!
Regards,
KAM
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
license: https://www.apache.org/dev/new-committers-guide.html
- Once they have an Apache ID, they should:
- SASA Member signs up for an Infra Jira account at
https://issues.apache.org/jira/secure/Signup!default.jspa?
- SASA Member adds an SSH public key to id.apache.org
- Add your PGP public key. http://people.apache.org/~kmcgrail/
- Create an account on our Wiki
- Email sysadmins-subscr...@spamassassin.apache.org
- Email sysadmins@spamassassin.apache.org and ask for karma to access
sa-vm1 with sudo access
- Email sysadmins@spamassassin.apache.org and ask for your account to
be added to https://wiki.apache.org/spamassassin/ContributorsGroup and
https://wiki.apache.org/spamassassin/AdminGroup
- Start looking at
https://wiki.apache.org/spamassassin/DevelopmentStuff 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 issues.apache.org similar to INFRA-14045 to
get them access to our box
On 5/12/2017 6:59 AM, Bryan Vest wrote:
Having a problem getting setup. I went through the process can I can sftp
to home.apache.org but sa-vm1.apache.org gives me LDAP authorisation check
failed.
--Bryan Vest
<http://sa-vm1.apache.org>
On Wed, May 10, 2017 at 11:08 AM, Dave Jones <da...@apache.org> wrote:
Brian,
I am still working on getting /usr/local/spamassassin setup properly as
our primary directory with all of the components under it. Let me get a
little further on this over the next couple of days and then I think we
will be at a place where 2 sysadmins can "be in the kitchen" without having
"too many cooks in the kitchen."
At that point we can split up the components -- automc (auto masscheck),
bbmass (buildbot mass check), corpus, etc. -- and work on these in parallel.
In the meantime:
1. Setup your apache.org email address and the forwarding to your
gmail.com address at https://id.apache.org.
2. Setup your SSH key, PGP key, etc. in https://id.apache.org.
3. Setup your OPIE password so you can SSH into sa-vm1.apache.org:
https://reference.apache.org/committer/opie
4. Make sure you have the ability to "sudo su -" to become root on
sa-vm1.apache.org by using OPIE. Here is the OPIE client I am using:
https://reference.apache.org/committer/otp-md5
Dave
On 05/08/2017 10:15 AM, Kevin A. McGrail wrote:
On 5/7/2017 3:43 PM, Dave Jones wrote:
Do you know what the long-term plan is for the /x1 mount? Was it setup
as a temporary place to restore old backups?
I am trying to organize everything under /usr/local/spamassassin and the
root FS doesn't have enough space. If the plan was to eventually unmount
and give back the /x1 storage, we can do that. If we are going able to keep
it, then I would like to remount it under /usr/local/spamassassin if that
is OK.
root@sa-vm1:/usr/local/spamassassin# df -H
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 34G 8.9G 24G 28% /
/dev/sdb1 1.2T 426G 678G 39% /x1
If we need the space, use it and remount how you would like!
Regards,
KAM
--
Kevin A. McGrail
Asst. Treasurer, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
