Closed-loop information technology issue remediation
Described embodiments provide systems and methods for providing closed-loop Information Technology (IT) issue remediation. At least one host state change is discovered. Events to be generated and persisted as a result of discovering the at least one host state change are calculated. The events are sent to a user for approval by the user or to be declined by the user. For each event one of an approval of the event or a rejection of the event is received. A workflow is executed for the approval or rejection of the event.
1. A method for providing closed-loop Information Technology (IT) issue remediation comprising:
discovering at least one host state change, the at least one host state change corresponds to a host that is moved from a first storage cluster to a second storage cluster, wherein the at least one host state change includes a Host Bus Adapter (HBA) change for hosts, the HBA changes include adjustments to HBA maximum queue depth values;
calculating events to be generated and persisted as a result of discovering the at least one host state change;
sending the events to a user for approval by the user or to be declined by the user;
receiving for each event one of user approval of the event or user rejection of the event; and
executing a workflow for the approval or rejection of the event, the workflow comprises synchronizing an environment with respect to the host state change including performing storage and zoning operations to enable data access to the host, the storage and zoning operations including using the event information to remove access to storage associated with the first storage cluster and grant access to storage associated with the second storage cluster;
wherein the event includes information relating to the host move from the first storage cluster to the second storage cluster, the storage associated with the first storage cluster to which the host loses access, and the storage associated with the second storage cluster to which the host gains access.
2. The method of claim 1 wherein the events are generated for non-duplicate state changes.
3. The method of claim 1 wherein the events are persisted with details about the event including a tenant associated with the event, affected resources, and workflows to invoke, and the tenant is one of a plurality of tenants that manages a corresponding set of resources and the user is permitted access to those events assigned to a corresponding tenant.
4. The method of claim 1 wherein when an approval for an event is received the appropriate workflow for the approved event is executed and the user is given an event task that is used to monitor the workflow for the approved event.
5. The method of claim 1 wherein when a rejection for an event is received the appropriate workflow for the rejected event is executed and the user is given an event task that is used to monitor the workflow for the rejected event.
6. The method of claim 1 , further comprising:
determining that the at least one host state change is a temporary host state change; and
declining by the user a corresponding event.
7. A computer program product including a non-transitory computer readable storage medium having computer program code encoded thereon that when executed on a processor of a computer causes the computer to operate a remediation system, the computer program product comprising:
computer program code for discovering at least one host state change, the at least one host state change corresponds to a host that is moved from a first storage cluster to a second storage cluster, wherein the at least one host state change includes a Host Bus Adapter (HBA) change for hosts, the HBA changes include adjustments to HBA maximum queue depth values;
computer program code for calculating events to be generated and persisted as a result of discovering the at least one host state change;
computer program code for sending the events to a user for approval by the user or to be declined by the user;
computer program code for receiving for each event one of an approval of the event or a rejection of the event; and
computer program code for executing a workflow for the approval or rejection of the event, the workflow comprises synchronizing an environment with respect to the host state change including performing storage and zoning operations to enable data access to the host, the storage and zoning operations including using the event information to remove access to storage associated with the first storage cluster and grant access to storage associated with the second storage cluster;
wherein the event includes information relating to the host move from the first storage cluster to the second storage cluster, the storage associated with the first storage cluster to which the host loses access, and the storage associated with the second storage cluster to which the host gains access.
8. The computer program product of claim 7 wherein the events are generated for non-duplicate state changes.
9. The computer program product of claim 7 wherein the events are persisted with details about the event including a tenant associated with the event, affected resources, and workflows to invoke, and the tenant is one of a plurality of tenants that manages a corresponding set of resources and the user is permitted access to those events assigned to a corresponding tenant.
10. The computer program product of claim 7 wherein when an approval for an event is received the appropriate workflow for the approved event is executed and the user is given an event task that is used to monitor the workflow for the approved event.
11. The computer program of claim 7 wherein when a rejection for an event is received the appropriate workflow for the rejected event is executed.
12. The computer program product of claim 11 wherein the user is given an event task that is used to monitor the workflow for the rejected event.
13. A system comprising:
a processor; and
memory storing computer program code that when executed on the processor causes the processor to operate a remediation system, wherein operating the remediation system includes:
discovering at least one host state change, the at least one host state change corresponds to a host that is moved from a first storage cluster to a second storage cluster, wherein the at least one host state change includes a Host Bus Adapter (HBA) change for hosts, the HBA changes include adjustments to HBA maximum queue depth values;
calculating events to be generated and persisted as a result of discovering the at least one host state change;
sending the events to a user for approval by the user or to be declined by the user;
receiving for each event one of an approval of the event or a rejection of the event; and
executing a workflow for the approval or rejection of the event, the workflow comprises synchronizing an environment with respect to the host state change including performing storage and zoning operations to enable data access to the host, the storage and zoning operations including using the event information to remove access to storage associated with the first storage cluster and grant access to storage associated with the second storage cluster:
wherein the event includes information relating to the host move from the first storage cluster to the second storage cluster, the storage associated with the first storage cluster to which the host loses access, and the storage associated with the second storage cluster to which the host gains access.
14. The system of claim 13 wherein the events are persisted with details about the event including a tenant associated with the event, affected resources, and workflows to invoke, and the tenant is one of a plurality of tenants that manages a corresponding set of resources and the user is permitted access to those events assigned to a corresponding tenant.
15. The system of claim 13 wherein when an approval for an event is received the appropriate workflow for the approved event is executed and wherein the user is given an event task that is used to monitor the workflow for the approved event.
16. The system of claim 13 wherein when a rejection for an event is received the appropriate workflow for the rejected event is executed and wherein the user is given an event task that is used to monitor the workflow for the rejected event.