Browse Prior Art Database

Intelligent Suspension of Self-Management Characteristics of Cloud Deployed Solutions to Allow Manual Intervention or Maintenance of Virtual Machines

IP.com Disclosure Number: IPCOM000216388D
Publication Date: 2012-Apr-03
Document File: 2 page(s) / 26K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method and apparatus that allows cloud-based solution management systems to either manually or intelligently temporarily suspend selective management functions that exist both internally and externally to the cloud, such as automatic recovery and scaling, via a single action so that users can intervene while leaving the solution running.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Intelligent Suspension of Self-Management Characteristics of Cloud Deployed Solutions to Allow Manual Intervention or Maintenance of Virtual Machines

Some cloud-based application management systems allow the deployment of complete solutions, consisting of many virtual machines (VMs) and processes that may include application servers, databases, proxies, etc. Such systems can also provide self-monitoring and management capabilities both internally and externally to the cloud, including auto-recovery of failed virtual machines or processes or scaling in and/or out the number virtual machines and/or processes as the demand increases/decreases. This management capability takes the solution management out of the administrator's hands, but can have unwanted side affects when an administrator wants to manually intervene to apply maintenance, recycle processes or virtual machines that they suspect are having problems, perform troubleshooting, etc. The management system could see a virtual machine stopping and assume it has failed, and start a new one in its place for example, which might not be the solution the administrator wants applied.

Administrators currently manage this situation by:


• Destroying the entire application solution and restarting it from the beginning. This might work in the case where the goal is to update the solution to use new images or download new code, but it does not work for the case where the administrator wants the solution to keep running while they apply selective maintenance to only parts of the solution or need to troubleshoot one of the virtual machines that is having problems.


• Manually stopping all of the cloud processes, both internally and externally, so that it performs the self-management capabilities by killing processes, etc. The bad side affect of this is that the system could lose other functions provided by the management processes as well.

Disclosed herein is a method and apparatus that allows cloud-based solution management systems to either manually or intelligently temporarily suspend selective management functions that exist both internally and externally to the cloud, such as automatic recovery and scaling, via a single action so that users can intervene while leaving the solution running.

The administrator performs manual temporary suspension of selective management functions via a button on a user interface (UI).

The system intelligently temporarily suspends selective management functions on a dep...