Migration to Docker

In this section, we describe the procedure that you need to follow in order to migrate to a Docker deployment from a manual one. As you imagine, the new Docker deployment will be completely clean. That means that the component databases will be empty. If that is fine with you, then before migrating please delete all your registered resources from the current deployment and register them again once the docker deployment is online, in order to avoid any conflicts. In such a scenario, you only need to complete steps 1 and 2 described below. Otherwise, you need to perform a database migration to the new docker deployment. This is described in step 3:

1. Follow the instructions for migrating to the latest symbIoTe release (i.e. 3.0.0)
2. Deploy the latest symbIoTe release as described here.
3. In case you want to perform a database migration, we provide some helpful scripts here. First, you need to dump the symbIoTe databases from your current deployment. This can be done by executing the following command in the host of your current deployment.

./symbiote-mongo-dump.sh

This command will create a folder named mongo_backups containing all the symbIoTe databases. Please, move this folder as well as the symbiote-mongo-restore.sh to your docker host. If the host is the same machine, you can naturally omit this step. Then, on your docker host, once your docker deployment has been launched, you need to copy the necessary files on the mongo container and run the migration script. This can be done with the following commands:

docker cp symbiote-mongo-restore.sh {mongo_container}:/home
docker cp mongo_backups/ {mongo_container}:/home
docker container exec -it {mongo_container} bash /home/symbiote-mongo-restore.sh

, where {mongo_container} is the name of the symbIoTe mongo container which can be found by executing:

docker container ls

Tab completion can also come in handy here for auto-completing the mongo container name.

NOTE:
Since, by using the Docker deployment the PAAM will get a new certificate, some of the Platform clients might complain that the PAAM certificate is not valid. In such a scenario, simply delete the keystore of the client and re-deploy it.