As discussed in this slack thread, the instability of mounting affects the performance of env_starter and batchq.
To avoid manually modifying the codes based on the variant status of servers, a better practice is to put all possible bindings and image locations in those two modules and do an automatic check to avoid problematic ones. By doing that, we can guarantee that users will get all of the possible resources without touching the inner side of the tools. The implementation of image location checking was done in #108, and here, we also added a similar function to the binding.
The unit tests are also updated accordingly. I have run the tests on midway2, midway3 and dali and on all servers they are working well.
As discussed in this slack thread, the instability of mounting affects the performance of
env_starterandbatchq. To avoid manually modifying the codes based on the variant status of servers, a better practice is to put all possible bindings and image locations in those two modules and do an automatic check to avoid problematic ones. By doing that, we can guarantee that users will get all of the possible resources without touching the inner side of the tools. The implementation of image location checking was done in #108, and here, we also added a similar function to the binding.The unit tests are also updated accordingly. I have run the tests on midway2, midway3 and dali and on all servers they are working well.