====== Monitoring the Infrastructure  ======
====== Project Member(s) ======

  * Chase (clee231)

====== Purpose ======

The main purpose is about the same, but the project has been redefined based on what was learned after the first attempt at making a Nagios server on a Raspberry Pi B+ host. The adjusted parameters include using one of the new Raspberry Pi 2 B boards to setup a Linux host with a Nagios fork called Icinga2. The host is to remove problems caused by the limited support for the ARMv6 SoC on the Pi B+, the Pi 2 uses ARMv7 which is a more widely supported architecture. The change is software is being made due to some pains and annoyances discovered working with Nagios and we hope that Icinga2's claims of addressing those issue ring true after evaluation. This project requires strong coordination and communication with an existing sysadmin. 

<del>This one is pretty straightforward. Nagios is to be used to monitor our infurstucture and most of the work is configuration and organization of resources. Talk to Walter to get access to a raspberry pi on the network to setup as a monitoring server. It should be able to set alerts, currently via the ACM's mail relay, in the event of the failure of any major service or machine outage. You will need to coordinate machine access for the Nagios (or whichever) instance.</del>

====== Resources======

[[https://www.icinga.org/icinga/icinga-2/]]

[[http://docs.icinga.org/icinga2/latest/doc/module/icinga2/toc]]

[[http://exchange.nagios.org/]]

[[http://www.nagios.org/documentation]]


IPMI Related Docs

====== Progress ======

  * August 25, 2015 - Decision made that project needs to be redone due to problems found in evaluation, Icinga2 should be tried next on a fresh linux install
  * January 28, 2015  - Setup on galaxy as the first client.
  * November 23, 2014 - LDAP nginx / Nagios Authentication setup.
  * November 22, 2014 - nginx installed to serve up Nagios webui.
  * November 17, 2014 - Nagios Installed on watchman.acm.cs