metaspace size or
max-requests-per-instance.
I'll try to lower the numer of workers and see if that has a positive
effect on memory / cpu usage while keeping the compilation times down.
Thanks again for all your suggestions!!
Best regards,
Martijn.
Op 10-2-2020 om 19:02 schreef Justin St
h a third of the memory and only 2
cores, seems to confirm this.
So:
- enough CPU power (I would think)
- enough memory
- no significant garbage collection
- Puppetserver causing a load of 5
Any more tips? Would it make sense to run PuppetDB and PostgreSQL on a
different VM?
Thanks,
Martijn Gr
to keep it down?
Thanks,
Martijn Grendelman
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this
Very nice! Thanks.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://g
what I'd expect.
Any other ideas?
I'd still like to hear how others bootstrap their AWS instances with Puppet
PC1 or newer? Maybe by a different cloud-init method?
Regards, Martijn
Op woensdag 8 november 2017 04:21:24 UTC+1 schreef Poil:
> Why not just create a symlink ?
>
--
Hmm, why didn’t I think of that. :D That should work fine for now. I’ll file a
bug report at Launchpad.
Thanks, Martijn
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from i
s are never replaced by the
instance-id and fqdn, as they were previously. I've tried half a dozen
variations, but none appear to work. Variable interpolation appears to be
limited to the old "puppet.conf.agent" style.
How do *you* bootstrap your Puppet nodes on AWS?
How do you dynam
keys like 'fd0'
and 'sda' from the hash, then you can use the remaining hash as input for
the LVM module.
Regards, Martijn
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and
but I am not sure the use case described in that
ticket is the same. Also, I don't think that adding a 'require' metaparam
to an already evaluated resource should require a re-evaluation of the
resource body.
If my pattern of conditionally adding to a resource's parameters is wrong,
gt;>
Sent: maandag, augustus 14, 2017 15:39
Subject: [Puppet Users] Re: Environment specific folders missing in Puppet
master version 3.6.2
To: Puppet Users
mailto:puppet-users@googlegroups.com>>
Hi Martijn,
Thanks for the quick reply.
Yes, I have set $environmentpath variable in p
Hi Rakshatha,
Did you set the $environmentpath in puppet.conf on the master? That is
needed to enable Directory Environments.
See
https://docs.puppet.com/puppet/3.6/environments_configuring.html#enabling-directory-environments-in-open-source-puppet
Regards, Martijn
Op maandag 14 augustus
our Puppetdb runs on the same host as the puppetserver the
installation was extremely easy. I only had to add the following lines to
our puppetmaster role:
class { 'puppetdb':listen_addresses => '0.0.0.0',
}
class { 'puppetdb::master::config': }
Reg
*csr_attributes.yaml*,
but I'd like to keep Cloud-init as compact as possible and do most things
via Puppet. This is a bit of a chicken and egg problem, so perhaps I should
just do it via Cloud-init.
What do you think? How would you implement this?
Regards, Martijn
--
You received this
t.
So, you could use the server_list.size as the seed to get a different but
number after you pop off an item from your server_list array.
--
Martijn
Op zondag 23 juli 2017 16:51:17 UTC+2 schreef Rob Nelson:
>
> You could try fqdn_rand(). Fqdn_rand will generate a random number, but
> the same rand
I think you're going to have to provide more information than that. Is
anything appearing in the logfiles on agent and master? Which versions are
you running? What has changed (was it working before)? What did you try
already? Etc.
Regards, Martijn
Op woensdag 17 mei 2017 14:35:39
which packages
do we skip, etc.. The actual updates are installed by unattended-upgrades.
Some modules are available for this:
https://forge.puppet.com/tags/unattended-upgrades
Regards, Martijn
--
You received this message because you are subscribed to the Google Groups
"Puppet Users&
eloading Upstart. Could I put those Service, Exec and
File resources all into the same Define, using the define's title to make
each resource unique?
I do feel my design could be simplified but am not seeing how.
Thanks, Martijn
--
You received this message because you are subscribed to th
use this new Upstart service in a
service, e.g.: service {'queue-website01': ensure => running, enable =>
true}. I mean, how do Puppet and the init system know about the new service?
Will that work, or am I going about this completely the wrong way? Should I
be using supervis
Thanks, that's interesting.
Op donderdag 23 februari 2017 10:33:34 UTC+1 schreef Steve ESSO:
>
> I know this post is old, but I'm just posting this answer as I got
> similar requirements and struggled a bit to have it implemented. Anyway,
> following your advise, I was able to automate Mysql Mul
ed it with r10k though.
Regards, Martijn
Op woensdag 14 december 2016 15:20:24 UTC+1 schreef Robert:
>
> Now there is just one question mark left*:
> - in some modules, under files, I store some bigger binaries (like
> apache-maven.tgz or a jdk-1.8.tar.gz) for which I'd like to
;
> -m
>
Hi Matt,
That's interesting. What are you using for ENC?
And I'd love to see your hiera configs, please.
Thanks, Martijn
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and st
That's excellent news Matthaus. Thanks.
Op woensdag 18 mei 2016 20:04:18 UTC+2 schreef Matthaus Litteken:
>
> Martijn,
> Yes, there is a plan for releasing Xenial packages. There are puppetserver
> and puppetdb releases tentatively planned for tomorrow that will contain
r now, but is there any planning on the
availability of a full Xenial setup?
Thanks for the hard work!
Regards, Martijn
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it
bottom of the file where the 'test' database is removed that is
present by default on fresh MySQL installations.
Regards, Martijn
Op donderdag 10 december 2015 15:20:46 UTC+1 schreef Sergiu Cornea:
>
> Hello guys,
>
> I am not sure if this question has been asked, however I
That's awesome. We're not yet up to Puppet 4, but your module is good
inspiration.
Thanks, Martijn
Op donderdag 3 december 2015 22:18:05 UTC+1 schreef David Danzilio:
>
> Let's Encrypt moved to public beta status today; in honor of that here's a
> Puppet mod
That looks very useful. Thanks for releasing it!
Regards, Martijn
Op donderdag 1 oktober 2015 07:25:01 UTC+2 schreef Corey Osman:
>
> Last year I had an idea to create a tool to automate the buildout of
> puppet unit tests by inspecting puppet code inside puppet manifests. Along
&g
tlabs
packages should lead to a working configuration. If that's not possible the
user should be notified. I hope Puppetlabs will someday resolve this.
Regards, Martijn
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsub
t that experienced with Puppet code yet it's something to be
aware of.
Regards, Martijn
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-use
Currently rebuilding my Puppet infra. This may be just what I need! Thanks.
Op woensdag 10 juni 2015 00:25:13 UTC+2 schreef Pete Brown:
>
>
> If you aren't aware of the module it is my take on managing puppet and
> friends with puppet.
> It doesn't do everything yet but it manages a significant
Op dinsdag 14 april 2015 14:07:24 UTC+2 schreef akash bhatia:
>
>
> i just want to understand the concept of how to achieve the same on the
> AWS, where we dont have liberty to customise domain name while creating a
> new instance in AWS EC2.
>
>
It is possible to set your own custom domain name
Thanks. Interesting slides!
Regards, Martijn
Op zaterdag 14 maart 2015 01:32:29 UTC+1 schreef Krzysztof Suszyński:
>
> Hi,
>
> I'm pleased to publish slides for lecture: "Reusable Puppet Modules -
> Development & Testing" that I've performed on WPUG (War
As a side node, that error ("Attempt to assign to a reserved variable") seems
to be caused by an error in your manifests. I don't see how it could be
related to the dns_alt_names setting in puppet.conf.
Regards, Martijn
Op maandag 16 maart 2015 20:59:33 UTC+1 schreef Rob
Here's an archive.org copy of the Posterous article you linked:
https://web.archive.org/web/20130304065656/http://glarizza.posterous.com/managing-puppet-ssl-certificates
It provides some example code that may be helpful to you.
Regards, Martijn
Op dinsdag 9 december 2014 23:54:19
Matt, I'd be very interested in that 'cert-api' endpoint code once you've
had a chance to work on this. Is there a change you could open-source that?
I think it would be very useful to the community, even if it is imperfect.
Hope you'll consider it,
Martijn
Op vrijdag
On Thursday, December 4, 2014 9:50:56 AM UTC+1, Martijn Grendelman wrote:
>
> Hi Henrik and Wil,
>
> > Is there ANY way that the notifys in the apache::vhost type would
>> > display a different value? Shouldn't $apache::params::priority and
>> > $priority
the resource apache::vhost{test: }. If you instead
> include the class prior to instantiating the resource it may work better.
>
> (Or organize the thing differently once you read about the order classes
> and defines are evaluated.)
>
Thank you both for helpful tips. I see I
things
for over an hour, and I'm afraid I'm losing my sanity...
Best regards,
Martijn.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-u
Very nice, thanks!
Op dinsdag 26 augustus 2014 15:04:39 UTC+2 schreef Erik Dalén:
>
> A new release of Puppet Explorer is out. It includes a new look which you
> can check out at the new public demo site: http://demo.puppetexplorer.io/
>
--
You received this message because you are subscribed t
a to graph metrics and show anomalies, not just for Puppet runs. I'd
prefer to add some active alerting to this pipeline, but have yet to figure
that out.
There are many ways to do this, but this works pretty well for us.
Regards, Martijn
Op dinsdag 26 augustus 2014 19:34:51 UTC+2 sc
s rolling. The remainder
is standard Puppet stuff (i.e. Facter, Hiera, Puppet).
Regards, Martijn
Op dinsdag 26 augustus 2014 21:41:01 UTC+2 schreef Alex Demitri:
>
> Hi guys - i am fairly new to puppet and i am trying to figure out ways to
> implement it in my organization to make good
That's very nice. Should make testing a pre-release easier for many users
than building from Git.
Thanks,
Martijn
Op dinsdag 26 augustus 2014 19:23:54 UTC+2 schreef Eric Sorenson:
>
> After the Puppet 3.5.0 release problems, we had a retrospective and tried
> to figure ou
will
'share' actual Puppet resources between nodes. Kind of hard to explain, so
check the Nagios example in the doc.
Hope this helps,
Martijn
Op woensdag 9 juli 2014 09:30:31 UTC+2 schreef shashank sinha:
>
> Hi,
>
> I have written a code on template to open & read file
to a .0 release.
Regards, Martijn
Op maandag 7 april 2014 16:14:51 UTC+2 schreef Jonathan Gazeley:
>
> This release of puppet was withdrawn after bugs were identified.
>
> https://groups.google.com/forum/#!msg/puppet-users/uJCKQ7uUlCs/46Hlk3REjQoJ
>
>
--
You received this message
.
Regards, Martijn
Op donderdag 6 februari 2014 13:41:44 UTC+1 schreef David Schmitt:
>
> Hi,
>
>
> Would it be enough to reduce the frequency of puppet runs to, like, once
> a day?
>
> Regards, David
>
> On 06.02.2014 12:13, Martijn wrote:
> > We run a small numbe
mit and cgroups, but am unsure how to
apply those via Puppet.
How can I avoid this throttling and the resulting alerts?
Reducing the number of Puppet resources further, to reduce the load,
appears difficult and would likely not be enough. Any other ideas?
Regards, Martijn
--
You received this
facter-1.7.4-rc1 is available and it looks like it works!
Martijn
Op woensdag 30 oktober 2013 17:50:59 UTC+1 schreef Paul Tötterman:
>
> Hi,
>
> Is anyone else getting this:
>
> $ facter
> /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.
}
> }
>
> John
>
Thanks John,
I ran into your answer via a Google search and was able to get nested case
statements working properly. The code can become quite verbose, but that's
not necessarily a bad thing. :)
Regards, Martijn
--
You received this message because you are su
the armhf
platform, since 'disposable' computing devices like the Raspberry Pi are a
good fit for config management. For now, I'm using the above repo.
Regards, Martijn
Op donderdag 15 augustus 2013 17:36:47 UTC+2 schreef Alastair Montgomery:
>
> I'm trying to install
Good idea, and much needed IMHO. Thanks!
Martijn
Op maandag 24 juni 2013 15:26:50 UTC+2 schreef Jens Braeuer het volgende:
>
> So I would like to make you aware of one of my side-projects called
> Raziel.
> https://github.com/jbraeuer/raziel/
> http://bit.ly/raziel-slides
>
warning is for. It doesn't break anything
yet, but gets people to take notice. :-)
Thankfully, deprecation warnings only show when the puppet master is
restarted.
Regards, Martijn
--
You received this message because you are subscribed to the Google Groups
"Puppet Users"
Just to clarify that statement: Postgres is actually optional, but
recommended for production use. The embedded db works fine for testing but
doesn't scale well.
Regards, Martijn
Op vrijdag 24 mei 2013 23:36:13 UTC+2 schreef Ashley Penney het volgende:
>
> You definitely still ne
cloud-init script to correctly bootstrap new nodes:
source: "deb http://apt.puppetlabs.com $RELEASE main dependencies"
Also, I've fixed existing nodes by pushing a similar change through Puppet
before attempting the upgrade to 3.2.1.
Regards, Martijn
Op donderdag 23 mei 2013
That is very cool, Erik, and looks very useful.
Thanks,
Martijn
Op maandag 27 mei 2013 20:44:19 UTC+2 schreef Erik Dalén het volgende:
>
> I just released dalen-puppetdbquery 1.1.0, one cool new feature in this
> release is a hiera backend.
>
>
--
You received this message
Ah, that bit me too. Thanks for clarifying. That's why aptitude was unable
to find a correct path to upgrade from Puppet 3.1.
I'll add the dependencies repo on all nodes.
Regards, Martijn
Op donderdag 23 mei 2013 02:08:42 UTC+2 schreef Matthaus Litteken het
volgende:
>
>
After 4 days without errors, I can safely say that using the latest Java 6
works fine.
Thanks again Ken.
Regards, Martijn
Op vrijdag 3 mei 2013 14:46:25 UTC+2 schreef Martijn het volgende:
>
> Hi Ken,
>
> I was indeed using openjdk-7. I've now downgraded to 6 and will see
Done!
More votes are definitely welcome, so if you use AWS and Puppet, do it!
Regards, Martijn
Op zaterdag 4 mei 2013 19:52:48 UTC+2 schreef Martin Rio het volgende:
>
> AWS pays lot of attention to customer feedback. Anyone who want's Puppet
> support in OpsWorks, take a minute
Op vrijdag 3 mei 2013 21:37:46 UTC+2 schreef Hugh Cole-Baker het volgende:
>
> On Friday, May 3, 2013 4:50:38 PM UTC+1, Martijn wrote:
>>
>> Dear list,
>>
>> When I bootstrap a new EC2 instance from a base Ubuntu 12.04 LTS image I
>> use cloud-init to insta
ut I'd like
to keep the bootstrapping as simple as possible and manage things via
Puppet.
This must be a common task, so how do you do it?
Thanks, Martijn
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this g
Hi Ken,
I was indeed using openjdk-7. I've now downgraded to 6 and will see if this
helps.
Thanks for the advice,
Martijn
Op donderdag 2 mei 2013 14:52:27 UTC+2 schreef Ken Barber het volgende:
>
> Are you running version 7 of the JDK? We believe this was a bug
> introduced du
citly allow agent IP's through the firewall to the master. The master
also collects reports from agents in puppet-dashboard and facts and catalog
are stored in PuppetDB.
Regards, Martijn
--
You received this message because you are subscribed to the Google Groups
"Puppet Users"
B.
ii puppetmaster-common
3.1.1-1puppetlabs1 Puppet master common scripts
ii puppetmaster-passenger
3.1.1-1puppetlabs1 Centralised configuration management
- master setup to run under mod passenger
Any idea what could be causi
ting a run. Add --noop for a trial-run, say if you just want
to see what would happen.
Contrary to Drew's suggestion we actually prefer running the agent service,
instead of cron. Just to provide another opinion :). Still, both methods
should work fine, so we'll need to figure that out
able to perform, so we'll know what would or wouldn't work.
Regards, Martijn
Op maandag 8 april 2013 13:03:27 UTC+2 schreef Richard het volgende:
>
> Hi All,
>
> I'm currently using puppet to deploy our O/S configuration to servers.
> I've got a requirement
/etc/puppetdb/conf.d
root@puppet:/var/lib/puppetdb/mq/localhost/KahaDB# dpkg -s puppetdb | grep
Version
Version: 1.1.1-1puppetlabs1
Regards, Martijn
Op woensdag 13 februari 2013 19:00:40 UTC+1 schreef Ken Barber het volgende:
>
> Hi all,
>
> I've been looking at a potential
so
we let dpkg figure out the dependency hell. We've not had any issues in the
9 months since we started using EC2 that we could blame on versions.
Of course upgrading to a newer Long Term Support release will take some
serious testing, but so far this simple method seems to work and sav
y. All those tools you drop in
/usr/local could easily be packaged, providing you with all the advantages
a packaging system has. Also, Puppet knows how to deal with packages, so
your Puppet manifests will be simpler as well.
Regards, Martijn Heemels
Op dinsdag 20 november 2012 10:44:01 U
a one to one replacement.
>
> Be advised :-)
>
> sent from my mobile
> On Nov 7, 2012 12:36 AM, "Martijn" wrote:
>
>> Op donderdag 1 november 2012 19:03:20 UTC+1 schreef Greg Sutcliffe het
>> volgende:
>>
>>> On 1 November 2012 17:54, Lucas Vick
e it's the main interface to Puppet
Enterprise as well I don't see it going away soon. The Foreman is also an
impressive dashboard with more features than Puppet Dashboard but a bit
more complexity as well.
Regards, Martijn Heemels
--
You received this message because you are
puppet:
conf:
agent:
server: "puppet.example.com"
certname: "%i.web.cluster1.ec2"
pluginsync: "true"
Regards, Martijn Heemels
Op maandag 2 juli 2012 22:58:28 UTC+2 schreef Leej het volgende:
>
> Hello, new user here. I'm trying to bootstr
Very nice! Congratulations.
I see a lot of things that will make my life easier. I can't wait to try it.
Regards, Martijn Heemels
Op vrijdag 28 september 2012 23:49:21 UTC+2 schreef Michael Stanhke het
volgende:
>
> Puppet 3.0.0 is a feature release for the 3.x series of Puppet.
&
tlabs/puppet/modules:/opt/puppet/share/puppet/modules
Run the first command again, and you should see that Puppet now uses the
path you specified.
Hope this helps,
Martijn Heemels
Op maandag 17 september 2012 09:42:12 UTC+2 schreef itJunky het volgende:
>
> My main issue it Where i can fin
be very interested to see how
others set up their version control workflow, since I'm looking into Hiera
as well.
Regards, Martijn
Op donderdag 30 augustus 2012 18:06:07 UTC+2 schreef Stephen Price het
volgende:
>
> I'm in the process of migrating data out of my standard Pup
Interesting! As a Puppet user working in Den Bosch I guess I'll come take a
look. I don't know what the goal of the talk is, but it'll be nice to meet
some fellow users in the area.
Regards, Martijn
Op vrijdag 31 augustus 2012 04:03:06 UTC+2 schreef Emilien Klein het
volgende
On 28-03-12 14:39, R.I.Pienaar wrote:
>
>
> - Original Message -
>> From: "Martijn Grendelman"
>
>
>
>> http://serverfault.com/questions/368784/puppet-and-templates-how-to-loop-sequently-and-not-randomly
>>
>> which suggests to
did stumble across this post:
http://serverfault.com/questions/368784/puppet-and-templates-how-to-loop-sequently-and-not-randomly
which suggests to do something like
<% aliases.sort_by {|key, value| key}.each_pair do |key, val| -%>
<% end -%>
Will it work? Is that a proper s
eurwebtest02 {
> include apache2
> include apache2::mods
> include apache2::pringo
> import "apache2/vhost.pp"
>
> vhost { 'local':
> }
>
> vhost { 'test':
> servername
No one? Is my question not clear (TL;DR, perhaps?), or doesn't anyone have
an answer?
Best regards,
Martijn.
On 17-11-11 17:18, Martijn Grendelman wrote:
> Hi,
>
> A small addition at the bottom...
>
>> I was looking at the basic example for exporting and collecti
On 17-11-11 11:51, Martijn Grendelman wrote:
> Hi,
>
> Is there a way to 'unique-ify' a collection of resources?
>
> Suppose that nodes export '@@nagios_hostgroup' resources for hostgroups
> that they want to be a member of. The Nagios server node
hen adding the class to a third server, all servers get the
Firewall::Rule from the two others, but never from itself.
> So exporting works (confirmed by looking at the database). So does
> collecting, only not from the local node. What am I doing wrong?
Most curious...
Best regards,
Martij
l::Rule[xtreemfs-repl-serverA], and on serverB, it's the other way
around.
So exporting works (confirmed by looking at the database). So does
collecting, only not from the local node. What am I doing wrong?
Best regards,
Martijn Grendelman
--
You received this message because you are subsc
me hostgroups, because the whole point of
having hostgroups is, that multiple hosts can be a member :-) So, the
collection would lead to duplicate definitions. Is there a way to avoid that?
Best regards,
Martijn Grendelman
--
You received this message because you are subscribed to the Google Group
:
Oct 18 09:02:13 dolly puppet-master[31443]: Report processor failed: Could
not create RRD file
/var/lib/puppet/rrd/server011.dev.iphion.nl/changes.rrd: you must define
at least one Data Source
Any idea what I could do to fix this?
Best regards,
Martijn Grendelman
--
iphion B.V.
TU/e Innovation
gards,
Martijn Grendelman
--
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
On 14-10-11 20:14, Nigel Kersten wrote:
>
>
> On Fri, Oct 14, 2011 at 11:11 AM, Jacob Helwig <mailto:ja...@puppetlabs.com>> wrote:
>
> On Fri, 14 Oct 2011 10:04:19 -0700, Nigel Kersten wrote:
> >
> > On Fri, Oct 14, 2011 at 7:05 AM, Martijn Grend
ts/..."
A little digging into the source revealed to me, that this feature is not
present in 2.6.3, but it is in 2.7.5. I have no idea in what version it
was introduced.
It would be nice if the type reference would contain that information.
Best regards,
Martijn Grendelman
--
You receive
On 29-09-11 14:03, Jonathan Stanton wrote:
> On Sep 29, 2011, at 7:35 AM, Martijn Grendelman wrote:
>>
>> Hi,
>>
>> I am currently testing my catalog, that runs fine with 2.6.3, with Puppet
>> 2.7.4. Now I am running into a problem, and I wonder why this was &#
he resource to prevent it being added repeatedly on every
catalog run, but apart from that? I have never had any problems with it.
If whitespace is permitted from OpenSSH's point of view, shouldn't Puppet
allow it too, and fix problems like this the right way? Or am I missing
something?
B
Hi,
I have this:
service { "bind9":
ensure => running,
hasrestart => true,
pattern => "named",
require => Package["bind9"],
}
because the process is called 'named'.
Best regards,
Martijn Grendel
age with Hiera...
Thanks for all your input!
Best regards,
Martijn Grendelman
--
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 t
I personally recommend avoiding deep node inheritance hierarchies.
> In fact, I recommend no more than two levels to your node inheritance
> tree. This may or may not help with your present problem.
We have three levels: a basenode in which we set defaults, a level for
'internal' and '
xec depend on those.
Best regards,
Martijn Grendelman
> --
> 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
nal = $shmmax
> } else {
> if $oracle {
> # For non-shm half the RAM for <= 4G, 2G otherwise
> if $mem <= 4294967296 {
> $shmmax_final = $mem / 2
> } else {
> $shmmax_final = $mem - 21474
values for certain nodes or groups of nodes (by inheritance)? And I'd
/really/ prefer to do that without having to pass on each and every value
as a parameter to the next included class...
Best regards,
Martijn.
--
You received this message because you are subscribed to the Google Groups
client? In other words:
during a puppet run, is 'classes.txt' updated before the facts are expanded?
Will explain my setup in a separate mail.
Best regards,
Martijn.
>
>
> On 8 June 2011 15:18, Chris Phillips <mailto:ch...@untrepid.com>> wrote:
>
>
ps)
that joins all the lines in the hostgroups-file together, for use with
nagios_host's hostgroups parameter.
The biggest drawback is that it takes two puppet runs on the target (first
one for populating the hostgroups-file, so that the custom fact is set
properly on the second run) befor
allow me to produce a report of packages that need
> upgraded. I can't just "ensure => latest" because it violates our
> change procedure.
>
You could define a type, that wraps Package and uses an Exec to do
whatever you want.
Best regards,
Martijn.
--
You received this
e, I'd try "ensure => absent". I think I remember
>> that works.
>>
>> For the httpd example, I'd try just ensuring that the httpd package isn't
>> installed.
>
Regards,
Martijn.
--
You received this message because you are subscribed to the
give many results in Google, so I wonder:
What exactly does that mean?
Does it do something unexpected (I expect the default to apply to any
apt::package defined in that specific class, and nothing else)?
Why is it necessary to log this, if nothing is wrong?
Best regards,
Martijn.
--
You recei
t should be named
users::something to be found by the autoloading mechanism. groups::namidev
doesn't work, it would only be found in a module named 'groups'.
Best regards,
Martijn.
--
You received this message because you are subscribed to the Google Groups
"Pup
On 11-03-11 12:46, Martijn Grendelman wrote:
[snip]
> I did exactly what you did: use exported concat-fragments to collect the
> hostgroups on the puppetmaster and then use generate() to provision the
> hostgroups parameter of the nagios_host.
[snip]
> The biggest downside of my s
1 - 100 of 158 matches
Mail list logo
