Feature request: AWS cost estimate

[scholtalbers]

On usegalaxy.eu (https://github.com/usegalaxy-eu/galaxy/blob/release_19.09_europe/templates/show_params.mako#L227) there is a cost estimate for running the same job on AWS.
This might be a nice feature for any Galaxy instance to give the user(and admin) an idea of what their computation costs.

Wishlist:

• total cost per job (instance, data transfer)
• total cost of a history (sum of all jobs + data storage)
• cost of storage usage

The instance estimate is what .eu is already providing, but it doesn't yet include any datastorage/transfer costs. See also https://gitter.im/usegalaxy-eu/Lobby?at=5ddf80f446397c721c4b1b85

[nsoranzo]

Ping @bgruening

[bgruening]

I know I talked to Jelle and then he created this issue :)

[HadleyKing]

@nsoranzo,
This is one of the things that @kee007ney and I are trying to work on with our project. We would be happy to try and help out with developing/testing this.

[bgruening]

@HadleyKing let me know if you need more informations. @scholtalbers already linked some code above.

[HadleyKing]

I think Step 1: enable this script (or a copy of it) to load when you select an invocation under the User -> Workflow Invocations
Once we were able to see an example that could aggregate the requisite info, we could tweak it and test it for accuracy.

[HadleyKing]

Or maybe it could be part of the View screen as well. Maybe under About this Workflow?

[bgruening]

I will talk to @OlegZharkov ... maybe he has time to look into it. I guess some portable Vue components with a flexible config file to provide the pricing-table could be useful.

[HadleyKing]

I would be happy to help... but I am a total noob.
@jpat1546 and I want to implement this functionality into a BCO extension.

[HadleyKing]

Using what I made in #10029 it should be possible to take the JobMetrics.vue and apply a version of it to the invocations space, maybe replicating it for the invocation. And those functions could probably be easily rewritten for the history, but I have not been using the history APIs much outside of pulling them into the invocation functions. And I have not looked at the history UI at all.