Inventory

Inventory management feature enables User to manage Master Inventory, Filters, Patching Inventory, Groups and Create Ad Hoc execution as well as View Inventory Logs for the list of devices.

Master Inventory

This screen allows users to manage master inventory where host name will be used as distinct entity. Users can either add a single device or upload bulk data using the import feature.

To add a single device:
1. click on the Add Device button. The below popup appears:
  Figure 2. Master Inventory – Add Device
2. Fill all the mandatory fields and the optional fields, if needed. Click on Save. The following alert appears:
  Figure 3. Master Inventory – Add Device (Cont.)
3. The data now appears in the grid.
  Figure 4. Master Inventory – Add Device (Cont.)
To bulk upload any data:
1. click on Import and select the file to be imported.
  Figure 5. Master Inventory – Bulk Data Upload
2. Click on Preview to have a look at the data being uploaded before proceeding.
  Figure 6. Master Inventory – Bulk Data Upload (Cont.)
3. Click on Import to upload the data. Below alert appears:
  Figure 7. Master Inventory – Bulk Data Upload (Cont.)
To delete the devices:
1. Select those devices and click on Delete. Below alert appears:
  Figure 8. Master Inventory – Delete a Device
2. Click on Yes to delete the selected records. Below alert generated:
  Figure 9. Master Inventory – Delete a Device (Cont.)
To edit any record:
1. Click onunder action column and update the required fields and click on Update button.
  Figure 10. Master Inventory – Edit Record
2. On successful update, below alert appears:
  Figure 11. Master Inventory – Edit Record (Cont.)

Filter

This screen allows users to create filters which are nothing but conditions that can be applied on the available devices under a change number to segregate specific type of records.

A screenshot of a computer Description automatically generated — Figure 12. Filter

To create a filter:
1. Click on Add Filter button and provide the filter name:
  Figure 13. Filter (Cont.)
2. Click on Save button and below alert appears:
  Figure 14. Filter (Cont.)
3. The filter now appears in the grid. To add condition to the filter, click on under actions column.
  Figure 15. Filter (Cont.)
4. Below popup opens to provide the conditions:
  Figure 16. Filter (Cont.)
5. Select the column name on which condition will be applied, select the valid operator and then provide the column value. In case of multiple conditions select the clause/sub clause and provide multiple conditions.
  Figure 17. Filter (Cont.)
6. Click on the save button to save the conditions for the filter. Below alert will be generated:
  Figure 18. Filter (Cont.)
7. To edit the name of the filter, click on under Actions column and update the filter name and click on Save.
8. To delete any filter, click on under Actions column and below confirmation box appears.
  Figure 19. Filter (Cont.)
9. Click on Yes to delete the filter and below alert gets generated.
  Figure 20. Filter (Cont.)

Patching Inventory

This screen allows users to manage patching inventory data for a change number. To upload a patching, a change number must be associated with it.

To upload patching data:
1. click on the +Create button.
  Figure 21. Patching Inventory
2. Provide the change number and select the file.
  Figure 22. Figure Patching Inventory (Cont.)
3. Click on Preview.
  Figure 23. Patching Inventory (Cont.)
4. It will show 2 sections:
  1. New Records: It will show all new/updated records which are there in uploaded Patching template but not there in Master Inventory. The records which are there in the master inventory as well as in uploaded data but have different value in any field are displayed in different colour. The following operations can be performed on this tab:
    - Discard: User can select single or multiple records from Grid to Discard inventory from uploaded list.
    - Add/Update: User can select single or multiple records from Grid to Add/Update in Master Inventory list.
  2. Existing Records: It will show all the records which are there in the Master Inventory as well as in Uploaded Inventory.
5. Click on the “Upload” button to upload Inventory list. The data will now appear under the View tab.
  Figure 24. Patching Inventory (Cont.)
6. To view the uploaded data, click on under Actions column.
  Figure 25. Patching Inventory (Cont.)
7. Click on the Approve button to approve the uploaded inventory. Another way to approve the uploaded data is to click on under Actions column. A confirmation box is generated.
  Figure 26. Patching Inventory (Cont.)
8. Click on yes. An alert will be generated.
  Figure 27. Patching Inventory (Cont.)
9. To delete the records, select the change and click on the Delete button. A confirmation box is generated.
  Figure 28. Patching Inventory (Cont.)
10. Click on yes. An alert will be generated.
  Figure 29. Patching Inventory (Cont.)
Note:
Netbot approver can only approve the changes uploaded by users. Netbot admin can both upload and approve the data changes. Netbot users can only upload the change data.

Group

This screen allows users to manage groups. Groups are used for the grouping of devices in the data uploaded corresponding to a change in patching inventory based on the already created filters.

To create a group:
1. select a change number.
  Figure 31. Group (Cont.)
2. Click on the Add Group button. And populate mandatory fields.
  Figure 32. Group (Cont.)
3. Select the filter and click Apply. The condition under selected filter gets applied on the devices uploaded under selected change number and in the filter result all those devices are listed on which condition gets satisfied. Click on Save. Below alert is generated.
  Figure 33. Group (Cont.)
4. The record gets listed in the grid.
  Figure 34. Group (Cont.)
5. To view the group and what all devices are falling under that group, click on under Action column. To delete any record, select the record and click on Delete button. Below confirmation box generates.
  Figure 35. Group (Cont.)
6. Click on yes to delete the record. An alert is generated.
  Figure 36. Group (Cont.)

Ad Hoc Execution

This screen allows users to execute the ansible tower playbook on any change number. All the runbooks available under Ansible Tower/AWX playbook mapped with organization and change request task module will be available for ad hoc execution.

Select any playbook to execute. Select the change number on which the playbook will be executed, select the activity either Post/Pre. Provide the task number. Select the Time Zone and based on it, select the Start Time at which the playbook will be executed.
Figure 38. Ad Hoc Execution (Cont.)
To trigger the execution, it is mandatory to have at least one parameter of playbook as a group parameter. For that, edit the parameter and tick the Is Group checkbox and under Value column, select the group so that the playbook will be executed on all the devices that fall under that group.
Figure 39. Ad Hoc Execution (Cont.)
Ater all fields have been entered, click on Schedule. An alert will be generated.
Figure 40. Ad Hoc Execution (Cont.)
User is redirected to the View tab of the page which lists all the ad hoc execution that have been scheduled.
Figure 41. Ad Hoc Execution (Cont.)
To view the parameters of the scheduled ad hoc, click on under Actions column.
Figure 42. Ad Hoc Execution (Cont.)
Click on the refresh button to see the status update on any ad hoc scheduled.
Users can delete any ad hoc scheduled if it’s in queued state. For that click on under Actions column.
A confirmation box will be generated.
Figure 43. Ad Hoc Execution (Cont.)
Click on yes and the following alert will be generated.
Figure 44. Ad Hoc Execution (Cont.)

Inventory Logs

This screen allows users to see all CI (Hostname) wise execution logs. The download button will be available once work starts, and log file gets created.

To view the logs on any CI, click on Download button, a file with all the available logs will be downloaded.

Inventory Execution History

This screen enables tracking all change requests, tasks history, including reference of execution.

For a specified duration, the user can see the statuses of all the executed changes and their corresponding task.