[Puppet Users] Re: Controlling the frequency of different tasks.

[Greg]

Just note that if you want stuff running every 5 minutes, use cron -
running Puppet every 5 minutes is generally not practical.

Greg

On Sep 15, 10:38 am, Tim Uckun  wrote:
> > Are you perhaps looking for the "schedule" meta-parameter:
> >http://reductivelabs.com/trac/puppet/wiki/TypeReference#available-met...
>
> Yea!. Thanks.
--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: A couple of persistent errors I can't seem to get rid of.

[Tim Uckun]

> I've seen the same; I saw somewhere (but can't find again) comments from the 
> puppet devs that if you don't have plugins
> to sync, you should turn of pluginsync otherwise you'll get this error 
> message.  The fix would be so convoluted as to be
> ridiculous.  Or something like that.  Damn, wish I could find that web 
> page.


I did put a plug in from one of the sample repositories in but it
didn't seem to cure the problem Perhaps the plugin format has changed
or something. I'll try to write up a simple one and see if I can make
it shut up.

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: commonly used, defacto standard web frontend to facter ... that everyone loves?

[Tim Uckun]

>
> which kind of graphs? something like how many servers are X or Y etc?

Things like memory usage, free disk space etc. Actually since zabbix
can be configured to accept, graph, and alert on just about anything
you can do things like number of postgres connections, the size of a
table, the size of a particular file, the number of hits to a page
etc.

One nice feature it has is that you can alert if it doesn't get a
value it's expecting in a particular time frame.

>
> I'm just implementing now the reports collector, It would be very easy to
> send out an alert based on various criteria e.g.:
> - something failed in the puppet run
> - took too long
> - no report
> etc

Yea.  Also things like "running out of disk space", process X taking
up more than Y amount of ram, "I haven't gotten a report from host X
in two hours" etc.

>
> Thanks, My main goal is to make Foreman the main place you want to go each
> time you want something related to your puppet managed servers.

Good luck.

>
> Thanks for the feedback,
> Ohads

Any time.

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: A couple of persistent errors I can't seem to get rid of.

[Craig Miskell]

Tim Uckun wrote:
> The puppetmaster reports the following error.
> 
> err: Report store failed: Invalid group puppet on setting . Valid
> groups are service.
> 
> What is it trying to tell me? I have the following set.
> 
> storeconfigs=true
> dbadapter = sqlite3
> dblocation = /var/puppet/storeconfigs.sqlite
> tagmap=/etc/puppet/tagmail.conf
> reports = tagmail,store,log
>
Seems to be a bug in 0.25.  I've reported it as issue 2639, and I have a fix 
that works for me but is apparently wrong. 
  Will have to see what the devs say.

> Also I am having problems with the plugins errors.
> 
> err: /File[/var/lib/puppet/lib]: Failed to retrieve current state of
> resource: Could not retrieve information from source
> 
> As long as pluginsync=true is set I get this error. I have tried
> various things like setting this in the fileserver.conf
> 
> [plugins]
>  path /etc/puppet/plugins
>  allow *
> 
> And such but nothing seems to be working.

I've seen the same; I saw somewhere (but can't find again) comments from the 
puppet devs that if you don't have plugins 
to sync, you should turn of pluginsync otherwise you'll get this error message. 
 The fix would be so convoluted as to be 
ridiculous.  Or something like that.  Damn, wish I could find that web page.

Craig

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: commonly used, defacto standard web frontend to facter ... that everyone loves?

[Ohad Levy]

On 9/15/09, Tim Uckun  wrote:
>
>
> >
> > What do you mean by over WAN? for facts? reports or both?
>
>
> Neither I think. I mean kick start a machine outside of the local LAN.
>   I have numerous data centers in different countries. My puppermaster
> is sitting in one country, I want to kick off a new server in another
> country. Both are behind firewalls but of course I have the puppet
> ports forwarding.


I've done this successfully with around 2000 installations.
the only thing you need to consider is where is your installation source
located, obviously Foreman just provide your kickstart / preseed  /
jumpstart files which point to the real location of the installation media.


I described in another email a process I intend to set up to send
> facts over to a zabbix server. We use zabbix for monitoring and if I
> could send facts to it I can not only graph them but base alerts off
> of them.


which kind of graphs? something like how many servers are X or Y etc?

One thing you may want to consider for the future is the ability to
> manipulate the RRD files puppets puts out and to be able create alerts
> based on them.

I'm just implementing now the reports collector, It would be very easy to
send out an alert based on various criteria e.g.:
- something failed in the puppet run
- took too long
- no report
etc


It seems like between puppet and foreman you already have about 50% of
> zabbix does with some nice additional feature.


Thanks, My main goal is to make Foreman the main place you want to go each
time you want something related to your puppet managed servers.

Thanks for the feedback,
Ohads

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: commonly used, defacto standard web frontend to facter ... that everyone loves?

[Tim Uckun]

>
> What do you mean by over WAN? for facts? reports or both?

Neither I think. I mean kick start a machine outside of the local LAN.
 I have numerous data centers in different countries. My puppermaster
is sitting in one country, I want to kick off a new server in another
country. Both are behind firewalls but of course I have the puppet
ports forwarding.

To be honest I really haven't spend any time with the foreman docs to
know if it's a suitable project or not. I thought I'd try and see what
it did.

> I've created - http://theforeman.org/issues/show/10
>

I described in another email a process I intend to set up to send
facts over to a zabbix server. We use zabbix for monitoring and if I
could send facts to it I can not only graph them but base alerts off
of them.

One thing you may want to consider for the future is the ability to
manipulate the RRD files puppets puts out and to be able create alerts
based on them.

It seems like between puppet and foreman you already have about 50% of
zabbix does with some nice additional feature.

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Question on proper use of virtual resources

[Jon Stanley]

I'm attempting to use virtual resources to get around multiple
definition errors, but it doesn't seem to be working.  I need to
create a directory structure like "/apps/siteA/instance_1/resin" and
"/apps/siteA/instance_2/resin". In reality it's a little more complex,
because there are multiple sites running on a given node.  Anyhow,
here's how I've defined it:

