Abstract: An example apparatus includes memory and a processor to execute instructions to set a scaling status of a first virtual machine included in an application deployed in a computing environment, the first virtual machine to execute a first component of the application, means for identifying an information dependency of a second virtual machine on information from the first virtual machine, the second virtual machine to execute a second component of the application, and update the information dependency based on the scaling status of the first virtual machine, the information dependency in the configuration information to include a reference to the first virtual machine.

Abstract: Networks and network elements having a service and power control orchestrator are disclosed, including a network element comprising a processor; a first port coupled to a first optical link carrying a first optical signal; a WSS having a multiplexer, a demultiplexer, and a control block operable to control the multiplexer/demultiplexer. The WSS operable to switch the first optical signal into a second optical signal. A second port is coupled to a second optical link, operable to carry the second optical signal, and in optical communication with the WSS. A memory stores an orchestrator application, an OTSA component, a service component, and instructions that cause the processor to: store a logical ROADM model having a connectivity matrix of the network element; receive a communication associated with the control block based on the logical ROADM model; and transmit, to the control block, a service loading sequence based on the logical ROADM model.

Abstract: An example apparatus includes means for setting a scaling status of a first virtual machine included in an application deployed in a computing environment, the first virtual machine to execute a first component of the application, means for identifying an information dependency of a second virtual machine on information from the first virtual machine, the second virtual machine to execute a second component of the application, and means for updating the information dependency based on the scaling status of the first virtual machine, the information dependency in the configuration information to include a reference to the first virtual machine.

Abstract: An example apparatus includes a deployment monitor to initiate a modification of a number of virtual machines deployed in the computing environment. The virtual machines including a first virtual machine to execute a first component of an application deployed in the computing environment. A dependents identifier is to identify an information dependency of a second virtual machine on information from the first virtual machine. The second virtual machine is to execute a second component of the application. An updater is to update the information dependency based on a scaling status of the first virtual machine. The information dependency in the configuration information including a reference to the first 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: An example apparatus includes a deployment monitor to initiate a modification of a number of virtual machines deployed in the computing environment. The virtual machines including a first virtual machine to execute a first component of an application deployed in the computing environment. A dependents identifier is to identify an information dependency of a second virtual machine on information from the first virtual machine. The second virtual machine is to execute a second component of the application. An updater is to update the information dependency based on a scaling status of the first virtual machine. The information dependency in the configuration information including a reference to the first virtual machine.

Abstract: Methods and systems to compute application license costs of a number of applications run on virtual machines of a virtualized data center are described. In one aspect, one or more of the virtual machines (“VMs”) that form the virtual data center are determined. Each VM is created from hardware components specifications of one or more application blueprints stored in a data-storage devices. The one or more blueprints are searched to determine the one more applications that run in each VM. For each VM, a total VM application licensing cost of the one or more applications is computed based on one or more of an application instance license cost, application socket license cost, and application core license of each of the one or more applications associated with each application.

Abstract: An example apparatus includes a deployment monitor to initiate a modification of a number of virtual machines deployed in the computing environment. The virtual machines including a first virtual machine to execute a first component of an application deployed in the computing environment. A dependents identifier is to identify an information dependency of a second virtual machine on information from the first virtual machine. The second virtual machine is to execute a second component of the application. An updater is to update the information dependency based on a scaling status of the first virtual machine. The information dependency in the configuration information including a reference to the first virtual machine.

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: Methods and apparatus are disclosed to scale application deployments in cloud computing environments using virtual machine pools. An example method disclosed herein includes preparing a virtual machine pool including a virtual machine for use in a scaling operation, the virtual machine prepared in accordance with a blueprint of the application deployed in a deployment environment separate from the virtual machine pool, in response to receiving a request to scale the application, determining by executing an instruction with a processor, whether configuration information of the virtual machine pool satisfies a scaling requirement included in the request, and based on the determination, executing an instruction with the processor to transfer the virtual machine from the virtual machine pool to the deployment environment to perform the scaling operation in accordance with the request to scale.

Abstract: An example apparatus includes a deployment monitor to initiate a modification of a number of virtual machines deployed in the computing environment. The virtual machines including a first virtual machine to execute a first component of an application deployed in the computing environment. A dependents identifier is to identify an information dependency of a second virtual machine on information from the first virtual machine. The second virtual machine is to execute a second component of the application. An updater is to update the information dependency based on a scaling status of the first virtual machine. The information dependency in the configuration information including a reference to the first virtual machine.

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.

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: An artifact manager generates an abstraction for artifacts and repositories in a deployment platform such that the artifacts may be located uniformly and securely in each deployment environment during the deployment process. The described system includes a release automation platform having a release pipeline which is responsible for deploying build artifacts into multiple deployment environments, testing the build artifacts thoroughly in each environment, and follow organization-specific approval processes to promote the build artifacts to a next deployment environment.

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.

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.

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: 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.