We need to be able to assess the size of an OpenQuake job prior to running it

[Muharem Hrnjadovic]

This is needed in order to enforce quotas and/or make the decision whether virtual machines should be spun up in the cloud in order to perform the calculation.
We could have some sort of quick analysis phase that yields assessment data points like the number of grid points, assets etc. These are then fed into an assessment algorithm.

[Lars Butler (lars-butler)]

At the present time, estimating job time upfront (given all of the various parameters) is rather difficult. I recommend that we delay work on this particular feature until we have more historical job information from which we can gather data to create better estimates.

[John Tarter (toh2)]

I moved this out a couple of Sprints, as our focus is on the new engine. This can be revisited after the new engine is in place.