Skip to main content
BeeGFS on NetApp with E-Series Storage

Deployment overview

Contributors netapp-jsnyder mcwhiteside netapp-jolieg codyharryman
PDFs

BeeGFS on NetApp can be deployed to validated file and block nodes using Ansible with NetApp’s BeeGFS building block design.

Ansible collections and roles

The BeeGFS on NetApp solution is deployed using Ansible, a popular IT automation engine that automates application deployments. Ansible uses a series of files collectively known as the inventory, which models the BeeGFS file system you want to deploy.

Ansible allows companies like NetApp to expand on built-in functionality using collections available on Ansible Galaxy (see NetApp E-Series BeeGFS collection). Collections include modules that perform specific functions or tasks (such as creating an E-Series volume) and roles that can call multiple modules and other roles. This automated approach reduces the time needed to deploy the BeeGFS file system and the underlying HA cluster. Additionally, it simplifies maintaining and expanding the cluster and BeeGFS filesystem.

For additional details, see Learn about the Ansible inventory.

Note Because numerous steps are involved in deploying the BeeGFS on NetApp solution, NetApp does not support manually deploying the solution.

Configuration profiles for BeeGFS building blocks

The deployment procedures cover the following configuration profiles:

  • One base building block that includes management, metadata, and storage services.

  • A second building block that includes metadata and storage services.

  • A third building block that includes only storage services.

These profiles demonstrate the full range of recommended configuration profiles for the NetApp BeeGFS building blocks. For each deployment, the number of metadata and storage building blocks or storage services-only building blocks may vary depending on capacity and performance requirements.

Overview of deployment steps

Deployment involves the following high-level tasks:

Hardware deployment

  1. Physically assemble each building block.

  2. Rack and cable hardware.
    For detailed procedures, see Deploy hardware.

Software deployment

  1. Set up file and block nodes.

    • Configure BMC IPs on file nodes

    • Install a supported operating system and configure management networking on file nodes

    • Configure management IPs on block nodes

  2. Set up an Ansible control node.

  3. Tune system settings for performance.

  4. Create the Ansible inventory.

  5. Define Ansible inventory for BeeGFS building blocks.

  6. Deploy BeeGFS using Ansible.

  7. Configure BeeGFS clients.

Note The deploy procedures includes several examples where text needs to be copied to a file. Pay close attention to any inline comments denoted by “#” or “//” characters for anything that should or can be modified for a specific deployment. For example:
beegfs_ha_ntp_server_pools: # THIS IS AN EXAMPLE OF A COMMENT!
- "pool 0.pool.ntp.org iburst maxsources 3"
- "pool 1.pool.ntp.org iburst maxsources 3"

Derivative architectures with variations in deployment recommendations: