Casper da Costa-Luis
Casper da Costa-Luis
idk what you mean by different code. I'm talking about same *code*, different logic-branch owing to different *env* vars. ```python #script index = os.environ.get('TPI_PARALLEL_INDEX', 0) total = os.environ.get('TPI_PARALLEL_TOTAL', 1) tasks...
> `PARALLEL_INDEX` is **not** straightforward to implement Really? Argh. Backlogging.
Actually... won't TPI `task` need this?
> whether allowing specifying a fixed spot price is a good idea Do all clouds guarantee `default(auto) spot pricing` < `on-demand`?
so something like this? - long term (major relase) + everywhere: `on_demand: bool=True` - intermediate + `task`: `spot: float=-1` + standalone binary: `on_demand: bool=True`
I thought GCP uses `s/spot/preemptible/` and `s/on.demand/standard/` :)
Anyway the point of renaming is mostly to retain some backward-compatibility? The alternative -- `spot: bool=False` -- will silently break existing user workflows that have `spot: float` (presumably the float...
added to https://github.com/iterative/terraform-provider-iterative/issues/641 :)
Takes me ~1min to `apply` and ~5min to `destroy` a minimal `script` single task with no `workdir` files to sync.
target audience: any user wondering how much something costs without reaching for a calculator. To me it's closer to `p1` than `p2`.