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.
Moving to 'NEW' and the default assignee to be triaged as the schedule allows.
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