Skip to content

Refactor maintenance-worker docker image

Hannes Heine requested to merge pr485head into pr485base

Created by: Tirokk

roschaefer Authored by roschaefer Merged

Pullrequest

This PR gives us a deployable maintenance-worker docker image. If we deploy this image with a pod in kubernetes, we should be able to do the following:

  • Import and migrate our legacy database
  • Import and migrate our legacy uploads directory

On Digital Ocean, this would require us to bring the application in maintenance mode first, remove the volume claim on the neo4j service and then deploy the pod with this very image. Reason: Digital Ocean has no multi-access on volumes. So we cannot deploy 2 pods (neo4j pod and maintenance pod) with a volume claim on the same volume.

Issues

  • None

Checklist

  • None

How2Test

  1. docker-compose -f docker-compose.maintenance.yml up --build
  2. docker-compose -f docker-compose.maintenance.yml exec maintenance bash

You should have a shell in the maintenance-worker. You can play around and try to carry out the tasks above ☝

E.g. import_legacy_db, import_legacy_uploads and of course you can neo4j-admin load ... and neo4j-admin dump ... see neo4j documentation.

You can check out the updated documentation.

Todo

  • None

Merge request reports