Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1076152

Summary: Add complete end-to-end examples for common deployment scenarios
Product: Red Hat Satellite 5 Reporter: Deon Ballard <dlackey>
Component: Docs Installation GuideAssignee: satellite-doc-list
Status: CLOSED WONTFIX QA Contact: satellite-doc-list
Severity: unspecified Docs Contact:
Priority: medium    
Version: 570CC: adahms, dchia, dlackey, ekere, hhutton, rdickens, sbream
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-24 00:12:18 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: 1076156    
Bug Blocks: 1018166    

Description Deon Ballard 2014-03-13 16:44:37 UTC 
The Satellite documentation needs examples that follow a common deployment scenario from beginning to end. While many of the steps are documented, they are spread over the entire documentation set; this can make the practical process of deploying a certain configuration very hard.

As a start, there are four processes which could be mapped as examples:

* Creating a build system
* Creating a patch system
* Creating a monitoring system
* Creating build, patch, and monitoring in the same system

It would also be beneficial to include environmental considerations, recommendations, or restrictions within the examples. E.g., if you are setting up a proxy system, you cannot install from the network. Also, possibly, sizing recommendations.
Comment 2 Andrew Dahms 2017-07-04 11:42:20 UTC 
Moving to 'NEW' and the default assignee to be triaged as the schedule allows.
Comment 4 Steve Bream 2017-07-18 09:39:33 UTC 
I think that the request is good and we should take it as a to-do going forward, but we can close the bug and make this a docs improvement item as part of our plan. 

Given the age of the bug, I think it makes sense to start fresh with 6.3 for this work.

Thanks,
Steve