Bug 1383733 - Provide more Information around OpenShift Platform Storage Requirements in the Planning Documenation
Summary: Provide more Information around OpenShift Platform Storage Requirements in th...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-11 15:43 UTC by Nick Schuetz
Modified: 2017-12-30 14:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-30 14:01:46 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Nick Schuetz 2016-10-11 15:43:02 UTC
Document URL: 

https://docs.openshift.com/container-platform/3.3/install_config/install/planning.html

Section Number and Name: 

Does not exist yet.

Describe the issue: 

I suggest adding more information to the planning guide around the OpenShift platform storage requirements. For instance, describe the relevance and sizing guidelines for /var/lib/openshift, /var/lib/docker and the docker-pool thin lv. 
In addition to that, I would suggest adding some information around storage requirements for the internal registry, metrics, logging storage requirements in this guide.


Suggestions for improvement: 

I constructed this statement based on the Atomic Host documentation (ref below):

The /var/lib/docker/ directory that lives on all nodes contains container images data, such as temporary data or the docker volumes. A separate Container Image Partition called docker-pool is formatted as an LVM thin pool by the docker-storage-setup service. It is used to store the container images. The space used by docker-pool is managed by the docker-storage-setup service. When you pull a container image from a registry, for example, the image takes up space on this partition. Container images are read-only. Once an image is launched as a container, all writes (except to mounted volumes or docker volumes) are stored in this Logical Volume (i.e. container logs).

Ref: https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/7/paged/getting-started-with-containers/chapter-7-managing-storage-with-docker-formatted-containers 

For the internal registry, metrics and aggregated container logging we could reference any existing documentation in the installation docs. It would also be nice to include any sizing guidelines here as well or instead of in the installation documentation.

Additional information: 

Internal Registry:
https://docs.openshift.com/container-platform/3.3/install_config/registry/deploy_registry_existing_clusters.html#storage-for-the-registry

https://docs.openshift.com/container-platform/3.3/architecture/infrastructure_components/image_registry.html

Metrics:
https://docs.openshift.com/container-platform/3.3/install_config/cluster_metrics.html#metrics-data-storage

Aggregating Container Logs:
https://docs.openshift.com/container-platform/3.3/install_config/aggregate_logging_sizing.html

Comment 1 Vikram Goyal 2017-12-30 14:01:46 UTC
This was added to the Scaling and Performance Guide in 3.7: https://docs.openshift.com/container-platform/3.7/scaling_performance/optimizing_storage.html


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