Project

General

Profile

How to update Copernicus on Production and Demo

Servers:

  • Demo:
    • ECS
  • Production:
    • Rancher Prod1Mil / Copernicus environment

Update procedure:

  • Demo:
    [TODO] Update here after moving demo websites to Rancher.
  • Production:
    Copernicus Land & Insitu is rancherized.

The rancher environment is here: https://rancherprod.eea.europa.eu/env/1a56647/apps/stacks

Revproxy and Docker/Rancher compose files are here: https://eeasvn.eea.europa.eu/repositories/deployment/copernicus/

Pre-requirements:

  • Rancher Compose
  • Within Rancher UI register min 1 hosts with label: `copernicus=yes`

Deploy in production

On your laptop do :

$ git clone https://github.com/eea/eea.docker.copernicus.git
$ cd eea.docker.copernicus/deploy/land
$ rancher-compose --project-name copernicus-land --env-file land.env up -d
$ cd eea.docker.copernicus/deploy/insitu
$ rancher-compose --project-name copernicus-insitu --env-file insitu.env up -d

See also Rancher tips and tricks
for info on how to restore Data.fs and blobstorage

Copernicus Land (website)

1. Release a new version of eeacms/plone-copernicus-land:

$ git clone https://github.com/eea/eea.docker.plone-copernicus-land.git
$ cd eea.docker.plone-copernicus-land
$ git tag 11.3-1.6
$ git push --tags

2. Update VERSION within `.env` files:

$ cd eea.docker.copernicus/deploy/land
$ vim land.env
VERSION=11.3-1.6

3. Run the upgrade:

$ rancher-compose --project-name copernicus-land --env-file land.env pull
$ rancher-compose --project-name copernicus-land --env-file land.env up -d --upgrade --interval 90000 --batch-size 1

4. Confirm that the upgrade went well:

$ rancher-compose --project-name copernicus-land --env-file land.env up -d --confirm-upgrade

5. Roll-back if the upgrade didn't go well:

$ rancher-compose --project-name copernicus-land --env-file land.env up -d --roll-back

6. Invalidate cache

$ rancher-compose --project-name copernicus-land --env-file land.env restart memcached

InSitu (website)

1. Release a new version of eeacms/plone-copernicus-insitu:

$ git clone https://github.com/eea/eea.docker.plone-insitu.git
$ cd eea.docker.plone-insitu
$ git tag 2.0
$ git push --tags

2. Update VERSION within `.env` files:

$ cd eea.docker.copernicus/deploy/insitu
$ vim insitu.env
VERSION=2.0

3. Run the upgrade:

$ rancher-compose --project-name copernicus-insitu --env-file insitu.env pull
$ rancher-compose --project-name copernicus-insitu --env-file insitu.env up -d --upgrade --interval 90000 --batch-size 1

4. Confirm that the upgrade went well:

$ rancher-compose --project-name copernicus-insitu --env-file insitu.env up -d --confirm-upgrade

5. Roll-back if the upgrade didn't go well:

$ rancher-compose --project-name copernicus-insitu --env-file insitu.env up -d --roll-back

6. Invalidate cache

$ rancher-compose --project-name copernicus-insitu --env-file insitu.env restart memcached