cloud-pipeline icon indicating copy to clipboard operation
cloud-pipeline copied to clipboard

Published 20 hours ago • verified publisher icon epam

Run estimation improvement

Open Wedds opened this issue 3 years ago • 1 comments
trafficstars

At the moment, run price estimation in UI might differ from the one, displayed in billing reports. It would be nice to make calculation procedures consistent.

Right now, billing-report-agent implements the following approach to determine compute resource billing for a certain period:

  1. Retrieve statuses of a run
  2. Adjust statuses:
  • all the statuses outside desired period are omitted (could be skipped for UI, since estimated price is calculated for the period from the start till the current moment)
  • in case pipeline is currently running – add STOPPED status with the current timestamp
  • there should be at least 2 statuses after adjusting
  1. Calculate billings for all the active periods, received after adjusting. While iterating over statuses:
  • period, started with RUNNING state, considered to be active
  • all others periods are inactive (zero cost)
  1. Merge active periods to calculate a total cost

Wedds avatar Mar 31 '22 12:03 Wedds

@Wedds @sidoruka backported to release/0.16 (d5e972abbb9dc45b67f7f9257156f73c6703d244)

rodichenko avatar Apr 05 '22 11:04 rodichenko