Bug 1306890 - [DOCS] [3.2] Document the scale numbers on users, pods, nodes and projects
Summary: [DOCS] [3.2] Document the scale numbers on users, pods, nodes and projects
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Deadline: 2016-03-15
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: brice
QA Contact: Jeremy Eder
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-12 02:04 UTC by Vikram Goyal
Modified: 2017-03-08 18:14 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-17 01:29:05 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Vikram Goyal 2016-02-12 02:04:23 UTC
For OpenShift Online Beta, on premise OpenShift installations - document what can a customer expect from various installation sizes.

We need to identify and document the scale numbers for users, pods, nodes and projects.

Contacts:
Jeremy Eder (QA Contact) and Tim St. Clair (CC'ed).

Likely Guide:
Possibly the Architecture or Installation Guide
https://docs.openshift.com/enterprise/3.1/architecture/index.html
https://docs.openshift.com/enterprise/3.1/install_config/index.html

Comment 3 brice 2016-05-04 00:30:03 UTC
Work has started in this PR:

https://github.com/openshift/openshift-docs/pull/1961

Comment 4 openshift-github-bot 2016-05-10 01:19:32 UTC
Commit pushed to master at https://github.com/openshift/openshift-docs

https://github.com/openshift/openshift-docs/commit/c7028a8db67ab836c61307d54a96a9a57bdef1cb
Merge pull request #1961 from bfallonf/bz1306890

Bug 1306890 : Added maximum pod and node info

Comment 5 brice 2016-05-17 01:29:05 UTC
Verified to be in the 3.2 docs:

Section 2.2.3.1 Sizing Recommendations:

https://access.redhat.com/documentation/en/openshift-enterprise/version-3.2/installation-and-configuration/#system-requirements


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