Releases

This page contains infomation about what is added or changed with each new release. The Critical section outlines any items the are highly likely to require changes from users. The Info section outlines informative items that may be helpful for users to know, but likely do not require action. All items described within a release are relative to the previous release.

4.0.1 (2019-04-10)

Critical

  • Previous releases of ESGF-Ansible created entries in /etc/fstab for the bind mounts required by GridFTP. These are now setup to be created when starting GridFTP and removed when stopping GridFTP. Their presence in /etc/fstab may or may not cause unexpected behavior and they should be safely removed.

Info

  • New status.yml playbook, see the new Verification Section.
  • Default memory for Tomcat has been increased.

4.0.0-beta2 (2019-03-27)

Critical

  • gftphost* variables renamed to globushost*
  • Added variables generate_* which are required to be specified if the user would like esgf-ansible to generate required files (keys/certs) for the respective service
  • Key, certificate, and other file paths specified in each host_vars/[hostname].yml file are now required to be on the managed machine, rather than the control machine
  • Added requirements to more reliably manage keys/certifcates, users are now required to specify either the file paths as described in the previous bullet or the respective generate_* variable
  • Added admin_pass variable and requirement for either the /esg/config/.esgf_pass file to be present on the Node or the admin_pass variable to be specified

Info

  • New sample files within the host_vars/ directory to help with all the new changes above
  • A new tag, publisher, has been added to the install.yml playbook to easily repeat the esg-publisher setup steps in the event of failure
  • No longer managing SELinux state
  • If setting up firewalld on CentOS 7, and it was not previously installed and enabled, a reboot will be required after installing and enabling
  • Not deploying monitoring software if neither of the prometheus_* variables are specified

A number of reported bugs have been resolved and fragile setup steps were made more resilient.

4.0.0-beta1 (2019-02-25)

Critical

Info