---------- Forwarded message ---------- From: Jens Rantil <[email protected]> Date: Sat, Jun 9, 2012 at 4:17 PM Subject: Re: [Supervisor-users] Supervising processes on multiple machines To: Alexander Krauss <[email protected]>
Hi Alex, We are running a couple of internal applications in using supervisor on a bunch of different machines. Just recently I started using Fabric[1] to orchestrate restarts among the different servers. We are partially also using cfengine[2] (v. 2) to roll out binaries and/or supervisor itself. Fabric also comes with host groups to easier classify different hosts. Using the execute[3] function you can easily orchestrate/poll status etc. of different hostgroups. Maybe this would help you in any way? If not, be a bit more specific about what exactly you would like to do. Is this simply for monitoring? In that case you could easily write a Nagios plugin that polls the local supervisor. Hope this helps, Jens [1] http://docs.fabfile.org/en/1.4.2/index.html [2] http://cfengine.com [3] http://docs.fabfile.org/en/1.4.2/api/core/tasks.html?highlight=execute#fabric.tasks.execute On Sat, Jun 9, 2012 at 11:12 AM, Alexander Krauss <[email protected]> wrote: > Dear list, > > Does anybody have experience with using supervisor on multiple machines? I > have roughly ten servers, each with a different configuration, running my > own daemon-like processes written in Python. Of course, I can run > supervisord on each machine, but it is easy to lose track of what is going > on where... > > My initial idea was that one could have a variant of supervisorctl or the > web interface that can dispatch its commands/requests to an arbitrary > number of supervisord processes and accumulate the results. Then, the > distributed processes could be controlled centrally. > > A refinement of the same idea is that such a dispatcher should itself > implement the xmlrpc interface and present itself as a single supervisord > process to clients, such that the existing supervisorctl tool could be used > for it. > > Has this possibility been considered before? Are there alternatives? Are > there difficulties? Does anybody have a similar use case, and what are your > solutions? > > Alex > ______________________________**_________________ > Supervisor-users mailing list > Supervisor-users@lists.**supervisord.org<[email protected]> > http://lists.supervisord.org/**mailman/listinfo/supervisor-**users<http://lists.supervisord.org/mailman/listinfo/supervisor-users> > -- Want to know how full my inbox is? Or how to get in touch with me faster? Or tell me your e-mail is not that important? Then check this out: http://courteous.ly/4WtfZY -- Want to know how full my inbox is? Or how to get in touch with me faster? Or tell me your e-mail is not that important? Then check this out: http://courteous.ly/4WtfZY
_______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