define resin::instance(
   $site_alias,
   $env_alias,
   $instance,
   $host_alias,
   $resin_ver,
   $java_ver
) {
   include resin::base
   @file { "/apps/runtime/$site_alias":
  owner => cnp,
  group => cnp-admin,
  mode => 0755,
  require => File["/apps/runtime"],
  ensure => directory;
   "/apps/runtime/$site_alias/$env_alias":
  owner => cnp,
  group => cnp-admin,
  mode => 0755,
  require => File["/apps/runtime/$site_alias"],
  ensure => directory;
   
"/apps/runtime/$site_alias/$env_alias/resin/${host_alias}_${env_alias}_${instance}":
  owner => cnp,
  group => cnp-admin,
  mode => 0755,
  require => File["/apps/runtime/$site_alias/$env_alias"],
  ensure => directory;
   }
   realize File["/apps/runtime/$site_alias"]
   realize File["/apps/runtime/$site_alias/$env_alias"]
   realize 
File["/apps/runtime/$site_alias/$env_alias/resin/${host_alias}_${env_alias}_${instance}"]

}

I was thinking that using the virtual resource in the definition would
get around the errors, but it doesn't seem to have:

err: Could not retrieve catalog: Puppet::Parser::AST::Resource failed
with error ArgumentError: Duplicate definition: File[/apps/runtime/gq]
is already defined in file
/var/lib/puppet/git/modules/resin/manifests/init.pp at line 40; cannot
redefine at /var/lib/puppet/git/modules/resin/manifests/init.pp:40 on
node s602250nj3el563.uspswy6.savvis.net

What's another approach to doing this?  The end goal is having one
simple call to define an instance, not mattering if the site is known
or unknown (so a bunch of classes to include wouldn't be scalable
here), or if it's on that machine or not - i.e. from one simple
resin::instance call, I should be able to have a functional instance.

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] A couple of persistent errors I can't seem to get rid of.

[Tim Uckun]

The puppetmaster reports the following error.

err: Report store failed: Invalid group puppet on setting . Valid
groups are service.

What is it trying to tell me? I have the following set.

storeconfigs=true
dbadapter = sqlite3
dblocation = /var/puppet/storeconfigs.sqlite
tagmap=/etc/puppet/tagmail.conf
reports = tagmail,store,log


Also I am having problems with the plugins errors.

err: /File[/var/lib/puppet/lib]: Failed to retrieve current state of
resource: Could not retrieve information from source

As long as pluginsync=true is set I get this error. I have tried
various things like setting this in the fileserver.conf

[plugins]
 path /etc/puppet/plugins
 allow *

And such but nothing seems to be working.

Just before this fires I get the following debug messages

debug: Using cached certificate_revocation_list for ca
debug: Puppet::Network::Format[json]: false value when expecting true
debug: Format s not supported for Puppet::FileServing::Metadata; has
not implemented method 'from_s'
debug: Puppet::Network::Format[json]: false value when expecting true
debug: Format s not supported for Puppet::FileServing::Metadata; has
not implemented method 'from_s'

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: commonly used, defacto standard web frontend to facter ... that everyone loves?

[Ohad Levy]

On 9/15/09, Tim Uckun  wrote:
>
>
> I installed foremen yesterday and it was ridiculously easy to set up.
> I haven't figured out how to make it work over  WAN or even if it can
> yet but as a front end to facter it seems pretty cool.


Thanks for the feedback, nice to know :)

What do you mean by over WAN? for facts? reports or both?
in the stable version you can specify a different directory where you could
import your facts from, however, I'm planing to write in the next few days a
simple fact importer that post the data to foreman web interface.
(more or less the same like how puppet reports are imported to Foreman).

I've created - http://theforeman.org/issues/show/10

Cheers,
Ohad

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: commonly used, defacto standard web frontend to facter ... that everyone loves?

[Ohad Levy]

On 9/15/09, Richard Wurman  wrote:
>
>
> I'm new to puppet in general - I just have a minimal node.pp defined
> for 2 clients so far. Before I reinvent the wheel ... is there a good
> web UI to facter that everyone uses? I've looked over foreman and I
> figure since it's new, it's probably not in widespread use currently.


Which features did you miss? I'll be happy for any feedback.

Ohad

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Puppet status reporting

[Ohad Levy]

Yes.

Ohad

