Support custom queues

[MarcCote]

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:

• Support custom queue name in the config files.
• Add the PBS option -q (the actual name of the queue to use) as an additional information for each queue.
• Allow adding PBS option -l as additional information for each queue.

[mgermain]

Not sure what you mean by "Add the PBS option -q to use "

[MarcCote]

When writing a PBS file, I think you must provide a -q option, specifying the actual name of the queue to use on the cluster.

[bouthilx]

Maybe BatchConfig would be less confusing. It could contain definition for all (or many) of smart-dispatch's parameters, including the queue. It would be passed with a new parameter, not to -q.