Revision [736]
This is an old revision of AuditingDiscussions made by AvoYager on 2007-08-03 01:07:05.
suggested Sequential Task List
- manually add Chris to the list of hosts
- carefully review existing configs for monitoring and alerting
- 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. for consistency with Hostmastering, .... mon1.pp.cc.opennic.glue where pp is province/state and cc is country
- We would like to consider/test a 'subversion (SVN)' 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. for consistency with Hostmastering, .... mon1.pp.cc.opennic.glue where pp is province/state and cc is country
- We would like to consider/test a 'subversion (SVN)' system to keep revisions of the config files. Any ideas, recommendations? Who has this experience?
