Skip to content

Commit

Permalink
Merge pull request #1385 from cgoveas/devel
Browse files Browse the repository at this point in the history
Updating documentation
  • Loading branch information
sujit-jadhav authored Jul 25, 2022
2 parents 2264541 + e94de8d commit 6ad5fd1
Show file tree
Hide file tree
Showing 3 changed files with 31 additions and 0 deletions.
19 changes: 19 additions & 0 deletions docs/Security/FreeIPA_User_Creation.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,3 +57,22 @@
7. The user has been assigned appropriate permissions to execute slurm jobs. Jobs can be executed

` srun --nodes 1 --ntasks-per-node 1 --partition normal hostname`

## Mounting user home directories to the NFS Share
### Configuring ipa client services on the NFS node
1. Log into the NFS node using any user account.
2. Update `/etc/host` with the IPA server host details. <br>
```text
vi /etc/hosts
xx.xx.xx.xx ipaserver.omnia.test
```
3. Use dnf to install ipa-client on the NFS server. <br>
`dnf install ipa-client -y`
4. Configure ipa-client services using the following command: <br>
`ipa-client-install --domain omnia.test --server ipaserver.omnia.test --principal admin --password kerberos --force-join --enable-dns-updates --force-ntpd --mkhomedir -U`

>> **Note**:
>> * The password to the admin account on the IPA server for the management server is available in `control_plane/input_params/login_vars.yml`. If your IPA server is on the login node, the password will be available in `input_params/omnia_config.yml`.
>> * The IPA server and the target cluster nodes do not have to be in the same domain. However, the server has to be reachable to all nodes.
5. (Optional) Set up the default home directory for IPA users with the command: `ipa config-mod --homedirectory=/mnt/users/ `
12 changes: 12 additions & 0 deletions docs/Troubleshooting/FAQ.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,18 @@ If `control_plane.yml` has run, a version file is created here: `/opt/omnia/omni
**Resolution**:
* Ensure that the input paths are a perfect match down to the character to avoid any errors.

## Why does the task 'control plane security: Authenticate as admin' fail?
**Potential Cause**: <br>
The required services are not running on the control plane. Verify the service status using: <br>
`systemctl status sssd-kcm.socket` <br>
`systemctl status sssd.service` <br>
**Resolution**: <br>
* Restart the services using: <br>
`systemctl start sssd-kcm.socket` <br>
`systemctl start sssd.service` <br>
* Re-run `control_plane.yml` using the tags `init` and `security`. <br>
`Ansible-playbook control_plane.yml –tags init,security`

## Why does the task 'Gather facts from all the nodes' stuck when re-running `omnia.yml`?
**Potential Cause**: Corrupted entries in the `/root/.ansible/cp/` folder. For more information on this issue, [check this out](https://github.com/ansible/ansible/issues/17349)! <br>
**Resolution**: Clear the directory `/root/.ansible/cp/` using the following commands: <br>
Expand Down
Binary file modified docs/images/Omnia_Flow.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 6ad5fd1

Please sign in to comment.