Skip to content
This repository has been archived by the owner on Dec 27, 2022. It is now read-only.

Add example of role in json #189

Closed
holms opened this issue Nov 29, 2013 · 4 comments
Closed

Add example of role in json #189

holms opened this issue Nov 29, 2013 · 4 comments

Comments

@holms
Copy link
Contributor

holms commented Nov 29, 2013

Can we please add example of logstash_server, logstash_client, and elasticsearch_server roles into readme file?
Currently you have only ruby code which is not even a role, and yet you expect to have those 3 roles in roles/ directory.

This is a node template which is specified in readme

name "logstash_server"
description "Attributes and run_lists specific to FAO's logstash instance"
default_attributes(
  :logstash => {
    :server => {
      :enable_embedded_es => false,
      :inputs => [
        :amqp => {
          :type => "all",
          :host => "127.0.0.1",
          :exchange => "rawlogs",
          :name => "rawlogs_consumer"
        }
]}})

we need some example of roles if you expect them.. not nodes, would be nice to have three of them. logstash_client.json, logstash_server.json. elasticsearch_server.json (or else kibana won't work out-of-the-box)

@Rockstar04
Copy link

I would love to see more examples in json as well

@paulczar
Copy link
Collaborator

paulczar commented Dec 4, 2013

I think we should keep the examples in the README very basic and then maybe use the wiki section to create in-depth examples.

@holms
Copy link
Contributor Author

holms commented Dec 4, 2013

Great idea about wiki 👍 I'd like to contribute my roles in there, would be also nice to polish them if something is wrong. Although my roles are still not finished. Cause I was struggling with all these issues, because of which I couldn't setup everything out-of-the-box.

@paulczar
Copy link
Collaborator

Closing out due to inactivity.

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

No branches or pull requests

3 participants