<html><head></head><body><div class="gmail_quote">Kevin Fenzi <kevin@scrye.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div style="white-space: pre-wrap; word-wrap:break-word; ">On Fri, 04 Mar 2011 19:07:53 -0500
Gareth Marchant <gareth@litehaus.net> wrote:
> Does the nagios stage environment operate in an equivalent manner to
> prod such that testing nagios 3 in stage for these systems would
> accurately reflect prod? I assume that there are specific monitors
> for each of these systems that would need to be exercised? I can only
> imagine what that list will look like...
<a href="https://admin.stg.fedoraproject.org/nagios">https://admin.stg.fedoraproject.org/nagios</a>/
You can see that it can't reach/monitor a lot of the things that the real instance does. The stg env just doesn't have access to all the things it would need outside it.
kevin<hr />infrastructure mailing list
infrastructure@lists.fedoraproject.org
<a href="https://admin.fedoraproject.org/mailman/listinfo/infrastructure">https://admin.fedoraproject.org/mailman/listinfo/infrastructure</a></div></blockquote></div><br clear="all">How about devices? I am sure there are routers, switches, gateways, firewalls and maybe storage hardware monitored by nagios that are high priority/highly critical and worthy of test? <br>
<br>
How deeply should testing go or, put another way, how much go-live risk can be tolerated? Should a gap analysis of stage environment to production be performed prior to making a nagios test plan? I am not sure how rigorously structured this upgrade plan should be!<br>
<br>
<br>
</body></html>