Updating NFS options

Signed-off-by: cgoveas <[email protected]>

control_plane/input_params/powervault_vars.yml

@@ -28,7 +28,7 @@ powervault_locale: "English"
 
 # Specify the system name to identify the system
 # Default value:  "Uninitialized_Name"
-# Length should be less than 30 and it should not contain space.
+# Length should be less than 30, and it should not contain space.
 # Optional
 powervault_system_name: "Unintialized_Name"
 

docs/Input_Parameter_Guide/Control_Plane_Parameters/login_vars.md

@@ -15,7 +15,7 @@ This file is located in [/control_plane/input_params](../../../control_plane/inp
 | ethernet_switch_password        |                          | Password used to login to the Ethernet Switch  <br> Forbidden Characters:  -,\, ',"                                                                                                                                                           |
 | ib_username                     |                          | Username used to login to the Infiniband Switch  <br> Forbidden Characters:  -,\, ',"                                                                                                                                                         |
 | ib_password                     |                          | Password used to login to the Infiniband Switch  <br> Forbidden Characters:  -,\, ',"                                                                                                                                                         |
-| powervault_username         |                          | Username used to login to the PowerVault    <br> Forbidden Characters:    -,\, ',"                                                                                                                                                            |
-| powervault_password         |                          | Password used to login to the PowerVault    <br> Forbidden Characters:    -,\, ',"                                                                                                                                                            |
+| powervault_username             |                          | Username used to login to the PowerVault    <br> Forbidden Characters:    -,\, ',"                                                                                                                                                            |
+| powervault_password             |                          | Password used to login to the PowerVault    <br> Forbidden Characters:    -,\, ',"                                                                                                                                                            |
 | ms_directory_manager_password   |                          | Password to authenticate Admin level access to the directory for system   management tasks and will be added to the instance of directory server   created for IPA. <br> Minimum Length: 8 characters <br> Forbidden   Characters:  -,\, ',"  |
 | ms_kerberos_admin_password      |                          | Password authenticating the 'admin' account on the IPA server. If 389ds   is in use, this field authenticates the Kerberos Admin.                                                                                                             |

docs/Installation_Guides/INSTALL_CONTROL_PLANE.md

@@ -181,7 +181,7 @@ If AWX is set up by the control plane (That is, when `awx_web_support` in `base_
 
 >> **Note**: The AWX configurations are automatically performed by Omnia, and Dell Technologies recommends that you do not change the default configurations that are provided by Omnia as the functionality may be impacted.  
 
-The AWX UI/ Ansible CLI can be used to run playbooks such as `omnia.yml`. To set up red hat subscription, Slurm, Kubernetes, JupyterHub , configure devices etc, check out [Using Playbooks](USING_PLAYBOOKS.md).
+The AWX UI/ Ansible CLI can be used to run playbooks such as `omnia.yml`. To set up red hat subscription, Slurm, Kubernetes, JupyterHub , configure devices etc., check out [Using Playbooks](USING_PLAYBOOKS.md).
 
 
 ## Creating a new cluster 

docs/NETWORK_TOPOLOGY_DEDICATED.md

@@ -7,7 +7,7 @@ Depending on internet access for host nodes, there are two ways to achieve a ded
 When all compute nodes have their own public network access, `primary_dns` and `secondary_dns` in `base_vars.yml` become optional variables as the control plane is not required to be a gateway to the network. The network design would follow the below diagram: <br>
 ![Dedicated Setup with dedicated public nic on compute nodes](images/Omnia_NetworkConfig_Inet.png)
 2. Dedicated Setup with single NIC on compute nodes <br>
-When all compute nodes rely on the control plane for public network access, the variables `primary_dns` and `secondary_dns` in `base_vars.yml` are used to indicate that the control plane is the gateway for all compute nodes to get internet access. Since all public network traffic will be routed through the control plane, the user may have to take precautions to avoid bottlenecks in such a set up. <br>
+When all compute nodes rely on the control plane for public network access, the variables `primary_dns` and `secondary_dns` in `base_vars.yml` are used to indicate that the control plane is the gateway for all compute nodes to get internet access. Since all public network traffic will be routed through the control plane, the user may have to take precautions to avoid bottlenecks in such a set-up. <br>
 ![Dedicated Setup with single NIC on compute nodes](images/Omnia_NetworkConfig_NoInet.png)
 
 

docs/PreRequisites/OMNIA_PreReqs.md

@@ -49,5 +49,4 @@ To open the ports required, use the following steps:
   1. **Single NFS node** : A single NFS filesystem is mounted from a single NFS server. The value of `nfs_bolt_on` would be <br> `- { server_ip: xx.xx.xx.xx, server_share_path: "/mnt/share", client_share_path: "/mnt/client", client_mount_options: "nosuid,rw,sync,hard,intr 0 0" }`
   2. **Multiple Mount NFS Filesystem**: Multiple filesystems are mounted from a single NFS server. The value of `nfs_bolt_on` would be <br>` - { server_ip: xx.xx.xx.xx, server_share_path: "/mnt/server1", client_share_path: "/mnt/client1", client_mount_options: "nosuid,rw,sync,hard,intr 0 0" }` <br> `- { server_ip: xx.xx.xx.xx, server_share_path: "/mnt/server2", client_share_path: "/mnt/client2", client_mount_options: "nosuid,rw,sync,hard,intr 0 0" }`
   3. **Multiple NFS Filesystems**: Multiple filesystems are mounted from multiple NFS servers. The value of `nfs_bolt_on` would be <br> ` - { server_ip: xx.xx.xx.xx, server_share_path: "/mnt/server1", client_share_path: "/mnt/client1", client_mount_options: "nosuid,rw,sync,hard,intr 0 0" }` <br> `- { server_ip: yy.yy.yy.yy, server_share_path: "/mnt/server2", client_share_path: "/mnt/client2", client_mount_options: "nosuid,rw,sync,hard,intr 0 0" }` <br> `- { server_ip: zz.zz.zz.zz, server_share_path: "/mnt/server3", client_share_path: "/mnt/client3", client_mount_options: "nosuid,rw,sync,hard,intr 0 0" } `
-
 Omnia supports all NFS mount options. For a list of mount options, [click here](https://linux.die.net/man/5/nfs).

docs/README.md

@@ -33,7 +33,7 @@ Omnia can deploy firmware, install Kubernetes or Slurm (or both), along with add
 - Added support for bolt-on BeeGFS configuration
 - Added ability to upgrade kernel on Red Hat devices
 - Added support for shared LOM (LAN on Motherboard) configuration
-- Due to known limitations with AWX, installation of AWX is now optional using the parameters `awx_web_support`.
+- Due to known limitations with AWX, installation of AWX is now optional using the parameter `awx_web_support`.
 - Added LMod module system installation to handle the MODULEPATH Hierarchical problem.
 - Added NFS bolt on support to allow manager, compute and login nodes to become NFS clients.
 - Added support for PowerVault ME5 over SAS.
@@ -68,4 +68,4 @@ It's not just new features and bug fixes that can be contributed to the Omnia pr
 * Feedback
 * Validation that it works for your particular configuration
 
-If you would like to contribute, see [CONTRIBUTING](https://github.com/dellhpc/omnia/blob/release/CONTRIBUTING.md).
+If you would like to contribute, see [CONTRIBUTING](../CONTRIBUTING.md).

docs/Security/FreeIPA_User_Creation.md

@@ -45,7 +45,7 @@
 			
 ```
 			
-4. The random password displayed can be used to login to the login node using the newly created user.
+4. The random password displayed can be used to log in to the login node using the newly created user.
 
 	` ssh [email protected]`
 

omnia_config.yml

@@ -36,7 +36,7 @@ k8s_pod_network_cidr: "10.244.0.0/16"
 # Username for Dockerhub account
 # This will be used for Docker login and a kubernetes secret will be created and patched to service account in default namespace.
 # This kubernetes secret can be used to pull images from private repositories
-# This value is optional but suggested to avoid docker pull limit issues
+# This value is optional but suggested avoiding docker pull limit issues
 docker_username: ""
 
 # Password for Dockerhub account

omnia_security_config.yml

@@ -57,7 +57,7 @@ allow_deny: "Allow"
 # Root access is needed.
 restrict_program_support: false
 
-# The below mentioned services can be disabled, by adding values in comma separated values format for restrict_softwares variable
+# The below-mentioned services can be disabled, by adding values in comma separated values format for restrict_softwares variable
 # Services: telnet,lpd,bluetooth,rlogin,rexec
 # Ex: restrict_softwares: 'telnet,lpd,bluetooth' ( This disables 3 services, to disable more services, add services with comma separation. )
 restrict_softwares: ''