On 9/15/09, Silviu Paragina  wrote:
>
>
> Is this the before called GNI?
>
>
>
> Silviu
>
>
> Ohad Levy wrote:
> > Hi,
> >
> > For future references, the primary website can be found at
> > http://theforeman.org
> >
> > Cheers,
> > Ohad
> >
> > On Mon, Sep 14, 2009 at 6:48 AM, James Turnbull
>
> > mailto:ja...@lovedthanlost.net>> wrote:
> >
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Craig Miskell wrote:
> > > Hi,
> > >   I'd like to have some sort of "status report" GUI for my
> > puppet installation.  Specifically, I would like to see
> > > a) Any nodes that haven't reported in for a while
> > > b) Any recent instances of having to make unexpected changes
> > (restart a stopped service, resetting some important file
> > > permissions but not because the policy changed, etc)
> > > c) Any failures to set policy on a client.
> > > d) Summary green light for the rest.
> >
> > Have a look at:
> >
> > http://github.com/ohadlevy/foreman
> >
> > And the Reductive Labs can probably jump in with whatever they are
> > working on.
> >
> > Cheers
> >
> > James Turnbull
> >
> > - --
> > Author of:
> > * Pro Linux Systems Administration (http://tinyurl.com/linuxadmin)
> > * Pulling Strings with Puppet (http://tinyurl.com/pupbook)
> > * Pro Nagios 2.0 (http://tinyurl.com/pronagios)
> > * Hardening Linux (http://tinyurl.com/hardeninglinux)
> > -BEGIN PGP SIGNATURE-
> > Version: GnuPG v1.4.7 (Darwin)
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> >
> > iQEVAwUBSq12oSFa/lDkFHAyAQJ2vAgA3Tp9eLsqHYyWx0aGrCZS4JYEt6qoXf97
> > KY4bAF5A7rd8pTeUsZgVPZZ6JszsS/2YHiLzYoM78NXqWEucwvj/jEUw653C/s/g
> > +OsikXaMGZ/Xj3FvgGAsFHnapcqe6zQykI4Bn8Vik9UzpCpC+O2rIS2gaZ+AU+X3
> > ASmRV9T8ZuQ8vQ/6jnL/1+LTCDgeprZvMr8wnX/vDYxoGDYaSOeW2nyJQJz51Km8
> > 0gIV3hlBjyYa5dQ3AJdXEysSVoqSdIshTBAHhAiew83nZVn7itcfGxYpIhiRTKKD
> > L1X48ZCSFd2Vr0YU2TdK5xbkUsLUsttxyOVQyfGItaF/YBufu0b04A==
> > =HC8Z
> > -END PGP SIGNATURE-
> >
> >
> >
> >
> > >
>
>
> >
>

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Controlling the frequency of different tasks.

[Tim Uckun]

> Are you perhaps looking for the "schedule" meta-parameter:
> http://reductivelabs.com/trac/puppet/wiki/TypeReference#available-metaparameters


Yea!. Thanks.

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Controlling the frequency of different tasks.

[Craig Miskell]

-- 
Craig Miskell
Senior Systems Administrator
Opus International Consultants
"People say I'm apathetic but I don't care"

Tim Uckun wrote:
> I know that the puppet client runs the entire catalog at the frequency
> you decide but...
> 
> I do think it would be nice to be able a little more fine grained
> approach to this. For example I might want to ensure that my package
> => latest is only run once a day or that some other task is run every
> five minutes.
Are you perhaps looking for the "schedule" meta-parameter:
http://reductivelabs.com/trac/puppet/wiki/TypeReference#available-metaparameters

Craig Miskell

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Controlling the frequency of different tasks.

[Tim Uckun]

I know that the puppet client runs the entire catalog at the frequency
you decide but...

I do think it would be nice to be able a little more fine grained
approach to this. For example I might want to ensure that my package
=> latest is only run once a day or that some other task is run every
five minutes.

Just a thought.

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: commonly used, defacto standard web frontend to facter ... that everyone loves?

[Tim Uckun]

On Tue, Sep 15, 2009 at 5:37 AM, Richard Wurman
 wrote:
>
> I'm new to puppet in general - I just have a minimal node.pp defined
> for 2 clients so far. Before I reinvent the wheel ... is there a good
> web UI to facter that everyone uses? I've looked over foreman and I
> figure since it's new, it's probably not in widespread use currently.
> Any suggestions?
>


I installed foremen yesterday and it was ridiculously easy to set up.
I haven't figured out how to make it work over  WAN or even if it can
yet but as a front end to facter it seems pretty cool.

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Configuration parse testing

[Tim Uckun]

> Be great if these other suggestions made it onto the wiki too.
>

Done.

http://reductivelabs.com/trac/puppet/wiki/Recipes/SubversionCommitHooks

I am not the most eloquent person in the world so feel free to modify
it as you wish.

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: snmpd v3 class help - need to stop service before copying file and then restart

[Silviu Paragina]

An odd workaround

Use a secondary file and an exec. Afaik if an exec isn't executed, the 
resources which depend on the exec aren't applied.
So...

class snmpd {

package { net-snmp: ensure => installed }

file { "/etc/snmp/snmpd.bogous.conf":
owner   => root,
group   => root,
mode=> 0644,
source  => "puppet:///snmpd/snmp.conf",
require => Package[net-snmp],
}
   
exec { "stop-snmpd":
refreshonly => true,
command=> "invoke-rc.d snmpd stop", #or change to 
/etc/init.d/snmpd stop or whatever
require=> File["etc/snmp/snmpd.bogous.conf"],
subscribe   => File["etc/snmp/snmpd.bogous.conf"],
}

file { "/etc/snmp/snmpd.conf":
owner   => root,
group   => root,
mode=> 0644,
source  => "puppet:///snmpd/snmp.conf",
require => [Package[net-snmp],Exec["stop-snmpd"]],
notify  => Service[snmpd],
}

file { "/var/net-snmp/snmpd.conf":
owner   => root,
group   => root,
mode=> 0600,
source  => "puppet:///snmpd/net-snmpd.conf",
require => [Package[net-snmp],File["/etc/snmp/snmpd.conf"]],
notify  => Service[snmpd],
}

service { snmpd:
enable  => true,
hasrestart => true,
ensure  => running,
require => Package[$autofs_packages],
}

try this with a puppet --test and see what happens
I know this is an ugly workaround :">


Silviu


Mark Christian wrote:
> The problem I have is that I need to ensure that snmpd is stopped
> before attempting to copy /var/net-snmp/snmpd.conf (snmpd credentials
> file that gets corrupted if copied while snmpd is running).  Any
> suggestions on how best to proceed?
>
>
> # what I have so far.
> class snmpd {
>
> package { net-snmp: ensure => installed }
>
> file { "/etc/snmp/snmpd.conf":
> owner   => root,
> group   => root,
> mode=> 0644,
> source  => "puppet:///snmpd/snmp.conf",
> require => Package[net-snmp],
> notify  => Service[snmpd],
> }
>
> file { "/var/net-snmp/snmpd.conf":
> owner   => root,
> group   => root,
> mode=> 0600,
> source  => "puppet:///snmpd/net-snmpd.conf",
> require => Package[net-snmp],
> notify  => Service[snmpd],
> }
>
> service { snmpd:
> enable  => true,
> hasrestart => true,
> ensure  => running,
> require => Package[$autofs_packages],
> }
>
> Thank you.
>
> Mark
> >
>   


--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: What does puppetrun do?

[Silviu Paragina]

Never forget (this might be the case) that if the new manifests don't 
compile the old ones are sometimes sent. I always scratch my head 
because of that.


Silviu

grandpa wrote:
> I think I might have misunderstood what puppetrun does.
>
> I've interpreted it as puppetrun triggers a remote run of puppet AND
> that the remote puppet fetches the latest manifests and applies them.
>
> This is not what seems to happen though. As far as I can tell,
> puppetrun
> just triggers the remote puppet to apply the manifests it has but not
> asking
> the server if there are any changes.
>
> Can I get puppetrun to trigger a remote run of puppet with the same
> result as
> logging in to the remote host and running puppetd --test ?
>
>
> /John
> >
>   


--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Puppet status reporting

[Silviu Paragina]

Is this the before called GNI?


Silviu

Ohad Levy wrote:
> Hi,
>
> For future references, the primary website can be found at 
> http://theforeman.org
>
> Cheers,
> Ohad
>
> On Mon, Sep 14, 2009 at 6:48 AM, James Turnbull 
> mailto:ja...@lovedthanlost.net>> wrote:
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Craig Miskell wrote:
> > Hi,
> >   I'd like to have some sort of "status report" GUI for my
> puppet installation.  Specifically, I would like to see
> > a) Any nodes that haven't reported in for a while
> > b) Any recent instances of having to make unexpected changes
> (restart a stopped service, resetting some important file
> > permissions but not because the policy changed, etc)
> > c) Any failures to set policy on a client.
> > d) Summary green light for the rest.
>
> Have a look at:
>
> http://github.com/ohadlevy/foreman
>
> And the Reductive Labs can probably jump in with whatever they are
> working on.
>
> Cheers
>
> James Turnbull
>
> - --
> Author of:
> * Pro Linux Systems Administration (http://tinyurl.com/linuxadmin)
> * Pulling Strings with Puppet (http://tinyurl.com/pupbook)
> * Pro Nagios 2.0 (http://tinyurl.com/pronagios)
> * Hardening Linux (http://tinyurl.com/hardeninglinux)
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.7 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEVAwUBSq12oSFa/lDkFHAyAQJ2vAgA3Tp9eLsqHYyWx0aGrCZS4JYEt6qoXf97
> KY4bAF5A7rd8pTeUsZgVPZZ6JszsS/2YHiLzYoM78NXqWEucwvj/jEUw653C/s/g
> +OsikXaMGZ/Xj3FvgGAsFHnapcqe6zQykI4Bn8Vik9UzpCpC+O2rIS2gaZ+AU+X3
> ASmRV9T8ZuQ8vQ/6jnL/1+LTCDgeprZvMr8wnX/vDYxoGDYaSOeW2nyJQJz51Km8
> 0gIV3hlBjyYa5dQ3AJdXEysSVoqSdIshTBAHhAiew83nZVn7itcfGxYpIhiRTKKD
> L1X48ZCSFd2Vr0YU2TdK5xbkUsLUsttxyOVQyfGItaF/YBufu0b04A==
> =HC8Z
> -END PGP SIGNATURE-
>
>
>
>
> >


--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: troubleshooting puppet on Ubuntu

[Silviu Paragina]

The warrning is beacause xmlsimple was moved (this is a guess), and for 
backward compatibility it was left there like
require File.dirname(__FILE__) + '/../xmlsimple.rb'

I'm guessing that puppet uses both require 'xmlsimple.rb' and require 
'lib/xmlsimple.rb'. Long story short because of the '..' in the above 
file, it seems that the file gets included twice.

The easy workardound is to replace the above with

> require 'xmlsimple.rb'
This made things right for me (Ubuntu 9.04), but I'm not sure if it can 
break other ruby software (I only use puppet).


Silviu

Julien Garet wrote:
> Le 12 sept. 09 à 12:58, Bogdan Bivolaru a écrit :
>
>   
>> Hello,
>> 
>
> Hello,
>
>   
>> I'm trying to follow the guide at 
>> http://reductivelabs.com/trac/puppet/wiki/SimplestPuppetInstallRecipe
>> , but I get a funny error when starting Puppetd:
>> Server:
>> sudo puppetmasterd --verbose
>> /usr/lib/ruby/1.8/xmlsimple.rb:275: warning: already initialized
>> constant KNOWN_OPTIONS
>> /usr/lib/ruby/1.8/xmlsimple.rb:280: warning: already initialized
>> constant DEF_KEY_ATTRIBUTES
>> /usr/lib/ruby/1.8/xmlsimple.rb:281: warning: already initialized
>> constant DEF_ROOT_NAME
>> /usr/lib/ruby/1.8/xmlsimple.rb:282: warning: already initialized
>> constant DEF_CONTENT_KEY
>> /usr/lib/ruby/1.8/xmlsimple.rb:283: warning: already initialized
>> constant DEF_XML_DECLARATION
>> /usr/lib/ruby/1.8/xmlsimple.rb:284: warning: already initialized
>> constant DEF_ANONYMOUS_TAG
>> /usr/lib/ruby/1.8/xmlsimple.rb:285: warning: already initialized
>> constant DEF_FORCE_ARRAY
>> /usr/lib/ruby/1.8/xmlsimple.rb:286: warning: already initialized
>> constant DEF_INDENTATION
>> /usr/lib/ruby/1.8/xmlsimple.rb:287: warning: already initialized
>> constant DEF_KEY_TO_SYMBOL
>>
>> Client:
>> b...@server:~$ sudo puppetd --verbose
>> [sudo] password for biv:
>> /usr/lib/ruby/1.8/xmlsimple.rb:275: warning: already initialized
>> constant KNOWN_OPTIONS
>> [ same warnings as on the server ]
>> /usr/lib/ruby/1.8/xmlsimple.rb:287: warning: already initialized
>> constant DEF_KEY_TO_SYMBOL
>> err: Could not create PID file: /var/run/puppet/puppetd.pid
>>
>> Back on the server I run "sudo puppetca --list", I get the same
>> warnings complaining about xmlsimple.rb,  and it tells me there are
>> "No certificates to sign". When I run the client on the same machine
>> as the server, I still get "Could not create PID". I restarted the
>> server machine, but it doesn't seem to help either.
>>
>> My guess is that there is something wrong with the client - do I need
>> to configure anything else? I'm a bit lost from here.
>>
>> I'm using Ubuntu 9.04 Jaunty on all my machines and I installed
>> puppetmaster and puppet from the repositories.
>> 
>
>
> Actually, you've hit a bug in ubuntu on libxml-simple-ruby 
> https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/296605 
> , the way to solve this problem is either :
> - download the karmic package and install it
> - wait for karmic
>
> Cheers,
>
> Julien
>
>
>   
>
>
> >
>   


--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Installing a lot of packages

[Jeff Adams]

We're a Debian shop, with our own internal repository for controlling 
packages. We use the unattended-upgrades package to perform upgrades and 
use puppet to instantiate the whole process using a variant of the 
recipe at the bottom of this page:

http://reductivelabs.com/trac/puppet/wiki/Recipes/Debian

- Jeff

On 09/14/2009 03:12 PM, ELTigre wrote:
>
> On Sep 14, 1:56 pm, Peter Meier  wrote:
>> Hi
>>
>>> I'd like to know at what level we can use puppet  to keep systems
>>> up2date. I appreciate if you share some experiences.
>>> :-)
>>
> Hi Pete,
> Thanks for your soon answer,  We've always updated packages of
> principal services  manually and other packages not so important
> automatically using some cron jobs. BUT, puppet comes to play and we
> have a lot of servers running in production environment. That's the
> reason why I'm asking the list. The updating process is complicated
> because you have to manually do the dirty job. We thought puppet can
> handle this servers's update job. But I see it's not a good idea.
>
> Does anyone in the list use puppet to handle updates on servers? :-)
>
> regards,
> Israel.
>> we don't use puppet at all to keep systems up2date and I don't think
>> it's a good idea either. Your package manager usually does a much better
>>   job. To manage bigger installations something like satellite or even an
>> own managed package repository, which you sync with the upstream updates
>> you need and then run a cron only against that repository might be a
>> suitable solution.
>>
>> cheers pete
> >

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Puppet / EC2 noob question

[dmangot]

On Sep 11, 5:07 am, Chris  wrote:
> Hi all,
>
> I'm starting to use EC2, and I'm after some examples of best practices/
> tips and tricks from folk with more experience of the Puppet/EC2 combo
> than me:
>
> We're starting by using EC2 for testing and development purposes. This
> means that we won't be running our instances full-time; rather, we'll
> be spinning them up and down for a few hours at a time, as and when
> needed. I'd like the instances to call back to my local puppetmaster
> to configure themselves post-boot.

Chris,

   I did exactly this.   Check out my blog post:

http://tech.mangot.com/roller/dave/entry/on_running_terracotta_on_ec2

   Works great.

 Cheers,

   -Dave





--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Installing a lot of packages

[Nigel Kersten]

On Mon, Sep 14, 2009 at 1:12 PM, ELTigre  wrote:

>
> On Sep 14, 1:56 pm, Peter Meier  wrote:
> > Hi
> >
> > > I'd like to know at what level we can use puppet  to keep systems
> > > up2date. I appreciate if you share some experiences.
> > > :-)
> >
> Hi Pete,
> Thanks for your soon answer,  We've always updated packages of
> principal services  manually and other packages not so important
> automatically using some cron jobs. BUT, puppet comes to play and we
> have a lot of servers running in production environment. That's the
> reason why I'm asking the list. The updating process is complicated
> because you have to manually do the dirty job. We thought puppet can
> handle this servers's update job. But I see it's not a good idea.
>
> Does anyone in the list use puppet to handle updates on servers? :-)
>

We have execs of apt-get update/upgrade that we run as part of our Puppet
runs.




>
> regards,
> Israel.
> > we don't use puppet at all to keep systems up2date and I don't think
> > it's a good idea either. Your package manager usually does a much better
> >  job. To manage bigger installations something like satellite or even an
> > own managed package repository, which you sync with the upstream updates
> > you need and then run a cron only against that repository might be a
> > suitable solution.
> >
> > cheers pete
> >
>


-- 
Nigel Kersten
nig...@google.com
System Administrator
Google Inc.

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Installing a lot of packages

[ELTigre]

On Sep 14, 1:56 pm, Peter Meier  wrote:
> Hi
>
> > I'd like to know at what level we can use puppet  to keep systems
> > up2date. I appreciate if you share some experiences.
> > :-)
>
Hi Pete,
Thanks for your soon answer,  We've always updated packages of
principal services  manually and other packages not so important
automatically using some cron jobs. BUT, puppet comes to play and we
have a lot of servers running in production environment. That's the
reason why I'm asking the list. The updating process is complicated
because you have to manually do the dirty job. We thought puppet can
handle this servers's update job. But I see it's not a good idea.

Does anyone in the list use puppet to handle updates on servers? :-)

