Protocol for releasing from gltg-dev to gltg

• Is everything ok on gltg-dev
• Tag source code
  • Clowder
  • Geodashboard
  • GLTG Project repo
• On gltg run backup.sh in /home/backup
  • Check postgresql is dumped in /home/backup/<date>/postgresql_dump.sql.gz
  • Check mongo is dumped in /home/backup/<date>/mongo
  • Check clowder is copied to /home/backup/<date>/[clowder]
  • Check geodashboard is copied to /home/backup/<date>/geodashboard
• Update clowder on gltg (/home/clowder/update-clowder.sh)
• Update geodashboard on gltg (/home/medici/update-geodashboard.sh)
• Update gltg (configuration for geodashboard)
• Start services and verify
• Copy parser/other scripts to gltg
• Run script (check config!!) for organizing greon files
• Run script (check config!!) for uploading greon files to clowder
• Run Each parser and check output (check config!!)
  • Greon
  • Usgs
  • Wq_portal
  • Ltrm
  • Noaa
• Test, Test, Test
• Call grandma and tell her what an awesome job we did

List from Rob:

tag clowder with gltg_v#.#

tag geodashboard with gltg_v#.#

tag gltg with v#.#

where the #.# are the same for all

1) dump database on gltg-dev

#/usr/bin/sudo -i -u postgres /usr/bin/pg_dumpall | gzip --rsyncable > /home/postgresql_dump.sql.gz

/usr/bin/sudo -i -u postgres /usr/bin/pg_dump -c -d geostream > /home/geostream.sql

scp  /home/geostream.sql gltg:/home

2) dump clowder if needed?

3) backup gltg

/home/backup/backup.sh

4) stop everything

stop clowder

stop geodashboard

5) update databases

sudo -u postgres psql -d geostream6 < /home/geostream.sql

6) update clowder

/home/clowder/update-clowder.sh --force

CLOWDER_BRANCH=CATS-CORE0 /home/clowder/update-clowder.sh --force                     //for develop branch

7) update geodashboard

/home/medici/update-geodashboard.sh --force