Abstract:
A system and method for efficiently replacing clients running a large scale application uses a pool of clients, which includes a group of active clients running the large scale application and at least one standby client. When a particular active client is identified to be replaced, one of the at least one standby client is selected as a replacement client for the particular active client. The particular active client is replaced with the selected replacement client with respect to the running of the large scale application such that the particular client is removed from the group of active clients and the selected replacement client is added to the group of active clients.
Abstract:
The current document is directed to automated application-release-management facilities that, in a described implementation, coordinate continuous development and release of cloud-computing applications. The application-release-management process is specified, in the described implementation, by application-release-management pipelines, each pipeline comprising one or more stages, with each stage comprising one or more tasks. Current application-release-management pipelines are linear, with the stages sequentially ordered within the pipeline. The current document is directed to an automated application-release-management facility that supports branch points within application-release-management pipelines where, as a result of inter-application dependencies, a task within a stage of the first pipeline associated with a first application launches a second pipeline associated with a second application. Branching pipelines and inter-application dependencies provide a significant increase in the scope and power of automated application-release management.
Abstract:
The current document is directed to an automated-application-release-management subsystem that executes application-release-management pipelines that includes one or more tasks and/or stages, execution of which launch execution of scripts on specified host computers. The capability for launching scripts from application-release-management-pipeline tasks and stages provides flexibility in design and development of application-release-management pipelines and provides an incremental path for migration of legacy-script-based application-release management to automated pipeline-based application-release management.
Abstract:
The current document is directed to an automated-application-release-management subsystem, or facility, that organizes and manages the application-development and application-release processes to allow for continuous application development and release. The current document is particularly directed to implementations in which the automated application-release-management subsystem is highly modularized to provide plug-in compatibility with a large variety of external, third-party subsystems, libraries, and functionalities. This highly plug-in-compatible architecture provides for decreasing dependencies on various subsystems and components of a workflow-based cloud-management system in which the plug-compatible automated application-release-management subsystem is incorporated.
Abstract:
The current document is directed to automated application-release-management facilities that, in a described implementation, coordinate continuous development and release of cloud-computing applications. The application-release-management process is specified, in the described implementation, by application-release-management pipelines, each pipeline comprising one or more stages, with each stage comprising one or more tasks.