Abstract: A monitoring system can monitor computing processes in clouds. The monitoring system can monitor the clouds for certain events associated with the computing processes. The monitoring system can receive, from the user, a particular event and an action to perform upon the occurrence of the event. Once received, the monitoring system can compare the information collected during monitoring against the event specified by the user. Once the event occurs, the monitoring system can perform the action associated with the event.

Abstract: A method of generating application build options in a cloud computing environment that includes receiving application usage data by a set of currently instantiated applications. The method further includes identifying, in view of the application usage data, a set of application resources in a cloud computing environment. The method further includes identifying additional application resources to be added to the set of application resources, to produce a modified set of application resources. The method further includes determining a cost of utilizing the modified set of application resources. The method further includes generating, in view of the cost of utilizing the modified set of application resources, a recommendation to modify the set of currently instantiated applications.

Abstract: Embodiments relate to managing multi-level service level agreements (SLAs) in cloud-based networks. A resource managing module can manage resources in the cloud-based networks in response to the detection of one or more triggering events. In embodiments, the triggering events can be changeovers in time periods, or meeting or exceeding thresholds associated with end user operation of the resources in the cloud-based networks. The multi-level SLAs can specify how to adjust the resources in the cloud-based networks in response to the detection of the triggering events. The resource managing module can adjust applicable resources in the cloud-based networks as specified by the multi-level SLAs.

Abstract: A compatibility service can determine the compatibility of different software programs provide by different vendors in a cloud. The compatibility service can identify the software programs provided by different vendors in the cloud and which of the identified software programs are compatible. The compatibility service can generate and store a record of the compatible software programs and provide identification, tracking, and mapping services based on the record.

Abstract: Cloud resource provisioning is described. A cloud resource provisioning method may include obtaining cloud resource usage data by a process, wherein the cloud resource usage data identifies a cloud resource consumed by the process and a usage level associated with the cloud resource. The method may also include assigning an importance indicator to the cloud resource, and identifying a recommended cloud resource having available capacity with respect to the usage level in view of the importance indicator.

Abstract: A monitoring system can monitor computing processes in clouds. The monitoring system can monitor the clouds for certain events associated with the computing processes. The monitoring system can receive, from the user, a particular event and an action to perform upon the occurrence of the event. Once received, the monitoring system can compare the information collected during monitoring against the event specified by the user. Once the event occurs, the monitoring system can perform the action associated with the event.

Abstract: A decision system for providing customized application build options to users of a cloud computing environment. The decision system can receive user usage history data and determine a customized set of application resources based on the usage history data. Information about the customized set of application resources can then be supplied to the user.

Abstract: Systems and methods for cross-cloud computing resource usage tracking. An example method comprises: receiving a request comprising an operational specification of a computing resource; selecting a first provisioning cloud in view of the operational specification; receiving an updated operational specification of the computing resource; receiving a first provisioning offer from the first provisioning cloud and a second provisioning offer from a second provisioning cloud responsive to the updated operational specification; selecting the second provisioning cloud in view of the first and second provisioning offers; providing an interface between the first computing resource and a second computing resource residing in a second provisioning cloud; and tracking resource usage data of the first computing resource across the provisioning clouds.

Abstract: Embodiments relate to systems and methods for the aggregate monitoring of utilization data for vendor products in cloud networks. A service can be abstracted and provided external to a set of cloud networks which can access the management system(s), vendor databases, or other resources in those clouds, and generate selective reports on application or other usage across those diverse cloud networks. A network user may wish to generate a report on the usage history of software or services in multiple host clouds, without establishing or accessing individual tracking servers or services in each of the host cloud networks. In aspects, the user may also wish to generate an aggregate report combining multiple vendors, user groups, software, or other attributes. The usage report(s) can be configured to use different criteria or generate different outputs on a dynamic basis, e.g. in different times frames, or altering reports under different usage conditions.

Abstract: A system and method include determining, by a processing device, a first quantity associated with usage of a hardware resource on which a virtual machine is instantiated in a cloud, determining, by the processing device from the virtual machine, a second quantity associated with usage of a software resource utilized on the virtual machine, and determining usage of the cloud in view of the first quantity and the second quantity.

Abstract: A processor receives, from a software vendor system, a rule for converting a software license associated with a software program to a cloud software license associated with using the software program in a cloud computing environment, and receives, from an owner computer of the software license, a request to convert the software license to the cloud software license. The request includes an identifier of the software vendor system and a license identifier. The processor identifies the rule for converting the software license to the cloud software license in view of the received identifier of the software vendor system and the license identifier and converts the software license to the cloud software license in response to the request by changing one or more terms of the software license, in view of the rule, wherein the cloud software license controls usage of a subscription for the software program in the cloud computing environment. The processor transmits the cloud software license to the owner computer.

