With changes to Nagios, use github for the latest Nagios code: http://github.com/tonvoon/opsview-nagios

Work there, including changes, documentation, tests.

Push to github.

Make a patch and add to opsview-base. Test functionality in new Opsview builds.

Some notes on upgrading Nagios. Also see 3rdpartycode

Check opsview-core/t/990nagconfgen.t returns back clean.

Get latest stable tarball.

Change opsview-base/Makefile with new version

rm nagios-{version}. Run make nagios to compile with newer nagios.

Edit patches as required, that maybe due to changes in core code.

Compare sample-config/nagios.cfg against the latest generated nagios.cfg. Add in any new variables.

Run opsview-core/t/990nagconfgen.pl. Check that changes are as expected.

Add CHANGES message to ENHANCEMENTS. Highlight anything that needs attention.

svn rm older version

Commit

Nagios CGIs are wrapped using [http://search.cpan.org/dist/Catalyst-Controller-WrapCGI/ Catalyst::Controller::WrapCGI], though we use a specific version within Opsview::Web.

If a Nagios CGI is likely to break how Opsview works (such as deleting a specific downtime by id number - this will not work in a distributed environment), either:

• disable the functionality in the CGIs
• redirect the request to an Opsview page