I wrote a proof of concept of web ui that could connect, monitor and control multiple supervisord servers, but the idea of xmlprc proxy seems neat!
The one issue I can see there is grouping the processes by server without breaking possible existing groups on the same box, since one process cannt be in multiple groups in current supervisord implementation.. Anyway, I'd be happy to take part in the developement. Regards, Ales Dne 9.6.2012 11:24 "Alexander Krauss" <[email protected]> napsal(a): > 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> >
_______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
