ESGF-Ansible is completely separate from the legacy 2.x ESGF-Installer. The tools provided by ESGF-Installer are, in general, incompatible with ESGF-Ansible and should not be used in cooperation with ESGF-Ansible. The FAQ page describes how to upgrade a node from the legacy installer using ESGF-Ansible, after which point the legacy tools should no longer be used.
Here is a summary of the system requirements, see Ansible Installation for more information.
|Control Machine||Managed Machine|
|OS||Any, Not Windows||CentOS 6/7|
|Python||>=2.7||2 (CentOS 6/7 has 2.6/7)|
|Other||SSH to Managed Machine||Account with escalated privileges|
To anyone new to ESGF and/or Web-based service deployments, running services in HTTPS is a must,
and this requires SSL certificates recognized by current browsers and other http(s) clients, eg.
If you haven’t already, please check with your organization to see if you have already purchased certificates from a vendor.
If not, purchase one for your targeted ESGF Node server. Free certificates can be obtained from
See the Web Certificate Section within this site for more information.
By default the firewall for a machine will not be configured. Users may set the following, applicable, variable and ESGF-Ansible will take steps to configure the firewall:
configure_centos6_iptables: true # or configure_centos7_firewalld: true
See the Host Variables Configuration Section for links to info about these variables.
The required open ports for each node type are as follows, for the default configuration:
|Data||80, 443, 50000:51000, 2811|
|IDP||80, 443, 7512|