Revision [731]
This is an old revision of AuditingDiscussions made by JulianDemarchi on 2007-08-02 13:11:22.
suggested Sequential Task List
- manually add Chris to the list of hosts
- carefully review existing configs for monitoring and alerting
- avo added the 3 monitors and modified hostgroups; all else looks good.
- devise scheme for rsyncing configs, histories, etc.
- prepare downloadable tarball and instructions for next host
Ideas to be discussed
- Criteria for setting up a Monitoring Station
- Required MTA
- Pre-requisites (apache, ssh, etc)
- Pre-requisites (apache, ssh, etc)
- How to inform the audit team of a new Monitoring Station
- Email template that should be filled out when server established.
EXAMPLE
SERVER IP:
SERVER LOCATION (City, country):
SERVER ADMIN:
ADMINS EMAIL:
Upon submission of this, the Audit team will audit the new Monitoring Station, and when approved, a hostname will be given with the .glue tld.
- Naming convention. My thinking was this, bneau.opennic.glue, pausa.opennic.glue.
So the way this would work is, take the first 3 values of the City (Brisabane = BNE), then the country code (Australia = AU).
- Brought up on IRC by avo, we would like to use a subversion system to keep revisions of the config files. Any ideas, recommendations? Who has this experience?
EXAMPLE
SERVER IP:
SERVER LOCATION (City, country):
SERVER ADMIN:
ADMINS EMAIL:
Upon submission of this, the Audit team will audit the new Monitoring Station, and when approved, a hostname will be given with the .glue tld.
- Naming convention. My thinking was this, bneau.opennic.glue, pausa.opennic.glue.
So the way this would work is, take the first 3 values of the City (Brisabane = BNE), then the country code (Australia = AU).
- Brought up on IRC by avo, we would like to use a subversion system to keep revisions of the config files. Any ideas, recommendations? Who has this experience?
