ESGF Installation Working Team Meeting Minutes

Sasha, Zed, Lina, Prashanth, William, Luca

Solr 6.x upgrade
- Seems to work with upgrade at JPL
- does not upgrade backend Lucene indices, that would be a separate migration to be implemented, and needed for 7.x upgrades
- Sasha to test, then try production
- not backwards compatible, so sites running 5 can't replicate 6, so a warning
- Action plan to discuss at next CDNOT
2.6.9 upgrade
- Key pieces in place, Prashanth to cut 2.6/0 for testing
- Leave cipher suite alone, maybe remove last cipher
Postgres upgrade to 9.x
- Will require data migration
- Using the postrges repos will require upgrading data if they drop the current version for continued support (eg 9.4 to 9.6)
- RHEL/CentOS 7 will have security plan so this is best option

Sasha, Katharina, Lina, Prashanth, William, Luca

2.6.9 - needed for conda package update
- Sasha to update esgprep tag and remove temporary requests version
- Prashanth to use 2.6.0 space first before cut to master
2.7
- August timeframe for testing
- add esgf-auth PR
- Python 9 RPMs
RHEL/CentOS 7
- LLNL to start testing
- Update Apache frontend to support two templates for 6 vs 7
- Need to engage with stats team on build failures for RHEL 7
3.0
- stuck on myproxy-logon issue
- Need to convert to Python 3.0
  - Also publisher, esgfpid, esgprep, cdf2cim, all the user auth modules
  - CoG will be most work
Solr
- Should upgrade to 6.x or 7.x
- Luca to investigate
- Will be a federation-coordinated effort - enlist CDNOT to coordinate

Provide feedback