Re: [Puppet Users] What can I do with erb templates in Puppet?

[Spencer Krum]

Puppet provides the erb templating system so you can do variable expansion
and replacement in your templates. The templates are processed on the
puppet master and sent to the client (windows) as text. The windows client
then replaces the old config file with the new one from the template.

Step 1) Copy an existing config file into your puppet module's template
section. Name it config_file.erb

Step 2) Replace variables in the config file with puppet facts or variables
from your manifests

Example:
If a line said:
listen_address = 192.168.0.5
You would change it to:
listen_address = <%= $::ipaddress %>

Step 3) Run Puppet on the client. Nothing should change on the first
client, but all subsequent clients will be easier to configure.

Hope this helps,
Spencer

On Sat, Nov 22, 2014 at 12:24 AM, Renu Chuppala  wrote:

> Please provide me steps to modify the config files using templates in
> *WINDOWS*
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/45e3f9da-31e0-4311-8a9f-931918547ce8%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Spencer Krum
(619)-980-7820

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CADt6FWOTTRVf3P2PGRTDX9uCCr2fs%2BpR47yWeJ8q%3DaaUxnpN9w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] configure puppet master and puppet agent

[Giacomo Vacca]

It would be useful to see the output of the agent and the logs on the master.
Have you created and signed the SSL certificates?
Also alt_dns_names in puppet.conf may have an impact: how does your puppet.conf 
look like? What versions of Puppet are you using?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/eff19d0a-e1f2-4a71-9aab-98cca73dfd14%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] What can I do with erb templates in Puppet?

[Giacomo Vacca]

Take a look at Windows-related modules on the 
Forge:https://forge.puppetlabs.com/tags/windows

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/a46551bc-db67-4547-98fc-c23154993057%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] execution expired with a puppetmaster with more then enough resources

[Felix Frank]

On 11/16/2014 09:48 PM, Philipp Dallig wrote:
>
> I also found this message in log file. Possible a PuppetDB performance
> problem?
> Nov 16 00:41:58 puppetmaster01 puppet-master[27659]: Could not
> retrieve resources from the PuppetDB at
> puppetmaster01.xxx.com:8081: Net::ReadTimeout on node
> rpm-repo.x.com

> At the moment i have around 200 nodes (most nodes with empty catalog).
> Every node connect every 30 minutes to puppet master.

Hi,

well with 200 nodes at a 30 minute interval, you should be fine. The
4*1800 CPU seconds that are available should be plenty for this node
count, as long as compile times don't rise to ~ 40 seconds.

Do the PuppetDB errors coincide with the overly long compiler runs?

FWIW, the read timeout does not feel like a performance issue to me, but
rather like a transient connectivity issue (packet loss?). This is just
a shot in the dark though - I have next to no experience operating a
PuppetDB instance.

Are the overlong compiler runs always exactly 120 seconds above the norm?

Thanks,
Felix

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5470EA71.9050902%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: invalid checksum using template

[Felix Frank]

On 11/18/2014 06:36 PM, Josh Cooper wrote:
> I'm pretty sure puppet has a bug whereby it thinks content of the form
> {FOO} specifies a checksum whose algorithm is FOO, and then tries to
> retrieve a file whose checksum is FOO from the filebucket.
>
> See 
> https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type/file/content.rb#L50-L53
>
> Josh

Yup. And it's been known for quite a while.

https://tickets.puppetlabs.com/browse/PUP-1043

I don't think that this can be worked around at the moment, unless the
OP can avoid `content` in favor of `source`.

Cheers,
Felix

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5470EFC6.806%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] SSL Cert issues - Puppet Agent and Master on same host

[Felix Frank]

On 11/18/2014 10:26 PM, kevin.mastel...@gmail.com wrote:
> [root@- puppet]# ./node.rb my-puppet-svr
> Could not send facts to Foreman: SSL_connect returned=1 errno=0
> state=SSLv3 read server certificate B: certificate verify failed

Hmm, I don't know which TCP port is used to contact Foreman, but I
suggest using `openssl s_client` to see which certificate is being
presented, and to see whether it can be verified using -CAfile.

HTH,
Felix

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5470F7C9.8090502%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] autosign with --allow-dns-alt-names

