You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Part of a CBRAIN admin job involves configuring new tools, or new tool versions, with new apptainer containers.
The ToolConfig object for a new tool (or not version of an existing tool) often needs to be configured with better values than the default ones (where the tool belongs to admin only, and has no environment variables or cluster parameters, etc). It's a bit of a pain to enter all the config parameters. Often, we just need to copy them from a similar tool, or from a previous version of the same tool.
For the container, CBRAIN has the ability to dynamically build a apptainer image out of a docker image name, and cache it, but a better mechanism is to pre-build the container and store it one of CBRAIN's data providers. Then the ToolConfig can be given the ID of this image directly, and there will never be a need to build the container on any of the clusters.
I'm thinking we could do all that with a new CBRAIN task, a Tool configurator helper. The admin could select an existing blank ToolConfig that they want to configure, and a previous ToolConfig to use as a base, and the task would copy the necessary config parameters. At the same time, if the ToolConfig specifies a docker image name that isn't already in CBRAIN, it would build it, save it to a DP and replace the docker name with the ID of the new apptainer image.
The text was updated successfully, but these errors were encountered:
Part of a CBRAIN admin job involves configuring new tools, or new tool versions, with new apptainer containers.
The ToolConfig object for a new tool (or not version of an existing tool) often needs to be configured with better values than the default ones (where the tool belongs to admin only, and has no environment variables or cluster parameters, etc). It's a bit of a pain to enter all the config parameters. Often, we just need to copy them from a similar tool, or from a previous version of the same tool.
For the container, CBRAIN has the ability to dynamically build a apptainer image out of a docker image name, and cache it, but a better mechanism is to pre-build the container and store it one of CBRAIN's data providers. Then the ToolConfig can be given the ID of this image directly, and there will never be a need to build the container on any of the clusters.
I'm thinking we could do all that with a new CBRAIN task, a Tool configurator helper. The admin could select an existing blank ToolConfig that they want to configure, and a previous ToolConfig to use as a base, and the task would copy the necessary config parameters. At the same time, if the ToolConfig specifies a docker image name that isn't already in CBRAIN, it would build it, save it to a DP and replace the docker name with the ID of the new apptainer image.
The text was updated successfully, but these errors were encountered: