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
Currently each ewatercycle.model.* has a _get_docker_image and _get_singularity_image. The images are coupled to the available_versions class property.
Ideally the system administrator would pull/build all images so the user can just start them. If they are not available, this leads to issues (eWaterCycle/grpc4bmi#100 and eWaterCycle/grpc4bmi#95).
It would be nice to have a new module for administrators to build/pull all images. This would hold a registry of all the docker containers and the names of the corresponding singularity images. The ewatercycle.models.* classes could then get the docker/singularity images from this module, instead of having it hardcoded.
The text was updated successfully, but these errors were encountered:
Currently each
ewatercycle.model.*
has a_get_docker_image
and_get_singularity_image
. The images are coupled to theavailable_versions
class property.Ideally the system administrator would pull/build all images so the user can just start them. If they are not available, this leads to issues (eWaterCycle/grpc4bmi#100 and eWaterCycle/grpc4bmi#95).
It would be nice to have a new module for administrators to build/pull all images. This would hold a registry of all the docker containers and the names of the corresponding singularity images. The
ewatercycle.models.*
classes could then get the docker/singularity images from this module, instead of having it hardcoded.The text was updated successfully, but these errors were encountered: