What do you use to manage & update multiple servers?

13»

Comments

  • bingobangobongobingobangobongo Hosting Provider

    @IAmNix said:

    @somik said:

    Fought with ansible for a while. It wants python module called "six" to be installed on ALL of my remote nodes/vms...

    Anyone know what I am doing wrong?

    This smells like mismatched ansible version to me. Ubuntu repos especially are very behind - maybe try finding a PPA to install ansible from. Or maybe install it from pip.

    Yep definitely something between versions here… I actually don’t install anything on nodes and have a Debian prep script that runs everything needed, so any blank/base install just werks.

    Will sanitize and post here shortly!

    Rock Solid Web Hosting, VPS & VDS with a Refreshing Approach - Xeon Scalable, DDoS protection and Enterprise Hardware! HostBilby Inc.

  • localhostlocalhost OG

    Currently have my laptop and phone (juice ssh) with keys to most vms

    Realized it hard way a few days ago... if I wanted to transfer files from one vm to another it is next to impossible as all are key based auth and none have keys to login to other

    Curious what is the way to go about...

    Have a decent bunch of idlers so having n idlers keys on m machines seems too much?

  • bingobangobongobingobangobongo Hosting Provider

    @localhost said:
    Currently have my laptop and phone (juice ssh) with keys to most vms

    Realized it hard way a few days ago... if I wanted to transfer files from one vm to another it is next to impossible as all are key based auth and none have keys to login to other

    Curious what is the way to go about...

    Have a decent bunch of idlers so having n idlers keys on m machines seems too much?

    Maybe have a secondary layer of auth/keys for stuff between nodes? Then as part of setup, deploy the key used for inter node work?

    Or Ansible, since noone has mentioned it yet…

    Thanked by (1)localhost

    Rock Solid Web Hosting, VPS & VDS with a Refreshing Approach - Xeon Scalable, DDoS protection and Enterprise Hardware! HostBilby Inc.

  • localhostlocalhost OG

    @bingobangobongo said:

    @localhost said:
    Currently have my laptop and phone (juice ssh) with keys to most vms

    Realized it hard way a few days ago... if I wanted to transfer files from one vm to another it is next to impossible as all are key based auth and none have keys to login to other

    Curious what is the way to go about...

    Have a decent bunch of idlers so having n idlers keys on m machines seems too much?

    Maybe have a secondary layer of auth/keys for stuff between nodes? Then as part of setup, deploy the key used for inter node work?

    Or Ansible, since noone has mentioned it yet…

    Yeah.
    Secondary keys is needed. But wanna keep overhead of number of keys limited.
    How to securely set same key on all nodes?

    I started tinkering with ansible and got my laptop and phone keys added to authorized keys. So there's that. But actual private key sharing over the wire seems trippy?

  • WSSWSS OG

    @localhost said:
    Curious what is the way to go about...

    python3 -m HTTPServer

    Thanked by (1)localhost

    My pronouns are like/subscribe.

  • localhostlocalhost OG

    @WSS said:

    @localhost said:
    Curious what is the way to go about...

    python3 -m HTTPServer

    Thats one way I was thinking too.
    Curious if having one key across all makes sense or to do the painful way for x keys on y servers

  • AuroraZeroAuroraZero ModeratorHosting ProviderRetired

    @localhost said: Curious if having one key across all makes sense or to do the painful way for x keys on y servers

    2 keys total, one main one and a backup. If you are the only admin there is no sense making it difficult to manage or prone to human error.

    Thanked by (1)localhost

    Free Hosting at YetiNode | MicroNode| Cryptid Security | URL Shortener | LaunchVPS | ExtraVM | Host-C | In the Node, or Out of the Loop? | In my cave if you need me ping me.

  • somiksomik OG

    @localhost said:

    @WSS said:

    @localhost said:
    Curious what is the way to go about...

    python3 -m HTTPServer

    Thats one way I was thinking too.
    Curious if having one key across all makes sense or to do the painful way for x keys on y servers

    No, it's never a good thing to share ssh keys.

    I usually go with 3 ways.

    If I want to automate file transfers, I usually create a low level user on the remote server and setup a ssh key between the 2 servers (like from my main server to my backup server).

    If I only need to transfer a lot of files, I use SCP to download it to my desktop and reupload it back.

    If it's just 1 or 2 files, I use: https://github.com/somik123/python3_http_upload_progress

    @IAmNix said:

    @somik said:

    Fought with ansible for a while. It wants python module called "six" to be installed on ALL of my remote nodes/vms...

    Anyone know what I am doing wrong?

    This smells like mismatched ansible version to me. Ubuntu repos especially are very behind - maybe try finding a PPA to install ansible from. Or maybe install it from pip.

    I installed it from ubuntu's repo, when that didn't work, I reinstalled it from python3 pip, but that didn't help either. I guess it's time to either try a proper PPA or install centos 8 and try from there. Thanks for the recommendations!

    @bingobangobongo said:

    @IAmNix said:

    @somik said:

    Fought with ansible for a while. It wants python module called "six" to be installed on ALL of my remote nodes/vms...

    Anyone know what I am doing wrong?

    This smells like mismatched ansible version to me. Ubuntu repos especially are very behind - maybe try finding a PPA to install ansible from. Or maybe install it from pip.

    Yep definitely something between versions here… I actually don’t install anything on nodes and have a Debian prep script that runs everything needed, so any blank/base install just werks.

    Will sanitize and post here shortly!

    Thanks! Looking forward to it!

    Thanked by (1)localhost

    It’s OK if you disagree with me. I can’t force you to be right!
    IPv4: 32 bits of stress. IPv6: 128 bits of... well, more stress... Have anyone seen my subnet?

  • localhostlocalhost OG

    @somik said:

    @localhost said:

    @WSS said:

    @localhost said:
    Curious what is the way to go about...

    python3 -m HTTPServer

    Thats one way I was thinking too.
    Curious if having one key across all makes sense or to do the painful way for x keys on y servers

    No, it's never a good thing to share ssh keys.

    I usually go with 3 ways.

    If I want to automate file transfers, I usually create a low level user on the remote server and setup a ssh key between the 2 servers (like from my main server to my backup server).

    If I only need to transfer a lot of files, I use SCP to download it to my desktop and reupload it back.

    If it's just 1 or 2 files, I use: https://github.com/somik123/python3_http_upload_progress

    Interesting
    Well file transfer is definitely not automated.

    And its not just transfer. I may need to quickly ssh into another box right from there... I know I can connect organically from my laptop. But since inam already on server 1 so if I need to check something in server 2 it should be easy, right?

    Thanks for the quick http file server. Will bookmark it

  • nullnotherenullnothere OG

    I've not been following this fully, but a few quick hints:

    1. Assume that your SSH connections are white listed (i.e. A->B, A->C and B<->C is allowed)
    2. You have an ssh key for logins to connect from A->B and A->C
    3. You want to transfer some file(s) from B->C
    4. Use ssh-agent forwarding to provide access to your key ("resident" on A) to B (or C) thereby allowing B->C (or C->B) connections via this agent.
    5. Since B->C (or vice-versa) is possible via agent forwarding, you can now directly rsync/scp files from B->C (or vice-versa).
    6. man ssh-agent and ssh-add for options/security etc. RTFM.

    Profit?

    Thanked by (1)localhost
  • localhostlocalhost OG

    @nullnothere said:
    I've not been following this fully, but a few quick hints:

    1. Assume that your SSH connections are white listed (i.e. A->B, A->C and B<->C is allowed)
    2. You have an ssh key for logins to connect from A->B and A->C
    3. You want to transfer some file(s) from B->C
    4. Use ssh-agent forwarding to provide access to your key ("resident" on A) to B (or C) thereby allowing B->C (or C->B) connections via this agent.
    5. Since B->C (or vice-versa) is possible via agent forwarding, you can now directly rsync/scp files from B->C (or vice-versa).
    6. man ssh-agent and ssh-add for options/security etc. RTFM.

    Profit?

    I think ssh-agent forwarding may work. Thanks

  • somiksomik OG

    @localhost said:

    @nullnothere said:
    I've not been following this fully, but a few quick hints:

    1. Assume that your SSH connections are white listed (i.e. A->B, A->C and B<->C is allowed)
    2. You have an ssh key for logins to connect from A->B and A->C
    3. You want to transfer some file(s) from B->C
    4. Use ssh-agent forwarding to provide access to your key ("resident" on A) to B (or C) thereby allowing B->C (or C->B) connections via this agent.
    5. Since B->C (or vice-versa) is possible via agent forwarding, you can now directly rsync/scp files from B->C (or vice-versa).
    6. man ssh-agent and ssh-add for options/security etc. RTFM.

    Profit?

    I think ssh-agent forwarding may work. Thanks

    ssh bastion host?

    It’s OK if you disagree with me. I can’t force you to be right!
    IPv4: 32 bits of stress. IPv6: 128 bits of... well, more stress... Have anyone seen my subnet?

  • localhostlocalhost OG

    @somik said:

    @localhost said:

    @nullnothere said:
    I've not been following this fully, but a few quick hints:

    1. Assume that your SSH connections are white listed (i.e. A->B, A->C and B<->C is allowed)
    2. You have an ssh key for logins to connect from A->B and A->C
    3. You want to transfer some file(s) from B->C
    4. Use ssh-agent forwarding to provide access to your key ("resident" on A) to B (or C) thereby allowing B->C (or C->B) connections via this agent.
    5. Since B->C (or vice-versa) is possible via agent forwarding, you can now directly rsync/scp files from B->C (or vice-versa).
    6. man ssh-agent and ssh-add for options/security etc. RTFM.

    Profit?

    I think ssh-agent forwarding may work. Thanks

    ssh bastion host?

    That too...
    Any recommendations?

Sign In or Register to comment.

© LowEndSpirit 2025

ipv6 ready