Abstract: Embodiments of the present invention provide systems and methods for constructing a plan for creating a cloud service. In one embodiment, a configurator receives a request for one or more services making up a cloud service, and a preliminary plan for the requested services is generated. A service provider determines that it is able to fulfill a requested service, and inserts a sub plan for fulfilling the requested service into the preliminary plan. A final plan is generated, which includes a sub plan from each service provider inserted into the preliminary plan.

Abstract: A source IT-infrastructure hosts a composite application including multiple functional modules connected to each other via communication links. An abstract pattern includes first nodes and first links representing the functional modules and communication links and lacks resource-related data enabling a deployment engine to instantiate a resource for providing a runtime environment. A target IT-infrastructure has assigned a resource catalog including, for each resource available in the target IT-infrastructure, a specification of the resource's capabilities, and includes second nodes and links, each second node being a representation of one or more of the resources of the target IT-infrastructure and including an indication of the capabilities of one or more resources represented by the second node. The first nodes and links of the abstract pattern are iteratively supplemented by the second nodes and second links.

Abstract: Extension patterns are deployed to core deployment patterns stored in a first software repository. An event relating to registration of a component is detected. In response to detecting the event, a tool registry can be queried to identify one or more extension deployment patterns for use with one or more core deployment patterns. Based upon the query, one or more extension deployment components can be retrieved from a second software repository. The one or more extension deployment components can be deployed on top of one or more instances of the one or more core deployment patterns.

Abstract: Extension patterns are deployed to core deployment patterns stored in a first software repository. An event relating to registration of a component is detected. In response to detecting the event, a tool registry can be queried to identify one or more extension deployment patterns for use with one or more core deployment patterns. Based upon the query, one or more extension deployment components can be retrieved from a second software repository. The one or more extension deployment components can be deployed on top of one or more instances of the one or more core deployment patterns.

Abstract: Disclosed embodiments provide techniques for automatic interdependency resolution for micro-service deployments. A micro-service deployment broker executing on a computing device obtains current environment and feature support of a deployed distributed computing environment. The micro-service deployment broker determines environment and feature requirements for a requested deployment, and compares that with the current environment and feature support of the deployed distributed computing environment. Based on the comparison, a deployment command is issued indicating the deployment plan for the requested deployment. In cases where deployment is not possible or only a partial deployment is possible, an indication is sent to an operator to indicate that full deployment did not occur.

Abstract: A computer-implemented method for performing a cloud computing resource operation in a cloud computing environment is herein provided. The method comprises receiving a request to create a resource from the cloud computing environment using a user interface and intercepting the request of the creation of the resource. The method further comprises determining whether an IT management process needs to be triggered based on a policy rule. In case of a positive outcome of the determination, the method comprises requesting a reserved resource identifier from the cloud computing environment relating to the request, creating a temporary representation identifier of the cloud computing resource, triggering the IT management process, receiving a process identifier from the cloud computing environment for the requested resource, creating the requested resource in the cloud computing environment, and on completion of the creation process, removing the temporary representation identifier.

Abstract: Instantiating a resource of an IT-service includes analyzing a service model of an IT-service, the service model including a node representing a resource for providing the IT-service. A resource type of the resource being indicated by the node is determined, and a resource manager being operable to instantiate the resource is identified. A resource-manager-specific API of the resource manager is identified, and at least one abstract method for instantiating the resource is overridden with a resource-manager specific method of the resource-manager-specific API. The resource-manager specific method for instantiating the resource represented by the node is executed.

Abstract: Placement of instances of virtual machine (VM) images in a cloud computing environment is optimized. A request is received to deploy a new VM image instance. VM resource usage profiles are read that indicate predicted resource consumption data of the VM image. Resource pool profiles for multiple resource pools are read that indicate predicted resource consumption data for the resource pools. For each of the resource pools, the VM resource usage profile is aligned with the respective resource pool profile. An aggregated resource consumption profile is calculated as an aggregation of the predicted resource consumptions of the aligned profiles. A determination is made of one of multiple resource pools with the least predicted aggregated resource consumption, and the VM image is instantiated on the determined one of the multiple resource pools with the least predicted aggregated resource consumption over time.

Abstract: An approach is provided in which an information handling system receives a set of discovery results that correspond to source application services executing in source environments. The information handling system then maps the set of discovery results to a target pattern includes at least one declarative description describing one or more components included in at least one of the one or more source environments. In turn, the information handling system creates a target application service based, at least in part, on the target pattern.

Abstract: A source IT-infrastructure hosts a composite application including multiple functional modules connected to each other via communication links. An abstract pattern includes first nodes and first links representing the functional modules and communication links and lacks resource-related data enabling a deployment engine to instantiate a resource for providing a runtime environment. A target IT-infrastructure has assigned a resource catalog including, for each resource available in the target IT-infrastructure, a specification of the resource's capabilities, and includes second nodes and links, each second node being a representation of one or more of the resources of the target IT-infrastructure and including an indication of the capabilities of one or more resources represented by the second node. The first nodes and links of the abstract pattern are iteratively supplemented by the second nodes and second links.