[Felix Frank]

On 11/20/2014 05:13 AM, Dejan Golja wrote:
> I was wondering if it's possible to change the autosign behavior that
> it will allow to autosign certs with alternative DNS entries.
> Currently the problem is if an auto scaling events create another
> master the autosign on CA will fail, because it has alternative DNS
> entries. 

Hi,

can you elaborate on your problem? I don't really see what's going on.

Who has alternative DNS entries? How does this interfere with your
autosigning?

Thanks,
Felix

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5470F94D.1050505%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Planning dynamic environments with Git

[Felix Frank]

On 11/20/2014 05:07 PM, Jonathan Gazeley wrote:
> But how does that work when the GitLab server and Puppetmaster are
> different servers?

Well, do they need to be? ;-)

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5470F980.1060107%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Unable to install Puppet Master

[Felix Frank]

On 11/20/2014 05:25 PM, KB_puppet wrote:
> I've been trying to install Puppet on my Centos 6.5 system since
> yesterday but to no avail. At first I installed
> the |puppetmaster-passenger| but got a lot of errors during
> installation. I ended up purging it and today tried a fresh install of
> just the puppetmaster. There were no errors but I cannot see the
> puppet.conf or the site.pp file. They are not created during
> installation. 

That's fine. Neither is strictly required to operate the master.

> ubuntu:/$ sudo puppet master --verbose --no-daemonize
> Notice: Starting Puppet master version 3.7.3
> Error: Could not run: Could not create PID file:
> /var/lib/puppet/run/master.pid
 
Well *that* is strange. Can you add --debug and put the output on
Pastebin, Gist or a similar service?

The master should create all required directories on its own.

Thanks,
Felix

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5470FA66.3020106%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Agent fails; Could not retrieve local facts - but Manually runs successfully

[Felix Frank]

