Trevor Vaughan | 1 May 04:35 2010

Re: [Puppet Users] Warning message from custom fact


Paul,

This is *completely* shooting from the hip, but I'm guessing that there
may be an issue with the fact files being pulled in as some sort of
dynamically created object.

If this is the case, then what you have below would be trying to
re-declare a constant in the (possibly) Facter namespace.

Try either locally scoping it to your file or sticking a 'self.' in
front of all mentions of REGEX_MAP.

I don't have a system to try it on at the moment, but I'd be curious to
hear if it works.

Otherwise, hitting the puppet-dev list might churn up a more useful answer.

Good luck,

Trevor

On 04/30/2010 11:01 AM, Paul Seymour wrote:
> Hello
> 
> Using a custom fact (see below) generates messages during the puppet
> runs like this any ideas how I can stop it ?:-
> ./ipfacts.rb:32: warning: already initialized constant REGEX_MAP
>  
> 
(Continue reading)

Brian Granger | 2 May 03:18 2010
Picon

[Puppet Users] Re: SSL issues when testing - This is how to fix

Gabriel,

I am running into similar problems in configuring a single client,
single server puppet setup.

> I’ve been suffering all week to fix all manner of SSL issues on my test setup, not realizing that it was my
puppet master where I had made a mistake. I’ve spoken to people in the IRC room for long enough to know that
a lot of people have this problem, so I’ve come up with a quick and dirty hack, that has FIXED all 4 test
setups I built. If you getting that dreaded hostname not matching SSL certificate or other, and your
puppet server IS NOT a production server then you go do what I did ☺
>
> • Okay, first nuke both SSL directories, on puppetmaster and client, I did  #] mv ssl sslbackup
> • Make sure puppet is NOT running on the client
> • Make sure that the puppet master hostname is what you expect it to be, (google change linux hostname, to
be SURE)
> • Add an entry to puppet client host file, to force it to go to the right server – Or you can update your DNS
and wait for it to propagate
> • On client: #] puppetd --waitforcert 60 --test --server host.domainname.com,
> • On server: #] puppetca  –list
> • On the server you should see -- puppetclient.domain.com

This is where I run into problems.  puppetca --list always returns
empty.  I have tried a number of different things (restart the
puppetmaster), remove/reinstall puppetmaster/puppet on client/server.
I don't have a firewall running and my /etc/hosts files are setup
correctly as far as I can tell.

What should I try next?

Cheers,
(Continue reading)

spawn-puppet | 1 May 05:20 2010

Re: [Puppet Users] LF complete recipe bundle

Along this line, I think it would be super useful (for folks new to 
puppet) to have a vmware type image of a working puppet system that 
could be fired up in a player and whose configuration and 
classes/modules were integrated with the documentation.

- Jeff

On 04/29/2010 12:23 PM, Alan McKay wrote:
> Hey folks,
>
> I've seen the recipes page and smatterings of "this-and-that", but
> what I'd really like to see is a big tarball of someone's entire
> /etc/puppet directory on their puppetmaster, to be able to see the
> interactions between all the different components.   What would be
> really useful is seeing this for a small, medium, and large config.
>
> Is there anyone willing to release that, or is there too much
> proprietary info in there?
>
> thanks,
> -Alan
>

--

-- 
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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

(Continue reading)

James Turnbull | 2 May 04:09 2010
Picon

[Puppet Users] Watchers replaces voting...


Hi all

Thanks to Eric Davis we can now sort issues by the number of people
watching them.  This should make it easier to determine who wants
what and how many people want it.

Up until now this was provided via the voting plug-in.  We're going
to replace this plug-in with this approach.  If you are interested
in a ticket or feature and want to ensure your interest is
registered then please start watching the ticket.

We won't remove the Votes plug-in for a while to allow us to
transition from it!

To do this click the Watch link at the top of a particular issue.

Thanks

James Turnbull

--

-- 
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)
Nigel Kersten | 2 May 04:22 2010
Picon

Re: [Puppet Users] Watchers replaces voting...



On Sat, May 1, 2010 at 7:09 PM, James Turnbull <james <at> lovedthanlost.net> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all

Thanks to Eric Davis we can now sort issues by the number of people
watching them.  This should make it easier to determine who wants
what and how many people want it.

huzzah!
 

Up until now this was provided via the voting plug-in.  We're going
to replace this plug-in with this approach.  If you are interested
in a ticket or feature and want to ensure your interest is
registered then please start watching the ticket.

We won't remove the Votes plug-in for a while to allow us to
transition from it!

To do this click the Watch link at the top of a particular issue.

Thanks

James Turnbull

- --
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)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBS9ze5iFa/lDkFHAyAQJiCggAk7yneCdqa6S1Jb+NEEQwPK2Bt4sUM1Hn
dLRnhtCW80/iqU8N8Hr0+MXYBXURn3yEYZcfVUwh7SbvztyV1Iv8zmO5T20LvDov
d7pe9pDeRJR6AaZjT8otaIGg2VRnEI5IJ92oLHrmNCe7l69QL2opVYrgt72cPCWr
7/4cmjWdGia761q9WAhMPPeAEmqYYDSDcZXIi+QGjUs4w9WWznUIkAoDXY9Egdx9
YEuNKMQJeNd1jeXqe83qX9oPrj7AcftzKsX0FTcKR3pAUyJttRLLuhVSMXU+iN9A
eT16X5Y/NZeTZ/JDf0EUG+N50nQzO85SnJH3xd3ALMGWk+QUztYqrw==
=ltSt
-----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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> 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-users <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Michael Stahnke | 2 May 04:52 2010
Picon

