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.
- With the release of the latest versions of Globus tools it is now required to deploy all Globus services, even if all are not going to be used.
- Hostnames that are used in config files can be better controlled by using the
6.6.6requires either a whitelist of shards or an explicit directive that no whitelist will be provided, the latter was chosen
- Cog updated to
- ESGF-ORP updated to
- ESGF-Security updated to
- esgpublisher updated to
- udunits2 updated to
- Small changes to the configuration of myproxy-server regarding the locations of certificates and keys
- A missing dependency for the Globus Transfer API was added to ensure Globus integration within CoG is operational.
- Tomcat webapps are now always cleaned out and re-installed
- Cog updated to
- Tomcat updated,
- Solr updated,
- Java 8 set to be updated to latest version of OpenJDK 8. This is also a switch to using
yumto install Java.
- Previous releases of ESGF-Ansible created entries in
/etc/fstabfor 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/fstabmay or may not cause unexpected behavior and they should be safely removed.
gftphost*variables renamed to
- 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].ymlfile 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
admin_passvariable and requirement for either the
/esg/config/.esgf_passfile to be present on the Node or the
admin_passvariable to be specified
- 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.ymlplaybook to easily repeat the esg-publisher setup steps in the event of failure
- No longer managing SELinux state
- If setting up
firewalldon 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.