Bug 1188133

Description of problem:
What I miss in the documentation is more sections on how to best use the different components together. I experience users (sys admins) often get lost because of the sheer amount of concepts that are brought together in this product. What are the best practices. Describe sample use cases (For example: DEV-QA-PROD). Write out how all different aspect interlock and work together. When to best use compiste content views? When not? How to model your host groups, host collections, etc, in combination with you activation keys, conent views, life cycle envrionment? I see a lot of mistakes happen when using Satellite 6 for the first time. Some call this "best practices", other call this "work flows" and some call is "patterns". You could even think about setting it up as a "cook book". Describe, for example, an imaginary IT shop, with a typical DEV-QA-PROD staging setup or some variation on that, and multiple business apps that need to be managed. Add a mixtures of external third party yum repo's and internal dev shops, some of who deliver RPM's and Puppet modules, some don't. Then describe how to set this all up in Satellite. 

Version-Release number of selected component (if applicable):


How reproducible:
Give a sysadmin Satellite (without any prior knowledge of the product), let him first read the docs, and then let him use it. Observe what happens.

Steps to Reproduce:
1.
2.
3.

Actual results:
Much trail and error happening 

Expected results:
Get it set up correctly in one go

Additional info:


Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information: