On 10 Mar 2010, at 11:15, . . wrote:
I guess there is no documentation for that. Does anyone have any idea how it could be accomplished apart from mounting the opsview-web site folder from the master via NFS ?
There is a dependency with Opsview-web (running on port 3000) and Nagios being on the same server. This is because the app server needs to be able to communicate with Nagios to do certain actions (reload, display the Nagios screens, acknowledge, etc).
You could move the Apache front end to a different server and proxy that through to the app server, but we haven't done this so haven't created any docs for this. If you'd like to add some documentation here, I'd be more than happy to give you access to http://docs.opsview.org .
There's also the possibility of splitting portions of the app server onto a different server because it just has database communications and does not need Nagios interaction - this would work for /status and /events. /graph needs the main server because it reads the RRD files. Actually, thinking about it, there are some session information which is stored on the filesystem of the app server (/tmp/opsview), so there maybe issues moving sessions between different app servers until we put that session info into the database instead.
Ton _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
