Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1301735

Summary: Missing Documentation on using Satellite6 as an ENC for puppet modules
Product: Red Hat Satellite Reporter: Stuart Auchterlonie <sauchter>
Component: Docs Puppet GuideAssignee: Stephen Wadeley <swadeley>
Status: CLOSED CURRENTRELEASE QA Contact: Lucie Jirakova <ljirakov>
Severity: medium Docs Contact:
Priority: high    
Version: 6.1.4CC: adahms, mburgerh, sbream, sspreitz, swadeley
Target Milestone: UnspecifiedKeywords: Documentation
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-06 20:11:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1316897    

Description Stuart Auchterlonie 2016-01-25 21:07:52 UTC
Document URL: 

There doesn't appear to be a document where we even cover this.

Section Number and Name: n/a

Describe the issue: 

When trying to use Satellite6 as an ENC (external node classifier) for puppet 
modules, the following is poorly / not at all documented.

1. Of all the areas parameters can be added, what is the order of operation such
that a parameter that is defined in multiple places, which takes precedence.

2. For smart classes/parameters what is a list of all valid matchers that can be used?

3. How to set up Hiera and if a hybrid approach between smart classes and Hiera
is used, what is the resulting order of operations to follow to determine what values take precedence over others?

4. How do I add AD/LDAP as a Hiera data source?

Comment 7 Stephen Wadeley 2017-01-03 08:29:07 UTC
(In reply to Stuart Auchterlonie from comment #0)
> Document URL: 
> 
> There doesn't appear to be a document where we even cover this.
> 
> Section Number and Name: n/a
> 
> Describe the issue: 
> 
> When trying to use Satellite6 as an ENC (external node classifier) for
> puppet 
> modules, the following is poorly / not at all documented.
> 
> 1. Of all the areas parameters can be added, what is the order of operation
> such
> that a parameter that is defined in multiple places, which takes precedence.

Hello, the section in the Host Configuration Guide describing Parameters was recently improved. See[1]. Does that answer this question of precedence? 


> 
> 2. For smart classes/parameters what is a list of all valid matchers that
> can be used?

I think it is not practical to provide a list as it depends on the host.

You can use a host attribute, host parameter, or a Puppet Fact. In that order of precedence for matching. 

It is recommend to use an attribute that is present in Facter and cannot be confused with a host attribute. 

To list available Puppet Facts navigate to Monitor → Facts. 

The procedures in the guide were recently improved to make this clearer. See [1]

> 
> 3. How to set up Hiera and if a hybrid approach between smart classes and
> Hiera
> is used, what is the resulting order of operations to follow to determine
> what values take precedence over others?

As Hiera is not part of the Foreman project I think this is out of scope for the Puppet Guide. I will mention this to the Content Strategist (whose job it is to decide what we document and where we document things).

> 
> 4. How do I add AD/LDAP as a Hiera data source?

Again, I think this is out of scope for the Puppet Guide. I will mention this to the Content Strategist.



[1] https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/host-configuration-guide/82-parameters

Comment 9 Steve Bream 2017-01-10 12:00:33 UTC
Hi Stephen,

I agree that the Hiera documentation is outside our scope. The improvements in the Host Configuration guide should address the other issues.

Thanks,
Steve

Comment 13 Stephen Wadeley 2017-03-06 20:11:34 UTC
Hello Stuart

Given comments above I cannot see what more Docs team can do with this bug.

Please re-open or raise new bugs as required.


Thank you

Comment 14 Stephen Wadeley 2017-03-07 13:01:34 UTC
Hello

On the subject of Hiera, see also:
Will Puppet Smart Classes and ENC be integrated?
https://access.redhat.com/solutions/1232033