[jira] [Created] (INFRA-6379) Help to get new monitoring..a.o setup in a standard asf way.

["jan iversen (JIRA)" <ji...@apache.org>]

jan iversen created INFRA-6379:
----------------------------------

             Summary: Help to get new monitoring..a.o setup in a standard asf way.
                 Key: INFRA-6379
                 URL: https://issues.apache.org/jira/browse/INFRA-6379
             Project: Infrastructure
          Issue Type: Wish
      Security Level: public (Regular issues)
          Components: Website
         Environment: ubuntu 12.04
            Reporter: jan iversen
            Priority: Critical


We have got a new vm at bytemark, to be used as a replacement for the existing monitoring.a.o. IP addr: 213.138.103.48, root passwd available from me (currently not distributed for security reasons)

the vm should be setup as a "standard" asf ubuntu vm. I have learned that we do not support vm's at bytemark (off colo) with ldap/puppet/f2b/sshd, but considering it is a key component in our setup, it might be an idea to at least half support this vm. 

I could use some help with:
1) Which users should I activate locally (current monitoring.a.o have plenty) ?
2) What are our procedures for ssh keys, and initial passwd on non ldap-vms ?
3) Is there any special procedures on id/gid I must adhere to ?
4) Do we want f2b to run, monitoring ssh and www (status.a.o) ?
5) Should I take any special measures when copying infrabot, considering especially the karma files ?
6) can I define a new dnsname like e.g. monitoring-vm2.a.o ?

Sorry for the many questions, but I am still learning and I prefer to ask instead of making too many mistakes.

rgds
jan I

Ps. remark, this task should be solved before circonus goes live and nagios RIP.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira