We try to balance cloud spend vs developer efficiency in our team. From time to time devs needs stronger instances (CPU/GPU/RAM/extra machine, etc) with their dev environment ready. However, the transitioning is cumbersome, although we added some scripts and automation. Machines tend to be idle a big portion of the time. Are there good solution to reduce devops burden from the devs while reducing wasted resources?
Gitpod (<a href="https://www.gitpod.io" rel="nofollow">https://www.gitpod.io</a>) is a great option here. It aims to remove the ops burden, provide a great developer experience and give you tools to manage your spend (eg automatic timeouts, suspend/resume, standardized creation of environments).<p>Full disclosure: I’m one of Gitpod’s co-founders.
We had a system (Jenkins job on a cron and some bash) at my last job that would turn them off at night. We then provisioned aws keys that could manage the power settings. That way devs could power them on/off as needed.<p>At my current place we have an older set of VMware infra that is used for this. Cap vs op expense, they are not powered off.