Abstract: Executing a business process can include providing a context data object including a payload data structure for storing a payload data and automatically splitting an annotated context data object into one or more utility data objects. Responsive to creating a second utility data object, a pre-processing task can be injected into the business process, the pre-processing task using a copy of a first mapping to read data from the predefined data structure instance and to store the read data as payload data in the payload data structure of the first utility data object. Responsive to creating a third utility object, a post-processing task can be injected into the business process. The post-processing task can use a copy of the second mapping to write the payload data of the first utility data object to elements of a predefined data structure instance.

Abstract: A source IT-infrastructure hosts a composite application including multiple functional modules connected to each other via communication links. An abstract pattern includes first nodes and first links representing the functional modules and communication links and lacks resource-related data enabling a deployment engine to instantiate a resource for providing a runtime environment. A target IT-infrastructure has assigned a resource catalog including, for each resource available in the target IT-infrastructure, a specification of the resource's capabilities, and includes second nodes and links, each second node being a representation of one or more of the resources of the target IT-infrastructure and including an indication of the capabilities of one or more resources represented by the second node. The first nodes and links of the abstract pattern are iteratively supplemented by the second nodes and second links.

Abstract: Extension patterns are deployed to core deployment patterns stored in a first software repository. An event relating to registration of a component is detected. In response to detecting the event, a tool registry can be queried to identify one or more extension deployment patterns for use with one or more core deployment patterns. Based upon the query, one or more extension deployment components can be retrieved from a second software repository. The one or more extension deployment components can be deployed on top of one or more instances of the one or more core deployment patterns.

Abstract: Extension patterns are deployed to core deployment patterns stored in a first software repository. An event relating to registration of a component is detected. In response to detecting the event, a tool registry can be queried to identify one or more extension deployment patterns for use with one or more core deployment patterns. Based upon the query, one or more extension deployment components can be retrieved from a second software repository. The one or more extension deployment components can be deployed on top of one or more instances of the one or more core deployment patterns.

Abstract: Extension patterns are deployed to core deployment patterns stored in a first software repository. An event relating to registration of a component is detected. In response to detecting the event, a tool registry can be queried to identify one or more extension deployment patterns for use with one or more core deployment patterns. Based upon the query, one or more extension deployment components can be retrieved from a second software repository. The one or more extension deployment components can be deployed on top of one or more instances of the one or more core deployment patterns.

Abstract: Disclosed embodiments provide techniques for automatic interdependency resolution for micro-service deployments. A micro-service deployment broker executing on a computing device obtains current environment and feature support of a deployed distributed computing environment. The micro-service deployment broker determines environment and feature requirements for a requested deployment, and compares that with the current environment and feature support of the deployed distributed computing environment. Based on the comparison, a deployment command is issued indicating the deployment plan for the requested deployment. In cases where deployment is not possible or only a partial deployment is possible, an indication is sent to an operator to indicate that full deployment did not occur.

Abstract: An order processing system can include an order processing container, a factory registry, a relationship registry, and synchronization function component. The order processing system can handle orders, which are build plans including a set of tasks. The tasks can specify programmatic actions which may include creation, deletion, and modification of resources and resource topologies. The order processing container can be central engine that programmatically drives order processing actions. The factory registry can support a creation and deletion of resource instances in a resource topology defined by at least one order. The relationship registry can maintain relationships among resources. The synchronization function component can permit transparent usage of shared resources in accordance with shared usage resource topology parameters specified within processed orders.

Abstract: Disclosed embodiments provide techniques for automatic interdependency resolution for micro-service deployments. A micro-service deployment broker executing on a computing device obtains current environment and feature support of a deployed distributed computing environment. The micro-service deployment broker determines environment and feature requirements for a requested deployment, and compares that with the current environment and feature support of the deployed distributed computing environment. Based on the comparison, a deployment command is issued indicating the deployment plan for the requested deployment. In cases where deployment is not possible or only a partial deployment is possible, an indication is sent to an operator to indicate that full deployment did not occur.

Abstract: A computer-implemented method for performing a cloud computing resource operation in a cloud computing environment is herein provided. The method comprises receiving a request to create a resource from the cloud computing environment using a user interface and intercepting the request of the creation of the resource. The method further comprises determining whether an IT management process needs to be triggered based on a policy rule. In case of a positive outcome of the determination, the method comprises requesting a reserved resource identifier from the cloud computing environment relating to the request, creating a temporary representation identifier of the cloud computing resource, triggering the IT management process, receiving a process identifier from the cloud computing environment for the requested resource, creating the requested resource in the cloud computing environment, and on completion of the creation process, removing the temporary representation identifier.

Abstract: A computer-implemented method for performing a cloud computing resource operation in a cloud computing environment is herein provided. The method comprises receiving a request to create a resource from the cloud computing environment using a user interface and intercepting the request of the creation of the resource. The method further comprises determining whether an IT management process needs to be triggered based on a policy rule. In case of a positive outcome of the determination, the method comprises requesting a reserved resource identifier from the cloud computing environment relating to the request, creating a temporary representation identifier of the cloud computing resource, triggering the IT management process, receiving a process identifier from the cloud computing environment for the requested resource, creating the requested resource in the cloud computing environment, and on completion of the creation process, removing the temporary representation identifier.