regards,
Israel.
> we don't use puppet at all to keep systems up2date and I don't think
> it's a good idea either. Your package manager usually does a much better
>  job. To manage bigger installations something like satellite or even an
> own managed package repository, which you sync with the upstream updates
> you need and then run a cron only against that repository might be a
> suitable solution.
>
> cheers pete
--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Installing a lot of packages

[Peter Meier]

Hi

> I'd like to know at what level we can use puppet  to keep systems
> up2date. I appreciate if you share some experiences.
> :-)

we don't use puppet at all to keep systems up2date and I don't think
it's a good idea either. Your package manager usually does a much better
 job. To manage bigger installations something like satellite or even an
own managed package repository, which you sync with the upstream updates
you need and then run a cron only against that repository might be a
suitable solution.

cheers pete

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: commonly used, defacto standard web frontend to facter ... that everyone loves?

[Disconnect]

We use iClassify but it has been abandoned upstream.

On Mon, Sep 14, 2009 at 1:37 PM, Richard Wurman
 wrote:
>
> I'm new to puppet in general - I just have a minimal node.pp defined
> for 2 clients so far. Before I reinvent the wheel ... is there a good
> web UI to facter that everyone uses? I've looked over foreman and I
> figure since it's new, it's probably not in widespread use currently.
> Any suggestions?
>
> >
>

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Pluginsync always downloads the same unchanged file

