Bug 1286876 - Explanation of Capsule Server scaling is very confusing and seemingly contradictory
Explanation of Capsule Server scaling is very confusing and seemingly contrad...
Status: NEW
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Docs Install Guide (Show other bugs)
6.1.0
Unspecified Unspecified
medium Severity medium (vote)
: GA
: 6.2
Assigned To: satellite-doc-list
satellite-doc-list
:
: 1286878 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-30 20:11 EST by Russell Dickenson
Modified: 2016-11-30 01:52 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Russell Dickenson 2015-11-30 20:11:06 EST
Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html-single/Installation_Guide/index.html#sect-Red_Hat_Satellite-Installation_Guide-Installing_Red_Hat_Satellite_Capsule_Server-Red_Hat_Satellite_Capsule_Server_Scalability

Section Number and Name: 7.1. RED HAT SATELLITE CAPSULE SERVER SCALABILITY

Describe the issue: The numerical data presented in the entire section, and accompanying text, is confusing and seemingly contradictory. For example, it states "The Capsule Server has a concurrency limitations of 100 concurrent puppet agents running at any single point in time. Running more than 100 concurrent puppet agents will result in a 503 HTTP error." Later in the same paragraph it states "...a Capsule Server with four CPUs can expect a maximum of 1250-1600 puppet clients with a moderate workload of 10 puppet classes assigned to each puppet client."

Suggestions for improvement:

Restructure the text and numerical data so that it is clear and easily understood. This will require SME assistance as it's critical the data is correct.
Comment 2 Russell Dickenson 2015-11-30 20:59:47 EST
*** Bug 1286878 has been marked as a duplicate of this bug. ***
Comment 3 jnikolak 2015-11-30 22:38:59 EST
i think we need to find out the passenger limits for customer running large environments

Current limit is set to 100.

passenger_max_request_queue_size

Syntax	passenger_max_request_queue_size integer;
Default	passenger_max_request_queue_size 100;

Then have this figure adjusted based on cpu/memory/hosts requirements


I can see two sections, that this information needs to be updated on.
In installation doc
--> 7.1 and 1.4.7

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