Currently Turbinia runs with a mostly static configuration, and so we run the same set of Tasks and the same set of arguments for those Tasks. We would like to be able to change the behavior of a given Turbinia run by passing this kind of data in as a recipe. This would allow us to specify more targeted processing and analysis for various scenarios. This issue is to track the "dynamic task configuration" part of this, and #26 will track the Recipe side.
Some notes:
For dynamic task configuration, tasks will define the configuration options that it can use at run time. This is just a flat dict of options set in the Task object code. Only the options found there can be configured dynamically by users. The values set in config will be the defaults that are used by the Task when no overriding config is specified.
Additionally, these options can also be used to dynamically generate command line option flags so users can specify those when making Turbinia requests.
Currently Turbinia runs with a mostly static configuration, and so we run the same set of Tasks and the same set of arguments for those Tasks. We would like to be able to change the behavior of a given Turbinia run by passing this kind of data in as a recipe. This would allow us to specify more targeted processing and analysis for various scenarios. This issue is to track the "dynamic task configuration" part of this, and #26 will track the Recipe side.
Some notes:
For dynamic task configuration, tasks will define the configuration options that it can use at run time. This is just a flat dict of options set in the Task object code. Only the options found there can be configured dynamically by users. The values set in config will be the defaults that are used by the Task when no overriding config is specified.
Additionally, these options can also be used to dynamically generate command line option flags so users can specify those when making Turbinia requests.