Re: [Puppet Users] Geppetto is ready
Hello Henrik, First of all thanks for providing and IDE for puppet module development! I started using Gepetto just before puppetcamp Amsterdam and using it ever since. I like the idea of creating a skeleton and integrating directly with version control. One issue I experience at the moment is: When cloning a newly created repo from git within Gepetto I get a null pointer exception Git repository clone failed. java.lang.NullPointerException import projects from git = clone When cloning on commandline it just warns me that I created an empty repo Initialized empty Git repository in /tmp/apache/.git/ warning: You appear to have cloned an empty repository Maybe its an option to clone an empty repo and just give a warning instead of bailing out. -- Martin Willemsma 2011/6/21 Henrik Lindberg henrik.lindb...@cloudsmith.com Geppetto 1.0 is released and ready for download. We want all the feedback we can get, so try it out and let us know what you think! Full story at: http://cloudsmith.github.com/**geppetto/http://cloudsmith.github.com/geppetto/ If you haven’t been following the project, Geppetto is an integrated toolset for working with Puppet modules and manifests. It’s built on the Eclipse platform. If you’re an Eclipse user, you can install it directly into your IDE. If you’re not, it’s also available as ready-to-run zip’s with a much smaller footprint than the full Eclipse. Although we’re calling it “1.0″ (actually “1.0.0″), Geppetto is is probably more mature than many 1.0 releases, and we have invested quite a bit of time in it over the last six months. (Actually, it didn’t come out of nowhere; it builds on work we’ve done in other domains over the last several years.) We released the first beta at FOSDEM 2011 in Brussels in early February, and got lots of really useful feedback there and at PuppetCamp Amsterdam in April. So thanks to everyone who’s offered help and encouragement along the way, with a special shout-out to the people at Puppet Labs. Regards - henrik -- 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+unsubscribe@** googlegroups.com puppet-users%2bunsubscr...@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 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] How to manage many nodes easily?
We had the same problem and we just separated each node (or group of nodes) in one file and then we load them using the following syntax: import nodes/*.pp You could also organize those files in subdirectories if you like so: import nodes/*/*.pp The only problem we've found with this approach is when creating new files, puppetmaster takes a while to see them. El 20/06/2011 5:25, flex escribió: We have many modules and many nodes, every node may use different module, so it's very unpleasant to modify the nodes.pp Then i saw the external node, but seems it only support class and we have many defines called in node.pp So here is my question: Is there another way for us to manage so many nodes easily or should i change all the defines to classes and using external nodes? -- 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] How to manage many nodes easily?
We use /etc/puppet/node-definitions/*.pp in site.pp similar to what Carles is saying. [node-definitions] is a git repo thats being synced on both puppermasters. This happens on every push to origin We use the 'default' node which does the baseline configuration based on a 'role' In a separate file $fqdn.pp I place the definitions for a node. Are there more people using this kind of approach? --- Martin 2011/6/21 Carles Amigó carles.am...@softonic.com We had the same problem and we just separated each node (or group of nodes) in one file and then we load them using the following syntax: import nodes/*.pp You could also organize those files in subdirectories if you like so: import nodes/*/*.pp The only problem we've found with this approach is when creating new files, puppetmaster takes a while to see them. El 20/06/2011 5:25, flex escribió: We have many modules and many nodes, every node may use different module, so it's very unpleasant to modify the nodes.pp Then i saw the external node, but seems it only support class and we have many defines called in node.pp So here is my question: Is there another way for us to manage so many nodes easily or should i change all the defines to classes and using external nodes? -- 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+unsubscribe@** googlegroups.com puppet-users%2bunsubscr...@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 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] How to manage many nodes easily?
I would see a principle whereby nodes should not ever be defined within the manifest code at all. To me the manifests should be written to be very generic, and then use ENC's to modify their behaviour at a user level. There is still a lot of inconsistency within Puppet as to how device specific data can be obtained (extlookup is very useful but rides roughshod over other architectural principles) but I try to stick to keeping all manifests generic. I write manifests to manage a package, then create a group in dashboard to relate that function to a business need and then a node into that group. On 21 June 2011 14:48, Martin Willemsma mwillem...@gmail.com wrote: We use /etc/puppet/node-definitions/*.pp in site.pp similar to what Carles is saying. [node-definitions] is a git repo thats being synced on both puppermasters. This happens on every push to origin We use the 'default' node which does the baseline configuration based on a 'role' In a separate file $fqdn.pp I place the definitions for a node. Are there more people using this kind of approach? --- Martin 2011/6/21 Carles Amigó carles.am...@softonic.com We had the same problem and we just separated each node (or group of nodes) in one file and then we load them using the following syntax: import nodes/*.pp You could also organize those files in subdirectories if you like so: import nodes/*/*.pp The only problem we've found with this approach is when creating new files, puppetmaster takes a while to see them. El 20/06/2011 5:25, flex escribió: We have many modules and many nodes, every node may use different module, so it's very unpleasant to modify the nodes.pp Then i saw the external node, but seems it only support class and we have many defines called in node.pp So here is my question: Is there another way for us to manage so many nodes easily or should i change all the defines to classes and using external nodes? -- 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+unsubscribe@** googlegroups.com puppet-users%2bunsubscr...@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 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.
[Puppet Users] Re: Problem in wordpress moodule.
On Jun 20, 4:54 pm, lucas.brig...@ymail.com grillobri...@gmail.com
wrote:
I tried using try the logouput = ON_FAILURE in the exec.
But my client is a puppet CentOS. (The puppet version is outdated).
Not recognizing this parameter.
As you asked, I used the - debug.
The output was this:http://pastie.org/2098147
The command that is failing now is 'cp -rp /usr/share/wordpress/ /var/
www/zertico'. Based on the manifests you attached, it looks like you
use this executable path: [/usr/local/bin, /opt/local/bin, /usr/
bin, /usr/sbin] (but I can't be sure, because your manifests don't
exactly match your log). On my CentOS 5 boxes, the cp command is in /
bin (only; this is the LSB-mandated location), so it will not be found
when Puppet attempts to apply your Exec. Given that you're running a
simple command rather than a script, I'd recommend that you just
specify the full path to the cp command (i.e. /bin/cp) instead of
using a separate 'path' parameter.
I discovered that any command that has not executed any parameter. Only simple
commands.
exec {Free: path = [/ usr / bin]}
The problem really is in the function exec.
The problem is in the specific Exec resource(s) in your manifest.
Exec in general works fine for many, many people, with a wide variety
of commands.
John
--
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] installing puppet client
CHEBRIAN wrote: Hi, how to install puppet client thru puppet master . My requirement is to install puppet client nearly 400 client servers. its difficult to install puppet client in all the servers by apt- get . share u r suggestions . Regards chebrian We only (will) have about 100 clients. We install puppet clients during initial Ubuntu installation. A postinstall script that comes in preseed file. This downloads and installs puppet and facter gems. But if you want to add puppet to already installed systems then I don't see much beside using the rsh/ssh approach already proposed. Maybe using pdsh if your servernames make for looping difficult. regards, Andreas -- 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] confused about file ensure/require
On Jun 20, 2011, at 3:54 PM, Ken Barber wrote:
It does seem like its not being included :-) ...
What does:
echo # foo /etc/ntp.conf
puppet apply -d -e 'include ntp'
Do?
seems so basic - output at bottom
I have gone over and over the Pro Puppet book and the
http://docs.puppetlabs.com/guides/file_serving.html page and they both are the
same and this should absolutely work.
# cat modules/ntp/manifests/ntp.pp
# ntp.pp
class ntp {
case $operatingsystem {
centos, redhat: {
$service_name = 'ntpd'
$conf_file = 'ntp.conf.el'
}
debian, ubuntu: {
$service_name = 'ntp'
$conf_file = 'ntp.conf.debian'
}
}
package { 'ntp':
ensure = installed,
}
service { 'ntp':
name = $service_name,
ensure = running,
enable = true,
subscribe = File['ntp.conf'],
}
file { 'ntp.conf':
path = '/etc/ntp.conf',
ensure = file,
require = Package['ntp'],
source = puppet:///modules/ntp/files/${conf_file},
}
}
# class {'ntp': }
but no matter what I do, it always errors and says it can't find
/etc/puppet/modules/ntp/files/ntp.conf.debian but yet it is there and readable
all the way...
# ls -l /etc/puppet/modules/ntp/files/ntp.conf.debian
-rw-r--r-- 1 root root 535 2011-06-13 12:55
/etc/puppet/modules/ntp/files/ntp.conf.debian
anyway, the output as requested...
Thanks
Craig
# puppet apply -d -e 'include ntp'
info: Loading facts in datacenter
info: Loading facts in datacenter
debug: importing '/etc/puppet/modules/ntp/manifests/init.pp' in environment
production
debug: importing '/etc/puppet/modules/ntp/manifests/ntp.pp' in environment
production
debug: Automatically imported ntp from ntp into production
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Puppet::Type::Package::ProviderUrpmi: file urpmi does not exist
debug: Puppet::Type::Package::ProviderNim: file /usr/sbin/nimclient does not
exist
debug: Puppet::Type::Package::ProviderPkg: file /usr/bin/pkg does not exist
debug: Puppet::Type::Package::ProviderHpux: file /usr/sbin/swinstall does not
exist
debug: Puppet::Type::Package::ProviderYum: file yum does not exist
debug: Puppet::Type::Package::ProviderZypper: file /usr/bin/zypper does not
exist
debug: Puppet::Type::Package::ProviderFink: file /sw/bin/fink does not exist
debug: Puppet::Type::Package::ProviderAptrpm: file rpm does not exist
debug: Puppet::Type::Package::ProviderAix: file /usr/bin/lslpp does not exist
debug: Puppet::Type::Package::ProviderSunfreeware: file pkg-get does not exist
debug: Puppet::Type::Package::ProviderPorts: file /usr/local/sbin/portversion
does not exist
debug: Puppet::Type::Package::ProviderOpenbsd: file pkg_delete does not exist
debug: Puppet::Type::Package::ProviderRug: file /usr/bin/rug does not exist
debug: Puppet::Type::Package::ProviderPortupgrade: file
/usr/local/sbin/portversion does not exist
debug: Puppet::Type::Package::ProviderPortage: file /usr/bin/emerge does not
exist
debug: Puppet::Type::Package::ProviderFreebsd: file /usr/sbin/pkg_delete does
not exist
debug: Puppet::Type::Package::ProviderUp2date: file /usr/sbin/up2date-nox does
not exist
debug: Puppet::Type::Package::ProviderRpm: file rpm does not exist
debug: Puppet::Type::Package::ProviderSun: file /usr/sbin/pkgadd does not exist
debug: Puppet::Type::Service::ProviderRunit: file /usr/bin/sv does not exist
debug: Puppet::Type::Service::ProviderLaunchd: file /bin/launchctl does not
exist
debug: Puppet::Type::Service::ProviderRedhat: file /sbin/service does not exist
debug: Puppet::Type::Service::ProviderGentoo: file /sbin/rc-update does not
exist
debug: Puppet::Type::Service::ProviderDaemontools: file /usr/bin/svc does not
exist
debug: Puppet::Type::File::ProviderMicrosoft_windows: feature microsoft_windows
is missing
debug: Creating default schedules
debug: Failed to load library 'shadow' for feature 'libshadow'
debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does
not exist
debug: Puppet::Type::User::ProviderLdap: true value when expecting false
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certs/ubuntu.ttinet.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/certificate_requests]:
Re: [Puppet Users] confused about file ensure/require
On Tue, Jun 21, 2011 at 9:03 AM, Craig White craig.wh...@ttiltd.com wrote:
On Jun 20, 2011, at 3:54 PM, Ken Barber wrote:
It does seem like its not being included :-) ...
What does:
echo # foo /etc/ntp.conf
puppet apply -d -e 'include ntp'
Do?
seems so basic - output at bottom
I have gone over and over the Pro Puppet book and the
http://docs.puppetlabs.com/guides/file_serving.html page and they both are
the same and this should absolutely work.
# cat modules/ntp/manifests/ntp.pp
# ntp.pp
class ntp {
case $operatingsystem {
centos, redhat: {
$service_name = 'ntpd'
$conf_file = 'ntp.conf.el'
}
debian, ubuntu: {
$service_name = 'ntp'
$conf_file = 'ntp.conf.debian'
}
}
package { 'ntp':
ensure = installed,
}
service { 'ntp':
name = $service_name,
ensure = running,
enable = true,
subscribe = File['ntp.conf'],
}
file { 'ntp.conf':
path = '/etc/ntp.conf',
ensure = file,
require = Package['ntp'],
source = puppet:///modules/ntp/files/${conf_file},
Take the files out of the source settings.
the filesystem path:
$modulepath/ntp/files/foo
translates to the puppet:// url:
puppet:///modules/ntp/foo
}
}
# class {'ntp': }
but no matter what I do, it always errors and says it can't find
/etc/puppet/modules/ntp/files/ntp.conf.debian but yet it is there and
readable all the way...
# ls -l /etc/puppet/modules/ntp/files/ntp.conf.debian
-rw-r--r-- 1 root root 535 2011-06-13 12:55
/etc/puppet/modules/ntp/files/ntp.conf.debian
anyway, the output as requested...
Thanks
Craig
# puppet apply -d -e 'include ntp'
info: Loading facts in datacenter
info: Loading facts in datacenter
debug: importing '/etc/puppet/modules/ntp/manifests/init.pp' in environment
production
debug: importing '/etc/puppet/modules/ntp/manifests/ntp.pp' in environment
production
debug: Automatically imported ntp from ntp into production
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Puppet::Type::Package::ProviderUrpmi: file urpmi does not exist
debug: Puppet::Type::Package::ProviderNim: file /usr/sbin/nimclient does
not exist
debug: Puppet::Type::Package::ProviderPkg: file /usr/bin/pkg does not exist
debug: Puppet::Type::Package::ProviderHpux: file /usr/sbin/swinstall does
not exist
debug: Puppet::Type::Package::ProviderYum: file yum does not exist
debug: Puppet::Type::Package::ProviderZypper: file /usr/bin/zypper does not
exist
debug: Puppet::Type::Package::ProviderFink: file /sw/bin/fink does not
exist
debug: Puppet::Type::Package::ProviderAptrpm: file rpm does not exist
debug: Puppet::Type::Package::ProviderAix: file /usr/bin/lslpp does not
exist
debug: Puppet::Type::Package::ProviderSunfreeware: file pkg-get does not
exist
debug: Puppet::Type::Package::ProviderPorts: file
/usr/local/sbin/portversion does not exist
debug: Puppet::Type::Package::ProviderOpenbsd: file pkg_delete does not
exist
debug: Puppet::Type::Package::ProviderRug: file /usr/bin/rug does not exist
debug: Puppet::Type::Package::ProviderPortupgrade: file
/usr/local/sbin/portversion does not exist
debug: Puppet::Type::Package::ProviderPortage: file /usr/bin/emerge does
not exist
debug: Puppet::Type::Package::ProviderFreebsd: file /usr/sbin/pkg_delete
does not exist
debug: Puppet::Type::Package::ProviderUp2date: file /usr/sbin/up2date-nox
does not exist
debug: Puppet::Type::Package::ProviderRpm: file rpm does not exist
debug: Puppet::Type::Package::ProviderSun: file /usr/sbin/pkgadd does not
exist
debug: Puppet::Type::Service::ProviderRunit: file /usr/bin/sv does not
exist
debug: Puppet::Type::Service::ProviderLaunchd: file /bin/launchctl does not
exist
debug: Puppet::Type::Service::ProviderRedhat: file /sbin/service does not
exist
debug: Puppet::Type::Service::ProviderGentoo: file /sbin/rc-update does not
exist
debug: Puppet::Type::Service::ProviderDaemontools: file /usr/bin/svc does
not exist
debug: Puppet::Type::File::ProviderMicrosoft_windows: feature
microsoft_windows is missing
debug: Creating default schedules
debug: Failed to load library 'shadow' for feature 'libshadow'
debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not
exist
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl
does not exist
debug: Puppet::Type::User::ProviderLdap: true value when expecting false
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/client_data]: Autorequiring
File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring
File[/etc/puppet/ssl]
Re: [Puppet Users] confused about file ensure/require
On 21/06/11 17:03, Craig White wrote:
On Jun 20, 2011, at 3:54 PM, Ken Barber wrote:
It does seem like its not being included :-) ...
What does:
echo # foo /etc/ntp.conf
puppet apply -d -e 'include ntp'
Do?
seems so basic - output at bottom
I have gone over and over the Pro Puppet book and the
http://docs.puppetlabs.com/guides/file_serving.html page and they both are
the same and this should absolutely work.
# cat modules/ntp/manifests/ntp.pp
# ntp.pp
class ntp {
case $operatingsystem {
centos, redhat: {
$service_name = 'ntpd'
$conf_file = 'ntp.conf.el'
}
debian, ubuntu: {
$service_name = 'ntp'
$conf_file = 'ntp.conf.debian'
}
}
package { 'ntp':
ensure = installed,
}
service { 'ntp':
name = $service_name,
ensure = running,
enable = true,
subscribe = File['ntp.conf'],
}
file { 'ntp.conf':
path = '/etc/ntp.conf',
ensure = file,
require = Package['ntp'],
source = puppet:///modules/ntp/files/${conf_file},
}
}
# class {'ntp': }
but no matter what I do, it always errors and says it can't find
/etc/puppet/modules/ntp/files/ntp.conf.debian but yet it is there and
readable all the way...
You don't want the /files/ bit. Puppet automatically looks for module
files in the /files/ subfolder. Currently puppet is trying to access
/etc/puppet/modules/ntp/files/files/ntp.conf.debian which doesn't exist :)
All you need is:
source = puppet:///modules/ntp/${conf_file}
HTH
Dan
# ls -l /etc/puppet/modules/ntp/files/ntp.conf.debian
-rw-r--r-- 1 root root 535 2011-06-13 12:55
/etc/puppet/modules/ntp/files/ntp.conf.debian
anyway, the output as requested...
Thanks
Craig
--
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] Adding README to puppetdoc?
Hi all, I'm working on creating all of our Documentation using puppetdoc (version 0.25 from EPEL on CentOS 5.5). We are including all of our modules at the same time using the --modulepath directive, however our README file is not being picked up. Is there any way to include the README file as part of the documentation which is being generated? We are currently using the following command: puppet doc --mode rdoc -o ../docs --verbose --config /etc/puppet/puppet.conf --modulepath modules/:systems/ The README sits above the modules and systems directory. Thanks in advance, Matt -- 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/-/S1vTg-n2ldwJ. 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] confused about file ensure/require
On Jun 21, 2011, at 9:09 AM, Nigel Kersten wrote:
On Tue, Jun 21, 2011 at 9:03 AM, Craig White craig.wh...@ttiltd.com wrote:
On Jun 20, 2011, at 3:54 PM, Ken Barber wrote:
It does seem like its not being included :-) ...
What does:
echo # foo /etc/ntp.conf
puppet apply -d -e 'include ntp'
Do?
seems so basic - output at bottom
I have gone over and over the Pro Puppet book and the
http://docs.puppetlabs.com/guides/file_serving.html page and they both are
the same and this should absolutely work.
# cat modules/ntp/manifests/ntp.pp
# ntp.pp
class ntp {
case $operatingsystem {
centos, redhat: {
$service_name = 'ntpd'
$conf_file = 'ntp.conf.el'
}
debian, ubuntu: {
$service_name = 'ntp'
$conf_file = 'ntp.conf.debian'
}
}
package { 'ntp':
ensure = installed,
}
service { 'ntp':
name = $service_name,
ensure = running,
enable = true,
subscribe = File['ntp.conf'],
}
file { 'ntp.conf':
path = '/etc/ntp.conf',
ensure = file,
require = Package['ntp'],
source = puppet:///modules/ntp/files/${conf_file},
Take the files out of the source settings.
the filesystem path:
$modulepath/ntp/files/foo
translates to the puppet:// url:
puppet:///modules/ntp/foo
Indeed - thanks - it was making me crazy.
I suspect that there was a very good reason for doing that (omitting the
'files' from the path) but it completely eludes me.
Craig
--
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] sysv init scripts when using gem to install
I am using ruby-enterprise for ruby packages and gem for puppet/facter
installation and I 'borrowed' the ubuntu sysv init scripts and they mostly work
but for some reason, it won't stop the service as written but it will start.
For example, the 'puppet' script (obviously for puppetd) has the following...
stop_puppet() {
start-stop-daemon --stop --quiet --pidfile $PIDFILE
}
# /etc/init.d/puppet restart
* Restarting puppet configuration management tool
Could not prepare for execution: Could not create PID file:
/var/run/puppet/agent.pid
[ OK ]
Now the file does exist and apparently doesn't get deleted and the process is
not killed as a result of that command and if I substitute 'killall puppetd'
for the 'start-stop-daemon' command, it does actually work but it seems so
inelegant and potentially a problem. The same sort of thing occurs with the
puppetmaster sysv initscript and I've spent too much time with no better answer
than substituting the 'killall puppetd|puppetmaster' and suspect that maybe the
problem is that I have so little familiarity with ubuntu/debian and their sysv
implementation.
Anyone have a better suggestion than 'killall puppetd|puppetmaster' for the
'stop' process?
--
Craig White ~~ craig.wh...@ttiltd.com
1.800.869.6908 ~~~ www.ttiassessments.com
Need help communicating between generations at work to achieve your desired
success? Let us help!
--
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 agent problem on Ubuntu
I'm in the process of setting up puppet and experiencing some issues.
I'm running Ubuntu 11.04 desktop and server in two seperate VM's. I've
installed puppet master (2.6.4) and puppet (2.6.4). The puppet master
and agent are happily working together.
I'm running the example in the book Pro Puppet. This is the first
example;
Code:
class sudo {
package { sudo:
ensure = present,
}
if $operatingsystem == Ubuntu {
package { sudo-ldap:
ensure = present,
require = Package[sudo],
}
}
file { /etc/sudoers:
owner = root,
group = root,
mode = 0440,
source = puppet://$puppetserver/modules/sudo/etc/sudoers,
require = Package[sudo],
}
}
On the agent I run the following command;
puppet agent --server=myserver --no-daemonize --verbose --onetime
The agent see's the change but I get an error;
info: Caching catalog for agentServer
info: Applying configuration version '123456789'
err: /Stage[main]/Sudo/Package[sudo-ldap]/ensure: change from purged
to present
failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--
force-confold
install sudo-ldap' returned 100: E: Could not open lock file /var/lib/
dpkg/lock
- open (13: Permission denied)
E: Unable to lick the administration directory (/var/lib/dpkg/), are
you root?
I don't have another package manager open.
I understand what the problem is. The agent is being run as the
current logged in user and that user doesn't have permission to run
apt-get. Generally to run apt-get i have to do sudo apt-get.
I've thought about modifying the sudoers file and adding nopasswd for
my user (as suggested in other posts) for apt-get but that doesn't
solve the problem since the command in the puppet agent is not run
with sudo.
I understand if I run the puppet agent as a daemon then it runs as
user root which I guess would solve the problem. I'm not sure it's
best to run the agent as a daemon. I might want to control when the
agent pulls the updates from the puppet master (or through cron).
If I run;
sudo puppet agent --server=myserver --no-daemonize --verbose --
onetime
I get a different error;
err: Could not request certificate: Retrieved certificate does not
match private
key; please remove certificate from server and regenerate it with the
current key
I've tried removing the ssl certs from both the puppet master and
agent and run the command again. I get the same problem. When I remove
the sudo from the start of the command the puppet agent is happy with
the cert.
I though about adding my user to the root group as a test. Even when I
do that if I run apt-get update manually a permission denied. I
wondered if this has something to do with the root user being disabled
by default on Ubuntu.
I'm a novice when it comes to these sorts of things. Has anyone got
this working or have any suggestions of how I might solve this issue?
--
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] confused about file ensure/require
I don't think you should be specifying the files part of the source path:
Try:
source = puppet:///modules/ntp/ntp.conf.debian
- Jeff
On 06/20/2011 06:12 PM, Craig White wrote:
I don't know if it is or isn't being included but the -d -e were certainly
useful bits...
err: /Stage[main]/Ntp/File[ntp.conf]: Could not evaluate: Could not retrieve
information from source(s) puppet:///modules/ntp/files/ntp.conf.debian at
/etc/puppet/modules/ntp/manifests/ntp.pp:31
notice: /Stage[main]/Ntp/Service[ntp]: Dependency File[ntp.conf] has failures:
true
but the file is clearly somewhere...
# ls -l /etc/puppet/modules/ntp/files/ntp.conf.debian
-rw-r--r-- 1 root root 535 2011-06-13 12:55
/etc/puppet/modules/ntp/files/ntp.conf.debian
and as noted below, the source is indicated to be
source = puppet:///modules/ntp/files/ntp.conf.debian
which is the same 2 questions I started with since I have the 'Puppet Pro' book
in my hand and various references on the puppetlabs documentation web pages and
I was pretty much of the opinion that this should be working.
Craig
On Jun 20, 2011, at 3:54 PM, Ken Barber wrote:
It does seem like its not being included :-) ...
What does:
echo # foo /etc/ntp.conf
puppet apply -d -e 'include ntp'
Do?
ken.
I thought it should work at least for the 'puppet agent' commands...
# cat manifests/site.pp
import templates
import nodes
import modules
root@ubuntu:/etc/puppet# cat manifests/templates.pp
class baseclass {
}
node default {
include baseclass
include ntp
include facts
}
and the nodes all have
include baseclass
in them
Craig
--
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] Using modules from PuppetForge
Hello All,
New puppet user here. I've been able to create and use my own puppet
modules, but I'm at a loss on how to use modules from PuppetForge,
which seem quite a bit more advanced. For example, I've installed the
camptocamp/apt module via the command 'puppet-module install
camptocamp/apt' into /etc/puppet/modules. I then tried to add the
following code to one of my manifests:
apt::sources_list {google-chrome:
ensure = present,
content = deb http://dl.google.com/linux/chrome/deb/
stable main,
}
apt::key {A040830F7FAC5991:
source =
https://dl-ssl.google.com/linux/linux_signing_key.pub;
}
package { 'google-chrome-stable' :
ensure = latest,
require = File['google-chrome-apt-repository'],
}
When I run the agent, I get an error stating that apt::sources_list is
an invalid resource type. Any idea what I'm doing wrong? I've spent
the last couple hours searching for an answer, and have yet to find
anything that spells it out.
Thanks,
Kyle
http://www.kylehall.info
Mill Run Technology Solutions ( http://millruntech.com )
Crawford County Federated Library System ( http://www.ccfls.org )
Meadville Public Library ( http://www.meadvillelibrary.org )
--
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] installing puppet client
Have you looked at clusterssh? -- vagn On 06/21/2011 12:01 PM, Andreas Kuntzagk wrote: CHEBRIAN wrote: Hi, how to install puppet client thru puppet master . My requirement is to install puppet client nearly 400 client servers. its difficult to install puppet client in all the servers by apt- get . share u r suggestions . Regards chebrian We only (will) have about 100 clients. We install puppet clients during initial Ubuntu installation. A postinstall script that comes in preseed file. This downloads and installs puppet and facter gems. But if you want to add puppet to already installed systems then I don't see much beside using the rsh/ssh approach already proposed. Maybe using pdsh if your servernames make for looping difficult. regards, Andreas -- 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] ANNOUNCE: Puppet 2.7.0 Released
It's here! Puppet 2.7.0. This release is available for download at: http://puppetlabs.com/downloads/puppet/puppet-2.7.0.tar.gz It's available as a gem from rubygems.org. See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected version of 2.7.0 http://projects.puppetlabs.com/projects/puppet/ Full Release Notes are available: https://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes To see the Full CHANGELOG: https://raw.github.com/puppetlabs/puppet/2.7.0/CHANGELOG Puppet 2.7.0 is out! This is a major feature release, and there's a lot of new stuff. Here's the high-level version: Apache License --- Puppet is now released under the Apache 2.0 license. More info is available [here](http://docs.puppetlabs.com/guides/faq#change-to-apache-license). Ruby 1.9 Support There are some known issues with the 2.7.0 release, but YES: we are now supporting Ruby 1.9.2 and higher, and will be aggressively fixing bugs under Ruby 1.9! Deterministic Catalog Application --- Previously, Puppet didn't guarantee that it would apply unrelated resources in any particular order. This meant that if you forgot to specify some important `before` or `require` relationship, a single catalog might work fine on eight nodes and then fail mysteriously on the ninth and tenth. This could be frustrating! Now it's gone: Puppet will make sure that the same catalog will always be applied in the same order on every machine, and it'll either succeed reliably or fail reliably. (This change will also be appearing in the final 2.6.x releases.) Manage Network Devices Puppet has new types for managing network hardware, and a new `puppet device` subcommand for applying these configurations. These are in their early stages and can currently only handle Cisco hardware, but they're the start of a big leap forward in Puppet's ability to manage your entire infrastructure. Man Pages We've spiffed up our man pages, in both regular and on-the-fly flavors! Try `man puppet-agent` or `puppet man catalog`, and party like it's 1971. (We recommend running `gem install ronn` before using the `puppet man` subcommand.) New Subcommands and the Faces API - We've added a powerful new API for creating new Puppet subcommands, and we've used it to expose most of Puppet's internal subsystems. One of our devs has written a series of blog posts about it ([one][faceswhat], [two][facesmore], [three][facesthree]), and there's more documentation on the way, but this opens the door to whole new ways of running Puppet and exploiting its data. To get a look at the new subcommands, just run `puppet help`; if you're interested in tweaking Puppet under the hood, take a look at `lib/puppet/face/secret_agent.rb` to see how easy it is to re-implement the puppet agent application. We've also implemented a new help interface: just run `puppet help subcommand [action]` for short, to-the-point command-line help with the Faces subcommands. [facesthree]: http://www.puppetlabs.com/blog/about-faces-until-we-go-in-the-right-direction/ [faceswhat]: http://www.puppetlabs.com/blog/puppet-faces-what-the-heck-are-faces/ [facesmore]: http://www.puppetlabs.com/blog/faces-actions-options-and-facades-oh-my/ Deprecations -- We're starting the hourglass on a few older features: * **'puppet' as a synonym for 'puppet apply'** --- Starting today, running `puppet my-manifest.pp` will issue a warning; you should start using `puppet apply` directly instead. Support for implicit invocation of puppet apply will be dropped in Puppet 2.8. * **Dynamic scope** --- We've started issuing warnings when variables or resource defaults are found via dynamic lookup. [There's more info and explanation in a guide on the docs site](http://docs.puppetlabs.com/guides/scope_and_puppet.html), but the short version is that you should start referencing variables with their qualified names instead of counting on dynamic scope. We hope to drop support for dynamic scope in Puppet 2.8. * **No more `--parseonly` option** --- This one's already gone, because we used Faces to build a drop-in replacement: use `puppet parser validate [manifest] [manifest ...]` instead. Notice Changed Manifests on the First Try --- During the 2.6.x series, puppet agent would sometimes require two runs to receive new configurations when puppet master was running under Passenger. This persistent bug has been dealt with. (This change will also be appearing in the final 2.6.x releases.) Static Compiler - We've introduced `static_compiler`, a new `catalog_terminus` which can be configured in puppet.conf on your puppet master. There are some known issues that keep it from being used as-is --- you have to manually sync the agent's filebucket to that of the master, and the compiler's behavior around recursion hasn't been
Re: [Puppet Users] Geppetto is ready
Thanks for the error report. Can you log this issue at github and attach the stack trace? I like to get this reported to the provider of the Git integration (I suspect that is where the NPE is coming from, but the stack trace will tell). Regards - henrik On 6/21/11 11:19 AM, Martin Willemsma wrote: Hello Henrik, First of all thanks for providing and IDE for puppet module development! I started using Gepetto just before puppetcamp Amsterdam and using it ever since. I like the idea of creating a skeleton and integrating directly with version control. One issue I experience at the moment is: When cloning a newly created repo from git within Gepetto I get a null pointer exception Git repository clone failed. java.lang.NullPointerException import projects from git = clone When cloning on commandline it just warns me that I created an empty repo Initialized empty Git repository in /tmp/apache/.git/ warning: You appear to have cloned an empty repository Maybe its an option to clone an empty repo and just give a warning instead of bailing out. -- Martin Willemsma 2011/6/21 Henrik Lindberg henrik.lindb...@cloudsmith.com mailto:henrik.lindb...@cloudsmith.com Geppetto 1.0 is released and ready for download. We want all the feedback we can get, so try it out and let us know what you think! Full story at: http://cloudsmith.github.com/__geppetto/ http://cloudsmith.github.com/geppetto/ If you haven’t been following the project, Geppetto is an integrated toolset for working with Puppet modules and manifests. It’s built on the Eclipse platform. If you’re an Eclipse user, you can install it directly into your IDE. If you’re not, it’s also available as ready-to-run zip’s with a much smaller footprint than the full Eclipse. Although we’re calling it “1.0″ (actually “1.0.0″), Geppetto is is probably more mature than many 1.0 releases, and we have invested quite a bit of time in it over the last six months. (Actually, it didn’t come out of nowhere; it builds on work we’ve done in other domains over the last several years.) We released the first beta at FOSDEM 2011 in Brussels in early February, and got lots of really useful feedback there and at PuppetCamp Amsterdam in April. So thanks to everyone who’s offered help and encouragement along the way, with a special shout-out to the people at Puppet Labs. Regards - henrik -- 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 mailto:puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@__googlegroups.com mailto:puppet-users%2bunsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/__group/puppet-users?hl=en 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. -- 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 agent problem on Ubuntu
Hey Im running puppet on Ubuntu
On Tue, Jun 21, 2011 at 3:25 PM, John Nicholson vilvic.j...@gmail.comwrote:
I'm in the process of setting up puppet and experiencing some issues.
I'm running Ubuntu 11.04 desktop and server in two seperate VM's. I've
installed puppet master (2.6.4) and puppet (2.6.4). The puppet master
and agent are happily working together.
I'm running the example in the book Pro Puppet. This is the first
example;
Code:
class sudo {
package { sudo:
ensure = present,
}
if $operatingsystem == Ubuntu {
package { sudo-ldap:
ensure = present,
require = Package[sudo],
}
}
file { /etc/sudoers:
owner = root,
group = root,
mode = 0440,
source = puppet://$puppetserver/modules/sudo/etc/sudoers,
require = Package[sudo],
}
}
On the agent I run the following command;
puppet agent --server=myserver --no-daemonize --verbose --onetime
The agent see's the change but I get an error;
info: Caching catalog for agentServer
info: Applying configuration version '123456789'
err: /Stage[main]/Sudo/Package[sudo-ldap]/ensure: change from purged
to present
failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--
force-confold
install sudo-ldap' returned 100: E: Could not open lock file /var/lib/
dpkg/lock
- open (13: Permission denied)
E: Unable to lick the administration directory (/var/lib/dpkg/), are
you root?
I don't have another package manager open.
I understand what the problem is. The agent is being run as the
current logged in user and that user doesn't have permission to run
apt-get. Generally to run apt-get i have to do sudo apt-get.
I've thought about modifying the sudoers file and adding nopasswd for
my user (as suggested in other posts) for apt-get but that doesn't
solve the problem since the command in the puppet agent is not run
with sudo.
I understand if I run the puppet agent as a daemon then it runs as
user root which I guess would solve the problem. I'm not sure it's
best to run the agent as a daemon. I might want to control when the
agent pulls the updates from the puppet master (or through cron).
In any case if you remote control the agent (via ssh) this might help
http://napkins.wordpress.com/2009/02/18/using-nopasswd-in-sudoers-on-ubuntu/
If I run;
sudo puppet agent --server=myserver --no-daemonize --verbose --
onetime
I get a different error;
err: Could not request certificate: Retrieved certificate does not
match private
key; please remove certificate from server and regenerate it with the
current key
I've tried removing the ssl certs from both the puppet master and
agent and run the command again. I get the same problem. When I remove
the sudo from the start of the command the puppet agent is happy with
the cert.
I though about adding my user to the root group as a test. Even when I
do that if I run apt-get update manually a permission denied. I
wondered if this has something to do with the root user being disabled
by default on Ubuntu.
I'm a novice when it comes to these sorts of things. Has anyone got
this working or have any suggestions of how I might solve this issue?
On the node machine run:
/usr/bin/find /var/lib/puppet/ssl/ -name '*.pem' -exec rm {} \;
Sign the cert on the master side and you should be good to go,
Another issue iv found is that the clocks of the node and the master need to
be in sync
--
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] confused about file ensure/require
Check your source declaration.
source = puppet:///modules/ntp/files/${conf_file},
If your files are in modules/ntp/files you don't include that in your source
declaration
source = puppet:///modules/ntp/${conf_file},
http://docs.puppetlabs.com/guides/file_serving.html
Cheers,
Den
On 22/06/2011, at 2:03, Craig White craig.wh...@ttiltd.com wrote:
On Jun 20, 2011, at 3:54 PM, Ken Barber wrote:
It does seem like its not being included :-) ...
What does:
echo # foo /etc/ntp.conf
puppet apply -d -e 'include ntp'
Do?
seems so basic - output at bottom
I have gone over and over the Pro Puppet book and the
http://docs.puppetlabs.com/guides/file_serving.html page and they both are
the same and this should absolutely work.
# cat modules/ntp/manifests/ntp.pp
# ntp.pp
class ntp {
case $operatingsystem {
centos, redhat: {
$service_name = 'ntpd'
$conf_file = 'ntp.conf.el'
}
debian, ubuntu: {
$service_name = 'ntp'
$conf_file = 'ntp.conf.debian'
}
}
package { 'ntp':
ensure = installed,
}
service { 'ntp':
name = $service_name,
ensure = running,
enable = true,
subscribe = File['ntp.conf'],
}
file { 'ntp.conf':
path = '/etc/ntp.conf',
ensure = file,
require = Package['ntp'],
source = puppet:///modules/ntp/files/${conf_file},
}
}
# class {'ntp': }
but no matter what I do, it always errors and says it can't find
/etc/puppet/modules/ntp/files/ntp.conf.debian but yet it is there and
readable all the way...
# ls -l /etc/puppet/modules/ntp/files/ntp.conf.debian
-rw-r--r-- 1 root root 535 2011-06-13 12:55
/etc/puppet/modules/ntp/files/ntp.conf.debian
anyway, the output as requested...
Thanks
Craig
# puppet apply -d -e 'include ntp'
info: Loading facts in datacenter
info: Loading facts in datacenter
debug: importing '/etc/puppet/modules/ntp/manifests/init.pp' in environment
production
debug: importing '/etc/puppet/modules/ntp/manifests/ntp.pp' in environment
production
debug: Automatically imported ntp from ntp into production
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Puppet::Type::Package::ProviderUrpmi: file urpmi does not exist
debug: Puppet::Type::Package::ProviderNim: file /usr/sbin/nimclient does not
exist
debug: Puppet::Type::Package::ProviderPkg: file /usr/bin/pkg does not exist
debug: Puppet::Type::Package::ProviderHpux: file /usr/sbin/swinstall does not
exist
debug: Puppet::Type::Package::ProviderYum: file yum does not exist
debug: Puppet::Type::Package::ProviderZypper: file /usr/bin/zypper does not
exist
debug: Puppet::Type::Package::ProviderFink: file /sw/bin/fink does not exist
debug: Puppet::Type::Package::ProviderAptrpm: file rpm does not exist
debug: Puppet::Type::Package::ProviderAix: file /usr/bin/lslpp does not exist
debug: Puppet::Type::Package::ProviderSunfreeware: file pkg-get does not exist
debug: Puppet::Type::Package::ProviderPorts: file /usr/local/sbin/portversion
does not exist
debug: Puppet::Type::Package::ProviderOpenbsd: file pkg_delete does not exist
debug: Puppet::Type::Package::ProviderRug: file /usr/bin/rug does not exist
debug: Puppet::Type::Package::ProviderPortupgrade: file
/usr/local/sbin/portversion does not exist
debug: Puppet::Type::Package::ProviderPortage: file /usr/bin/emerge does not
exist
debug: Puppet::Type::Package::ProviderFreebsd: file /usr/sbin/pkg_delete does
not exist
debug: Puppet::Type::Package::ProviderUp2date: file /usr/sbin/up2date-nox
does not exist
debug: Puppet::Type::Package::ProviderRpm: file rpm does not exist
debug: Puppet::Type::Package::ProviderSun: file /usr/sbin/pkgadd does not
exist
debug: Puppet::Type::Service::ProviderRunit: file /usr/bin/sv does not exist
debug: Puppet::Type::Service::ProviderLaunchd: file /bin/launchctl does not
exist
debug: Puppet::Type::Service::ProviderRedhat: file /sbin/service does not
exist
debug: Puppet::Type::Service::ProviderGentoo: file /sbin/rc-update does not
exist
debug: Puppet::Type::Service::ProviderDaemontools: file /usr/bin/svc does not
exist
debug: Puppet::Type::File::ProviderMicrosoft_windows: feature
microsoft_windows is missing
debug: Creating default schedules
debug: Failed to load library 'shadow' for feature 'libshadow'
debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does
not exist
debug: Puppet::Type::User::ProviderLdap: true value when expecting false
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/puppet]
debug:
Re: [Puppet Users] Geppetto is ready
Hi, thanks for this program. I've just created Gentoo ebuild for Geppetto-1.0.0: https://github.com/Scrill/scrill-overlay/raw/master/app-editors/geppetto/geppetto-1.0.0.ebuild Regards. 21.06.2011 02:38, Henrik Lindberg пишет: Geppetto 1.0 is released and ready for download. We want all the feedback we can get, so try it out and let us know what you think! Full story at: http://cloudsmith.github.com/geppetto/ If you haven’t been following the project, Geppetto is an integrated toolset for working with Puppet modules and manifests. It’s built on the Eclipse platform. If you’re an Eclipse user, you can install it directly into your IDE. If you’re not, it’s also available as ready-to-run zip’s with a much smaller footprint than the full Eclipse. Although we’re calling it “1.0″ (actually “1.0.0″), Geppetto is is probably more mature than many 1.0 releases, and we have invested quite a bit of time in it over the last six months. (Actually, it didn’t come out of nowhere; it builds on work we’ve done in other domains over the last several years.) We released the first beta at FOSDEM 2011 in Brussels in early February, and got lots of really useful feedback there and at PuppetCamp Amsterdam in April. So thanks to everyone who’s offered help and encouragement along the way, with a special shout-out to the people at Puppet Labs. Regards - henrik smime.p7s Description: S/MIME Cryptographic Signature
[Puppet Users] Module in maintenance mode
All, I have a module that I would like to set a variable for, and then if that is variable is set, consider the module (which deploys software), in 'maintenance mode', where it drops out of the module, and moves into the next module, kind of like a return function. Can puppet do that? I don't want to use fail() as it stops ALL puppet processing. Doug. -- 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] Module in maintenance mode
On Jun 21, 2011, at 5:04 PM, Douglas Garstang wrote:
All,
I have a module that I would like to set a variable for, and then if that is
variable is set, consider the module (which deploys software), in
'maintenance mode', where it drops out of the module, and moves into the next
module, kind of like a return function. Can puppet do that? I don't want to
use fail() as it stops ALL puppet processing.
Well, this Pesudo-code should work:
init.pp
class my_module {
$module_is_enabled = true
if( $module_is_enabled ) {
include my_module::content
}
}
content.pp:
class my_module::content {
Put real content here
}
--
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] Module in maintenance mode
Oh... right... of course... Put the logic one level up... That will work. Thanks
On Jun 21, 2011, at 5:54 PM, Patrick kc7...@gmail.com wrote:
On Jun 21, 2011, at 5:04 PM, Douglas Garstang wrote:
All,
I have a module that I would like to set a variable for, and then if that is
variable is set, consider the module (which deploys software), in
'maintenance mode', where it drops out of the module, and moves into the
next module, kind of like a return function. Can puppet do that? I don't
want to use fail() as it stops ALL puppet processing.
Well, this Pesudo-code should work:
init.pp
class my_module {
$module_is_enabled = true
if( $module_is_enabled ) {
include my_module::content
}
}
content.pp:
class my_module::content {
Put real content here
}
--
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.
[Puppet Users] Announce: 2.6.9 Released
This release is a maintenance release of the 2.6.x series of Puppet.
This will likely be the last release in the 2.6.x series for Puppet,
now that 2.7 is out.
It's also a little odd that we have two production releases on the
same day, but that's just how it worked out.
This release is available for download at:
http://puppetlabs.com/downloads/puppet/puppet-2.6.9.tar.gz
See the Verifying Puppet Download section at:
http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet
Please report feedback via the Puppet Labs Redmine site, using an
affected version of 2.6.9
http://projects.puppetlabs.com/projects/puppet/
Release notes found at:
https://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes#2.6.9
= 2.6.9 =
2.6.9 is a maintenance release in the 2.6.x branch.
Notable Fixes and Features
Bug #7127:
A puppet run will now stop if a prerun command fails.
Bug #650
Puppet will now honor symlinks for configuration directories
Feature #2128
Added support for hostname setting based on facts, also get facts
before retrieving the catalog.
Bug #7139
Accept ‘/’ as a valid path in filesets
CHANGELOG
2.6.9
98ba407 (#7127) Stop puppet if a prerun command fails
6996e0b Do not needlessly create multiple reports when creating a transaction
caca469 (#4416) Ensure types are providified after reloading
413b136 (#4416) Always remove old provider before recreating it
98f58ce (#2128) Add WARNING for node_name_{fact,value} descriptions
d9b5c1a (#2128) In-line docs for node_name_{fact,value}
3f0dbb5 (#650) Allow symlinks for configuration directories
1c70f0c (#2128) Add support for setting node name based on a fact
c629958 (#2128) Get facts before retrieving catalog
cd4fe14 (#2128) Add the ability to specify a node name
16b2311 (#6885) puppet agent fingerprint requires --verbose to return a value.
75e2764 (#5318) Always notice changes to manifests when compiling.
8b76be3 (#3836) External nodes should only capture stdout
90eb937 (#7139) Accept '/' as a valid path in filesets
729336e (#6845) Mount writes incorrect vfstab entries
16cf1ac (#6442) Be able to start agents --listen without namespaceauth.conf
0352402 (#3420) Nagios name attribute does not output correctly
f656818 (#4487) When setting environment on a host, ensure it is a string.
c306db2 (#6487) Add some testing for OS X version support in
DirectoryService provider
0008b63 (#6487) Directoryservice provider will fail in future OS releases
6b18f8f Move acceptance tests from puppet-acceptance repo
9a5bf6e Fixed #7166 - Replaced deprecated stomp send method with publish
656eff8 (#4655) Allow stage to be set using a default class parameter
7f658e6 vim: Initial ftplugin and indent support
ccbe9f3 Fixed #6681 - Remove --force-yes option from aptitude is used
--
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.
