Puppet users - Oct 2012 - how to stop puppet from checking a service

Is there an way for puppet to not check whether a service is running
or not? I''m basically looking for the equivalent of enable => manual
for Linux systems, I think. This would be useful when the service
itself is under the control of a CRM like Pacemaker or I want to give
control of the service to an end user, say both tomcat and glassfish
are on the same box and they want to run one instead of the other.

Supposedly the Example42 modules support this by disableboot=>true,
but that doesn''t appear to do anything other than set "enable
=>
false" for the service and I don''t see how that stops Puppet from
checking whether the service is up or down.

Thanks!

--
Later,
Darin

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Monday, October 1, 2012 3:56:42 PM UTC-5, Darin Perusich
wrote:
>
> Is there an way for puppet to not check whether a service is running 
> or not? I''m basically looking for the equivalent of enable =>
manual
> for Linux systems, I think. This would be useful when the service 
> itself is under the control of a CRM like Pacemaker or I want to give 
> control of the service to an end user, say both tomcat and glassfish 
> are on the same box and they want to run one instead of the other. 
>

I suspect it''s not possible to prevent Puppet from *checking* whether a
managed service is running, but it may be possible to prevent it from *
managing* whether the service is running.  Try omitting the
''ensure''
parameter altogether.

Note that if you''re not managing whether the service is running, then
the
only other thing about it you can be managing is whether it starts at boot 
(via the ''enable'' parameter).  If you don''t want to
manage that either,
then just don''t declare a Service resource in the first place.


> Supposedly the Example42 modules support this by disableboot=>true, 
> but that doesn''t appear to do anything other than set "enable
=>
> false" for the service and I don''t see how that stops Puppet
from
> checking whether the service is up or down. 
>
>
It doesn''t, but what''s the harm in just checking?

I haven''t looked at the modules you''re talking about, but
perhaps they do
as I suggested?  It would be fairly easy to overlook complete omission of a 
parameter -- much more so than to overlook a special parameter value.


John

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/GdMKCawsHsoJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Mon, Oct 1, 2012 at 6:03 PM, jcbollinger <John.Bollinger@stjude.org>
wrote:
>
>
> On Monday, October 1, 2012 3:56:42 PM UTC-5, Darin Perusich wrote:
>>
>> Is there an way for puppet to not check whether a service is running
>> or not? I''m basically looking for the equivalent of enable
=> manual
>> for Linux systems, I think. This would be useful when the service
>> itself is under the control of a CRM like Pacemaker or I want to give
>> control of the service to an end user, say both tomcat and glassfish
>> are on the same box and they want to run one instead of the other.
>
>
>
> I suspect it''s not possible to prevent Puppet from checking
whether a
> managed service is running, but it may be possible to prevent it from
> managing whether the service is running.  Try omitting the
''ensure''
> parameter altogether.
You are correct...by omitting the "ensure" the service is no longer
checked to if it''s running or not.

Thanks!
> Note that if you''re not managing whether the service is running,
then the
> only other thing about it you can be managing is whether it starts at boot
> (via the ''enable'' parameter).  If you don''t want
to manage that either, then
> just don''t declare a Service resource in the first place.
>
>
>>
>> Supposedly the Example42 modules support this by disableboot=>true,
>> but that doesn''t appear to do anything other than set
"enable =>
>> false" for the service and I don''t see how that stops
Puppet from
>> checking whether the service is up or down.
>>
>
> It doesn''t, but what''s the harm in just checking?
>
> I haven''t looked at the modules you''re talking about, but
perhaps they do as
> I suggested?  It would be fairly easy to overlook complete omission of a
> parameter -- much more so than to overlook a special parameter value.
>
>
> John
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/GdMKCawsHsoJ.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.