[Bostjan Skufca]

Hi!

I have developed couple of plugins and puppet is syncing them. But it
always downloads one particular file disregarding the fact that it has
not changed at all. The md5 hash it displays in the log is indeed
different, but if I do md5sum on the file it displays the correct
hash.

Can someone hint me what could be wrong or what am I doing wrong
b.

PS: Despite this "issue" plugins work just fine.



--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Can puppet handle device files

[Bostjan Skufca]

Nice trick. Thans for all the input!

b.



On Sep 12, 3:42 am, "John A. Barbuto" 
wrote:
> Hi Bostjan,
>
> On Wed, Sep 9, 2009 at 7:17 PM, Bostjan Skufca  
> wrote:
>
> > Hi!
>
> > I cannot find it in documentation (yet?), but can puppet handle device
> > files, in (examplary) form like this:
>
> > file { "/var/named/dev/zero":
> >        ensure   => device,
> >        minor     => 10,
> >        major     => 20,
> >  }
>
> > Can this be done or do I have to create my own type handlers?
>
> I do this by taking advantage of the device files already in /dev:
>
>     define copy_device_node() {
>         exec {
>             "copy_device_node_${name}":
>                 command => "/usr/bin/rsync -aR $name /chroot",
>                 creates => "/chroot${name}",
>         }
>     }
>
>     copy_device_node {
>         "/dev/log": ;
>         "/dev/null": ;
>         ...
>     }
>
> Amazing how many uses you can find for rsync. :)
>
> -jab
>
> --
> John A. Barbuto                         jbarb...@corp.sourceforge.com
> Senior System Administrator             SourceForge, Inc.
--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] commonly used, defacto standard web frontend to facter ... that everyone loves?

