Download and Installation of Packages

Note: If you are installing BeeGFS for the first time, you should take a look at the Section System Architecture from the User Guide to see what kinds of services you will need to install.

Table of Contents (Page)

  1. Package Repositories
  2. Package Descriptions
  3. Proceed to next Step...

Package Repositories

To start an installation of BeeGFS:
  1. Download the BeeGFS repository file for your Linux distribution from Table 1 to the specified directory.
  2. Make the repository available on all nodes, either by storing it in your node boot image or by copying it to all nodes that you want to use with BeeGFS.
  3. Install the BeeGFS services with your distribution's package manager (e.g. "yum install beegfs-storage" on RedHat). An overview of available packages is provided in the next section.

If you want to download the packages directly instead of using repositories, you can find them here.

Note: BeeGFS can be used in heterogeneous environments with different architectures and/or distributions.

Linux Base DistributionVersionPackage ManagerRepository File
(Save to...)
Red Hat Linux
(and derivatives,
e.g. Fedora)
6.x yum
(Save to: /etc/yum.repos.d/)
7.x yum
(Save to: /etc/yum.repos.d/)
Suse Linux
(and derivatives,
e.g. OpenSuse)
12.x zypper
(Save to: /etc/zypp/repos.d/)
Debian GNU Linux
(and derivatives,
e.g. Ubuntu)
(Save to: /etc/apt/sources.list.d/)
(Save to: /etc/apt/sources.list.d/)
Table 1: BeeGFS Repository Files

Note: When using apt, please do not forget to run "apt-get update" after adding the repository.

Repository Signature Keys
BeeGFS repositories and packages are digitally signed. If you would like to verify the package signatures, you can add the public BeeGFS GPG key to your package manager:
To add the key on RedHat/SuSE, use the following command:
$ rpm --import

To add the key on Debian, use the following command:
$ wget -q -O- | apt-key add -

Package Descriptions

Table 2 shows the roles that need to be defined to run BeeGFS and the corresponding package for each role. BeeGFS has been designed to allow running any combination of services (e.g., metadata and storage server) on the same node. Additional information about the roles of BeeGFS nodes can be found in the User Guide.

Management Server (one node)
  • Manages configuration and group membership
  • Hostname or IP address must be known by other nodes at service start time
Metadata Server (at least one node)
  • Stores directory information and allocates file space on storage servers
Storage Server (at least one node)
  • Stores raw file contents
  • Kernel module to mount the file system
  • Requires userspace helper daemon for logging and hostname resolution
RDMA support
  • libraries for RDMA support for Metadata and Storage Services
Admon - Administration and Monitoring Server (optional)
  • Provides graphical interface
  • Continuous monitoring of servers
  • Live statistics
  • beegfs-mon must not be installed on the same server
Mon - InfluxDB based Monitoring Server (optional)
  • Continuous monitoring of servers
  • Live statistics
  • beegfs-admon must not be installed on the same server
BeeGFS utilities for administrators
  • beegfs-ctl tool for command-line administration
  • beegfs-fsck tool for file system checking
  • Several small helper scripts
BeeGFS Common
  • Common files for all packages
Table 2: BeeGFS Roles and corresponding Packages

Note: The management server daemon and the optional Admon daemon have only moderate RAM and CPU requirements. As these services are not critical for file system performance, you do not need to run them on a dedicated machine. They are typically running on the cluster master node.

Each BeeGFS service (including the client) comes with:
After installation, all services will be set to automatic startup at system boot. If you do not want to run BeeGFS services automatically during system boot, use e.g. the chkconfig tool to disable automatic startup.

Another way to disable BeeGFS services startup would be to set START_SERVICENAME="NO" in the corresponding service config file (/etc/default/beegfs-X). Note that this would have the side effect of completely disabling init script startup of the service, not only during system boot.

Installation does not start any of the services directly, because there are a few configuration options that need to be set before the first startup. These will be described in the following sections.

Proceed to next Step...

Next step: Building Kernel Modules and OpenTk Library

Back to table of contents
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki