Comments on: My Zenoss Development Environment – Part 1 http://blog.nuclearbunny.org/2009/10/22/my-zenoss-development-environment-part-1/ Fri, 30 Dec 2011 19:10:01 +0000 hourly 1 http://wordpress.org/?v=3.3 By: davetoo http://blog.nuclearbunny.org/2009/10/22/my-zenoss-development-environment-part-1/comment-page-1/#comment-459 davetoo Wed, 14 Apr 2010 04:56:42 +0000 http://blog.nuclearbunny.org/?p=469#comment-459 bash-3.2$ svn info ... URL: http://dev.zenoss.org/svn/tags/zenoss-2.4.2/inst bash-3.2$ svn info
…
URL: http://dev.zenoss.org/svn/tags/zenoss-2.4.2/inst

]]> By: chadwick http://blog.nuclearbunny.org/2009/10/22/my-zenoss-development-environment-part-1/comment-page-1/#comment-457 chadwick Wed, 14 Apr 2010 00:41:14 +0000 http://blog.nuclearbunny.org/?p=469#comment-457 So are you building from source, and are you using trunk or another version like 2.4.x or 2.5.x? Trunk source builds are a little funky right now and are under great-flux as we move to the new version of Python and Zope... So are you building from source, and are you using trunk or another version like 2.4.x or 2.5.x?

Trunk source builds are a little funky right now and are under great-flux as we move to the new version of Python and Zope…

]]> By: davetoo http://blog.nuclearbunny.org/2009/10/22/my-zenoss-development-environment-part-1/comment-page-1/#comment-456 davetoo Wed, 14 Apr 2010 00:39:45 +0000 http://blog.nuclearbunny.org/?p=469#comment-456 So I'm not sure what steps I missed, but I ended up with an install with only Zenoss components in $ZENHOME/Products, and I had to execute a separate step to check that directory out from svn and then re-run part of the post-install config process. I don't know if this happened because I was installing as a nonstandard user into a nonstandard place, or there are some steps missing from the build-from-svn process. I suspect the latter, actually. So I’m not sure what steps I missed, but I ended up with an install with only Zenoss components in $ZENHOME/Products, and I had to execute a separate step to check that directory out from svn and then re-run part of the post-install config process. I don’t know if this happened because I was installing as a nonstandard user into a nonstandard place, or there are some steps missing from the build-from-svn process. I suspect the latter, actually.

]]> By: davetoo http://blog.nuclearbunny.org/2009/10/22/my-zenoss-development-environment-part-1/comment-page-1/#comment-455 davetoo Tue, 13 Apr 2010 23:22:24 +0000 http://blog.nuclearbunny.org/?p=469#comment-455 I also had to install mysql-devel (RHEL 5.5). So I did the build/install as described above but it defaulted to username 'zenoss'; it looks like we might need to patch build-functions.sh. I was trying to figure out how to recover from that without doing another hour-long build, but I have up and hardcoded my username in build-functions.sh and install-functions.sh. I also had to install mysql-devel (RHEL 5.5).

So I did the build/install as described above but it defaulted to username ‘zenoss’; it looks like we might need to patch build-functions.sh. I was trying to figure out how to recover from that without doing another hour-long build, but I have up and hardcoded my username in build-functions.sh and install-functions.sh.

]]> By: chadwick http://blog.nuclearbunny.org/2009/10/22/my-zenoss-development-environment-part-1/comment-page-1/#comment-454 chadwick Tue, 13 Apr 2010 13:25:07 +0000 http://blog.nuclearbunny.org/?p=469#comment-454 Yep, everything in my dev environment is always being run as my local user. I usually maintain a trunk version and two older versions in separate directories for support. For the MySQL database, I just name the database something like events25 or events24 to keep them separate from one another. Yep, everything in my dev environment is always being run as my local user. I usually maintain a trunk version and two older versions in separate directories for support. For the MySQL database, I just name the database something like events25 or events24 to keep them separate from one another.

]]> By: davetoo http://blog.nuclearbunny.org/2009/10/22/my-zenoss-development-environment-part-1/comment-page-1/#comment-453 davetoo Tue, 13 Apr 2010 08:06:30 +0000 http://blog.nuclearbunny.org/?p=469#comment-453 So this is not running as user 'zenoss' but your usual login? Do you maintain environments for multiple Zenoss versions/instances? e.g. for sustaining/backports? How do you deal with mysql if so? So this is not running as user ‘zenoss’ but your usual login?

