Add SSH Options in Dashboard for Deployments

[Mik-TF]

Feature Request

• Add SSH Options in Dashboard for Deployments
  • add ssh pub key in authorized_keys
  • replace current ssh pub key with new key

In Practice

It would be nice if users could add an ssh public key in the authorized_keys on their VMs, by using the SSH section of the dashboard. So we would add an option to update the authorized_keys file of all of the current user VM.

Also, it would be nice if users could update the ssh public key in the SSH section and that it would be reflected in all the VMs of the user (update existing pub key, not just adding a new key)

Use

This is very useful for users that actively use the grid on perhaps more than just 1 computer.

[xmonader]

The thing for that to be done completely from the client side, this requires tcp sockets in the browsers, which is intentionally not allowed, for security reasons. What I've been thinking of, is the user can deploy another workload e.g gridagent that can some specific tasks and that one can do ssh manipulation or whatever things that aren't allowed from the browser

[Mik-TF]

I totally agree with you here. So perhaps the issue should be: Create Weblet to Interact with TFGrid (change/update ssh keys, make backups of data). Let me know if I can help around this.

In the same vein, @scottyeager and I discussed of a weblet that could do automatic backups of other weblets on the playground. Imagine you have a wordpress weblet running and you can use a "Backup Weblet" on the TF Playground that makes a QSSS version of your wordpress database. That could be nice. For this use case, the weblet could be set with mimimum CRU and MRU, and just focus on storage, so the backup is cheaper than running the whole deployment.