Input parameters for the cluster
These parameters are located in input/omnia_config.yml
, input/security_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
Variables |
Details |
---|---|
scheduler_type
|
Default value: |
mariadb_password
|
|
k8s_version
|
|
k8s_cni
|
|
k8s_pod_network_cidr
|
|
docker_username
|
|
docker_password
|
|
ansible_config_file_path
|
|
enable_omnia_nfs
|
|
omnia_usrhome_share
|
Default value: “/home/omnia-share” |
security_config.yml
Parameter |
Details |
---|---|
|
Boolean indicating whether FreeIPA is required or not.
|
|
Sets the intended realm name.
|
|
Password authenticating admin level access to the Directory for system management tasks. It will be added to the instance of directory server created for IPA.Required Length: 8 characters. The password must not contain -,, ‘,” |
|
“admin” user password for the IPA server on RockyOS. |
|
Boolean indicating whether ldap client is required or not.
|
|
Sets the intended domain name.
|
|
LDAP server IP. Required if |
|
For a TLS connection, provide a valid certification path. For an SSL connection, ensure port 636 is open.
|
|
This variable accepts Server Certificate Path. Make sure certificate is present in the path provided. The certificate should have .pem or .crt extension. This variable is mandatory if connection type is TLS.
|
|
This variable accepts the user home directory path for ldap configuration. If nfs mount is created for user home, make sure you provide the LDAP users mount home directory path.
|
|
If LDAP server is configured with bind dn then bind dn user to be provided. If this value is not provided (when bind is configured in server) then ldap authentication fails. Omnia does not validate this input. Ensure that it is valid and proper.
|
|
If LDAP server is configured with bind dn then bind dn password to be provided. If this value is not provided (when bind is configured in server) then ldap authentication fails. Omnia does not validate this input. Ensure that it is valid and proper. |
|
Boolean value deciding whether security features are enabled on the Login Node.
|
storage_config.yml
Name |
Details |
---|---|
|
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:
3. Multiple NFS file systems: Multiple filesystems are mounted from multiple servers.
Sample Values:
Default value: |
|
This variable is used to install beegfs-client on compute and manager nodes Choices:
|
|
This variable is used if user has RDMA-capable network hardware (e.g., InfiniBand) Choices:
|
|
The path where separate OFED kernel modules are installed.
|
|
BeeGFS management server IP. Note: The provided IP should have an explicit BeeGFS management server running . |
|
|
|
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:
|
|
Beegfs client version needed on compute and manager nodes.
|
|
Use this variable to change the BeeGFS version on the target nodes. Choices:
|
|
|
Click here for more information on FreeIPA, LDAP, BeeGFS or, NFS.
Note
- The
input/omnia_config.yml
file is encrypted on the first run of the provision tool: To view the encrypted parameters:
ansible-vault view omnia_config.yml --vault-password-file .omnia_vault_key
To edit the encrypted parameters:
ansible-vault edit omnia_config.yml --vault-password-file .omnia_vault_key
If you have any feedback about Omnia documentation, please reach out at omnia.readme@dell.com.