On 11/21/2014 12:30 AM, hendri wrote:
> This is on Amazon Linux on EC2 - Puppet Agent and master are at 2.7.25
>
> Manual runs of facter and puppet `puppet agent -t` complete
> successfully and produce no errors. how were if puppet runs either as
> service daemon or cron I get the above error in the log.
>
> Here is the error
>
> /var/log/messages
> Nov 17 21:47:36 servername puppet-agent[123]: Starting Puppet client
> version 2.7.25
> Nov 17 21:47:36 servername puppet-agent[123]: Could not run Puppet
> configuration client: *Could not retrieve local facts: private method
> `scan' called for nil:NilClass*

Hi,

sounds like an issue with the environment. Hard to solve without taking
a direct look at the system.

Can you run from cron with an added --trace option? That will produce a
somewhat more informative log message.

Thanks,
Felix

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5470FAE9.8020302%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Anyone made parser = future working on CentOS 6.5 & Ruby 1.8.x?

[Felix Frank]

On 11/21/2014 04:16 PM, Larry Liu wrote:
> Hi everyone,
>
> According to puppetlab's doc, parser=future is supposed to work with
> puppet version 3.5 or higher. I'm on 3.7.1 which falls under
> https://docs.puppetlabs.com/puppet/latest/reference/experiments_future.html,
> but it has not worked for me at all. Interestingly it works fine if I
> run just CLI puppet apply --parser=future xyz.pp. Once I enable it on
> my puppet masters, clients just keep getting 'Error: Could not
> retrieve catalog from remote server: Error 400 on SERVER: Could not
> parse for environment production: Do not add methods to model classes
> directly, add them to the ClassModule instead on node xx'. The
> ruby version on both masters and clients is ruby-1.8.7.352-13.el6.x86_64.
>
> Anyone know why?

The error is from rgen.

https://github.com/puppetlabs/puppet/blob/master/lib/puppet/vendor/rgen/lib/rgen/metamodel_builder.rb#L198

It is unclear how your master triggers this.

Can you reproduce the error using `puppet master --compile `?
If so, please add --trace and put the output somewhere for us to see.

Thanks,
Felix

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5470FC02.10204%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppetdoc readme markdown ignored

[Felix Frank]

Yes, and it is not clear from the post what part of Puppet is supposed
to honor the markdown formatting at the moment.

To the OP: Are you using `puppet doc`? Please note that the
documentation that you linked refers to documentation that is displayed
on the Forge only. The `puppet doc` face expects rdoc formatting.

HTH,
Felix

On 11/21/2014 04:33 PM, Spencer Krum wrote:
> For what it's worth, the community is trying to migrate to the puppet
> strings tool at this point.
>
> https://github.com/puppetlabs/puppetlabs-strings
>
>
> On Fri, Nov 21, 2014 at 2:52 PM, ubuntu811  > wrote:
>
> Hi
>
> I'm pretty new to puppet and trying to create the documentation
> for a newly created puppet module.
>
> How do I tell Puppet that the README File in the Project is in
> markdown language? Right now any markdown syntax as documented
> 
> inhttps://docs.puppetlabs.com/puppet/latest/reference/modules_documentation.html
> seems to get ignored. (As well if I name the thing README.md).
>
> I'm running Puppet 3.5.1.
>
> Regards,
> Mirjam
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5471009F.4050909%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Ensure "rows" in a mysql table

[Felix Frank]

On 11/22/2014 04:33 AM, Abhijeet Rastogi wrote:
> Hi everyone,
>
> I've this unique requirement where I have to manage "rows" in a
> database using puppet. Well, these rows actually represent "dns
> entries". (I'm using powerdns witih mysql
> http://doc.powerdns.com/html/generic-mypgsql-backends.html ).
>
> What do you guys thing is the right way to approach this? Below are
> the couple of things I can think of:-
>
> 1. First write various command line scripts like show_rows, add_rows &
> delete_rows. And then call "exec" with conditionals to alter these
> rows.
> 2. Write a custom type/resource which connects to mysql instance and
> does it's job.
>
> Although, second option is the most optimal way to do, it also
> requires more man hours. I would be happy to choose something that's
> already built and tested. Any ideas?
>
>

Yes, option 1 is likely more economic. Perhaps you can start from this:

http://serverfault.com/a/560568/216487

HTH,
Felix

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/547102A2.7010301%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] configure puppet master and puppet agent

[Felix Frank]

On 11/20/2014 03:26 AM, fauzi.profit...@gmail.com wrote:
> Hi, im very new using linux and I need to make connection between
> puppet master and puppet agent. I already success to make httpd port
> 8140 listen after that I continues to make a connection between puppet
> master and agent but failed. I cant send request from agent to master.
> Can someone here help me? Im using CentOS 5. I already attach the
> documentation that I followed. Thanks
>
Where did you obtain that documentation? No offence, but I would not put
too much faith into it.

Apparently you have configured the EL6/7 repo on your CentOS 5 machine.
This is likely a mistake.

Try this documentations:
https://docs.puppetlabs.com/guides/install_puppet/install_el.html

Make sure to choose the EL5 specific instructions.

HTH,
Felix

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/547105A1.9030509%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Planning dynamic environments with Git

[Spencer Krum]

A hook can use ssh to push. We set up a tool called puppetsync that would
be run on the puppetmaster, but would be triggered by post-recieve hook
over ssh from the git server.

On Sat, Nov 22, 2014 at 9:00 PM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:

> On 11/20/2014 05:07 PM, Jonathan Gazeley wrote:
> > But how does that work when the GitLab server and Puppetmaster are
> > different servers?
>
> Well, do they need to be? ;-)
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/5470F980.1060107%40Alumni.TU-Berlin.de
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Spencer Krum
(619)-980-7820

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CADt6FWNGHH0rvv61_%3DDMkXjVUHUepjxhBHmidkAZqrFyCeFtmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Anyone made parser = future working on CentOS 6.5 & Ruby 1.8.x?

[Larry Liu]

Hi Felix,

Here's the trace output.

Warning: ActiveRecord-based storeconfigs and inventory are deprecated. See 
http://links.puppetlabs.com/activerecord-deprecation
   (at 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/active_record.rb:12:in 
`initialize'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:334:in `new'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:334:in 
`make_terminus'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:129:in 
`terminus'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/store_configs.rb:6:in 
`initialize'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:334:in `new'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:334:in 
`make_terminus'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:129:in 
`terminus'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:48:in `cache'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:234:in 
`find_in_cache'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:193:in `find'; 
/usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:166:in `compile'; 
/usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:158:in 
`run_command'; /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:384:in 
`run'; /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:510:in 
`plugin_hook'; /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:384:in 
`run'; /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:488:in `exit_on_fail'; 
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:384:in `run'; 
/usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:146:in `run'; 
/usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:92:in `execute'; 
/usr/bin/puppet:8)
Warning: ActiveRecord-based storeconfigs and inventory are deprecated. See 
http://links.puppetlabs.com/activerecord-deprecation
   (at 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/facts/active_record.rb:13:in 
`initialize'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:334:in `new'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:334:in 
`make_terminus'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:129:in 
`terminus'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/store_configs.rb:6:in 
`initialize'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:334:in `new'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:334:in 
`make_terminus'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:129:in 
`terminus'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:48:in `cache'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:234:in 
`find_in_cache'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:193:in `find'; 
/usr/lib/ruby/site_ruby/1.8/puppet/node.rb:116:in `fact_merge'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/node/plain.rb:17:in `find'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:201:in `find'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/compiler.rb:111:in 
`find_node'; 
/usr/lib/ruby/site_ruby/1.8/puppet/util/profiler/around_profiler.rb:58:in 
`profile'; /usr/lib/ruby/site_ruby/1.8/puppet/util/profiler.rb:51:in 
`profile'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/compiler.rb:108:in 
`find_node'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/compiler.rb:147:in 
`node_from_request'; 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/compiler.rb:49:in 
`find'; /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:201:in 
`find'; /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:166:in 
`compile'; /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:158:in 
`run_command'; /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:384:in 
`run'; /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:510:in 
`plugin_hook'; /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:384:in 
`run'; /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:488:in `exit_on_fail'; 
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:384:in `run'; 
/usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:146:in `run'; 
/usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:92:in `execute'; 
/usr/bin/puppet:8)
Error: Could not parse for environment production: Do not add methods to 
model classes directly, add them to the ClassModule instead on node 
prod-opstest-fo2.xyz.com
/usr/lib/ruby/site_ruby/rgen/metamodel_builder.rb:198:in `method_added'
/usr/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/core_ext/module/aliasing.rb:33:in
 
