This document provides examples of using Arcshell to manage SSH configurations and connections. It demonstrates how to source the Arcshell module, view available functions, load SSH configuration files defining nodes and groups, edit the configuration files, add and remove nodes, define new groups, set the working node, connect to nodes via password or key, fix remote SSH directories, send a public key to authorize access, and run commands on groups of nodes. The document encourages contacting Arcshell to help build automated solutions.

2. You can source Arcshell
into your environment by
running “.
${HOME}/.arcshell”
ssh_help returns the
synopsis for each function
available in the module.
Here we limit the result
set to 20 lines so it fits
on the screen.
FYI: *_help functions are
automatically generated
from your source code using
the arcshell_docengine.sh
library.

3. This command is usually run
automatically but we are
running it manually here.
This builds up the ssh
configuration from the
various ssh.config files.
Here we see that 3 nodes
and a single group are
loaded from our
configuration files.

4. This is what our ssh.config
file looks like. It is pure
“shell” which means you can
add your own shell to the
file. You can add if then
else statements, case
statements, loops,
variables and more!
Config as shell is one of
the concepts we push within
Arcshell.
There are 3 ssh.config
files possible, delivered
(from us), global (all your
nodes), and local (runs on
single node only).

5. First we list the currently
available config files. We
see there is a global and
local file. We can edit
those files directly using
the full path or use one of
the ssh_edit_*_config
commands.
Next we run the command
that returns the templates
to use when configuring a
node or a group.

6. Delete the dev2 node.
Add it back (normally done
from a config file if you
want it to persist).
List the current nodes.
Define a new group.
List the members of the
group (ignore the error, I
fixed it!).

7. Set the working node to the
‘wahoo’.
Connect to it using a
password.

8. Check to see if the remote
.ssh directory is setup
correctly.
It isn’t. So fix it
automatically.

9. Add our local public key to
the remote authorized_keys
file using ssh_send_key.
Now we can log in and run
commands against the remote
server without a password.

10. Create a new group called
all which contains all
nodes (note this would
usually be done in a
ssh.config file if you want
it to persist).
List the members.
Run a command against each
node in the group.

11. Arcshell accelerates automation.
We would like to help you build something
amazing.
(931) 230 3317