On Mon, Sep 22, 2008 at 8:52 PM, Blake Barnett <[EMAIL PROTECTED]> wrote:
>
> I'd also recommend using a .gemrc file (managed by puppet!) to add "--
> no-rdoc --no-ri" since it's usually what everyone wants as the
> default, especially in production.
>
> -Blake
>
> On Sep 22, 2008, at 1:46 PM, Ash
Can anyone give me a hint about how to use puppet to parse the configuration
of a host (e.g. auto load all needed manifest files using puppet internals
using external node, inheritance order etc ).
After this part is done, it should be rather easy to parse all of the files
and generate some html c
Hi,
I'm interested, I've already done some basic work on the puppet side.
In our setup we decided not to use storeconfig (due to technical limitations
of having too many puppet masters in different locations), therefor, we have
re implemented many of facts importing and collecting.
I would assume
I'd also recommend using a .gemrc file (managed by puppet!) to add "--
no-rdoc --no-ri" since it's usually what everyone wants as the
default, especially in production.
-Blake
On Sep 22, 2008, at 1:46 PM, Ashley Penney wrote:
>
> You could just do exec { "gem-install-mysql": command => "gem
On Sep 22, 2008, at 5:45 AM, [EMAIL PROTECTED] wrote:
>
> Hi Guys,
>
> Does anyone know of, or are there any plans for, a documentation
> parser/generator for puppet, akin to pydoc or javadoc?
>
> In my opinion, one of the unsung advantages of managing systems via
> puppet is that you get a fo
You could just do exec { "gem-install-mysql": command => "gem install
mysql --no-rdoc --no-ri -- --with-mysql-config=/usr/bin/mysql_config",
}
Then you can rely on require => Exec["gem-install-mysql"] elsewhere.
On Mon, Sep 22, 2008 at 2:15 PM, Ed Greenberg <[EMAIL PROTECTED]> wrote:
>
> I need
On 9/22/2008 2:30 PM, Brian Gupta wrote:
> Anyone have any recipes for this? Also logrotate bits would help.
I just leave logrotate on the defaults. But for syslog-ng (edited down
to the relevant bits):
> node "syslog.cae.tntech.edu" {
> include baseclass
> $syslogtype = 'server'
>
On Mon, Sep 22, 2008 at 12:25 PM, Digant C Kasundra <[EMAIL PROTECTED]> wrote:
>
> Hello Puppet users,
>
> I was curious if anyone else works at an institution that uses Remedy,
> particularly as a CMDB infrastructure. We're planning to do that and so I've
> been tasked with writing integration
Look for an external node classification tool like iClassify.
iClassify let's you store all the puppet variables and class
assignments for individual nodes in a central database.
On Mon, Sep 22, 2008 at 3:26 PM, Subhasis Dasgupta
<[EMAIL PROTECTED]> wrote:
> Hi,
> I apologize for my previous pos
Hi,
I am using puppet for maintaining a number of node configuration management
. I want to change my configuration from outside the puppet . so what will
be the best possible solution for them ? Storeconfig or LDAP ?
Thank you very much ,
--
Subhasis Dasgupta
www.kaavo.com
Phone : +919830282
Hi,
I apologize for my previous posting , because it may not be very much clear
about the problem. My problem is , from outside of the puppet I want to
modify / update my puppet node configuration . Conventional, storing of
node details in a file is not an ideal solution for me because I want t
Anyone have any recipes for this? Also logrotate bits would help.
--
- Brian Gupta
--~--~-~--~~~---~--~~
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@googlegroup
I need to do this in puppet:
gem install mysql --no-rdoc --no-ri -- --with-mysql-config=/usr/bin/
mysql_config
Not sure how to express any of the arguments to gem install in my
puppet Package stanza.
can somebody explain?,
--~--~-~--~~~---~--~~
You received t
Hi,
somehow I am stuck with my variable interpolation.
I have a few nodes in our LDAP. Among the attributes for some nodes
is the attribute 'puppetbinpatch'. Each node can have n attributes of
this type to list the patches that should be applied on a node.
my class looks like this:
class binpat
Hello Puppet users,
I was curious if anyone else works at an institution that uses Remedy,
particularly as a CMDB infrastructure. We're planning to do that and so I've
been tasked with writing integration tools so that Puppet can feed data of
interest up into that system. If anyone is intere
When things are fairly small, it isn't an issue and certainly documentation is
key. I'm just very OCD about conventions and naming and I like having things
named in ways that it is explicit to the purpose. Generally, it is fairly easy
to tell that ssh::files would most likely be a class that
On Mon, Sep 22, 2008 at 10:40 AM, Aj <[EMAIL PROTECTED]> wrote:
>
> You'll want to have one inherit the parent (named) and use the overide
> syntax on the resources.
>
> class named::hpc inherits named {
> Service['named'] { enabled => false }
> }
>
I am actually needing to call the service for
On Mon, Sep 22, 2008 at 10:25 AM, Chad Huneycutt
<[EMAIL PROTECTED]> wrote:
>
> Are you actually including both "named" and "hpc::named" on a single
> host? If not, then there will not be a conflict.
>
> - Chad
Yup, that is why I am surprised there is not a conflict. I think I
have actually found
Hey Mark,
I was thinking somehow puppet automatically created the error tag when there
we errors in the output stream. I guess that the book is a little out of
Date then. Well if you don't get a chance to fix it maybe I will try my hand
at a little more advance Ruby in a few weeks, for now I thin
You'll want to have one inherit the parent (named) and use the overide
syntax on the resources.
class named::hpc inherits named {
Service['named'] { enabled => false }
}
Regards,
Aj
On 23/09/2008, at 3:25 AM, "Chad Huneycutt" <[EMAIL PROTECTED]>
wrote:
>
> Are you actually including bo
Are you actually including both "named" and "hpc::named" on a single
host? If not, then there will not be a conflict.
- Chad
On Wed, Sep 17, 2008 at 12:41 PM, Evan Hisey <[EMAIL PROTECTED]> wrote:
>
> As understand puppet I should not be able to have two service[named]
> entries in the same com
Hi
> $ puppetmasterd --verbose
> info: Starting server for Puppet version 0.20.1
> Syntax error at 'user::virtual' in
> file /etc/puppet/modules/user/itstaff.pp at line 3
your version iy heavily outdated. you might use the sid one. it's more
actual and stable enough.
greets pete
--~--~
Hi Guys,
Does anyone know of, or are there any plans for, a documentation
parser/generator for puppet, akin to pydoc or javadoc?
In my opinion, one of the unsung advantages of managing systems via puppet
is that you get a formal definition of your systems state which is only a
hair-width away
23 matches
Mail list logo
