- 16 Feb 2022
- 7 Minutes to read
- Print
- DarkLight
- PDF
Client Operator -PRIVILEGES
- Updated on 16 Feb 2022
- 7 Minutes to read
- Print
- DarkLight
- PDF
- Cartridge Flow
- Receive Cartridge from Shipping Box
- Move Cartridge to Node
- Move Cartridge from Node to Shipping Box
- Media Flow
- Move MEDIA from Car to JBOD
- Remove MEDIA from JBOD
- Media Repair Flow
- Remove failed MEDIA
- Reinsert MEDIA to JBOD
- Cartridge Repair Flow
- Remove Failed Cartridge from Node
Cartridge Flow
Receive Cartridge from Shipping Box
Akri operator packs the Cartridge in the Shipping Box and sends the same to the client Location, where the Client operator receives the Cartridge and starts processing with a new event. Cartridge is now ready to proceed with subsequent flow.
Move Cartridge to Node
Upon successful login and badge scanning the operator shall scan the cartridge and node to proceed with this flow.
Once the cartridge is moved to the node the backend system will trigger the “Cartridge init” call and then the operator shall proceed with the next sequence.
Move Cartridge from Node to Shipping Box
This flow allows the operator to move Cartridge from node to Shipping Box. Operator receives a push notification stating that “Move Cartridge from Node to Shipping Box”.
Once the Cartridge is removed from the node and packed to the shipping box the application allows the Akri operator under the location side to proceed with the next sequence.
Media flow
Disk Group Register
A disk group is created to process multiple discs as one unit.
Follow the below instructions to create and register a disk group,
Instructions | Image |
---|---|
1. Scan the endpoint. | |
2. Enter the valid login credentials (Username and Password). 3. Click Login. The Badge Scanning Screen is displayed. | Login |
4. Scan the Operator badge QR from the application to approve the authentication of the operator login which then allows the user to access the mobile application. | Badge Scanning Screen |
5. Click Authorize. | Authorize |
6. Operator now lands on the dashboard of the application which contains the list of menu options pertaining to Manage Disk Group (disk group pipeline). Manage Disk Group
| Dashboard |
Manage Disk Group
Instructions | Image |
---|---|
1. Click Manage Disk Group. Existing disk groups are displayed along with an option to create new disk groups. 2. Click icon. | |
3. Enter a valid DiskGroup ID. 4. In the DiskGroupName field click on the drop down arrow. 5. Choose NUSCENES by clicking on the radio button which is the disk source data. 6. Click OK. 7. In the DiskGroupCluster field click on the drop down arrow. 8. Select the edge by clicking on the radio button. 9. Click OK. 10. Click icon to register one or more disks. | Details of DiskGroup |
To add disks: 11. Enter disk number under SerialNumber or scan the QR code. 12. In the DiskType field click on the drop down arrow. 13. Choose NUSCENES by clicking on the radio button. 14. Click Add button to add more disks. 15. Click Cancel button to cancel the addition. | Details of Media |
16. Click Review button to review the DiskGroup. 17. Click Back button to go back and edit, add, and remove disks or click Register button to register the DiskGroup. Note: After registering the disk group edit options are not available. | Review Diskgroup |
To edit DiskGroup before registering: Click Back button. The disk group is displayed under Manage DiskGroup. 18. Click the disk group that you want to edit. 19. Click icon available next to Disk1 to view options to Edit, and Delete the disk. 20. Click Delete button to delete the Disk1. | Delete Disk |
21. Click icon to add a new disk. 22. Follow instructions from To add disks. 23. Click Confirm button or Cancel button to cancel the registration. Diskgroup registration is successful. 24. Click OK. Note: The registered disk group is displayed in the Manage DiskGroup screen. | Confirm Registration Disk Group Registration Successful |
Move MEDIA to JBOD
This flow allows the operator to move MEDIA to JBOD and then the backend system will trigger the subsequent system calls “WfSessioninit”, “WfSessioncopy status”, “WfSessionCopyCompletestatus”, “CartridgeCopyStatus”, “CartridgeCopycomplete” and then allows the operator to proceed with the next sequence.
Follow the below instructions to move MEDIA to JBOD slot,
Instructions | Image |
---|---|
1. Click MOVE Media to JBOD from the Dashboard of the application. | |
2. Enter the value (Disk Group name) or scan the QR code from the web application. 3. Click Validate button. 4. Click icon. 5. Scan JBOD slot QR Code from the web application. | Details of Media |
6. Click Validate button. The summary is displayed. 7. Click Submit to confirm. Note: If an error is displayed, click icon and rescan the media and click Submit button. | Summary |
8. After clicking Submit button, media content will start getting ingested. 9. Click Next Scan to scan more discs in the disk group or Click Home. A notification is displayed to show the media processing is complete. | Media Moved to JBOD Slot |
Remove MEDIA from JBOD
Once the system call “WfSessionCopyCompletestatus” has processed and completed successfully, the operator is now allowed to remove the MEDIA from JBOD. Operator receives a push notification stating that “Session Completed. Remove MEDIA from JBOD”
Follow the below instructions to remove the MEDIA from JBOD slot,
Instruction | Image |
---|---|
1. Click icon to check the status of the MEDIA. Note: If the media processing is not complete, a notification to take corrective action is displayed. | Notification |
2. Click REMOVE Media from JBOD from the Dashboard of the application to remove MEDIA from JBOD slot. |
Media Repair Flow
Remove failed MEDIA
Perform this activity during the below listed scenarios (Push Notifications):
- SSD Insertion Failure at Edge - RecoverableSSDError
- Recoverable SSD error count exceeds max retry count
- SSD Insertion Failure at Edge - UnrecoverableSSDError
- SSD CopyCompleteStatus Failure - RecoverableSSDError
SSD Insertion Failure at Edge - Recoverable SSD Error
Once the operator is done with “Move MEDIA to JBOD” flow and if the backend system call “WfSessionInitstatus” fails. Operator receives a push notification saying “Media insertion failure. Remove MEDIA(MEDIA id) and Reinsert”.
Follow the below instructions to remove the failed MEDIA from JBOD:
Instruction | Image |
---|---|
Operator receives a push notification saying “Media insertion failure. Remove MEDIA(MEDIA id) and Reinsert”. 1. Click on the notification. | Action Notification |
2. Click Re-Scan button to rescan the JBOD slot. | Re-Scan |
3. Click Scan button. | Scan |
4. Click Submit button. | Submit |
Failed MEDIA is removed from JBOD. 5. Click Next Scan to scan more JBOD slots or click Home. | Failed MEDIA Removed |
Recoverable error count exceeds max retry count
Once the operator is done with “Move MEDIA to JBOD” flow and if the backend system call “WfSessionInitstatus” fails subsequently for 5 or more times. Operator receives a push notification saying “Retry count exceeded. Remove fault MEDIA(MEDIA ID) and insert new MEDIA”.
Follow the instructions as mentioned in 8.3.1.1. SSD Insertion Failure at Edge - Recoverable SSD Error to remove the faulty MEDIA from JBOD and perform the “Move MEDIA to JBOD” flow again by inserting a new MEDIA.
SSD Insertion Failure at Edge - Unrecoverable SSD Error
Once the operator is done with “Move MEDIA to JBOD” flow and if the backend system call “WfSessionInitstatus” failed upon setting unrecoverable state under the detailed error field while initiating the system call. Operator receives a push notification saying “Remove fault MEDIA(MEDIA ID) and insert new MEDIA”.
Follow the instructions as mentioned in 8.3.1.1. SSD Insertion Failure at Edge - Recoverable SSD Error to remove the faulty MEDIA from JBOD and perform the “Move MEDIA to JBOD” flow again by inserting a new MEDIA.
SSD CopyComplete Failure at Edge - Recoverable SSD Error
Once the operator is done with “Move MEDIA to JBOD” flow and if the backend system call “Wfsessioncopycomplete” fails upon setting recoverable state under the detailed error field while initiating the system call. Operator receives a push notification saying “Media Session failure. Remove MEDIA(MEDIA id) and Reinsert”.
Follow the instructions as mentioned in 8.3.1.1. SSD Insertion Failure at Edge - Recoverable SSD Error to remove the failed MEDIA from JBOD and proceed with 9.2. Reinsert MEDIA to JBOD.
Reinsert MEDIA to JBOD
Once the operator performs the “Remove failed MEDIA” flow (9.1.1. SSD Insertion Failure at Edge - Recoverable SSD Error, 9.1.4. SSD CopyComplete Failure at Edge - Recoverable SSD Error) with RecoverableSSDError.
1. SSD Insertion Failure at Edge - RecoverableSSDError
2. SSD CopyCompleteStatus Failure - RecoverableSSDError
Operator is supposed to reinsert MEDIA to JBOD and now the backend system will trigger the subsequent system calls “WfSessioninit”, “WfSessioncopy status”, “WfSessionCopyCompletestatus”, “CartridgeCopyStatus”, “CartridgeCopycomplete” and then allows the operator to proceed with 8.1.3. Remove MEDIA from JBOD.
Remove Failed Cartridge from Node
Operator is supposed to perform this activity during the below listed scenarios:
- Cartridge Insertion Failure at Edge - RecoverableCartridgeError
- Recoverable Cartridge error count exceeds max retry count
- Cartridge Insertion Failure at Edge - UnrecoverableCartridgeError
Cartridge Insertion Failure at Edge- Recoverable Cartridge Error
Once the operator is done with “Move Cartridge to Node” flow and if the backend system call “Cartridgeinit” gets failed. Operator receives a push notification saying “Cartridge insertion failure. Remove cartridge(cartridge id) and Reinsert”.
Follow the below instructions to remove the failed cartridge from Node and perform the “Move Cartridge to Node” flow again:
Instruction | Image |
---|---|
Operator receives a push notification saying “Cartridge insertion failure. Remove cartridge(cartridge id) and Reinsert”. 1. Click on the notification. | Action Notification |
2. Click Re-Scan button to rescan the cartridge. | Re-Scan |
3. Click Scan button. | Scan |
4. Click Submit button. | Submit |
Failed Cartridge is removed from Node. 5. Click Next Scan to scan more cartridges or click Home. | Failed Cartridge Removed |
Recoverable error count exceeds max retry count
Once the operator is done with “Move Cartridge to Node” flow and if the backend system call “Cartridgeinit” gets failed subsequently for 5 or more times.
Operator receives a push notification saying “Retry count exceeded. Remove fault Cartridge(Cartridge ID) and insert new Cartridge”.
Follow the instructions as mentioned in 8.3.3.1. Cartridge Insertion Failure at Edge- Recoverable Cartridge Error to remove the faulty cartridge from Node and perform the “Move Cartridge to Node” flow again by inserting a new cartridge.
Cartridge Insertion Failure at Edge - Unrecoverable Cartridge Error
Once the operator is done with “Move Cartridge to Node” flow (Section - 6.2) and if the backend system call “Cartridgeinit” gets failed upon setting unrecoverable state under the detailed error field while initiating the system call.
Operator receives a push notification saying “Remove fault Cartridge(Cartridge ID) and insert new Cartridge”.
Follow the instructions as mentioned in 8.3.3.1. Cartridge Insertion Failure at Edge- Recoverable Cartridge Error to remove the fault cartridge from Node and perform the “Move Cartridge to Node” flow again by inserting a new cartridge.