Yes i intended to pass a variable to a class through node definition.
Could you please show me an example of the syntax please ?
Message initial
De: Michael DeHaan
Reply-to: puppet-users@googlegroups.com
À: puppet-users@googlegroups.com
Sujet: Re: [Puppet Users] Templates : abou
On Mon, Mar 22, 2010 at 10:50 PM, John Warburton wrote:
> The issue isn't organising puppet, but dealing with a global team of 50
> people who may or may not really understand what they are dealing with
>
> I was thinking that rather than find out too late that someone has tried to
> manage the sa
I have such a setup :)
what we ended up using is some sort of a define to the file statement, which
search in different places based on some logic.
at the end of the day, it depends on the usage cases, based on your ACL
(e.g. who is allowed to change what in your manifest etc).
my 2 cents,
Ohad
The issue isn't organising puppet, but dealing with a global team of 50
people who may or may not really understand what they are dealing with
I was thinking that rather than find out too late that someone has tried to
manage the same file in muliple modules, I was wondering if putting all file
su
You could probably create your own function, which checks if a file exists
and if it does call the template function on it.
Ohad
On Tue, Mar 23, 2010 at 1:23 PM, Douglas Garstang
wrote:
> On Mon, Mar 22, 2010 at 7:15 PM, Ohad Levy wrote:
> > Hmm.. Puppet does not support going over multiple te
On Mon, Mar 22, 2010 at 7:15 PM, Ohad Levy wrote:
> Hmm.. Puppet does not support going over multiple templates like it does in
> plain files.
>
> maybe there is even a feature request for it ;)
Aw crap. I've been told that twice in the last few days. Is there
another way I could emulate this fun
Why not simply using inheritance? or alternativly, have a source search
order?
e.g. find the first files it find.
in moduleA, modubleB, common
if you really need to manage different parts of the file in different
modules, you might want to look for volcane concat module.
cheers,
Ohad
On Tue, Mar
Hi,
You can achieve that with a few options:
1. use storeconfigs, export and collection will allow your nfs clients to
export, and your nfs server to collect the list of machines.
maybe not usable if you have a large setup (or multi location puppetmaters).
2. parse the yaml files on the master (e
Hmm.. Puppet does not support going over multiple templates like it does in
plain files.
maybe there is even a feature request for it ;)
Ohad
On Tue, Mar 23, 2010 at 6:34 AM, Douglas Garstang
wrote:
> Can someone tell me why this works:
>
> file {
>"/etc/sudoers":
>source =>
Hi,
I have a similar structure, but the modules them self are versioned, so
instead of putting the real module in the env directory, I use links (which
are managed by puppet), e.g.:
/etc/puppet/env/global_puppetmaster
apache2 ->
/etc/puppet/modules/stable/services/apache2_0.2/
co
On Mon, Mar 22, 2010 at 6:25 PM, Scott Smith wrote:
> On 3/22/10 1:26 PM, Paul Lathrop wrote:
>>
>> Scott,
>>
>> I know it defaults to production if a environment is not specified.
>> However, that's not the case here. The client *is* specifying an
>> environment, the server doesn't know about tha
On 3/22/10 1:26 PM, Paul Lathrop wrote:
Scott,
I know it defaults to production if a environment is not specified.
However, that's not the case here. The client *is* specifying an
environment, the server doesn't know about that environment. I think
this is different than what you are describing
I have same structure, but interested if there is any other out there.
On Mon, Mar 22, 2010 at 4:33 PM, Nigel Kersten wrote:
> You should use 'lib' instead of 'plugins' for 0.25.x clients.
>
> Otherwise that's exactly how I have things laid out.
>
>
> On Mon, Mar 22, 2010 at 4:24 PM, Allan Marcu
On Mon, Mar 22, 2010 at 5:32 PM, chuck clark wrote:
> I'm using puppet 0.25.2 in a RHEL5 environment and Glassfish is one of the
> resources under management. Managing the Glassfish configuration is proving
> troublesome.
>
> I have a glassfish module with a glassfish class which has the followi
>
> I think a custom resource to drive asadmin is probably the right way to go.
> What version are you using?
> As of Glassfish v3 there's a good REST API ( v3asadmin is essentially
> a http client).
> See the article here:
>
> http://blogs.sun.com/aquatic/entry/glassfish_rest_interface_for_managem
I'm using puppet 0.25.2 in a RHEL5 environment and Glassfish is one of the
resources under management. Managing the Glassfish configuration is proving
troublesome.
I have a glassfish module with a glassfish class which has the following
file resource definition:
"/opt/glassfish/domains/pulse
Hi All
I've done a small scale puppet (130 servers) implementation per the book and
had my files hierarchy under each module:
modules/module1/files
modules/module2/files
modules/module3/files
etc
This worked fine because we only had a small number of people working on the
project
You should use 'lib' instead of 'plugins' for 0.25.x clients.
Otherwise that's exactly how I have things laid out.
On Mon, Mar 22, 2010 at 4:24 PM, Allan Marcus wrote:
> hello,
>
> Is this directory structure for modules still recommended, or is there a
> better way?
>
> http://projects.reduct
hello,
Is this directory structure for modules still recommended, or is there a better
way?
http://projects.reductivelabs.com/projects/puppet/wiki/Module_Organisation
We are thinking of having a directory for each environment, then broken down as
recommended here:
http://projects.reductivelab
Hello all,
On several servers, I get the following outputs in the syslog files,
especially after log rotation :
puppetd: Reopening log files
puppetd: Starting Puppet client version 0.24.5
puppetd: Configuration retrieval timed out
puppetd: Starting catalog run
Is there a link between log rotatio
Can someone tell me why this works:
file {
"/etc/sudoers":
source => [
"puppet://$server/security/etc/sudoers:${fqdn}",
"puppet://$server/security/etc/sudoers"
],
owner => root, group => root, mode => 440,
}
but, this doe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/03/10 7:26 AM, Paul Lathrop wrote:
> Scott,
>
> I know it defaults to production if a environment is not specified.
> However, that's not the case here. The client *is* specifying an
> environment, the server doesn't know about that environment.
Hi,
I'd like to hear some idea's on how to do the following with puppet:
Suppose I have a node that implements a certain server class, eg. nfs-
server,
and some other nodes that implement a class nfs-client.
I'd like all nodes that implement nfs-client to contain a reference to
the node that impl
On Mon, Mar 22, 2010 at 2:24 PM, Julian Simpson wrote:
> I'd expect it to fail in such a way that the puppet run could not happen.
> Anything else could have worse consequences.
++
> J.
>
> On 22 March 2010 20:26, Paul Lathrop wrote:
>>
>> Scott,
>>
>> I know it defaults to production if a env
I'd expect it to fail in such a way that the puppet run could not happen.
Anything else could have worse consequences.
J.
On 22 March 2010 20:26, Paul Lathrop wrote:
> Scott,
>
> I know it defaults to production if a environment is not specified.
> However, that's not the case here. The client
Modules can't currently take parameters (I think you intend to really pass
parameters to a class, not a module, right?); they can however make use of
variables, whether set by an external nodes classifier or in site.pp.
Parameterized classes, however, are coming soon and would do what you
want.
Scott,
I know it defaults to production if a environment is not specified.
However, that's not the case here. The client *is* specifying an
environment, the server doesn't know about that environment. I think
this is different than what you are describing - if the client does
not specify an enviro
Hi,
I just have a question about puppet syntax.
I would like to give a parameter to my ldap module.
In the node definition i would like to specify the domain.
Example :
ldapnode {
include ldap::master::domain("domain.tld")
}
And in the manifest :
define ldap::master::domain() {...}
but i don't
On Mon, Mar 22, 2010 at 11:39 AM, Michael DeHaan
wrote:
>
>
> On Mon, Mar 22, 2010 at 2:01 PM, Arnauld wrote:
>
>> Hi,
>>
>> It may be obvious but I don't understand what the 'ca/ca_*.pem' and
>> the 'certs/ca.pem' files stand for :(
>> It sounds a bit 'redundant' to me
>> Someone has an expl
On 3/22/10 10:27 AM, Paul Lathrop wrote:
IMHO this is a bug, but I can see how it might be by design. Any
comments? Should I file it?
--Paul
Don't know if it's a bug but... Yeah it defaults to "production" - you have to create an empty
manifest for "production" in order to prevent Very Scary
On Mon, Mar 22, 2010 at 2:01 PM, Arnauld wrote:
> Hi,
>
> It may be obvious but I don't understand what the 'ca/ca_*.pem' and
> the 'certs/ca.pem' files stand for :(
> It sounds a bit 'redundant' to me
> Someone has an explanation ?
>
>
Hi Arnauld,
Have you seen
http://projects.reductivelabs
Oh Ok, so what you are looking for is more like a feature to let you know
that the environment "foo" does not exist.
Does not sounds bad to me, if somebody uses tons of environments it will
reduce errors or at least will be easier to find them.
On Mon, Mar 22, 2010 at 11:14 AM, Paul Lathrop wrot
Tony,
Sure, I understand that, but if the client is asking for a specific
environment that the puppetmaster doesn't know about, I feel like that
warrants a warning at minimum, probably an error and a refusal to
compile. Would be interested if anyone has a counter-argument.
--Paul
On Mon, Mar 22,
Hi,
It may be obvious but I don't understand what the 'ca/ca_*.pem' and
the 'certs/ca.pem' files stand for :(
It sounds a bit 'redundant' to me
Someone has an explanation ?
Best regards,
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To
Hi Paul,
How does your config file look like in the main section?
There is a default one if no environment is defined, e.g.
environments = production,testing,development*
manifest = /opt/puppet/production/site.pp <-- These are the
modulepath = /opt/puppet/production/modules <-- default
Over the weekend we noticed an interesting and unexpected behavior
with environments. I made a change to the way our puppet.conf file is
generated and distributed, which led to an environment which had been
defined on a puppetmaster being no longer defined in puppet.conf.
We'll call this the "core"
Hello,
This short notice to inform folks from Switzerland & vicinity that we
will be holding a small puppet booth at OpenExpo, which takes place
in Bern next wednesday an thursday.
If you happen to be around, come and find us at the open-source
village[¹] !
Cheers,
the guys behind spug.ch
[¹] h
I am trying to create set of users from different set of lists in the
following way;
*Secondary Classes*
-
class /*DevelopersManager */#Secondary Class 1
{
*$fileList* = "developerUserlist.txt"
*$group* = "users"
*$home *= "/home"
include StaffManager
}
class /*Admi
Hi .*,
with the first puppet run on a freshly installed system all custom
types and providers a synced. As you can see from the output for some
reason puppet tries to load the providers before the types and
therefore the custom provider loads throw an error. It looks like the
load happens alphabet
39 matches
Mail list logo
