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
{{ message }}
This repository has been archived by the owner on Oct 26, 2022. It is now read-only.
With slice modify, users can be confused about when a particular reservation times out. 'Slice reservation time' really no longer makes sense (never did, really). We should take that out and replace with per-reservation expiration time in manifest.
Extend operations are really per-reservation operations anyhow.
We can then modify Flukes and client libraries to support this.
We can keep the semantics of the extendSlice call as is for now (as in 'extend all currently active reservations in this slice until date D', however long term we may want to fully expose the per-reservation semantics.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
With slice modify, users can be confused about when a particular reservation times out. 'Slice reservation time' really no longer makes sense (never did, really). We should take that out and replace with per-reservation expiration time in manifest.
Extend operations are really per-reservation operations anyhow.
We can then modify Flukes and client libraries to support this.
@YufengXin @paul-ruth
The text was updated successfully, but these errors were encountered: