[Supervisor-users] New to supervisor

[Brian Dunbar]

Hi,

On suggestion from my lead dev, I'm looking at supervisor as a replacement
for upstart on our SaaS stack. Looks cool. And I do like the web
interface.

I'm confused about this line from Introduction:Features.

Does it imply that if I have host A, assuming I have things setup
correctly, I can manage processes on hosts B, C, and D?

Centralized

Supervisor provides you with one place to start, stop, and monitor your
processes. Processes can be controlled individually or in groups. You can
configure Supervisor to provide a local or remote command line and web
interface.


Because if so that would be very, very, slick. As our app has matured
we've blown out the server stack and so what once was 'a' server now has
many other components and it's gotten to be quite the handful to manage.

[Jens Rantil]

Hi Brian,

What you have read is true. You can control processes on multiple machines using the "supervisorctl" command line tool (or supervisor's XML-RPC from code). The manual[1] states:

"The command-line client talks to the server across a UNIX domain socket or an internet (TCP) socket. The server can assert that the user of a client should present authentication credentials before it allows him to perform commands. The client process typically uses the same configuration file as the server but any configuration file with a [supervisorctl] section in it will work."

[1] http://supervisord.org/introduction.html#supervisor-components

I hope this clarifies things.

Cheers,
Jens

Hi,
On suggestion from my lead dev, I'm looking at supervisor as a replacement for upstart on our SaaS stack. Looks cool. And I do like the web interface.
I'm confused about this line from Introduction:Features.
Does it imply that if I have host A, assuming I have things setup correctly, I can manage processes on hosts B, C, and D?
Centralized
Supervisor provides you with one place to start, stop, and monitor your processes. Processes can be controlled individually or in groups. You can configure Supervisor to provide a local or remote command line and web interface.
Because if so that would be very, very, slick. As our app has matured we've blown out the server stack and so what once was 'a' server now has many other components and it's gotten to be quite the handful to manage.
--
Brian Dunbar
"Display some adaptability"
_______________________________________________
Supervisor-users mailing list
https://lists.supervisord.org/mailman/listinfo/supervisor-users

[Richard Moorhead]

So for example;

two nodes, A (server) B (client)

supervisor would be installed for both nodes

supervisord.conf for B would need to point to A via

[supervisorctl]
serverurl = http://hostA:9001

The program configurations specific to B would only be present in the
supervisord.conf on B.

Is this correct?

[Jens Rantil]

Richard,

That is correct. However, you can also set `--serverurl` as a command line
parameter to `supervisorctl`. That way, you don't need to add it to
`[supervisorctl]`.

/J


On Sat, Jan 11, 2014 at 12:43 AM, Richard Moorhead <

Post by Richard Moorhead
So for example;
two nodes, A (server) B (client)
supervisor would be installed for both nodes
supervisord.conf for B would need to point to A via
[supervisorctl]
serverurl = http://hostA:9001
The program configurations specific to B would only be present in the supervisord.conf on B.
Is this correct?