PERFORMING A CHANGE PROCESS BASED ON A POLICY

• US 20130340035A1
• Filed: 03/09/2011
• Published: 12/19/2013
• Est. Priority Date: 03/09/2011
• Status: Abandoned Application

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Ronen, Edith, Regev, Adi, Uziel, Roie, Hajyhia, Shehab
• Application Number:
  US14/001,782
• Publication Number:
  US 20130340035A1
• Time in Patent Office: Days
• US Class Current: 726/1
• CPC Class Codes: G06F 21/00 Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

A request to change a component of an infrastructure is received (102). In response to the request a change process having plural phases is performed (104). A transition between plural phases is allowed based on at least one policy.

Claims

1. A method comprising:

receiving, by a system having a processor, a request to change a component in an infrastructure;

in response to the request, performing, by the system, a change process having plural phases, wherein the change process comprises;

determining, based on accessing at least one policy, whether or not transitions among the plural phases are allowed, wherein the determining comprises triggering a policy rule engine to apply the at least one policy for a particular transition between successive ones of the plural phases; and

invoking exception handling by the policy rule engine in response to determining that violation of the at least one policy would result from the particular transition.

2. The method of claim 1, wherein information associated with the at least one policy indicates selected ones of the phases to which the at least one policy is to be applied, and

wherein, triggering the policy rule engine for the particular transition is in response to

3. The method of claim 1, wherein information associated with the at least one policy identifies one or multiple change processes to which the at least one policy is to be applied, and wherein the policy rule engine is to apply the at least one policy to the change process corresponding to the request based on the information.

4. The method of claim 1, wherein the at least one policy identifies an entity that is to be notified in case of violation of the policy, and

wherein invoking the exception handling comprises notifying the entity of the violation.

5. The method of claim 1, wherein invoking the exception handling comprises:

providing information of the violation to at least one stakeholder to prompt for approval or dis-approval of the particular transition.

6. The method of claim 5, further comprising:

in response to receiving approval of the particular transition from the at least one stakeholder, allowing the change process to perform the particular transition to a next phase of the change process, and continuing with the change process.

7. The method of claim 5, wherein providing the information of the violation to the at least one stakeholder comprises providing the information of the violation to plural stakeholders,

wherein approval of the particular transition is based on a predefined, combination of positive indications from the plural stakeholders to allow the particular transition.

8. The method of claim 1, wherein the change process further comprises:

assessing a risk of the change requested by the received request, wherein assessing the risk is based on the component being changed and based on a relationship of the component to at least another component in the system.

9. The method of claim 8, wherein the component being changed and the another component are represented by respective configuration items, and wherein the relationship between the configuration items are expressed by a correlation between the configuration items.

10. The method of claim 8, wherein invoking the exception handling is invoked based on the assessed risk exceeding a predefined threshold.

11. (canceled)

12. A system comprising:

at least one processor; and

a management subsystem having at least one module executable on the at least one processor to;

receive a change request for changing a component of an infrastructure;

perform a change process in response to the change request, the change process having plural phases;

decide to transition between successive ones of the plural phases based on whether or not a respective transition between successive ones of the plural phases would violate at least one policy, as determined by a policy rule engine;

allow a given transition between successive ones of the plural phases if the at least one policy would not be violated; and

invoke exception handling for the given transition if the at least one policy would be violated

13. The system of claim 12, wherein the exception handling comprises providing notification of violation of the at least one policy to plural stakeholders, and wherein a decision to decide whether the given transition is allowed is based on receiving approval from a predefined combination of the plural stakeholders.

14. The system of claim 13, wherein the predefined combination of plural stakeholders comprises one of;

(1) a majority of the plural stakeholders;

(2) any of the plural stakeholders; and

(3) a majority of a quorum of the plural stakeholders.

15. The system of claim 12, further comprising a change request queue to store the received change request, wherein the change request queue further stores additional change requests to he processed by the management subsystem, and wherein the management subsystem is to further;

as part, of performing the change process, modify the received change request; and

store the modified change request in the change request queue for further processing.

16. An article comprising at least one machine-readable storage medium storing instructions that upon execution cause a system having a processor to perform a method comprising;

receiving, by a system having a processor, a request to change a component in an infrastructure;

in response to the request, performing, by the system, a change process having plural phases, wherein the change process comprises;

determining, based on accessing at least one policy, whether or not transitions among the plural phases are allowed, wherein the determining comprises triggering a policy rule engine to apply the at least one policy for a particular transition between successive ones of the plural phases; and

invoking (108) exception handling by the policy rule engine in response to determining that violation, of the at least one policy would result from the particular transition

17. The article of claim 16, wherein information associated with the at least one policy indicates selected ones of the phases to which the at least one policy is to be applied, and

wherein triggering the policy rule engine for the particular transition is in response to the information.

18. The article of claim 16, wherein information associated with the at least one policy identifies one or multiple change processes to which the at least one policy is to be applied, and wherein the policy rule engine is to apply the at least one policy to the change process corresponding to the request based on the information.

19. The article of claim 16, wherein the at least one policy identifies an entity that is to be notified in case of violation of the policy;

and

wherein invoking the exception handling comprises notifying the entity of the violation.

20. The article of claim 16, wherein invoking the exception handling comprises:

providing information of the violation to at least one stakeholder to prompt for approval or dis-approval of the particular transition.

21. The article of claim 16, wherein the method comprises:

assessing a risk of the change requested by the received request, wherein assessing the risk is based on the component being changed and based on a. relationship of the component to at least another component in the system.