Skip to content

Bug 1281651, added sizing guidelines for etcd service nodes #3448

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 10, 2017
Merged

Bug 1281651, added sizing guidelines for etcd service nodes #3448

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions install_config/install/prerequisites.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ ifdef::openshift-enterprise[]
* Base OS: RHEL 7.3 or later with "Minimal" installation option, or RHEL Atomic
Host 7.3.2 or later. RHEL 7.2 is also supported using Docker 1.12 and its dependencies.
endif::[]
* NetworkManager 1.0 or later
* NetworkManager 1.0 or later.
* 1 vCPU.
* Minimum 8 GB RAM.
* Minimum 15 GB hard disk space for the file system containing *_/var/_*.
Expand All @@ -79,7 +79,13 @@ back end; see xref:configuring-docker-storage[Configuring Docker Storage]
below.

|External etcd Nodes
|Minimum 20 GB hard disk space for etcd data.
a|* Minimum 20 GB hard disk space for etcd data.
* Consult
link:https://github.com/coreos/etcd/blob/master/Documentation/op-guide/hardware.md#hardware-recommendations[Hardware
Recommendations] to properly size your etcd nodes.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The information in this link is great, however I don't think it looks good for us to point customers at github wiki page to define such an important concept.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@timothysc thoughts?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@timothysc Please see this comment from @sferich888 . How should we move forward? Thanks!

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't thinks it's a concern at this time. My 0th concern is getting the information in the hands of those who need it, and it staying current, and this is the easiest way to do that.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to merge what we have. We can continue to iterate on this as it evolves.

* Currently, {product-title} stores image metadata in etcd. You must periodically
prune old images. If you are planning to leverage a large number of images,
place etcd on machines with large amounts of memory and fast SSD drives.
|===

[IMPORTANT]
Expand Down