Right now, our config files (JSON) describe the information of available queues on a given cluster and are not easily customizable. For instance, when loading queues from a config file, the keys of the returned dictionary must correspond to an actual queue name on the cluster (i.e. the PBS option -q). Also, there is no way, in the config of a queue, to add additional PBS options (e.g. -l feature=k80).
What should be done:
Right now, our config files (JSON) describe the information of available queues on a given cluster and are not easily customizable. For instance, when loading queues from a config file, the keys of the returned dictionary must correspond to an actual queue name on the cluster (i.e. the PBS option -q). Also, there is no way, in the config of a queue, to add additional PBS options (e.g.
-l feature=k80).What should be done:
-q(the actual name of the queue to use) as an additional information for each queue.-las additional information for each queue.