e4_computer_engineering.beegfs.storaged role – Configure Beegfs Storage services
Note
This role is part of the e4_computer_engineering.beegfs collection (version 1.1.0).
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it use: ansible-galaxy collection install e4_computer_engineering.beegfs
.
To use it in a playbook, specify: e4_computer_engineering.beegfs.storaged
.
Entry point main
– Configure Beegfs Storage services
New in e4_computer_engineering.beegfs 1.0.0
Synopsis
Install and configure Beegfs Storage services.
Parameters
Parameter |
Comments |
---|---|
The list of storage targets and their parameters for each storage server |
|
The list of interfaces to use by the daemon This list will be used in the `conn_interfaces_file` Default: |
|
The TCP port at which the management service is responding at This option is used and documented in the file /etc/beegfs/beegfs-storage.conf Default: |
|
The UDP port at which the management service is responding at This option is used and documented in the file /etc/beegfs/beegfs-storage.conf Default: |
|
The RDMA buffer count allocated for the communication conn_rdma_buf_num * conn_rdma_buf_size This option is used and documented in the file /etc/beegfs/beegfs-storage.conf Default: |
|
The RDMA buffer size allocated for communication conn_rdma_buf_num * conn_rdma_buf_size This option is used and documented in the file /etc/beegfs/beegfs-storage.conf Default: |
|
The TCP port at which the storage service is responding at This option is used and documented in the file /etc/beegfs/beegfs-storage.conf Default: |
|
The UDP port at which the storage service is responding at This option is used and documented in the file /etc/beegfs/beegfs-storage.conf Default: |
|
Name of the device that will mount the beegfs storage partition Note that /dev/ must be omitted because it is already present in the path of the device |
|
Where log entries for the Beegfs management daemon should go This option is used and documented in the file /etc/beegfs/beegfs-storage.conf Choices:
|
|
An ID that must be unique among metadata and storage target mirror group definitions Even if Beegfs allows to have the same ID definition among metadata and storage mirrror groups we do not support it You must specify the same mirrorgroup id in two and only two storage targets to have a mirror relationship created The order in which the targets appear in the storaged_server_targets structure defines if these are primaries or secondaries Default: |
|
Enable the quota enforcement feature This option is used and documented in the file /etc/beegfs/beegfs-storage.conf Choices:
|
|
A name for the storagepool that the target must be part of The name must be unique inside the cluster Default: |
|
The storage pool id to assign the storage target The name must be unique inside the cluster Default: |
|
The address at which the management service is responding at This option is used and documented in the file /etc/beegfs/beegfs-storage.conf Default: |
|
Timeout in seconds before the target is considered “Offline” This option is used and documented in the file /etc/beegfs/beegfs-storage.conf Default: |
|
The ID to assign to the storage target object Albeit not required by Beegfs, the ID needs to be unique in the cluster The ID is used to create the target directory mountpoint `/data/beegfs_storage/t<target_id>` The ID is used to setup the Buddy Mirror relationship The ID is used to setup the Storage Pool membership Default: |
|
The file read size from filesystem This option is used and documented in the file /etc/beegfs/beegfs-storage.conf Default: |
|
The file write size on filesystem This option is used and documented in the file /etc/beegfs/beegfs-storage.conf Default: |
|
Number of worker threads to assign to the beegfs-storage.service This option is used and documented in the file /etc/beegfs/beegfs-storage.conf Default: |
|
Start the `beegfs-storage.service` or `beegfs-storage@.service` Choices:
|