Proxy services restart

I'm revisiting Feature #6781: Capsule: need method of restarting capsule services, akin to 'katello-services' - Katello - Foreman yet again,
which is the bug to provide a way to restart capsule services.

The idea being you could do "capsule-service restart/stop/start/status"
and it would restart DHCP, DNS, Pulp, and then foreman-proxy.

This is a bit more complicated than katello-service, given the variety
of services a proxy can manage, and also we don't own it all.

So, a few points:

  1. Are we using the "capsule" terminology in Katello? It's confusing, I
    believe it should just be called Smart/Foreman proxy.

  2. Should this be a Katello-only feature? I've been thinking about it
    for a while, and maybe this is useful if the smart proxy plug-ins
    themselves say if they use local service(s), and if so which, and then
    some tool – e.g. proxy-service can do the actions.

Would Foreman be interested in such a tool for the smart proxy?

  1. Is this really needed? I suppose a "proxy-service status" could be
    useful, but global start/restart is really heavy handed, I've never
    needed to do it. I just make my changes to the specific component
    service I'm interested in (e.g. bind), and then restart it, and
    maybe foreman-proxy.
··· -- Stephen Benjamin

Red Hat GmbH | http://de.redhat.com/ | Sitz: Grasbrunn
Handelsregister: Amtsgericht München, HRB 153243
Geschäftsführer: Charles Cachera, Michael Cunningham,
Michael O’Neill, Charles Peters

> I'm revisiting Feature #6781: Capsule: need method of restarting capsule services, akin to 'katello-services' - Katello - Foreman yet again,
> which is the bug to provide a way to restart capsule services.
>
> The idea being you could do "capsule-service restart/stop/start/status"
> and it would restart DHCP, DNS, Pulp, and then foreman-proxy.
>
> This is a bit more complicated than katello-service, given the variety
> of services a proxy can manage, and also we don't own it all.
>
> So, a few points:
>
> 1) Are we using the "capsule" terminology in Katello? It's confusing, I
> believe it should just be called Smart/Foreman proxy.

It's already difficult enough that the project is called smart-proxy,
but deployed as foreman-proxy upstream. That downstream calls it capsule
makes it even harder.

> 2) Should this be a Katello-only feature? I've been thinking about it
> for a while, and maybe this is useful if the smart proxy plug-ins
> themselves say if they use local service(s), and if so which, and then
> some tool – e.g. proxy-service can do the actions.

In theory it could become very complex. You can specify an external DNS
server. Also other plugins could require additional services. To keep it
correct, it would need to restart every additional service.

> 3) Is this really needed? I suppose a "proxy-service status" could be
> useful, but global start/restart is really heavy handed, I've never
> needed to do it. I just make my changes to the specific component
> service I'm interested in (e.g. bind), and then restart it, and
> maybe foreman-proxy.

As a user, I never felt the need for this. I managed configs through
puppet which restarted specific services as needed.

All in all I don't really see a use case for this.

··· On Tue, Nov 04, 2014 at 02:58:10PM +0100, Stephen Benjamin wrote: