This discussion triggers the issue. The idea is that sometime we have disconnection between nodes and storage for temporary maintenance, and it would be annoying to keep releasing everytime there is a new situation. However, modifying the shared xenon_config will be helpful. Maybe add a [batchq] section in /project2/lgrandi/xenonnt/xenon.config when temporary issues happen so users need to do nothing and admin will take 2 minutes to override. Then, in batchq, it should be able to read the config in xenon_config and dynamically decide which binding to exclude.
Similar idea should generalize for all temporary fluctuations to minimize users efforts.
This discussion triggers the issue. The idea is that sometime we have disconnection between nodes and storage for temporary maintenance, and it would be annoying to keep releasing everytime there is a new situation. However, modifying the shared
xenon_configwill be helpful. Maybe add a[batchq]section in/project2/lgrandi/xenonnt/xenon.configwhen temporary issues happen so users need to do nothing and admin will take 2 minutes to override. Then, inbatchq, it should be able to read the config inxenon_configand dynamically decide which binding to exclude.Similar idea should generalize for all temporary fluctuations to minimize users efforts.