VirtualFlow 2.0

General

Each VirtualFlow 2.0 module can be installed and used individually. And it needs to be installed for each workflow that is run. Meaning, that if two workflows are to be run in parallel on a cluster, the VirtualFlow modules will be installed in two freely choosable folders, and the workflow will run in each of them separately.

A VirtualFlow 2.0 module (VFLP 2.0, VFVS 2.0, and VFU 2.0) can be installed via one of two ways:

Installation Location

Before installing a VirtualFlow 2.0 module, the filesystem for the installation has to be chosen. The filesystem has to be a shared storage that is available to all compute nodes that are used by VirtualFlow 2.0. Usually, there are two types of such filesystems available on a typical cluster:

  1. The home filesystem

  2. The scratch filesystem

When using a Linux cluster, the scratch filesystem should in almost all cases be used, because VirtualFlow 2.0 can be I/O intensive. And the scratch filesystem is usually able to handle higher I/O loads than the home filesystem. In addition, it can be faster as well. Another reason why the home filesystem is often not suitable is that the filesystem quota per user is often very low, too low for the often large amounts of input/output data used/generated by VirtualFlow 2.0 (only relevant if the in/output data is stored locally on the cluster rather than in the cloud).

When using AWS Batch: The home folder of the login should be used. The preconfigured AWS Batch login node that VirtualFlow provides uses a fast SSD.

Tarball Installation

The tar-archive versions of VirtualFlow 2.0 modules can be downloaded from the VirtualFlow homepage:

The files can also be obtained directly via the wget command, in the case of VFLP 2.0:

wget -O VFLP.tar.gz https://github.com/VirtualFlow/VFLP/archive/python-develop.tar.gz

In the case of VFVS 2.0:

wget -O VFVS.tar.gz https://github.com/VirtualFlow/VFVS/archive/python-develop.tar.gz

And in the case of VFU 2.0:

wget -O VFU.tar.gz https://github.com/VirtualFlow/VFU/archive/refs/heads/main.tar.gz

After downloading the tar-archive, it can be simply installed by extracting it on the desired location. In the case of VFLP 2.0:

tar -xvzf VFLP-python-develop.tar.gz

In the case of VFVS 2.0:

tar -xvzf VFVS-python-develop.tar.gz

And in the case of VFU 2.0:

tar -xvzf VFU-main.tar.gz

Cloning the GitHub Repository

VirtualFlow 2.0 can also be installed by cloning the GitHub repository. In the case of VFLP 2.0:

git clone git@github.com:VirtualFlow/VFLP.git

In the case of VFVS 2.0:

git clone git@github.com:VirtualFlow/VFVS.git

And in the case of VFU 2.0:

git clone git@github.com:VirtualFlow/VFU.git

Last updated