Merge pull request #601 from cgoveas/devel

Updating schedule and parameter details.

docs/INSTALL_OMNIA_CONTROL_PLANE.md

@@ -157,9 +157,9 @@ Omnia creates a log file which is available at: `/var/log/omnia.log`.
 After you deploy the Omnia control plane, the devices such as Ethernet switches, InfiniBand Switches, and PowerVault storage devices are configured by Omnia according to the support enabled in the *base_vars.yml* file. The bare metal servers in the cluster are provisioned with custom CentOS based on the availability of iDRAC Enterprise or Datacenter License on the iDRAC.
 
 ## Default Ansible AWX configurations  
-The role used to deploy AWX within the *control_plane.yml* file: *webui_awx*.  
-All the pods are deployed in the specific namespace: *awx*.  
-The AWX reference source code repository: https://github.com/ansible/awx.git 
+* The role used to deploy AWX within the *control_plane.yml* file: *webui_awx*.  
+* All the pods are deployed in the specific namespace: *awx*.  
+* The AWX reference source code repository: https://github.com/ansible/awx.git 
 
 Omnia performs the following configurations on AWX:
 * The organization's name is set to **DellEMC**.
@@ -169,7 +169,7 @@ Omnia performs the following configurations on AWX:
 * The device credentials are stored in **idrac_credential**, **ethernet_credential**, **infiniband_credential**, and **powervault_me4_credential**. The **node_credential** stores the credentials of nodes in the cluster. 
 * Four groups are created under **node_inventory**-manager, compute, login, and nfs. All nodes in the inventory are added to these groups from the AWX UI.
 * iDRAC, networking switches, InfiniBand switches, and PowerVault storage devices can be configured using the respective templates: **idrac_template**, **ethernet_template**, **infiniband_template**, and **powervault_me4_template**. **deploy_omnia_template** is used to deploy Kubernetes and Slurm on the compute nodes. 
-* Schedules are created for **node_inventory_job** and **device_inventory_job** templates. These schedules are set to run every 10 minutes to dynamically retrieve and update the node and device details to AWX.  
+* Schedules are created for the **node_inventory_job** (every **10 minutes**) and the **device_inventory_job** (**once daily**) to dynamically retrieve and update node and device details to AWX.  
 
 >> **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.  
 

docs/control_plane/device_templates/CONFIGURE_INFINIBAND_SWITCHES.md

@@ -20,7 +20,7 @@ Under the `control_plane/input_params` directory, edit the following files:
 
 	File name	|	Variables	|	Default, choices	|	Description
 	-----------	|	-------	|	----------------	|	-----------------
-	base_vars.yml	|	ib_switch_support	|	<ul><li>**false**</li><li>true</li></ul>	|	To enable Mellanox InfiniBand switch configuration, set the variable to "true".
+	base_vars.yml	|	ib_switch_support	|	<ul><li>false</li><li>**true**</li></ul>	|	To enable Mellanox InfiniBand switch configuration, set the variable to "true".
 	<br>	|	ib_network_nic	|	<ul><li>**ib0**</li></ul>	|	NIC or Ethernet card that must be connected to configure Mellanox InfiniBand switches.  
 	<br>	|	ib_network_dhcp_start_range, ib_network_dhcp_end_range	|		|	DHCP range for the DHCP server to assign IPv4 addresses.
 	

docs/control_plane/device_templates/CONFIGURE_POWERSWITCHES.md

@@ -6,7 +6,7 @@ Under the `control_plane/input_params` directory, edit the following files:
 
 	Variable	|	Default, choices	|	Description
 	-------	|	----------------	|	-----------------
-	ethernet_switch_support	|	<ul><li>**false**</li><li>true</li></ul>	|	Set the variable to "true" to enable Ethernet switch configurations.  
+	ethernet_switch_support	|	<ul><li>false</li><li>**true**</li></ul>	|	Set the variable to "true" to enable Ethernet switch configurations.  
 
 2. `login_vars.yml` file:  Enter the following details to configure Ethernet switches.  
 	a. `ethernet_switch_username`- username for Ethernet switches.  

docs/control_plane/device_templates/CONFIGURE_POWERVAULT_STORAGE.md

@@ -26,11 +26,11 @@ Under the `control_plane/input_params` directory, edit the following files:
 	powervault_me4_k8s_volume_name [Required] |	<ul><li>**k8s_volume**</li><li>User-defined name</li></ul> |	Enter the Kubernetes volume name.	
 	powervault_me4_slurm_volume_name [Required] |	<ul><li>**slurm_volume**</li><li>User-defined name</li></ul> |	Enter the Slurm volume name.
 	powervault_me4_disk_group_name |	<ul><li>**omnia**</li><li>User-defined name</li></ul> |	Enter the group name of the disk.
