Comment 6 for bug 1457768

Revision history for this message
N Dillon (sicarie) wrote :

I'm not sure why I mentioned the sec-guide in there, however my original bug was that only a select few items were called out generally. Re-opening was due to:

1) My main issue is that the two examples I see are for disk utilization and plugins and only 5 total general categories are called out (Disk usage, Server load, Memory usage, Network I/O, Available vCPUs) - are these the only things that should be monitored on a nova deployment? Is warning at 80% utilization and critical at 90 applicable across *all* deployments? Or is there a way we can enable a deployer to determine what their threshold should be based on their use-case?

2) The examples are in Nagios - this issue was recently brought up in the sec-guide: do we attest to non-OpenStack ecosystem applications? Should this be referenced in its own section?

3) Object storage links are to Mirantis docs - are these not addressed in the OpenStack documentation? It's fine if they're not, I just want to make sure that is being considered (and we should probably have doc bugs opened on them for that project in that case).

Full disclosure: I'm a huge Nagios fan, I think it should be in there, but I also think that getting coverage on *what* would be more useful, and we need to make sure the Foundation agrees with the position of including/not the outside applications (sec-guide dev has slowed significantly due to this ambiguity). Had I not been on leave, I would have recommended this be merged as a partial-bug until we get the rest of the "what" set up. Apologies for the lateness and lack of clarity!