The current CT config files and docker-compose are unwieldy, with many configurations duplicated across several files, and subfor ltle changes are required in certain situations that will not be obvious to operators (e.g., changing the image name of certain plugins based on the architecture). We need a program that can take a high-level config and generate the equivalent of a "release" directory, with the compose and all of the configs ready to go.
The high-level config should consist of:
- architecture (x86 vs arm, etc)
- source images (directory or URL)
- model (the id of a model in the MC, longer term)
- log level (optional)
- release version (optional, default to latest)
- Advanced custom config (optional, to set configs like saving threshold in the storing plugin)
This should probably be a comand-line program at a minimum.
The current CT config files and docker-compose are unwieldy, with many configurations duplicated across several files, and subfor ltle changes are required in certain situations that will not be obvious to operators (e.g., changing the image name of certain plugins based on the architecture). We need a program that can take a high-level config and generate the equivalent of a "release" directory, with the compose and all of the configs ready to go.
The high-level config should consist of:
This should probably be a comand-line program at a minimum.