Puppet users - Jun 2013 - Puppetd with --noop and operation with puppetrun

Hi,

I have a puppetd 2.7 running on my server with --noop. I don''t like 
automatic updates. I have foreman and foreman-proxy. Can I run puppetrun 
from foreman and execute updates on my server with puppetd running with 
--noop?
I want a manual updates, not automatic.

Thank you
Giovanni

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

On Thursday, June 6, 2013 1:29:58 PM UTC-5, Giovanni
wrote:
>
> Hi,
>
> I have a puppetd 2.7 running on my server with --noop. I don''t
like
> automatic updates. I have foreman and foreman-proxy. Can I run puppetrun 
> from foreman and execute updates on my server with puppetd running with 
> --noop?
>

I wouldn''t think so.

 
> I want a manual updates, not automatic.
>
>
Instead of --noop, I think you want --no-client.  That will prevent the 
agent from automatically retrieving and applying catalogs, but when 
triggered via puppetrun it will apply whatever catalog it retrieves 
normally.


John

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

> Instead of --noop, I think you want --no-client.  That will prevent the 
> agent from automatically retrieving and applying catalogs, but when 
> triggered via puppetrun it will apply whatever catalog it retrieves 
> normally.
>
>  
Thank you John for your suggestion. 
With --no-client puppet stop to send reports to puppermaster. 
Do I need to use a crontab for reports or I have to change some parameters 
in puppet.conf?

Giovanni

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

On Friday, June 7, 2013 11:54:24 AM UTC-5, Giovanni
wrote:
>
>
> Instead of --noop, I think you want --no-client.  That will prevent the 
>> agent from automatically retrieving and applying catalogs, but when 
>> triggered via puppetrun it will apply whatever catalog it retrieves 
>> normally.
>>
>>  
> Thank you John for your suggestion. 
> With --no-client puppet stop to send reports to puppermaster. 
>

Do you mean it does not send reports when you manually trigger the client 
to perform a run, or that it does not send reports on a regular schedule?  
The latter is to be expected, since the whole point of --no-client is that 
the agent does not perform any automated runs in the first place (so 
there''s nothing to report on).

On the other hand, if the agent is configured to send reports but does not 
do so when it actually performs a run, then I would account that a bug.  If 
that''s the case then I recommend you file a ticket.

 
> Do I need to use a crontab for reports or I have to change some parameters 
> in puppet.conf?
>
>
If you want agent reports on a regular schedule then you need to perform 
runs on a regular schedule.  If you do not want these regularly-scheduled 
runs to change anything, then the agent processes performing them should 
use --noop.

If you want to be able to trigger runs via the ''puppetrun''
mechanism (which
is what I think foreman does) then you must have an agent running in daemon 
mode and listening for network requests to perform runs.  For those 
triggered runs to actually apply any changes, the agent processes 
performing them must *not* use --noop.

To the best of my knowledge and expectation, you cannot get both --noop and 
standard behavior from the same agent process, therefore you need separate 
processes if you want both types of behavior on the same node.  Your best 
bet in that case would be to perform the --noop runs via an external 
scheduler, such as cron (though there are other alternatives).  (So
that''s
a long-winded "yes".)

Do note that if you try to trigger a manual run while an automated --noop 
run is in progress then the manual run will be blocked (but the agent 
should recover gracefully).


John

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