Allow override of data, log and naming configs

* Allow override of data directory
* Allow override of log directory
* Allow specification of cluster name
* Allow specification of node name, default to hostname
Ok valid.

Should we have an issue to synchronize such changes for next big major revision upgrade?
Your thoughts?


Sent from my iPhone

> On 19 Nov 2014, at 12:15, Mike Pountney <notifications@github.com> wrote:
> 
> In elasticsearch/map.jinja:
> 
> > @@ -1,6 +1,10 @@
> >  {% set elasticsearch = salt['grains.filter_by']({
> >      'Debian': {
> >          'bind': '0.0.0.0',
> > +        'data_path': '/var/lib/elasticsearch',
> At the moment, the default should remain the same as it is in all the ES deployments. There is no reason to move it to /data until /data is a dedicated LV.
> 
> If I change it now, it makes for a really horrid migration to this version of the formula.
> 
> —
> Reply to this email directly or view it on GitHub.
>