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
Change Provider.launched_environment() to take an optional shutdown delay time (default to None using current behaviour, otherwise delay for the specified number of minutes).
Change each Provider to be able to handle an already-running instance. (Perhaps setting and releasing a lock on that instance?)
Change each Provider to run the shutdown command if the instance has a shutdown delay time set (even if that time is 0, in which case the shutdown should still occur asynchronously).
Why it needs to get done
During iteration on a (snap|charm|rock|whatever), each run includes starting up and shutting down an instance, which can add significantly to the time the run takes. A pre-warmed machine can avoid this.
NOTE: It will be up to the application to actually opt into using this feature, so it will be a backwards compatible change.
The text was updated successfully, but these errors were encountered:
Multipass' stop has a timeout to delay the shutdown, we used to always use this with a timeout that would allow for iterations. Not sure why that is no where to be seen now
What needs to get done
Basically make #571 production-ready.
Provider.launched_environment()
to take an optional shutdown delay time (default to None using current behaviour, otherwise delay for the specified number of minutes).Provider
to be able to handle an already-running instance. (Perhaps setting and releasing a lock on that instance?)Provider
to run theshutdown
command if the instance has a shutdown delay time set (even if that time is 0, in which case the shutdown should still occur asynchronously).Why it needs to get done
During iteration on a (snap|charm|rock|whatever), each run includes starting up and shutting down an instance, which can add significantly to the time the run takes. A pre-warmed machine can avoid this.
NOTE: It will be up to the application to actually opt into using this feature, so it will be a backwards compatible change.
The text was updated successfully, but these errors were encountered: