CIPRES 2013-8-7

Transcript

2. Current Submit Call Graph
3. Current Submit System submit.py: •Templating engine for “COMMANDLINE” and “batch_command.run” files. •Slightly different copies per cluster? lib.py: •Settings for queues, maximum run time, functions for calling qsub, etc. etc. •Interprets “scheduler.conf” properties file. •Different copies for each cluster. •Configuration as an if-else tree. •Catch-All
4. Possible Submit System submit.py: •Templating engine for “COMMANDLINE” and “batch_command.run” files. •Slightly different copies per cluster? lib.py: •Settings for queues, maximum run time, functions for calling qsub, etc. etc. •Interprets “scheduler.conf” properties file. •Different copies for each cluster. •Configuration as an if-else tree. •Catch-All •Hack another function into lib.py
5. Suggested Submit System submit.py: •Templating engine for “COMMANDLINE” and “batch_command.run” files. •Slightly different copies per cluster? lib.py: •Settings for queues, maximum run time, functions for calling qsub, etc. etc. •Interprets “scheduler.conf” properties file. •Different copies for each cluster. •Configuration as an if-else tree. •Catch-All •Cleanliness •Use a fully-featured template system. •Use a fully-featured java-properties-file library. •Break functionally into logical groups •Maintainability •Eliminate “code as configuration” •Decide on a configuration format. •JSON, YAML, XML, etc. •Results in one code-base for all resources. •Extensibility •Add hooks for custom input-validators and parallel-rules-evaluators.