Project

General

Profile

Feature #4680

Quantize glidein shutdown times in the cloud

Added by Burt Holzman almost 6 years ago.

Status:
Assigned
Priority:
Low
Category:
Factory
Target version:
Start date:
09/24/2013
Due date:
% Done:

0%

Estimated time:
Stakeholders:
Duration:

Description

Many clouds have quantized pricing for fixed time intervals -- for example, in EC2 if you run for 1 minute you may as well run for 60.
We should adjust the glidein lifecycle to maximize the value.

Example: An EC2 glidein job runs for 50 minutes. (The glidein is set to wait 20 minutes before retiring).
Since we would retire at 70 minutes, we should extend the glidein lifetime to roughly 120 minutes, since we've already paid for that hour.


Related issues

Related to glideinWMS - Bug #5359: Modify DAEMON_SHUTDOWN to use idle timers that are relative to change in stateClosed2014-02-06



Also available in: Atom PDF