[Richard Wurman]

I'm new to puppet in general - I just have a minimal node.pp defined
for 2 clients so far. Before I reinvent the wheel ... is there a good
web UI to facter that everyone uses? I've looked over foreman and I
figure since it's new, it's probably not in widespread use currently.
Any suggestions?

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: error starting puppetmaster after upgrade to 0.25.0

[Allan Marcus]

see the thread "New 2.5 gem does not create entries into /usr/sbin"




---
Thanks,

Allan Marcus
505-667-5666



On Sep 14, 2009, at 10:54 AM, Chris Blumentritt wrote:

> After an upgrade to 0.25.0 I get the following error:
>
> /usr/local/lib/site_ruby/1.8/rubygems.rb:383:in `bin_path': can't  
> find executable puppetmasterd for puppet-0.25.0 (Gem::Exception)
>   from /usr/bin/puppetmasterd:19
>
> Uninstall just 0.25.0 and returning to .0.24.8 and it startup  
> works.  I also uninstalled all puppet gems and just tried to install  
> 0.25.0 by itself.  When I did this no executables were created in  
> the /usr/bin directory for puppet.
>
> I am using hardy as the OS and installing via gem.  Bug or is  
> something whack in my environment?
>
> Chris
>
>
> >


--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] error starting puppetmaster after upgrade to 0.25.0

[Chris Blumentritt]

After an upgrade to 0.25.0 I get the following error:
/usr/local/lib/site_ruby/1.8/rubygems.rb:383:in `bin_path': can't find
executable puppetmasterd for puppet-0.25.0 (Gem::Exception)
from /usr/bin/puppetmasterd:19

Uninstall just 0.25.0 and returning to .0.24.8 and it startup works.  I also
uninstalled all puppet gems and just tried to install 0.25.0 by itself.
 When I did this no executables were created in the /usr/bin directory for
puppet.

I am using hardy as the OS and installing via gem.  Bug or is something
whack in my environment?

Chris

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: modifying a client's config file

[Peter Meier]

>>        augeas {"/boot/grub/grub.conf":
>>                context => "/files/boot/grub/grub.conf",
>>                changes => [ "set timeout 3",
>>                        ],
>>                require => File["/usr/share/augeas/lenses/grub.aug"]
>>                }
>>
>> Because of a bug in the current Augeas I have a copy of
>> /usr/share/augeas/lenses/dist/grub.aug in
>> /usr/share/augeas/lenses/grub.aug where I've edited the hard coded
>> location of /etc/grub.conf to /boot/grub/grub/conf, hence the require on
>> the above. If your /etc is on the same disk partition as your /boot then
>> you won't need this.
>
> Automateit handles these in ruby. I wonder of some of the code that's
> in automateit can be incorporated into puppet since they are both
> GPLed (automateit is GPL3).

what do you mean with these? File editing? augeas is a completely  
different approach than a sed interface in ruby...
But for sure you're always free to add your own providers...

cheers pete

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Installing a lot of packages

[ELTigre]

On Sep 14, 4:00 am, David Schmitt  wrote:
> Chris Blumentritt wrote:
> > The spirit of puppet is to install via the package resource.  You could
> > write a shell script to install using a text file as a data source then
> > use the exec resource using onlyif to check to see if you need to run
> > it.  What I would do is create a separate class in its own manifest file
> > and do some fancy searching and replacing (matching beginnings and
> > endings of lines) with your list of packages.  Since you have so many
> > packages I doubt the resource will be more than one line.  End up with
> > something like:
>
> > package { "package_name": ensure => installed }
>
> > You might run into trouble here if you are using different distros of
> > linux or linux and freebsd as the package names may be different.  You
> > would get the benefit of later being able to hit the file and change
> > installed to latest if you want update a specific package though.
>
> > I have never heard of a file being used as a source for a resource but
> > it is an interesting thought.  You might get away with an inline
> > template to do that but that would be dirty:
>
> > package { inline_template("<%= filename.each_line.collect %>"):
> >   require => File["filename"],
> >   ensure => installed
> > }
>
> No need to make it so complicated:
>
> | $packages = split("\n", file("/etc/puppet/packagelist"))
> | packages { $packages: ensure => latest }
Hi Cris,
Do you think it a good idea to use puppet to maintain servers up2date?
Or  it's better to use some kind of cron scripts?
We're planning to use puppet for this task, but we've found a lot of
packages, dependencies, priorities, essential, no essential so it's a
little bit complicated to split packages regarding categories and
setup puppet for doing this. Another thing we're looking for is how to
manage packages belonging daemon services in production with puppet.

I'd like to know at what level we can use puppet  to keep systems
up2date. I appreciate if you share some experiences.
:-)

thanks

regards,
Israel.

>
> Please be aware though, that this will lead puppet to query the package
> manager for every package, one by one, which may be quite the
> performance hit.
>
> Alternatively only specify the differences from the basic installed
> system and use something like apt-dater to keep your servers up to date.
>
> Regards, DavidS
--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Puppet and Amazon EC2

[Robin Sheat]

Op dinsdag 15 september 2009 01:29:09 schreef CaptTofu:
> * Having the certificate requests for these new instances
> automatically signed
> * Creating a new node for a new instance, once it is up and I know the
> host/ip. As you know, you don't know that until Amazon assigns this.
> How could I automate this? My first impulse is to write Perl or Ruby
> code to write a nodes.pp file, but I'm guessing there is a better way
> to do this (???)

I have puppet configuring all my EC2 images from (almost) scratch to do 
whatever it is they should be doing. I only have a single node definition for 
all of them, and use --fqdn to force them to all pretend to be the same node 
to the puppetmaster.

To distinguish the images from each other, I use the user data, and made a 
factor plugin that will pull that in as 'key=value'. The node description then 
uses those variables to work out what to do, basically with a lot of if 
statements.

As all our EC2 servers are simple variations on a theme (glassfish Java 
application servers running a webapp backed with postgresql), it's quite 
effective. About 20 minutes after startup, all going well, the instance is 
completely configured and running (it takes a while as it's pulling a lot of 
small things over a fairly high-latency connection.)

The plugins and some other misc scripts are here:
https://code.launchpad.net/~eythian/+junk/ec2facts

