search for: ignoreschedul

Greetings, Shouldn''t puppetd -o --ignoreschedules ... imply that splay* options are ignored :-) If that''s not the intended behavior could we get a --run-now that ignores splay* and schedules? Cheers, Ryan

I would like to have packages installed either in the early morning or whenever I manually choose to do so on a particular machine. I am trying to convert my existing configuration from cfengine so in that tool I had something like: packages: Hr03|ManualRun:: <package installation commands> This basically says to install packages if it''s either 3:00-3:59am or if

Hello all, I''m thinking about a configuration class that, amongst other things execs out to a ''dangerous'' configuration script. I''d like to make this a noop by default, so the operator has to try a bit harder to invoke it. So I thought about doing something like: class blah { exec { danger: noop => true, tag => hitme, command

I was wondering how to configure the puppet clients to only listen, not to periodically pull configs down from the puppetmaster. I''d rather push the configs out from the puppetmaster with puppetrun... At a guess I need to set runinterval to 0 in /etc/puppet/puppet.conf? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post

Hi, I''m in the process of evaluating puppet and cfengine for a rollout on a mix of in-house servers and managed customer servers. I''ve always been a pro-cfengine man, and it''s already running on a small setup of 5 machines. But even though I have pretty clear idea of how I should proceed building the system, I''m intimidated by the vast amount of

...e yum -t -y install puppet-agent fi cat > /etc/puppetlabs/puppet/puppet.conf << EOF [main] vardir = /opt/puppetlabs/puppet/cache logdir = /var/log/puppetlabs/puppet rundir = /var/run/puppetlabs ssldir = /etc/puppetlabs/puppet/ssl [agent] pluginsync = true report = true ignoreschedules = true ca_server = urzlxdeploy.rz.uni-leipzig.de certname = galaxy110.sc.uni-leipzig.de environment = production server = urzlxdeploy.rz.uni-leipzig.de EOF puppet_unit=puppet /usr/bin/systemctl list-unit-files | grep -q puppetagent && puppet_unit=puppetagent /...

...n-production.pem hostprivkey = /var/lib/puppet/ssl/private_keys/vusion-production.pem hostpubkey = /var/lib/puppet/ssl/public_keys/vusion-production.pem http_compression = false http_proxy_host = none http_proxy_port = 3128 httplog = /var/log/puppet/http.log ignorecache = false ignoreimport = false ignoreschedules = false inventory_port = 8140 inventory_server = puppet inventory_terminus = facter keylength = 1024 lastrunfile = /var/lib/puppet/state/last_run_summary.yaml lastrunreport = /var/lib/puppet/state/last_run_report.yaml ldapattrs = all ldapbase = "" ldapclassattrs = puppetclass ldapnodes...

I have a test area network that is not routed to the production network because of IP address space re-use between the two networks. I would like the puppetmaster to serve both the production and test area networks. The puppetmaster is on the production network. I understand the puppet to puppetmaster connect to be HTTP using SSL. Can I somehow setup the puppet clients to use an HTTP

I just started digging into puppet and it looks like puppet is using a pull model. You have a master server and clients talk to it to get config info. Is anyone out there using a push model? If not, why not? Are there security reasons you would use one over the other? It seems that cfengine also uses a push model, so I wondered if this is a "standard" or if there are specific

Hello... I need some help with tags. as an example: # pseudo code class ssh { file { "/etc/ssh/ssh_config": # normal stuff tag("dangerous") } file { "/etc/ssh/sshd_config": # normal stuff tag("dangerous") } file { "/etc/ssh/ssh_known_hosts": # normal stuff tag("safe") } } on client: puppetd --tags

...a failure. This can help reduce flapping if too # many clients contact the server at one time. # The default value is ''120''. # configtimeout = 120 # Boolean; whether puppet agent should ignore schedules. This is useful # for initial puppet agent runs. # ignoreschedules = false # The port to communicate with the report_server. # The default value is ''$masterport''. report_port = 8140 # Whether puppet agent should listen for # connections. If this is true, then puppet agent will accept incoming # REST API requests, subj...