Automated and optimal deactivation of service to enable effective resource reusability

• US 9,104,463 B2
• Filed: 11/07/2012
• Issued: 08/11/2015
• Est. Priority Date: 11/07/2012
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Mahindru, Ruchi, Subramanian, Suraj, Viswanathan, Mahesh
• Primary Examiner(s): Tang, Kenneth
• Application Number:
  US13/670,806
• Publication Number:
  US 20140130043A1
• Time in Patent Office: 1,007 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 2009/45562 Creating, deleting, cloning virtual machine instances
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

Automated deactivation of service to enable effective resource reusability in a computing system, may include receiving a request to destroy a virtual machine, the virtual machine running in a virtual data center comprising one or more software components allocated for servicing a customer. In response, a provisioning module may be notified to remove the virtual machine. Based on the number of resources determined to be left as available, deactivation of pending actions on the virtual machine may be performed at the time the virtual machine is being removed or as an automatic scheduled job to be performed at a scheduled time.

Claims

1. A method for automated deactivation of managed service to enable effective resource reusability in a computing system, comprising:

receiving a request to destroy a virtual machine, the virtual machine running in a virtual data center comprising one or more software components allocated for servicing a customer;

notifying a provisioning module to remove the virtual machine;

determining a number of resources left available in the virtual data center;

in response to determining that the number of resources left available is less than a defined threshold value, sending a notification to one or more modules that manage activities associated with the virtual machine to disable managing the activities, closing all pending activities on the virtual machine, and releasing all resources used by the virtual machine concurrently with the provisioning module removing the virtual machine; and

in response to determining that the number of resources left available is greater than or equal to the defined threshold value, scheduling the sending, the closing and the releasing to be performed at a scheduled time,

wherein a decision of whether the deactivation of managed services should take place now as event-based or later as part of a periodic scheduled job is determined based on the number of resources left available.

2. The method of claim 1, wherein the resources comprise IP addresses used for the virtual machine.

3. The method of claim 1, wherein the resources comprise user identifier associated with the virtual machine.

4. The method of claim 1, wherein the defined threshold value is configurable.

5. The method of claim 1, wherein the one or more modules comprise an event management module, a patch management module, an identification management module, backup management module, or asset management module, or combinations thereof.

6. The method of claim 1, wherein the activities comprise monitoring the virtual machine, creating incident tickets associated with one or more artifacts provisioned on the virtual machine, managing update codes associated with the virtual machine managing user identifiers on the virtual machine, managing assets on the virtual machine, or managing backups on the virtual machine, or combinations thereof.

7. The method of claim 1, wherein the step of sending a notification to one or more modules that manage activities associated with the virtual machine to disable managing the activities, closing all pending activities on the virtual machine, and releasing all resources used by the virtual machine concurrently with the provisioning module removing the virtual machine in response to determining that the number of resources left available is less than a defined threshold value, occurs as a service request that invokes the sending, the closing and the releasing.

8. The method of claim 7, wherein the step of sending a notification to one or more modules that manage activities associated with the virtual machine to disable managing the activities, closing all pending activities on the virtual machine, and releasing all resources used by the virtual machine concurrently with the provisioning module removing the virtual machine in response to determining that the number of resources left available is less than a defined threshold value, is triggered as a result of event status update.

9. The method of claim 1, wherein the releasing of all resources used by the virtual machine includes updating one or more data tables associated with the virtual machine.

10. A computer readable storage medium storing a program of instructions executable by a machine to perform a method of automated deactivation of managed service to enable effective resource reusability in a computing system, comprising:

receiving a request to destroy a virtual machine, the virtual machine running in a virtual data center comprising one or more software components allocated for servicing a customer;

notifying a provisioning module to remove the virtual machine;

determining a number of resources left available in the virtual data center;

in response to determining that the number of resources left available is less than a defined threshold value, sending a notification to one or more modules that manage activities associated with the virtual machine to disable managing the activities, closing all pending activities on the virtual machine, and releasing all resources used by the virtual machine concurrently with the provisioning module removing the virtual machine; and

in response to determining that the number of resources left available is greater than or equal to the defined threshold value, scheduling the sending, the closing and the releasing to be performed at a scheduled time,

wherein a decision of whether the deactivation of managed services should take place now as event-based or later as part of a periodic scheduled job is determined based on the number of resources left available.

11. The computer readable storage medium of claim 10, wherein the resources comprise IP addresses used for the virtual machine.

12. The computer readable storage medium of claim 10, wherein the resources comprise user identifier associated with the virtual machine.

13. The computer readable storage medium of claim 10, wherein the defined threshold value is configurable.

14. The computer readable storage medium of claim 10, wherein the one or more modules comprise an event management module, a patch management module, an identification management module, backup management module, or asset management module, or combinations thereof.

15. The computer readable storage medium of claim 10, wherein the activities comprise monitoring the virtual machine, creating incident tickets associated with one or more artifacts provisioned on the virtual machine, managing update codes associated with the virtual machine managing user identifiers on the virtual machine, managing assets on the virtual machine, or managing backups on the virtual machine, or combinations thereof.

16. The computer readable storage medium of claim 10, wherein the step of sending a notification to one or more modules that manage activities associated with the virtual machine to disable managing the activities, closing all pending activities on the virtual machine, and releasing all resources used by the virtual machine concurrently with the provisioning module removing the virtual machine in response to determining that the number of resources left available is less than a defined threshold value, occurs as a service request that invokes the sending, the closing and the releasing.

17. The computer readable storage medium of claim 16, wherein the step of sending a notification to one or more modules that manage activities associated with the virtual machine to disable managing the activities, closing all pending activities on the virtual machine, and releasing all resources used by the virtual machine concurrently with the provisioning module removing the virtual machine in response to determining that the number of resources left available is less than a defined threshold value, is triggered as a result of event status update.

18. The computer readable storage medium of claim 10, wherein the releasing of all resources used by the virtual machine includes updating one or more data tables associated with the virtual machine.

19. A system of automated deactivation of managed service to enable effective resource reusability in a computing system, comprising:

a service management system comprising at least a processor, the service management system operable to receive a request to destroy a virtual machine running in a virtual data center comprising one or more software components allocated for servicing a customer,

the service management system further operable to notify a provisioning module executing in the virtual data center to remove the virtual machine,

the service management system further operable to determine a number of resources left available in the virtual data center,

in response to determining that the number of resources left available is less than a defined threshold value, the service management system further operable to send a notification to one or more modules that manage activities associated with the virtual machine to disable managing the activities, closing all pending activities on the virtual machine, and releasing all resources used by the virtual machine concurrently with the provisioning module removing the virtual machine, and

in response to determining that the number of resources left available is greater than or equal to the defined threshold value, the service management system is further operable to schedule the sending, the closing and the releasing to be performed at a scheduled time,

wherein a decision of whether the deactivation of managed services should take place now as event-based or later as part of a periodic scheduled job is determined based on the number of resources left available.

20. The system of claim 19, wherein the resources comprise IP addresses used for the virtual machine.

21. The system of claim 19, wherein the resources comprise user identifier associated with the virtual machine.

22. The system of claim 19, wherein the defined threshold value is configurable.

23. The system of claim 19, wherein the one or more modules comprise an event management module, a patch management module, an identification management module, backup management module, or asset management module, or combinations thereof.

24. The system of claim 19, wherein the activities comprise monitoring the virtual machine, creating incident tickets associated with one or more artifacts provisioned on the virtual machine, managing update codes associated with the virtual machine managing user identifiers on the virtual machine, managing assets on the virtual machine, or managing backups on the virtual machine, or combinations thereof.