Abstract: A system and method include determining, by a processing device, a first duration of usage of a hardware resource on which a virtual machine is instantiated in a cloud, determining, by the processing device from the virtual machine on the cloud, a second duration of usage of a software resource that is utilized by a user on the virtual machine, the software resource comprising at least part of an operating system, and calculating, by the processing device, a usage of the cloud by the user in view of the first duration and the second duration.

Abstract: A “Bring Your Own License” (BYOL) service can convert users' “off-the-shelf” (OTS) software licenses for use in public clouds according to rules provided by independent software vendors (ISVs). The BYOL service can offer additional license terms to the users during conversion of the OTS software license on behalf of the ISVs. The additional license terms can be an expansion of the use of the software, an expansion of the technical support offer by the new cloud license, and expansion of the duration of use.

Abstract: Systems and methods for cross-cloud computing resource usage tracking. An example method comprises: receiving a request comprising an operational specification of a computing resource; selecting a first provisioning cloud in view of the operational specification; receiving an updated operational specification of the computing resource; receiving a first provisioning offer from the first provisioning cloud and a second provisioning offer from a second provisioning cloud responsive to the updated operational specification; selecting the second provisioning cloud in view of the first and second provisioning offers; providing an interface between the first computing resource and a second computing resource residing in a second provisioning cloud; and tracking resource usage data of the first computing resource across the provisioning clouds.

Abstract: Embodiments relate to managing multi-level service level agreements (SLAs) in cloud-based networks. A resource managing module can manage resources in the cloud-based networks in response to the detection of one or more triggering events. In embodiments, the triggering events can be changeovers in time periods, or meeting or exceeding thresholds associated with end user operation of the resources in the cloud-based networks. The multi-level SLAs can specify how to adjust the resources in the cloud-based networks in response to the detection of the triggering events. The resource managing module can adjust applicable resources in the cloud-based networks as specified by the multi-level SLAs.

Abstract: Embodiments relate to systems and methods for a cross-cloud vendor mapping service in a dynamic cloud marketplace. The cloud marketplace system receives bids from a user for the provisioning of applications or other software in the cloud, and registers selected provisioning clouds to deliver the requested software. The set of provisioning clouds can be re-selected on a scheduled and/or other ongoing basis, creating a sequence of provisioning clouds. A vendor mapping service can be abstracted and provided external to the cloud marketplace system, and track the user's software usage across the shifting sets of provisioning clouds. The vendor mapping service can aggregate the usage history over time, and generate billing and/or other subscription reports. The cloud marketplace system need only register the user ID, software applications, and/or other subscription data to the vendor mapping service one time, after which the service can track the user's software usage history automatically.

Abstract: Embodiments relate to combinatorial optimization of multiple resources across a set of cloud-based networks. In aspects, a set of usage histories can store patterns for users in a host cloud-based network recording the consumption of processor, memory, storage, operating system, application, or other resources subscribed to by the user. The user can be a corporation or other collective user. A deployment engine can identify similar target resources available in a set of target clouds. The engine can receive selection criteria for selecting target clouds for a migration of the user's deployment. In the combinatorial selection, each target cloud can independently supply one or more target resources. The engine can thus identify a series of combinations of target resources and target clouds supplying those resources to discover combinations of target clouds and target resources that can satisfy or optimize the selection criteria, such as cost or others.

Abstract: A decision system for providing ranked candidate cloud computing environments to customers for migration of subscribed services. The decision system can receive user usage history data and compare parameters of subscribed services on a host cloud to candidate clouds. Based on the comparison, a rank of candidate clouds for migration of the subscribed services can be determined and supplied to the customer.

Abstract: Embodiments relate to systems and methods for managing multi-level service level agreements (SLAs) in cloud-based networks. A resource managing module can manage resources in the cloud-based networks in response to the detection of one or more triggering events. In embodiments, the triggering events can be changeovers in time periods, or meeting or exceeding thresholds associated with end user operation of the resources in the cloud-based networks. The multi-level SLAs can specify how to adjust the resources in the cloud-based networks in response to the detection of the triggering events. The resource managing module can adjust applicable resources in the cloud-based networks as specified by the multi-level SLAs.

Abstract: Embodiments relate to systems and methods for identifying service dependencies in a cloud deployment. In particular, a deployment module can receive usage data from a host cloud comprising data related to end user operation of a set of services in the host cloud as well as service dependencies among the set of services. In embodiments, the deployment module can determine candidate target clouds in which to deploy the set of services. Further, in embodiments, the deployment module can determine whether the candidate target clouds have a capacity to support the set of services, as well as whether services within the candidate target clouds are compatible based on the service dependencies.