an example of what I put in the user data is:
inst_glassfish=true
inst_apache2=true
inst_apache2ssl=true
inst_postgresql=true
apache_domain=my.domain.com
apache_template=default
gf_appcontext=context
gf_apps3path=s3bucket/path/webapp.war
pg_database=dbname
pg_db_username=username
pg_db_password=password
pg_db_backup=s3bucket/backup/location
gf_connpool=ConnectionPool
gf_jdbcname=jdbc/TheDB
gf_autoredeploy=false
ebs_volume_id=vol-12345678
gf_restartondeploy=true

-- 
Robin  JabberID: 
http://www.kallisti.net.nz/blog   |||   http://identi.ca/eythian

PGP Key 0xA99CEB6D = 5957 6D23 8B16 EFAB FEF8  7175 14D3 6485 A99C EB6D


signature.asc
Description: This is a digitally signed message part.

[Puppet Users] Puppet and Amazon EC2

[CaptTofu]

Hi all,

So far, I'm finding puppet to be quite excellent. I feel a bit novice,
despite having done admin and programming for almost two decades. I'm
a Perl developer by nature, but am open to learn Ruby and Python. Code
all has so many similarities, and I can grok what any code does.

The question I have is one where I'd like to know what I should be
looking at - what is the best way to automate EC2 instances with
Puppet. What I've done so far is to define two types of servers and
have even created an AMI which has puppet pre-installed and starts up
pointing to my puppet server. This works quite well for the most part.
I do have to iron out dependencies better so things install in a
better order.

The part I don't quite yet grasp is how I could automate:

* Having the certificate requests for these new instances
automatically signed
* Creating a new node for a new instance, once it is up and I know the
host/ip. As you know, you don't know that until Amazon assigns this.
How could I automate this? My first impulse is to write Perl or Ruby
code to write a nodes.pp file, but I'm guessing there is a better way
to do this (???)

Thanks in advance for any help on these questions! I'm sure there are
those out there who've been through setting this up already.

Thanks!

Patrick

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: What does puppetrun do?

[Jordi Funollet]

On Saturday 12 September 2009 11:54:59 grandpa wrote:
> Can I get puppetrun to trigger a remote run of puppet with the same
> result as
> logging in to the remote host and running puppetd --test ?

Hi John,

I just tried 'puppetrun --host xxx' and works as expected. Both machines are 
runnig Debian Stable with 'puppet' and 'facter' installed from 
'backports.org'.
-- 
##
### Jordi Funollet
### http://www.terraquis.net


--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Installing a lot of packages

[David Schmitt]

Chris Blumentritt wrote:
> The spirit of puppet is to install via the package resource.  You could 
> write a shell script to install using a text file as a data source then 
> use the exec resource using onlyif to check to see if you need to run 
> it.  What I would do is create a separate class in its own manifest file 
> and do some fancy searching and replacing (matching beginnings and 
> endings of lines) with your list of packages.  Since you have so many 
> packages I doubt the resource will be more than one line.  End up with 
> something like:
> 
> package { "package_name": ensure => installed }
> 
> You might run into trouble here if you are using different distros of 
> linux or linux and freebsd as the package names may be different.  You 
> would get the benefit of later being able to hit the file and change 
> installed to latest if you want update a specific package though.
> 
> I have never heard of a file being used as a source for a resource but 
> it is an interesting thought.  You might get away with an inline 
> template to do that but that would be dirty:
> 
> package { inline_template("<%= filename.each_line.collect %>"): 
>   require => File["filename"],
>   ensure => installed
> }

No need to make it so complicated:

| $packages = split("\n", file("/etc/puppet/packagelist"))
| packages { $packages: ensure => latest }


Please be aware though, that this will lead puppet to query the package 
manager for every package, one by one, which may be quite the 
performance hit.

Alternatively only specify the differences from the basic installed 
system and use something like apt-dater to keep your servers up to date.


Regards, DavidS


--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: puppetd executes after every 30 minutes

[David Schmitt]

lovewadhwa wrote:
> Hi all
> 
> I executed a manifest to be replicated to all servers through
> puppet.By default puppet executes the manifest if any change in
> configuration every 30 minutes.
> 
> Though i have not changed anything in the configuration or manifest,
> puppet executes the same manifest after every 30 minutes as seen from
> below syslogs.The same logs appear in my syslogs file after every 30
> minutes.
> 
> puppetd[18730]: (//Exec[ssh]
> 
> Believe the log should appear in syslog only the very first time.
> 
> Please help and assure me how can i check my puppet is not executing
> the same manifest again after every 30 minutes.


Puppet does apply the whole manifest by default every 30 minutes. Not 
only the changed parts, but the whole. If you want an Exec to only run 
under specific circumstances, please read the TypeReference for exec on 
the wiki[1], giving special consideration to the creates, refreshonly, 
onlyif and unless parameters.



Regards, DavidS

[1]http://reductivelabs.com/trac/puppet/wiki/TypeReference#exec

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Configuration parse testing

[James Turnbull]

> Great suggestion thanks; we have a slightly different way to generate the 
> list of servers, but the concept is sound.
> Just a couple of notes for anyone who might try this in Debian, with 0.25:
>
> 1) The "puppetmasterd --compile" has to run as the puppet user.  It's 
> something to do with how all the defaults use
> "service" instead of "puppet" to represent the user/group that the process is 
> actually running as.   I use "su", having
> changed the shell for the puppet user to /bin/bash.
>
> 2) You'll need the JSON library package (libjson-ruby1.8 in etch at least).
>
> --

Be great if these other suggestions made it onto the wiki too.

Thanks

James Turnbull

