Duke-GCB / Duke-GCB/bespin-api
While waiting for user restart, VMs will run idle
Open
- Dominant language
- Python
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Placeholder issue for now. When a job fails to complete and the VM is left running, this will continue to count CPU hours, doing nothing until the user attempts to restart the VM.
We can discuss solutions but we should not be charging users during this period. Ideally we could pause the VM so it's not actually running while in this state.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.