Abstract: An incompatible software level of an information technology infrastructure component is determined by comparing collected inventory information to a minimum recommended software level. If a knowledge base search finds that the incompatible software level is associated with a prior infrastructure outage event, an outage count score is determined for the incompatible software level by applying an outage rule to a historic count of outages caused by a similar incompatible software level, and combined with an average outage severity score assigned to the incompatible software level based on a level of severity of an actual historic failure of the component within a context of the infrastructure to generate a normalized historical affinity risk score. The normalized historical affinity risk score is provided for prioritizing the correction of the incompatible software level in the context of other normalized historical risk level scores of other determined incompatible software levels.

Abstract: Server consolidation using virtual machine resource tradeoffs, is provided. One implementation involves assigning a virtual machine to a target physical server based on a plurality of virtualization parameters for maximizing utility of a plurality of virtual machines and physical servers. The assigning performs resource allocation for the virtual machine based on capabilities of the target physical server and a plurality of virtual machine resource requirements. Virtualization parameters include a reservation parameter (min) representing a minimum resources required for a VM, a limit parameter (max) representing a maximum resources allowable for the VM, and a weight parameter (shares) representing a share of spare resources for the VM.

Abstract: The present invention proactively identifies hotspots in a cloud computing environment through cloud resource usage models that use workload parameters as inputs. In some embodiments the cloud resource usage models are based upon performance data from cloud resources and time series based workload trend models. Hotspots may occur and can be detected at any layer of the cloud computing environment, including the server, storage, and network level. In a typical embodiment, parameters for a workload are identified in the cloud computing environment and inputted into a cloud resource usage model. The model is run with the inputted workload parameters to identify potential hotspots, and resources are then provisioned for the workload so as to avoid these hotspots.

Abstract: A method and system for intelligent tiering is provided. The method includes receiving a request for enabling a tiering process with respect to data. The computer processor retrieves a migration list indicating migration engines associated with the data. Additionally, an entity list of migration entities is retrieved and each migration entity is compared to associated policy conditions. In response, it is determined if matches exist between the migration entities and the associated policy conditions and a consolidated entity list is generated.

Abstract: A method and system. In response to a request for a proposed additional data transfer from a source storage system to a target storage system, an estimate is made of utilization of one or more data transfer components of the source storage system and the target storage system that would occur during the proposed additional data transfer combined with other scheduled data transfers involving the source storage system and the target storage system, based in part on (i) an I/O request rate for recent actual data transfers involving the source storage system and the target storage system combined with (ii) an estimated I/O request rate for the proposed additional data transfer. It is ascertained whether the estimated utilization exceeds a corresponding utilization threshold. If so, execution of the proposed additional data transfer is postponed. If not, execution of the proposed additional data transfer is initiated.

Abstract: A method and system for intelligent tiering is provided. The method includes receiving a request for enabling a tiering process with respect to data. The computer processor retrieves a migration list indicating migration engines associated with the data. Additionally, an entity list of migration entities is retrieved and each migration entity is compared to associated policy conditions. In response, it is determined if matches exist between the migration entities and the associated policy conditions and a consolidated entity list is generated.

Abstract: The present invention proactively identifies hotspots in a cloud computing environment through cloud resource usage models that use workload parameters as inputs. In some embodiments the cloud resource usage models are based upon performance data from cloud resources and time series based workload trend models. Hotspots may occur and can be detected at any layer of the cloud computing environment, including the server, storage, and network level. In a typical embodiment, parameters for a workload are identified in the cloud computing environment and inputted into a cloud resource usage model. The model is run with the inputted workload parameters to identify potential hotspots, and resources are then provisioned for the workload so as to avoid these hotspots.

Abstract: In general, embodiments of present invention provide an approach for calibrating a cloud computing environment. Specifically, embodiments of the present invention provide an empirical approach for obtaining end-to-end performance characteristics for workloads in the cloud computing environment (hereinafter the “environment”). In a typical embodiment, different combinations of cloud server(s) and cloud storage unit(s) are determined. Then, a virtual machine is deployed to one or more of the servers within the cloud computing environment. The virtual machine is used to generate a desired workload on a set of servers within the environment. Thereafter, performance measurements for each of the different combinations under the desired workload will be taken. Among other things, the performance measurements indicate a connection quality between the set of servers and the set of storage units, and are used in calibrating the cloud computing environment to determine future workload placement.

Abstract: Embodiments of the invention relate to dynamic application migration in a shared pool of configurable computer resources with disaster recovery support. Write operations are executed by an application at a first data site. Data is generated and stored in first data storage local to the first data site. The stored data is replicated from the first data storage to a backup data storage, and a consistency point of the data is created in both the first data storage and the backup data storage. In response to a local hardware failure at the first data site, an unplanned migration protocol is initialized to migrate the application to a second data site remote from the first data site, which includes re-launching the application at the second data site. Data is transferred from the backup data storage to the second data storage local to the second data site from the consistency point.

Abstract: Scheduling a proposed additional data transfer from one or more source storage devices to one or more target storage devices. A computer receives a request for the proposed additional data transfer, and in response, determines a measure of the proposed additional data transfer. The computer determines a measure of recent actual data transfers. The recent actual data transfers involve one or more of the source storage devices and one or more of the target storage devices. In response to the request for the proposed additional data transfer, the computer estimates performance of one or more of the source storage devices and one or more of the target storage devices that would occur during the proposed additional data transfer based on the measure of recent actual data transfers combined with the measure of the proposed additional data transfer.

