[Go-essp-tech] ESG Gateway 1.2.0 Beta Release

[Eric Nienhouse]

Hi All,

We're pleased to announce the ESG Gateway 1.2.0 Beta Release.  We're 
currently deploying this version to the NCAR staging system for 
testing.  Details for accessing this release can be found below.

*Please note* that a database issue has been discovered which may affect 
those planning to upgrade to the 1.2.0 Beta.  (See included message 
below.)  If you have not already sent in a database dump, I encourage 
you to do so in order to assess upgrade impact as well as to identify 
the simplest course of action for your gateway.  (*Please send your 
dumps directly to me and not to the list*.)

The configuration of the gateway has changed significantly with this 
release.  This has been done in order to simplify the management of 
site-specific configuration.  As such, the gateway now utilizes a 
separate "gateway home directory" for configuration, including the 
gateway.properties and messages.properties files.  Further details can 
be found at the links below.

Installing a 1.2 Gateway:

 
https://wiki.ucar.edu/display/esgcet/Gateway+Installation+Instructions+%28version+1.2%29 


Upgrading from 1.1 to a 1.2 Gateway:

 
https://wiki.ucar.edu/display/esgcet/Gateway+Upgrade+Instructions+%28version+1.1+to+version+1.2%29 


The release installation package can be downloaded from:

 
https://vets.development.ucar.edu/nexus/content/repositories/releases/sgf/gateway/1.2.0-BETA/ 


Please provide feedback (good or bad!) to:  
esg-gateway-dev at earthsystemgrid.org

-or-

If you have Jira Issue Tracking access, please enter a trouble ticket 
against version "1.2.0-BETA1" under the "Affects Version/s" drop-down.

Thank you and best regards,

-The ESG-CET Gateway Development Team

Nathan Wilhelmi wrote:
> Hello,
>
> We have discovered an issue with the database in current releases 
> where duplicate files may be published that put the gateway into an 
> inconsistent state. The problem has been fixed in version 1.2 so the 
> issue should not reoccur after the next release.
>
> The fix for 1.2 cannot be applied when the duplicate records exist. So 
> for the folks planning to do an upgrade to 1.2 from 1.1 (rather than a 
> clean install) we would like to get a copy of your database so we can 
> determine if you are affected and the exact course of action that will 
> need to be taken.
>
> So if you could send me a dump of your database we will review the 
> data and run a test upgrade of the database for version 1.2.0. If you 
> are affected we can work out the easiest course of action for your 
> particular case. *Please send your dumps directly to me, not the 
> list*. If you could send a database backup using plain text format 
> using insert statements with $ quoting disabled.
>
> Please let me know if you have any questions.
>
> Thanks!
>
> -Nate