I will take a crack at this as I am working with Satellite and Puppet in the 
same environment.

First of all, the Puppet inside of Satellite is way back at version 
3.something, so many newer Puppet technical tips will not work.

About answering your question, start here:
https://docs.puppet.com/puppet/3.8/lang_node_definitions.html

A node definition or node statement is a block of Puppet code that will only be 
included in one node’s catalog. This feature allows you to assign specific 
configurations to specific nodes.

Node statements are an optional feature of Puppet. They can be replaced by or 
combined with an external node classifier, or you can eschew both and use 
conditional statements with facts to classify nodes.

Unlike more general conditional structures, node statements only match nodes by 
name. By default, the name of a node is its certname (which defaults to the 
node’s fully qualified domain name).

https://docs.puppet.com/puppet/3.8/modules_fundamentals.html#using-modules

Modules are how Puppet finds the classes and defined types it can use — it 
automatically loads any class or defined type stored in its modules. Within a 
manifest or from an external node classifier (ENC), any of these classes or 
defined types can be declared by name.

The Red Hat Satellite Puppet Guide does not really discuss setting up nodes.  
It seems to focus on how Satellite can manage the Puppet modules.

Dan White | d_e_wh...@icloud.com
------------------------------------------------
“Sometimes I think the surest sign that intelligent life exists elsewhere in the 
universe is that none of it has tried to contact us.”  (Bill Waterson: Calvin & 
Hobbes)

On Jan 18, 2017, at 03:05 PM, "warron.french" <warron.fre...@gmail.com> wrote:

Does this community support questions related to Red Hat Satellite's 
implementation of Puppet, or only PuppetLabs developed and supported products 
more generically?

I have a question about the phases of tasks that must be completed within a Red Hat 
Satellite Puppet Environment and how to get them "onto" the Puppet Client 
machines running a Puppet agent.


I have generated a module, Validated its syntax to find no errors, neither in 
the .pp nor the .erb template files, and have gone through Red Hat Satellite's 
process of creating the module archive, Uploading, Publishing and Promoting 
that module; but I can't figure out why its not getting applied to the client 
machines.  Even after a puppet run is executed!


Thanks for any help and direction anyone can provide me.
--------------------------
Warron French


--
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 the web visit 
https://groups.google.com/d/msgid/puppet-users/CAJdJdQnpQfr4Y1fOw0_pTTA2T%2Bcn0eMvHX1SHWHpUXkNX53ZVw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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 the web visit 
https://groups.google.com/d/msgid/puppet-users/b3445ec5-cf42-44c9-879d-957b9a1ac640%40me.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to