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
We currently use Vagrant to manage VMs in EC2 for recount-pump runs.
However, node management is ad hoc---each node has its own Vagrant process and subdirectory.
Node failures, either due to workflow specific problems (e.g. running out of disk space) or because nodes were pre-empted (spot market) need to be manually detected currently.
For a few tranches this is fine, for longer term runs, we may want to either try to use existing orchestration tools or roll our own to support the mix of inside/outside container code we're using.
The text was updated successfully, but these errors were encountered:
We currently use Vagrant to manage VMs in EC2 for recount-pump runs.
However, node management is ad hoc---each node has its own Vagrant process and subdirectory.
Node failures, either due to workflow specific problems (e.g. running out of disk space) or because nodes were pre-empted (spot market) need to be manually detected currently.
For a few tranches this is fine, for longer term runs, we may want to either try to use existing orchestration tools or roll our own to support the mix of inside/outside container code we're using.
The text was updated successfully, but these errors were encountered: