Bug 1489220 - [RFE] [6.3] Document how to configure gofer-less host management
Summary: [RFE] [6.3] Document how to configure gofer-less host management
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Managing Hosts
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: csherrar
QA Contact: Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks: 1486095
TreeView+ depends on / blocked
 
Reported: 2017-09-07 02:06 UTC by Andrew Dahms
Modified: 2019-09-26 16:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-29 05:27:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Andrew Dahms 2017-09-07 02:06:13 UTC
A new section must be added as an appendix in the Host Configuration Guide that outlines the following -

* A brief introduction to gofer-less host management, and what benefit it
  provides to users
* A section on prerequisites (package version that must be installed, that
  remote execution must already be set up on hosts
* A note on the limitation that Hammer does not provide this yet, and an
  example of how to work around this
* A section on how to make gofer-less host management the system default

Comment 1 Andrew Dahms 2017-09-07 02:07:39 UTC
Assigning to Clifton for review.

Clifton - the following article provides most of the required details -

https://access.redhat.com/articles/3154811

We cannot use the text as is, but the basic steps and details required to create our own content can mostly be found here. It would be nice to have a Satellite installation to try some of these steps as well, although maybe setting up ReX for this purpose might be too much at this stage.

Comment 5 Andrew Dahms 2017-09-18 23:12:34 UTC
Hi Clifton,

Thank you for your needinfo request.

I have now changed the component to 'Host Configuration Guide' so that it matches with the description. My apologies for the confusion.

Ideally, the changes should be made first on the 'master' branch and then back-ported to the '6.2' branch after the bug has been verified, but we can always bring the changes forward from '6.2' to 'master' if needed.

The feature itself was completed as part of the 6.2.11 release, and was initially documented as a KBase article with the intent of having the content officially added to the documentation for the 6.3 release.

Since we now have some more bandwidth to address requests like this now, I have brought this up so that we can include it in the 6.2 documentation when it is ready, with a target release of 6.2.12 if possible.

I hope that provides a bit more clarification, but I can see how all the flags and milestones can be a bit confusing without more clarification. I'll keep that in mind for future bugs like this and add more detail or set the flags more clearly.

Let me know if there is anything else you need.

Kind regards,

Andrew

Comment 15 Andrew Dahms 2017-09-29 05:27:23 UTC
This content will be published with the next release for Red Hat Satellite 6.3

Closing.

Comment 16 Andrew Dahms 2017-12-11 01:47:06 UTC
Updating the target milestone to reflect the time frame in which this work was completed.

Comment 17 Andrew Dahms 2018-01-15 01:10:14 UTC
Updating the component and doc type.


Note You need to log in before you can comment on or make changes to this bug.