[SERVER-1630] Support user configuration of JRuby 1.7 or 9k in Puppet Server packaging Created: 2016/11/02 Updated: 2018/04/17 Resolved: 2017/06/28
|Fix Version/s:||SERVER 5.0.0|
|Reporter:||Jeremy Barlow||Assignee:||Jeremy Barlow|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Epic Link:||Upgrade Puppet Server to JRuby 9k|
|Sprint:||Server 2017-04-19, Server 2017-05-03, Server 2017-05-31|
|Release Notes:||New Feature|
|Release Notes Summary:|| Puppet Server packages now include both the dependencies for JRuby 1.7 (running under Ruby language version 1.9.3) and for JRuby 9k (running under Ruby language version 2.3 or later). By default, Puppet Server will use JRuby 1.7. Users can choose to have Puppet Server run with JRuby 9k instead, however, by adding the following environment variable assignment to the "/etc/sysconfig/puppetserver" or "/etc/default/puppetserver" file and restarting the puppetserver process:
While we eventually hope to be able to support JRuby 9k as the "primary" version of JRuby in Puppet Server, we've encountered some blocker issues that are currently impeding that transition. It is possible, though, that some users may be wiling to live with or may not be too adversely affected by the performance and memory issues we've seen in some internal testing so far and would much rather trade those off for the ability to use MRI Ruby 2.3+ functionality on the server.
Chris Price and I have talked about the possibility of packaging Puppet Server in such a way that a user could configure it to run with either JRuby 1.7.X or JRuby 9k. This would likely involve some work with dependency configuration and possibly altering the Java command line used by the ezbake scripts to add in JRuby and its upstream dependencies via an extension to the CLASSPATH - as opposed to just picking those dependencies up via a Puppet Server uberjar.
Giving at least OSS users the ability to at least experiment with JRuby 9k in Puppet Server could help us obtain some valuable feedback on how well this may already work in the "real world".
|Comment by Kenn Hussey [ 2017/05/15 ]|
Jeremy Barlow please provide release notes for this issue, if applicable.