Abstract: A method and system for intelligent tiering is provided. The method includes receiving a request for enabling a tiering process with respect to data. The computer processor retrieves a migration list indicating migration engines associated with the data. Additionally, an entity list of migration entities is retrieved and each migration entity is compared to associated policy conditions. In response, it is determined if matches exist between the migration entities and the associated policy conditions and a consolidated entity list is generated.

Abstract: Embodiments of the invention relate to dynamic application migration in a shared pool of configurable computer resources with disaster recovery support. Data from an application is replicated from local data storage to remote data storage. A consistency point of the data is created in both the local data storage and the remote data storage. The application may be migrated to a second data site with separate local data storage. The migration may be planned or unplanned. Based upon the created consistency point, a consistent set of application data may be requested to support a read operation from the migrated application.

Abstract: A method and system for intelligent tiering is provided. The method includes receiving a request for enabling a tiering process with respect to data. The computer processor retrieves a migration list indicating migration engines associated with the data. Additionally, an entity list of migration entities is retrieved and each migration entity is compared to associated policy conditions. In response, it is determined if matches exist between the migration entities and the associated policy conditions and a consolidated entity list is generated.

Abstract: A method and system for intelligent tiering is provided. The method includes receiving a request for enabling a tiering process with respect to data. The computer processor retrieves a migration list indicating migration engines associated with the data. Additionally, an entity list of migration entities is retrieved and each migration entity is compared to associated policy conditions. In response, it is determined if matches exist between the migration entities and the associated policy conditions and a consolidated entity list is generated.

Abstract: An incompatible software level of an information technology infrastructure component is determined by comparing collected inventory information to a minimum recommended software level. If a knowledge base search finds that the incompatible software level is associated with a prior infrastructure outage event, an outage count score is determined for the incompatible software level by applying an outage rule to a historic count of outages caused by a similar incompatible software level, and combined with an average outage severity score assigned to the incompatible software level based on a level of severity of an actual historic failure of the component within a context of the infrastructure to generate a normalized historical affinity risk score. The normalized historical affinity risk score is provided for prioritizing the correction of the incompatible software level in the context of other normalized historical risk level scores of other determined incompatible software levels.

Abstract: Embodiments of the present invention provide an integrated host and subsystem port selection methodology that uses performance measurements combined with information about active data paths. This technique also helps in resilient fabric planning by selecting ports from redundant fabrics. In a typical embodiment, host port to storage port pairs that create a path between a host and a storage device will be identified. From these pairs, a set of host port to storage port candidates for communicate data from the host to the storage device will be identified based on a set of resiliency constraints. Then, a specific host port to storage port pair will be selected from the set based on a lowest joint workload measurement. A path will then be created between the specific host port and storage port, and data will be communicated from the host to the storage device via the path.

Abstract: An incompatible software level of an information technology infrastructure component is determined by comparing collected inventory information to a minimum recommended software level. If a knowledge base search finds that the incompatible software level is associated with a prior infrastructure outage event, an outage count score is determined for the incompatible software level by applying an outage rule to a historic count of outages caused by a similar incompatible software level, and combined with an average outage severity score assigned to the incompatible software level based on a level of severity of an actual historic failure of the component within a context of the infrastructure to generate a normalized historical affinity risk score. The normalized historical affinity risk score is provided for prioritizing the correction of the incompatible software level in the context of other normalized historical risk level scores of other determined incompatible software levels.

Abstract: Methods, systems, and articles of manufacture for identifying compatible system configurations are provided herein. A method includes generating a second graph from a first graph of multiple devices in a network and a set of one or more network compatibility rules, wherein said generating comprises dividing each device in the first graph into multiple nodes in the second graph, and wherein each node in the second graph represents a valid configuration of a device in the first graph; identifying a sub-graph of two or more linked nodes in the second graph that is isomorphic to at least a portion of the first graph, wherein the two or more linked nodes in the second graph represent two or more configurations that are compatible based on the set of one or more network compatibility rules; and determining each of one or more changes needed to convert a current configuration in the network to a target configuration specified by the sub-graph.

Abstract: An approach for reactive throttling of heterogeneous migration sessions running concurrently in a virtualized cloud environment is disclosed. The heterogeneous migration sessions are characterized by several attributes such as the type of function performed by the migration session and the value that is attained by performing the migration session. An input/output (I/O) path to any resource in the virtualized cloud environment computing that is experiencing excessive resource congestion is identified. Bottlenecks along the I/O path are then determined. Virtual-to-physical resource mapping information of resources in the virtualized cloud computing environment are used to obtain a list of the heterogeneous migration sessions contributing to the bottlenecks along the identified I/O path.

Abstract: Computing resource allocation for map-reduce job execution comprises determining the volume of input data to the map-phase and the reduce-phase of a map-reduce job prior to execution. Based on said determination, data blocks and virtual machines (VMs) are selectively placed for locality aware map-reduce job execution on a cluster of computing nodes in a network. Selectively placing data blocks and VMs comprises integrally placing the data and the VMs at selected nodes to lower data transfer network hops for a map-phase and a shuffle-phase of the map-reduce job upon execution by the VMs.