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.

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

Conversation

ahardin-rh
Copy link
Contributor

@ahardin-rh ahardin-rh added this to the Future Release milestone Jan 5, 2017
@ahardin-rh ahardin-rh self-assigned this Jan 5, 2017
@ahardin-rh
Copy link
Contributor Author

ahardin-rh commented Jan 5, 2017

@timothysc @adellape @sferich888 PTAL

@ahardin-rh ahardin-rh mentioned this pull request Jan 5, 2017
@timothysc
Copy link

lgtm, but ideally I'd like @sferich888 to once over as well.

Copy link
Contributor

@adellape adellape left a comment

Choose a reason for hiding this comment

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

LGTM

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!

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.

@ahardin-rh ahardin-rh merged commit d35148f into openshift:master Jan 10, 2017
@ahardin-rh
Copy link
Contributor Author

ahardin-rh commented Jan 10, 2017

[rev_history]
|xref:../install_config/install/prerequisites.adoc#install-config-install-prerequisites[Installing a Cluster -> Prerequisites]
|Added sizing guidelines for etcd service nodes within the xref:../install_config/install/prerequisites.adoc#hardware[Minimum Hardware Requirements] table.
%

@vikram-redhat vikram-redhat modified the milestones: Future Release, Staging, OCP 3.4 GA Jan 16, 2017
@ahardin-rh ahardin-rh deleted the etcd-hardware-recommendations branch November 9, 2017 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update etcd prereqs.
5 participants