Deployment onto Dev Site

This page details how the code goes from development to deployment on a Dev VM.

Git repo: https://github.com/ral-facilities/user-upload-service

Harbor repo: https://harbor.stfc.ac.uk/harbor/projects/122230/repositories

VM Deployment (VPN needed): http://host-172-16-114-165.nubes.stfc.ac.uk/

View metadata in Dev VM via ICAT Admin tool

VM ICAT metadata can be seen by:

• Turning off mixed content restrictions in Chrome

• visiting https://vigorous-lamarr-7b3487.netlify.app/

  • setting http://host-172-16-114-165.nubes.stfc.ac.uk as the server

  • auth=simple, user=root, password=pw

At the moment the deployment in the VM is done manually by bringing up/down the docker-compose stack.

Preparing for Dev deployment

The following variables need to be changed/checked to deploy to the dev from a local working system:

• Change/check the reverse proxy options for the upload container

• Change/check the docker-compose options for:

  • datagateway UPLOAD_URL

  • upload S3 endpoint and credentials to point to ECHO

  • upload image should be pulled from Harbor

Metrics on Dev VM

Metrics are gathered using a Prometheus server at http://host-172-16-103-209.nubes.stfc.ac.uk:8080/ (details on how it was set up here)

This polls the Upload metrics URL, available at http://host-172-16-114-165.nubes.stfc.ac.uk/upload-service/metrics

These are then displayed in Grafana at http://host-172-16-114-165.nubes.stfc.ac.uk/grafana/

Alex Kemp holds the access credentials for these.