I almost have this working 100%. Combining information from posts from versions 1.x and 2.x (mostly Chet - thanx!), I did the following ; Note: The primary/central server is A and the additional one is B. Both of these servers sit behind a firewall so apache is used with the mod_rewrite module in order to access zenoss over port 80 from my desktop.
1) Create DNS CNAMES Host A: zenoss.<your domain>.com Host B: B.zenoss.<yourdomain>.com 2) Configured the following daemons on B to connect to A's zenhub and appropriate monitor zenperfsnmp zencommand zenprocess zenwin zeneventlog zenwinmodeler with the following in the .conf file monitor B.zenoss.<your domain>.com hubhost zenoss.<your domain>.com 3) Create a performance monitor on host A with the name of B.zenoss.<your domain>.com 3b) Set the RenderURL to http://B.zenoss.<your domain>.com:80 (or 8080 depending on config) 3c) I used the admin login/password for the Render User/Pass 4) Modified the $ZENHOME/Products/PluggableAuthService/plugins/CookieAuthHelper.py line containing "setCookie" to the following: response.setCookie(self.cookie_name, quote(cookie_val), path='/', domain='zenoss.yourdomain.com') 5) Have Zope on B use the ZODB server on A: Edit $ZENHOME/etc/zope.conf on B: Search for the zeoclient section and change the server to zenoss.<your domain>.com 6) Modify the Zenoss startup on B to the following; Edit $ZENHOME/bin/zenoss #C="$C zeoctl" C="$C zopectl" #C="$C zenhub" #C="$C zenping" #C="$C zensyslog" #C="$C zenstatus" #C="$C zenactions" #C="$C zentrap" #C="$C zenmodeler" ##C="$C zenrender" C="$C zenperfsnmp" C="$C zencommand" C="$C zenprocess" ##C="$C zenmail" 7) For apache I had to change the rewrite mode to update it with the zenoss.<your domain>.com in the rule ServerName also needs to be B.zenoss.<your domain>.com on B and zenoss.<your domain>.com on A Now this works...I get the graphs etc. I know I need to set the permissions for the database so events can be seen from B but I am only looking to this to work from A at the moment. Now the only time it worked was AFTER I went directly to server B and logged in. This is when the cookie for B was created locally on my PC. Before this, the graphs were still being denied due to authorization. I suspect I am missing something for the cookie. The cookie zenoss.<your domain>.com exists. Then a separate cookie, NOT in this tree was created afterwards B.zenoss.<your domain>.com. Anyone else better with cookies can explain? It would be really helpful. Also not sure why zenactions gets started on B. Also need to figure out how to stop server B from showing up as a zenoss issue on A. It would be really nice if the graphs used the render user/pass as well...instead of just being used for SysUptime on the top device page. It would make everything so much easier. -Paul -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=12681#12681 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
