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 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-installation subsystem that provisions, installs, and configures applications across cloud-computing providers, including applications that invoke functions provisioned and executed through a distributed-function-as-a-service feature of the automated-application-installation subsystem. The automated-application-installation subsystem employs application blueprints to identify components to provision. An application blueprint generally includes component specifications, constraints, and interdependencies. The automated-application-installation subsystem then determines a cost-effective provisioning of the identified components across available cloud-computing providers and installs the application according to the cost-effective provisioning.
Abstract:
Disclosed examples to configure an application for deployment involve displaying a user-selectable control in a user interface. A selected state and an unselected state of the user-selectable control distinguish between whether different components of the application are to be deployed in a same cloud and whether the different components of the application are to be deployed in separate clouds. When the user-selectable control indicates that the different components of the application are to be deployed in the separate clouds, a first one of the different components is bound to a first cloud and a second one of the different components is bound to a second cloud in an application deployment profile. When the user-selectable control indicates that the different components of the application are to be deployed in the same cloud, the different components of the application are bound to the same cloud in the application deployment profile.
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:
System and computer-implemented method for analyzing software-defined data center (SDDC) components in a computing environment uses network traffic data, which is correlated with an inventory of SDDC components in the computing environment to calculate a metric collection parameter for each SDDC component in the computing environment based on data flow associated with that SDDC component. Relevant metrics from each of the SDDC components in the computing environment are collected according to the metric collection parameter for that SDDC component to analyze the SDDC components.
Abstract:
The current document is directed to an automated-application-installation subsystem that provisions, installs, and configures applications across cloud-computing providers, including applications that invoke functions provisioned and executed through a distributed-function-as-a-service feature of the automated-application-installation subsystem. The automated-application-installation subsystem employs application blueprints to identify components to provision. An application blueprint generally includes component specifications, constraints, and interdependencies. The automated-application-installation subsystem then determines a cost-effective provisioning of the identified components across available cloud-computing providers and installs the application according to the cost-effective provisioning.
Abstract:
The current document is directed to an automated-application-release-management system 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 provides persona-based dashboard displays to users, tailoring the dashboard displays to the job profiles of users and to individual users. Persona-based dashboard displays are facilitated by standardized stage and task outputs, output contexts implemented by code-change identifiers, and stage/task-output aggregation.
Abstract:
Disclosed examples to configure an application for deployment involve displaying a user-selectable control in a user interface. A selected state and an unselected state of the user-selectable control distinguish between whether different components of the application are to be deployed in a same cloud and whether the different components of the application are to be deployed in separate clouds. When the user-selectable control indicates that the different components of the application are to be deployed in the separate clouds, a first one of the different components is bound to a first cloud and a second one of the different components is bound to a second cloud in an application deployment profile. When the user-selectable control indicates that the different components of the application are to be deployed in the same cloud, the different components of the application are bound to the same cloud in the application deployment profile.
Abstract:
Disclosed examples display a template mapping graphical user interface (GUI), the template mapping GUI indicative of services mappable to service templates; map a first service of the services to a first service template of the service templates; and generate an application blueprint based on the first service mapped to the first service template, the application blueprint to provide an option during a runtime phase for user-selection of the first service to be deployed based on the application blueprint.