`alias_method'
/usr/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/core_ext/module/aliasing.rb:33:in
 
`alias_method_chain'
/usr/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:116:in
 
`included'
/usr/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:114:in
 
`class_eval'
/usr/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/dep

[Puppet Users] Diagram of Puppet Agent/Master/DB communication (Was: Puppet variable with a custom fact)

[Wil Cooley]

>
>
> On Thursday, November 20, 2014 9:22:29 AM UTC-8, Wil Cooley wrote:
>>
>> (Aside: Does anyone have a link to a diagram of the dance the master and
>> agent do? I've been meaning to try to make one on websequencediagrams.com
>> but not gotten around to it.)
>>
>
jcbollinger wrote:

> There is a diagram and accompanying descriptive text that looks pretty
> comprehensive here:
> https://docs.puppetlabs.com/puppet/3/reference/subsystem_agent_master_comm.html
> .


On Fri, Nov 21, 2014 at 12:57 PM, Eric Sorenson <
eric.soren...@puppetlabs.com> wrote:
>
> I made one for the SSL bootstrapping sequence here:
> http://ask.puppetlabs.com/question/25/how-can-i-troubleshoot-problems-with-puppets-ssl-layer/
>
> And one for the agent/master communication which I haven't found a good
> place for on ask:
> https://dl.dropboxusercontent.com/u/18472980/puppet-agent-timeseq.png
>
>
Those all look good for what they are intended, but I was thinking more
about something that was simplified for newish users and included where the
various Ruby extensions are used.

Something like this:

http://preview.tinyurl.com/nezauat

I considered including the agent->master communication about File resources
using "source" but couldn't quite find a satisfactory way to represent it.

I realize now that I am unclear about whether the master submits the
compiled catalog and facts to PuppetDB at the time that the report is
submitted or earlier; its probably not a detail worth worrying about though.

Wil

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAMmm3r4%2BNYzV-vrubv8h1-fuH0rHpA2XWuLGWm8im3Bh6FudJA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.