Setting up GenSynth for Multi-Machine
If you want packages, copy the package repository to the location configured by GENSYNTH_PACKAGE_REPO on the API server machine.
Note
The default configuration extracts the file given to you by your Professional Services representative to the root of this repository.
Run start.sh on the master to start the Docker containers. If successful, the start script creates worker configuration and copies it to the shared workspace.
Tip
Optionally, run start.sh --install-templates to install the Simpnet and Resnet50 FRCNN templates. This will use the resource-install command to install the Simpnet and Resnet50 FRCNN data, models, and configuration from the GENSYNTH_PACKAGE_REPO location.
On each worker, change the working directory [cd] to a local folder, preferably in the home directory. From this location, run the setup_worker.sh script. This script resides on
<path-to-shared-drive>/multi-machine/setup_worker.sh.
This step unpacks configuration and scripts togensynth-deploy
under the current working directory.Run start.sh within the
gensynth-deploy
folder to start the worker API container on each worker, utilizing the configuration that was generated by the previous steps.Log into the GenSynth UI at <GENSYNTH_API_HOSTNAME>:<GENSYNTH_WEB_PORT>. The first person to log in should use the administrator login/password to create accounts as needed as well as to change the default administrator password.
Note
If you need to remove the containers (e.g., for an upgrade),use stop.sh on each machine to terminate all of the Docker containers. Note that doing this will invalidate your license and it will need to be activated again, as this script destroys the containers. Alternatively, you can manually interact with the containers such as docker stop gensynth-db. Stopping and starting the containers will not invalidate your license.