Hi,
I try to write an autoconfigure module (collectd) that depends on other
modules included for my node.
So I've this class autoloaded for all my nodes :
class collectd::client::autoconfig {
require collectd::client
if tagged('apache') {
require apache
include collectd::client::
Hi all,
When using the Notify resource type, is there any way to hide the log
message that is produced by the definition itself and only keep the
actual message string on the output generated by Puppet agent?
In this example:
Notice: hello
Notice: /Stage[main]/Foo::Bar/Notify[baz]/messag
Hi,
I tried to find in r10k documentation about what to expect when doing a
r10k deploy module module_name command but I didn't find explicit behavior
for Puppetfile.
What I understand is if I want an updated Puppetfile (from Control Repo) I
must run r10k deploy environment command. Otherwis
On Friday, November 28, 2014 7:03:54 PM UTC-6, pankaj sehgal wrote:
>
> Thanks for the reply.
> I m not cloaking any fact just trying to know in a general puppet run how
> it should go??
If you cannot tell the difference then what does it matter? Or to put it
the other way around, why is
On Sunday, November 30, 2014 8:57:50 PM UTC-6, fauzi.p...@gmail.com wrote:
>
> Can I use yum update on puppet master then make it also changes in puppet
> agent? I dont know the step, could you please show me the step if it can be
> done. Thank you
>
>
No, Puppet does not work that way, and I
On Monday, December 1, 2014 2:21:01 AM UTC-6, Poil wrote:
>
> Hi,
>
> I try to write an autoconfigure module (collectd) that depends on other
> modules included for my node.
>
If you mean you are writing a module containing declarations that are
conditioned on whether other classes or module
Maybe you could use the notice() or warn() functions?
--
Spencer Krum
n...@spencerkrum.com
On Mon, Dec 1, 2014, at 04:36 AM, Nacho Barrientos wrote:
> Hi all,
>
> When using the Notify resource type, is there any way to hide the log
> message that is produced by the definition itself and
Simon,
Think of the Puppetfile like a Puppet manifest... It is a desired
end-state declaration... You don't just run r10k to update a single
module, you run the deploy environment to deploy that environment to
make it match what the Puppetfile specifies. In this case an r10k
environment is a
Hi,
I am trying to loop the iterations and concatenate the values. But the code
is working on ruby, but when i implement the code in puppet facts, it is
not returning any value.
require 'facter'
require 'facter/util/file_read'
logfile = "/home/weblogic/javaapp.txt"
java_count = 0
first = nil
On Nov 27, 2014 12:54 AM, "Peter Bauer" wrote:
>
> i know that PuppetDB is the way to go for the future but currently i am
forced to use Puppet 2.7 with the Stored Configuration feature.
Are you aware that you can use PuppetDB 1.6 with Puppet 2.7? (I'm assuming
you're using it for exported resour
Nice work Felix!
On 1 December 2014 at 00:24, Felix Frank
wrote:
> Hi all,
>
> it's with great pride that I follow Alessandro with yet another plug of
> relevant literature.
>
> My first book, Puppet Essentials, is available as of right now. Check it
> out: http://bit.ly/1zoGxbW
>
> It's suitabl
Congratulations Felix !
- henrik
On 2014-30-11 15:24, Felix Frank wrote:
Hi all,
it's with great pride that I follow Alessandro with yet another plug of
relevant literature.
My first book, Puppet Essentials, is available as of right now. Check it
out: http://bit.ly/1zoGxbW
It's suitable for
thanks for the reply, is it will make puppet connection lost or something
bad happen if we use yum update ?
On Monday, December 1, 2014 10:08:38 PM UTC+8, jcbollinger wrote:
>
>
>
> On Sunday, November 30, 2014 8:57:50 PM UTC-6, fauzi.p...@gmail.com wrote:
>>
>> Can I use yum update on puppet mas
On 01/12/14 16:25, Spencer Krum wrote:
Maybe you could use the notice() or warn() functions?
Those would log server-side, wouldn't they? I want to see it on the
client console and on the Puppet report :)
--
bye
Nacho
http://cern.ch/nacho
--
You received this message because you are subs
14 matches
Mail list logo