On Feb 24, 5:28 pm, cyrus wrote:
> Hi:
>
> Using augeas, how do you add a comment to the beginning of a file. I
> know you can use ins but you need to specify a path to insert before
> or after. In my case I can't with 100% certainty say I will no what
> the first line.
Hi Cyrus,
I posted some A
On 02/23/2011 10:15 PM, Douglas Garstang wrote:
So... in puppet.conf on the puppet master, there's the external_nodes
setting, which defines the location of the external nodes script. If I
am using multiple environments, I guess I have to have ONE set of
external nodes since external_nodes in p
On 2011-02-25 00:23, Nigel Kersten wrote:
> On Thu, Feb 24, 2011 at 3:05 PM, Thomas Bellman wrote:
>> So if you
>> *do* have different plugins in different environments, and those
>> contain secrets the wrong client must not know, then I believe you
>> *are* screwed, because I don't think there
On 2011-02-25 13:27, Dave Augustus wrote:
> I have added the following in my puppetmaster.conf file:
>
> [production]
> manifest = $vardir/env/production/manifests/site.pp
> modulepath = $vardir/env/production/modules:$vardir/env/common/modules
> [test]
> manifest = $vardir/env/test/m
At the least, can someone be so kind as to tell me the term to search
about -- i've googled a bit, and I think "node override" is what im
after?
On Feb 24, 9:16 am, Jed wrote:
> Hi all,
>
> I think this has been asked in one form or another, but my problem so
> far is i'm not sure of the terminol
For the way you are doing thing, the easiest answer is: use templates. Here
is an example from my sshd_config.erb file that may be of use to you:
- CUT HERE -
pps = cprt_classes.split(',') rescue []
my_login_groups = ['root', 'wheel', 'sysadmin']
my_login_group
On Feb 16, 2:40 pm, Nigel Kersten wrote:
> Where does it say this Phillip? We must have some unclear documentation.
http://docs.puppetlabs.com/guides/configuring.html#configure-dns-optional
It is quite confusing... I struggled for a moment getting a puppet-
master daemon running, too - the confi
You can use regex matches against your nodes' facts, $hostname for
example, to select classes or resources to include. Actually, you can
do this at at least two levels:
At node level:
node /wwwfe/ {
include "base_line"
include "wwwfe"
}
OR
node default {
include "base_line"
}
node /www
Based on 'time out range' seems that you need to do an NTP sync.
-Mark
On Feb 25, 2011, at 10:51 AM, Ace wrote:
> I am trying to connect a solaris puppet client version 2.6.4 to a
> linux puppet master server. I am getting a starnge message as below
> and the puppetca on the master is not able t
I am trying to connect a solaris puppet client version 2.6.4 to a
linux puppet master server. I am getting a starnge message as below
and the puppetca on the master is not able to see the client
certificate.
[root@ /]$ puppetd --test --server
warning: peer certificate won't be verified in thi
On Feb 24, 10:52 am, Tim Dunphy wrote:
> Also I should have mentioned that both services start by hand with an
> exit code of 0 (echo $?)
Do the initscripts depend on any environment variables that they do
not set themselves? When run by Puppet, the scripts will have a much
sparser environment
Time is in sync on both client and master. Both are running NTP.
On Feb 25, 10:53 am, Mark Stanislav wrote:
> Based on 'time out range' seems that you need to do an NTP sync.
>
> -Mark
>
> On Feb 25, 2011, at 10:51 AM, Ace wrote:
>
> > I am trying to connect a solaris puppet client version 2.6.4
On Feb 24, 10:17 am, Tim Dunphy wrote:
> class dbservices {
>
> $pgapps = [ "postgresql84-server","postgresql84" ]
> package { $pgapps: ensure => installed }
>
> $mysqlapps = [ "mysql-server","mysql","php-mysql" ]
> package { $mysqlapps: ensure => installed }
>
> service { postgr
On Feb 24, 10:52 am, Tim Dunphy wrote:
> Also I should have mentioned that both services start by hand with an
> exit code of 0 (echo $?)
Do the dbserver scripts depend on something else environmental, such
as some other service being up? The network service springs to mind
as a possible examp
Hi all
I'm trying to set up a separate puppet master and client on EC2. I've
used two instances of CentOS5.4 with nothing other than the base
install and have installed puppet via the ruby gems. Puppet is at
2.6.4 on both machines.
I've been following the guide to get a basic configuration workin
On Fri, Feb 25, 2011 at 5:10 AM, Thomas Bellman wrote:
> On 2011-02-25 13:27, Dave Augustus wrote:
>
> > I have added the following in my puppetmaster.conf file:
> >
> > [production]
> > manifest = $vardir/env/production/manifests/site.pp
> > modulepath =
> $vardir/env/production/modules:
In my site.pp I have a var set to false
then I include a per_host module, which sets it for some host, to
true, the intent if for this new value to be used * thereafter*
I put I few notice statement in my manifests, and it seems my var that
get start as false, gets set to true in my per-host module
Thanks so much guys, I really really appreciate you taking the time
to respond to my question.
I've been reading quite a bit , but could not really find out how to
do this
I'll give these method a try and report back
Thanks again!
On Feb 25, 10:51 am, jcbollinger wrote:
> You can use re
Maybe the puppet master already has signed a request from your host
(maybe older from an older installation)?
Try on master:
puppet cert --list --all | grep clienthostname
On Fri, Feb 25, 2011 at 08:02:29AM -0800, Ace wrote:
> Time is in sync on both client and master. Both are running NTP.
M
puppet cert --list --all | grep clienthostname
The above command does not list the client host key. I have done a
puppet cert --clean clienthostname in any case.
The timezones on both client and server are the same.
On Feb 25, 3:47 pm, Stefan Schulte
wrote:
> Maybe the puppet master already has
I am running 0.24.8 clients and a 2.5.5 master. When I moved to separate
environments I noticed that the exported resources did not respect
environment boundaries. For example, an exported nagios_host resource that
was exported by a node in the dev environment showed up in the production
nagios con
On Thu, Feb 24, 2011 at 01:57:14PM -0800, mark risher wrote:
> Thanks, but I do have those parameters; I was trying to keep my quote
> short. Here's the full monty:
>
> # create an ssh key for this user
> ssh_authorized_key { "$username.$ssh_public_key":
> ensure => present,
>
On Fri, Feb 25, 2011 at 12:53:22PM -0800, Ace wrote:
> puppet cert --list --all | grep clienthostname
> The above command does not list the client host key. I have done a
> puppet cert --clean clienthostname in any case.
>
> The timezones on both client and server are the same.
>
Does running wi
On Fri, Feb 25, 2011 at 12:58:40PM -0800, Christopher Webber wrote:
> I am running 0.24.8 clients and a 2.5.5 master. When I moved to separate
> environments I noticed that the exported resources did not respect
> environment boundaries. For example, an exported nagios_host resource that
> was expo
Yeah, that's probably not going to get you where you need to be.
Scope in Puppet goes like this:
* When you declare a variable in a scope, it is local to that scope.
* Every scope has one and only one "parent scope."
* If it's a class or node that inherits from a base class/node,
its parent s
Hello list!!
Your help is invaluable and genuinely appreciated!! Here is the
manifest as things stand now:
class dbservices {
class postgres {
$pgapps = ["postgresql84-server","postgresql84"]
package { $pgapps: ensure => installed }
user { "postgres:":
uid => 26,
Running in the --no-daemonize mode for both client and master does not
show anything interesting.
Whats interesting is that I can have linux puppet clients connect to
the linux master but none of the solaris clients work. More
interesting is that I can connect to the Solaris master with the
solari
On Wed, Feb 23, 2011 at 2:04 PM, Nick Lewis wrote:
> Our current plan for the inventory service is to provide active_record
> termini for the "facts" and "inventory" indirections. This is to support
> fast look-up of facts, and search of nodes based on their facts. However,
> there are already tab
On Feb 25, 3:34 pm, Tim Dunphy wrote:
> class mysql {
>
> $mysqlapps = ["mysql-server","mysql","php-mysql"]
> package { $mysqlapps: ensure => installed }
> user { "mysql":
> uid => 27,
> ensure => present
> }
> group { "mysql":
> gid => 27,
>
Thanks a lot Nick for the detailed response. Not sure I fully
understand yet. I dont think I can use option one because the external
classifier would does not have access to the clients facts. I will
read about parametrized classes and learn to use them, though I dont
yet see how they can solve my
Firstly, forgive me if I get my terminology mixed up. Being sold on
the virtues of TDD, I have a growing itch to test our puppet
manifests. Now by this I dont mean testing, say, the mechanics of a
define to test that the right things *happen*, I mean being able to
say that given a collection of cla
Operations Engineer
WeatherBill, Inc
San Francisco, CA
WeatherBill is a successful start-up in the heart of San Francisco
with an open and flat-structured environment that is revolutionizing
how the world deals with weather risk and peril through sophisticated
parametric modeling that can be used
Currently puppet supports regex matching on node names
also puppet looks if a node is named default and applies this manifest
but there is also an "inherit" where nodes can inherit another one (but
only one!) so it might help to split your manifests up to different
nodes and inherit them either to
On Fri, Feb 25, 2011 at 9:24 AM, Darren Worrall wrote:
> Firstly, forgive me if I get my terminology mixed up. Being sold on
> the virtues of TDD, I have a growing itch to test our puppet
> manifests. Now by this I dont mean testing, say, the mechanics of a
> define to test that the right things *
On Fri, Feb 25, 2011 at 3:25 PM, Mohamed Lrhazi wrote:
> Thanks a lot Nick for the detailed response. Not sure I fully
> understand yet. I dont think I can use option one because the external
> classifier would does not have access to the clients facts. I will
> read about parametrized classes and
35 matches
Mail list logo