Re: [Puppet Users] status of cpan provider?

Something to keep in mind is that if you are making your own package
repo for Perl RPMS (or any other type of package), you may want to try
to get them upstream in a repo.  It's not very difficult to become a
Fedora/EPEL maintainer.  I would assume Debian has methods to manage
packages that also include a fairly low barrier to entry.

Part of the drive of the puppet project is to provide re-usable
infrastructure.  An easy way to do that is get packages we all create
into operating system packages repositories, pending good licenses and
such of course.  That way we can all benefit from these packages.  I
know that I have put over 25 packages into EPEL simply because I
needed them at my day job, and decided if I had to maintain the
package once, I may as well do that for everyone else.

I am certainly not saying there shouldn't be a CPAN provider.  But I
really prefer OS packages.

stahnma

--

-- 
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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

linuxdatacenter | 2 May 06:10 2010
Picon

[Puppet Users] Puppet and systemimager

Hi,

I've written a small tutorial on how to deploy images for puppet using
systemimager. Please check it out:

http://linuxdatacenter.blogspot.com/2010/05/systemimager-puppet.html

-Linuxdatacenter

--

-- 
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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

James Turnbull | 2 May 10:25 2010
Picon

[Puppet Users] ANNOUNCE: Puppet 0.25.5 - Release Candidate 2 available!


Welcome back to the Puppet release cycle for the second outing of
0.25.5 - release candidate number 2.

The 0.25.5 release is a maintenance release in the
0.25.x branch. It contains a number of bug fixes but also
performance enhancements including speed-ups to Puppet's graphing.

The release candidate is available at:

http://puppetlabs.com/downloads/puppet/puppet-0.25.5rc2.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.5rc2.

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.

The default factpath is now $vardir/lib/facter/.

The generate function now sets the working directory to the
directory containing the specified command.

The "warning: Value of 'preferred_serialization_format' ('pson') is
invalid, using default ('yaml')" is now a debug level message.

CHANGELOG

0.25.5rc2
=========
5258a0a  Fixing #3533 - Removing all transaction cleanup
bcde541  Fix for #2910 -- Tidy/matches is too tricky to use
5abe571  Bug #3451: Don't leak the terminus class setting from
Puppet::Resource::Catalog's spec
ebd924c  Fix to the fix for #3295
ce233aa  Write ssh_authorized_keys as user
6739bab  Fix for #3558 -- source file reading speedup
b0e3c61  Fix for #3556 Plussignment value melding
8a30495  Fixed #3655  - Puppet doesn't find installed packages with
portage provider
e4130af  Fixed #3672 - Error message on duplicate fileserver mounts
incorrect
1275a47  conf/redhat: Add notifempty to logrotate config
134204d  Fixed stored configuration documentation
1aa98a6  Fixes #3653 - Changed default factpath value to better
reflect plugins in modules
44f6d64  Partial fix to #2837 - changed warning message to debug
3a1b178  Fix #3555 - fix state of purged lists
f6046ab  Fix for #3577 -- to_yaml parameter in 0.25.5rc1
f351e2d  Renamed all references to Reductive Labs to Puppet Labs
cf7e696  Updated Rake tasks to no longer load puppet.rb
b93924e  Fix #3540 - name methods correctly
9bc2f28  Fixes #3295 - generate() now sets the working directory to
the directory containing the specified command.
3ee6834  Added YARD task
99818ef  Update man pages and partial doc fix to #3491
f988af3  Fixed #3532 - Typo in lib/puppet/ssl/host.rb
f0e12e5  Fix #3496 - suppress transaction debug message

0.25.5rc1
=========
0eea2f5  Updated version and CHANGELOG to 0.25.5rc1
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 (http://tinyurl.com/pronagios)
* Hardening Linux (http://tinyurl.com/hardeninglinux)
Jesús M. Navarro | 2 May 13:52 2010

Re: [Puppet Users] ANNOUNCE: Puppet 0.25.5 - Release Candidate 2 available!

Hi, James:

On Sunday 02 May 2010 10:25:13 James Turnbull wrote:
> Welcome back to the Puppet release cycle for the second outing of
> 0.25.5 - release candidate number 2.
>
> The 0.25.5 release is a maintenance release in the
> 0.25.x branch. It contains a number of bug fixes but also
> performance enhancements including speed-ups to Puppet's graphing.

[...]

> 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.

[...]

> The default factpath is now $vardir/lib/facter/.

Does this mean a default for /var/lib/puppet/lib/facter/ instead 
of /var/lib/puppet/facter/?  Seems a bit weird, doesn't it?

Cheers.

--

-- 
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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

Peter Meier | 2 May 16:57 2010
Picon

Re: [Puppet Users] ANNOUNCE: Puppet 0.25.5 - Release Candidate 2 available!


> Does this mean a default for /var/lib/puppet/lib/facter/ instead 
> of /var/lib/puppet/facter/?  Seems a bit weird, doesn't it?

This change puts the plugins stuff more in line with modules etc.
Additionally, for example other plugins for puppet go then imho into
/var/lib/puppet/lib/puppet

So imho it's a much cleaner way to organize the different plugins.

cheers pete

Gmane