On Sun, Jul 16, 2017 at 1:09 AM, Samuel Sieb <samuel@xxxxxxxx> wrote: > On 07/15/2017 02:01 PM, bruce wrote: >> >> Testing Digitalocean >> >> I can create a ssh key I can create a remote instance and poulate it >> with the key to be able to do >> >> ssh foo_user@1.2.3.4 >> >> and access the vm with no issue... >> >> however:: >> >> if i spin up 1.2.3.4, as well as 5.6.7.8 >> >> how can i be on box 1.2.3.4 and do ssh foo_user@5.6.7.8 >> >> if i'm spinning up 1.2.3.4 and 5.6.7.8 what do i need to provide in >> each box o accomplish this! > > > If you use the ssh-agent and you ssh into one instance, you should be able > to ssh from there to the other instance. If you're wanting automated ssh > connections, then you either put the private key on the instances or you'll > have to create new key pairs and distribute the public keys. This is pretty > standard ssh stuff, check the docs. > --------------- Hey guys... getting back to say what i did, and it appears to work I'm spinning up a bunch of temp instances for a project The instances are up for a few hrs, then destroyed... I've got a "master" that handles the clients it needs, with the master running a basic script that currently sequentially performs a bunch of tasks on the clients. The clients have different "screen" sessions set so I can "peak" over time at the realtime progress of the different client running processes.. What I realized I needed was a "quick/dirty" method of allowing the different masters to be able to ssh/run the client cmds.. thus the need to be able to spin up the clients with whatever they needed to already be on the vm when it was created.. so.. every box has the same /home/foo/.ssh id_rsa config authorized_keys the authorized_keys file has the contents of the initial id_rsa.pub -- which is the public key the config file is used to simply "disable" the initial question about adding the key/client and yeah, in normal situations, where you have long running VMs.. this might not be the best. But in this situation, once the work is accomplished, the VMs are destroyed. thoughts/comments! thanks -------------- > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
