no existing nodes.pp file
17 views
Skip to first unread message
Deo Breathnu
Apr 4, 2019, 6:15:45 PM4/4/19
to Puppet Users
I am fairly new to puppet. I have a puppet master that is orchestrating the builds for three AWS autoscaling groups of Nginx reverse proxy servers. The three types are fairly similar except for some conf files.
In the main site.pp file there is a line " case $::ec2_tag_role" . So it is obvious that it seems that the logic as the configuration differences is controlled here since the 3 tags are here below the case. There is no nodes.pp file. Has anyone seen this configuration before?
Martin Alfke
Apr 5, 2019, 6:31:07 AM4/5/19
to puppet...@googlegroups.com
Hi Deo,
> On 5. Apr 2019, at 00:02, Deo Breathnu <deo.br...@gmail.com> wrote:
>
> I am fairly new to puppet. I have a puppet master that is orchestrating the builds for three AWS autoscaling groups of Nginx reverse proxy servers. The three types are fairly similar except for some conf files.
>
> In the main site.pp file there is a line " case $::ec2_tag_role" . So it is obvious that it seems that the logic as the configuration differences is controlled here since the 3 tags are here below the case. There is no nodes.pp file. Has anyone seen this configuration before?
manifests/site.pp is the main entry point for Puppet when looking for node classifications.
You can have additional files within manifests directory which get parsed by Puppet master automatically.
Nodes.pp was used by people in the past.
hth,
Martin
> On 5. Apr 2019, at 00:02, Deo Breathnu <deo.br...@gmail.com> wrote:
>
> I am fairly new to puppet. I have a puppet master that is orchestrating the builds for three AWS autoscaling groups of Nginx reverse proxy servers. The three types are fairly similar except for some conf files.
>
> In the main site.pp file there is a line " case $::ec2_tag_role" . So it is obvious that it seems that the logic as the configuration differences is controlled here since the 3 tags are here below the case. There is no nodes.pp file. Has anyone seen this configuration before?
You can have additional files within manifests directory which get parsed by Puppet master automatically.
Nodes.pp was used by people in the past.
hth,
Martin
jcbollinger
Apr 5, 2019, 9:01:44 AM4/5/19
to Puppet Users
On Thursday, April 4, 2019 at 5:15:45 PM UTC-5, Deo Breathnu wrote:
I am fairly new to puppet. I have a puppet master that is orchestrating the builds for three AWS autoscaling groups of Nginx reverse proxy servers. The three types are fairly similar except for some conf files.In the main site.pp file there is a line " case $::ec2_tag_role" . So it is obvious that it seems that the logic as the configuration differences is controlled here since the 3 tags are here below the case. There is no nodes.pp file. Has anyone seen this configuration before?
As Martin observed, use of a nodes.pp file is only a convention (an old one). That file name does not have inherent significance to Puppet. You may be getting node definitions from some other file(s), instead.
However, I suspect what you're really describing is that there aren't any node blocks at all. That is indeed a supported configuration, and one that is sometimes used. It is relatively common in conjunction with an external node classifier, but it is sometimes used even without. Whether or not there are any node blocks or any external node classification, all code that appears at top scope in the site manifest applies to all nodes.
So yes, although of course I haven't seen your exact configuration, I have seen configurations like it, and others have, too. Did you have a more specific question about it?
John
Deo Breathnu
Apr 5, 2019, 9:22:55 AM4/5/19
to Puppet Users
Deo Breathnu
Apr 5, 2019, 9:25:22 AM4/5/19
to Puppet Users
No, I am just trying to figure out how this works. Thanks for the replies.
On Friday, April 5, 2019 at 9:01:44 AM UTC-4, jcbollinger wrote:
Reply all
Reply to author
Forward
0 new messages