Do you maintain environments for multiple Zenoss versions/instances? e.g. for sustaining/backports? How do you deal with mysql if so?

]]> By: chadwick http://blog.nuclearbunny.org/2009/10/22/my-zenoss-development-environment-part-1/comment-page-1/#comment-445 chadwick Fri, 26 Mar 2010 15:20:38 +0000 http://blog.nuclearbunny.org/?p=469#comment-445 <a href="#comment-444" rel="nofollow">@Matthew </a> For reference, we're working on a native build for Snow Leopard and the trunk version of Zenoss right now. It's using Python 2.6 so the build issues are going away... real soon now. @Matthew For reference, we’re working on a native build for Snow Leopard and the trunk version of Zenoss right now. It’s using Python 2.6 so the build issues are going away… real soon now.

]]> By: Matthew http://blog.nuclearbunny.org/2009/10/22/my-zenoss-development-environment-part-1/comment-page-1/#comment-444 Matthew Thu, 25 Mar 2010 18:11:24 +0000 http://blog.nuclearbunny.org/?p=469#comment-444 Fabulous, thank you. In general, I appreciate Apple's innovation, and how willing they are to depart from the past (sacrificing backwards compatibility) in order to move technology forward. However, this isn't one of those times... : ) Fabulous, thank you. In general, I appreciate Apple’s innovation, and how willing they are to depart from the past (sacrificing backwards compatibility) in order to move technology forward. However, this isn’t one of those times… : )

]]> By: chadwick http://blog.nuclearbunny.org/2009/10/22/my-zenoss-development-environment-part-1/comment-page-1/#comment-443 chadwick Thu, 25 Mar 2010 13:43:07 +0000 http://blog.nuclearbunny.org/?p=469#comment-443 One of our developers came up with a work-around that uses the stack installer to provide the binaries and then you can customize that to make a development environment out of it, as described below: 1. Download the latest BitRock stack (core) from http://www.zenoss.com such as http://downloads.sourceforge.net/zenoss/zenoss-stack-2.5.2.app.tar.gz 2. Install it to, say, /Users/ian/zenoss. Unless your name is ian, I suggest you do not copy/paste this path. 3. Don't launch it yet 4. Shut down the mysql daemon that was started by the installer: $ ps aux | grep $ZENDIR/mysql | awk '{print $2}' | sudo xargs kill 5. Run this: $ export ZENDIR=/Users/ian/zenoss $ export ZENUSR=ian # Again, probably not a copy/paste candidate here $ sudo chown -R $ZENUSR $ZENDIR/mysql/data/events $ find $ZENDIR -user zenoss | sudo xargs chown $ZENUSR:staff $ find $ZENDIR/mysql -user root -o -user _mysql | sudo xargs chown $ZENUSR 6. Assuming you have a checkout of Zenoss trunk in ~/src/core, do: $ rm -rf $ZENDIR/zenoss/Products && ln -s ~/src/core/Products $ZENDIR/zenoss/Products 7. Edit ~/.bashrc (or ~/.profile, if .bashrc isn't sourced in .profile) and add: export PATH=$PATH:/Users/ian/zenoss/zenoss/bin To make life a little easier, can also add: export ZENHOME=/Users/ian/zenoss/zenoss alias cdp=cd $ZENHOME/Products alias cdz=cd $ZENHOME alias zpy=$ZENHOME/bin/python 8. Make a few changes to $ZENHOME/etc/zope.conf. Find "effective-user zenoss" (line 153) and change it to: effective-user ian Then find "# debug-mode on" (line 138) and uncomment it. 9. Get mysql into your path: $ ln -s $ZENDIR/mysql/scripts/ctl.sh $ZENDIR/zenoss/bin/zenmysqld $ ln -s $ZENDIR/mysql/bin/mysql $ZENDIR/zenoss/bin/zenmysql C'est ça. Should now be able to start up mysql: $ zenmysqld start Then ZEO, and run Zope in the foreground with debug output: $ zeoctl start $ runzope One of our developers came up with a work-around that uses the stack installer to provide the binaries and then you can customize that to make a development environment out of it, as described below:

1. Download the latest BitRock stack (core) from http://www.zenoss.com such as http://downloads.sourceforge.net/zenoss/zenoss-stack-2.5.2.app.tar.gz
2. Install it to, say, /Users/ian/zenoss. Unless your name is ian, I suggest you do not copy/paste this path.
3. Don’t launch it yet
4. Shut down the mysql daemon that was started by the installer:

$ ps aux | grep $ZENDIR/mysql | awk ‘{print $2}’ | sudo xargs kill

5. Run this:

$ export ZENDIR=/Users/ian/zenoss
$ export ZENUSR=ian # Again, probably not a copy/paste candidate here
$ sudo chown -R $ZENUSR $ZENDIR/mysql/data/events
$ find $ZENDIR -user zenoss | sudo xargs chown $ZENUSR:staff
$ find $ZENDIR/mysql -user root -o -user _mysql | sudo xargs chown $ZENUSR

6. Assuming you have a checkout of Zenoss trunk in ~/src/core, do:

$ rm -rf $ZENDIR/zenoss/Products && ln -s ~/src/core/Products $ZENDIR/zenoss/Products

7. Edit ~/.bashrc (or ~/.profile, if .bashrc isn’t sourced in .profile) and add:

export PATH=$PATH:/Users/ian/zenoss/zenoss/bin

To make life a little easier, can also add:

export ZENHOME=/Users/ian/zenoss/zenoss
alias cdp=cd $ZENHOME/Products
alias cdz=cd $ZENHOME
alias zpy=$ZENHOME/bin/python

8. Make a few changes to $ZENHOME/etc/zope.conf. Find “effective-user zenoss” (line 153) and change it to:

effective-user ian

Then find “# debug-mode on” (line 138) and uncomment it.

9. Get mysql into your path:

$ ln -s $ZENDIR/mysql/scripts/ctl.sh $ZENDIR/zenoss/bin/zenmysqld
$ ln -s $ZENDIR/mysql/bin/mysql $ZENDIR/zenoss/bin/zenmysql

C’est ça. Should now be able to start up mysql:

$ zenmysqld start

Then ZEO, and run Zope in the foreground with debug output:

$ zeoctl start
$ runzope

]]> By: Matthew http://blog.nuclearbunny.org/2009/10/22/my-zenoss-development-environment-part-1/comment-page-1/#comment-442 Matthew Thu, 25 Mar 2010 03:58:40 +0000 http://blog.nuclearbunny.org/?p=469#comment-442 Thank you for this post. Do you have the actual workaround mentioned here, for building Zenoss on Snow Leopard? Thank you for this post. Do you have the actual workaround mentioned here, for building Zenoss on Snow Leopard?

]]>