You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Background
At the moment, Cloud Pipeline does not respect Lustre costs for run price calculations and it would be nice to support it.
Approach
Currently, run object provides the following information about prices:
computePricePerHour - virtual machine price per hour
diskPricePerHour - instance disk gigabyte price per hour
pricePerHour - overall run price per hour: computePricePerHour + <disk size GB> * diskPricePerHour
To support run filesystem costs a new run field shall be added:
fsPricePerHour - filesystem price per hour taking into account its current capacity. This value shall be updated as per as the file system capacity is updated.
This price shall be included into pricePerHour value. This way, a new total run price per hour shall be re-calculated as:
Background
At the moment, Cloud Pipeline does not respect Lustre costs for run price calculations and it would be nice to support it.
Approach
Currently, run object provides the following information about prices:
computePricePerHour
- virtual machine price per hourdiskPricePerHour
- instance disk gigabyte price per hourpricePerHour
- overall run price per hour:computePricePerHour
+<disk size GB>
*diskPricePerHour
To support run filesystem costs a new run field shall be added:
fsPricePerHour
- filesystem price per hour taking into account its current capacity. This value shall be updated as per as the file system capacity is updated.This price shall be included into
pricePerHour
value. This way, a new total run price per hour shall be re-calculated as:fsPricePerHour
shall also be updated as per as the run's file system capacity is updated.The text was updated successfully, but these errors were encountered: