Abstract:
Disclosed examples to configure an application for deployment across a plurality of deployment environments involve displaying a user-selectable control in a user interface. The user-selectable control is to specify whether the application is to be deployed across the plurality of deployment environments. Based on selection of the user-selectable control, a blueprint of the application stores an indication of whether the application is to be deployed across the plurality of deployment environments. Based on the indication in the blueprint, an application deployment profile is generated to specify the plurality of deployment environments across which to deploy the application.
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 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. The currently described methods and systems allow resources to be shared among multiple, interdependent release pipelines and allow access to shared resources to be controlled.
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:
In one example, a computing node includes a metric dependency graph knowledge base to store a data structure representing a relationship between a plurality of metrics. Further, the computing node may include a processor and a memory having a metric recommendation unit. The metric recommendation unit may determine a first metric of a monitored computing-instance while a user interacts with a GUI of a monitoring application. Further, the metric recommendation unit may retrieve the data structure corresponding to the first metric. The data structure may include the first metric and a plurality of dependent metrics associated with the first metric. Further, the metric recommendation unit may apply a machine learning model on the data structure to determine a second metric from the plurality of dependent metrics. Furthermore, the metric recommendation unit may output the second metric related to the first metric on the GUI.
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:
Disclosed examples to configure an application blueprint involve, during a design phase, binding a service template to a node of the application blueprint. The application blueprint defines an application to be deployed in a cloud environment. The service template is mapped to a plurality of services that are selectable during a runtime phase to implement the node in the cloud environment. During the runtime phase, a first one of the services is bound to the node of the application blueprint based on the first one of the services being mapped to the service template and being selected during the runtime phase. An application deployment profile is generated based on the binding of the first one of the services to the node.