schedulerinputparams.rst

Input parameters for the cluster

These parameters are located in input/omnia_config.yml, input/security_config.yml, input/telemetry_config.yml and [optional] input/storage_config.yml.

Caution!

Do not remove or comment any lines in the input/omnia_config.yml, input/security_config.yml and [optional] input/storage_config.yml file.

omnia_config.yml

security_config.yml

storage_config.yml

Name	Details
nfs_client_params JSON list Optional	If NFS client services are to be deployed, enter the configuration required here in JSON format. The server_ip provided should have an explicit NFS server running. If left blank, no NFS configuration takes place. Possible values include: 1. Single NFS file system: A single filesystem from a single NFS server is mounted. Sample value: - { server_ip: xx.xx.xx.xx, server_share_path: “/mnt/share”, client_share_path: “/mnt/client”, client_mount_options: “nosuid,rw,sync,hard,intr” } 2. Multiple Mount NFS file system: Multiple filesystems from a single NFS server are mounted. Sample values: - { server_ip: xx.xx.xx.xx, server_share_path: “/mnt/server1”, client_share_path: “/mnt/client1”, client_mount_options: “nosuid,rw,sync,hard,intr” } - { server_ip: xx.xx.xx.xx, server_share_path: “/mnt/server2”, client_share_path: “/mnt/client2”, client_mount_options: “nosuid,rw,sync,hard,intr” } 3. Multiple NFS file systems: Multiple filesystems are mounted from multiple servers. Sample Values: - { server_ip: zz.zz.zz.zz, server_share_path: “/mnt/share1”, client_share_path: “/mnt/client1”, client_mount_options: “nosuid,rw,sync,hard,intr”} - { server_ip: xx.xx.xx.xx, server_share_path: “/mnt/share2”, client_share_path: “/mnt/client2”, client_mount_options: “nosuid,rw,sync,hard,intr”} - { server_ip: yy.yy.yy.yy, server_share_path: “/mnt/share3”, client_share_path: “/mnt/client3”, client_mount_options: “nosuid,rw,sync,hard,intr”} Default value: { server_ip: , server_share_path: , client_share_path: , client_mount_options: }
beegfs_support boolean Optional	This variable is used to install beegfs-client on compute and manager nodes Choices: false <- Default true
beegfs_rdma_support boolean Optional	This variable is used if user has RDMA-capable network hardware (e.g., InfiniBand) Choices: false <- Default true
beegfs_ofed_kernel_modules_path string Optional	The path where separate OFED kernel modules are installed. Default value: "/usr/src/ofa_kernel/default/include"
beegfs_mgmt_server string Required	BeeGFS management server IP. Note: The provided IP should have an explicit BeeGFS management server running .
beegfs_mounts string Optional	Beegfs-client file system mount location. If storage_yml is being used to change the BeeGFS mounts location, set beegfs_unmount_client to true Default value: "/mnt/beegfs"
beegfs_unmount_client boolean [1] Optional	Changing this value to true will unmount running instance of BeeGFS client and should only be used when decommisioning BeeGFS, changing the mount location or changing the BeeGFS version. Choices: false <- Default true
beegfs_client_version string Optional	Beegfs client version needed on compute and manager nodes. Default value: 7.2.6
beegfs_version_change boolean [1] Optional	Use this variable to change the BeeGFS version on the target nodes. Choices: false <- Default true
beegfs_secret_storage_filepath string Required	The filepath (including the filename) where the connauthfile is placed. Required for Beegfs version >= 7.2.7 Default values: /home/connauthfile

telemetry_config.yml

[1]	(1, 2) Boolean parameters do not need to be passed with double or single quotes.

Click here for more information on FreeIPA, LDAP, Telemetry, BeeGFS or, NFS.