You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix when condition for es_ssl_certificate_authority
7.5.0 - 2019/12/09
7.5.0 as default version
6.8.5 as 6.x tested version
Breaking changes
Removing the MAX_THREAD settings
Ansible-elasticsearch 7.5.0 is removing the option to customize the maximum number of threads the process can start in #637.
We discovered that this option wasn't working anymore since multi-instance support removal in ansible-elasticsearch 7.1.1.
This option will be added back in a following release if it's still relevant regarding latest Elasticsearch evolutions.
Changes about configuration files
Ansible-elasticsearch 7.5.0 is updating the configuration files provided by this role in #637 which contained some otions deprecated in 6.x and 7.x:
/etc/default/elasticsearch|/etc/sysconfig/elasticsearch: the new template reflect the configuration file provided by Elasticsearch >= 6.x, the parameter we removed were already not used in 6.x and 7.x
/etc/elasticsearch/jvm.options: the new template reflect the configuration files provided by Elasticsearch >= 6.x
/etc/elasticsearch/log4j2.properties:
We removed log4j2.properties.j2 template from this Ansible role as it was a static file not bringing any customization specific to some ansible variable.
Deployment of this Ansible role on new servers will get the default log4j2.properties provided by Elastisearch without any override.
WARNING: For upgrade scenarios where this file was already managed by previous versions of ansible-elasticsearch, this file will become unmanaged and won't be updated by default. If you wish to update it to 7.5 version, you can retrieve it here and use this file with es_config_log4j2 Ansible variable (see below).
How to override configuration files provided by ansible-elasticsearch?
You can now override the configuration files with your own versions by using the following Ansible variables:
es_config_default: "elasticsearch.j2": replace elasticsearch.j2 by your own template to use a custom /etc/default/elasticsearch|/etc/sysconfig/elasticsearch configuration file
es_config_jvm: "jvm.options.j2": replace jvm.options.j2 by your own template to use a custom /etc/elasticsearch/jvm.options configuration file
es_config_log4j2: "": set this variable to the path of your own template to use a custom /etc/elasticsearch/log4j2.properties configuration file
SSL/TLS Support
Ansible-elasticsearch is now supporting SSL/TLS encryption. Please refer to X-Pack Security SSL/TLS to configure it.
Starting with ansible-elasticsearch:7.1.1, installing more than one instance of Elasticsearch on the same host is no longer supported.
Configuration, datas, logs and PID directories are now using standard paths like in the official Elasticsearch packages.
If you use only one instance but want to upgrade from an older ansible-elasticsearch version, follow upgrade procedure
If you install more than one instance of Elasticsearch on the same host (with different ports, directory and config files), do not update to ansible-elasticsearch >= 7.1.1, please follow this workaround instead.
You can now using basic authentication by overriding es_api_basic_auth_username and es_api_basic_auth_password variables without providing a license file.
Features
7.1.1 as default Elasticsearch version
#539 and #542 - @grzegorznowak - Make ansible role compatible with ansible check mode
#558 - @jmlrt - Add support for Elasticsearch 7.x, remove 5.x support and update tests
#560 - @jmlrt - Use default xpack features and remove system_key deprecated feature
#562 - @hamishforbes - Allow to customize instance suffix
#526 - @Fra-nk - Allow not installing Elasticsearch deb repository key
#527 - @katsukamaru - Execute java version check in check mode
6.5.1.1 - 2018/11/27
Fixes
#516 - @Crazybus - Only attempt to copy the old users file if it actually exists
6.5.1 - 2018/11/26
Features
6.5.1 as default Elasticsearch version
Fixes
#487 - @lazouz - Disable check mode to make install plugins idempotent
#501 - @kaxil - Make the order of configs consistent for comparing
#497 - @Crazybus - Document es_use_repository and es_custom_package_url
#504 - @victorgs - Using tests as filters is deprecated
#493 - @Crazybus - Only use the first found java version if there are multiple installed
6.4.0 - 2018/08/24
Features
6.4.0 as default Elasticsearch version
Fixes
#484 - @kimoto - Fix downgrading Elasticsearch on RedHat hosts
#476 - @Crazybus - Fix version locking for the elasticsearch-oss package
6.3.1 - 2018/07/05
Features
6.3.1 as default Elasticsearch version
6.3.0.1 - 2018/06/28
Fixes
#460 - @toadjaune - Make sure ansible doesn't fail if the default systemd service file doesn't exist
#461 - @bilsch - Add missing become root in tasks that require root access
6.3.0 - 2018/06/18
Breaking changes
Elasticsearch 6.3 includes several big changes that are reflected in this role.
When upgrading from module versions prior to 6.3, there are a number of upgrade considerations to take into account:
This role defaults to the upstream package repositories, which now include X-Pack bundled by default. To preserve previous behavior which does not include X-Pack be sure to explicitly set es_enable_xpack: false which will install the elasticsearch-oss package.
Great care has been taken in making sure that all upgrade paths work, however as always please take extra caution when upgrading and test in a non-production environment. New automated tests have been added to make sure that the following upgrade paths work:
oss to oss
oss to xpack
xpack to xpack
X-Pack configuration files which used to be in ${ES_PATH_CONF}/x-pack are now in ${ES_PATH_CONF}/. If you have any configuration files in this directory not managed by ansible you will need to move them manually.
Features
Integration testing has been refactored in #457. This removed a lot of duplicate tests and added new tests to make sure all upgrade paths work.
It is now possible to test Elasticsearch snapshot builds by setting es_use_snapshot_release to true
Fixes
Installing es_plugins from custom urls is now idempotent. Previously the plugin name was being compared to the url which meant it would be reinstalled every time ansible was run because they didn't match
#454 - @Crazybus - Move jenkins matrix file into the repo so test suites are controlled via the pull request workflow
#455 - @Crazybus - Add automated test for upgrading from oss to oss
#457 - @Crazybus - Refactor integration tests to remove duplication and add extra suites to make sure all upgrade paths are covered
6.2.4.1 - 2018/06/14
Patch release requested by @average-joe in #453
Pull requests
#445 - @gekkeharry13 - Added configuration options for configuring x-pack notifications via email with some other nice fixes.
#450 - @Crazybus - improving some flakey tests which were randomly failing.
#447 - @chaintng - Fix to make sure sudo is used when running update-alternatives for java.
#423 - @eRadical - Fixing the until condition being used when installing rpms from a custom repository.
6.2.4 - 2018/04/24
6.2.4 and 5.6.9 as the default versions.
6.2.3 - 2018/04/21
Thanks to @cl0udf0x for adding proper names to all tasks which were unnamed #417
Thanks @cyrilleverrier for having a keen eye and spotting this typo. #432
6.2.2 - 2018/02/22
6.2.2 and 5.6.8 as the default versions
Thanks to @pemontto for fixing up all of the ansible conditional logic elastic#429
Thanks @cyrilleverrier for elastic#427 which makes sure x-pack settings are not in the config file when x-pack isn't enabled
6.1.3 - 2018/02/01
6.x is now the default es_major_version with 6.1.3 as the default es_version
Special thanks to @shribigb, @toddlers and @remil1000 for their efforts in getting 6.x support working!
.kitchen.yml has been updated to allow testing both 6.x and 5.x versions
A new Jenkins job has been added for pull requests to automatically test all combinations of 6.x and 5.x on ubuntu-1404, ubuntu-1604, debian-8 and centos-7 with the various test suites.