CAF::Service should allow to enable a service about caf HOT 4 CLOSED

we can rediscuss this during the workshop, but i still do not see why ncm-chkconfig can't be used.
the components should configure the service they are meant to configure (this could mean briefly starting a service, but should also restore the service to its original state, i.e. stopping it in the end if it wasn't running before). the only component needed to actually enable services is ncm-chkconfig.
implementing the logic in pan is the preferred option imho, also because it is a lot easier typically (and less perl code 😄 )

what we do need however, is a CAF::Service->status() (and a condrestart), most of which can be found https://github.com/quattor/configuration-modules-core/blob/master/ncm-postgresql/src/main/perl/Postgresql/Service.pm

if we would decide however that this is feature that components can handle, i think we should make this part of CAF::Service->start (or restart). i.e. any service started should be enabled automatically (or by default). (but removing the component should also imply disabling it, so some trivial unconfigure might required for each such component.

from caf.

I agree with you last paragraph: it should not be a distinct method but really an option of methods affecting the service state do do it permanently. I thought we already had the status and condrestart methods, they are clearly needed.
I will try to have a look to see if I can offload the chkconfig part in ncm-dpmlfc to the template site without adding too much complexity to the templates (that are already quite large).

from caf.

status and espcially condrestart are not provided by all sysvinit services, so having it in CAF might imply that it doesn't work (and there's no easy way to query the init script to see if it is supported or not). also , i have no clue what the situation is in solaris.

from caf.

As discussed at 21st workshop, we have decided that we will not implement this.

from caf.