[Puppet Users] PE VMware VM deployment (localization problem)
Hi Guys ! I'm currently evaluating Puppet's cloud provisioner on vmWARE. I think I just ran into a silly localisation problem : [root@puppet ~]# puppet node_vmware list notice: Connecting ... notice: Connected to myVcenter as Puppet (API version 4.1) notice: Finding all Virtual Machines ... (Started at 10:30:37 AM) notice: Control will be returned to you in 10 minutes at 10:40 AM if locating is unfinished. Locating: 100% |oo| Time: 00:00:00 notice: Complete /Centres de données/myCluster/vm/Modeles/Linux/mymodel powerstate: poweredOff [...] template: true puppet node_vmware create --name=deploy_puppet --template=/Centres de données/myCluster/vm/Modeles/Linux/mymodel err: The --template option must be a path, for example /Datacenters/Solutions/vm/templates/puppet_template. err: Try 'puppet help node_vmware create' for usage I think the french translation of vCenter is messing up with fog, anyone experiencing the same issue ? Regards, Benoit BARTHELEMY -- 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/-/s5bGi3N_gOoJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Converting puppet client to servr
On Wednesday, December 12, 2012 10:35:21 PM UTC, Bret Wortman wrote: Yeah, I was starting to think that was the solution. That's not strictly necessary, you can install a Puppet Master with Puppet just fine, the problem you're running into is how to manage the Puppet CA across multiple Masters. This is not an easy problem to solve. If you start a master for the first time it will initialise it's own personal CA and certificate. This will conflict with the cert it got from the *other* master when it was installed and probably the cause of your connectivity problems. Also, your other agents won't be able to jump between masters because the CAs are different. I would break the problem into these tasks: - Decide on a centralised CA (a Puppet Master Master even) that you can generate other Puppet Master certificates from and give that cert the 'puppet' alias if you use it at your sites (puppet ca generate woof.hostname.com --dns-alt-names puppet) - Figure out how to get this Cert and the Master CA onto your new Puppet Master instead of letting the Puppet Mater. NFS? HTTPS download? Package? - Figure out how to share certificates between Puppet Masters so an Agent can check in to different Puppet Masters. Centralised CA? Multi-way rsync? -Luke -- Bret Wortman http://bretwortman.com/ http://twitter.com/bretwortman On Wednesday, December 12, 2012 at 5:26 PM, Jakov Sosic wrote: On 12/12/2012 10:04 PM, Bret Wortman wrote: Is there an easy way to convert a puppet client into being a puppet master? Here's the scenario. I'm using puppet to configure all my systems, and would like it to be able to deploy a new puppet master as well. We have systems worldwide so having local puppet masters is very desirable for fault tolerance. So Kickstart (via cobbler) installs a puppet client during the initial system installation, then puppet installs everything else. And I've written a puppet-server module to attempt to deploy the puppet-server package, but I end up getting into certificate problems every time. The initial cert draws complaints, so I delete it and clean the certificate from the master, but then the systems will not connect under any circumstances: # puppet agent -t Exiting: no certificate found and waitforcert is disabled There's no request on the master (either this or the other). Thoughts? You should deploy master through cobbler, or run masterless puppet to set up the master. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet...@googlegroups.comjavascript: . To unsubscribe from this group, send email to puppet-users...@googlegroups.com javascript:. 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 view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/tQYBNKzPoQAJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] check if if file exists on client an master
Romain, I am confused.
In your first post you said you need to check if a package exists on the
Agent, the Puppet client.
Now below you say you need the check executed on the Master.
Facts are executed on the Agents and only ever on Agents. If you want to
check for something on a client/agent machine, you use a Fact, like the one
you posted below.
If you want to execute arbitrary code on the Master (during catalogue
compilation) probably the simplest thing you are after is the Generate
function:
http://docs.puppetlabs.com/references/latest/function.html#generate
On linux, I would use something that looks a bit like this:
class woof {
$file_exists = generate('/bin/test', '-f',
'/softw4pc/Misc/pfoleproxy/pfoleproxy*.txt')
if $file_exists {
...
}
}
There are other ways you can execute arbitrary code, like embedded Ruby
with the inline_template() function, pure Ruby manifests, or bury the code
somehow in a custom type and provider.
Does that help?
-Luke
On Thursday, December 13, 2012 6:46:07 AM UTC, Romain Gales wrote:
The facter should be executed on the server instead on the client.
On Thursday, December 13, 2012 1:29:23 AM UTC+1, Jakov Sosic wrote:
On 11/28/2012 09:46 PM, Romain Gales wrote:
there is what i tried:
# getpfoleproxyver.rb
#
Facter.add(:getpfoleproxyver) do
setcode do
Facter::Util::Resolution.exec('basename `ls
/softw4pc/Misc/pfoleproxy/pfoleproxy*.txt`')
end
end
the fact is working fine, but how to use this in my manifest?
i tried a lot but it was always empty?
$getpfoleproxyver should be correct, no?
Are you sure it's working on the client? You can see the value when you
type facter -p | grep getpfoleproxyver
?
--
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/-/zrpJgZzE8poJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet module restart puppet client or not?
On Thu, Dec 13, 2012 at 12:41 AM, Ugo Bellavance u...@lubik.ca wrote: I guess maybe I should ask to the Foreman group, but I was mostly wondering whether it was a good idea or not to restart puppet when changing puppet.conf. I think it would be a bad idea not to. Otherwise you've got a process running under a different configuration than what is on disk, so when it doesn't look like it's behaving like the config suggests it should, it can cause a lot of head-scratching! Note the advice in the thread at https://groups.google.com/d/msg/puppet-users/LViZFxc5ZAE/2yWRRixDoOQJ though, about how to get puppet to successfully restart the agent! Regards, Matt. -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet with dedicated ruby install
Hi There, We take this approach as well with our platform to ensure that puppet upgrades don't affect any applications that may be using the OS version of Ruby. Disclaimer: I don't actually love our approach to packaging Ruby and am aware of its flaws, however it has proved to be OK for the time being until I can fully review it. (ie, should I be moving to an RPM per gem as per EPEL and Puppet Enterprise do, etc , etc ?) Quick overview of what we do: 1. Build your Ruby from source, using a unique location for its prefix ie, /opt/ruby-1.8.7/ 2. Build and install the rubygems framework into this install 3. Using gems, install all your required gems into the ruby installation, don't forget that a number of them require additional libraries and packages to function, ie Augeas 4. Package this software into an RPM - Dont forget to add requires for the additional dependencies you need , as well as document all the gems you added and what they are for so you can repeat this process on other platforms, ie RHEL4/5/6 5. Grab the puppet and facter source - These ship with SPEC files to aid in building them, you just need to modify the ruby path they reference, and all should be OK. Don't forget to add the dependencies for this package against your own ruby packages so they install nice via YUM or similar. 6. Test lots of times, then deploy. Maintainence wise, if we need to add / change functionality, we install the package on a clean dev host, make the changes and re-package into a new revision of that package. We repeat this procedure for all the other OS versions of ruby so they are identical feature wise. I have found the rubygems_snapshot gem/tool is quite useful for this kind of task. Like I said, our approach is not perfect, but it works for now until I can clean it up and hopefully automate the lot with Jenkins. I hope this is of some use. Cheers, K On Wednesday, December 12, 2012 8:54:56 PM UTC, Alexander Philipp wrote: Are there any good guides out there to using Puppet agents with a dedicated, separate ruby install? Our apps are all Ruby based and require different versions than Puppet. Installing the agent from a package will override our ruby installs. -- 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/-/gGsL2feZ90oJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] issues with puppet 3.0.1 using ruby 1.9.3 and passenger (3.0.18)
Hi Josh,
I installed puppet-server using yum by installing the rpm from puppetlabs
that enables the puppet repo. I then installed rubygems which enabled me to
gem install rack and passenger.
I did compile ruby1.9.3 using this method:
This installs libyaml 0.1.4
cd /opt
wget http://pyyaml.org/download/libyaml/yaml-0.1.4.tar.gz
tar xzvf yaml-0.1.4.tar.gz
cd yaml-0.1.4
./configure --prefix=/usr/local
make
make install
This installs ruby 1.9.3.0d
cd /opt
wget http://ftp.ruby-lang.org/pub/ruby/1.9/ruby-1.9.3-p0.tar.gz
tar xzvf ruby-1.9.3-p0.tar.gz
cd ruby-1.9.3-p0
./configure --enable-shared --disable-pthread
make
make install
I run this as part of the setup
cp /usr/share/puppet/ext/rack/files/config.ru /etc/puppet/rack/
Currently I am using ruby 1.8.7 which works fine but in the config.ru i see
this
# if puppet is not in your RUBYLIB:
# $LOAD_PATH.unshift('/opt/puppet/lib')
If I were to use 1.9.3, would I have to update this to the correct ruby
path for 1.9.3? Is that what you are suggesting will fix this?
I dead keen on running ruby 1.9.3 as this is a new implementation so would
like to get to that version rather than have to upgrade at a later date
Cheers,
Oli
On Wed, Dec 12, 2012 at 4:02 AM, vioilly olive...@gmail.com javascript:
wrote:
I have installed puppet 3.0.1,
Installed as a gem or native package?
It appears to me that this is a PATH issue. Does anyone know how to fix
this?
In your puppet config.ru, can you verify that puppet's lib directory
is in the $LOAD_PATH? Also note the line at the top of that file.
As far as why it works on 1.8.7, but not 1.9.3, makes me think that
puppet is installed as a gem, and that there are rubygem differences
between the two rubies.
--
Josh Cooper
Developer, Puppet Labs
--
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/-/zp6Xzi9hUIwJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] could not find user when running as daemon
On Wednesday, December 12, 2012 4:44:54 PM UTC-6, Jeff Goldschrafe wrote: Sorry to be a thread-necromancer, but we're seeing the same problem on a tiny subset of our hosts. We saw the problem on a CentOS 5 x86_64 host, then it mysteriously went away, and now we're consistently seeing it on a CentOS 5 i386 host. As with pattryn, the resource applies successfully when run from the command line with *puppet apply*, but does not when Puppet is running with *puppet agent -t*. SELinux is in permissive mode. Things work fine when nscd is running, but like many CentOS 5 users, we'll never touch that thing in production. We saw this behavior originally on the 2.7 client, upgraded to the 3.0 client, and are still seeing the issue. Anyone have any ideas? Did you ever have nscd running on the affected system? Nscd is rather deeply integrated with the C library, such that depending on how it is configured, you may need to restart the system after disabling or reconfiguring it. 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/-/S94HvklusW0J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet with dedicated ruby install
On Wednesday, December 12, 2012 2:54:56 PM UTC-6, Alexander Philipp wrote: Are there any good guides out there to using Puppet agents with a dedicated, separate ruby install? Our apps are all Ruby based and require different versions than Puppet. Installing the agent from a package will override our ruby installs. Have you considered a dedicated puppetmaster instead? Especially if your apps are outward-facing, it would be good practice anyway to separate them as much as possible from your infrastructure services, such as Puppet. 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/-/CNT93IVh2UMJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: PE VMware VM deployment (localization problem)
On Thursday, December 13, 2012 3:36:52 AM UTC-6, Benoit BARTHELEMY wrote: Hi Guys ! I'm currently evaluating Puppet's cloud provisioner on vmWARE. I think I just ran into a silly localisation problem : [root@puppet ~]# puppet node_vmware list notice: Connecting ... notice: Connected to myVcenter as Puppet (API version 4.1) notice: Finding all Virtual Machines ... (Started at 10:30:37 AM) notice: Control will be returned to you in 10 minutes at 10:40 AM if locating is unfinished. Locating: 100% |oo| Time: 00:00:00 notice: Complete /Centres de données/myCluster/vm/Modeles/Linux/mymodel powerstate: poweredOff [...] template: true puppet node_vmware create --name=deploy_puppet --template=/Centres de données/myCluster/vm/Modeles/Linux/mymodel err: The --template option must be a path, for example /Datacenters/Solutions/vm/templates/puppet_template. err: Try 'puppet help node_vmware create' for usage I think the french translation of vCenter is messing up with fog, anyone experiencing the same issue ? I am not experiencing the issue, but it is plausible that the 'é' in the path is confusing Puppet. Actually, it's more likely to be confusing the underlying Ruby, as Ruby had pretty lackluster support for varying character sets until version 1.9. Even if you're running on 1.9, I'm not sure how well Puppet uses the better character set support it provides. Also plausible, albeit less likely, is that the spaces in the path need to be shell-escaped (/Centres\\ de\\ données/myCluster/...). You could try creating a symlink that bypasses the troublesome path component, and expressing the template in terms of the link. Any way around, I hope you will file a ticket. 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/-/1btpl4MlN0kJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: variables created with generate() function have a newline when used in a template
This works when using the variable inside a template. But I want to use the variable in an Exec command. How to remove the newline here? .chomp does not seem to work here. THanks On Sunday, December 26, 2010 1:43:26 PM UTC+1, bowlby wrote: Thanks, both of you! That solved it. Merry Christmas (for what's left of it...) On Dec 26, 12:54 pm, Daniel Pittman dan...@rimspace.net wrote: On Sun, Dec 26, 2010 at 22:45, bowlby bramenn...@gmail.com wrote: I have this in nodes.pp $puppetmaster_fqdn = generate(/usr/bin/facter,fqdn) and this in a template http://%= puppetmaster_fqdn %:8080 When puppet runs, this is the result: http://puppet.home :8080 Anybody any clue to whats causing this? I've tried -% I suspect that -% only eats whitespace outside the bracket, not inside. Anyhow, you can make this do the right thing using a tiny bit of ruby: %= puppetmaster_fqdn.chomp % Regards, Daniel -- ✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155 707 ♽ made with 100 percent post-consumer electrons -- 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/-/AECI05CiIRYJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] check if if file exists on client an master
Hi,
I malformed my question.
This is a hint in the right direction.
Romain
On Thursday, 13 December 2012 11:26:20 UTC+1, Luke Bigum wrote:
Romain, I am confused.
In your first post you said you need to check if a package exists on the
Agent, the Puppet client.
Now below you say you need the check executed on the Master.
Facts are executed on the Agents and only ever on Agents. If you want to
check for something on a client/agent machine, you use a Fact, like the one
you posted below.
If you want to execute arbitrary code on the Master (during catalogue
compilation) probably the simplest thing you are after is the Generate
function:
http://docs.puppetlabs.com/references/latest/function.html#generate
On linux, I would use something that looks a bit like this:
class woof {
$file_exists = generate('/bin/test', '-f',
'/softw4pc/Misc/pfoleproxy/pfoleproxy*.txt')
if $file_exists {
...
}
}
There are other ways you can execute arbitrary code, like embedded Ruby
with the inline_template() function, pure Ruby manifests, or bury the code
somehow in a custom type and provider.
Does that help?
-Luke
On Thursday, December 13, 2012 6:46:07 AM UTC, Romain Gales wrote:
The facter should be executed on the server instead on the client.
On Thursday, December 13, 2012 1:29:23 AM UTC+1, Jakov Sosic wrote:
On 11/28/2012 09:46 PM, Romain Gales wrote:
there is what i tried:
# getpfoleproxyver.rb
#
Facter.add(:getpfoleproxyver) do
setcode do
Facter::Util::Resolution.exec('basename `ls
/softw4pc/Misc/pfoleproxy/pfoleproxy*.txt`')
end
end
the fact is working fine, but how to use this in my manifest?
i tried a lot but it was always empty?
$getpfoleproxyver should be correct, no?
Are you sure it's working on the client? You can see the value when you
type facter -p | grep getpfoleproxyver
?
--
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/-/au5MT1bWYxcJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: bootstrap aws instance - set server address in instance puppet.conf?
Having the same problem as quoted below. I'm even using autosign for the time-being while trying to solve this. Leej, did you solve this? notice: Waiting for SSH response ... Done notice: Installing Puppet ... notice: Puppet is now installed on: blahblah.eu-west-1.compute.amazonaws.com notice: No classification method selected notice: Signing certificate ... err: Signing certificate ... Failed err: Signing certificate error: Could not render to pson: The certificate retrieved from the master does not match the agent's private key. -- 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/-/zywDZNncfDoJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] err: Signing certificate error
Your problem is that you are not propogating the RUBYLIB environment variable (for the cloud provisioner) when you run sudo as you are. Use: sudo RUBYLIB=$RUBYLIB puppet node_aws ... On Monday, October 1, 2012 2:00:48 AM UTC-4, Ignasi López wrote: 2.7.19 It's weird but, i can use puppet without sudo, in fact, the initial problem appears without sudo. If i try run puppet as a root in order to sign, list o revoke certificates there aren't any problem. But if i try run puppet to launch an instance with root, i get the last error... On Monday, October 1, 2012 12:37:50 AM UTC+2, Clarence Beeks wrote: On Sun, Sep 30, 2012 at 2:22 PM, Ignasi López ignasi...@mmip.es wrote: in fact i can't use puppet as a root: *sudo puppet help* *err: no such file to load -- puppet/face/node/install* *err: Try 'puppet help help help' for usage* First step is seeing if puppet will run for you. Puppet runs as root or you need to sudo and run it. What version of puppet are you running? -- 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/-/lSPlgiA7U4gJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Strange signing problem in AWS - stumped
I have even gone so far on the master as to completely uninstall the puppetmaster package, sudo rm -rf /var/lib/puppet/ssl, and reinstall the puppetmaster package on the master. Then provision a brand new EC2 instance with puppet node_aws bootstrap... Same result: The certificate retrieved from the master does not match the agent's private key. -- 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/-/nkShZrC8QR4J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Is it able to obtain performance metrics from puppet master?
Hello Is it able to obtain performance metrics from puppet master ( or puppet dashboard ) ? I intend to use this metrics in external monitoring system. Of particular interest are the following metrics: * list of agents * time since the certain agent last apply manifest ( to find stuck agents ) * time used to compile manifest by puppet master for the certain agent * time used by the certain agent to apply manifest P.S. sorry for my english, it is not my native language -- 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/-/vcbg7SIFH7oJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Converting puppet client to servr
Which files will I need to transfer to the new puppet master? /var/lib/puppet/ssl/ca/ca_crt.pem /var/lib/puppet/ssl/certs/ca.pem /var/lib/puppet/ssl/certs/woof.hostname.com.pem We had been planning for a central master master anyway and it already has a dns alias for puppet. Once I solve the distribution problem, I'll take on keeping these boxes in sync. * * * Bret Wortman*** http://bretwortman.com/ http://twitter.com/BretWortman On Thu, Dec 13, 2012 at 5:15 AM, Luke Bigum luke.bi...@lmax.com wrote: On Wednesday, December 12, 2012 10:35:21 PM UTC, Bret Wortman wrote: Yeah, I was starting to think that was the solution. That's not strictly necessary, you can install a Puppet Master with Puppet just fine, the problem you're running into is how to manage the Puppet CA across multiple Masters. This is not an easy problem to solve. If you start a master for the first time it will initialise it's own personal CA and certificate. This will conflict with the cert it got from the *other* master when it was installed and probably the cause of your connectivity problems. Also, your other agents won't be able to jump between masters because the CAs are different. I would break the problem into these tasks: - Decide on a centralised CA (a Puppet Master Master even) that you can generate other Puppet Master certificates from and give that cert the 'puppet' alias if you use it at your sites (puppet ca generate woof.hostname.com --dns-alt-names puppet) - Figure out how to get this Cert and the Master CA onto your new Puppet Master instead of letting the Puppet Mater. NFS? HTTPS download? Package? - Figure out how to share certificates between Puppet Masters so an Agent can check in to different Puppet Masters. Centralised CA? Multi-way rsync? -Luke -- Bret Wortman http://bretwortman.com/ http://twitter.com/bretwortman On Wednesday, December 12, 2012 at 5:26 PM, Jakov Sosic wrote: On 12/12/2012 10:04 PM, Bret Wortman wrote: Is there an easy way to convert a puppet client into being a puppet master? Here's the scenario. I'm using puppet to configure all my systems, and would like it to be able to deploy a new puppet master as well. We have systems worldwide so having local puppet masters is very desirable for fault tolerance. So Kickstart (via cobbler) installs a puppet client during the initial system installation, then puppet installs everything else. And I've written a puppet-server module to attempt to deploy the puppet-server package, but I end up getting into certificate problems every time. The initial cert draws complaints, so I delete it and clean the certificate from the master, but then the systems will not connect under any circumstances: # puppet agent -t Exiting: no certificate found and waitforcert is disabled There's no request on the master (either this or the other). Thoughts? You should deploy master through cobbler, or run masterless puppet to set up the master. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet...@googlegroups.com. To unsubscribe from this group, send email to puppet-users...@** googlegroups.com. For more options, visit this group at http://groups.google.com/** group/puppet-users?hl=enhttp://groups.google.com/group/puppet-users?hl=en . -- 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/-/tQYBNKzPoQAJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] help with scoping variable into a template
On 10/29/2012 09:11 PM, mparrad wrote:
Hi guys,
I'm working on puppet for windows, and now I have to work on a template
that use the value from a variable set it on a class, the problem that i
got is always I got undef value on the result file.
I checked this URL without no results
http://stackoverflow.com/questions/10589404/puppet-cant-find-variable-for-template
These are my classes variables:
class direct::config () {
require direct::setup
$nameSite = 'some.site.com'
..
}
and this where I use it on my template locate on
direct/templates/conf/css.erb:
.
DomainIP %= @ipaddress %,127.0.0.1
DefServerName %= scope.lookupvar(direct::config::nameSite) %
.
.
And the file results css.cfg:
.
DomainIP 10.10.10.23,127.0.0.1
DefServerName undefined
.
.
I expected DefServerName some.site.com
Could you help me with this issue? What Am I doing wrong?
Do you have direct::config included in your host manifest anywhere? Also
could you paste part of the code (including the wrapper class) that
defines file which uses template css.erb?
--
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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] in-module data with hiera
The good news: Without /etc/puppet/hiera.yaml Without module/data/hiera.yaml = OK! Without /etc/puppet/hiera.yaml but with empty module/data/hiera.yaml = OK! Without /etc/puppet/hiera.yaml but with module/data/hiera.yaml with a hierarchy = OK! With empty /etc/puppet/hiera.yaml Without module/data/hiera.yaml = OK! With /etc/puppet/hiera.yaml with a hierarch Without module/data/hiera.yaml = OK! With /etc/puppet/hiera.yaml with a hierarch with empty module/data/hiera.yaml = OK! With /etc/puppet/hiera.yaml with a hierarch with module/data/hiera.yaml with a hierarchy = OK! Lookups via hiera() in a define also seem to work well! Comment: The default file looked up in the in-module data backend is 'default.yaml', not 'common.yaml' and that is different from the yaml backend so it is somewhat confusing. It is also not what was 'agreed' in this thread. All this is based on a simple test with a module with one class and one define so it is not very in-depth but the results are clear and as expected Thank you Volcane ! We're getting there. :-) Regards, Stefan - Zipkid - Goethals. On 12 Dec 2012, at 17:05, R.I.Pienaar r...@devco.net wrote: - Original Message - From: Jakov Sosic jso...@srce.hr To: puppet-users@googlegroups.com Sent: Wednesday, December 5, 2012 11:15:57 PM Subject: Re: [Puppet Users] Re: in-module data with hiera On 12/05/2012 09:45 PM, Stefan Goethals wrote: Not having any problem with osfamily i agree with John. A default to 'common' would suffice i believe. Agree, common is more than enough as default. I've updated my pull request[1] with this feedback and the bugs Zipkid reported, any testers and more feedback welcome [1] https://github.com/puppetlabs/puppet/pull/1217 -- 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+unsubscr...@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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] in-module data with hiera
- Original Message - From: Stefan Goethals zipkid@gmail.com To: puppet-users@googlegroups.com Sent: Thursday, December 13, 2012 5:37:30 PM Subject: Re: [Puppet Users] in-module data with hiera The good news: Without /etc/puppet/hiera.yaml Without module/data/hiera.yaml = OK! Without /etc/puppet/hiera.yaml but with empty module/data/hiera.yaml = OK! Without /etc/puppet/hiera.yaml but with module/data/hiera.yaml with a hierarchy = OK! With empty /etc/puppet/hiera.yaml Without module/data/hiera.yaml = OK! With /etc/puppet/hiera.yaml with a hierarch Without module/data/hiera.yaml = OK! With /etc/puppet/hiera.yaml with a hierarch with empty module/data/hiera.yaml = OK! With /etc/puppet/hiera.yaml with a hierarch with module/data/hiera.yaml with a hierarchy = OK! Lookups via hiera() in a define also seem to work well! Comment: The default file looked up in the in-module data backend is 'default.yaml', not 'common.yaml' and that is different from the yaml backend so it is somewhat confusing. It is also not what was 'agreed' in this thread. yes good, actually common is a default set by hiera, this should be consistant here too, I agree will fix. https://github.com/puppetlabs/hiera/blob/master/lib/hiera/config.rb#L13-14 All this is based on a simple test with a module with one class and one define so it is not very in-depth but the results are clear and as expected Thank you Volcane ! We're getting there. :-) no thank you, community members testing this stuff is super awesome and help us a lot. -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Unit-Testing/test: recommended method?
Hi, is there any officially recommended default/standard method to realize Puppet module unit test beyond linting (puppet-lint)? Compatibility to version 3.x is nice but NOT needed. My main questions are: 1) I know there are different, well-known methods: - Test::Unit - rspec-puppet - cucumber-puppet Is there anything missing worth a look? Which are deprecated, wich are future-proof? 2) There are helpful blog postings and articles out there [1] [2] [3] [4]. However, none of them gives me a clue if there is a commonly recommended tool/method to implement Unit test, some kind of use X because everybody is using it, you won't get compatibility issues and the dev-community behind is healthy. A hint out of e.g. Puppet Labs or experienced community members Point-of-View would be very helpful. Are there any recommendations? Getting familiar with testing needs some work which I don't want to invest into the wrong candidate/method/tools. ;-) [1] http://puppetlabs.com/blog/testing-modules-in-the-puppet-forge/ [2] http://bombasticmonkey.com/2012/03/02/automatically-test-your-puppet-modules-with-travis-ci/ [3] http://puppetlabs.com/blog/testing-modules-in-the-puppet-forge/ [4] http://projects.puppetlabs.com/projects/puppet/wiki/Development_Writing_Tests -- Andreas http://blog.andreas-haerter.com signature.asc Description: OpenPGP digital signature
Re: [Puppet Users] Unit-Testing/test: recommended method?
On Thu, Dec 13, 2012 at 11:01 AM, Andreas Haerter list+puppet-us...@mail-node.com wrote: Hi, is there any officially recommended default/standard method to realize Puppet module unit test beyond linting (puppet-lint)? Compatibility to version 3.x is nice but NOT needed. My main questions are: 1) I know there are different, well-known methods: - Test::Unit - rspec-puppet - cucumber-puppet Is there anything missing worth a look? Which are deprecated, wich are future-proof? Not aware of Test::Unit. Cucumber Puppet is deprecated [1]. rspec-puppet is the way to go. 2) There are helpful blog postings and articles out there [1] [2] [3] [4]. However, none of them gives me a clue if there is a commonly recommended tool/method to implement Unit test, some kind of use X because everybody is using it, you won't get compatibility issues and the dev-community behind is healthy. A hint out of e.g. Puppet Labs or experienced community members Point-of-View would be very helpful. Are there any recommendations? Getting familiar with testing needs some work which I don't want to invest into the wrong candidate/method/tools. ;-) The blog posts you referenced are slightly out of date. I would start with Branan's post on Puppet Labs spec_helper [2]. It's used in all puppet labs modules. You can see it in action both in travis-ci [3] and puppet labs public Jenkins CI [4]. [1] https://github.com/nistude/cucumber-puppet#readme [2] http://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing/ [3] https://travis-ci.org/puppetlabs/puppetlabs-openstack/builds/3551120 [4] https://jenkins.puppetlabs.com/view/Puppet%20Modules/ Thanks, Nan -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] PE VMware VM deployment (localization problem)
On Thu, Dec 13, 2012 at 11:36 AM, Benoit BARTHELEMY benoit.barthel...@gmail.com wrote: Hi Guys ! I'm currently evaluating Puppet's cloud provisioner on vmWARE. I think I just ran into a silly localisation problem : [root@puppet ~]# puppet node_vmware list notice: Connecting ... notice: Connected to myVcenter as Puppet (API version 4.1) notice: Finding all Virtual Machines ... (Started at 10:30:37 AM) notice: Control will be returned to you in 10 minutes at 10:40 AM if locating is unfinished. Locating: 100% |oo| Time: 00:00:00 notice: Complete /Centres de données/myCluster/vm/Modeles/Linux/mymodel powerstate: poweredOff [...] template: true puppet node_vmware create --name=deploy_puppet --template=/Centres de données/myCluster/vm/Modeles/Linux/mymodel err: The --template option must be a path, for example /Datacenters/Solutions/vm/templates/puppet_template. err: Try 'puppet help node_vmware create' for usage I think the french translation of vCenter is messing up with fog, anyone experiencing the same issue ? yes, thats true, sadly fog does not support vcenter in a non English setup. Regards, Benoit BARTHELEMY -- 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/-/s5bGi3N_gOoJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] in-module data with hiera
- Original Message - From: R.I.Pienaar r...@devco.net To: puppet-users@googlegroups.com Sent: Thursday, December 13, 2012 5:58:42 PM Subject: Re: [Puppet Users] in-module data with hiera - Original Message - From: Stefan Goethals zipkid@gmail.com To: puppet-users@googlegroups.com Sent: Thursday, December 13, 2012 5:37:30 PM Subject: Re: [Puppet Users] in-module data with hiera The good news: Without /etc/puppet/hiera.yaml Without module/data/hiera.yaml = OK! Without /etc/puppet/hiera.yaml but with empty module/data/hiera.yaml = OK! Without /etc/puppet/hiera.yaml but with module/data/hiera.yaml with a hierarchy = OK! With empty /etc/puppet/hiera.yaml Without module/data/hiera.yaml = OK! With /etc/puppet/hiera.yaml with a hierarch Without module/data/hiera.yaml = OK! With /etc/puppet/hiera.yaml with a hierarch with empty module/data/hiera.yaml = OK! With /etc/puppet/hiera.yaml with a hierarch with module/data/hiera.yaml with a hierarchy = OK! Lookups via hiera() in a define also seem to work well! Comment: The default file looked up in the in-module data backend is 'default.yaml', not 'common.yaml' and that is different from the yaml backend so it is somewhat confusing. It is also not what was 'agreed' in this thread. yes good, actually common is a default set by hiera, this should be consistant here too, I agree will fix. https://github.com/puppetlabs/hiera/blob/master/lib/hiera/config.rb#L13-14 yay, confused myself - this is of course in the backend too, doh. I updated the pull with this fix, thanks again. -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: puppet dashboard inventory
Just trying to get help here.
My puppetdb server is called puppet-server3. My dashboard server is
puppet-server2. I can run inventory commands against my puppetdb and get
results.
For example - i have a puppet-client2.test.net machine running the puppet
agent
[root@puppet-server3 ~]# curl -H Accept: application/json
'http://localhost:8080/status/nodes/puppet-client2.test.net'
{
name : puppet-client2.test.net,
deactivated : null,
catalog_timestamp : 2012-12-13T17:55:28.704Z,
facts_timestamp : 2012-12-13T17:55:28.534Z
So that tells me the puppetdb is holding facts about my puppet agent
For the dashboard, what inventory server do I specify in settings.yml? It
is the puppetdb server (puppet-server3.test.net)
# Hostname of the inventory server.
inventory_server: 'puppet-server3.test.net'
# Port for the inventory server.
inventory_port: 8081
Do I need to set up SSL certs between the dashboard server and the puppetdb
server?
Any help would be appreciated
Cheers,
Oli
--
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/-/QAfTY4yJgb0J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Unit-Testing/test: recommended method?
Hi! On Thu, Dec 13, 2012 at 11:42:19AM -0800, Nan Liu wrote: On Thu, Dec 13, 2012 at 11:01 AM, Andreas Haerter list+puppet-us...@mail-node.com wrote: 1) I know there are different, well-known methods: - Test::Unit - rspec-puppet - cucumber-puppet Is there anything missing worth a look? Which are deprecated, wich are future-proof? Not aware of Test::Unit. Cucumber Puppet is deprecated. rspec-puppet is the way to go. rspec-puppet is great for testing an isolated module. For testing a complete machine or all of the catalog, I very much prefer cucumber-puppet. That's why I forked the repo and develop it further [1]. ruby 1.9 and puppet 3 are supported by my fork. If you use Puppet 2.7 and Ruby 1.8, I recommend the official gem. If you have puppet 3, the you could give my fork a try. Up until now, it's just a few fixes, I haven't had the time to integrate them into the bigger picture with backwards compatibility and so on. I have puppet-lint and cucumber-puppet integrated into my Jenkins-setup. Cheers, Matthias Viehweger [1] https://github.com/kronn/cucumber-puppet -- Serververwaltung und Softwareentwicklung https://www.heute-kaufen.de Prinzessinnenstraße 20 - 10969 Berlin signature.asc Description: Digital signature
Re: [Puppet Users] Re: puppet dashboard inventory
On Dec 13, 2012, at 4:09 PM, vioilly wrote:
Just trying to get help here.
My puppetdb server is called puppet-server3. My dashboard server is
puppet-server2. I can run inventory commands against my puppetdb and get
results.
For example - i have a puppet-client2.test.net machine running the puppet
agent
[root@puppet-server3 ~]# curl -H Accept: application/json
'http://localhost:8080/status/nodes/puppet-client2.test.net'
{
name : puppet-client2.test.net,
deactivated : null,
catalog_timestamp : 2012-12-13T17:55:28.704Z,
facts_timestamp : 2012-12-13T17:55:28.534Z
So that tells me the puppetdb is holding facts about my puppet agent
For the dashboard, what inventory server do I specify in settings.yml? It is
the puppetdb server (puppet-server3.test.net)
# Hostname of the inventory server.
inventory_server: 'puppet-server3.test.net'
# Port for the inventory server.
inventory_port: 8081
Do I need to set up SSL certs between the dashboard server and the puppetdb
server?
Any help would be appreciated
Cheers,
Oli
You do not need to make any changes to your dashboard server. Instead, you need
to modify two files and add one file to your puppet master. See step 2 on this
page for the details:
http://docs.puppetlabs.com/puppetdb/1/connect_puppet_master.html#step-2-edit-config-files
--
Peter
--
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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: puppet dashboard inventory
Correction to the above post Also puppetdb.conf [master] storeconfigs = true storeconfigs_backend = puppetdb should be [main] server = puppet-server3.test.net port = 8081 -- 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/-/AzA2bKtVECQJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] puppet dashboard 1.2.15-rc1 report search problem
On a fresh Dashboard installation I get these:
Puppet Dashboard encountered an error.
Something went wrong, and Puppet Dashboard was unable to render the
requested page. Please contact your site’s help desk or systems
administrator; if that happens to be you, please check Dashboard’s logs for
more information.
Processing ReportsController#search (for 93.38.53.173 at 2012-12-13
23:55:51) [GET]
Parameters: {controller=reports, action=search}
Rendering template within layouts/application
Rendering reports/search
ActionView::TemplateError (undefined local variable or method `errors' for
#ActionView::Base:0x7fc3aef36848) on line #9 of
app/views/reports/search.html.haml:
6: Search Latest Inspect Reports
7:
8: .item
9: - if errors.present?
10: %div{:class = section error}
11: %h3 Errors
12: - errors.each do |messages|
app/views/reports/search.html.haml:9:in
`_run_haml_app47views47reports47search46html46haml'
haml (3.1.2) [v] rails/./lib/haml/helpers/action_view_mods.rb:13:in
`render'
haml (3.1.2) [v] rails/./lib/haml/helpers/action_view_mods.rb:13:in
`render'
sass (3.1.2) [v] rails/./lib/sass/plugin/rack.rb:54:in `call'
/usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
/usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
/usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
/usr/lib/ruby/1.8/webrick/server.rb:162:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
/usr/lib/ruby/1.8/webrick/server.rb:95:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:92:in `each'
/usr/lib/ruby/1.8/webrick/server.rb:92:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:23:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:82:in `start'
Rendering /usr/share/puppet-dashboard/public/500.html (500 Internal Server
Error)
Any idea on what could be the problem?
Thanks
Luca
--
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/-/u9bg24moPsMJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Solaris Packages for Puppet 3.0.0-rc7, Facter 1.6.0 and Hiera 1.0.0
Do you have packages for Solaris 10 as well? Thanks! On Friday, September 21, 2012 8:11:39 PM UTC-4, Moses Mendoza wrote: -- Forwarded message -- From: Rahul Gopinath ra...@puppetlabs.com javascript: Date: Fri, Sep 21, 2012 at 4:43 PM Subject: [Puppet-dev] Solaris Packages for Puppet 3.0.0, Facter 1.6.0 and Hiera 1.0.0 To: puppet...@googlegroups.com javascript:, puppe...@googlegroups.comjavascript: Hello, For the first time, experimental Solaris 11 IPS packages for Puppet 3.0.0-rc7, Facter 1.6.12 and Hiera 1.0.0 are available under http://downloads.puppetlabs.com/solaris They are: puppet@3.0.0,5.11-9211.p5p facter@1.6.12,5.11-819.p5p hiera@1.0.0,5.11-116.p5p The versioning scheme for Solaris is different from the default scheme. The versioning scheme is product@product-version,consolidation-build number . Specifically the RC candidates and the Final version are distinguished only by their build number which is monotonic. To install these packages, download them from the above link and use IPS pkg command. E.g for puppet pkg install -g ./puppet@3.0.0,5.11-9211.p5p puppet Note that since this is experimental and each product is in its own repository archive, Hiera and Factor need to be installed first before Puppet is installed. To Solaris users, we would greatly appreciate your feedback on these packages. We are also in the process of setting up public IPS repositories and will update you as we make progress. Rahul -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To post to this group, send email to puppe...@googlegroups.comjavascript:. To unsubscribe from this group, send email to puppet-dev+...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en. -- 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/-/mYNiHg8yadAJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Is it able to obtain performance metrics from puppet master?
most of these are available in the reports, have a look in he reportdir (puppet master --configprint reportdir). You can also write a report processor to feed them directly into your monitoring system. On 13 December 2012 18:09, Oleg Korchagin madrou...@gmail.com wrote: Hello Is it able to obtain performance metrics from puppet master ( or puppet dashboard ) ? I intend to use this metrics in external monitoring system. Of particular interest are the following metrics: * list of agents * time since the certain agent last apply manifest ( to find stuck agents ) * time used to compile manifest by puppet master for the certain agent * time used by the certain agent to apply manifest P.S. sorry for my english, it is not my native language -- 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/-/vcbg7SIFH7oJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Erik Dalén -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet module restart puppet client or not?
On Thursday, December 13, 2012 5:43:14 AM UTC-5, Matthew Burgess wrote: On Thu, Dec 13, 2012 at 12:41 AM, Ugo Bellavance ug...@lubik.cajavascript: wrote: I guess maybe I should ask to the Foreman group, but I was mostly wondering whether it was a good idea or not to restart puppet when changing puppet.conf. I think it would be a bad idea not to. Otherwise you've got a process running under a different configuration than what is on disk, so when it doesn't look like it's behaving like the config suggests it should, it can cause a lot of head-scratching! That rises two questions in my mind: 1. In my understanding, puppetmaster catches any changes in the manifests without needing a restart, why can't the puppet client reload its puppet.conf parameters at the next run? 2. Why puppet can't use the reload option of most current daemons' init scripts? I think there should be a parameter hasreload, similar to hasrestart, saying that the init script supports the use of the reload argument. This would avoid this kind of problem, and people wouldn't have to redefine the restart command. Ugo -- 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/-/Vi0T1D5_sfwJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet 3.0 Puppet labs repo package problem on rhel5
On 11/28/2012 05:58 PM, Jeff McCune wrote: Jakov, I'm really sorry to step in on this one but our ruby should fully support gems installed using the gem command. I understand it's not ideal and that RPM's are definitely preferable. I encourage people to use RPMs whenever possible in this situation. However, I'm deeply concerned that we may be replacing the system ruby, which does support gem install, with something that does not. To this end, I'd like to clarify that if you run into this problem and you're using gem install instead of yum, and we find out there's a bug here, then this issue should also be resolved for you and your deployment scenario. Please keep troubleshooting the issue even if you're using gems and not RPMs. Let me clarify myself - I don't even try to suggest that ruby provided by puppetlabs for el5 does not support 'gem install', I'm only strongly advising against it - no matter if it's RedHat's ruby package in questions or PuppetLabs one. IMHO it's a really bad practice to mix different packaging systems and that practice will byte you, sooner or later. -- Jakov Sosic www.srce.unizg.hr -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet and Mcollective yaml file changing when it shouldn't
Has anyone else ran into this?
debug: /Stage[main]/Mcollective/File[/var/tmp/facts.yaml]/content:
Executing 'diff -u /var/tmp/facts.yaml
/tmp/puppet-file20121214-13448-933j3r-0'
notice: /Stage[main]/Mcollective/File[/var/tmp/facts.yaml]/content:
--- /var/tmp/facts.yaml 2012-12-14 00:53:20.0 +
+++ /tmp/puppet-file20121214-13448-933j3r-0 2012-12-14 00:55:35.0
+
@@ -93,13 +93,13 @@
architecture: *id002
processor14: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz
- type: Rack Mount Chassis
processor20: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz
+ type: Rack Mount Chassis
domain: mochimedia.net
timezone: UTC
title: mcollective
- diskdrives: sda
+ diskdrives: sda
ipaddress_eth1: 10.0.8.71
processor8: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz
processor11: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz
When Puppet comparse the /var/tmp/facts.yaml file to the file in the
Filebucket it adds some replaces some entries with an extra space. It
appears to add a couple different entries each run.
Here is the file resource --
/var/tmp/facts.yaml:
owner= root,
group= root,
mode = 400,
loglevel = debug,
content = inline_template(%= scope.to_hash.reject { |k,v| k.to_s
=~ /(uptime_seconds|uptime_hours|timestamp|free)/ }.to_yaml %)
Any thoughts or suggestions? Seems like an odd one to me.
-Z
--
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/-/KWkrTqkvwXcJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet and Mcollective yaml file changing when it shouldn't
Running Ruby 1.8.7... I believe this issue started when I upgraded from
1.8.5, but I am not 100% positive.
On Thursday, December 13, 2012 5:06:54 PM UTC-8, Zane Williamson wrote:
Has anyone else ran into this?
debug: /Stage[main]/Mcollective/File[/var/tmp/facts.yaml]/content:
Executing 'diff -u /var/tmp/facts.yaml
/tmp/puppet-file20121214-13448-933j3r-0'
notice: /Stage[main]/Mcollective/File[/var/tmp/facts.yaml]/content:
--- /var/tmp/facts.yaml 2012-12-14 00:53:20.0 +
+++ /tmp/puppet-file20121214-13448-933j3r-0 2012-12-14 00:55:35.0
+
@@ -93,13 +93,13 @@
architecture: *id002
processor14: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz
- type: Rack Mount Chassis
processor20: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz
+ type: Rack Mount Chassis
domain: mochimedia.net
timezone: UTC
title: mcollective
- diskdrives: sda
+ diskdrives: sda
ipaddress_eth1: 10.0.8.71
processor8: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz
processor11: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz
When Puppet comparse the /var/tmp/facts.yaml file to the file in the
Filebucket it adds some replaces some entries with an extra space. It
appears to add a couple different entries each run.
Here is the file resource --
/var/tmp/facts.yaml:
owner= root,
group= root,
mode = 400,
loglevel = debug,
content = inline_template(%= scope.to_hash.reject { |k,v| k.to_s
=~ /(uptime_seconds|uptime_hours|timestamp|free)/ }.to_yaml %)
Any thoughts or suggestions? Seems like an odd one to me.
-Z
--
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/-/US1QA9X_VSoJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet and Mcollective yaml file changing when it shouldn't
Well I think I came up with a decent hack.
content = inline_template(%= scope.to_hash.reject { |k,v| k.to_s =~
/(uptime_seconds|uptime_hours|timestamp|free)/ }.to_yaml.sort { |a,b| b =
a} %)
the sort and then inverse (to make sure the ---/n is on top for the fact
file format) seems to stop to_yaml from adding spaces.
On Thursday, December 13, 2012 5:06:54 PM UTC-8, Zane Williamson wrote:
Has anyone else ran into this?
debug: /Stage[main]/Mcollective/File[/var/tmp/facts.yaml]/content:
Executing 'diff -u /var/tmp/facts.yaml
/tmp/puppet-file20121214-13448-933j3r-0'
notice: /Stage[main]/Mcollective/File[/var/tmp/facts.yaml]/content:
--- /var/tmp/facts.yaml 2012-12-14 00:53:20.0 +
+++ /tmp/puppet-file20121214-13448-933j3r-0 2012-12-14 00:55:35.0
+
@@ -93,13 +93,13 @@
architecture: *id002
processor14: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz
- type: Rack Mount Chassis
processor20: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz
+ type: Rack Mount Chassis
domain: mochimedia.net
timezone: UTC
title: mcollective
- diskdrives: sda
+ diskdrives: sda
ipaddress_eth1: 10.0.8.71
processor8: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz
processor11: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz
When Puppet comparse the /var/tmp/facts.yaml file to the file in the
Filebucket it adds some replaces some entries with an extra space. It
appears to add a couple different entries each run.
Here is the file resource --
/var/tmp/facts.yaml:
owner= root,
group= root,
mode = 400,
loglevel = debug,
content = inline_template(%= scope.to_hash.reject { |k,v| k.to_s
=~ /(uptime_seconds|uptime_hours|timestamp|free)/ }.to_yaml %)
Any thoughts or suggestions? Seems like an odd one to me.
-Z
--
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/-/eE8sQojblMUJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet and Mcollective yaml file changing when it shouldn't
Actually, applying sort doesn't work. It doesn't sort the file properly
and the spacing and line creation is incorrect.
I looked at other similar posts and it appears to be an issues with Ruby
with no direct solution besides stopping puppet from managing this file.
On Thursday, December 13, 2012 5:06:54 PM UTC-8, Zane Williamson wrote:
Has anyone else ran into this?
debug: /Stage[main]/Mcollective/File[/var/tmp/facts.yaml]/content:
Executing 'diff -u /var/tmp/facts.yaml
/tmp/puppet-file20121214-13448-933j3r-0'
notice: /Stage[main]/Mcollective/File[/var/tmp/facts.yaml]/content:
--- /var/tmp/facts.yaml 2012-12-14 00:53:20.0 +
+++ /tmp/puppet-file20121214-13448-933j3r-0 2012-12-14 00:55:35.0
+
@@ -93,13 +93,13 @@
architecture: *id002
processor14: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz
- type: Rack Mount Chassis
processor20: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz
+ type: Rack Mount Chassis
domain: mochimedia.net
timezone: UTC
title: mcollective
- diskdrives: sda
+ diskdrives: sda
ipaddress_eth1: 10.0.8.71
processor8: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz
processor11: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz
When Puppet comparse the /var/tmp/facts.yaml file to the file in the
Filebucket it adds some replaces some entries with an extra space. It
appears to add a couple different entries each run.
Here is the file resource --
/var/tmp/facts.yaml:
owner= root,
group= root,
mode = 400,
loglevel = debug,
content = inline_template(%= scope.to_hash.reject { |k,v| k.to_s
=~ /(uptime_seconds|uptime_hours|timestamp|free)/ }.to_yaml %)
Any thoughts or suggestions? Seems like an odd one to me.
-Z
--
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/-/-P8raaZkRKcJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] mcollective and aptitude safe-upgrade
Guys Compliments of the festive season to everyone. Ive looked at mcollective plugins from http://projects.puppetlabs.com/projects/mcollective-plugins/wiki And I tried / installed some of them. What im looking for is a method or really a mcollective plugin to 'aptitude safe-upgrade' on my test VMs. Would anyone have a solution or method on how I can go about this. The only other solution I can think of, is to use capistrano (which is the reason for this email, as im not entirely satisfied with that solution) and then have puppet manage my public key. Kind Regards Brent Clark -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] New Puppet User: Issues with pre-commit script
Hi Guys,
I am new to puppet so please let me know if this is not the correct place
for asking this question. I am setting up a new puppet environment running
the latest 3.x version. I have the puppet master and client setup
correctly and tested with deploying a simple file to the client. Now, I am
working on adding all the configs to SVN since I will have all my users
checkout the nodes.pp file and place their node entries in this file via
SVN. I would like to do some check on this file before it is checked in to
make sure there are no syntax errors. I am using the following pre-commit
scirpt that I came across online:
--
#!/bin/bash
REPOS=$1
TXN=$2
tmpfile=$(mktemp)
export
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
for file in $(svnlook changed -t $TXN $REPOS | awk '/^[^D].*\.pp$/
{print $2}')
do
svnlook cat -t $TXN $REPOS $file $tmpfile
puppet parser validate $tmpfile /dev/null
if [ $? -ne 0 ]
then
echo Puppet syntax error in $file 12
exit 1
fi
done
--
Here is my nodes.pp file that is being edited:
--
node 'testrhel.gene.com' { include simtestfile }
--
Now with this node.pp file I am able to update the testrhel server with the
simtestfile just fine and the puppet parser validate command does not
complain if I run it manually:
--
[root@ssfpuppetd01 hooks]# puppet parser validate
/etc/puppet/manifests/nodes.pp
[root@ssfpuppetd01 hooks]#
--
However, now when I try to svn ci this file I get an error and it looks
like it is because the above command returns a 1 for some reason:
--
..snip..
Sendingnodes.pp
Transmitting file data .svn: Commit failed (details follow):
svn: Commit blocked by pre-commit hook (exit code 1) with output:
+ REPOS=/var/svn/repos/puppet
+ TXN=30-28
++ mktemp
+ tmpfile=/tmp/tmp.EmWYD21813
+ export
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
+
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
++ svnlook changed -t 30-28 /var/svn/repos/puppet
++ awk '/^[^D].*\.pp$/ {print $2}'
+ for file in '$(svnlook changed -t $TXN $REPOS | awk
'\''/^[^D].*\.pp$/ {print $2}'\'')'
+ svnlook cat -t 30-28 /var/svn/repos/puppet manifests/nodes.pp
Sendingnodes.pp
Transmitting file data .svn: Commit failed (details follow):
svn: Commit blocked by pre-commit hook (exit code 1) with output:
+ REPOS=/var/svn/repos/puppet
+ TXN=30-28
++ mktemp
+ tmpfile=/tmp/tmp.EmWYD21813
+ export
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
+
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
++ svnlook changed -t 30-28 /var/svn/repos/puppet
++ awk '/^[^D].*\.pp$/ {print $2}'
+ for file in '$(svnlook changed -t $TXN $REPOS | awk
'\''/^[^D].*\.pp$/ {print $2}'\'')'
+ svnlook cat -t 30-28 /var/svn/repos/puppet manifests/nodes.pp
*+ puppet parser validate /tmp/tmp.EmWYD21813*
*+ '[' 1 -ne 0 ']'*
+ echo 'Puppet syntax error in manifests/nodes.pp'
Puppet syntax error in manifests/nodes.pp
+ exit 1
--
However, if I run that command manually it does not return any errors:
--
[root@ssfpuppetd01 hooks]# puppet parser validate /tmp/tmp.EmWYD21813
[root@ssfpuppetd01 hooks]# cat /tmp/tmp.EmWYD21813
node 'testrhel.gene.com' {
include simtestfile
}
[root@ssfpuppetd01 hooks]#
--
Any help would be greatly appreciated.
Thanks,
-J
--
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/-/W2HkSI7z5FcJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: puppet dashboard inventory
Hi,
I believe I have done that.
So on my puppet master (puppet-server1) I have modified the puppet.conf
file and added the following:
[master]
storeconfigs = true
storeconfigs_backend = puppetdb
Also puppetdb.conf
[master]
storeconfigs = true
storeconfigs_backend = puppetdb
and added the route.yaml file
I did also edit the auth.conf file - do I need to do on the puppetmaster ?
On the dashboard server I have turned on the inventory service and added
the puppetdb server as the invenory_server - wher else would it know how to
connect to the puppetdb ?
I have also made sure all the certs have been signed by the puppet CA
server and are valid
Thanks,
Oli
On Thursday, December 13, 2012 9:26:28 PM UTC, pmbuko wrote:
On Dec 13, 2012, at 4:09 PM, vioilly wrote:
Just trying to get help here.
My puppetdb server is called puppet-server3. My dashboard server is
puppet-server2. I can run inventory commands against my puppetdb and get
results.
For example - i have a puppet-client2.test.net machine running the puppet
agent
[root@puppet-server3 ~]# curl -H Accept: application/json '
http://localhost:8080/status/nodes/puppet-client2.test.net'
{
name : puppet-client2.test.net,
deactivated : null,
catalog_timestamp : 2012-12-13T17:55:28.704Z,
facts_timestamp : 2012-12-13T17:55:28.534Z
So that tells me the puppetdb is holding facts about my puppet agent
For the dashboard, what inventory server do I specify in settings.yml? It
is the puppetdb server (puppet-server3.test.net)
# Hostname of the inventory server.
inventory_server: 'puppet-server3.test.net'
# Port for the inventory server.
inventory_port: 8081
Do I need to set up SSL certs between the dashboard server and the
puppetdb server?
Any help would be appreciated
Cheers,
Oli
You do not need to make any changes to your dashboard server. Instead, you
need to modify two files and add one file to your puppet master. See step 2
on this page for the details:
http://docs.puppetlabs.com/puppetdb/1/connect_puppet_master.html#step-2-edit-config-files
--
Peter
--
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/-/I4jqT0AyqGYJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet module restart puppet client or not?
On Thursday, December 13, 2012 4:03:20 PM UTC-8, Ugo Bellavance wrote: That rises two questions in my mind: 1. In my understanding, puppetmaster catches any changes in the manifests without needing a restart, why can't the puppet client reload its puppet.conf parameters at the next run? There's a pretty big distinction between the puppetmaster watching -manifests- that it uses and watching/changing -config settings- : the first one is pretty safe (controlled by the `filetimeout` setting and mostly works), the second is pretty perilous when running in a monolithic long-lived ruby process. There is a lot of tangled stuff around puppet early bootstrapping and initialization that is a major focus of work for the upcoming 3.1 release: http://projects.puppetlabs.com/versions/288 but even if after that's cleared up, the edge cases are pretty brutal -- For example if the value (or heck, the contents) of $libdir changes and new versions of plugins are available, they can't be reliably reloaded into the same ruby process. See stuff like http://projects.puppetlabs.com/issues/4248#note-29 , and the long list of related issues on http://projects.puppetlabs.com/issues/7316 . IMO this is the biggest drawback to long-running puppet daemon processes compared to periodic instantiation via cron / god / daemontools /etc: you just cannot be confident that the interpreter state is actually going to reinitialize cleanly if something big changes underneath it. 1. Why puppet can't use the reload option of most current daemons' init scripts? I think there should be a parameter hasreload, similar to hasrestart, saying that the init script supports the use of the reload argument. This would avoid this kind of problem, and people wouldn't have to redefine the restart command. Look back through some of the prior discussions on this topic; I can understand the desire but previous discussions have raised some legitimate issues that nobody's code so far has addressed -- http://projects.puppetlabs.com/issues/1014 (!!) http://projects.puppetlabs.com/issues/3323 Looks like the most recent state of play was Daniel Pittman's proposal here: http://projects.puppetlabs.com/issues/3323#note-14 which seems nice clean (add support for `hasrestart = graceful`). eric0 -- 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/-/VJjARPE_o7sJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
