Load database drivers offline
If your CloudDM deployment cannot reach the public internet or a Maven repository, download the offline driver archive in advance and extract it into the CloudDM data directory.
CloudDM loads drivers from each component's data/drivers directory by default.
- In single-node mode (Alone), the Console and Sidecar run in the same process. Load the drivers once.
- In cluster mode, the Console and Sidecars run separately. Load the same drivers on the Console and every Sidecar in the target cluster.
Download the offline driver archive
Download the CloudDM offline driver archive and transfer drivers.tar.gz to the CloudDM host. The archive contains a top-level drivers/ directory. After extraction, check that the contents follow this layout.
<CloudDM data directory>/
└── drivers/
├── <driver name>/
│ └── <version>/
└── ...
Single-node mode
Load the offline driver archive into the CloudDM Alone data directory. These examples assume the following paths.
- CloudDM installation directory is
/opt/cgdm/alone. - Offline driver archive is
/tmp/drivers.tar.gz.
TGZ example
Stop CloudDM Alone, extract the archive into data, and start the service again.
cd /opt/cgdm/alone
./bin/shutdown.sh
tar -xzf /tmp/drivers.tar.gz -C data
./bin/startup.sh
Docker example
This example assumes the container is named cgdm-alone. Copy the archive into the container, then extract it into the persistent data directory.
docker cp drivers.tar.gz cgdm-alone:/tmp/drivers.tar.gz
docker exec cgdm-alone \
tar -xzf /tmp/drivers.tar.gz -C /root/cgdm/alone/data
docker exec cgdm-alone rm -f /tmp/drivers.tar.gz
docker restart cgdm-alone
Cluster mode
CloudDM checks the driver on the Console and every connected Sidecar in the target cluster. It marks the driver as available only when all those nodes have it. Load the same drivers into the data/drivers directory on the Console and on each Sidecar in the target cluster.
TGZ example
This example uses one Console and two Sidecars.
| Node | Hostname | Installation directory |
|---|---|---|
| Console | console-01 | /opt/cgdm/console |
| Sidecar 1 | sidecar-01 | /opt/cgdm/sidecar |
| Sidecar 2 | sidecar-02 | /opt/cgdm/sidecar |
Copy the archive to every node.
scp drivers.tar.gz console-01:/tmp/drivers.tar.gz
scp drivers.tar.gz sidecar-01:/tmp/drivers.tar.gz
scp drivers.tar.gz sidecar-02:/tmp/drivers.tar.gz
On the Console node, stop the service and extract the archive.
cd /opt/cgdm/console
./bin/shutdown.sh
tar -xzf /tmp/drivers.tar.gz -C data
On each Sidecar node, stop the service and extract the archive.
cd /opt/cgdm/sidecar
./bin/shutdown.sh
tar -xzf /tmp/drivers.tar.gz -C data
Once the archive is extracted on every node, start the Console first, then start each Sidecar.
# Run on console-01
cd /opt/cgdm/console
./bin/startup.sh
# Run on both sidecar-01 and sidecar-02
cd /opt/cgdm/sidecar
./bin/startup.sh
Docker example
This example assumes the cluster uses the cgdm-console and cgdm-sidecar containers. Load drivers into both containers, then restart the Console before restarting the Sidecar.
docker cp drivers.tar.gz cgdm-console:/tmp/drivers.tar.gz
docker exec cgdm-console \
tar -xzf /tmp/drivers.tar.gz -C /root/cgdm/console/data
docker exec cgdm-console rm -f /tmp/drivers.tar.gz
docker cp drivers.tar.gz cgdm-sidecar:/tmp/drivers.tar.gz
docker exec cgdm-sidecar \
tar -xzf /tmp/drivers.tar.gz -C /root/cgdm/sidecar/data
docker exec cgdm-sidecar rm -f /tmp/drivers.tar.gz
docker restart cgdm-console
docker restart cgdm-sidecar
If the cluster has multiple Sidecars, repeat the copy, extract, and restart steps for every Sidecar container.