So who else is going to this next week?
Anyone want to meet up?
Matt.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-use
Patrick Debois, Kris Buytaert, and myself will be there. We're expecting a
rumble with the LCFG guys.
J.
On 18 March 2010 07:04, Matthew Macdonald-Wallace wrote:
> So who else is going to this next week?
>
> Anyone want to meet up?
>
> Matt.
>
> --
> You received this message because you are su
Hi Marcus,
On 16 mrt, 14:26, Marcus Moeller wrote:
> First of all I would like to know if it's possible to use variables
> within the define statement, e.g.:
>
> define $module_name::preseed_package
>
> This would make the define much more flexible as I could then just
> copy it over to the other
> So who else is going to this next week?
>
> Anyone want to meet up?
I have tickets, might make it
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this g
On 3/17/2010 8:41 PM, Luke Kanies wrote:
If you have two services, where one service specifies that it being in a
'running' state requires that the other service must also be in a
'running' state, when you got to restart the required service then the
requiring service can automatically be brought
Ah, turns out the group type doesn't support the 'members' attribute
on CentOS anyway - dilemma avoided :)
On Tue, Mar 16, 2010 at 11:20 AM, Dick Davies wrote:
> On Mon, Mar 15, 2010 at 9:52 AM, Bruce Richardson
> wrote:
>> On Mon, Mar 15, 2010 at 09:31:54AM +, Dick Davies wrote:
>>> Offhan
On Wed, Mar 17, 2010 at 7:35 PM, Christopher Johnston
wrote:
> I guess my only gripe here is I have about 2 dozen modules most of install
> some form of a pkg from yum. So they all have a direct dependency on my yum
> module to do the right thing. I would hate to have to put a require in
> every
Can some help explain the differences and use cases of subscribe and
require. They seem to have a bit overlap in the sense that they do the same
thing almost. I understand a require sets up a dependency. So for eg the
following below would setup a dependency on the package pam to be installed
in
Being able to install yum groups would be a nice value add. Sucks having to
list out 8-9 packages and hope rpm/yum deps get sorted out. But what I am
really griping about though is something like this.
Say you have 2 modules, one called ntpd and one called snmpd. Two totally
different types of
On Thu, Mar 18, 2010 at 2:57 PM, Christopher Johnston
wrote:
> Can some help explain the differences and use cases of subscribe and
> require. They seem to have a bit overlap in the sense that they do the same
> thing almost. I understand a require sets up a dependency. So for eg the
> followin
But what I am confused about is how is subscribe different? Doesn't that
handle the same relationship of saying that you are "subscribing" (and/or)
requiring something?
there is subscribe/notify and require/before. The last 2 simply order
resources and the first two either listen on events or
On Thu, Mar 18, 2010 at 10:07 AM, Daniel Kerwin wrote:
> On Thu, Mar 18, 2010 at 2:57 PM, Christopher Johnston
> wrote:
>> Can some help explain the differences and use cases of subscribe and
>> require. They seem to have a bit overlap in the sense that they do the same
>> thing almost. I under
On Thu, Mar 18, 2010 at 10:03 AM, Christopher Johnston
wrote:
> Being able to install yum groups would be a nice value add. Sucks having to
> list out 8-9 packages and hope rpm/yum deps get sorted out. But what I am
> really griping about though is something like this.
Well, if the packages *do
Ok, that helped a lot. I read the documentation which is helpful, but the
way you described it here made it easier to understand the use cases.
On Thu, Mar 18, 2010 at 10:10 AM, Peter Meier wrote:
> But what I am confused about is how is subscribe different? Doesn't that
>> handle the same rela
>
> To put it another way, subscribe is a special case of require with
> added magic in it. They both imply the same ordering relationship,
> but require adds the additional 'restart if this is changed' logic.
That should read "but subscribe adds the additional..."
>
> Similarly, notify is lik
I keep writing these exec types to things like service restart,
sounds like I dont need them and could just use subscribe which will in
effect do the same thing.
exec { 'sssd-restart':
command => '/sbin/service sssd restart',
refreshonly => true,
require => File['/etc/sssd/s
Michael DeHaan wrote:
> What if we taught the yum provider to know about "yum groupinstall" ?
>
> That way you could add packages into comps.xml and reference them
> together, which would also be faster than referencing each one by one.
>
> While it would not technically be a 'package' this might b
Majority of the time rpm deps in fedora are good, so thats not that big of a
concern. I am just overly anal about stuff where if I install the ldap
client I also make sure pam is there also (yet you would expect the rpm dep
to satisfy it).
Hmm, maybe you are misunderstanding me. The NTPD class/m
On Thu, Mar 18, 2010 at 7:32 AM, Christopher Johnston
wrote:
> Majority of the time rpm deps in fedora are good, so thats not that big of a
> concern. I am just overly anal about stuff where if I install the ldap
> client I also make sure pam is there also (yet you would expect the rpm dep
> to s
Hey Guys,
I wrote some custom facts that generate about 80 additional facts. It
parses the output of the HP SmartArray command line utility,
'hpacucli'. I am also used stored configs.
puppetd sends the facts to the puppetmaster by using a get request.
The server does not accept the request as the
Hi,
I am trying to use puppet to configure bacula. I am wondering whether
anybody have done anything for this before?
Bacula needs 2 files for every client, with a common shared key per
client in these 2 files. The best solution I can think is to write a
script that generates these 2 files per cl
On Thu, Mar 18, 2010 at 10:25 AM, Todd Zullinger wrote:
> Michael DeHaan wrote:
>> What if we taught the yum provider to know about "yum groupinstall" ?
>>
>> That way you could add packages into comps.xml and reference them
>> together, which would also be faster than referencing each one by one.
Hi,
Anyone running puppetd --test in their preseed late_command? I can't
seem to get it working as the installer hangs forever in the
late_preseed stage.
This is what I am using,
d-i preseed/late_command string chroot /target; mount /proc;
/usr/sbin/puppetd --test --server puppetserver.my.
On Thu, Mar 18, 2010 at 10:32 AM, Christopher Johnston
wrote:
> Majority of the time rpm deps in fedora are good, so thats not that big of a
> concern. I am just overly anal about stuff where if I install the ldap
> client I also make sure pam is there also (yet you would expect the rpm dep
> to
> We set a resource default at the top level of our manifests like this:
>
> Package { require => Class["package::apt::update"] }
Beat me to it :)
>
> and that class manages it's own internal dependencies so that before
> any package is installed, we're guaranteed to have run:
>
> apt-get update
Yup the yum manifest sets up my configuration files for the various repos
(ie, we have a development repos for our lab that only goes on lab systems
and production hosts the production repo).
Package { require => Class["yum::base"] }
I guess I could put that in every manifest at the top that is d
On Thu, Mar 18, 2010 at 10:21 AM, Christopher Johnston
wrote:
> I keep writing these exec types to things like service restart,
> sounds like I dont need them and could just use subscribe which will in
> effect do the same thing.
> exec { 'sssd-restart':
> command => '/sbin/service sssd
This answered all my questions, thx! Should hopefully clean up my manifests
a bit those execs were overkill.
On Thu, Mar 18, 2010 at 11:51 AM, Michael DeHaan
wrote:
> On Thu, Mar 18, 2010 at 10:21 AM, Christopher Johnston
> wrote:
> > I keep writing these exec types to things like service
> re
On Thu, Mar 18, 2010 at 8:49 AM, Christopher Johnston
wrote:
> Yup the yum manifest sets up my configuration files for the various repos
> (ie, we have a development repos for our lab that only goes on lab systems
> and production hosts the production repo).
>
> Package { require => Class["yum::ba
Hello,
I'm running puppet on a bunch of Red Hat Enterprise Linux 5 machines.
I am seeing an issue where puppetd will freeze in the middle of a run,
regularly. If I run with --debug, the last line of output I see is
usually a command that completes quickly, or a notification that
something has succ
On Thu, Mar 18, 2010 at 12:36 PM, Thomas wrote:
> Hello,
>
> I'm running puppet on a bunch of Red Hat Enterprise Linux 5 machines.
> I am seeing an issue where puppetd will freeze in the middle of a run,
> regularly. If I run with --debug, the last line of output I see is
> usually a command that
Puppet is version 0.25.4
The machines are all running under similar hardware, sorry if the word
"class" was misleading. The database machines are failing to run
puppet, while all of the other servers (mostly application servers)
have no problem.
On Mar 18, 12:41 pm, Michael DeHaan wrote:
> On T
On Wed, Mar 17, 2010 at 07:10:20PM -0400, Derek Yarnell wrote:
> Hi,
>
> Anyone running puppetd --test in their preseed late_command? I
> can't seem to get it working as the installer hangs forever in the
> late_preseed stage.
>
> This is what I am using,
>
> d-i preseed/late_command string chr
When no environment is defined it uses production, per my notes:
environments = production,testing,development
manifest = /opt/puppet/production/site.pp
modulepath = /opt/puppet/production/modules
This is part of [main].
On Wed, Mar 17, 2010 at 5:00 PM, Rob McBroom wrote:
> How is the
Thomas writes:
> Hello,
>
> I'm running puppet on a bunch of Red Hat Enterprise Linux 5 machines.
> I am seeing an issue where puppetd will freeze in the middle of a run,
> regularly. If I run with --debug, the last line of output I see is
> usually a command that completes quickly, or a notifica
On Thu, Mar 18, 2010 at 12:45 PM, Thomas wrote:
> Puppet is version 0.25.4
>
> The machines are all running under similar hardware, sorry if the word
> "class" was misleading. The database machines are failing to run
> puppet, while all of the other servers (mostly application servers)
> have no p
pstree doesn't show anything interesting:
├─sshd,1354
│ ├─sshd,2008
│ │ └─bash,2010
│ ├─sshd,4942
│ │ └─bash,4944
│ │ └─puppetd,5459 /usr/sbin/puppetd --onetime --no-
daemonize --test --pluginsync --factpath=/var/lib/puppet/lib/facter --
server puppet1.sermo.dev
│
I have a situation where I am trying to manage some systems that have
a single IP address but different ssh port numbers. For each of these
systems I need to individually manage a logrotate.d configuration
file, and a separate archive directory.
Of course, this won't work...
file {
"/data/sys
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> and this:
>
> if ! defined(File["/data/syslog/${remote_host}/archive"]) {
> file {
> "/data/syslog/${remote_host}/archive":
> ensure => directory;
> }
> }
this should work.
> both of which r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> puppetd sends the facts to the puppetmaster by using a get request.
> The server does not accept the request as the URL is too long, I
> realize I could probably tweak this on the server side. But my
> question is this.
which version of puppet are
Looking into it more, I think I found the root of the problem. The
following is a snippet from my puppet configuration:
# create /var/log/mysql/archived_logs
file { "archived_logs":
path=> "/var/log/mysql/archived_logs",
ensure => directory,
On Thu, Mar 18, 2010 at 3:04 PM, Peter Meier wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>> and this:
>>
>> if ! defined(File["/data/syslog/${remote_host}/archive"]) {
>> file {
>> "/data/syslog/${remote_host}/archive":
>> ensure => directory;
I enabled reports on my puppetmaster and client. I am getting the following
error when ever I run pupetd --test.I am using v 0.24.8 on both the
client and the server.
err: Reporting failed: private method `gsub' called for true:TrueClass
--
You received this message because you are subscrib
Nevermind, I had a config error its "report = true" and not "reports =
true".
-Chris
On Thu, Mar 18, 2010 at 4:03 PM, Christopher Johnston wrote:
> I enabled reports on my puppetmaster and client. I am getting the
> following error when ever I run pupetd --test.I am using v 0.24.8 on
> both
Hey,
Many thanks! I was spending way too much time troubleshooting this
when found your solution!
Rafael
On Feb 13, 7:46 am, Trevor Vaughan wrote:
> You need to add the following to your exec:
>
> environment => ['PAGER=/bin/cat','DISPLAY=:9']
>
> vmware-config-tools.pl is kind of awful.
>
> Tre
On Mar 18, 2010, at 12:24 PM, Thomas wrote:
> Looking into it more, I think I found the root of the problem. The
> following is a snippet from my puppet configuration:
>
> # create /var/log/mysql/archived_logs
> file { "archived_logs":
> path=> "/var/log/mysql/archive
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> What exactly are you trying to do here? Are you trying to push logs
> from the server to the clients? If not, why do you have "recurse =>
> true"? If you are trying to push permissions, this isn't a good way
> to do it. Sadly, Puppet is slow enou
I am using 0.25.4 but I am running the puppetmaster through
mod_passenger. I just recently switched over from the standalone
puppetmaster because we are deploying a lot more systems now and I
want to avoid any performance problems. I suppose this very well could
be fixed.
For those using mod_passe
Finally found the issue
I never looked into the /etc/puppet directory(my bad), there was the issue,
a strange one although but here is what happened, in there were two
files(wish I knew why there were that second if we use puppet 0.24.8):
puppet.conf
puppetd.conf
Same content, nothing different,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Functions can absolutely be used inside of manifests.
You may be running into an issue in that 'defined' works based on the
compile time order of your manifests.
Example:
class foo { ... }
class bar { ... }
# This does not work as expected
if ! de
50 matches
Mail list logo
