puppet-elasticsearch fix(compat): bare min. to get srv running on 7.x

Fixed jvm.options.erb to add required jvm options for 7.x Fixed jvm.options.erb to change jvm options required only for openjdk 8 Added ES_PATH_DIR instance environment var Fixed log4j2.properties.erb to fix Deprecation WARNINGS Keeped Backward Compatibility but not tested yet

Pull request acceptance prerequisites:

[x] Signed the CLA (if not already signed)
[x] Rebased/up-to-date with base branch
[x] Tests pass [ except recurrent master fails on Debian 8 and OpenSuse 42 ]

Jun 27 '19 05:06 smasa90

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

Jun 27 '19 05:06 elasticmachine

Seems to have a little dups here https://github.com/elastic/puppet-elasticsearch/pull/1021 Didn't see the PR before pushing this one.

Jun 27 '19 05:06 smasa90

You’re right, I’ve not thought as much on how to handle correctly this version condition. I’ll update this when I have the time ti dig into. Or if someone as suggestions, I’ll consider it. Marked this as WIP

Jun 27 '19 08:06 smasa90

Is that better like that ? Private var, no mandatory implicit dependency to elastic_stack module. Default to false if no version is provided nor in elastic_stack::repo::version nor in elasticsearch::version. Can default to true when community will be ready to default to 7.x with Puppet modules.

Jul 02 '19 22:07 smasa90

Ping @tylerjl ?

Jul 04 '19 02:07 smasa90

Apologies for the delays here, I'm trying to get some more resources dedicated to some module updates and maintenance.

The short answer is that it gets really challenging to make these sorts of version detection changes since the module is in total control of the jvm.options file - I'm hoping that dropping support for multiple instances will let us manage the jvm.options file on a line-by-line basis, so users will be able to add or remove lines as necessary (that match the format for the version of Elasticsearch they're running) and alleviate the need to populate the entire file at all.

Jul 09 '19 23:07 tylerjl

How could we plan it ? A solution can be to copy default jvm.options file on each instance and manage it line by line

Jul 10 '19 20:07 smasa90

ping @tylerjl, I think we need this one way or an other. If this module is not maintained any more, on which provisioner can we turn ourselves to get a maintained module ?

Jul 29 '19 07:07 sticky-note

Rel #1032 Any updates on this?

Oct 18 '19 12:10 NITEMAN

Hi there,

Firstly, thank you for taking the time to contribute, and apologies for the radio silence from Elastic on this PR.

I'm going to be working on this module over the next few weeks, with an ultimate aim of updating the module to support the elasticsearch 7.x and simplifying the module to make it easier to use.

I'll be reviewing all the open issues and PRs over the next few days, and will merge or provide feedback where appropriate.

So please hang in there whilst we give this module some TLC.

Thanks again.

Feb 04 '20 13:02 fatmcgav

Dear @smasa90, thanks for the PR!

This is Vox Pupuli Tasks, your friendly Vox Pupuli GitHub Bot. I noticed that your pull request contains merge conflict. Can you please rebase?

You can find my sourcecode at voxpupuli/vox-pupuli-tasks

Jun 21 '22 19:06 vox-pupuli-tasks[bot]