International Business Machines Corporation

Robert A Morgan

Kenneth Wayne Roberson

Swaminathan Balasubramanian

Cheranellore Vasudevan

Mitchell Dennis Felton

Jason Matthew Blackwell

Clare T Kibler

Automatically deploying a configured system into a computing environment (such as a cloud computing environment) for execution therein comprises obtaining a configured architecture model describing the configured system, and iteratively evaluating the model to deploy pre-built components for the system and to create and enable a development environment in the computing environment for development of custom-built components needed for the system according to the model. The automated deployment processing further comprises automatically configuring the system; determining a proper installation sequence; allocating resources in the target environment; and installing the required tools and other software that will be needed for execution once the components of the system are deployed. Component metadata is used during the deployment, enabling automated consideration of various factors such as whether component dependencies, resource requirements, and compatibility issues are met.

Automated deployment of a configured system into a computing environment

The configuration of a system is programmatically determined. More particularly, these determinations are made using architecture artifacts that describe requirements of the system (which may be comprised of software, hardware, services, or some combination thereof), where these requirements are iteratively compared to characteristics of available components. A percentage of match is preferably computed, thus allowing for complete matches as well as partial matches. A weighting factor may be applied to attributes, effectively prioritizing attributes in view of their relative importance in the assembled system. When more than one component is a candidate for meeting a particular requirement, user input may be obtained to select one of the candidates. One or more attributes (such as cost information) of each candidate, including how well that candidate matched requirements, may be included for each candidate presented for user selection. The model may be updated and re-evaluated iteratively.

Configuring assembly of a system using supplied architectural artifacts

A requester-side autonomic governor is provided for a requester configured to send service requests to a service provider. For example, the requester and service provider may be disposed in a Service Oriented Architecture (SOA) architected system. A feedback loop, preferably a monitor portion of a Monitor, Analyze, Plan, and Execute (MAPE) loop, is configured to monitor responses to service requests. An autonomic governor mechanism limits the type and/or number of concurrent service requests according to a resource pool scheme, and dynamically adjusts a resource threshold of the resource pool scheme based on information provided by the feedback loop. In one embodiment, the resource threshold is reduced if more than a predetermined number of service requests generated time-outs, and is increased if more than a predetermined number of service requests are being held awaiting available pool resources and less than a predetermined number of service requests generated time-outs.

Requester-side autonomic governor

Computer-implemented method for implementing a requester-side autonomic governor using feedback loop information to dynamically adjust a resource threshold of a resource pool scheme

In general, the present invention allows one to define both a hierarchy with one or more peers and no parents (e.g., one or more blades and no chassis) and a hierarchy with one or more peers and a parent (e.g., one or more blades and a chassis) as long as the relationships are valid. Rather than relying on a user's a priori knowledge of the hierarchical relationships, this invention allows a user to select any starting point and then drive in any desired direction. Despite this flexibility, the invention still allows rules for permissible relationships to be enforced. Thus, driving is limited by the relationships extant in the underlying data, or the known combining rules.

Growing community of inventors

Apex, NC, United States of America

Robert A Morgan