Getting Started

adminware must be installed within /opt using:

cd /opt
git clone https://github.com/alces-software/adminware.git
cd adminware
make setup

Commands' Structure

The command line interface of Adminware is laid out as follows:

exit - exits the CLI.

help - displays help for the current level's commands.

run - command group used for running tools - works in parallel across nodes.

• run <TOOL...> NODE(S) [ARGUMENTS]
  • Runs tool TOOL on NODE(S).
  • If a tool marked as being interactive only (see 'Adding Tools') and you attempt to run it on more than one node it will cancel and an error will be thrown.
  • Additionally a tool marked as interactive will open an interactive ssh session with the node when ran
  • Optionally, arguments for the shell command can be provided.

view - inspect groups and tools.

• view group [GROUP]
  • Lists all the nodes in group GROUP
  • If no group is given, a list of all groups can be found in the command's help display
• view tool [TOOL...]
  • Shows info about tool TOOL
  • Displays the tool's name, description, command, whether it must be ran interactively and the contents of its working directory
  • If a tool consisting of other tools is given, in the command's help display it lists the sub-tools of that tool.
  • If NAMESPACE(S) is not given, it lists at the highest level tools directory.

status - retrieve the past job results

• status [TOOL...]
  • By default it returns the last run of each tool on all the nodes
  • The nodes can be filtered using --node and --group
  • The TOOL input will filter by tool name/group
  • All the past results are retrieved by the --history flag. Without this flag only the most recent job is returned for each node/tool combination.
  • The special --job input will retrieve a single job by id

Error Codes

The exit code for the remote command is saved within the database. The meaning of the exit code is determined by the underlying command and will range from 0-255.

All negative exit codes indicate an internal Adminware error. The exit codes and their meanings are as follows:

Error Code	Description
-1	SSH Connection Error
-2	General Error
-3	Interactive Job
-4	Abandoned Job Error

-1: SSH Connection Error

An initial SSH connection could not be established with the node.

NOTE: This error code will only be issued for handled errors. It is still possible for unhandled SSH errors to be issued a different error code.

-2: General Error

An error has occurred that concerns the job. See the jobs STDERR for more details.

-3: Interactive Job

The tool has been ran in an interactive shell. The STDOUT, STDERR, and exit code are not available. This does not mean the job failed, instead its status is undetermined.

-4: Abandoned Job Error

The job has been created and queued to be ran but has since been abandoned. This indicates the job was never ran, but this can not been known for certain.

Possible Causes:

1. Adminware was sent an interrupt,
2. An uncaught SSH connection error has occurred,
3. The connection was lost to the adminware appliance, or
4. An unexpected error occurred before the job was started.

Adding Tools

Tools can be ran interactively and non-interactively; a tool will automatically be ran interactively if selected with a single node. Interactive mode establishes an interactive shell session, this allows for full screen applications (e.g. vi, top, bash). Interactive mode does not save anything to the database. Non-interactive mode allows for multiple tools to be ran over mutliple nodes with single line output. The full results are logged to the database.

Tools are automatically picked up from config files stored at:

/var/lib/adminware/tools/[<optional-directories>/].../<tool-name>/config.yaml

The config.yaml files cannot have directories as their siblings, although there can be other files in the same directories.

The config files should follow the following format:

# Could be system command like `uptime` or tool dir command like
# `./script.rb`.
command: command_to_run

# Full help text for this tool, it will be picked up and displayed in full when `help
# is displayed for this tool in `run` commands.
help: command_help

# A flag stating that this tool's command is only to be ran in an interactive
# shell. It's value must be "True" for this to take effect. If a tool marked as
# interactive only is ran as part of another tool or on more than one node an error
# will be thrown.
interactive: True

# Runs the command in reporting mode. The standard output of the remote command will
# be dumped to the screen instead of the exit code.
report: True

# The following list forms the arguments for the command line. They are set as
# bash shell variables when running the command. This allows them to be used
# within the command.
# Argument names are comprised of lowercase alphanumerics and must start with
# a letter.
# NOTE: this key is optional
arguments:
  - arg1
  - arg2
  ...

Configuring Run Parameters

Maximum SSH Operations

There is an inbuilt limit on how many parallel ssh operations can be made. This is not strictly the number of open connections, but however the number of actions that can be preformed over them.

The default maximum is 100, but it can be set from the environment with: ADMINWARE_MAX_SSH

Delay Between Jobs

There is a minor delay between starting new Jobs. This causes the initial SSH connections to be spread out whist the Jobs are starting.

The delay defaults to 0.2s, but can be changed by setting: ADMINWARE_START_DELAY

Development setup

It is recommended that Adminware is developed locally (so you have all your local development tools available) and synced, run, and tested in a clean remote environment (to be in an environment close to what it will normally use in production, and to avoid polluting or depending on things in your local environment).

You can try adapting this setup, but this is what I'm doing (which works):

1. Have remote CentOS/RedHat EL7 machine available to sync and develop on, with root access available - I have:

[root@bob adminware]# uname -a
Linux bob 3.10.0-862.11.6.el7.x86_64 #1 SMP Tue Aug 14 21:49:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

2. Then locally:

make rsync PASSWORD="password for machine" IP="ip of machine"

3. Remotely:

cd /tmp/adminware
make development-setup

Development process

• To keep remote machine as setup above constantly in sync with local changes (leave this running):

  gem install rerun # If you don't have this already.
  make watch-rsync PASSWORD="password for machine" IP="ip of machine"

• To run synced, development admin CLI remotely:

  cd /tmp/adminware
  bin/starter [ADMIN_COMMANDS_AND_ARGS]

• To run tests remotely:

  make unit-test