On 21 January 2014 06:47, Muhammad Yousuf Khan wrote:
>
>
> On Monday, January 20, 2014 8:01:13 PM UTC+5, Felix.Frank wrote:
>>
>> Hi,
>>
>> On 01/20/2014 03:25 PM, Muhammad Yousuf Khan wrote:
>> > hello guys,
>> >
>> > i am new to puppet and few days back have installed motd module for
>> > test
The fundamental problem is that such information is only going to be
accurate to the last
Puppet run, it's not realtime. Hence the need for some sort of
external orchestration (which
you'd get for free with DNS/DHCP data). Other options are of course available.
On 21 January 2014 07:25, Jose Luis
Hi community, I need a suggestion.
Some of my modules like nagios or nfs shares are having a lot of static
data which needs to be defined in the bottom of hierarchy.
It makes my file generic.yaml quite massive and not that readable.
What are the options do I have to separate this into more structur
On 01/21/2014 07:41 AM, Dirk Heinrichs wrote:
> Opposed to what Felix is thinking, my previous message was meant
I thought so, but have issues with the notion that /etc/hosts is to be
ignored in favor of DNS in any production environment.
> seriously. I don't see a trivial solution to your proble
I have my Puppet installation up and running, but I currently just run
"puppet agent --test" to use it. As I understand it, in a master/agent
configuration, Puppet automatically runs every 30 minutes by default as
long as the service is running.
With Puppet 3.4.2 on OS X, is there still a need
For example with this code
yumrepo { 'erlang':
baseurl => '[url_repo]',
enabled=> 1,
gpgcheck => 0,
}
package {'erlang':
ensure => installed,
require => Yumrepo['erlang']
}
I look for solutions that disable epel (and that's what I used) but is
there any solut
On Monday, January 20, 2014 8:25:18 AM UTC-6, Muhammad Yousuf Khan wrote:
>
> hello guys,
>
> i am new to puppet and few days back have installed motd module for
> testing this is my first module working great however i just see too many
> change messages since the day motd module has install
On Monday, January 20, 2014 9:17:39 AM UTC-6, ak0ska wrote:
>
> Hello,
>
> We wanted to created a query, which would check the hostgroup fact of
> machines that apply a certain type of resource declared in a certain
> manifest file. We wanted to use the 'select-resources' subquery as follows:
>
Hi,
I am the deploying the puppet master rpm 3.4.2 onto a centos 6.3 VM using
the following script files but output reports the error 'Report processor
failed: uninitialized constant Puppet::FileSystem::File', has anyone seen
this error?
** SITE.pp ***
import "nodetypes/*.pp"
E
Sounds interesting. Checked it out, but it doesn't seem that SugarCRM's
config.php supports xml.
--
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+un
On Monday, January 20, 2014 8:52:34 AM UTC-6, zerozer...@gmail.com wrote:
>
> Hi,
> as far as I understand, spacing should usually not be an issue in
> manifests between the attribute name and the "arrow", right?
>
>
Right.
> For example, for a "host" type resource:
>
> ip => "192.168.1.1
On Friday, January 17, 2014 8:01:08 PM UTC-6, Sam Rajagopal wrote:
>
> I have the exec resource defined as follows, to be able to install
> tcserver using a command line, inside of my init.pp. For some reason, it is
> not able to execute the install command, when I run puppet agent -t on the
>
On Tuesday, January 21, 2014 9:15:50 AM UTC-6, jcbollinger wrote:
>
> First, it looks like you want
>
> provider => 'shell'
>
> in your command.
>
Sloppy. I meant you want to add that to the parameters of your Exec.
Sorry for any confusion.
John
--
You received this message because you
On Sunday, January 19, 2014 3:34:39 PM UTC-6, Erwin Bogaard wrote:
>
> Hi,
>
> I'm looking into a way to manage the SugarCRM config.php (see partial
> example below this message). This proposes several problems:
> 1. The file is full of arrays and arrays-in-arrays (So I think Augeas is
> useles
Yeah, that looks like a bug Akos. Can you file it?
On Tue, Jan 21, 2014 at 2:49 PM, jcbollinger wrote:
>
>
> On Monday, January 20, 2014 9:17:39 AM UTC-6, ak0ska wrote:
>>
>> Hello,
>>
>> We wanted to created a query, which would check the hostgroup fact of
>> machines that apply a certain type o
On Mon, Jan 13, 2014 at 3:47 PM, Ben Hines wrote:
> Howdy,
>
> My organization has a pre-existing hiera configuration which uses
> {calling_class}.yaml configuration files, like:
>
> classes/base::openldap.yaml
>
> Which get pulled into hiera via this path in the hierarchy.
>
> :hierarchy:
> ...
The 1.8.7 ruby, rubygems and its gems were uninstalled. The root .gem and
user .gem directories were also removed. I am hunting for what I am
overlooking.
I am now looking at using the yum package to install puppet. Listed below
are the results of the package install. Notice it's trying to ins
On Tuesday, January 21, 2014 3:13:49 PM UTC-5, machete wrote:
>
> The 1.8.7 ruby, rubygems and its gems were uninstalled. The root .gem and
> user .gem directories were also removed. I am hunting for what I am
> overlooking.
>
> I am now looking at using the yum package to install puppet. List
Fedora 18 reached end of life on 2014-01-14 [1], so we are no longer
building new packages for it and will remove it from our yum
repository on Monday, March 18.
[1] -
https://lists.fedoraproject.org/pipermail/test-announce/2014-January/000848.html
Rob Braden
Puppet Labs
Join us at PuppetConf 20
My question would be what are you doing with nagios that need so much
static data?
My monitoring module uses facts and one or two static vars.
I would suggest putting defaults in your modules so you don't need to
set so many variables.
Basing those defaults of custom facts would help reduce your n
I am pretty sure you still need to setup the launch daemon manually on OS X.
On 21 January 2014 06:55, Jason Hatman wrote:
> I have my Puppet installation up and running, but I currently just run
> "puppet agent --test" to use it. As I understand it, in a master/agent
> configuration, Puppet aut
**Release Candidate**
Hiera 1.7.5-rc1
---
*Pre-release*: Facter 1.7.5 is not yet released.
- RC1: January 21, 2014.
Facter 1.7.5-rc1 Downloads
--
Source: https://downloads.puppetlabs.com/facter/facter-1.7.5-rc1.tar.gz
On 21 January 2014 00:33, Erwin Bogaard wrote:
> Hi Pete,
>
> thanks for your reply.
> I thought I replied to you last night, but Google doesn't show it. So here
> it is again:
>
> The difficulty with using a template, is that there are just too many
> exceptions between the instances. Some keys o
On 2014-10-01 22:13, Daniele Sluijters wrote:
So I'd like to propose two things:
* If you're going to FOSDEM, reply to this e-mail, drop a line with
your name, nickname and if you're comfortable with it, a picture so that
people might recognise you;
* Join the meetup, which will likely involv
So how did you install Ruby 1.9.3? Did you create your own RPM or use
something else? The RPM packages for puppet will have dependencies
and then yum will try to satisfy them by looking in it's configured
yum repositories. It usually tries to find the latest version.
Looking at your output it lo
Hi Jason,
Pete is correct. The OSX puppet package does not ship with a launchd
plist. That example appears mostly up-to-date, with the notable
exception RUBYLIB (in 3.4.0 puppet moved to /Library/Ruby/Site for
compatibility with Mavericks) and the ServiceDescription and
ServiceIPC keys that don't
Hello all,
I'm attempting to follow along in the puppet book with the ssh module
lesson. I'm at the part where I'm attempting to use a variable that's been
set in another class called ssh::params. When I run the puppet on the
client I get the following error:
[root@beta:~] #puppet agent --test -
Hey all,
Sorry but I forgot to include a key piece of information in that last
email.
In the ssh class I have defined in the modules init.pp I had this
definition:
class ssh {
include ssh::install, ssh::config, ssh::service, ssh::params
}
But then I read on into the book a little more
Those are mostly definitions of custom checks to export + templates which
group those checks by server types
On 21 Jan 2014 22:40, "Pete Brown" wrote:
> My question would be what are you doing with nagios that need so much
> static data?
> My monitoring module uses facts and one or two static var
Copied from another thread:
:hierarchy:
...
- "%{environment}/classes/%{calling_class}
Perhaps it is easier that way.
Regards
--
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,
30 matches
Mail list logo
