santerikainulainen/ansible-role-elasticsearch
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

reset to elastic/master to work around rebase conflict

Browse source
This commit is contained in:
Jakob Reiter 2015-10-19 14:42:27 +02:00
parent bef38dfad0
commit e889b41b7c
1 changed files with 16 additions and 72 deletions
Download patch file Download diff file Expand all files Collapse all files

88
README.md
View file

@ -38,10 +38,10 @@ hosts: my_host
roles: roles:
- elasticsearch - elasticsearch
vars: vars:
java_debian: java_packages:
- "openjdk-7-jre-headless" - "oracle-java7-installer"
es_major_version: 1.7 es_major_version: 1.4
es_version: 1.7.0 es_version: 1.4.4
es_start_service: false es_start_service: false
es_plugins_reinstall: false es_plugins_reinstall: false
es_plugins: es_plugins:
@ -72,75 +72,19 @@ ansible-playbook -i hosts ./your-playbook.yml
## Configuration ## Configuration
You can add the role without any customisation and it will by default install Java and Elasticsearch, without any plugins. You can add the role without any customisation and it will by default install Java and Elasticsearch, without any plugins.
#### Description of the variables available. Following variables affect the versions installed:
```es_major_version``` (e.g. `1.7` ) * ```es_major_version``` (e.g. "1.5" )
* ```es_version``` (e.g. "1.5.2")
Which major version to use. This is also used to define which the repository is used. * ```es_start_service``` (true (default) or false)
* ```es_plugins_reinstall``` (true or false (default) )
```es_version``` (e.g. `1.7.0`) * ```es_plugins``` (an array of plugin definitons e.g.:
Which minor version to use.
```es_start_service``` (true (default) or false)
Should elasticsearch be started after installation?
```es_use_repository``` (true (default) or false )
Should elasticsearch be installed from a repository or from a url download. If false package will be downloaded from https://download.elastic.co/elasticsearch/elasticsearch/elasticsearch.... You can also specify `es_custom_package_url` with a url to a custom package.
```es_version_lock``` (true or false (default))
This will lock the elasticsearch version using `yum versionlock`. Only available on RHEL/CentOS. For Debian/Ubuntu see `apt pinning` below.
```es_scripts``` (true or false (default))
If true you need to supply a files/scripts/ folder with your scripts, inside the role directory. The folder and all files will be copied to `/etc/elasticsearch/scripts`. You can also provide a scripts/ folder at toplevel of your playbook.
```es_plugins_reinstall``` (true or false (default) )
Schould plugins be reinstalled?
```es_plugins``` (an array of plugin definitons e.g.:)
``` ```
es_plugins: es_plugins:
- plugin: elasticsearch-cloud-aws - plugin: elasticsearch-cloud-aws
version: 2.5.0 version: 2.5.0
``` ```
`java_debian` * ```java_repos``` (an array of repositories to be added to allow java to be installed)
* ```java_packages``` (an array of packages to be installed to get Java installed)
name of the java debian package to use (e.g. `openjdk-7-jre-headless`)
`java_rhel`
name of the java rhel package to use (e.g. `java-1.8.0-openjdk.x86_64`)
## apt pinning
apt pinning is possible using an external role like https://github.com/debops/ansible-apt_preferences.
To use this, add it as another role e.g.
```
cd /my/repos/
git clone git@github.com:debops/ansible-apt_preferences.git
cd /my/ansible/playbook
mkdir -p roles
ln -s /my/repos/ansible-apt_preferences ./roles/apt_preferences
```
then add something like this to your playook:
```
roles:
- apt_preferences
- elasticsearch
vars:
...
apt_preferences_list:
- package: elasticsearch
version: 1.7.0
...
```