BeeOND

BeeOND™: BeeGFS On Demand



Table of Contents (Page)

  1. What is BeeOND?
  2. Advantages
  3. Installation
  4. Usage
 


What is BeeOND?


BeeOND ("BeeGFS On Demand") was developed to enable easy creation of one or multiple BeeGFS instances on the fly. This ability can be useful in many different use-cases, for example in cloud environments, but especially to create temporary work file systems. BeeOND is typically used to aggregate the performance and capacity of internal SSDs or hard disks in compute nodes for the duration of a compute job. This provides addtional performance and a very elegant way of burst buffering.

BeeOND on Compute Nodes

BeeOND Overview
 

Nowadays, most HPC cluster systems use a global storage system based on a parallel file system on dedicated servers to enable high throughput. Compute nodes are often equipped (or can easily be equipped) with internal hard disks or SSDs, which could deliver an additional performance advantage. The problem with the internal drives in compute nodes is that they provide neither the advantage of a single name space across multiple machines nor the flexibility and performance of a shared parallel file system. BeeOND solves this problem by creating a shared parallel filesystem on a "per-job basis" across all compute nodes that are part of the particular compute job, exactly for the runtime of the job.

BeeOND can be used independent of whether the global shared cluster file system is based on BeeGFS or on other technology. BeeOND simply creates a new separate mountpoint. Any of the standard tools (like cp or rync) can be used to transfer data into and out of BeeOND, but the BeeOND package also contains a parallel copy tool to transfer data between BeeOND instances and another file system, such as your persitent global BeeGFS.

Due to the very simplified startup, it is easy to integrate BeeOND with workload managers, such as Torque or Slurm. Torque, for example, provides prologue and epilogue scripts, which will be executed on the first node assigned to a job. As BeeOND can start and stop new BeeGFS instances with just one single command, you can easily add it to these scripts to start BeeOND when a compute job starts and stop if when the job is finished. Please refer to the documentation of your workload manager for similar mechanisms.


Advantages


The main advantages of the typical BeeOND use-case on compute nodes are:
 

Installation


BeeOND is available as standard package in the normal BeeGFS repositories and can be installed by using your distribution's package manager. For example, if running Red Hat, you can simply use yum on all nodes in your cluster:
$ ssh root@nodeXX
$ yum install beeond


For operation, BeeOND needs the BeeGFS server and client components. Therefore, the respective packages are set as dependency and will be installed automatically.

If you want to use RDMA in the BeeOND environment you have to enable it for the client module as usual. This can be done by editing /etc/beegfs/beegfs-client-autobuild.conf as described in Building the Client Kernel Module.


Usage


The main component of the BeeOND package is a script to start and stop a BeeGFS file system instance. This script is located at /opt/beegfs/sbin/beeond. A BeeOND instance can be controlled using "beeond start" and "beeond stop".

The easiest way to start a BeeOND instance is running beeond with the following set of parameters:
$ beeond start -n nodefile -d /data/beeond -c /mnt/beeond

Description of start parameters:
To shut a BeeOND instance down, you only need to use the "stop" mode of the script, similar to startup:
$ beeond stop -n nodefile -L -d

Description of stop parameters:
For a more detailed information and additional parameters, please see:
$ beeond -h

The tool "beeond-cp" can be used to perform a parallel stage-in and stage-out of the data you need. If we assume, that you need two working sets, which are located in /scratch/first and /scratch/second you can use the following command to copy the data into /mnt/beeond:
$ beeond-cp copy -n nodefile /projects/dataset01 /projects/dataset02 /mnt/beeond

Description of copy parameters:
For a more detailed information, please see:
$ beeond-cp -h




Back to User Guide - Table of Contents
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki