Re: [Puppet Users] Removal of CentOS 8 Support

[Peter Meier]

Hi

Great questions! I'm adding Margaret Lee, one of our Product Managers, 
to help get your questions answered. She'll be back from PTO on Monday! 
Thanks.


Just to re-iterate what I brought up a few months ago: It would be very 
welcoming, when Puppet ships at least a "supported" agent (or at least 
an installable as preview) as early as possible for CentOS Stream 9.


This would allow other communities (e.g. voxpupuli 
(https://github.com/voxpupuli/beaker-hostgenerator/pull/225), etc.) to 
start working on supporting CentOS Stream 9 as early as possible and 
thus would also likely help to boost adoption of puppet within RHEL 9 
environments and also keep it in place for folks who are upgrading to EL 9.


From a technical perspective, it is likely similar to how the agent is 
bundled for Fedora 34 / 35 - so I don't see a lot to be done for a dev 
preview.


~pete

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/4728fe4d-e65a-920b-4f71-b47a3f7f3dd4%40immerda.ch.

Re: [Puppet Users] Removal of CentOS 8 Support

[Peter Meier]

Hi All,

This is an announcement that we’ll be removing support for CentOS 8 in 
February 2022 because CentOS 8 is EOLed from the vendor in December 
2021. For a list of other supported operating systems for your primary 
server, see the supported operating systems 
docs. 


Are you going to add CentOS Stream 8, Alma Linux 8 and Rocky Linux 8 ?

Given all of them are RHEL 8 based (Stream 8 just tracking ahead, but 
still it's RHEL 8), I would expect it to just work. But Since CentOS 8 
was officially supported what needs to be done to get these EL 8 
releases to the same level?


~pete

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0f2882b8-f6c3-b7ee-08d5-8ecbdd36c00c%40immerda.ch.

Re: [Puppet Users] Newbie wants to know your favourite distro for Puppet Server

[Peter Meier]

On 17.06.21 02:58, Ian Mortimer wrote:
> On Wed, 2021-06-16 at 05:44 -0700, Jarod Schoen wrote:
> 
>> I went CentOS 7.9 because some body of people is saying that version
>> 8 is beleaguered already... I dont know who to believe.
> 
> You probably don't want to install CentOS 8 on any production server. 
> It will be replaced at the end of the year by CentOS Stream:
> 
>https://www.centos.org/centos-stream/
> 
> If you want to stay RedHat based, Oracle Linux would be the safest
> option currently.

Or you just don't believe the FUD spread all over the internet and you
go with CentOS Stream 8 already now, which is the same as CentOS Linux
just a bit earlier available (even earlier than Oracle, Rocky, ...).

I happily converted all my CentOS Linux 8 Systems (close to 100) to
CentOS Stream 8 last year and it all works fine. There is zero difference.

I am also looking forward to start integrating CentOS Stream 9 in the
next few months, which means I'll be able to start planning and
integrating the next version way before Oracle even gets to rebuild it.

~pete

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/be1545f0-40dd-caf2-0c70-22b3f86c0324%40immerda.ch.

Re: [Puppet-dev] Re: [Puppet Users] Upcoming changes to the rolling 'puppet' repos!

[Peter Meier]

Hi Josh,

> All resolved issues should be available in nightly puppet7 builds, such
> as http://nightlies.puppet.com/yum/puppet7-nightly-release-el-8.noarch.rpm
> .
> It'd be great to get confirmation in the next few days that these issues
> are in fact fixed.

Unfortunately, the EL 7 nightly repo wants to install el8 content, which
is a) wrong and b) is not found in the repo. See below.

So I installed the rpm directly:

yum update
http://nightlies.puppet.com/yum/puppet7-nightly/el/7/x86_64/puppet-agent-7.0.0.103.gf0655d02-1.el7.x86_64.rpm


Which worked and I confirmed in the ticket that this fixes the issue.

~pete

# grep puppet /etc/yum.repos.d/*
/etc/yum.repos.d/puppet7-nightly.repo:[puppet7-nightly]
/etc/yum.repos.d/puppet7-nightly.repo:baseurl=http://nightlies.puppet.com/yum/puppet7-nightly/el/7/$basearch
/etc/yum.repos.d/puppet7-nightly.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppet7-nightly-release
/etc/yum.repos.d/puppet.repo:[puppet]
/etc/yum.repos.d/puppet.repo:baseurl=https://yum.puppetlabs.com/puppet/el/7/$basearch
/etc/yum.repos.d/puppet.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppet-release
/etc/yum.repos.d/puppet.repo:[puppet-source]
/etc/yum.repos.d/puppet.repo:baseurl=https://yum.puppetlabs.com/puppet/el/7/SRPMS
/etc/yum.repos.d/puppet.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppet-release

# rpm -qf /etc/yum.repos.d/puppet7-nightly.repo
puppet7-nightly-release-1.0.0-2.el7.noarch

# yum update --disablerepo=puppet
Loaded plugins: fastestmirror, priorities
Repository base is listed more than once in the configuration
Repository centosplus is listed more than once in the configuration
Repository extras is listed more than once in the configuration
Repository updates is listed more than once in the configuration
Loading mirror speeds from cached hostfile
 * base: mirror.imt-systems.com
 * centos7-plus: centos.bio.lmu.de
 * epel: mirrors.ircam.fr
 * extras: linuxsoft.cern.ch
 * nux-dextop: mirror.li.nux.ro
 * updates: mirror.imt-systems.com
939 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package puppet-agent.x86_64 0:7.0.0-1.el7 will be updated
---> Package puppet-agent.x86_64 0:7.0.0.103.gf0655d02-1.el8 will be an
update
---> Package puppet7-nightly-release.noarch 0:1.0.0-2.el7 will be updated
---> Package puppet7-nightly-release.noarch 0:1.0.0-2.el8 will be an update
--> Finished Dependency Resolution

Dependencies Resolved


 Package   Arch Version
Repository Size

Updating:
 puppet-agent  x86_64
7.0.0.103.gf0655d02-1.el8   puppet7-nightly24 M
 puppet7-nightly-release   noarch   1.0.0-2.el8
puppet7-nightly14 k

Transaction Summary

Upgrade  2 Packages

Total download size: 25 M
Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for puppet7-nightly
puppet7-nightly-release-1.0.0- FAILED

http://nightlies.puppet.com/yum/puppet7-nightly/el/7/x86_64/puppet7-nightly-release-1.0.0-2.el8.noarch.rpm:
[Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use
https://bugs.centos.org/.

puppet-agent-7.0.0.103.gf0655d FAILED

http://nightlies.puppet.com/yum/puppet7-nightly/el/7/x86_64/puppet-agent-7.0.0.103.gf0655d02-1.el8.x86_64.rpm:
[Errno 14] HTTP Error 404 - Not Found
Trying other mirror.


Error downloading packages:
  puppet7-nightly-release-1.0.0-2.el8.noarch: [Errno 256] No more
mirrors to try.
  puppet-agent-7.0.0.103.gf0655d02-1.el8.x86_64: [Errno 256] No more
mirrors to try.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/cb882c56-58ab-54e3-4b42-7c06750e8747%40immerda.ch.

Re: [Puppet Users] Upcoming changes to the rolling 'puppet' repos!

[Peter Meier]

Hi All,

> Tomorrow morning (~9am Pacific) we'll be updating the rolling 'puppet'
> repos to point to the new 'puppet7' release from a couple of weeks ago.
> If you're already using the 'puppet' release packages (such
> as http://yum.puppetlabs.com/puppet-release-el-7.noarch.rpm
> ), your repos
> will start pointing to puppet7 tomorrow.


Anybody having VMs / Baremetals / ... using VLANs: You will run into a
regression with Facter 4 that will stop puppet 7 from working on these
machines:

https://tickets.puppetlabs.com/browse/FACT-2870

The fix is there, but there is no release yet containing the fix. So
it's worth holding these machines of from being updated on the rolling
repos.

Additionally, there are a couple of regressions regarding how networking
facts are being reported by Facter 4:

https://tickets.puppetlabs.com/browse/FACT-2871
https://tickets.puppetlabs.com/browse/FACT-2872

If you are depending on these facts in your manifests (e.g. in a
condition), it might be the case that puppet will do something
differently. I suggest checking your manifests for the usage of these facts.

I didn't check the bug tracker thoroughly for other regressions, but I
have seen a few more. So it might worth looking into it, as regressions
in fact reporting can have unintended side-effects.

And really only cosmetic wise, you get a bunch of warnings in puppet 7
for the user and exec types:

https://tickets.puppetlabs.com/browse/MODULES-10876
https://tickets.puppetlabs.com/browse/PUP-10790

They are not really an issue, but might affect you if you are parsing
the output. E.g. filtering cron output -> cron emails are sent out with
these alerts.

Other than that: Puppet 7 runs smoothly, be sure to re-install your
gems, as it switches to Ruby 2.7

best

~pete

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/354bd76b-c85c-3026-9906-b7c3d20adf3b%40immerda.ch.

Re: [Puppet Users] Issue with puppet6 release packages

[Peter Meier]

>   * If /etc/yum.repos.d/puppet.repo exists -- you are affected. Unless
> you want to be subscribed to the repo with rolling updates, you
> should uninstall and reinstall the release package.
>   * If /etc/yum.repos.d/puppet6.repo exists -- you are not affected.

So what is the intend for rolling updates?

Given https://yum.puppetlabs.com/puppet/el/7/x86_64/ does not anymore
contain the 7.0.0 release although it did for a while.

~pete

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/34c6750c-48f4-5b0a-951b-1e1a5cedcbc7%40immerda.ch.

REGRESSION - Re: [Puppet Users] Announcement: Release of Puppet Platform 6.0.1

[Peter Meier]

Hi All,

> We're happy to announce the release of Puppet Platform 6.0.1. This is
> primarily a bug release, with some improvements to Puppet, some new
> features in Puppet Server, and some new component versions in Puppet
> Agent.

Just a heads up to everybody: There is a pretty severe regression in the
exec provider together with cwd, as the behavior of the type/provider
changed from 6.0.0 to 6.0.1:

https://tickets.puppetlabs.com/browse/PUP-9194

tldr; The cwd param is not respected in 6.0.1 for the commands specified
in unless or onlyif. This might trigger an unwanted execution of the
command, as the safe-guards in unless/onlyif might fail as they are not
anymore executed in the cwd.

best

~pete

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/9101b379-79d9-3e04-df4f-3cd0c82880bd%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [Puppet Users] Announce: Puppet Platform 5.5.6 is now available!

[Peter Meier]

Hi

thanks for the answer.

> We hope to have another release relatively soon that allows you update
> the settings (and resolve the deprecation warnings).

Yeah would make sense to have that rather sooner than later. While I
understand why you want to get deprecation warnings in as early as
possible, there must be an alternative to migrate to (if the feature is
not to be dropped at all).

With deprecation warnings you want to signalize folks that they have to
act and adjust their configuration. But at the moment they just can't do
anything other than ignoring it, which defeats the whole purpose of that
warning. And eventually will make them also ignoring other warnings.

best pete

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/a92cd9d0-e215-71bc-c554-fe108d9ae34d%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [Puppet Users] Announce: Puppet Platform 5.5.6 is now available!

[Peter Meier]

On 08/22/2018 08:42 PM, Molly Waggett wrote:
> Puppet Platform 5.5.6 is a bug-fix, feature, and deprecations release
> that includes updates for Puppet 5.5.6, Facter 3.11.4, and Puppet agent
> 5.5.6. For details, see the Puppet
> , Facter
> ,
> and puppet-agent 
> release notes.

So this release deprecates autosign:

Warning: Setting autosign is deprecated.
   (location:
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:1169:in
`issue_deprecation_warning')

But to what should this configuration option now be migrated so there is
no deprecation warning anymore?

>From what I see when scanning through docs and jira, the new options are
not yet implemented. So we just have to live with the deprecation
warnings? Or what am I missing?

best

~pete

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/6872e14d-6379-f592-f68f-d4d2bc031642%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [Puppet Users] Announce: Puppet Platform 5.3.4 is now available

[Peter Meier]

> The puppet agent indeed has a default config  that I did not specify –
> and don’t want to, I’m running with a puppetserver :
>
> # puppet config print environmentpath
>
> /etc/puppetlabs/code/environments
>
> # grep env /etc/puppetlabs/puppet/puppet.conf
>
> environment = dev
>
> ð  Question : what am I doing wrong ?

I realized this morning (after the update) that updating the RPM (and
likely also the deps) overwrite/enforce various settings:

https://tickets.puppetlabs.com/browse/CPR-515

Maybe you are affected by the same bug?

As I read from your email, you get a warning that puppetserver can't
find things in

/etc/puppetlabs/code/environments

Is this, where your code should live? Are your environments there?

If not, then maybe changing it back to what you had there helps?

To me it looks like puppetserver isn't searching in /puppet/code/envs
but rather /etc/puppetlabs/code/environments

best

~pete

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5c56964f-8eea-2e35-03d1-14636274fb6e%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [Puppet Users] PuppetServer 2.8 resource Leak

[Peter Meier]

> There still a leak on Trocla database connections (latest
> gem/module/hiera backend).
> 
> I've installed a puppetserver, with only a node connected on; after 5
> days, there is 240 opened connections.

So, as you were changing a lot (new gem, module and switching to new
backend) I'm not sure whether you are still the facing exactly the same
issue as at the beginning, but just a different variant of it.

But so let's focus on the current situation as it is the one with
everything up-to-date.

I dumped the situation and my current guess on what is going wrong in
the module's issue tracker:

https://github.com/duritong/puppet-trocla/issues/25

As you have a single node in on environment that reproduces the problem
I would be happy if you could provide in the ticket more information,
specifically regarding to:

* How does your hiera config look like atm., so how is the trocla
backend hooked into the hierarchies
* How many classes does the node include during compilation
* How many class parameters are triggering the trocla backend?
* is the amount of connections growing over time, even if you don't
change anything (no new puppet code or something like that).

Estimated numbers are fine, but they should get an indication whether we
have too many caches that all keep connections open, while the actual
idea was to use the caches to not open too many connections.

thanks and best

~pete

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/cff3445a-3c2e-c115-3a14-1d5ec51e3a30%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [Puppet Users] PuppetServer 2.8 resource Leak

[Peter Meier]

> We are on hiera v3, we only tuned  "max-requests-per-instance: 5000"
> because of a databases connection leak with our Trocla library.

This is fixed with the trocla module 1.0.1 [1] are you on that version?

best

~pete

[1]
https://github.com/duritong/puppet-trocla/commit/bbedb788a7951e2f69c1c2815a5c3c669ff02ae6

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/e586fee5-028c-bc30-6758-5190c487010f%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [Puppet Users] Config test when restarting a service

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 Notify on its own is no good, since if the exec fails, the service
 gets restarted anyway.
 
 Require on its own is no good, since the exec runs every time.
 
 Is there some way to combine the two?

The problem is that a notify includes a before relationship, which
means that the service resource is always being managed *before* the
config test happens. What you want is the following:


file{'/etc/dhcpd/dhcpd.conf':
  notify = [Exec['dhcpd-config-test'],Service['dhcpd']],
  
}

# This exec tests the dhcpd config and fails if it's bad
# It isn't run every time puppet runs, but only when dhcpd is to be
# restarted
exec { 'dhcpd-config-test':
  command = '/usr/sbin/dhcpd -t',
  refreshonly = true,
  before  =  Service['dhcpd'],
}

service { 'dhcpd':
  ensure = running,
  enable = true,
}


This will not restart the dhcpd if the exec fails, as they have now a
relationship and if the exec fails the service is skipped. And the
exec is only being triggered when the file changes.

However, this has the drawback that you will only realize that within
the run where puppet changes the file. On the next run, though the
previous one failed, the file won't change anymore, the exec won't be
run and the service will already be running. So no change anymore.

I don't see a solution to that without having to constantly check the
config file and/or rechange the file, so it keeps chaning on the next
run, e.g. like:

exec { 'dhcpd-config-test':
  command = '/usr/sbin/dhcpd -t || (echo #failed 
/etc/dhcpd/dhcpd.conf  /usr/bin/false)',
  refreshonly = true,
  before  = Service['dhcpd'],
}

This will invalidate the target state of the configfile and so it will
be changed on the next run again, the validation fails again and you
keep having that node being reported as a failed node.
Otherwise, it will only fail once.

best

pete
-BEGIN PGP SIGNATURE-

iEYEARECAAYFAlWagfwACgkQbwltcAfKi39RtwCfcXp8wbJGntag04oiulW3qDHi
YiQAn0+Vk2p8QLAlf+A4dudpCeCUlYa/
=mSSL
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/559A8201.8030300%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] How to use multiple versions of same module

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 Ultimately, it seems that we should move to librarian puppet, but
 I'm not sure that that solves the basic problem, which is that I
 need to have multiple versions of the same modules.
 
 How do I accomplish this?

At the moment the best thing is: You don't

But you could (ab-)use environments for that, however this introduces
new workflows/changes, but is probably the best idea.

best

pete

-BEGIN PGP SIGNATURE-

iEYEARECAAYFAlWZRx0ACgkQbwltcAfKi39osACfYlDQqdUMg6tYXr5UMEKxTnxM
QLoAn1O37j3tVptmdlelvH0uMgz1r1s3
=774L
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/55994724.6050102%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet open source Puppet Enterprise

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 We are evaluating Puppet open source for our infrastructure and so 
 far so (very) good. Now my question is if in the future we want to 
 migrate to Puppet Enterprise will be an easy job or we need 
 basically to re-create everything from scratch? Any 
 clue/idea/documentation would be welcome!

I don't really see any reason why switching should not be possible and
I'm not aware of anything that should block you from just switching over.

It might require some steps to port over certs and so on, although I
don't really see any blocker there and why this should not work as
flawless as just installing PE.

~pete

-BEGIN PGP SIGNATURE-

iEUEARECAAYFAlQ8L8sACgkQbwltcAfKi3/GBACYsoDTo+kGVR/PQgax23r/WkF5
xgCgqduzJ6dGS7aK6W++pSLcepau71A=
=iWVj
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/543C2FD1.8030807%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] exported resources with puppet apply and deprecation of activerecord

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi all,

So as activerecord based storeconfigs are getting deprecated, what
options to use modules with exporting  collecting resources do we have?

The main problem that without a PuppetDB you are currently not able to
run puppet apply without getting any kinds of warnings. Either that
exported resources might not work (which might make modules working
not correctly) or that you use a deprecated feature, which will
disappear sooner or later.

IMHO setting up a local puppetdb with all the SSL dance one has to do
can't really be the answer. Or is there a more simpler setup of
puppetdb that I haven't yet found?

~pete
-BEGIN PGP SIGNATURE-

iEYEARECAAYFAlPuMPgACgkQbwltcAfKi3+SLgCdHSHkEgll+dHb6OgJEAzFlpvg
AWoAoJoZoHo4A6zp5MQA1Rj9rfpEg4t0
=PMvT
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/53EE3100.7020602%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet copy not working

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07/11/2014 08:09 PM, Rich Burroughs wrote:
 http://docs.puppetlabs.com/guides/file_serving.html

If you intend to get more help than this, it might be worth thinking
about what others could get from your statement it throws some error.

Btw: It works for me... ;-) ...at least on my machine...

~pete

-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlPAV0IACgkQbwltcAfKi38OJwCdGNmtj7i9RzjxcxHcOwOKDCc3
R6EAoLZ0RNqc/wDEUNCU00K2AWNnzZHj
=ETmW
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/53C05746.7040801%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Hook before Puppet compiles a catalog (for pulling update from GIT)

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 Perhaps the prerun_command[1] configuration setting might help. It 
 allows you to run a command before every agent run. I use it to run
 r10k.
 
 [1] - 
 http://docs.puppetlabs.com/references/latest/configuration.html#preruncommand

But
 
this is on the agent side, and not the master.

What I would do to have instant git updates, is updating things based
on a server side git post-update hook (the place where you push the
code). If you do the script in a little intelligent way, you can speed
up that quite good to make it pretty fast.

~pete

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlOVgfgACgkQbwltcAfKi38ObACeLB501PDamdCY4cR5X+bFFjgB
J8MAoJu/XATPpk1of4FJLGfAFV6pni9V
=hLSA
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/539581FD.8020106%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet 3.6.1 Virtual Packages, and unrelated facts questions...

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 I know we can set a top level default but does that really have
 to come out constantly ?
 
 I agree, I was thinking of filing a bug for this to request that
 it's dialled down to info or notice level, if it must be printed at
 all.
 
 Deprecation information at warning level might make sense if the
 user must make a change, e.g. in cases where a parameter is being
 removed, but it's unduly noisy at 'warning' level when in the vast
 majority of cases users need to take no action.


+1 - let's file a bug report.

~pete

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlN/FzkACgkQbwltcAfKi3/4WwCdEJ1vMif1KXq4CW27HFfXrObc
77wAoILuLKVZZhpISJQtOjBHosSd50OA
=PPxv
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/537F173F.5090609%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Workaround for user password hash

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 I suppose it will be useful if I share a workaround I just found
 for a problem I encountered.
 
 I needed a user puppet resource to add a user and set its
 password, on CentOS 6.4. The manifest was applied with no errors,
 but the password was not set correctly.

Shameless plug: If you care about passwords in manifests, then for
password management there is also trocla:

https://github.com/duritong/trocla

With the matching module: http://forge.puppetlabs.com/duritong/trocla


~Pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLzu+8ACgkQbwltcAfKi3/nzQCfWcF2UfNgxlB2QjlnWFzZ3R1b
6H4An3TDLM6b5Mpysxze/VhUO6eq+bMo
=IPar
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/52F3BBF5.6060706%40immerda.ch.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] puppet augeas - where to put augeas definition?

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi

 Per the snippet above, I'm simply trying to add in an extra entry
 into my /etc/apt/sources.list but I'm not sure where I would
 actually put the above piece of code.  I currently have it sitting
 in my init.pp file for the corresponding class but I'm not sure if
 that's really where it belongs.
 
 Is the init.pp file the right place for this and if not, where
 would I put it?
 
 My apologies if this is a stupid question as I'm having a hard
 time wrapping my head around this one.

The answer totally depends on how you would like to structure your
modules.

Given that you are managing apt-stuff I would assume that you have
something like an apt-module and I would place it within there.

You could place it there in the init.pp in the apt-class and on all
your debian systems, you would do an include apt. However you might
not want this repository to be present on all nodes, actually only on
the ones that need the client-repo.
So then a class called apt::repos::client (in the apt-modules in
manifests/repos/client.pp ) might be the better place to put it and
include this class on all nodes that require this repository.

This has even a different advantage: Maybe the main purpose for this
repository is have the packages available to install certain
applications - that you are also managing by puppet. So you could
include this repo-class only in the classes that manage the packages
for these applications (specify a dependency!) and you have not
anymore to think about this apt-dependency if you apply a certain
application-class to a node.

But this might already be a little bit off-the-topic. Anyway
http://www.slideshare.net/PuppetLabs/roles-talk is really a good
practice to structure your puppet code.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLg0tkACgkQbwltcAfKi3+YzACfSSsiJpa0nr9/XvpNjRNtIS1L
RXwAn3UPFCCJVC4F3twiozCGNqI4PAoI
=I0Xj
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/52E0D2DF.4070306%40immerda.ch.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] The Future - ENCs vs Hiera?

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 But as I'm starting down the road of writing *another* ENC -
 hopefully a good one this time - and more and more people whose
 advice and knowledge I've respected for years say use Hiera, I'm
 starting to wonder if either (a) I'm totally missing something, or
 (b) the community is increasingly ignoring a subset of us who, in
 fact, don't want every bit of configuration data committed to a git
 repo and/or like web UIs for certain things and/or need to
 manipulate that data via an API.

What you need to do is to write a tool that can act as an interface
for a datastore for your server data.

Your datastore then can then be used either by an ENC or hiera (write
your own backend, dump the data in a supported hiera format, ...).

Hiera has various advantages over an ENC and all the things that you
can do with an ENC are also possible within hiera, but not the other
way round.

Hence, if you build your interface the way that it can be used by both
techniques you're on the safe side and very flexible (you could even
use it in a mix mode). And actually if you think a little bit further,
it's actually not a big thing to support both ways of handing data
over to puppet.

~pete

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLILDIACgkQbwltcAfKi3+27gCgitWOzIViRTUAgZnwMzA+V27p
rGEAoJT/AJmuPnGpD5J4q2YIdSloghhz
=wb5g
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/52C82C38.7080606%40immerda.ch.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] hiera oddities

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 My current setup has a puppet master and an agent.  On both I have
 the same /etc/hiera.yaml file linked into the /etc/puppet
 directory.  I've also been able to confirm that hiera is seeing the
 right json files in /var/lib/hiera.

Note: if you want to go with plain master/agent setup, there is no
need to setup hiera on the client. As the agent gets a compiled
catalog from the master that can be seen as kind of static, at least
all the hiera lookups are done when the agent receives the catalog.

~pete

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlJGumsACgkQbwltcAfKi394RgCfQ8+6+7uqJx02XO9wKux/Qb2k
W8QAoK/tCiEO3Q2w4gY1q/3GENSqrI07
=nmWj
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] facter doesn't load from /ect/facter/facts.d

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 Is there a setting or search path I need to create?
 
 Details:
 
 puppet 3.0.1 facter 1.6.14-1.el6


I don't think this is supported in facter 1.6. One used to have the
stdlib module for it until facter 1.7 should be released, which will
provide that.

But maybe I'm wrong.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlFpd30ACgkQbwltcAfKi3921wCgqqmxl7eAybhAtl4Z7AKs0k5c
q2cAn3ynRWqJLoqxYFFY8YoSKPPjm8uG
=RMny
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Question on Variable Scope

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 Is there a way to export a $variable from a node so it can be read
 when the node processes one of its inherited modules? Is there
 something I can put in the inherited node like import $variable 
 before the included modules execute?
 
 FYI running puppet 2.6.16

This one of the parts where node inheritance is really nasty and I
wouldn't use it. I would try to do it with classes, like:

class basenode::core {
  $snmp_server = 10.0.0.10
  include snmpd
}

node 'myserver.domain.com' {
  $snmp_password = mypassword
  inherits basenode::core
}

Also I would try to do that with parametrized classes:

class basenode::core($snmp_password) {
  class{'snmpd':
server   = '10.0.0.10',
password = $snmp_password
  }
}

node 'myserver.domain.com' {
  class{'basenode::core':
snmp_password = mypassword
  }
}

you might also want to look into hiera, which can give you additional
options on how to structure that.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlFpeMcACgkQbwltcAfKi38m6QCfVVDG4FyZKyWjOb7JELuw8Gvf
IPQAoJGkEpdXBbTqzgGKWeaCkSPFXYFi
=KpJb
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Understanding how Puppet SSL works !

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 Thanks for the reply. It turns out puppet cert clean is not good
 enough, one has to restart either puppetmaster or the httpd service
 (I am running puppetmaster behind apache) to clean it up from
 memory.

Yes, this is a long outstanding bug in apache. you will find various
reports about apache not rereading the clr.

~pete

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlFpeTUACgkQbwltcAfKi3+gdgCgsVdRAUjrIVFt/knJYPvPmN6H
2wsAn2QiqFPflEYNPPomG72CInoquNgR
=EZZs
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Reassigning value of class declared in templates file

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 Does anyone have any ideas host to do this?

Do not use node inheritance, simply don't - it will hurt you badly at
some point.

It does not work in the same way as class inheritance does. And also
class inheritance should not used that widely (more or less only if
you need to overwrite values for resources, that aren't assignable as
parameter from an external source.

Instead use hiera and design your hierarchy there, then you will have
much more flexibility.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlFRldgACgkQbwltcAfKi38a0wCeLmJwcsPkEdHBjK2eO1zehXRD
k2sAoKxQgEy95TR4ExAPjNUVCQiTEQyD
=WmAP
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Query for file synchronization

[Peter Meier]

*My requirement:*
Let say file on master server *test_1.txt *got modified by some binary.
After modification I want to replicate the changes instantly on all other
nodes (agent nodes/servers).
Do puppet synchronize the file instantly to all servers?


No, puppet nodes usually pull a new catalog from time to time (by  
default every half an hour) from the master. But your requirements  
sounds more that you want to look into something like lsyncd. I would  
not recommend to try to abuse puppet for instant file synchronization.  
Also puppet is not very good a synchronizing large directory trees.  
There are better tools for that job.


~pete

--
You received this message because you are subscribed to the Google Groups Puppet 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Passing variables from one template to another included template

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 So what options do I have in 3.x to address my requirements?
 Something that would also work on  3.x would be nice.

I figured out that I can achieve that with an extended
templatewrapper: http://forge.puppetlabs.com/duritong/templatewlv

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlFKIrQACgkQbwltcAfKi38HlQCcC/QSyb8bYs2EoOzSU+0bNP01
pJAAn1w0L9nUfQQjqaXyBa3uk5TMjWbM
=9xo1
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Passing variables from one template to another included template

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi all,

I have the following basic requirement to pass variables from one
template to another included one:

#some_template.erb
%- [:foo, :bar].each do |state| %
  %= scope.function_template('some/other_template.erb') %
%- end %

# some/other_template.erb
%- if state == :foo %
write something
%- end %

However, this does not work like that and in #6492 [1] we came up with
a workaround:

#some_template.erb
%- [:foo, :bar].each do |state|
  scope.unsetvar('state')
  scope.setvar('state',state)
%
  %= scope.function_template('some/other_template.erb') %
%- end %

This worked until 3.x, but in 3.x unsetvar was removed (it was already
marked as used only for testing in  3.x codebase).

To get a proper solution for that I opened #6592 [2].

So what options do I have in 3.x to address my requirements? Something
that would also work on  3.x would be nice.

Thanks

~pete

[1] http://projects.puppetlabs.com/issues/6492
[2] http://projects.puppetlabs.com/issues/6592
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlFIKLAACgkQbwltcAfKi3+qfQCgiqrqWHrAQFXe2eBjsT0isbFQ
cHAAni3fL1WeusPzBh0gcikLeD09vU/Q
=4ry6
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] How to loop through entries in nodes definition for puppet

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 I'd like to print out the above using my template file, however I
 can't be certain of how many entries will exist, I want to end up
 with a file like so:

pass a hash to your ip::addr define and loop over keys/values as
indication which interfaces to you have with which values:

ip::addr{'bla':
  interfaces = {
'eth0' = {
  ip = 0.0.0.0,
  prefix = '/24'
}
'eth1' = {
  ip = 1.0.0.0,
  prefix = '/24'
}
  }
}

template:


server: %= name %
% interfaces.keys.sort.each_with_index do |k,i| -%
ipaddress%= i % = %= interfaces[k]['ip']
prefix%= i % = %= interfaces[k]['prefix']
% end -%

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlFIQFsACgkQbwltcAfKi3+7HgCgnJ/ldEJRmQdSMq77SMFOAh2m
kLMAnjFYTpenMyfFz+zOlhqXoFe6yjR3
=CVkW
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Does facter 2.x need cfengine key support?

[Peter Meier]

On 12/07/2012 03:24 AM, John Warburton wrote:
 We were tripped up (we shot ourselves) on facter 1.6.x looking in a missing
 NFS mounted /usr/local, which got me thinking - does facter 2.x really need
 this?
 
 https://github.com/puppetlabs/facter/blob/2.x/lib/facter/Cfkey.rb

And why shouldn't it?

~pete




signature.asc
Description: OpenPGP digital signature

Re: [Puppet Users] puppet agent cache files used in exec?

[Peter Meier]

 Could puppet cache /root/.my.cnf and reread it only after reboot.
 I see no other explanation. Is it bug?

No, puppet does nothing like that. It's strange that it works *now* but
I would say the problem is definitely somewhere else.

~pete




signature.asc
Description: OpenPGP digital signature

Re: [Puppet Users] in-module data with hiera

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 09/30/2012 05:01 PM, Ashley Penney wrote:
 This is -exactly- what I've wanted in my modules since I heard of 
 Hiera and I am strongly supporting this proposal.  I'll be 
 experimenting with your gem.  I can't give this enough support as
 this is what I wanted since Hiera began.  It'll make supporting
 multiple distros/operating systems much easier for modules on the
 forge.

+1. Nice idea!

~pete

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBqkw0ACgkQbwltcAfKi398AACbBbGxDdWcpHBySXCSUY++yydb
D4cAn318SEhFYPqjyKymaH45vKYUzxvi
=3lWJ
-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.

Re: [Puppet Users] any cobbler management modules out there?

[Peter Meier]

 Cobbler manages all its internal info.  To get Puppet to manage it
 would, IMO, either involve hacking Cobbler or wrapping Cobbler
 command line calls in Puppet exec resources.

Cobbler has also an API you can talk to. There is a cobbler gem [1], [2]
that provides you an easy way to interact with the cobbler api from
ruby. It so far is known to work with Cobbler 2.0.x, but should probably
also work with any 2.x.

~pete

[1] https://rubygems.org/gems/cobbler
[2] https://github.com/duritong/ruby-cobbler



signature.asc
Description: OpenPGP digital signature

Re: [Puppet Users] Escaping Quotes

[Peter Meier]

exec {
'oracle-extract-part':
command = /usr/bin/printf
\n\np\n2\n2091\n+16384M\nw\n\ | /sbin/fdisk /dev/xvdj,
unless  = /bin/cat /proc/partitions | /bin/grep
${orcl_ephm_device}2;
}


if you don't need to interpolate a variable, you can simply use single  
quotes, so you don't need to escape anything.


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

Re: [Puppet Users] Escaping Quotes

[Peter Meier]

Zitat von Max Schubert max.schub...@gmail.com:


How about using the alternate single quotes in ruby

%q{string string string}


puppet manifests are not ruby code.

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

Re: [Puppet Users] Hiera - How to set a parameter to the value false

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 I've been using hiera for a few weeks now, but I'm stuck now trying
 to set a value to false
 
 Basically, I have a class that read its parameter in hiera, and in
 a yaml file I have the following code:
 
 --- use_ecrypt_fs: true server_region: fr puppet_enable: false
 
 
 This ultimately leads to the following error: err: Could not
 retrieve catalog from remote server: Error 400 on SERVER: Could not
 find data item puppet_enable in any Hiera data file and no default
 supplied at
 
 When I set puppet_enable: true this works fine, but I can't figure
 out how to pass a false value (tried false, False, nil )

which version are you using? This have been fixed some time ago:
https://github.com/ripienaar/hiera/commit/3cd4cecaea1b4ea014e4ba4567a8322f0b987284

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk69YbYACgkQbwltcAfKi39v/wCcD62vk6u721kUwZ7sbfRO/89N
YGsAoIX71R9eQQlcQ1EtJIQLYQVdiQsW
=F/V8
-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.

Re: [Puppet Users] How does puppet copy files?

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 When agent notices that master.passwd should be refreshed, how 
 exactly does copy process happen? Is it atomic (e.g. fetch to some 
 temp filename on local filesystem and then rename)?

it does it this way.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk69X4QACgkQbwltcAfKi3/UlACfWrlwrdCCg+9tjjRQJ31iNLvg
OyUAn3FONkQR1aDxYtwlS2Xphb9PneaV
=4KAu
-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.

Re: [Puppet Users] Puppet Dashboard 1.2.2; node report; change sort in log tab

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/07/2011 08:55 PM, Stefan Heijmans wrote:
 The sorting in the log tab on a node report seems to be on the
 level column, which is hard to read when multiple changes take
 place, as notice and info of the actions are on the top and bottom
 of the log. Can this be adjusted so its displayed as 'puppet agent
 --test' does (sort on time and line column).

Sounds like a reasonable bug report/feature request:
http://projects.puppetlabs.com/projects/dashboard

~pete

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk69YkIACgkQbwltcAfKi3/RXgCfcIXrDJp32VnXVxK1UM7RYylV
uesAoItxpdNGLAiqxq5RWSo04wLYvZ/s
=Apya
-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.

Re: [Puppet Users] organizing Ruby DSL manifests

[Peter Meier]

 Thanks Chris, that's helpful. I am wondering if I should be mixing
 Ruby DSL manifests with the Puppet DSL manifests. Is there any
 recommended practice for keeping both styles together? 

Afaik you can mix both DSL. If one file in a module ends with .rb it's
ruby dsl, if it ends with .pp it's puppet dsl. Obviously they shouldn't
have the same name.

But if you only use modules and follow the autoloading rules (one
define/class per file with the same name as the filename/heirarchy) you
won't name a file twice with the same name anyway.

 Also, does Ruby
 DSL get converted into Puppet DSL before execution?

Both, puppet and ruby DSL get compiled as a catalog, which is then sent
to the client and applied there. The same goes for the standalone mode,
where the client just applies the catalog it compiled before. So in both
ways they end up in the same abstract target, called catalog.

If you're switchting to client/server mode, the only thing that you need
to consider is that ruby-dsl files (as the puppet dsl files) are parsed
and compiled on the master. This means that if you have in these
ruby-dsl files any file-operations, binary executions etc. without using
the proper puppet providers, your ruby code will be executed on the
master. As it goes with puppet functions, that are also executed on the
master at compile time.

So having the idea of querying DBs FROM the client while applying the
catalog (not to mix with compiling the catalog) or do any other magic
using ruby code, won't work, as this code will always be executed on the
master.

The client just gets a fixed compiled catalog it applies, nothing else.

~pete



signature.asc
Description: OpenPGP digital signature

Re: [Puppet Users] [ask] Upgrade for CVE-2011-3872 AltNames Vulnerability

[Peter Meier]

Is it ok if i just upgrade puppetmaster to 2.6.12 and still using  
old puppet.conf with certdnsnames?


The certdnsnames have been abandonned in favor of a new option:  
http://docs.puppetlabs.com/references/stable/configuration.html#certdnsnames


And if your current client certificates contain a master  
altSubjectName, you need to rollout a new (from the ground up) CA.  
Otherwise you're still subject to a possible attack with old certs.


The notes released by puppetlabs are quite detailed about that:  
http://puppetlabs.com/security/cve/cve-2011-3872/


Unfortunately, if you are affected, this issue is *not* fixed by  
simply updating a package.


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

Re: [Puppet Users] Regenerating puppet master certificate

[Peter Meier]

Wish I could've found that in the docs.
This will certainly get me going again.


Sounds like a ticket for puppet documentation...

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

Re: [Puppet Users] Re: Using puppet to install debian packages from backports

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi

 I'll try to setup apt-pinning.

the apt module @ https://labs.riseup.net/code/projects/shared-apt/

Can help you by setting up pinning:

https://labs.riseup.net/code/projects/shared-apt/repository/revisions/master/entry/README#L303

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk6AHHUACgkQbwltcAfKi3+DFwCeKQB2szZ9ODbrUqZHUbjO800n
LGoAn2T125VuvPvRlK0zI4Cx2sYslUq1
=9bca
-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.

Re: [Puppet Users] Variable number of variables in external node output...

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 1) Use a template. Templates have embedded ruby code and run on the clients.

template() is a function and as any other function it will run on the
server.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk56028ACgkQbwltcAfKi3/e+wCfVcovUxo7vjzG4BD7XOeZLU/6
XlIAn231meTEH9REpxBBWxtcvSSedhMz
=di4d
-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.

Re: [Puppet Users] Re: Puppet 2.7.3 Cannot alias .. already defined

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 A single manifests works fine, but this is not the only module I have
 where I set permissions using the sysconfig::permissions module.

Ah, now I as I read your problem better: The error indicates more that
you name two resources with the same name/alias. And you can't and
shouldn't do that!
Actually your code should imho not work on 2.6.9 either and yes it looks
like 2.7 got more strict.

Anyway, you shouldn't do what you do currently, this is quite dangerous!

Note: Puppet automagically sets the execute flag on directories, so if
you'd like to have the directory 0750 and the files 0640, then simply
set the mode of the directory to 0640 and to recurse. If you would like
to set the files to 0600, then you have to manage them invidually,
because the file provider of puppet does (currently) not (yet) support
that feature.

 I can rewrite them, (and probably have to, to make it work again) but
 then it seems that the ' name' option in the file type is going to be
 obsoleted as it doesn't work anymore.

Unlikely, name is quite an important attribute for all resources. It is
more that you end up having two different resources with the same name
or alias. And that should really not be.  It looks like a serious bug
_got_ fixed in 2.7


~pete

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk50prIACgkQbwltcAfKi3+vjQCfboeXmfrBJzDS1/5NSsO8McDB
pwIAn2QOSWif3fZVkCEvLt/se5BoeoFL
=SOll
-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.

Re: [Puppet Users] OpenBSD/i386 Puppet 2.7.3

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 I expect the default user provider should be useradd(8) but
 ProviderUseradd seems to be looking for 'chage' binary which isn't
 used on OpenBSD. I've checked out the 'Puppet OpenBSD' doc but didn't
 find anything applicable. Searching archives and Google for this error
 showed a few issues on Solaris and other systems but I wasn't able to
 find anything specific to this issue.
 
 Am I looking at a bug?

Likely, I would file a ticket.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5zmxMACgkQbwltcAfKi39jVwCdGIp3gfTsl70/gMaP1ieowEs+
IiIAoJn/ryH+ijPcsOBD546cadZPs/E6
=IOOL
-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.

Re: [Puppet Users] Puppet 2.7.3 Cannot alias .. already defined

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 I would reference from back from the sysconfig::permissions module to
 the ntp module file by specifying
 name = /var/lib/ntp
 
 Do I need to change all my modules because I used a feature of puppet
 which should not be there, and if so, how could I best fix this.

does a single manifests like

file{'foo':
  name = '/tmp/foo',
  mode = 0700;
}

with puppet apply, also raise an error?

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5zm6YACgkQbwltcAfKi3/k2QCfcG/LwcP+pebtbOA1vwFlOLwq
BoAAn1ukeUejmGFp4w4yCBk4No34xJhw
=pvok
-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.

Re: [Puppet Users] Storeconfigs seem slow

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 We're at about the 100 hosts, but have closer to 1500 services - maybe we
 have exceeded what storeconfigs can do then.  If that is the case, is there
 a recommended alternative that isn't manually maintaining config files? 

Just to be clear: After the catalog has been compiled and sent to the
client, storeconfigs is not anymore involved at all.

So if your compile time is reasonable, but execution time on the client
is slow, then you have to look on the client side and not storeconfigs.

Storeconfigs just adds a few selects (and inserts) of additional
resources, that weren't directly in your manifest. But they end up the
same way in the catalog as any other resource does.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5u+AkACgkQbwltcAfKi38OJACfXT9sumhvPpIoK0qUlH5x4JfN
AaMAnROsu3S4u3w82sI9NzDeBWdlwKvP
=xUF9
-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.

Re: [Puppet Users] Storeconfigs seem slow

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 The good thing with this method is that you can manage the module
 directory (where the different config file excerpts are stored) with
 'purge = true' so that only exported resources are present in the final
 nagios configuration (something that native types don't handle very well
 -- or actually handle very badly).

Yes, because purging the directory would unexport the resource of the
decomissioned host. But, as other resources might have been exported as
well, that can't be purged by that trick, I would still recommend to
clean up decommissioned hosts with the puppet node clean face-action,
that got partially merged into 2.7.3 and hopefully will be fully (with
the important parts for our discussion) merged into 2.7.4.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5u+bAACgkQbwltcAfKi39iQQCeIf2CPVgA3f11wE0VxPCefZDb
OvEAn1Tw5UTSTnons6wJGyqUdO50lspD
=c84z
-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.

Re: [Puppet Users] A new-to-puppet question

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 Let me start by saying I'm really jazzed by what i'm uncovering on the
 *nix front with Chef - seems like a LOT of what I'm looking for is
 already done.
 
 Is there a writeup somewhere that shows/documents manipulating an esx
 server/creating/cloning/etc vms?
 
 I see there are a lot of cloud provider type cookbooks available, but
 maybe I overlooked an esx cookbook.

Chef?

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5pwQgACgkQbwltcAfKi39AmgCfZpwT21GecpbaH/lbpSL7oJb1
Xo8AoJEbTeLzu4/cTJz4zdKehgm0sLxO
=tHJq
-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.

Re: [Puppet Users] Re: The require function

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 You've seen this with your own resources where the parent is a directory and
 the child is a file?
 Please bug report, as it's been a very long time since that autorequire was
 put in (0.24.x ? 0.25.x?), and I haven't seen a reported bug since then.
 
 Totally... Although in this particular instance, the server is
 2.7.3, and the client is 0.25.5...

Note that to my knowledge this is an unsupported combination. Afair
puppet only supports one major (?) version less as a client. Means that
the client should be at least 2.6.x.

Also if you are going to add a bugreport a (complete!) manifest that
fails would be very helpfull, because With the simplest manifest:

file{'/tmp/foo': ensure = directory }
file{'/tmp/foo/bar': ensure = present }

I'm not able to reproduce your problem in over a hundred executions.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5oe8sACgkQbwltcAfKi3+JtgCeKekxf2F9akTGPSa2I6gcX1YG
5DcAnjxR2jw1Lb+FCnvvLpKxAIJFlUiM
=T3cl
-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.

Re: [Puppet Users] undefined method `function_extlookup'

[Peter Meier]

On 09/07/2011 11:44 AM, piavlo wrote:
 Trying to use extlookup from within template i use
 
 %= scope.function_extlookup(blah) %
 
 but get the undefined method `function_extlookup' error
 
 According to 
 http://docs.puppetlabs.com/guides/templating.html#access-to-variables-and-puppet-functions-with-the-scope-object
 this should work.

http://projects.puppetlabs.com/issues/4549

it will work in the next 2.7 minor version, so long you have to use
MarkusQ's workaround, to load the function to make it available.

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

Re: [Puppet Users] small problem with init script on RHEL6

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 This change in the init script fixed the problem:
 
 #pidfile=/var/run/puppet/puppetmasterd.pid
 pidfile=/var/lib/puppet/run/puppetmasterd.pid
 
 Is that a bug worth reporting?

I would, at least somebody can then decide if it's really a bug or not.
But as you are using 0.25.5 you better first check if it's fixed in the
latest version.

I assume it to be fixed a long time ago...

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5nzZUACgkQbwltcAfKi38mowCfTaupFunS1SfblhIaWDFuXn2Z
g6EAoIGoqqMzZovObtxk5joO/plFNL4C
=CD/d
-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.

Re: [Puppet Users] Question on accessing a variable from another class

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 modules/rep/templates/test_template.xml.erb
 ?xml version=1.0?
 configuration
test_template cname='%= ldap_cname % /

The template is in a different scope than ldap::variables_common, so
ldap_cname is not directly present like that and you need to use:

test_template cname='%=
scope.lookupvar('ldap::variables_common::ldap_cname') %

But for reusable modules etc. I would recommend you to look into hiera
[1] and to combine it with parametrized classes as shown in [2], it
makes it quite easy and really extensible.

~pete

[1]
http://www.devco.net/archives/2011/06/05/hiera_a_pluggable_hierarchical_data_store.php
[2] http://www.devco.net/archives/2011/06/06/puppet_backend_for_hiera.php
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5CJC8ACgkQbwltcAfKi3+3lQCdEc5g80XeAE60nBuXlafiy7xE
HTcAoLKfAon6XT/e7frTKboQC178hQsq
=6jw/
-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.

Re: [Puppet Users] Workaround to Provider groupadd does not support features manages_members ?

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi

 I wanted to manage a couple of groups membership, under RedHat,
 without managing the users (as they are LDAP users) but found out it
 is not supported Is there a workaround to this?

As denmat mentioned as well I would generally try to avoid a local
groups and ldap users mix.

But, it's possible to use augeas to manage users in a group:
https://github.com/duritong/puppet-user/blob/9bbd720da1549bf58c7707c1ac109a47e4b4a946/manifests/groups/manage_user.pp

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4/hKkACgkQbwltcAfKi3+XuACePGaZjfkJm+ySkVoMq6z7VDGo
nLgAn2MGcXo7zbpwQNlN7VDtG8A35cE9
=AI9M
-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.

Re: [Puppet Users] Re: Unable to display Filebucket in Dashboard 1.2rc3 : We're sorry, but something went wrong

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 Also I noticed I can only read the first file, the changed file, not
 the second, the original (content changed '{md5}
 70c1c6de6d4b1a02ec32b463e4d255b0' to '{md5}
 78124298c2b4c1e63658599a2c208853') :
 
 info: FileBucket read 70c1c6de6d4b1a02ec32b463e4d255b0
 info: Could not find file_bucket_file for
 'md5/78124298c2b4c1e63658599a2c208853'

This is a known current limitation:
http://projects.puppetlabs.com/issues/7934

Because puppet hasn't yet uploaded the version of the file to the file
bucket it installed, it only uploads the changed versions.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4/hukACgkQbwltcAfKi38/mACfbsAwBocPZ/TqGXjWc2SJmWUW
PB8An1Rm+UkZVkQ0BSO5BGqL8ACF2apn
=QIfL
-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.

Re: [Puppet Users] Step by step guide to setting user passwords

[Peter Meier]

 Can someone walk me through the steps of sending out a password to all
 my computers for user student.
 
 I do this a lot:
 
 yes 'PASSWORD' | passwd username
 
 Then you can extract the password from /etc/shadow
 
 also  see here:
 
 http://serverfault.com/questions/87874/how-should-someone-create-an-encrypted-password-for-etc-shadow


No need to go over /etc/shadow or use mkpasswd (which is not available
that easy on all distros). How about

# salt=`pwgen 8 1`; pass=`pwgen -s 12 1`;ruby -e puts \
  ARGV[0].crypt('\$6\$'  ARGV[1]  '\$') $pass $salt; echo $pass
$6$eemaihic$3gwFGQxMWE8n/KMZlNe3O9dVoQC5zCXrtabhpCLeDp54eYTGK8WAHovxYZLaQf8YF93Hwfh466CQ966Xoh6O81
FmstT8KObWVu

?

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

Re: [Puppet Users] pluginsync before catalogue?

[Peter Meier]

 Its my understanding the 'customfact1' fact is meant to be transferred
 to the host as part of the pluginsync process before the catalogue is
 rendered, but this doesn't seem to be happening on our new builds from
 the above error.

Yes it works exactyl that way.

 Does anyone have any insight into the pluginsync/catalogue process and
 how this is fixable?

Can you provide more information from a `puppet agent --test` run from
your client? Otherwise it's quite hard to guess what your problem is.

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

Re: [Puppet Users] Step by step guide to setting user passwords

[Peter Meier]

On 08/03/2011 04:44 PM, Matthew J Black wrote:
 Not sure if that'll work right but one option is you should be able to use
 the generate function in the manifest to make an external call within the
 puppetmaster to create the encrypted password. The downside is that its
 going to execute every time, where it might be less of a performance hit to
 cut and paste in the encrypted password into the manifest.

or you can use something like trocla to not even store the encrypted
password in the manifest:

https://github.com/duritong/trocla
https://github.com/duritong/puppet-trocla

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

Re: [Puppet Users] Re: Puppet 2.7.1, variable scoping, best practices

[Peter Meier]

On 08/02/2011 04:20 AM, Aaron Grewell wrote:
 I recommend taking a look at R I Pienaar's alternative extlookup
 implementation.  It supports YAML in addition to csv which allows for the
 full range of available variable types to be pulled in from external
 sources.   I've combined this with a YAML-based ENC to put all variables for
 a single node into one YAML file.  It's working well for me.

but then, you should better directly go with hiera.

my2c

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

Re: [Puppet Users] Facter 1.6.0 and CentOS 6.0

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 Is this a known issue? Is there any work-around? It's really breaking my 
 CentOS 6 servers' ability to find their REPOs. :-)
 
 You need to have the lsb_release command installed for the lsb* results
 to appear.
 
 Fedora/Redhat have it in the redhat-lsb package, so it possibly has a
 similar name under CentOS.

yes, this is the missing package. It has the same name on centos.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk42z70ACgkQbwltcAfKi3/TxQCfcaJFWkiyBKhpAWQ6grnIUkJ4
fBUAn2ZiusnYKuM5F51UscOg2e6WrTgf
=xBYh
-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.

Re: [Puppet Users] Master failover and cert names.

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 I know that there's a 'certname' option but it looks like it's only valid in
 the [agent], not the master section. How do I do this?

It works in the master section as well.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk41QYwACgkQbwltcAfKi38SWACdGScL/R3xv/dh3dNDL6Ko1inW
dd0An28vtvwmfUQ/qCGmxSeb7GCpRcG3
=B753
-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.

Re: [Puppet Users] Is class?

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 It just seemed to me that there must be some way to derive what is
 installed on the client within a manifest but I couldn't find any
 suggestions on Google or PuppetLabs site so I asked.

Manifests are compiled to a catalog on the master. The catalog is then
sent to the client, which only applies what the master compiled. The
master can know about things of the client via facts.

So if you want to know if something is on the client you need to write a
custom fact for that.

But wait a moment before you do that. As puppet is your CM-Tool of
choice you would like to likely control things that are installed on the
clients via puppet. And somewhere at some point you define your puppet
client as an ldap server. As Nan suggested, this is the point where you
should also add the ldap-server itself as client. Not?

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4ycRsACgkQbwltcAfKi38zrwCePHUgFIOcnC1gJXhpJiWsLLGV
/zEAoI2203IoWWambb3++gevlmyj5amG
=UHs0
-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.

Re: [Puppet Users] Upgrading 0.25.5 to 2.7.1

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07/28/2011 12:09 AM, Nick Moffitt wrote:
 vagn scott:
 Funny you should mention that.  I have been playing around with
 separating the puppetmaster config from the agent config.  See here:

 http://agawamtech.com/blog/?p=383
 
 I solved this by having the puppetmasters all proxypass (they're running
 in apache+passenger) their CA port (specified in the puppet.conf as a
 non-standard one) up to a central CA.

I would recommend the first way, actually the only thing you need to do
is to set a seperate ssldir option within the master section (and
probably appropriate certname, certdnsnames options to fit your dns
alias for the puppetmaster) to seperate the ca from the client config.

And why can't you simply point your client forth and back between
multiple masters that do not share a CA? This is how OpenSSL works and
how it protects the communication of your puppet nodes.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4xBwUACgkQbwltcAfKi39uxwCdGeu+XuZ03lC6fK00SuhvEryY
GB8AmgNQ1Gyc+t0K6fA1JwfmLfACMssP
=+E2M
-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.

Re: [Puppet Users] lstat on a large dir done by puppet

[Peter Meier]

 The swapfiles is a large directory with lots of files. Is there a way
 to avoid this, since its taking lots of time to compile the catalog
 from the puppetmaster. Can i somehow prevent this?

I guess it's not during compilation, as this happens on the master,
rather while applying the catalog.

How does your catalog looks like regarding that directory? Any recursive
management?

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

Re: [Puppet Users] Accessing puppet.conf settings in a manifest

[Peter Meier]

On 07/25/2011 05:07 AM, Zain Memon wrote:
 Is there some way I can access variables from puppet.conf (e.g.
 $confdir) in my manifest?

${settings::confdir} but in a master client/setup these are the settings
from the master. So what you want to do is to write a custom fact that
exposes your setting. This is quite easy:

Facter.add(confdir) do
  setcode do
Puppet.settings[:confdir]
  end
end

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

Re: [Puppet Users] Re: Not getting errors/warnings/etc in reports

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 I'm guessing I'll have to write my own to do that -- does anyone have
 any examples of logging the error message and also adding it to the
 report object?   (... and I don't really want to use the exec {
 /bin/false: } workaround)
 
 Digging through the code it looks like puppet adds messages internally
 using Puppet.warning(), Puppet.error(), so I made a custom function to
 call these directly.
 
 I'm still not getting my error() messages in the report yaml ... why?

Probably, because functions are evaluated on the master, while the
report is created on the client when the catalog is applied. So these
messages never get sent down the client...

~pete

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4oOb0ACgkQbwltcAfKi3+UkgCfVa2tz5Nr6NyklpBwgGuHMoNL
klQAoICzzOX7fckqU//hHxRSGFj8tskV
=1kTp
-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.

Re: [Puppet Users] Re: Seemingly random failures after 2.7.1 upgrade

[Peter Meier]

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

Re: [Puppet Users] Re: A Question about mixing Puppet with other things

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07/12/2011 05:26 PM, Dan White wrote:
 This tells me RedHat picked Foreman over Cobbler.  It does not tell
 me WHY.
 
 Their reasons may not apply to my situation.
 
 I am not trying to be difficult, but I find that I cannot accept an
 opinion on a technical issue without technical information to back it
 up.  Also, this is for my job, so I need to be able to justify my
 decision with more than The folks on the puppet mailing list told me
 to do it this way.

* strong: foreman, thanks to its smart proxies, is not that subnet
  oriented as cobbler is. Means: You can use one foreman to deploy
  things into multiple subnets/locations from one installation, which
  gets much more complicated with cobbler.

* strong: foreman integrates puppet from the beginning on, means for
  example:

** strong: foreman integrates the configuration of puppet nodes, while
   cobbler has a much simpler general external parameter option meant
   for any configuration management system
** strong: foreman integrates puppet reporting, while with cobbler you
   would need another tool, like dashboard.

* strong: foreman has much better support for other distros than redhat
  based distros

* medium: cobbler has better integration to address baremetals, like
  powering them on via powerbars. According to my current knowledge
  foreman doesn't (yet) have the capability to tell powerbars to turn
  baremetals on.

* medium non-technical: cobbler is integrated in the current
  spacewalk/satellite solution, while foreman is part of the next
  generation of redhat's satellite. - http://katello.org

* medium: cobbler can also manage external repositories, while foreman
  rather delegates that to other tools (rsync scripts,...).

* uncertain, but rather strong: foreman has better integration with
  libvirt, actually within the webinterface cobbler doesn't have one at
  all imho. but I could be wrong...

* weak: foreman is written in the same language as puppet, so if you
  anyway would have to learn both ruby and python, it might be easier
  to have 2 new tools written in the same language

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4dNUsACgkQbwltcAfKi3/fFgCfUvOZ2gP0TzDIiy6gg21IQbCy
41wAnA/J49OLHpaILc+yBIabjbZ8Kphd
=P2nf
-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.

Re: [Puppet Users] Seemingly random failures after 2.7.1 upgrade

[Peter Meier]

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

Re: [Puppet Users] Re: how to write classes to install package from source

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07/12/2011 12:19 PM, Al @ Lab42 wrote:
 You might find this define useful ( 
 https://github.com/example42/puppet-modules/blob/master/common/manifests/defines/netinstall.pp
  
 ):
 

or as a general best practice you might want to build your own packages.
They're much easier to handle!

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4dO2kACgkQbwltcAfKi3+5WQCfa35P0lZKGS8xYyitmfLt7Kiy
wUwAn0pnp4xscGeMNl3VA1Lo1xSygYh9
=ZGSf
-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.

Re: [Puppet Users] puppet manifest execution orders

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07/13/2011 08:51 AM, Roni wrote:
 I created manifest for our webserver. manifest included git clone,
 database creation and restore database etc How to order the
 installation and exec exactly

by using require, before, notify, subscribe...

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4dey4ACgkQbwltcAfKi39V5ACgmVJlYay6nCMQ/NruO/yiICHf
XysAoJ89DzSQ74/rTyxmTTIGLUcvI5Ai
=wY2a
-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.

Re: [Puppet Users] Re: puppet master and puppet client running very slow

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

  File: 1539.03

This indicates clearly a problem in serving files, so does the other
error you posted.

As others asked: Are you still running with Webrick (means default
puppetmaster without setting up passenger/mongrel)?  And how many
clients are connecting to the server how frequently?

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4SpsUACgkQbwltcAfKi3+AeQCfVKw/DBKcMIlCzMfGK7gF0xpK
0BYAn3ph1iWV8YjO5WxuEzm7bhucvAU+
=Aj9t
-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.

Re: [Puppet Users] proposed syntax: order { }

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

This

 file { a:
 path =  aaa ,
 before = Exec[ b ],
 }
 
 exec { b:
 command = bbb,
 before = File[ c ],
 }
 
 file { c:
 path =  ccc ,
 before = Exec[ d ],
 }

Can also be:


file { a:
path =  aaa ,
}

exec { b:
command = bbb,
}

file { c:
path =  ccc ,
}

File['a'] - Exec['b'] - File['c']

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4Sp60ACgkQbwltcAfKi39UGwCeLzGDvKifM4wojlomy7O0idmo
i5IAni52e3YvE8pWdRf8Ide8vLcZPkl0
=NSLF
-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.

Re: [Puppet Users] Ruby 1.8.7 manifest

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi

 If you have used a public accessible manifest for ruby 1.8.7 ree or
 you are willing to share ... I am looking for one!

I would look on how to generate packages for your distro for REE (if
they aren't yet available) put them in a local repository and install
them simply by using the package provider.

scripting ./configure;make;make install with puppet exec resources is
imho a bad idea.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4RXAIACgkQbwltcAfKi39yeACgpRYf6gISbB/y1uCFsRD6MqK1
mckAn3Nz6WBIva+ANtCeWdp1H0OU9mF9
=uNG0
-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.

Re: [Puppet Users] Re: puppet master and puppet client running very slow

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 as i m able to see that puppet master taking around 7-8 seconds to
 compiler catalog
 and puppet client taking around 1106 second to apply catalog .

run the client with --summarize and see on which resource types it is
spending most of the time, then you can probably figure out what is wrong.

also analyzing the reports with something like the dashboard or the
foreman can help to trace these issues.

Certainly something within your environment or its dependencies has
changed. Puppet is heavily calling out to tools like facter, package
managers, service scripts etc. which all can easily affect your puppet runs.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4R+mcACgkQbwltcAfKi3/d/QCeODSqHvF8OxULMcbw6gfuEOT9
noMAn2b0DySrqrZ27kA6Xfvb1WaVWKdX
=pHX/
-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.

Re: [Puppet Users] Re: err: Could not retrieve catalog from remote server: Could not intern from pson: Could not convert from pson: Could not find relationship target File[]

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07/04/2011 08:49 PM, Michael Halligan wrote:
 Forgive my cluelessness, but why is it so difficult for Puppet to at least
 tell me what file this came from like 90% of other errors I've encountered?

I don't think there is a particular reason. Did you look for bugreports
and/or submitted an error message improvement request?

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4SNOoACgkQbwltcAfKi38J0wCaA6xk3UiaUEXrxu3gVKbKYO2l
UHMAnRFfJc4icgV7Srt6Darz2Q54cqQO
=L6+R
-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.

Re: [Puppet Users] Ruby script to download files without 'puppet agent'

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [root@foo me]# ./puppet-wget file_content/sudo/sudoers
 https://foo.bar:8140/file_content/sudo/sudoers
 warning: peer certificate won't be verified in this SSL session
 /usr/lib/ruby/1.8/net/http.rb:2099:in `error!': 403 Forbidden request:
 foo.bar(10.2.3.4) access to /sudo/sudoers [find] authenticated  at line 93
  (Net::HTTPServerException)
 from ./puppet-wget:56
 from ./puppet-wget:43:in `each'
 from ./puppet-wget:43

Using your script works to get a file from a module files, like:

./puppet_wget
/development/file_content/modules/site-bind/etc/rz.foo.ch/named.conf

However your error looks like the client is not authorized to find that
content. Maybe some tweaks in the auth.conf are missing to fetch files
from the fileserver instead from modules?

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4LCqYACgkQbwltcAfKi38O9wCgnUKnyugLiukznBcjjLQ2wXbd
sK0AnA8UAYkrIiFPAkIbCELvFLu7F6q3
=iiOQ
-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.

Re: [Puppet Users] How to add extra lines in the existing files?

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 I am hesitant for us to put something like this in the core distribution
 though, simply because we know it's a maintenance problem over time.

 Fair enough.

 Though I imagine not having this feature will lose puppet some people.
 
 Then lets get a simple text patterns module together for people to use.

But be aware that names like appendifnosuchline do not fit the mental
model that puppet tries to propagate, but are fine for script oriented
configuration management systems such as cfengine or cdist.

Something like:

line{'SftpSubsystem ':
  file = '/tmp/test',
  ensure = (present|absent)
}

fits much more the mental model of puppet. Usually such a statement is a
quick but dirty way to do things and I try to avoid them as much as
possible. Therefore, I completely understand and support the concerns of
Nigel to not include such a feature in the core.

But yes it would be good to have a solid module in the forge where
people can be pointed at.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4DaPMACgkQbwltcAfKi3/eegCgkG3wg+FSkHlMx5Ze6um8jw1M
7woAn1sGv7Jc5vMaSmguIE7Yl6NQYx8z
=F+9W
-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.

Re: [Puppet Users] Concat Module posted to Onyx Point Github.

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi

 After an hour or three of hacking, I've managed to add the insync? checks to 
 both the build and fragment types. It's the first time I've ever really 
 messed with types and providers, so it's very ugly (and probably has bugs), 
 however I'm happy to share my patches. Would that be best a) here b) in 
 puppet-dev, or c) direct to Onyx Point?

awesome! I used your changes and besides some corner cases they looked
fine. I pushed my fixes for these corner cases and also some (initial)
general cleanup of the module on github [1].

Thanks!

~pete

[1] https://github.com/duritong/pupmod-concat/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk30nvcACgkQbwltcAfKi3+o2wCgnPLw0lnd6OBnEb91VazYXCGU
wTYAoJLGtze917x5pw5snvf5oHUNOSjl
=YuBj
-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.

Re: [Puppet Users] Server side filebucket issue

[Peter Meier]

filebucket { puppet:
server = puppetmaster-cbr.it.csiro.au
}


you need to add path = false, as you're hitting a long outstanding bug. [1]

~pete

[1] http://projects.puppetlabs.com/issues/5362

--
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: Open Source Team planning meeting summary

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi

First, I would like to thank for that open process and the commitment
you are putting into that. And I'm really excited that there is now a
team dedicated to address the things in core puppet. Awesome! Thanks!

However, as this thread seemed to become more and more a Please, fix
that bug-list, I would like to tell my story as well:

 I hope this gets resolved too, but the bug ticket says it was pushed to
 2.8.x
 
 
 I asked the core developers to spend some time investigating it a while ago
 to see if we could fix it in 2.6.x, but the report was that this would
 require significant enough plumbing changes that it needs to be done for a
 feature release, and we didn't get it into 2.7.x
 
 If there's an appropriate middle ground we can hit for a solution, I'd love
 to target it earlier if possible.

in the last two days I was bootstrapping a new puppet environment at a
customer's place and I ran into some wtf's of problems I had forgotten
or I haven't encountered so far.

But for nearly every issue I could find a (long) outstanding bug report.
Most of them are about puppet acting in a unexpected way aka ignoring
the principle of last surprise. As usual there are people who started to
depend on that behavior and now we need to make it configurable and the
idea is to wait for a new major release so we can introduce a behavior
change while switching to the more expected way.

None of them seem to be fixed so far for 2.7, so my assumption is that
we have to wait till the next one. :/

Often there are workarounds available or they are not that severe, so
one can live with them. But still: things are broken.

I know we are a bit late to the 2.7 release game, but I still would like
to raise my concerns that to me it sometimes looks like a lot of these
bugs seem to get forgotten more and more and are getting burried within
progress and the available workarounds. But still: things are broken.

I'm going to comment on these bug reports.

One of the major ones I found is that filebucketing is broken (since a
year):

#5362 [1]  #3807 [2] - I really had to do the following to get
filebuckets to the master:

filebucket{main:
  path = false,
  server = puppet,
}
File{ backup = main }

filebucket's got recently some improvements like getting a diff and
displaying the buckets in the dashboard is quite a nice feature. But the
underlying puppet feature is broken for over a year?

Imho this should get the attention it deserves for 2.7.

Actually, I wanted to do here another rant about ENC acting weird, but
while doing more research I actually found a couple of other bug reports
all talking about the same and also one where it looks like this is
going to be fixed. But the history of back and forth is quite amazing :/ ...

So I will link all these bug reports together so you can decide which
one is actually still valid.

I hope you understand my point, otherwise please ask!

Thanks!

~pete

[1] http://projects.puppetlabs.com/issues/5362
[2] http://projects.puppetlabs.com/issues/3807
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3mi30ACgkQbwltcAfKi3+bRwCfY4qnlHA8AtYCHEjMZKIyW7Y5
CC4AoKp3AU3FTuD3LN4G9pzdUGr23h/c
=Inz9
-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.

testing new puppet versions - was Re: [Puppet Users] enabling of 'thin_storeconfigs'

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi

 I'd avoid any version of puppet that ends in a 0 like the plague if you
 want stability.
 
 
 The project has been steadily improving in this regard, but it's definitely
 been a problem.
 
 I have great hopes for 2.7.0 though, and the more people that test out our
 RCs (hint! hint!) the better it's going to be.

Awesome would be some kind of script with which I could test the new
release. Something with puppet cucumber, that people could run and that
would simply try to compile all the catalogs for their hosts and maybe
also comparing the catalogs to the ones of the currently installed version.

Also it could record compile time etc. so we wouldn't fall into another
regression as we did with 2.6.0

I know more or less how I could do that with puppet-cucumber and R.I.'s
catalog-diff but I lack a bit the time to setup that. But I would
certainly download a tarball and run the script that I only need to
point to my puppet.conf and send the feedback on that.

I think this could be in general useful for future releases.

Yeah I know, I'm just throwing in ideas that don't contain actual
code... Sorry.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3f0GsACgkQbwltcAfKi3/bNACeOw2bAr+oYL3VGoWZSLJWCpni
bl4AoIx0j7pTlabE4jAkGUEX8hpbxOv0
=2EUf
-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.

Re: [Puppet Users] ruby 1.9.2 rpms for testing

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi

   I noticed from the list that puppet is not ready for ruby 1.9.2 yet.
 I'm working at a ruby shop so I gave a shot at building ruby 1.9.2 rpms
 with supporting gems for RHEL/CentOS.  I have ruby-1.9.2 rpms that
 replace the vendor rpms and ruby192 rpms that install in parallel with
 the vendor rpms.
 
   Is anyone interested in using these rpms to get puppet working with
 1.9.2 and/or other ruby code?

definitely! This would probably also support early adopters. Maybe you
could publish the spec files somewhere? Like on github?

Awesome! Thanks!

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3cImkACgkQbwltcAfKi3+gsgCeLJXMmZe7EOI10uXyDaj/VEc8
dcMAmgIkai1CQIRY7FG4XaJgI4nI3ncT
=TsFu
-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.

Re: [Puppet Users] Re: Applying Catalogs

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Yushu,

 My case is a little bit different. Because my webserver might need the IP
 address of the mysql node, and before mysql node is deployed and configured,
 it's IP address is not known.

you should probably look into exported resources and export the IP of
the mysql server to all your webnodes. If that's a feasible approach.

Otherwise it is still unclear why you want different catalogs for each
service.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3cMIEACgkQbwltcAfKi39YEwCcDfBNZ3ZIFrq1qSrwicTd8u0u
xa8AnR8+EqQkndo8cue+qwTWgUiP7TM/
=4tiU
-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.

Re: [Puppet Users] PC EU feedback: exported resource syntax is too magical, hard to read

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 If you really want to simplify people's life, make those extra
 attributes become metaparameters (but please keep the old syntax):
 
 user { luke: ensure = present, virtual = [boolean] }
 
 That would even allow us to parametrize virtuality/exportability with
 the help of an expression (ie selectors, functions, boolean expressions ...)

awesome!

+1

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3cM2YACgkQbwltcAfKi38nlACfQZ7M5Lc9UoLruDr99VmEG21o
vKAAoIeR39sgLeQO90Uu5qGRyVpWFyhc
=nJQx
-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.

[Puppet Users] Next SPUG Meeting 19.5.2011 @swisstopo in Bern - 19.00 o'clock

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

The Swiss Puppet User Group (SPUG) meets again on Thursday 19th May.

If you like to attend the meeting, please announce your attendance to
Hanspeter Christ (hanspeter.christ(at)swisstopo.ch), as noted in the
announcement mail.

If you like to receive any future announcements, please subscribe to the
low traffic list s...@lists.saitis.net [1]

~pete

[1] http://lists.saitis.net/cgi-bin/mailman/listinfo/spug

- -

Hi

After a short but recreative hibernation the SPUG meets again to
discuss, explore and share the interesting world of puppet managed
systems. We would like to invite you this time to the offices of
Swisstopo (Switzerland?s national cartography agency) in Bern. We set
the date right after the upcoming PuppetCamp [1] in Amsterdam, as
various people around the SPUG are attending the PuppetCamp and we
thought that it would be interesting if the attendees could report back
about what is going on in the wider puppet community.

So we meet on

Thursday 19. May
at 19.00 o'clock

at the offices of Swisstopo, which are located at

Seftigenstrasse 264 in Wabern near Bern. [2]

Arriving there is quite simple: Take Tram #9 in direction of Wabern and
drive till Eichholz or the final station Wabern. The offices of
Swisstopo are located within these two stations. For detailed
information have a look at [2].

Attention: May 19th is a week later than a date that have been
previously leaked to a few people. So if you already knew about the
upcoming meeting, please adjust your calendar.

We would like to ask interested people to send a simple e-mail to
Hanspeter Christ (hanspeter.christ(at)swisstopo.ch) with the Subject
Teilnahme spug meeting @swisstopo to register their attendance.

Drinks and Snacks are provided.

Furthermore we are looking for people that would be willing to
present/discuss/share/ask/... something about their usage with puppet or
related tools, so we could have a few presentations to announce. This
can be in a very short manner, even only 30s presentation or a bit
longer ones, like 5 or a bit more minutes. Please send your presentation
idea to Marcel Härry (mh (at) scrit.ch), so we can announce them prior tothe
meeting. But it will also be possible to spontaneously give a lightning
talk at the meeting. A beamer and a Linux-based laptop will be available.

We can already announce a few short presentations:

Hanspeter Christ of Swisstopo will talk about how a puppet managed
infrastructure is seen from a IT Project Manager's point of view and
will share his experience in managing a team that completely automates
the infrastructure with puppet.

Another one will be held by Marc Fournier (Camptocamp SA). He will show
how to use the cucumber testing framework to refactor your manifests and
change Puppet versions without becoming insane.

Marcel Härry (Puzzle ITC) will talk about the new introduced Ruby-DSL
of Puppet and a use case where the Ruby-DSL provided more flexibility
than the common external Puppet-DSL.

Yet to be confirmed, Mathieu Bornoz (Camptocamp SA) would like to show us
how he hooked a CouchDB CMDB to Puppet to be able to create/edit/remove
resources properties without having to edit manifests.

If you have further questions do not hesitate to ask on the
SPUG-List ( spug (at) lists.saitis.net ). If you haven't done so, please
subscribe to this low-traffic list, where we will also announce further
meetings.

Information about this meeting is also available on http://spug.ch/

Cu there!

Hanspeter Christ, Marc Fournier and Marcel Härry
for the SPUG


[1]
http://www.puppetlabs.com/community/puppet-camp/puppet-camp-ams-2011-info/
[2]
http://www.swisstopo.admin.ch/internet/swisstopo/en/home/swisstopo/contact/train.html
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3I7TkACgkQbwltcAfKi38SKgCfYeET7Y2fGfgp+1NxVqj2FgqT
qicAnAlbfTU+pQDZRM0CIUMhHWLON1Qo
=Ru3m
-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.

Re: [Puppet Users] parse puppet yaml in java

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 I am playing with snakeyaml and trying to use a custom class to parse
 yaml returned by puppet as mentioned in
 http://code.google.com/p/snakeyaml/wiki/Documentation#Custom_Class_Loader
 
 But I am not sure how to deal with --- !ruby/object:Puppet::Run: and
 !ruby/sym report: !ruby/object:Puppet::Transaction::Report
 
 These seem to be ruby specific.

afair you should be able to just strip that off, before pass it to the
yaml reader. There have been some discussion about that on the list and
I think this was the solution.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk27WQAACgkQbwltcAfKi3+ImQCglHbndbFbCczd8FsDC2vS9Y8O
LXYAoITcmr+RrGDxB+GVm5FTo7o7Ram4
=marw
-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.

Re: [Puppet Users] Re: Passenger

[Peter Meier]

 Thanks for the reply. Is there a way to install passenger without a
 compiler?

Friends of Phusion (Passenger People) are now providing RPMs for
Passenger:
http://blog.phusion.nl/2011/01/04/phusion-passenger-native-packages-for-redhatfedoracentos/

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

Re: [Puppet Users] empty files being served from puppet master

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 I'm assuming this might be the clients running an older version?

likely, as imho the clients are actually the ones dealing with the
exception.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk1+s2QACgkQbwltcAfKi3+SBQCdGHWZrnfQiUx8RYORmLDakAAU
oYYAn2bYtyEqGwhWLNZxuwojnScmS+Tm
=8DjO
-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.

Re: [Puppet Users] Re: class + each do

[Peter Meier]

 You made a class for it? As it sounds like it's not getting called at all.

 Yes.I did a class for this:

are you including this class somewhere?

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

Re: [Puppet Users] Re: returning a hash (json object) from custom function?

[Peter Meier]

 Ok, I was mistaken.  Returning a hash works.  It would be helpful if
 the ruby exceptions bubbled up to puppet reported the correct line
 number from the ruby source -- if that is possible.

Could you file a bugreport[1], if there isn't yet one? Thanks!
Then the chances are high that it will get fixed.

~pete

[1] http://projects.puppetlabs.com/projects/puppet

-- 
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] scheduler problem?

[Peter Meier]

the notify is executed only once but tidy still during each run.

is this a bug or a feature? if a bug, is it fixed in some recent version?


I would say a bug. Check the bug tracker:  
http://projects.puppetlabs.com/projects/puppet/issues for any open or  
closed bugs regarding that problem and if you don't find one: Please  
file a bug report.


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

Re: [Puppet Users] sysctl type not available

[Peter Meier]

 from http://projects.puppetlabs.com/projects/1/wiki/Puppet_Modules
 
 wanted to take a look at sysctl type but it's not available.
 
 http://spook.wpi.edu/sysctl
 
 Anyone could give it a look?

As far as I remember this one:
http://git.puppet.immerda.ch/?p=module-sysctl.git;a=summary

was originally based on that one.

~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-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] Exactly how do people replace include with parametrised classes?

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 dont you find having to specify the relationships of httpd::ssl and
 httpd here to be wrong?
 
 Isn't the fact that the httpd module is designed to have this
 ordering requirement an implementation detail and not a usage
 detail?
 
 Surely people who just want to use the httpd module do not need to
 know this implementation detail?  They should just be able to say use
 the module without understanding or knowing the ordering of
 internals.

 It's also not very DRY.

Yep, I also recently started thinking about various new introduced
problems I see with parametrized classes. For example, how could I do
the following in the future with parametrized classes:

class apache {}
define apache::vhost(){
  include ::apache
  ...
}

so the user only needs to define:

apache::vhost{'example.com': }

and everything else is pulled in automatically.

This gives a very nice interface, is easy to use and if this way of
writing puppet code wouldn't be anymore possible my infrastracture code
would get *very* overloaded and ugly.

And as R.I.Pienaar outlined later, we learned in the past to deal with
the current scoping problems, but still producing more or less nice
code. Although, I agree that parametrized classes provide a much nicer
interface and I'm very happy they got introduced, I'm already seeing
some problems with them:

class apache($version = 'latest') {}
define apache::vhost(){
  class{'apache': }
  ...
}

This will raise problems if we define a second vhost. With the current
scoping issues and my rule of thumb (First define all variables, then
include classes) I had no problem with writing:

$apache_version = '2.2.18'
apache::vhost{'example.com': }
apache::vhost{'cdn.example.com': }

But how would I do that now?

A possible solution would be to put the variables in a config class:

class apache::config($version='latest'){}
class apache {
  package{'apache':
ensure = ${apache::config::version},
  }
}
define apache::vhost(){
  include ::apache
  ...
}

and then write:

class{'apache::config': version = '2.2.18' }
apache::vhost{'example.com': }
apache::vhost{'cdn.example.com': }

But how can I ensure that apache::config is loaded/included/applied when
we include ::apache?

I currently only see:

class apache {
  if !defined(Class['apache::config']){
class{'apache::config': }
  }
  package{'apache':
ensure = ${apache::config::version},
  }
}

But this raises other ordering problems and breaks another rule of thumb
of mine: Never use defined() as it can be seen as codesmell, for example
exactly due to the ordering problems it raises.
But this is the best solution I can currently come up with. Although, it
still smells in my opinion.

~pete

PS: Sorry, to come up with code examples, however I think I can express
the current *new* limitations with them the best way. I will try to
think about a non-code discussion contribution and maybe add it later to
the thread.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0rgaYACgkQbwltcAfKi38w4gCeJ8j3B6zcilYnXicgambV5Ty7
eqwAn1L86SUkKuMYwKTnVopNNgNntBBW
=ODmw
-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.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: Considerations for puppet/cluster to manage 6000 hosts.

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 You'll need one or more mysql servers if you use storedconfigs.  
 Storedconfigs can be useful, but will drastically increase the server CPU 
 usage and will require a mysql backend.  You can always turn it on later.
 
 One or more *SQL* servers: we ran happily on PostgreSQL 8.4, which we
 found scaled much better than MySQL did, and was our standard server
 platform anyway.  Otherwise I absolutely agree with this. :)

If you are only interested in exported resources then you might want to
enable thin_storeconfigs, which will reduce the load also drastically.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0p1cwACgkQbwltcAfKi38e1QCfck1x+ee5DtBxrHAerSHgNkTC
ImEAnjvxy/8yrh4v1elvLz4INF5sA5NO
=BOdC
-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.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: Exit gracefully

[Peter Meier]

 Thanks. That should do it. Like a lot of things in puppet, not pretty, but
 it will get the job done.

I think your idea is not that bad and it's simply not *yet* possible
with puppet. Hence, the best goal towards a pretty solution in puppet is
to raise a feature request for such a function:
http://projects.puppetlabs.com/projects/puppet

~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-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] Small documentation addition

[Peter Meier]

 Maybe it can be noted in the text, that on Debian and Ubuntu, the package
 is called 'librrd-ruby'.

the best thing would be to open a documentation bug report. Oh and maybe
even supply a patch?

http://docs.puppetlabs.com/contribute.html

~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-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] Small documentation addition

[Peter Meier]

 Doesn't that seem .. I dunno.. insanely bad?

I wrote *maybe* (you seem to be able to read...) so what's your problem?

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