Re: [Puppet Users] Re: Seemingly random failures after 2.7.1 upgrade
done! http://projects.puppetlabs.com/issues/8433 Gus On Fri, Jul 15, 2011 at 7:59 AM, Peter Meier peter.me...@immerda.ch wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 same problem for me.. I've notice the problem on modules using autoloading... I think I will stick to version 2.6.9... can you at least file a detailed bug report? Thanks! Otherwise the situation can't be really improved... ~pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4gHX4ACgkQbwltcAfKi3/GXQCgpZMNyTEiV1USVG1qpxgCh3mE +S8AoJnCLIYreiOg3bXr1zf4u56eZivk =NF0L -END PGP SIGNATURE- -- 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] Re: Seemingly random failures after 2.7.1 upgrade
Hi Trey,
same problem for me.. I've notice the problem on modules using
autoloading...
I think I will stick to version 2.6.9...
Gus
On Thu, Jul 14, 2011 at 8:57 AM, treydock treyd...@gmail.com wrote:
I think the way I posted the contents of the modules may have been
misleading, as I do actually have each class in it's own file so
kvm::host class has it's own host.pp file. So far I've actually
noticed this problem only on my modules that make use of the
autoloading, so each class in it's own *.pp file. Not all my modules
suffer from this, but that's one common thing among the ones that do
fail. I'm in the process of moving my other modules to that layout as
they currently have all classes in init.pp, but interestingly enough
none of those modules have had random failures.
- Trey
On Jul 13, 1:29 am, Peter Meier peter.me...@immerda.ch wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is using an empty class in init.pp problematic ? All of these modules
worked just fine before going from 2.6.8 to 2.7.1.
I have no idea, whether this is the problem. But why do you do:
# manifests/init.pp
import classes/*.pp
class kvm {
}
# manifests/classes/host.pp
class kvm::host {
?
Why not just have one file manifests/host.pp that contains the kvm::host
class? Everything else is not really necessary.
Puppet has quite a powerfull autoloading feature of classes and I think
it can be seen as a general best practice to have one class in a file in
its corresponding path on the filesystem.
With your current way you would need a global import kvm, so that the
init.pp class is actually parsed, so that the files in classes/ are
imported.
If this is not the case and the kvm::host class is not in a file that
can be found by the autoloader it won't find the class.
This becomes even trickier as other hosts can now interfere which
classes are available while compiling the next hosts classes, as an
import statement might only have been executed if Host A is compiled and
only this would then make these imported classes that Host B requires
available.
Actually, I remember that the autoloader should also look into init.pp
for the kvm::host class. But it's possible that something like that
might have changed in 2.7. But I don't know it.
Due to these two reasones (magic availability of classes, possible
changes in how classes become available in 2.7) I would generally
recommend to *not* use import statements and instead use puppet's
autoloading feature. They're rather hard to debug.
~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org/
iEYEARECAAYFAk4dOygACgkQbwltcAfKi39akACcCwslVzxzrTy3/H0r7kGyi4dB
M4gAn1LHtc/LGk7OtbVfDolhm5cXwm/p
=lWHm
-END PGP SIGNATURE-
--
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] Re: Seemingly random failures after 2.7.1 upgrade
Hi Nigel,
here we go...
* all my classes are included (I was still using 0.25.x...)
* In my $confdir/manifests/classes/roles I have a very generic class for all
puppet hosts declared as follow:
class role_puppet_common {
$role = puppet_common
include common
include puppet::common
include puppet::user
}
in $confdir/manifests/site.pp I have the following line...
[...]
import classes/roles/*
[...]
the weird Could not find class problem occurs for class puppet::common
my directory structure is as follow:
...
$confdir/modules/puppet/
$confdir/modules/puppet/manifests
$confdir/modules/puppet/manifests/init.pp
$confdir/modules/puppet/manifests/classes/
$confdir/modules/puppet/manifests/classes/common.pp
...
in $confdir/modules/puppet/manifests/init.pp I have:
import puppet/classes/*
and in $confdir/modules/puppet/manifests/classes/common.pp
class puppet::common {
...
}
* my modulepath declared in puppet.conf is as follow:
modulepath = /mnt/puppet/conf/modules:/mnt/puppet/othermodules
where /mnt/puppet/conf is set to $confdir.
That's it!
As I said before, when I downgraded to version 2.6.9 everything worked fine.
Thanks in advance,
Gus
On Thu, Jul 14, 2011 at 11:59 AM, Nigel Kersten ni...@puppetlabs.comwrote:
On Wed, Jul 13, 2011 at 2:26 PM, Gus gustavosoa...@gmail.com wrote:
Hi!
I've also noticed this (weird) behaviour. I am planning an (huge)
upgrade (from 0.25.x to 2.7.1) in all my puppet's boxes...
I've installed puppet's 2.7.1 gem and got a lot of Could not find
class problem... and everything worked just fine with 0.25.x.
So, I decided to uninstall the gem for version 2.7.1 and install
puppet version 2.6.9.
Everything worked just fine... no weird Could not find class
problem...
am I missing something?
You need to give us a few more details.
* name of the classes that are failing and succeeding autoloading
* How you're declaring the classes (include vs parameterized class
declaration)
* the file paths that contain the classes that fail and succeed
* some info about the modulepath for this environment.
* whether you're using 'import' anywhere.
Thanks in advance,
Gus
On Jul 13, 11:03 am, Nigel Kersten ni...@puppetlabs.com wrote:
On Tue, Jul 12, 2011 at 11:29 PM, Peter Meier peter.me...@immerda.ch
wrote:
Puppet has quite a powerfull autoloading feature of classes and I
think
it can be seen as a general best practice to have one class in a file
in
its corresponding path on the filesystem.
What he said. :)
Life really does become a lot simpler if you avoid 'import' everywhere
you
can and just rely upon the class autoloader.
--
Nigel Kersten
Product Manager, Puppet Labs
Twitter: @nigelkersten
*Join us for **PuppetConf *http://www.bit.ly/puppetconfsig
September 22nd and 23rd in Portland, Oregon, USA.
*
*
--
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.
--
Nigel Kersten
Product Manager, Puppet Labs
Twitter: @nigelkersten
*Join us for **PuppetConf *http://www.bit.ly/puppetconfsig
September 22nd and 23rd in Portland, Oregon, USA.
*
*
--
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] SVN hooks
I am also using some hooks, but for git. I've been using to hooks:
client-side hooks and server-side hooks.
Take a look on this link:
http://projects.puppetlabs.com/projects/puppet/wiki/Puppet%20Version%20Control
Gus
On Thu, Aug 12, 2010 at 6:12 AM, Alexander Kriventsov a...@vl.ru wrote:
12.08.2010 13:03, Jean Baptiste FAVRE пишет:
Hello list,
I'm planning to deploy and use Puppet at work.
For this, I've set up a SVN server to keep track of all changes in
modules manifests.
Reading documentation to be able to define coding rules, I want to put
some SVN hooks to ensure for correct syntax and coding rules respect.
Does anybody here use such scripts ? Are some public version available ?
Or am I wrong going this way ?
You're on a good way.
I'm using pre-commit hook to check syntax on FreeBSD, so you should to
check path
#!/bin/sh
#
# SVN pre-commit hook to check Puppet syntax for .pp files
# Modified from
http://mail.madstop.com/pipermail/puppet-users/2007-March/002034.html
#
REPOS=$1
TXN=$2
tmpfile=`mktemp /tmp/X`
export HOME=/
export PATH=/sbin:/bin:/usr/sbin:/usr/bin
SVNLOOK=/usr/local/bin/svnlook
PUPPET=/usr/local/bin/puppet
$SVNLOOK changed -t $TXN $REPOS | awk '{print $2}' | grep '\.pp$' |
while read line
do
$SVNLOOK cat -t $TXN $REPOS $line $tmpfile
if [ $? -ne 0 ]
then
echo Warning: Failed to checkout $line 2
fi
$PUPPET --color=false --confdir=/tmp --vardir=/tmp --parseonly
--ignoreimport $tmpfile 2
if [ $? -ne 0 ]
then
echo Puppet syntax error in $line. 2
exit 2
fi
done
res=$?
rm -f $tmpfile
if [ $res -ne 0 ]
then
exit $res
fi
Regards,
JB
--
Alexander Kriventsov
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@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] install package based on operatingsystem AND operatingsystemrelease
I've been doing like this. (Don't know if it is the better ways.. but.. :))
if ($operatingsystemrelease = 4) and ($operatingsystemrelease 5) {
$release = el4
}
else {
if ($operatingsystemrelease = 5) and ($operatingsystemrelease 6) {
$release = el5
}
}
package { abc: ensure = 0.25.5-1.${release} }
PS.: I am running puppet 0.25.x in 2.6 I believe there is a elsif or
something like that...
Gus
On Wed, Aug 11, 2010 at 1:52 PM, Nigel Kersten nig...@google.com wrote:
On Wed, Aug 11, 2010 at 9:48 AM, Nan Liu n...@puppetlabs.com wrote:
On Wed, Aug 11, 2010 at 11:55 AM, Jason Amato amato_ja...@yahoo.com
wrote:
How can I create a class to install a RPM based on the o/s type and
the o/s release.
I want to install a package on SLES, but only if it's release 11, not
10.
I suppose you can write nested if statements. Not sure if there are other
more elegant methods. Assuming facter $operatingsystemrelease for SLES 11
returns 11.x, is this what you are looking for?
$os_release = ${operatingsystem}-${operatingsystemrelease}
$pkg = ${os_release} ? {
/^OEL-/ = redhat-lsb,
/^SLES-11./ = lsb,
default = redhat-lsb,
}
package { $pkg:
ensure = installed,
}
Won't that try to install 'redhat-lsb' on SLES 10 ?
I think you want
ensure = undef
for SLES 10 if you truly want to not manage it.
I tend to be more of a fan of explicit conditional statements outside
resource definitions these days, nested selectors are harder to parse
quickly, and now we have decent conditional logic, it's much easier.
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-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
nigel
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@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] exec not finding shell builtins/functions?
+1
On Fri, Jul 30, 2010 at 10:07 AM, Joe McDonagh
joseph.e.mcdon...@gmail.comwrote:
On 07/30/2010 12:18 AM, Daniel Pittman wrote:
James Turnbullja...@puppetlabs.com writes:
Richard Crowley wrote:
On Thu, Jul 29, 2010 at 3:23 PM, Greg Grafgreg.g...@rackspace.com
wrote:
[...]
I saw the same thing happen with a few for-loops and had to wrap them
up in /bin/sh -c '...' for 2.6. Now that I look for it, I can't find
anything about this behavior change in the release notes for 2.6. Was
it coincidental that it ever worked?
See:
http://projects.puppetlabs.com/issues/4288
http://projects.puppetlabs.com/issues/4299
For some history and comments on this. We'd welcome some input into
what you think should be safe and expected behaviour here.
If this is a voting matter, let me put in a vote for passing a simple
string
to the shell, and passing an array direct to exec, which is consistent
with
the use of 'system' style commands in a whole bunch of sysadmin scripting
languages.
Eg, this:
exec { foo: command = ['/bin/ls', '|' 'foo'] }
will pass '|' 'foo' to the ls command, compared to:
exec { foo: command = /bin/ls | foo }
...which passes it to the default system shell.
Daniel
That seems like the implementation would be tricky and error-prone,
compared to having people add sh/bash/ksh -c to the beginning of the command
in the exec. I mean, is that really such a big deal?
--
Joe McDonagh
AIM: YoosingYoonickz
IRC: joe-mac on freenode
When the going gets weird, the weird turn pro.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@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: rollback from 2.6...
What problem did you have with foreman after migrating to 2.6? I am concerned about this.. since I am running a 0.25.x branch o puppet with foreman and I am planning to migrate to 2.6... Thanks in advance, Gus On Mon, Jul 26, 2010 at 2:06 PM, Thomas A. McGonagle mcgona...@gmail.comwrote: Thanks Jeff, Super helpful! -Tom On Jul 26, 2010, at 9:03 AM, CraftyTech wrote: Thanks Jeff, that worked out just fine. Cheers, Henry On Jul 25, 4:33 pm, Jeff McCune j...@puppetlabs.com wrote: On Fri, Jul 23, 2010 at 4:50 PM, CraftyTech hmmed...@gmail.com wrote: Hello, If I installed from source (install.rb), is there a by the book method for rolling back to 25.4? I installed 2.6 and it broke my foreman config and ssl certs, not to mention most of the variables from puppet.conf which are deprecated in the latest version Any suggestions? Remove puppet.rb and puppet/ from the ruby library site_ruby directory. On an enterprise linux based machine, this is: /usr/lib/ruby/site_ruby/1.8 You'll also want to remove the puppet executable from /usr/bin, or wherever it got installed to. Hope this helps, -- Jeff McCunehttp://www.puppetlabs.com/ -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@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] Dashboard or Foreman
IMHO it depend's... if you are just looking for a dashboard.. honestly.. I don't know which one is better... however, If you are looking for more functionallity... than you should take a look on foreman. I am using foreman... The dashboard is nice and I can use foreman as a external node tool :) Cheers, Gus On Wed, Jun 16, 2010 at 3:12 PM, Walter Heck - OlinData.com walterh...@olindata.com wrote: Is there any difference in core-functionality? On Tue, Jun 15, 2010 at 23:44, Eric Shamow eric.sha...@gmail.com wrote: Having tried both I settled on Foreman, although I haven't checked out Puppet-Dashboard after the 1.0 release. Foreman just provides more information, I find, although Puppet-Dashboard looks slightly slicker. Foreman also seems easily hackable/extensible and comes with a nice query tool. -Eric On Tue, Jun 15, 2010 at 12:00 PM, Walter Heck walterh...@gmail.com wrote: Hi Guys, I'm reading about dashboard and foreman, and I'm wondering if there is anyone who made a comparison of the two? Can anyone help me decide which one to use? It feels like foreman is 'ahead' for now? cheers, Walter Heck Engineer @ OlinData (http://olindata.com) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@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: New Foreman release - 0.1-5
the web interface is a 100% better!!! the usability is better as well. Cheers, Gus On Tue, Jun 8, 2010 at 12:37 PM, Ohad Levy ohadl...@gmail.com wrote: there are examples in the extra subdir, and there is even a module which pre-configures it for you :) checkout http://github.com/ohadlevy/puppet-foreman, you would need to edit the init.pp and enable passenger. cheers, Ohad On Tue, Jun 8, 2010 at 10:30 PM, CraftyTech hmmed...@gmail.com wrote: It looks great, good job. Is there going to be instructions for deploying Foreman in a Passenger config? On Jun 7, 8:49 am, Ohad Levy ohadl...@gmail.com wrote: Just following up: Ubuntu package (tested on Ubuntu 10.04) can be found here: http://theforeman.org/attachments/download/109/foreman_0.1.5-1_all.deb RHEL5 packages can be found here: http://theforeman.org/repo/el5/noarch/rubygem-rack-1.0.1-1.noarch.rpmhttp://theforeman.org/repo/el5/noarch/foreman-0.1.5-1.noarch.rpmhttp://theforeman.org/repo/el5/noarch/rubygem-passenger-2.2.2-1.noarc...http://theforeman.org/repo/el5/SRPM/foreman-0.1.5-1.src.rpm Many many thanks to everyone who took part in the huge foreman release (over 100 tickets!) Ohad On Mon, Jun 7, 2010 at 4:22 PM, Ohad Levy ohadl...@gmail.com wrote: I’m happy to announce a new version of Foreman - 0.1-5 Highlights are: *Web interface* Most of the pages have been rewritten, there are many changes: Search options - Hosts (filter based on facts, based on host groups etc - Facts (all hosts with fact x or with value y etc) - Reports (show me all failed reports in the last 3 months etc) - Audits (per user, per type – e.g. all hosts, per action – e.g. delete) Improved Graphs for dashboard and per host Host edit page now has a lot of logic - Class selection depends on your chosen environment - Class selection breaks down into modules, making it easy to navigate - Inherited classes (via hostgroups), are also visible. - Unattended settings will only show selection based on the os (e.g. no debian disk templates will be shown to redhat based os etc). - Clone existing hosts (instead of choosing all of the options again) Perform changes on many hosts at once - change a parameter for many hosts - change host group for many hosts - change environment for many hosts - delete many hosts at once Import new puppetclasses from the interface *Unattended installations* - added support for dynamic disk layout - added kickstart/preseed compatibility with Ubuntu 10.04, RHEL6 beta, Fedora 13 - Support for customized kickstart files (e.g. if you use a package like rpm, you can create your own kickstart which will not be replaced on next update). - medias can now be shared with many operating systems (e.g. with replacing variables for $arch or $version) - x-rhn-provisioning headers support for booting from other devices than eth0 *Query interface* - added verbose mode, which will return all of hosts classes, facts and external node parameters. - added query based on a hostgroup *Others* - Host ownership (via a user or a user group) base infrastructure for per host authorization (e.g. who can change what) and sending the reports to the right people. - Speed optimization when keeping many reports in the db - Puppetdoc integration - Foreman can generate puppetdoc (via a rack task, so you can add it to your repo post commits scripts), and links to the docs via the puppet classes page. - Improved PRM packaging - added startup script for foreman (uses webrick) - moved all config files to /etc/foreman and /etc/sysconfig/foreman - moved log files to /var/log and added logrotate support - moved db files state dir - ... - Added Debian package support - Fact importer now imports the hardware model information Full changelog can be found here: http://theforeman.org/versions/show/7 New rpms should already be available in Foreman repos, Debian package will follow shortly. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com . For
Re: [Puppet Users] Re: storing facter facts in Dashboard.....
I've installed foreman yesterday to play around.. I've have used the tar.gz in the src.rpm file to install it... is it old? Thanks in advance, Gus On Wed, Jun 2, 2010 at 12:28 PM, CraftyTech hmmed...@gmail.com wrote: Sounds great. I'm looking forward to the major release. On May 31, 10:31 am, Ohad Levy ohadl...@gmail.com wrote: You might want to wait for another day or so, as a new major release is just around the corner :) or you can test the release candidate (which seems to be quite stable at the moment). Ohad On Mon, May 31, 2010 at 10:29 PM, CraftyTech hmmed...@gmail.com wrote: Thanks for the feedback. I'll look it into it immediately. Cheers, Henry On May 31, 10:16 am, Ohad Levy ohadl...@gmail.com wrote: Hi, The Foreman supports inventory and many other features - seehttp:// theforeman.org/projects/foreman/wiki/Features Ohad On Mon, May 31, 2010 at 10:14 PM, CraftyTech hmmed...@gmail.com wrote: It can be either Dashboard or any other web interface for Puppet. I'd be great for reporting on current inventory. Has any has gotten this piece to work? Is it an intended feature, or wishful thinking on my part? -- 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.compuppet-users%2bunsubscr...@googlegroups.com puppet-users%2bunsubscr...@googlegroups.compuppet-users%252bunsubscr...@googlegroups.com puppet-users%2bunsubscr...@googlegroups.compuppet-users%252bunsubscr...@googlegroups.com puppet-users%252bunsubscr...@googlegroups.compuppet-users%25252bunsubscr...@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-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com puppet-users%2bunsubscr...@googlegroups.compuppet-users%252bunsubscr...@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-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@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] Fabric vs ControlTier
I am using Fabric for deployment and also to automate the installation of a puppet master server and puppet client servers. I have nothing to complain about it. Cheers, Gus On Thu, Apr 15, 2010 at 4:53 PM, Michael DeHaan mich...@puppetlabs.comwrote: On Thu, Apr 15, 2010 at 4:17 AM, SyRenity stas.os...@gmail.com wrote: Hi. While this not entirely related question to Puppet, I noticed many hear use Fabric for deployments and remote control. I'm currently checking a tool called ControlTier (namely ct_exec), as Fabric doesn't currently run on my CentOS machine. Can anyone say about the difference between these 2 deployment tools? Regards. I'll throw a couple more into the mix --- Func also runs on your CentOS machine and can use Puppet certs in the latest source version. http://fedorahosted.org/func (which I helped write) There's also Capistrano and mcollective. (And a lot of distributed ssh tools on the side.) I don't like to look at these as deployment tools -- I strongly prefer packaging applications properly and pushing them out with Puppet, but it's good for ad-hoc tasks like power these off now, or initiate OS reinstall.Func was really designed to be a reusable component for building secure remote applications, as we wrote one and found there wasn't a good framework to use for that. Where you don't want packages, take a look at using something like http://github.com/reductivelabs/puppet-vcsrepo to check out code from source, right on your puppet managed machines. --Michael -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@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] ANNOUNCE: Puppet 0.25.5 - Release Candidate 1 available!
Hi, I would like confirm if the bug #3182 will be solved in the 0.25.5 final release (I am asking this because I didn't saw it in the changelog of the RC1). Thanks in advance, Gus On Thu, Apr 1, 2010 at 3:22 AM, James Turnbull ja...@lovedthanlost.netwrote: Welcome back to the Puppet release cycle - brought to you by the newly minted Puppet Labs. The 0.25.5 release is a maintenance release in the 0.25.x branch. It contains a number of bug fixes but also some performance enhancements including speed-ups to Puppet's graphing. The release candidate is available at: http://puppetlabs.com/downloads/puppet/puppet-0.25.5rc1.tar.gz Please note that all final releases of Puppet are signed with the Reductive Labs key (we'll issue a new, improved Puppet Labs key after the Rowlf release). See the Verifying Puppet Download section at http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please test this release candidate and report feedback via the Puppet Labs Redmine site: http://projects.puppetlabs.com Please select an affected version of 0.25.5rc1. RELEASE NOTES The default location for Puppet's dynamic files, the $vardir option, has changed from /var/puppet to /var/lib/puppet. This is already the default for the Fedora EPEL and Debian/Ubuntu packages and brings Puppet into FHS compliance. You can now specify checksum = none in the file type to disable file check-summing. CHANGELOG 57ae381 Modify SuSE spec file for 0.25.x and correct shebang lines for puppetd/puppetmasterd d90ec79 Fixes #3460 - Makes Puppet FHS compliant by moving /var/puppet to /var/lib/puppet ae0b0bf Fix for #3101 (bug in MRI 1.8.7) 9db066b Fixes #3419. OS X 10.6 Ruby doesn't set supplementary groups 306d082 Revert the guts of #2890 4eea77a Fail gracefully on packages that don't have the HOMEPAGE variable set (e.g. dev-lang/php). f5b8494 Fixed #3443 - Typo in mount type b0ef2c6 Fixes #3135 - darwin doesn't support 'mount -o remount' 7018cf5 Adding :catalog_terminus setting 978ab8a fixing obsolete comment in puppetd 6d13d0d Adding support for only using cached catalogs bc28715 Refactoring Configurer to enable the next feature ba43d7b Fix for #3366 - --tags '' treated as boolean 'true' 5ab5e8a Supressing warnings (not really failures) in test/unit e4df0b0 Fix test using wrong Puppet util filesetting group eeb3d74 Mock user in SUIDManager tests 9ea27db Removing resources generate tests 218e3e9 Removing old test for service/debian provider 1556938 Replace test/unit file write test with spec 2defc00 Fix for #3424 and tests to prove it. 44798b9 Fixed changelog Rake task 5d10f65 Fix #3155 - prevent error when using two matching regex in cascade fbedb99 Fixing #3148 Settings#without_noop when run with no noop setting 389c77b Another trivial follow-up fix for #2604: invalid path to zaml.rb 56b5753 Fix inefficient SimpleGraph#matching_edge 4b2b9eb Fix #3229 - use original value in case/selector regex matching 19863c0 Fix #2929 - Allow checksum to be none fd76142 Fixed puppetlast typo 3b4e782 Follow up for #2604, debug msg left behind. e44430b Fix for #2604 Pure Ruby yaml generation 74cd55f Fixes #3113 - When importing a manifest puppet needs to chill 7ec50a7 Fixes #3387 - Handle path elements with ticks and spaces d561a98 Fix for #3412 install.rb should not put . first in the tmp_dirs 751df45 Fix #3186 - require function set relationship only on the last class a1d216c Fixed the return types were valid, and removed the copy paste error with the exception logic d532e6d Fixing #3185 Rakefile is loading puppet.rb twice 5aa596c Fix #3150 - require function doesn't like ::class syntax 3457b87 Added time module to tagmail report 71653a7 Fixed #3162 - tidy does not remove empty files when size = 0 is set efd0f76 Fixed #3128 - Updated man pages and moved puppet.conf.8 to puppet.conf.5 ad4f94a Add version number to puppetlast display. 0533cea Forgot fakedata called in spec 6416f91 Fixing #2669 puppetmasterd integration has leaky state 8a3a205 Fix for #2327, check the return types from augeas and fail where appropriate 2ae7516 2047: Add a not_include into match 55f6239 Minor unit test fixes b7b7a1c vim: Improve function matching when functions contain ')' b3c363c vim: puppetDefArguments is contained by puppetDefine f9e05a8 Fix for #3094 (libdir should take : delimited path) b473264 Fix #1842 Net::HTTP#enable_post_connection_check doesn't work anymore 9419c2b Fix for #3035 (redhat services use init for source) 10becce Fix for #3077 (unit tests broken in 0.25.1--0.25.4) 49a7185 Fix for #3085 (user_role_add pulls from same source as useradd) 1f086c2 Fix for #3114 (ruby's arbitrary limit on process groups too low) Regards James Turnbull -- Author of: * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0
[Puppet Users] broken image links on puppet-dashboard tour documentation
Hi! I don't know if here is the right place to say this, but the puppet-dashboard tour webpage ( http://www.puppetlabs.com/blog/a-tour-of-puppet-dashboard-0-1-0/) seems to have some broken image links. Thanks in advance, Gus -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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 with mysql user not root
I don't know which OS you are using, but maybe
you should take a look on this post
http://zcentric.com/2010/03/11/install-puppet-dashboard-on-redhatcentos-5/
Cheers,
Gus
On Wed, Apr 7, 2010 at 2:46 PM, Asif Iqbal vad...@gmail.com wrote:
On Wed, Apr 7, 2010 at 1:31 PM, Asif Iqbal vad...@gmail.com wrote:
Hi All
I am trying to install puppet dashboard and it is failing like this
r...@sys-ubuntu { ~/puppet-dashboard }$ rake install
(in /home/iqbala/puppet-dashboard)
Couldn't create database for {encoding=utf8, username=root,
adapter=mysql, database=dashboard_development}, charset:
utf8, collation: utf8_unicode_ci (if you set the charset manually,
make sure you have a matching collation)
-- create_table(assignments, {:force=true})
rake aborted!
Access denied for user 'root'@'localhost' (using password: NO)
(See full trace by running task with --trace)
I like to grant a non root user to create a database with a password .
What file to change on puppet dashboard to achieve that?
found it. config/database.yml
--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@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] REST API for puppet
Ok, thanks. I'll check the code too. Gus --- Original message --- From: James Turnbull ja...@lovedthanlost.net To: puppet-users@googlegroups.com Sent: 30.3.'10, 22:58 On 31 March 2010 11:36, Paul Lathrop paul.lath...@gmail.com wrote: It does exist! Sadly, the documentation is the code, as far as I've been able to determine. You can get a fair amount of information if you are using a webserver like Apache in front of puppetmasterd by watching your access logs. Paul's quite right - the docs are currently the Code. It's on the radar (because I also nagged Luke et al about it) to do a simple explanation of the API along the lines of: URL - /environment/blah/blah Post/Get Payload in JSON, etc There is a ticket for this you can +1 or vote for: http://projects.reductivelabs.com/issues/3016 Cheers James -- Author of: * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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-us...@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] REST API for puppet
ok, I will do that. I am using apache + passenger. Thanks. On Wed, Mar 31, 2010 at 12:05 PM, Brice Figureau brice-pup...@daysofwonder.com wrote: On Wed, 2010-03-31 at 07:29 -0700, Nigel Kersten wrote: On Wed, Mar 31, 2010 at 7:19 AM, Brice Figureau brice-pup...@daysofwonder.com wrote: On Wed, 2010-03-31 at 10:45 -0300, Gustavo Soares wrote: Ok, thanks. I'll check the code too. You can also have a look to the auth.conf file which lists most of the REST urls. I found that using ssldump to sniff the connection traffic was quite illuminating as you need to set the Accept header at least appropriately. ie GET /production/file_metadatas/plugins?links=managerecurse=true ignore=---+%0A-+.svn%0A-+CVS%0A-+.git%0A HTTP/1.1 -- Accept: pson, b64_zlib_yaml, yaml, marshal, raw If you use nginx or apache as a front-end SSL termination, you can grep your access log files for the same result (except of course access to the headers). -- Brice Figureau Follow the latest Puppet Community evolutions on www.planetpuppet.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-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@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] REST API for puppet
Hello everyone! Is there any REST API avaiable for puppet? In the documentation page ( http://docs.puppetlabs.com/) there is a message saying that the doc will be comming soon.. but I am in doubt... the REST API exists, but it is not documented or it does not exist? If it exists, does anyone know what can kind of thing can be done with the API? Thanks in advance, Gus -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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] sharing variables between definitions
I have thought of using qualified variables, but i think that won't work
inside a tempalte, right? Or can I do %= class::variable % ?
And I guess that if I am using dynamic variables, once I include the it
will be evaluated only once, right?
Gus
--- Original message ---
From: Michael Gliwinski michael.gliwin...@henderson-group.com
To: puppet-users@googlegroups.com
Sent: 25.3.'10, 6:46
On Wednesday 24 Mar 2010 22:15:27 Michael DeHaan wrote:
On Wed, Mar 24, 2010 at 5:51 PM, Gustavo Soares
gustavosoa...@gmail.comwrote:
Hi, Michael! thanks for your reply!
actually it is the opposite.. :) i.e, I want to use the same variable,
but in different definitions...
Ok, sorry for the confusion.
I would have thought $common_variables::x would have worked to
reference
something in a parent, but it does not.
Perhaps someone else can share a workaround as I'm not too familiar with
scoping in this case.
I know you can do variables at top scope or through your external nodes
classifier, but that is not ideal.
--Michael
IIRC you also need to 'include' the class within the define, then
qualified
variables (like ${class::variable}) should work. YMMV, these kinds of
things
have always caused enough issues to drive me crazy, but definitely
possible.
--
Michael Gliwinski
Henderson Group Information Services
9-11 Hightown Avenue, Newtownabby, BT36 4RT
Phone: 028 9034 3319
***
***
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee and access to the
email by anyone else is unauthorised.
If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on it,
is prohibited and may be unlawful.
When addressed to our clients, any opinions or advice contained in this
e-mail are subject to the terms and conditions expressed in the governing
client engagement leter or contract.
If you have received this email in error please notify
supp...@henderson-group.com
John Henderson (Holdings) Ltd
Registered office: 9 Hightown Avenue, Mallusk, County Antrim, Northern
Ireland, BT36 4RT.
Registered in Northern Ireland
Registration Number NI010588
Vat No.: 814 6399 12
***
**
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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-us...@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] sharing variables between definitions
Hi, Michael, thank you for your reply.
What I mean about dynamic variables is:
let's say that I have a variable like *$log_path = /var/log/$site *to
specify the log path for different applications
that run on the same host. Thus, depending on the value of $site
variable, the $log_path variable will be different.
If I put that in a class, it will be evaluated for the first value of $site
called, right? or am I missing something?
I hope, that I could clarify. :)
Gus
On Thu, Mar 25, 2010 at 9:54 AM, Michael Gliwinski
michael.gliwin...@henderson-group.com wrote:
On Thursday 25 Mar 2010 11:48:44 Gustavo Soares wrote:
I have thought of using qualified variables, but i think that won't work
inside a tempalte, right? Or can I do %= class::variable % ?
It will but you have to use %= scope.lookup('class::variable') % (note,
typing from memory, to be sure check the puppet templating page on the
wiki,
there is an example there).
And I guess that if I am using dynamic variables, once I include the it
will be evaluated only once, right?
I'm not sure what you mean by dynamic variables, but the class is indeed
evaluated only once (and therefore variables are bound only once IIUC),
even
though it is included from a define which may be declared (i.e. 'called'?)
multiple times.
--
Michael Gliwinski
Henderson Group Information Services
9-11 Hightown Avenue, Newtownabby, BT36 4RT
Phone: 028 9034 3319
**
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee and access to the email
by anyone else is unauthorised.
If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on it,
is prohibited and may be unlawful.
When addressed to our clients, any opinions or advice contained in this
e-mail are subject to the terms and conditions expressed in the governing
client engagement leter or contract.
If you have received this email in error please notify
supp...@henderson-group.com
John Henderson (Holdings) Ltd
Registered office: 9 Hightown Avenue, Mallusk, County Antrim, Northern
Ireland, BT36 4RT.
Registered in Northern Ireland
Registration Number NI010588
Vat No.: 814 6399 12
*
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@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] sharing variables between definitions
well, forget what I said.. It seems that I have misunderstood the variable
scope...
I will try to do as you suggest.
Thanks!
On Thu, Mar 25, 2010 at 10:42 AM, Gustavo Soares gustavosoa...@gmail.comwrote:
Hi, Michael, thank you for your reply.
What I mean about dynamic variables is:
let's say that I have a variable like *$log_path = /var/log/$site *to
specify the log path for different applications
that run on the same host. Thus, depending on the value of $site
variable, the $log_path variable will be different.
If I put that in a class, it will be evaluated for the first value of $site
called, right? or am I missing something?
I hope, that I could clarify. :)
Gus
On Thu, Mar 25, 2010 at 9:54 AM, Michael Gliwinski
michael.gliwin...@henderson-group.com wrote:
On Thursday 25 Mar 2010 11:48:44 Gustavo Soares wrote:
I have thought of using qualified variables, but i think that won't work
inside a tempalte, right? Or can I do %= class::variable % ?
It will but you have to use %= scope.lookup('class::variable') % (note,
typing from memory, to be sure check the puppet templating page on the
wiki,
there is an example there).
And I guess that if I am using dynamic variables, once I include the it
will be evaluated only once, right?
I'm not sure what you mean by dynamic variables, but the class is indeed
evaluated only once (and therefore variables are bound only once IIUC),
even
though it is included from a define which may be declared (i.e. 'called'?)
multiple times.
--
Michael Gliwinski
Henderson Group Information Services
9-11 Hightown Avenue, Newtownabby, BT36 4RT
Phone: 028 9034 3319
**
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee and access to the email
by anyone else is unauthorised.
If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on it,
is prohibited and may be unlawful.
When addressed to our clients, any opinions or advice contained in this
e-mail are subject to the terms and conditions expressed in the governing
client engagement leter or contract.
If you have received this email in error please notify
supp...@henderson-group.com
John Henderson (Holdings) Ltd
Registered office: 9 Hightown Avenue, Mallusk, County Antrim, Northern
Ireland, BT36 4RT.
Registered in Northern Ireland
Registration Number NI010588
Vat No.: 814 6399 12
*
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@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] sharing variables between definitions
Hi everybody!
I would like to share a group of variables between definitions and I don't
know what it is the best approach to do this...
First, let me explain the situation...
I were using a class and defining those variables inside of it.. then I
used inheritance to this class to
get the variables instantiated.
For instance:
class common_variables {
$a_var = hello world
}
class class_a inherits common_variables {
notice($a_var)
}
class class_b inherits common_variables {
notice($a_var)
}
The problem, is since class are singletons, I can't do that in a situation
where need to have
multiple instances of class_a and class_b on in a host. So, I am trying to
implement the
same logic using definitions, but after reading the language tutorial at
puppet's official
wiki, I still haven't found a nice way to do.
One solution would be to put the definition of
$a_var inside boths defines, but I didn't like to do that. Has anyone
experienced a problem
like this? what would it be the best approach and the right way to do it?
Thanks in advance,
Gus
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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] sharing variables between definitions
Hi, Michael! thanks for your reply!
actually it is the opposite.. :) i.e, I want to use the same variable, but
in different definitions...
Using classes, I can accomplish that using class inheritance, but with
definitions.. I have no clue...
Just to clarify the reason of that...
1) I have a couple of common variables
2) I have a define A
2) I have a define B
I need to have multiple instances of objects defined in define A in one host
and multiple instances of objects defined in define B
on another host, but both define (A and B) share a couple of variables...
Using classes this is pretty straight forward, but since classes
are singleton, I need to use Definitions and I don't know how to do that
without putting the shared variables in each definition.
I hope, I have managed to clarify the issue.
Cheers,
Gus
On Wed, Mar 24, 2010 at 6:22 PM, Michael DeHaan
mich...@reductivelabs.comwrote:
On Wed, Mar 24, 2010 at 5:11 PM, Michael DeHaan mich...@reductivelabs.com
wrote:
On Wed, Mar 24, 2010 at 3:10 PM, Gustavo Soares
gustavosoa...@gmail.comwrote:
Hi everybody!
I would like to share a group of variables between definitions and I
don't know what it is the best approach to do this...
First, let me explain the situation...
I were using a class and defining those variables inside of it.. then I
used inheritance to this class to
get the variables instantiated.
For instance:
class common_variables {
$a_var = hello world
}
class class_a inherits common_variables {
notice($a_var)
}
class class_b inherits common_variables {
notice($a_var)
}
If I understand this correctly, you'd like to use different variables with
the same definitions?
This sends 5 as a notice value:
class base {
$x=3
define yell($what) {
notice($what)
}
}
class outera inherits base {
$x=4
base::yell { some title : what = $x }
}
class outerb inherits base {
$x=5
base::yell { some title : what = $x }
}
Sorry for the confusion --
I'm missing a include base at the very bottom of my example.
If that's not what you meant about variables in defines, please clarify.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@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: migating from 0.24.8 to 0.25.0rc1
sorry for the late reply :) but yes, I have switched to passenger. Gus On Tue, Sep 29, 2009 at 5:22 PM, Chris Westin cwes...@yahoo.com wrote: I'm getting similar messages about cacrl, even though I haven't set it. Did switching to passenger fix the problem? Or did you find another way to fix it? I'm using webrick and don't want to complicate things further for now if I don't have to. Chris --~--~-~--~~~---~--~~ 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.compuppet-users%2bunsubscr...@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-us...@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] managing gem files with puppet
I am using version 0.25.1, but I have also noticed that in the previous one.
I have not tested with latest released, but according the change log, I am
not sure if it will solve this issue.
Gus,
On Fri, Feb 5, 2010 at 2:16 PM, Dan Bode d...@reductivelabs.com wrote:
what version does this occur on?
On Wed, Feb 3, 2010 at 11:52 AM, Gustavo Soares
gustavosoa...@gmail.comwrote:
Hi everyone!!
I have noticed that if I am managing gem files with puppet ensuring a
specific version and the system has the gem 2 versions of that gem
installed, including the version that I am managing, puppet doesn't identify
that I have that gem installed.
For example:
package { fastthread:
ensure = 1.0.5,
provider = gem,
}
and on the server I have:
[pup...@localhost init.d]$ gem list | grep fastthread
fastthread (1.0.7, 1.0.5)
puppet says: (I am running puppet with --noop flag)
Feb 3 17:50:32 riovld37 puppetd[15489]:
(//gem::fastthread/Package[fastthread]/ensure) is 1.0.7, should be 1.0.5
(noop)
shouldn't puppet be aware that I have the package installed?
Thanks in advance,
Gus
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@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] ssh_authorized_key creating multiple entries on repeated runs
what version of puppet are running? I faced this problem with puppet 0.24.8,
but since I have updated to the 0.25.x release that I don't have this
problem anymore.
Gus
On Wed, Feb 10, 2010 at 7:03 AM, Peter Meier peter.me...@immerda.ch wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
Newbie here. Question regarding the reference type
ssh_authorized_key. Is this part of the designed behaviour?
I have:
ssh_authorized_key { someuser:
ensure = present,
key = some id_rsa.pub key,
type = ssh-rsa,
user = someuser
}
It keeps appending to /home/someuser/.ssh/authorized_keys
I assume the key param looks like ssh-rsa AAA. ? Afaik the
described behavior is the one you get if you do that. Don't add the
whole content, just add the key.
Is this the best way to manage 1 or 2 admin type of users in the
system?
imho definitely. I do it with up to 10...
cheers pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAktydkwACgkQbwltcAfKi3+jWwCdHdm+e3EAIXE1SvdUl4BegDOZ
vZYAoJyDXr34V33Y2pb6vHgopzoWV4c8
=OaJf
-END PGP SIGNATURE-
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@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-us...@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] managing gem files with puppet
Hi everyone!!
I have noticed that if I am managing gem files with puppet ensuring a
specific version and the system has the gem 2 versions of that gem
installed, including the version that I am managing, puppet doesn't identify
that I have that gem installed.
For example:
package { fastthread:
ensure = 1.0.5,
provider = gem,
}
and on the server I have:
[pup...@localhost init.d]$ gem list | grep fastthread
fastthread (1.0.7, 1.0.5)
puppet says: (I am running puppet with --noop flag)
Feb 3 17:50:32 riovld37 puppetd[15489]:
(//gem::fastthread/Package[fastthread]/ensure) is 1.0.7, should be 1.0.5
(noop)
shouldn't puppet be aware that I have the package installed?
Thanks in advance,
Gus
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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] Duplicate parameter 'require'
Hi!!
I was using puppet 0.24.8 and I have recently upgraded to version 0.25.1. (I
am using puppet + passenger configuration)
I have noticed that when I have to requires in a manifest, the following
error is raised:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Duplicate parameter 'require'
here is an example (extracted from
http://projects.reductivelabs.com/issues/2736):
ssh_authorized_key { authkeypuppet:
user = puppet,
key = A,
type = ssh-rsa,
name = w...@noc,
ensure = present,
require = User[puppet],
require = File[/var/lib/puppet/.ssh],
target = /var/lib/puppet/.ssh/authorized_keys2
}
am I missing something? This kind of definition was working...
Thanks in advance,
Gus
--~--~-~--~~~---~--~~
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: Duplicate parameter 'require'
all right! that explains everything! I've tried to find any example like yours (require = [ User[puppet], File[/var/lib/puppet/.ssh] ]) on the wiki, but I hadn't found. thank you!! On Wed, Nov 4, 2009 at 4:01 PM, R.I.Pienaar r...@devco.net wrote: Hello, - Gustavo Soares gustavosoa...@gmail.com wrote: Hi!! I was using puppet 0.24.8 and I have recently upgraded to version 0.25.1. (I am using puppet + passenger configuration) I have noticed that when I have to requires in a manifest, the following error is raised: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Duplicate parameter 'require' snip require = User[puppet], require = File[/var/lib/puppet/.ssh], target = /var/lib/puppet/.ssh/authorized_keys2 snip am I missing something? This kind of definition was working... Actually it wasn't working at all. What would happen in the past is that only the 2nd require would be taken, the first would be silently ignored and not do what you intended at all. The parser now help you pick up this kind of mistake, the right syntax is: require = [ User[puppet], File[/var/lib/puppet/.ssh] ] -- R.I.Pienaar --~--~-~--~~~---~--~~ 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: migating from 0.24.8 to 0.25.0rc1
Larry, for now I haven't setup apache + passenger yet. I was running some tests in a lab environment first with the builtin webserver (I believe that it is Webrick, right?) and then I would setup passenger to increase sacalability. I must use passenger in 0.25.x? Gus On Thu, Aug 20, 2009 at 10:04 AM, Larry Ludwig la...@reductivelabs.comwrote: On Aug 19, 2009, at 3:42 PM, Gustavo Soares wrote: Hi all! I have migrated some machines from puppet 0.24.8 to 0.25.0rc1, mainly because of bug in 0.24.8 when using ssh_authorized_keys and I am getting the following messages when starting the client: Setting the :cacrl to 'false' is deprecated; Puppet will just ignore the crl if yours is missing Starting Puppet client version 0.25.0 Cached certificate_revocation_list for ca failed: Cannot manage the CRL when :cacrl is set to false Could not retrieve catalog from remote server: Could not intern from s: Cannot manage the CRL when :cacrl is set to false Hi Gus, How is your Puppetmaster setup? Passenger? Can you send your apache config? -L -- Larry Ludwig Reductive Labs --~--~-~--~~~---~--~~ 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: migating from 0.24.8 to 0.25.0rc1
thanks Pete.. I will use passenger for sure... I were beginning to think that the problem that I face when migrating from 0.24.8 to 0.25.0rc1 (which I had already rolled back) was somehow connected to Webrick.. but I guess not... Cheers On Thu, Aug 20, 2009 at 4:27 PM, Peter Meier peter.me...@immerda.ch wrote: Hi for now I haven't setup apache + passenger yet. I was running some tests in a lab environment first with the builtin webserver (I believe that it is Webrick, right?) and then I would setup passenger to increase sacalability. I must use passenger in 0.25.x? no, you can still use webrick for smaller setups or mongrel cluster for setups with more nodes, if you don't want to use passenger. however passenger is getting more and more the default way to run puppetmaster. cheers pete --~--~-~--~~~---~--~~ 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] migating from 0.24.8 to 0.25.0rc1
Hi all! I have migrated some machines from puppet 0.24.8 to 0.25.0rc1, mainly because of bug in 0.24.8 when using ssh_authorized_keys and I am getting the following messages when starting the client: Setting the :cacrl to 'false' is deprecated; Puppet will just ignore the crl if yours is missing Starting Puppet client version 0.25.0 Cached certificate_revocation_list for ca failed: Cannot manage the CRL when :cacrl is set to false Could not retrieve catalog from remote server: Could not intern from s: Cannot manage the CRL when :cacrl is set to false However, if I run puppetd with -tvd, everything works fine. I have no idea why this is going on if anyone could help I would apreciate. Thanks in advance, Gus --~--~-~--~~~---~--~~ 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: reports file created with gmt time
Hi ohad! I mean the filename created on disk. Cheers, Gus 2009/8/15, Ohad Levy ohadl...@gmail.com: Hi, I'm not sure I follow, I checked both puppet report files, node and facts file and they all contain the local time. do you mean the mtime of the file itself? Ohad On Sat, Aug 15, 2009 at 4:41 AM, Gustavo Soares gustavosoa...@gmail.comwrote: Hi All! Maybe it is a dummy question, but I was wondering if is there any reason to use gmt time and not the currently time on the machine for the reports files generated on disk when using store config ( http://reductivelabs.com/trac/puppet/wiki/ReportReference)? I am using puppet 0.24.8. Thanks in advance, Gus -- Enviado do meu celular --~--~-~--~~~---~--~~ 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] reports file created with gmt time
Hi All! Maybe it is a dummy question, but I was wondering if is there any reason to use gmt time and not the currently time on the machine for the reports files generated on disk when using store config ( http://reductivelabs.com/trac/puppet/wiki/ReportReference)? I am using puppet 0.24.8. Thanks in advance, Gus --~--~-~--~~~---~--~~ 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: Puppetshow problem - ActionView::TemplateError
Apparently the problem is due to the version of ruby that I am using
(1.8.7)... (I must say that my experience in programming ruby is not that
much...)
I found the solution in this post (
http://railsforum.com/viewtopic.php?id=27226), which says to add the
following code to the environment.rb
unless '1.9'.respond_to?(:force_encoding)
String.class_eval do
begin
remove_method :chars
rescue NameError
# OK
end
end
end
I will try this on and see how it goes..
Cheers,
Gus
On Wed, Aug 12, 2009 at 11:40 AM, Gus gustavosoa...@gmail.com wrote:
Hi all!
I am running some tests with puppet (0.24.8) and puppetshow.
Right now I am struggling to put puppetshow to run. I have just
discovered the right gem versions that I should install (http://
groups.google.com/group/puppet-users/browse_thread/thread/
f41ce288f49d1cb?pli=1http://groups.google.com/group/puppet-users/browse_thread/thread/%0Af41ce288f49d1cb?pli=1)
.. but now I am getting the following error
when I try access the main page.
ActionView::TemplateError (undefined method `[]' for
#Enumerable::Enumerator:0xb76eaad4) on line #3 of vendor/plugins/
active_scaffold/frontends/default/views/_list_header.rhtml:
1: % if active_scaffold_config.action_links.any? { |link| link.type
== :table } -%
2: div class=actions
3: % new_params = params_for(:action = :table) %
4: % active_scaffold_config.action_links.each :table do |link| -
%
5: % next if controller.respond_to? link.security_method and !
controller.send(link.security_method) -%
6: %= render_action_link(link, new_params) -%
vendor/rails/activesupport/lib/active_support/core_ext/string/
access.rb:43:in `first'
vendor/plugins/active_scaffold/lib/helpers/view_helpers.rb:104:in
`params_for'
vendor/plugins/active_scaffold/frontends/default/views/
_list_header.rhtml:3:in
`_run_erb_47vendor47plugins47active_scaffold47frontends47default47views47_list_header46rhtml'
vendor/rails/actionpack/lib/action_view/base.rb:637:in `send'
vendor/rails/actionpack/lib/action_view/base.rb:637:in
`compile_and_render_template'
vendor/rails/actionpack/lib/action_view/base.rb:365:in
`render_template'
vendor/rails/actionpack/lib/action_view/base.rb:316:in
`render_file_without_dryml'
vendor/plugins/hobo/lib/action_view_extensions/base.rb:7:in
`render_file'
vendor/rails/actionpack/lib/action_view/base.rb:331:in
`render_without_active_scaffold'
vendor/plugins/active_scaffold/lib/extensions/
action_view_rendering.rb:60:in `render'
vendor/rails/actionpack/lib/action_view/partials.rb:120:in
`render_partial_without_active_scaffold'
vendor/plugins/active_scaffold/lib/extensions/
action_view_rendering.rb:70:in `render_partial'
vendor/rails/actionpack/lib/action_view/base.rb:352:in
`render_without_active_scaffold'
vendor/plugins/active_scaffold/lib/extensions/
action_view_rendering.rb:60:in `render'
vendor/plugins/active_scaffold/frontends/default/views/list.rhtml:
3:in
`_run_erb_47vendor47plugins47active_scaffold47frontends47default47views47list46rhtml'
vendor/rails/actionpack/lib/action_view/base.rb:637:in `send'
vendor/rails/actionpack/lib/action_view/base.rb:637:in
`compile_and_render_template'
vendor/rails/actionpack/lib/action_view/base.rb:365:in
`render_template'
vendor/rails/actionpack/lib/action_view/base.rb:316:in
`render_file_without_dryml'
vendor/plugins/hobo/lib/action_view_extensions/base.rb:7:in
`render_file'
vendor/rails/actionpack/lib/action_controller/base.rb:1100:in
`render_for_file_without_dryml'
vendor/plugins/hobo/lib/hobo/dryml/template_handler.rb:71:in
`render_for_file'
vendor/rails/actionpack/lib/action_controller/base.rb:858:in
`render_with_no_layout'
vendor/rails/actionpack/lib/action_controller/base.rb:872:in
`render_with_no_layout'
vendor/rails/actionpack/lib/action_controller/layout.rb:270:in
`render_without_benchmark'
vendor/rails/actionpack/lib/action_controller/benchmarking.rb:
51:in `render_without_active_scaffold'
/opt/local/lib/ruby/1.8/benchmark.rb:293:in `measure'
vendor/rails/actionpack/lib/action_controller/benchmarking.rb:
51:in `render_without_active_scaffold'
vendor/plugins/active_scaffold/lib/extensions/
action_controller_rendering.rb:13:in `render_without_hobo_model'
vendor/plugins/hobo/lib/hobo/model_controller.rb:558:in `render'
vendor/plugins/active_scaffold/lib/actions/list.rb:13:in `table'
vendor/rails/actionpack/lib/action_controller/base.rb:1158:in
`send'
vendor/rails/actionpack/lib/action_controller/base.rb:1158:in
`perform_action_without_filters'
vendor/rails/actionpack/lib/action_controller/filters.rb:697:in
`call_filters'
vendor/rails/actionpack/lib/action_controller/filters.rb:689:in
`perform_action_without_benchmark'
vendor/rails/actionpack/lib/action_controller/benchmarking.rb:
68:in `perform_action_without_rescue'
