A command-line tool similar to Ansible ad-hoc mode, much more efficient, implemented in Go. Only hosts with bash shell installed are supported.
Just a binary file, You don't need Python, don't need to install any software or libraries. One line of code can use the power of all CPU cores to execute shell commands concurrently on thousands of hosts. Get results in real time.
Carrier does:
- Execute shell commands on the remote hosts concurrently, display and record the results and time-consuming of the last execution.
- Copy local file/directory to the remote hosts concurrently, record the result of the last execution.
- Check the result of the last execution.
- Extract the last successful/Failed hosts.
Use carrier -h for more information about commands.
-
Config the settings in the config file, adjust the timeout to suit your environment.
-
Prepare a list of host, host is an example.
-
Execute commands concurrently. It is best to check your shell commands by using
--dry-runand test them on a few hosts first.
$ ./carrier sh "echo -n 'hostname: ';hostname;echo -n 'cpu: ';cat /proc/cpuinfo |grep processor |wc -l;echo -n 'mem: ';cat /proc/meminfo |grep MemTotal |awk '{printf \"%d\n\", \$2/1024/1024}';echo -n 'disk: ';df -m|grep '/dev/'|grep -v tmpfs|awk '{sum+=\$2};END{printf \"%d\", sum/1024}'"
192.168.220.122 OK 139.7102ms
================================
hostname: kb3
cpu: 2
mem: 3
disk: 17
192.168.220.102 OK 156.6899ms
================================
hostname: docker
cpu: 2
mem: 3
disk: 18
192.168.220.1 Failed 1.0007601s
================================
dial tcp 192.168.220.1:22: i/o timeout- Check the result of last execution, the format could be table or csv.
$ ./carrier logs
+----+-----------------+-----------+------------------+--------+----------------------------------------+------------+
| SN | IP | SUCCEEDED | STDOUT | STDERR | ERROR | DURATION |
+----+-----------------+-----------+------------------+--------+----------------------------------------+------------+
| 1 | 192.168.220.102 | true | hostname: docker | | | 156.6899ms |
| | | | cpu: 2 | | | |
| | | | mem: 3 | | | |
| | | | disk: 18 | | | |
+----+-----------------+-----------+------------------+--------+----------------------------------------+------------+
| 2 | 192.168.220.122 | true | hostname: kb3 | | | 139.7102ms |
| | | | cpu: 2 | | | |
| | | | mem: 3 | | | |
| | | | disk: 17 | | | |
+----+-----------------+-----------+------------------+--------+----------------------------------------+------------+
| 3 | 192.168.220.1 | false | | | dial tcp 192.168.220.1:22: i/o timeout | 1.0007601s |
+----+-----------------+-----------+------------------+--------+----------------------------------------+------------+- Extract the last successful/Failed hosts, you can redirect the result to a temp file and make further processing.
$ ./carrier hosts -sfalse
192.168.220.1,22,root,11111- Copy local file to the remote hosts concurrently. If the path is a directory, carrier will copy directories recursively and each file in the directory will be transferred concurrently. In order to avoid mistakes, basename of src and dst must be the same.
$ ./carrier cp -s /mnt/d/scp -d /root/scp -m 0644
192.168.220.122 OK 1.0064326s
================================
192.168.220.102 OK 1.6755888s
================================Here is an approximate benchmark for reference. Results are affected by hosts and network environment. According to the scale of concurrency, the CPU of the machine initiating the ssh command also greatly affects performance.
- shelll command: hostname
- hosts: distributed in 2 IDCs more than 1200 kilometers apart
| Hosts | Duration |
|---|---|
| 1000 | 2.5s |
| 5000 | 40s |
| 10000 | 70s |
| 27000 | 2m |
Resource consumption of the machine that sending the command to 27000 hosts
- cpu: exhaust 4 virtual cores(Intel Xeon @ 2.00GHz)
- mem: 1.8G