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

Get rid of distinction between cluster and single #135

Closed
martinb3 opened this issue Apr 30, 2015 · 1 comment · Fixed by #141
Closed

Get rid of distinction between cluster and single #135

martinb3 opened this issue Apr 30, 2015 · 1 comment · Fixed by #141
Assignees

Comments

@martinb3
Copy link
Contributor

Most people assumed single meant a single server, not a self-contained test box that doesn't accept external logstash data. We should just assume ::default is clustering, and not have a single.

martinb3 added a commit that referenced this issue May 1, 2015
- Fixes #135, stop making a distinction between a cluster install vs. a single all-in-one install without any agent.
- Merge default and cluster and single recipes. Default is now a clustered elkstack.
- Tags and search/discovery all operate off 'elkstack' tag. There is no more 'elkstack_cluster' tag.
- Fixed some of the rspec/chefspec unit tests as well.
martinb3 added a commit that referenced this issue May 1, 2015
- Fixes #135, stop making a distinction between a cluster install vs. a single all-in-one install without any agent.
- Merge default and cluster and single recipes. Default is now a clustered elkstack.
- Tags and search/discovery all operate off 'elkstack' tag. There is no more 'elkstack_cluster' tag.
- Fixed some of the rspec/chefspec unit tests as well.
@martinb3 martinb3 self-assigned this May 1, 2015
@gsaslis
Copy link

gsaslis commented Sep 10, 2016

wow, yes, I also assumed the same... : )

Docs in README.md haven't really been updated to reflect this change (it still talks about single vs. cluster)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants