Systems and methods for command execution request for pull model devices
Embodiments presented herein enable non-volatile memory express (NVMe®) subsystem-driven command execution requests. By configuring subsystems as pull model devices, subsystems can request a centralized discovery controller to perform one or more operations. Embodiments may leverage a command execution request architecture to achieve the subsystem-driven pull model functionality.
1. A processor-implemented method comprising:
responsive to a centralized discovery controller (CDC) receiving a command execution request from a direct discovery controller (DDC) of a storage subsystem indicating that the DDC wants an operation performed, sending a request to the DDC requesting what operation the DDC wants to be performed;
receiving an indication from the DDC that specifies which operation the DDC wants performed and including one or more operation specific parameters associated with the requested operation; and
issuing one or more commands related to the requested operation.
2. The processor-implemented method of claim 1 wherein the step of issuing one or more commands related to the requested operation comprises:
sending a status message to the DDC indicating a status of execution of the operation.
3. The processor-implemented method of claim 2 wherein the status message includes a transaction identifier associated with the operation.
4. The processor-implemented method of claim 2 further comprising:
performing one or more actions related to the operation prior to sending the status message.
5. The processor-implemented method of claim 1 wherein the operation allows the DDC to obtain information from the CDC about a zone group associated with the DDC, to obtain information from the CDC about one or more hosts, or to change information about a zone group associated with the DDC.
6. The processor-implemented method of claim 1 wherein the command execution request from a direct discovery controller (DDC) comprising an asynchronous event notification that comprises a pull device request identifier that indicates to the CDC to send a specific type of Get Log Page to the DDC.
7. The processor-implemented method of claim 6 wherein the indication received from the DDC that specifies which operation the DDC wants performed is a Get Log Page response that comprises an identifier of the operation and one or more operation specific parameters.
8. The processor-implemented method of claim 1 further comprising the step of:
sending to the DDC an event request command to subscribe to receive a notice from the DDC to facilitate receipt of the command execution request from the DDC.
9. An information handling system operating as a centralized discovery controller (CDC), comprising:
one or more processors; and
a non-transitory computer-readable medium or media comprising one or more sets of instructions which, when executed by at least one of the one or more processors, causes steps to be performed comprising:
responsive to a centralized discovery controller (CDC) receiving a command execution request from a direct discovery controller (DDC) of a storage subsystem indicating that the DDC wants an operation performed, sending a request to the DDC requesting what operation the DDC wants to be performed;
receiving an indication from the DDC that specifies which operation the DDC wants performed and including one or more operation specific parameters associated with the requested operation; and
issuing one or more commands related to the requested operation.
10. The information handling system of claim 9 wherein the step of issuing one or more commands related to the requested operation comprises:
sending a status message to the DDC indicating a status of execution of the operation.
11. The information handling system of claim 10 wherein the status message includes a transaction identifier associated with the operation.
12. The information handling system of claim 10 wherein the non-transitory computer-readable medium or media further comprises one or more sequences of instructions which, when executed by at least one of the one or more processors, causes steps to be performed comprising:
performing one or more actions related to the operation prior to sending the status message.
13. The information handling system of claim 9 wherein the operation allows the DDC to obtain information from the CDC about a zone group associated with the DDC, to obtain information from the CDC about one or more hosts, or to change information about a zone group associated with the DDC.
14. The information handling system of claim 9 wherein the command execution request from a direct discovery controller (DDC) comprising an asynchronous event notification that comprises a pull device request identifier that indicates to the CDC to send a specific type of Get Log Page to the DDC.
15. The information handling system of claim 14 wherein the indication received from the DDC that specifies which operation the DDC wants performed is a Get Log Page response that comprises an identifier of the operation and one or more operation specific parameters.
16. A processor-implemented method comprising:
sending, from a direct discovery controller (DDC) of a storage subsystem to a centralized discovery controller (CDC), a command execution request that indicates that the DDC wants an operation performed;
responsive to receiving a request from the CDC requesting what operation the DDC wants to be performed, sending a message to the CDC that specifies which operation the DDC wants performed and one or more operation specific parameters; and
receiving from the CDC a status message indicating a status of execution of the operation.
17. The processor-implemented method of claim 16 further comprising:
receiving from the CDC an event request command to subscribe to receive a notice from the DDC to facilitate receipt of the command execution request from the DDC.
18. The processor-implemented method of claim 16 wherein the DDC using the command execution request to command execution request to obtain information from the CDC about a host, about a zone group associated with the DDC, or to change information about a zone group associated with the DDC.
19. The processor-implemented method of claim 16 wherein at least one of the one or more operation specific parameters is a transaction identifier.
20. The processor-implemented method of claim 19 wherein the DDC uses the transaction identifier to correlate status information to the operation.