Puppet Community

Guys I need help in puppet file resource type.

what kind of attribute are you thinking of?

i have one template file and I want to add that in a single server.

In template there are very slight change.

okay. did you already write some code? which issue do you have?

Like we have below two file resource.
```  file {"/opt/solr/members/conf/data-config.xml":
    ensure  =&gt; present,
    owner   =&gt; 'solr',
    group   =&gt; 'solr',
    mode    =&gt; '0644',
    content =&gt; template('solr8/data-config_members.erb')
  }
  file {"/opt/solr/offices/conf/data-config.xml":
    ensure  =&gt; present,
    owner   =&gt; 'solr',
    group   =&gt; 'solr',
    mode    =&gt; '0644',
    content =&gt; template('solr8/data-config_offices.erb')
  }```
Both are generating same file on the server but using different template.

Change between the template file is just the name of solr core.

The problem is i can not use some custom attribute in file resource type to use the resource type in puppet template to convert it to a single file

mhm sorry, I don't quite understand the problem

you want to create two files based on the same template?

like
```  file {"/opt/solr/offices/conf/data-config.xml":
    ensure  =&gt; present,
    owner   =&gt; 'solr',
    group   =&gt; 'solr',
    mode    =&gt; '0644',
    core    =&gt; "offices",
    content =&gt; template('solr8/data-config_offices.erb')
  }```
So then I can use below:-
```&lt;% if @core  == /offices/ %&gt;
        &lt;str name="masterUrl"&gt;<http://localhost:8983/solr/offices/replication>&lt;/str&gt;
&lt;% end %&gt;```


in erb, you can access puppet variables. you don't need to explicitly pass them

<https://puppet.com/docs/puppet/6/lang_template_erb.html>

That puppet variable i want to define in the resource file

Can you provide me example which is getting created on a single server by different name and we have to use same variable in template?

why do you have to use the same variable?

use one variable in one template and another variable for the other template

If I can use different template file then I will just create normal files without template.

I have not used that before. I will try to do that.

Hello alls ! is there any french puppet user here ? :slightly_smiling_face:

OMG i love u :slightly_smiling_face: thanks

I think the last activity is a wizz :trollface:

Damn, in joy I didn't even look at the timestamps...

2x3-acadiana-flag-image__92103 copy.jpg

I’m Cajun, but that’s not the same.  :smile:

:slightly_smiling_face: , not easy for me to speak/writte english so i've check if there was some frenchs :slightly_smiling_face:

i'm newbe on puppet and for my organization we what to use the puppet api to sign certificate

MyFrench is both bad and ancient.  :smile:  It’s like King Louis XII era French

I understood "je suis un noob sur puppet" though! :slightly_smiling_face:

Does the Academie Francaise not have an 'approved' word for you to use?! :smile:

Yeah, something tells me my 17th century French won’t be of help to you.  :smile:

Hello, i'm running a puppet server with arround 500 agents, and I have load issue on the server, and this seems to lead to agent delays on running

currently I have configure puppet agent to runinterval = 1800, how dioes the agent behave ?

currently I have configure puppet agent to runinterval = 1800

here is the config :
splay = false
splaylimit = 1800

I don't know this parameter, what is it doing ?

it makes sure there is a random delay between agent start and agent applying catalog

so if you restart 500 servers at once, they will not try to pull catalog at once

on Windows it's a mess. on Unix it is added once, sequential runs happens after `runinterval`

but it's random on windows too, so, it's good to enable anyway

Ok, so I might need to restart all puppet agent on all servers to get effect

nope, agent re-applies changes after config is changed

and configure max-queued-requests in puppetserver

I know I'm suing out of date puppet 5, still need to find time to upgrade !

<https://www.estcequonmetenprodaujourdhui.info/|https://www.estcequonmetenprodaujourdhui.info/>

DeepinScreenshot_Alacritty_20220722114815.png

DeepinScreenshot_Alacritty_20220722114259.png

It says compiled catalog for mezzanotte-00 but I need it to compile for mezzanotte-01

`puppet apply` is meant for compiling *and applying* a catalog locally.

You can’t specify a remote target. That’s not what the `puppet apply` command is for.

Maybe you meant to run `puppet agent -t` on your agent?
That command is meant to be run from remote agents, and they’ll ask the master to compile a catalog and send it back, then they’ll apply that catalog to themselves.

Ah ok, is there a way I can apply a catalog to all agents from the master?

Puppet operates in a “pull” model, where all the agents regularly run Puppet and request their catalog from the master.

The standard way of doing what you want is by setting up the puppet service, a cron job, or a systemd timer to run the Puppet agent on a regular interval.
By default, installing the `puppet-agent` package also adds the `puppet` service, which has a default run interval of 30 minutes. It’s not started by default, so you’d just need to start it if you want Puppet runs to happen automatically.

So how do I give a catalog from the master server so the agents can get their catalog?

Like do I have to run a command or do I have to place it in a specific directory?

And the way you assign Puppet code to an agent is through a process called “classification”.
Classification determines what ends up in an agent’s catalog when it requests it.

Classification can be done a few ways, but the simplest way is through `node` definitions: <https://puppet.com/docs/puppet/7/lang_node_definitions.html>

&gt; Like do I have to run a command or do I have to place it in a specific directory?
You don’t “give” a catalog. Instead, you write `node` definitions that declare some Puppet code. And when the agent requests a catalog, the master compiles all the code in a node’s `node` definition into a catalog and delivers it to the agent.

Node definitions get defined in `.pp` files in what’s known as “the main manifests directory”, which by default is `/etc/puppetlabs/code/environments/production/manifests/`.
And standard convention is to start with one main manifest called `site.pp`.

So that’d be on your Puppet master at `/etc/puppetlabs/code/environments/production/manifests/site.pp`.

```# Example of /etc/puppetlabs/code/environments/production/manifests/site.pp

node 'fqdn.of.a.specific.node' {
  notify { 'hello':
    message =&gt; 'this is a specific match for one host',
  }
}

node /foo/ {
  notify { 'hello':
    message =&gt; 'this is a regex match for possibly multiple hosts',
  }
}

node default {
  notify { 'hello':
    message =&gt; 'This is a notify in the default node definition',
  }
}```
That doc I linked explains more of this in detail, but the basic idea is that you can create `node` definitiosn that match a specific host, match hosts via regex, or match all nodes that don’t have a more specific match (the `default`).

from there, I recommend looking into the roles and profiles method: <https://puppet.com/docs/pe/2019.8/osp/the_roles_and_profiles_method.html> which will help you organize everything you are doing over time.  I would also look at using puppet forge modules to help take the load off of what you do yourself (if this is all about learning, I'd keep doing it myself though)

My friend that works at Apple still uses a defined type and pumps the password into an exec that just runs /usr/bin/dscl . -passwd /Users/username