Skip to content
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

`server` v `cluster` semantics unclear to new user / "Getting Started" under-discoverable #149

Closed
donaldguy opened this Issue Mar 17, 2015 · 1 comment

Comments

Projects
None yet
2 participants
@donaldguy
Copy link

commented Mar 17, 2015

As I explained at length in #135 , I shot myself in the foot by missing the Getting Started section. I saw Usage, it only mentioned chef-provisioning which I didn't want to use (cause we autoscale) and by the time I was reading LWRP definitions, I assumed all that would follow was more of that (which I would look at more closely once I had a cluster running) and perhaps a "contributing" section.

Additionally, in the process of debugging I got as far as setting bootstrap_expect manually and finding that it wasn't getting written to my config. This is because I was using server rather than cluster for my service mode. I didn't understand the difference on account of being unaware of the getting started section.

As of 0.9.0, a user will likely figure out the semantics by the time they get a cluster working, but once Atlas autojoin is merged the failure to set bootstrap_expect with server is likely to confuse more users. (since Atlas will let consul members return correctly - but no leader will be elected).

@johnbellone

This comment has been minimized.

Copy link
Contributor

commented Jun 16, 2015

I am closing this out because of impeding #126 landing on master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.