Hi,
On 2 August 2017 at 16:15, RG wrote:
> I am trying to write my first puppet module.
>
> I need to be able to pull a value from a custom fact and write a value in
> a config file based on a value in the fact.
>
> Can I do and "if-then" statement like in bash?
>
Yes! See https://docs.puppet.
I am trying to write my first puppet module.
I need to be able to pull a value from a custom fact and write a value in a
config file based on a value in the fact.
Can I do and "if-then" statement like in bash?
Thanks for any guidance.
--
You received this message because you are subscribed
Hello I am a newbie with puppet
I am trying to take a module I cobbled together to run a script
class mymodule::myscript {
file {
'myscript':
ensure => 'file',
source => 'puppet:///modules/mymodule/myscript.sh',
path => '/usr/local/bin/myscript.sh',
owner => 'root'
I'd really recommend that second edition for Pro Puppet for you if you are
starting and want to learn to Puppet the right way. If I remember right
doing Apache vhosts is an example they use in the book even.
The problem is that there are certain types of tasks that it's going to be
able to do with
My rationale for it is exactly that. Focus on learning how Puppet itself
works, and then learn the add-ons after the fact. On top of that, Hiera
isn't a requirement for use - you can just as easily use something like
Foreman (which, from what I've seen of it so far looks really good.) But
even in m
Yeah I think part of the difficulty is that there are multiple ways to do
things and not everyone agrees on what is the best way. There are some
groups that have put their entire Puppet code base on GitHub. I bet you
could find some by Googling or searching on GitHub. That's one of the nice
things
On 6/23/2014 4:05 AM, Ben Ruset wrote:
Ah, okay this makes more sense for me. So I know that I can stick this
in the same file with the node definitions, but there's got to be a
better place for it to go. Where would the "proper" place be for it to go?
Many thanks for your responses. They've bee
I think the good form these days is to create generic modules and keep the
site-specific data in hiera (not that I'm good at keeping up with fashion).
Once you've gone through the Learning Puppet series of docs you'll probably
have more context to the roles/profiles pattern and other links.
htt
Well, so I didn't know if it was "good form" to modify modules to hold
site-specific configuration items.
I think part of my frustration is that I haven't been able to find a doc,
or maybe one doesn't exist, that shows what a decent "production" Puppet
environment might look like. I think it'd be
Perhaps read about modules? if you specify a class name (apache,
apache::vhosts) that class is automatically loaded from the relevant module.
Just like putting stuff directly in node definitions has correctly gone out of
style, so has defining classes/defines outside of modules.
http://docs.pup
Ah, okay this makes more sense for me. So I know that I can stick this in
the same file with the node definitions, but there's got to be a better
place for it to go. Where would the "proper" place be for it to go?
Many thanks for your responses. They've been very helpful.
On Sun, Jun 22, 2014 at
Before hiera you might have a define specifying what a vhost is, and then have
a class with the defines all listed. You would include that class in your node
definition, ensuring that this class was applied after the basic apache class.
Sometimes people would put the defines right in the node, b
Thanks for the answer. I grasp the fundamentals of what you're saying, but
right now I'm a little leery of delving into Hiera when I don't really know
the fundamentals of Puppet itself yet. My reading through those docs would
only confuse me more. (Not that those docs are probably not good - it'
Short version: read up on hiera, data bindings, and create_resources.
Details:
It sounds like you might want to look into hiera (baked into puppet 3 and
higher) and the create_resources function. Specifically that you list the
variable portions of things in your puppet configuration in hiera, a
Alright, this is definitely a Puppet 101 question, and I am sure that the
Puppet docs have an answer for this and I am just dense and can't find it.
I'm trying to teach myself Puppet, with the goal of managing the VPS I run
with it. Additionally, when I get a better grasp on things, I want to
Are you sure your client is using 3.x? This error typically crops up with older
facter versions which don't define the osfamily variable.
To test, run "facter" on your client and see if osfamily is listed.
Sent from my iPhone
On 01 Mar 2013, at 01:47, "Alejandro Betancourt"
mailto:alejandro.be
Hi
I am new in Puppet and i have one error when i test Postgresql module in
infrastructure mode.
I'm using Puppet 3.1.0 in Debian squeeze or 6.0.7
i tape the next command puppetd -t -v and this is the error
info: Retrieving plugin
info: Loading facts in pe_version
info: Loading facts in postg
On Tue, Jul 10, 2012 at 4:18 PM, Marshie8 wrote:
>
> On Tuesday, July 10, 2012 4:12:42 PM UTC+1, Matthew Burgess wrote:
>>
>> Then it looks like you're running puppet under its default webrick
>> configuration. How do you start your puppetmaster? Via the init
>> script?
>
>
> Yes, it's running a
On Tuesday, July 10, 2012 4:12:42 PM UTC+1, Matthew Burgess wrote:
>
> Then it looks like you're running puppet under its default webrick
> configuration. How do you start your puppetmaster? Via the init
> script?
Yes, it's running as the puppet user:
server-1:~ # ps -ef |grep 'puppetmast
On Tue, Jul 10, 2012 at 3:57 PM, Marshie8 wrote:
>
>
> On Tuesday, July 10, 2012 3:26:47 PM UTC+1, Andreas Paul wrote:
>>
>> Of course the file you want to deploy with puppet must be readable by the
>> puppetmaster.
>> Do you use Apache Passenger, Nginx or webbrick?
>>
>> If you use Apache Passeng
On Tuesday, July 10, 2012 3:26:47 PM UTC+1, Andreas Paul wrote:
>
> Of course the file you want to deploy with puppet must be readable by the
> puppetmaster.
> Do you use Apache Passenger, Nginx or webbrick?
>
> If you use Apache Passenger:
>
> The file /etc/puppet/files/server_file must be read
Of course the file you want to deploy with puppet must be readable by the
puppetmaster.
Do you use Apache Passenger, Nginx or webbrick?
If you use Apache Passenger:
The file /etc/puppet/files/server_file must be readable by the user, who
owns the /etc/puppet/rack/config.ru file.
On Tuesday, Ju
On Tuesday, July 10, 2012 11:33:38 AM UTC+1, Matthew Burgess wrote:
>
> My suggestion would be to take a copy of the file as it is on your
> server now, and place it under the control of puppet. The following
> simple manifest should do what you're after:
>
> class server_file {
>
> file
Hi Marshie8
can you tied filebucket
#Filebucket config
filebucket { main:
server => "puppet"
}
-Ganesh.
Did I learn something today? If not, I wasted it.
On Tue, Jul 10, 2012 at 4:55 AM, Marshie8 wrote:
> Hi,
>
> I am new to Puppet.
>
> I need to monitor a file for changes on a serve
On Tue, Jul 10, 2012 at 9:55 AM, Marshie8 wrote:
> Hi,
>
> I am new to Puppet.
>
> I need to monitor a file for changes on a server and if it does, copy it
> immediately to the clients. But it has permissions 640, and must retain
> these.
>
> Can anyone suggest a manifest for this?
Hi,
The idea
Hi,
I am new to Puppet.
I need to monitor a file for changes on a server and if it does, copy it
immediately to the clients. But it has permissions 640, and must retain
these.
Can anyone suggest a manifest for this?
Thanks a lot.
M
--
You received this message because you are subscri
On Friday, September 2, 2011 at 10:46 AM, Mitch Anderson wrote:
> I'm just starting out with puppet, and I'm trying to get one of the
> new environments I'm managing using puppet. The site is apache/php,
> so I've been trying to use one of the prewritten apache modules...
> without any luck... so I
I'm just starting out with puppet, and I'm trying to get one of the
new environments I'm managing using puppet. The site is apache/php,
so I've been trying to use one of the prewritten apache modules...
without any luck... so I've ended up taking snippits of a few
different ones... anyway, I'm get
I ended up having to use $hostname
not braces, nothing, weird
On Fri, Aug 5, 2011 at 12:54 AM, Denmat wrote:
> Hi,
>
> You can use facts supplied by facter to do the following (assuming you want
> to do this for host with hostname host1).
>
> > puppet:///files/configuration_files/${hostname}/m
Hi,
You can use facts supplied by facter to do the following (assuming you want to
do this for host with hostname host1).
> puppet:///files/configuration_files/${hostname}/mystuff/test.sh',
You can also assign variables easily like:
$host = 'host1'
And then use $host in your source statement.
Hi
I have a very simple manifest
file { '/mystuff/test.sh':
ensure => file,
mode => 0755,
source => 'puppet:///files/configuration_files/host1/mystuff/
test.sh',
}
I would like to define the "host1" as a variable while fetching from
the puppetmaster
How can I do that?
--
Hi ,
just starting off with Puppet on Macs. initially we are planning for a
small group of machines. If successfull we plan to span it to entire
environment in a phased manner.
I have a couple of newbie questions.
Do i have to use custom script to create and maintain user/group
accounts as far
32 matches
Mail list logo
