Abstract: A mechanism for declarative service domain federation uses a declarative approach to both the visibility aspect and the management aspect of service domain federation. Instead of manually exporting services, that is, selecting individual services from source domains to be visible in the target domain, using the present system, a federation architect uses a federation console to specify federation intent. The federation intent may include federation rule, query-based service group, and quality-of-service (QoS) policy. Based on the declared federation intent, a planning engine resolves the individual services based on the group query, generates the service visibility configuration, and creates the necessary service proxies and/or mediation objects to satisfy the goal. At runtime, a service monitor collects the performance metrics of federated services and dynamically adjusts the mediation/proxy configurations to maintain the QoS objectives specified by the federation architect.

Abstract: A mechanism for declarative service domain federation uses a declarative approach to both the visibility aspect and the management aspect of service domain federation. Instead of manually exporting services, that is, selecting individual services from source domains to be visible in the target domain, using the present system, a federation architect uses a federation console to specify federation intent. The federation intent may include federation rule, query-based service group, and quality-of-service (QoS) policy. Based on the declared federation intent, a planning engine resolves the individual services based on the group query, generates the service visibility configuration, and creates the necessary service proxies and/or mediation objects to satisfy the goal. At runtime, a service monitor collects the performance metrics of federated services and dynamically adjusts the mediation/proxy configurations to maintain the QoS objectives specified by the federation architect.

Abstract: A mechanism for declarative service domain federation uses a declarative approach to both the visibility aspect and the management aspect of service domain federation. Instead of manually exporting services, that is, selecting individual services from source domains to be visible in the target domain, using the present system, a federation architect uses a federation console to specify federation intent. The federation intent may include federation rule, query-based service group, and quality-of-service (QoS) policy. Based on the declared federation intent, a planning engine resolves the individual services based on the group query, generates the service visibility configuration, and creates the necessary service proxies and/or mediation objects to satisfy the goal. At runtime, a service monitor collects the performance metrics of federated services and dynamically adjusts the mediation/proxy configurations to maintain the QoS objectives specified by the federation architect.

Abstract: Integrating data processing resources across a hybrid cloud includes providing a plug-in software component configured to be installed in a software framework. When the plug-in software component is activated, it may generate an interface for a consumer of data processing resources. Using this interface, the consumer of data processing resources may request the use of data processing resources provided as a service on the hybrid cloud. In response, the plug-in software component may acquire the requested data processing resources via interfaces provided by the various data processing resources. A number of different data processing resources may have different interface requirements. However, the first interface generated by the plug-in software component may provide a single vendor neutral interface for accessing data processing resources on the hybrid cloud by the consumer of data processing resources.

Abstract: A hybrid cloud integrator provides a capability for integrating data processing resources provided as services across a hybrid cloud. The hybrid cloud integrator includes a software framework that provides for installing, configuring, activating, and controlling operation of a number of plug-in software components. The plug-in software components are configured to provide for using data processing resources provided as a service to process a consumer workload.

Abstract: A mechanism for declarative service domain federation uses a declarative approach to both the visibility aspect and the management aspect of service domain federation. Instead of manually exporting services, that is, selecting individual services from source domains to be visible in the target domain, using the present system, a federation architect uses a federation console to specify federation intent. The federation intent may include federation rule, query-based service group, and quality-of-service (QoS) policy. Based on the declared federation intent, a planning engine resolves the individual services based on the group query, generates the service visibility configuration, and creates the necessary service proxies and/or mediation objects to satisfy the goal. At runtime, a service monitor collects the performance metrics of federated services and dynamically adjusts the mediation/proxy configurations to maintain the QoS objectives specified by the federation architect.

Abstract: A method, apparatus, and computer program product for managing a workload in a hybrid cloud. It is determined whether first data processing resources processing a portion of a workload are overloaded. Responsive to a determination that the first data processing resources are overloaded, second data processing resources are automatically provisioned and the portion of the workload is automatically moved to the second data processing resources for processing. The second data processing resources are data processing resources that are provided as a service on the hybrid cloud. Processing of a first portion of a workload being processed on first data processing resources of a hybrid cloud are monitored simultaneously with monitoring processing of a second portion of the workload being processed on second data processing resources of the hybrid cloud. The workload may be allocated automatically between the first portion and the second portion responsive to the simultaneous monitoring.

Abstract: Integrating data processing resources across a hybrid cloud includes providing a plug-in software component configured to be installed in a software framework. When the plug-in software component is activated, it may generate an interface for a consumer of data processing resources. Using this interface, the consumer of data processing resources may request the use of data processing resources provided as a service on the hybrid cloud. In response, the plug-in software component may acquire the requested data processing resources via interfaces provided by the various data processing resources. A number of different data processing resources may have different interface requirements. However, the first interface generated by the plug-in software component may provide a single vendor neutral interface for accessing data processing resources on the hybrid cloud by the consumer of data processing resources.

Abstract: A hybrid cloud integrator provides a capability for integrating data processing resources provided as services across a hybrid cloud. The hybrid cloud integrator includes a software framework that provides for installing, configuring, activating, and controlling operation of a number of plug-in software components. The plug-in software components are configured to provide for using data processing resources provided as a service to process a consumer workload.