I'm not clear what the context is here. Those snippets are what's in your
YAML file? Maybe you could post the relevant code from your manifest too?
Rich
On Thu, Sep 18, 2014 at 6:19 PM, Daniel Johnson tekno...@gmail.com wrote:
Things like
require: File['somefile']
or
require:
File:
Try changing the Mdoulfile instread of the metadata file.
On 19 Sep 2014 04:35, Allen Santora allen.sant...@gmail.com wrote:
Greetings,
(puppet-server-3.5.1 on CentOS 6.4)
I'm writing my own nodejs manager in Puppet and I want to enforce a
version number
I have generated the module
Keith,
Thanks for that. Did the following:
file { /etc/cron.d/puppet:
ensure = file,
owner = root,
group = root,
mode = 0644,
content = inline_template(%= scope.function_fqdn_rand([60]) % * * * *
root /usr/bin/puppet agent --onetime --no-daemonize --no-splay\n),
}
Works fine. Cheers,
What nikolavp said is true, the metadata.json became the standard starting
from Puppet 3.6, but since you use 3.5 the Modulefile still prevails.
Off subject: any reason not to upgrade your master? I have really bad
memories of Puppet 3.5 on CentOS, whereas 3.6 fixed all my troubles. Would
also
Hi teknotus,
I don't think that would work since you can not declare a Puppet resource
in Hiera, you are limited to core types.
In your case, Puppet would interpret File['somefile'] as a string, and
File: somefile as a hash, but will never translate that to a resource.
Cheers,
Toni
--
You
Hi,
I'm searching for the best way to use parameter in multiple modules.
Example: I am declaring a variable $port in module 'server' and I need this
variable in module 'firewall' to open this port. If i have to change this
variable I actually have to change 4 Variables in 4 modules.
Is
On Thursday, September 18, 2014 5:59:56 PM UTC-5, François Lafont wrote:
Hi,
Le 18/09/2014 16:40, jcbollinger a écrit :
So, finally, is this way below a correct and good way to use the params
pattern?
-
# Example of
On Thursday, September 18, 2014 6:22:22 PM UTC-5, Jürgen Hermann wrote:
The Puppet file you pass to an apply is basically a full site.pp, so try
adding a node default {…} around your resources.
See https://github.com/jhermann/devpi-puppet/blob/master/site.pp#L31 for
an example.
No, a
On Friday, September 19, 2014 6:45:43 AM UTC-5, Antoine Cotten wrote:
Hi teknotus,
I don't think that would work since you can not declare a Puppet resource
in Hiera, you are limited to core types.
In your case, Puppet would interpret File['somefile'] as a string, and
File: somefile as
On Thu, Sep 18, 2014 at 6:19 PM, Daniel Johnson tekno...@gmail.com wrote:
Things like
require: File['somefile']
or
require:
File: somefile
both crash, and burn.
Not having a require also causes failure as it tries to do things it
can't without the prerequisite.
After hours of
Version 0.1.1 fixes the Linux build issue
--
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
Hello,
did the metadata accepted change recently? I have a module that had a
'requirements' field populated with the puppet version, but now when I try
to release a new module to the forge it complains that The requirement
'puppet' in the metadata.json specifies an invalid 'version_requirement'
Puppet 3.6.2
First, I understand that Execs try not to run multiple times if called many
times by many resources and typically wait until they've all been
collected from all resources, but I have a specific case where I need
different Execs to run in a particular order based on a set of
The order of resources in the manifest doesn't matter. Puppet will build a
graph from all resources and dependencies and executes resources from the
same level randomly.
You need something like this:
exec { start:
path=
Yes Cristian, I understand that, but the issue is less the order of the
Execs in relation to each other, but when the Execs run in relation to the
config file resource and the package resource. I need for the stop Exec
to run before the package is installed, and then the start Exec to run.
Using hiera is probably the best solution.
Regards,
El 19/09/2014 14:14, Marco Dürrwächter derse...@gmail.com escribió:
Hi,
I'm searching for the best way to use parameter in multiple modules.
Example: I am declaring a variable $port in module 'server' and I need
this variable in module
Out of curiosity, how does it compare with puppet dashboard ?
Is Puppet Dashboard really EOL ?
What's currently the best reporting open source solution for Puppet ?
Cheers
On Friday, September 12, 2014 5:19:25 PM UTC+2, Erik Dalén wrote:
A new release of Puppet Explorer is out! This release
On 11/09/14 05:49 PM, Matthaus Owens wrote:
# wget -O - https://downloads.puppetlabs.com/puppetlabs-gpg-signing-key.pub
| gpg --import
that step is not mentioned in the documentation about intalling puppet:
https://docs.puppetlabs.com/guides/install_puppet/install_debian_ubuntu.html
in fact
Hello,
I'm using puppet 3 with roles (mostly), profiles, and Hiera. I have a
profile setup (for pdxcat/collectd) to, amongst other things, hiera_array()
for values [of localports] to pass on to collectd::plugin::tcpconns.
Defining everything in hiera files works as expected. However, I would
I have a single class for every application to be installed on our
Macintosh clients. The problem I am having is in the section of the class
below. This copies files to the User Template folder so when users login
they get predefined preferences.
file { System/Library/User
Puppet Explorer and PuppetBoard are both superior to the Puppet Dashboard.
Puppet dashboard is in community support, but this list is full of people
having trouble installing it. I would highly recommend using one of the
other tools.
What the Puppet Dashboard does do that the other tools do not
Use the same approach the firewall module uses: A main class, declared at a
global level, creates/manages the folder. A defined type is used to
create/manage imdividual prefs files and is involed inside the module for the
individual app.
A basic pronciple of object-oriented code. Pull out the
Your File['Config'] - Exec['stop'] - Package['foo'] - Exec['start']
should do what you want.
Can you also try to require Exec['stop'] in your package foo?
Also, the refreshonly = true on you stop exec I don't think it matters.
You will need a notify Exec[stop] in your config for that.
On Fri,
Glad the concept is correct, but I've been playing with it and am not sure
which part of the firewall class processes the passed on code. In the
firewall/apache analogy, you use the following code.
class apache {
firewall { '100 allow http and https access':
port = [80, 443],
proto
Hello all,
I have a question about class and subclass relationships and what is/isn't
the ideal way to go about such a thing. Please bear with me as I'm still
refining my understanding of containment. Let's say I have a puppet module
which manages the install of puppet and has the following
On 2014-17-09 17:37, jcbollinger wrote:
On Tuesday, September 16, 2014 12:26:24 PM UTC-5, Juan Sierra Pons wrote:
Hi guys,
From your comments I see that there are 2 issues here the parser and
the anchor. For clarity shake I have deleted the anchor resources and
Class
It appears I'm looking for a defined type to do this.
https://docs.puppetlabs.com/learning/definedtypes.html#special-little-flowers
I'll see if I can get this to work for my purpose though this article
mentions duplicate definitions and I'm guessing I'll have the same problem.
On Friday,
TLDR summary:
1. include/require class does not provide containment.
2. anchor is just a empty resource for containment.
3. contain class provides containment without the need for anchor
4. contain may cause unnecessary relationship, so use it only when
appropriate
5. The original purpose for
28 matches
Mail list logo
