On the RPM repo at http://yum.puppetlabs.com/el/5/products/x86_64/,
the puppet-server rpm for 2.7.4 seems to be missing.
el5
puppet-2.7.4-1.el5.noarch.rpm
---
el6
puppet-2.7.4-1.el6.noarch.rpm
puppet-server-2.7.4-1.el6.noarch.rpm
--
You received this message because you are subscribed to the Go
Hi all,
One of my facter variables returns an array of disks presently connected
to the system. I want to have something in my manifest that loops around
the array and adds a Nagios check for each disk.
In perlish pseudocode, I imagine something like this:
@disks = sda,sdb,sdc
foreach $disk
- Original Message -
> Hi all,
>
> One of my facter variables returns an array of disks presently
> connected
> to the system. I want to have something in my manifest that loops
> around
> the array and adds a Nagios check for each disk.
>
> In perlish pseudocode, I imagine something li
R.I.Pienaar:
> here's a very simple one that loops an array and create 'notify'
> resources:
> define print { notify{"the message is: ${name}": } }
> print{["one", "two", "three"]: }
Strictly speaking, this isn't really "looping" on the array so much as
"mapping" on the array (there may be a more
Hi,
I am currently testing my catalog, that runs fine with 2.6.3, with Puppet
2.7.4. Now I am running into a problem, and I wonder why this was 'fixed'
in Puppet the way it was.
Please consider http://projects.puppetlabs.com/issues/7888
In Puppet 2.7.4, there is code [1] that prevents ssh_author
On Sep 29, 2011, at 7:35 AM, Martijn Grendelman wrote:
>
> Hi,
>
> I am currently testing my catalog, that runs fine with 2.6.3, with Puppet
> 2.7.4. Now I am running into a problem, and I wonder why this was 'fixed'
> in Puppet the way it was.
>
> Please consider http://projects.puppetlabs.com/
On Sep 28, 5:38 pm, Sans wrote:
> Thanks Peter!
> Custom fact is a great idea but the downside is one needs to create a
> custom-fact each for every check you wanna perform. Isn't there
> anything a bit more dynamic, like checking the location on fly ( bash
> equivalent: if [ -d "/var/torque/mom
http://biggerbras.ca/store/site.php?html50
--
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.c
*sigh* And how did these spammers know I was so flat-chested?
Seriously, can you guys enlighten us as to what's being done to prevent spam
coming in on the list? It's been pretty prevalent lately. I'm not sure if
Google Groups just doesn't cut it or what, but I'm hoping you guys have some
plans in
I just wanted to take a minute to thank you for working on these packages.
Having first class packages like this available is absolutely vital and
it's both helped me internally bring up Puppet faster as well as helped me
advocate the product to several other people lately by being able to point
t
On 29-09-11 14:03, Jonathan Stanton wrote:
> On Sep 29, 2011, at 7:35 AM, Martijn Grendelman wrote:
>>
>> Hi,
>>
>> I am currently testing my catalog, that runs fine with 2.6.3, with Puppet
>> 2.7.4. Now I am running into a problem, and I wonder why this was 'fixed'
>> in Puppet the way it was.
>>
On Thu, Sep 29, 2011 at 01:35:15PM +0200, Martijn Grendelman wrote:
> Hi,
>
> I am currently testing my catalog, that runs fine with 2.6.3, with Puppet
> 2.7.4. Now I am running into a problem, and I wonder why this was 'fixed'
> in Puppet the way it was.
>
> Please consider http://projects.puppe
You should totally boycott the list
On Sep 29, 2011 7:15 AM, "Nathan Clemons" wrote:
> *sigh* And how did these spammers know I was so flat-chested?
>
> Seriously, can you guys enlighten us as to what's being done to prevent
spam
> coming in on the list? It's been pretty prevalent lately. I'm not
On Thu, Sep 29, 2011 at 1:24 AM, rvlinden wrote:
> On the RPM repo at http://yum.puppetlabs.com/el/5/products/x86_64/,
> the puppet-server rpm for 2.7.4 seems to be missing.
>
> el5
> puppet-2.7.4-1.el5.noarch.rpm
> ---
Fixed now. It was in i386 but not linked into x86_64.
>
> el6
> puppet-2.7.
We were using Naginator resources like nagios_host, etc. along with stored
configurations and exported resources. Worked pretty well. However we have to
separate the Puppet master and the Icinga (Nagios) server. They will be on
different machines from now on. Are there any best practices for suc
On Thu, Sep 29, 2011 at 7:22 AM, Ashley Penney wrote:
> I just wanted to take a minute to thank you for working on these packages.
> Having first class packages like this available is absolutely vital and
> it's both helped me internally bring up Puppet faster as well as helped me
> advocate the
So, I have all the nodes export their Nagios stuff, and all my Nagios hosts
then collect what they need (via tagging). The only tricks I used were to
override the file locations so that everything actually gets put into a test
directory, and then have an exec kicked by changes which runs a pre-
Hi,
In class parameters, things like x="x", y="y${x}" don't always evaluate
right (y="yx"), seems random. I'm using 2.7.1
class test1(
$servicex = "sonar",
$logfoldera = "${homex}/logs",
$logfoldere = "${homey}/logs",
$logfolderh = "${homez}/logs",
$logfolder = "${homex}/l
I raised a bug earlier https://projects.puppetlabs.com/issues/9766 which
could be a can of worms.
My opinion is, facter has a bug and needs (eventual) fixing even if it
causes problems for some. There is a reason we have changelogs.
Debate?
--
You received this message because you are subscribe
Sounds good. Will start trying this tomorrow and post the results when done.
Thanks!
Bernd
> -Ursprüngliche Nachricht-
> Von: puppet-users@googlegroups.com [mailto:puppet-
> us...@googlegroups.com] Im Auftrag von Brian Gallew
> Gesendet: Donnerstag, 29. September 2011 17:54
> An: puppet-u
On Sep 28, 5:02 pm, rvlinden wrote:
> Hi,
>
> I'm using puppet 2.7.3 on RHEL/CentOS and I have an issue which is now
> a big blocking issue within my environment. What I'm trying to
> accomplish wit puppet is a create a mountpoint, mount a filesystem on
> it and install an application on that fi
Facter 1.6.1 is a maintenance release containing fixes, updates and
refactoring. Significant effort has been put into getting to Facter to
run on Windows for this release, as noted below.
This release is available for download at:
http://puppetlabs.com/downloads/facter/facter-1.6.1.tar.gz
See th
Carlos,
This seems to be a bug as things be weirder the more I test.
class test1(
$servicex = 'servicex',
$servicey = 'servicey',
$service1 = "/bar/${servicex}",
$service2 = "/bar/${servicey}",
$homex= 'homex',
$home1= "/bar/${homex}"
) {
notice($service1)
notice(
Is it really a good idea to have a period/dot in the hostname?
Although I do agree it should be considered as a bug in terms of
"good" programing. Cheers!!
On Sep 29, 3:25 am, Doug Balmer wrote:
> I raised a bug earlierhttps://projects.puppetlabs.com/issues/9766which
> could be a can of worms.
>
Technically, a hostname may not legally contain a dot. A fully qualified
domain name, OTOH, pretty much has to have (at least) one dot.
On Thu, Sep 29, 2011 at 10:59 AM, Sans wrote:
> Is it really a good idea to have a period/dot in the hostname?
> Although I do agree it should be considered as
Background:
I like to keep installed apps in a non-standard area and sym link to
the binaries, libraries and other files through the /usr/local tree so
that they're in the user's path. The purpose of this is to help with
software versions, upgrades and to allow me to keep multiple versions
of apps
On Thu, Sep 29, 2011 at 12:25:23PM +1000, Doug Balmer wrote:
>I raised a bug earlier [1]https://projects.puppetlabs.com/issues/9766
>which could be a can of worms.
>My opinion is, facter has a bug and needs (eventual) fixing even if it
>causes problems for some. There is a reason we
> On Sep 27, 8:44 pm, Jo Rhett wrote:
>> You can't do that, as the IF code is resolved by the puppet master before
>> delivering the compiled catalog to the client. It looks like you want to
>> just make a shell script, push it to the client and run it there.
On Sep 28, 2011, at 7:03 AM, jcbol
>
> 'Note that periods are only allowed when they serve to delimit components
> of "domain style names".'
>
Let's give this sentence some context.
ASSUMPTIONS
1. A "name" (Net, Host, Gateway, or Domain name) is a text string up
to 24 characters drawn from the alphabet (A-Z), digits (0-9
On Thu, Sep 29, 2011 at 5:28 PM, Doug Balmer wrote:
> 'Note that periods are only allowed when they serve to delimit components
>> of "domain style names".'
>>
>
> Let's give this sentence some context.
>
>
> ASSUMPTIONS
>
>1. A "name" (Net, Host, Gateway, or Domain name) is a text string
>
> but I don't think that RFC quoting alone is going to give us the right
> answer as to whether we should do it or not.
>
100% agree.
To add to my point, facter should be reporting facts. If the hostname,
albeit possibly incorrectly, is set to "foo.bar" then it should report it
so.
--
You re
Except that is the fqdn.
On Sep 29, 2011 7:05 PM, "Doug Balmer" wrote:
>>
>> but I don't think that RFC quoting alone is going to give us the right
>> answer as to whether we should do it or not.
>>
>
> 100% agree.
>
> To add to my point, facter should be reporting facts. If the hostname,
> albeit
So Dexter P sent me an email on this and I want to paraphrase:
"I understand there are major implications to this and the task may be
challenging, one suggestion would be to set up another facter
parameter something like
uname.hostname
or
uname.domain
or perhaps a configuration parameter to us
>
> Except that is the fqdn.
>
No. "foo.bar" could be the hostname but foo.bar.example.com could be the
FQDN.
--
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 fro
>
> "I understand there are major implications to this and the task may be
> challenging, one suggestion would be to set up another facter
> parameter something like
>
> uname.hostname
>
> or
>
> uname.domain
>
> or perhaps a configuration parameter to use POSIX compliance parameters."
>
> Which ma
>
> Our concept of 'hostname' as a fact is equivalent to hostname -s up
>> until now - it doesn't mean the result of the 'hostname' command
>> necessarily.
>
>
> This makes sense and is an easy compromise. Could I suggest the doco
> reflect that $hostname is `hostname -s`?
>
... or at least your d
36 matches
Mail list logo
