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:
Methods, apparatus, systems and articles of manufacture are disclosed to scale application deployments in cloud computing environments. An example method disclosed herein includes marking a scaling status of a virtual machine included in a first node deployed in the computing environment, the first node executing a first component of the application, the scaling status of the virtual machine indicating a change in a number of virtual machines included in the first node. The example method also includes identifying a second node including a dependency with the virtual machine, the second node deployed in the computing environment. The example method also includes updating configuration information associated with the second node based on the scaling status of the virtual machine, the configuration information including a reference to the virtual machine.
Abstract:
The current document is directed to an integrated cloud-management facility, or subsystem, that incorporates an automated-application-deployment-facility integrator that incorporates one or more automated-application-deployment facilities into the cloud-management facility. The automated-application-deployment-facility integrator allows users of the cloud-management facility to access one or more automated-application-deployment facilities within the context of the cloud-management facility. The automated-application-deployment-facility integrator provides to system managers and administrators, through the cloud-management facility, a wider range of functionalities and capabilities than is provided by a cloud-management facility that includes only a single automated-application-deployment facility, or subsystem.
Abstract:
Methods, apparatus and systems are disclosed to update application deployments in cloud computing environments. An example method disclosed herein includes identifying an update profile to promote across the plurality of deployment environments, the update profile to update a component of the application, in response to a notification of promotion of the update profile received at a first deployment environment. The example method also includes displaying a user-selectable control in a user interface, the user-selectable control to specify whether to apply the update profile to the component of the application deployed in the first deployment environment, based on selection of the user-selectable control, performing a compatibility check of the first deployment environment and the update profile, and based on an outcome of the compatibility check, applying the update profile to the component of the application deployed in the first deployment environment.
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.