PR that replaces `machine` with `task` within DVC machine

[DavidGOrtega]

PR that alters tpi behaviour replacing machine with task

The basic idea would be starting a dummy service and they would be controlling task the same way they do with machine

[casperdcl]

potentially could transfer this to tpi?

[dacbd]

"DVC machine"?

[0x2b3bfa0]

🙊

[dacbd]

🙊

👀🎁🎄

[pmrowla]

This probably belongs in the tpi python package. But also, IMO the python package should reflect all of the resource types supported in the actual provider (so both iterative_machine and iterative_task resources, but maybe not the CML specific types).

[pmrowla]

I see that iterative-machine is now undocumented in the readme (and the formal provider docs), but having a standardized (cloud-agnostic) way of specifying a remote machine with consistent mappings for cpu/gpu resources still seems like it would be a useful general-purpose (non-DVC/CML related) feature for us to provide.

[casperdcl]

To summarise DVC-required features of TPI task:

• serverless (no SaaS deps)
• multi-cloud provisioning support
• sync via folder
• sync directly (e.g. via SSH and no S3 bucket, no spot instance recovery of data)
• one-off user-specified script/experiment
• user-specified setup deps (manually in initial script)
• download all logs (terraform refresh && terraform show)
• user can go offline

So there's "just" one major outstanding feature required for this integration :)