-	powervault_me4_disk_partition_size [Required] |	<ul><li>**5**</li><li>Any value between 5-99</li></ul> |	Enter the partition size which would be used as an NFS share.  
+	powervault_me4_disk_partition_size [Required] |	<ul><li>**5**</li><li>Any value between 5-90</li></ul> |	Enter the partition size which would be used as an NFS share.  
 	powervault_me4_volume_size [Required] |	<ul><li>**100GB**</li><li>Custom value</li></ul> |	Enter the volume size in the format: *SizeTB*, *SizeGB*, *SizeMB*, or *SizeB*.  
 	powervault_me4_pool [Required] |	<ul><li>**a** (or A)</li><li>b (or B)</li></ul> |	Enter the pool for the volume.  
 	powervault_me4_server_nic [Required] |	<ul><li>**em1**</li></ul> |	Enter the NIC of the server to which the PowerVault Storage is connected.
-	powervault_me4_pool_type [Required] |	<ul><li>**Virtual**</li><li>Linear </li></ul> |	Select the type of pool to be deployed on PowerVault. Ensure that all pools on the device are exclusively virtual or linear.
+	powervault_me4_pool_type [Required] |	<ul><li>Virtual</li><li>**Linear** </li></ul> |	Select the type of pool to be deployed on PowerVault. Ensure that all pools on the device are exclusively virtual or linear.
 	
 ## Configuring PowerVault Storage
 

docs/control_plane/input_parameters/INFINIBAND_SWITCHES.md

@@ -12,7 +12,7 @@ Under the `control_plane/input_params` directory, edit the following files:
 
 File name	|	Variables	|	Default, choices	|	Description
 -----------	|	-------	|	----------------	|	-----------------
-base_vars.yml	|	ib_switch_support	|	<ul><li>**false**</li><li>true</li></ul>	|	To enable Mellanox InfiniBand switch configuration, set the variable to "true".
+base_vars.yml	|	ib_switch_support	|	<ul><li>false</li><li>**true**</li></ul>	|	To enable Mellanox InfiniBand switch configuration, set the variable to "true".
 <br>	|	ib_network_nic	|	<ul><li>**ib0**</li></ul>	|	NIC or Ethernet card that must be connected to configure Mellanox InfiniBand switches.  
 <br>	|	ib_network_dhcp_start_range, ib_network_dhcp_end_range	|		|	DHCP range for the DHCP server to assign IPv4 addresses.
 

docs/control_plane/input_parameters/POWERSWITCHES.md

@@ -6,7 +6,7 @@ Under the `control_plane/input_params` directory, edit the following files:
 
 	Variable	|	Default, choices	|	Description
 	-------	|	----------------	|	-----------------
-	ethernet_switch_support	|	<ul><li>**false**</li><li>true</li></ul>	|	Set the variable to "true" to enable Ethernet switch configurations.  
+	ethernet_switch_support	|	<ul><li>false</li><li>**true**</li></ul>	|	Set the variable to "true" to enable Ethernet switch configurations.  
 
 2. `login_vars.yml` file:  Enter the following details to configure Ethernet switches.  
 	a. `ethernet_switch_username`- username for Ethernet switches.  

docs/control_plane/input_parameters/POWERVAULT_STORAGE.md

@@ -26,7 +26,7 @@ Under the `control_plane/input_params` directory, edit the following files:
 	powervault_me4_k8s_volume_name [Required] |	<ul><li>**k8s_volume**</li><li>User-defined name</li></ul> |	Enter the Kubernetes volume name.	
 	powervault_me4_slurm_volume_name [Required] |	<ul><li>**slurm_volume**</li><li>User-defined name</li></ul> |	Enter the Slurm volume name.
 	powervault_me4_disk_group_name |	<ul><li>**omnia**</li><li>User-defined name</li></ul> |	Enter the group name of the disk.
-	powervault_me4_disk_partition_size [Required] |	<ul><li>**5**</li><li>Any value between 5-99</li></ul> |	Enter the partition size which would be used as an NFS share.  
+	powervault_me4_disk_partition_size [Required] |	<ul><li>**5**</li><li>Any value between 5-90</li></ul> |	Enter the partition size which would be used as an NFS share.  
 	powervault_me4_volume_size [Required] |	<ul><li>**100GB**</li><li>Custom value</li></ul> |	Enter the volume size in the format: *SizeTB*, *SizeGB*, *SizeMB*, or *SizeB*.  
 	powervault_me4_pool [Required] |	<ul><li>**a** (or A)</li><li>b (or B)</li></ul> |	Enter the pool for the volume.
 	powervault_me4_pool_type [Required] |	<ul><li>Virtual</li><li>**Linear** </li></ul> |	Select the type of pool to be deployed on PowerVault. Ensure that all pools on the device are exclusively virtual or linear.