On 02/07/2003 02:16 PM, Paul Winkler wrote:

On Fri, Feb 07, 2003 at 10:32:44AM -0800, sean.upton@uniontrib.com wrote:

...

If there is any interest in a framework that could provide the underlying functionality to multiple UI front-ends, as well as automated stuff like alerts/monitoring, I would certainly be interested in using and contributing to development of such a beast.

Oooh! Oooh! One more: build in a window with a python prompt that connects straight in to a ZEO debugging session ( (possibly remotely).

Okay, I added some features to the mockup: http://hathaway.freezope.org/Images/controller_snapshot2.png Now the right-hand panel is a scrolling window with expand buttons to the left of each process being monitored. That way, this little GUI can scale up to monitoring large clusters or many independent Zopes. I also added a "debug" button to one of the ZEO clients, which would open a Python prompt in a window. I imagine that the interface to the backend would be a TCP connection with simple text commands and asynchronous replies. Using TCP this way makes it possible to use either a local connection or SSH to connect to the server being monitored. As for PyQT vs. wxPython, either one is fine. I also lean toward wxPython, partly because its license is simple. Shane

Very nice Shane! I want one! I definitely agree with the separation of UI and back-end.

On Fri, Feb 07, 2003 at 12:00:45PM -0800, Jamie Heilman wrote:

...

Heck, I would love to have an curses-based alternative to manage, monitor, and provide an interface to restart all ZEO clients and ZSS boxes in a terminal; this would make for easier remote admin via SSH from potentially different client platforms.

I've said it before, but http://cr.yp.to/daemontools.html

... which, FYI is kind of a pain to use with zope prior to CVS / 2.7, because zope insists on forking to the background unless you run in debug (-D) mode, and daemontools (or rather, svc) is designed to work with daemons that can be run in the foreground. So we can either run with -D even though it turns on all kinds of crap that you may not want on a production server, or write a wrapper zope script that runs in the foreground and signals Zope when you signal it. The latter solution "works" but seems rather fragile. Have I mentioned lately that I'm very thankful to the people that are working on decomposing the various behaviours toggled by -D? -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's PREFIX SADIST! (random hero from isometric.spaceninja.com)

On Fri, Feb 07, 2003 at 12:41:36PM -0800, Jamie Heilman wrote:

Paul Winkler wrote:

...

... which, FYI is kind of a pain to use with zope prior to CVS / 2.7, because zope insists on forking to the background unless you run in debug (-D) mode, and daemontools (or rather, svc) is designed to work with daemons that can be run in the foreground. So we can either run with -D even though it turns on

Oh. I rewrote z2.py and use my own logger. So I never ran into that problem.

I looked into doing exactly that, but I pretty quickly gave up trying to trace exactly what happens when you select "debug". It didn't look easy to get z2 in the foreground without all the other stuff.

I'll probably release an alpha of my work sometime soon, let me know if you're interested and I'll make sure to notify you when its ready.

That would be nice, thanks! -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's POLYTHEI-ROBBER VON ALPHA! (random hero from isometric.spaceninja.com)