Jarvis-CD

Jarvis-CD is a unified platform for deploying various applications, including storage systems and benchmarks. Many applications have complex configuration spaces and are difficult to deploy across different machines.

We provide a builtin repo which contains various applications to deploy. We refer to applications as "jarivs pkgs" which can be connected to form "deployment pipelines".

Installation

IoWarp

If you installed iowarp already, Jarvis-CD is a dependency. No need to install anything further. Go to the next section.

Spack

Install Spack

cd ${HOME}
git clone https://github.com/spack/spack.git
cd spack
git checkout tags/v0.22.2
echo ". ${PWD}/share/spack/setup-env.sh" >> ~/.bashrc
source ~/.bashrc

Clone the IOWarp Spack Repo

cd ${HOME}
git clone https://github.com/iowarp/iowarp-install.git
spack repo add iowarp-install/iowarp-spack

Install

spack external find python
spack install py-ppi-jarvis-cd

Spack packages must be loaded to use them. You'll have to do this for each new terminal.

spack load py-ppi-jarvis-cd

Pip

Jarvis-Util

Jarvis-CD depends on jarvis-util. jarvis-util contains functions to execute binaries in python and collect their output.

git clone https://github.com/grc-iit/jarvis-util.git
cd jarvis-util
python3 -m pip install -r requirements.txt
python3 -m pip install -e .

Jarvis-CD

cd /path/to/jarvis-cd
python3 -m pip install -r requirements.txt
python3 -m pip install -e .

Net Test

Network test tool for identifying valid networks.

spack install ppi-chi-nettest

Building the Jarvis Configuration

Jarvis packages provide 3 ways to configure Hermes:

Single Machine

Bootstrapping for a single-node machine

For testing on a single node, use:

jarvis bootstrap from local

Existing Machine

Bootstrapping from a specific machine

Jarvis has been pre-configured on some machines. This includes machines at IIT, Sandia, and Argonne.

To bootstrap on one of them, run the following:

jarvis bootstrap from [machine-name]

See available machines with:

jarvis bootstrap list

NOTE: If you are unsure which machine is yours, you probably should read the New Configuration tab instead. Don't bootstrap from a random machine -- it will break your deployments.

New Configuration

Initialize jarvis configuration

A configuration can be generated as follows:

jarvis init [CONFIG_DIR] [PRIVATE_DIR] [SHARED_DIR]

• CONFIG_DIR: A directory where jarvis metadata for pkgs and pipelines are stored. This directory can be anywhere that the current user can access.
• PRIVATE_DIR: A directory which is common across all machines, but stores data locally to the machine. Some jarvis pkgs require certain data to be stored per-machine. OrangeFS is an example.
• SHARED_DIR: A directory which is common across all machines, where each machine has the same view of data in the directory.

For a personal machine, these directories can be the same directory.

Set or Change the active Hostfile

The hostfile contains the set of nodes that the pipeline will run over. This is structured the same way as a traditional MPI hostfile.

An example hostfile:

ares-comp-20
ares-comp-[21-25]

To set the active hostfile, run:

jarvis hostfile set /path/to/hostfile

Note that every time you change the hostfile, you will need to update the pipeline. Jarvis does not automatically detect changes to this file.

jarvis ppl update

Building a Resource Graph

NOTE: This step only needs to be run if you did jarvis bootstrap from local or jarvis init. If you bootstrap from a specific machine, then skip this section.

The resource graph is a snapshot of your systems network and storage. Many packages depend on it for their configurations. The Hermes I/O system, for example, uses this to identify valid networks and buffering locations.

jarvis rg build

This command only needs to be run once for the duration of Jarvis (or whenever your resources change). For example, if you get a new hard drive, you should re-run this command.

NOTE: Make sure the hostfile contains a representative set of nodes. General rules:

1. If you are trying to do multi-node deployments, make sure the hostfile contains at least two nodes before running this command. This will allow us to introspect valid networks between hosts.
2. In addition, make sure that the nodes are representative of the machine. For example, if you plan to do multi-node deployments, the master node probably should not even be introspected.