similar to: Puppet Node Create?

Hi ! I am currently testing puppet on CentOS 6 and I wish to test the cloud provisioner tool. The problem is the following : I can''t use fog because of ruby version issue. The system : CentOS 6.4 with Ruby 1.8.7 (last version for CentOS) What I did to get the problem : install puppet-server install module puppetlabs-cloud_provisioner Trying install Fog -v 0.7.2 (cloud service library

Hi Guys, I''m unable to load the module cloud provisioner, when I try to run node_aws it gives me the below errors: Error: Could not autoload puppet/face/node_aws/list_keynames: no such file to load -- guid Error: Could not parse application options: Could not autoload puppet/face/node_aws/list_keynames: no such file to load -- guid And when I see the help list I can see the below

Hello, We''re trying to come up with a nice way to indicate when a Puppet module like cloud provisioner breaks a Puppet subcommand because of missing dependencies. When this happens in the current 3.0rc branch, all help for all subcommands is unavailable. This isn''t very helpful. We''re planning to simply mark the subcommands that have incomplete actions as

We are happy to announce the first public release candidate of our Puppet Cloud Provisioner. This release is available for download at our Module Forge: http://forge.puppetlabs.com/puppetlabs/cloud_provisioner<http://downloads.puppetlabs.com/dashboard/> Extensive documentation can be found at: http://docs.puppetlabs.com/guides/cloud_pack_getting_started.html Please report feedback via the

Any light someone can shed sure would be appreciated. I start with 1 cert -- the master''s, where I am running this: jblaine@ip-10-191-115-140:~$ sudo puppet cert list --all + "ip-10-191-115-140.ec2.internal" (74:8B:7B:EF:41:E6:F9:98:93:15:42:6A:4C:2F:28:CC) (alt names: "DNS:ip-10-191-115-140.ec2.internal", "DNS:puppet", "DNS:puppet.ec2.internal")

Hi all, When i try to boot an ec2 instance using: *puppet node_aws bootstrap --server myserverOnAWS.com --image ami-61ad0108 --keyname test-malcom --login ubuntu --type m1.small --keyfile test-malcom.pem -g puppets --verbose --debug --puppetagent-certname test* I get this error: *notice: Signing certificate ...* *debug: certificate_status supports formats: b64_zlib_yaml pson raw yaml; using

Hi, I am trying to install node_openstack module for puppet. But I see its dependency on puppetlabs-cloud_provisioner<https://forge.puppetlabs.com/puppetlabs-cloud_provisioner> (>= 1.0.2) Is this version available, if not is there any work around? regards, Haynes Davis ________________________________ This message is for the designated recipient only and may contain privileged,

Hi everyone! having a slight problem with the installing the cloud provisioning module [code] http://docs.puppetlabs.com/guides/cloud_pack_getting_started.html [/code] everything worked until I wanted to actually try to fire it up: [code] >puppet node_aws list Error: Could not autoload puppet/face/node_aws/fingerprint: cannot load such file -- guid Error: Could not parse application

Hi, I am trying to install fog which is required for cloud provisioner. > gem install fog -v 0.7.2 I am getting the following error Building native extensions. This could take a while... ................ ERROR: Error installing fog: ERROR: Failed to build gem native extension. /usr/bin/ruby extconf.rb creating Makefile make

No problem installing open puppet and using it. patterns run aok. when trying to use the installer for pe, on the puppetmaster, installs ok. when trying to use the installer for pe, on the puppet agent, installs ok but no cert sent as shown by puppet cert list on puppetmaster. also puppet agent --test on puppet agent shows err: could not retrieve catalog from remote server: error 400 on

So I was looking at the type reference, and noticed that for a lot of the types, no namevar was listed. When I checked the types in the code, for each of those omissions, the namevar was simply "name". Now, it might be self evident that this is the case, but a little documentation couldn''t hurt, If not in each type, at least in the section where it describes what namevars

Hi, I have created an agent node from a master node using below command. puppet node_aws create --image ami-cc5af9a5 --keyname icos-client --type ti.micro Now as i am trying to install puppet on it using below command puppet node install \ --install-script=puppet- enterprise \ --installer-payload=/usr/local/puppet/puppet-2.7.0.tar.gz \ --installer-answers=/usr/local/puppet/agent.txt \

Hi, I needed a function to check if a file is existing on the Debian box I am configuring. So I used this one module Puppet::Parser::Functions newfunction(:file_exists, :type => :rvalue) do |args| if File.exists?(args[0]) return 1 else return 0 end end end It work greats for some service where apache2 doesn''t work for me. I am using it this way

Just started a rollout of centos 6.x across our Puppet deployment (100-odd servers). what fact would people suggest I use to distinguish 5.x from 6.x (quite a lot of subsystems are different between major releases)? lsb* facts don''t seem to be present on centos 6 - is this an EPEL bug, or have they just been removed in Facter? Thanks! -- You received this message because you are

Hi, I am using the cloud provisioner to bootstrap some ec2 nodes, and these clients are signed using a randomly generated certname, which is put in /etc/puppet.conf at the bootstrap time (eg certname = d7bcd693-73fd-495f-0876-ff91ea11111e). But my puppet code repo also manages the puppet.conf file, so the file will be overwritten on the client at the first puppet run. Nevertheless, i should not

0.25.5 changed the default vardir from /var/puppet to /var/lib/puppet and it''s caused the odd issue we have to fix in the Mac pkg preflights. After re-reading ''man hier'' I''m tempted to change the default on OS X to: /var/db/puppet instead. /var/ multi-purpose log, temporary, transient, and spool files ...

Dear community, I use puppet to deploy iptables on every server. This is working fine. In the manifest I defined an iptables service which leads to my init script. The thing is each time I run puppet I got : notice: /Stage[main]/Iptables/Service[netfilter]/ensure: ensure changed ''stopped'' to ''running'' I would like to add a status command to my startup script

I have a freshly installed and updated CentOS 5.4 system running puppet 0.25.5. I followed the passenger docs here: http://projects.puppetlabs.com/projects/puppet/wiki/Using_Passenger Upon starting the client, the following appears in the apache error log. [Thu Jun 24 10:48:40 2010] [error] [client 10.10.4.45] Premature end of script headers: production [ pid=6785 file=ext/apache2/Hooks.cpp:706

Hi! Which database would you recommend to use mysql or postgresql for puppet? Estimated number of nodes 30000, they send reports every 30 minutes. Thanks -- 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

Hiera-Puppet 1.0.0rc1 is a feature release candidate designed to accompany Puppet 3.0 and Hiera 1.0. It includes Puppet functions for hiera and also the puppet backend for hiera lookups. Downloads are available: * Source http://downloads.puppetlabs.com/hiera/hiera-puppet-1.0.0rc1.tar.gz * Apt and yum development repositories * Apple package