-- 
Author of:
* Pro Linux Systems Administration (http://tinyurl.com/linuxadmin)
* Pulling Strings with Puppet (http://tinyurl.com/pupbook)
* Pro Nagios 2.0 (http://tinyurl.com/pronagios)
* Hardening Linux (http://tinyurl.com/hardeninglinux)

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] is there a conary package provider in the works?

[Richard Wurman]

I have some rpath/foresight machines I'd like to puppet'ize but AFAIK
no one's made a conary package provider ...

I suppose what I most care about are config files for now -- because
we are using the "conary way" of keeping our packages updated.

That said, it would be nice to know that there's something out there?
If there isn't one ... I wonder wow much ruby (maybe python also since
it's conary) do I need to know to make make a conary package provider?

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] puppetd executes after every 30 minutes

[lovewadhwa]

Hi all

I executed a manifest to be replicated to all servers through
puppet.By default puppet executes the manifest if any change in
configuration every 30 minutes.

Though i have not changed anything in the configuration or manifest,
puppet executes the same manifest after every 30 minutes as seen from
below syslogs.The same logs appear in my syslogs file after every 30
minutes.

puppetd[18730]: (//Exec[ssh]

Believe the log should appear in syslog only the very first time.

Please help and assure me how can i check my puppet is not executing
the same manifest again after every 30 minutes.


--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: troubleshooting puppet on Ubuntu

[Julien Garet]

Le 12 sept. 09 à 12:58, Bogdan Bivolaru a écrit :

>
> Hello,

Hello,

> I'm trying to follow the guide at 
> http://reductivelabs.com/trac/puppet/wiki/SimplestPuppetInstallRecipe
> , but I get a funny error when starting Puppetd:
> Server:
> sudo puppetmasterd --verbose
> /usr/lib/ruby/1.8/xmlsimple.rb:275: warning: already initialized
> constant KNOWN_OPTIONS
> /usr/lib/ruby/1.8/xmlsimple.rb:280: warning: already initialized
> constant DEF_KEY_ATTRIBUTES
> /usr/lib/ruby/1.8/xmlsimple.rb:281: warning: already initialized
> constant DEF_ROOT_NAME
> /usr/lib/ruby/1.8/xmlsimple.rb:282: warning: already initialized
> constant DEF_CONTENT_KEY
> /usr/lib/ruby/1.8/xmlsimple.rb:283: warning: already initialized
> constant DEF_XML_DECLARATION
> /usr/lib/ruby/1.8/xmlsimple.rb:284: warning: already initialized
> constant DEF_ANONYMOUS_TAG
> /usr/lib/ruby/1.8/xmlsimple.rb:285: warning: already initialized
> constant DEF_FORCE_ARRAY
> /usr/lib/ruby/1.8/xmlsimple.rb:286: warning: already initialized
> constant DEF_INDENTATION
> /usr/lib/ruby/1.8/xmlsimple.rb:287: warning: already initialized
> constant DEF_KEY_TO_SYMBOL
>
> Client:
> b...@server:~$ sudo puppetd --verbose
> [sudo] password for biv:
> /usr/lib/ruby/1.8/xmlsimple.rb:275: warning: already initialized
> constant KNOWN_OPTIONS
> [ same warnings as on the server ]
> /usr/lib/ruby/1.8/xmlsimple.rb:287: warning: already initialized
> constant DEF_KEY_TO_SYMBOL
> err: Could not create PID file: /var/run/puppet/puppetd.pid
>
> Back on the server I run "sudo puppetca --list", I get the same
> warnings complaining about xmlsimple.rb,  and it tells me there are
> "No certificates to sign". When I run the client on the same machine
> as the server, I still get "Could not create PID". I restarted the
> server machine, but it doesn't seem to help either.
>
> My guess is that there is something wrong with the client - do I need
> to configure anything else? I'm a bit lost from here.
>
> I'm using Ubuntu 9.04 Jaunty on all my machines and I installed
> puppetmaster and puppet from the repositories.


Actually, you've hit a bug in ubuntu on libxml-simple-ruby 
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/296605 
, the way to solve this problem is either :
- download the karmic package and install it
- wait for karmic

Cheers,

Julien


>
> >


--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Installing a lot of packages

[Martin Wheldon]

Hi,

You could take a slightly different approch and create a debian meta
package with all the required packages listed, then have puppet keep
the mata package up to date.

Don't know if this helps.

Martin

On Mon, Sep 14, 2009 at 1:16 AM, Trevor Vaughan  wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> My suggestion, if possible, is to run a nightly cron job that updates
> everything on the system.
>
> This way, puppet only manages the things you actually want to manage.
>
> Trevor
>
> On 09/12/2009 04:56 PM, ELTigre wrote:
>>
>> On Sep 12, 10:10 am, Chris Blumentritt  wrote:
>> Hi Chirs,
>>
>> I only use debian lenny on my servers. I just want to create a class
>> with all package from APT to keep them  up2date all the time with this
>> configuration (ensure => latest) and whenever I create a new server it
>> install all theses packages.
>>
>>> The spirit of puppet is to install via the package resource.  You could
>>> write a shell script to install using a text file as a data source then use
>>> the exec resource using onlyif to check to see if you need to run it.  What
>> How does "onlyif" fits here if I use exec? What should I check to
>> prevent exec running every time puppet client get the catalog?
>>
>>> I would do is create a separate class in its own manifest file and do some
>>> fancy searching and replacing (matching beginnings and endings of lines)
>>> with your list of packages.  Since you have so many packages I doubt the
>>> resource will be more than one line.  End up with something like:
>>> package { "package_name": ensure => installed }
>> Coul you explain me this, please? :-)
>>
>>>
>>
>>
>>> You might run into trouble here if you are using different distros of linux
>>> or linux and freebsd as the package names may be different.  You would get
>>> the benefit of later being able to hit the file and change installed to
>>> latest if you want update a specific package though.
>>>
>>> I have never heard of a file being used as a source for a resource but it is
>>> an interesting thought.  You might get away with an inline template to do
>>> that but that would be dirty:
>>>
>>> package { inline_template("<%= filename.each_line.collect %>"):
>>>   require => File["filename"],
>>>   ensure => installed
>> I'll test it and let you know.
>>
>> thanks a lot.
>> regards,
>> israel
>>>
>>> }
>>>
>>> I have no idea if the above will work and I doubt the erb is correct since
>>> my ruby sucks.
>>>
>>> Chris
>>>
>>> On Sat, Sep 12, 2009 at 12:02 AM, ELTigre  wrote:
>>>
 How can I install a lot (more than 800) of APT packages using an easy
 way in puppet? I mean, using some file.txt where I put there the
 packages I want to install and my package resource get the list . Is
 it possible? Or do I have to put all packages in the package resource?
>>>
 regards,
 Israel.
>> >
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkqti2kACgkQyjMdFR1108B0EQCeIEFZC0Thahsf27RGGeal7Qpv
> MX0An2Kkuwo6a1o0kvtGwq1gei9UHnEu
> =lkQl
> -END PGP SIGNATURE-
>
> >
>

--~--~-~--~~~---~--~~
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.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---