Hybrid Cloud Broker with Static and Dynamic Capability Matching

1. A method comprising: collecting static capabilities of at least two infrastructure computing systems using a multi-staged broker, collecting dynamic capabilities of said at least two infrastructure computing systems using said multi-staged broker, combining said static capabilities and said dynamic capabilities for determining a first most suitable infrastructure system for deploying a service requiring a computing environment satisfying attribute values of a service capability profile, deploying said service on said first most suitable infrastructure system, receiving an event indicative of a change, reassessing said determination regarding said most suitable infrastructure system and repeating said combining said static capabilities and said dynamic capabilities for determining a second most suitable infrastructure system for deploying said service satisfying said attribute values of said service capability profile, and redeploying said service on said second most suitable infrastructure system, wherein said redeploying said service on said first most suitable infrastructure system comprises stopping said deploying of said service on said first most suitable infrastructure system, wherein the method includes receiving from an owner of the service, data defined by the owner, generating based on the owner defined data, a service definition record, wherein the service definition record generated based on the owner defined data includes a service definition ID, a service name, a service part identifier, and for first and second different parts of the service, owner defined requirements, wherein the owner defined requirements include first requirements for the first part of the service and second requirements for the second part of the service, wherein the service definition record further includes an owner defined policy.

2. The method of claim 1 , wherein the stopping said deploying of said service on the first most suitable infrastructure system includes stopping said deploying of said service on said first most suitable infrastructure system without deleting of said service on said first most suitable infrastructure system, wherein the method includes later restarting said service on said first most suitable infrastructure system.

3. A method comprising: collecting first changing capabilities of at least two infrastructure computing systems using a multi-staged broker, collecting second changing capabilities of said at least two infrastructure computing systems using said multi-staged broker, combining said first changing capabilities and said second changing capabilities for determining a first most suitable infrastructure system for deploying a service requiring a computing environment satisfying attribute values of a service capability profile, deploying said service on said first most suitable infrastructure system, receiving an event indicative of a change, reassessing said determination regarding said most suitable infrastructure system and repeating said combining said first changing capabilities and said second changing capabilities for determining a second most suitable infrastructure system for deploying said service satisfying said attribute values of said service capability profile, and redeploying said service on said second most suitable infrastructure system, wherein said redeploying said service on said first most suitable infrastructure system comprises stopping said deploying of said service on said first most suitable infrastructure system, wherein the method includes receiving from an owner of the service, data defined by the owner, generating based on the owner defined data, a service definition record, wherein the service definition record generated based on the owner defined data includes a service definition ID, a service name, a service part identifier, and for first and second different parts of the service, owner defined requirements, wherein the owner defined requirements include first requirements for the first part of the service and second requirements for the second part of the service, wherein the service definition record further includes an owner defined policy.

4. The method according to claim 3 , wherein said redeploying said service on said first most suitable infrastructure system comprises deleting said service on said first most suitable infrastructure system.

5. The method of claim 3 , wherein the method comprises a selecting a first infrastructure system for deployment of the first part of the service based on the first requirements and selecting a second infrastructure system for deployment of the second part of the service based on the second requirements.

6. The method of claim 3 , wherein the method comprises a selecting a first infrastructure system for deployment of the first part of the service based on the first requirements and selecting a second infrastructure system for deployment of the second part of the service based on the second requirements, and wherein the method includes simultaneously running the first part of the service on the first infrastructure system and the second part of the service on the second infrastructure system, wherein the method includes discontinuing running of the first part of the service on the first infrastructure system in response to an outage of the first infrastructure system and continuing to run the second part of the service on the second infrastructure system during the outage on the first infrastructure system.

7. The method of claim 3 , wherein the method includes receiving from the owner of the service, owner defined requirements and owner policies defined by the owner for the service, wherein the method includes performing a matching of capabilities of candidate infrastructure systems against the owner defined requirements defined by the owner for the service and performing a filtering of the candidate infrastructure systems in dependence on the owner defined policies for the service defined by the owner.

8. The method of claim 3 , wherein the service definition record further includes an owner defined policy, wherein the owner defined requirements are defined on a per service part basis and wherein the owner defined policy is defined by the owner on a per service basis so that for a given service having first and second parts there is defined first requirements for the first service part, second requirements for the second service part, and a policy for the service that comprises the first and second service parts, wherein the method includes receiving from the owner of the service the first requirements for the first service part, second requirements for the second service part, and a policy for the service that comprises the first and second service parts, wherein the method includes performing a matching of capabilities of candidate infrastructure systems against the owner defined first requirements and second requirements defined by the owner for the service and performing a filtering of the candidate infrastructure systems in dependence on the owner defined policy for the service defined by the owner.

9. The method of claim 3 , wherein the method includes receiving from an owner of the service data defined by the owner, generating based on the owner defined data, a service definition record, wherein the service definition record generated based on the owner defined data includes a service definition ID, a service name, a service part identifier, and for first and second different parts of the service, owner defined requirements, wherein the owner defined requirements include first requirements for the first part of the service and second requirements for the second part of the service, wherein the service definition record further includes an owner defined policy, wherein the owner defined requirements are defined on a per service part basis and wherein the owner defined policy is defined by the owner on a per service basis so that for a given service having first and second parts there is defined first requirements for the first service part, second requirements for the second service part, and a policy for the service that comprises the first and second service parts, wherein the method includes receiving from the owner of the service the first requirements for the first service part, second requirements for the second service part, and a policy for the service that comprises the first and second service parts, wherein the method includes performing a matching of capabilities of candidate infrastructure systems against the owner defined first requirements and second requirements defined by the owner for the service and performing a filtering of the candidate infrastructure systems in dependence on the owner defined policy for the service defined by the owner, wherein the method includes creating at least one capability record specifying names of capabilities of respective infrastructure systems, types of capabilities, and capability values, wherein the method includes receiving from an owner of the service data defined by the owner, generating based on the owner defined data, a service definition record, wherein the service definition record generated based on the owner defined data includes a service definition ID, a service name, a service part identifier, and for first and second different parts of the service, owner defined requirements, wherein the owner defined requirements include first requirements for the first part of the service and second requirements for the second part of the service, wherein the service definition record further includes an owner defined policy, wherein owner defined requirements of the service definition record include optional conditions defined by the owner and mandatory conditions defined by the owner, wherein the method comprises a selecting a first infrastructure system for deployment of the first part of the service based on the first requirements and selecting a second infrastructure system for deployment of the second part of the service based on the second requirements, and wherein the method includes simultaneously running the first part of the service on the first infrastructure system and the second part of the service on the second infrastructure system, wherein the method includes discontinuing running of the first part of the service on the first infrastructure system in response to an outage of the first infrastructure system and continuing to run the second part of the service on the second infrastructure system during the outage on the first infrastructure system.

10. The method according to claim 3 , wherein said collecting first changing capabilities comprises: receiving messages by said multi-staged broker from a sensory adapter connected to at least one of said at least two infrastructure systems, wherein said messages are indicative of non-continuously changing characteristic values of said at least two infrastructure systems.

11. The method according to claim 3 , wherein said collecting second changing capabilities comprises: receiving messages by said multi-staged broker from a sensory adapter connected to at least one of said at least two infrastructure computing systems, wherein said messages are indicative of continuously changing characteristic values of said at least two infrastructure systems.

12. The method according to claim 3 , wherein said combining said first changing capabilities and said second changing capabilities comprises: creating at least one capability record representing logically names of capabilities, types of capabilities and/or related type capability values of said at least two infrastructure systems; creating at least one service provider record identifying said service provider by a unique identifier; and determining by said multi-staged broker a list of potential infrastructure systems out of which said most suitable infrastructure system is selected for a deployment of said service.

13. The method according to claim 3 , wherein said service capability profile of said service includes each of a service description, a service provider name, a unique identifier of a service provider, a capability type name, a capability type identifier, a performance indicator, an operating system indicator, a storage amount indicator, a scaling indicator, a cost indicator, a hardware architecture indicator, a hypervisor type indicator, and an availability guarantee indicator.

14. The method according to claim 3 , wherein said redeploying said service on said first most suitable infrastructure system comprises deleting said service on said first most suitable infrastructure system.

15. The method according to claim 3 , wherein the event indicative of a change includes each of (a) an event indicative of a change of said first changing capabilities, (b) an event indicative of a change of said second changing capabilities, and (c) an event indicative of a change of said service capability profile.

16. The method according to claim 3 , wherein for successive iterations of said reassessing said determination regarding said most suitable infrastructure system is performed according to each of: (a) periodically, (b) at predefined points in time, and (c) upon receiving said event.

17. The method according to claim 3 , wherein said collecting first changing capabilities comprises: receiving messages by said multi-staged broker from a sensory adapter connected to at least one of said at least two infrastructure systems, wherein said messages are indicative of non-continuously changing characteristic values of said at least two infrastructure systems, wherein said collecting first changing capabilities comprises: receiving messages by said multi-staged broker from a sensory adapter connected to at least one of said at least two infrastructure systems, wherein said messages are indicative of non-continuously changing characteristic values of said at least two infrastructure systems, wherein said collecting second changing capabilities comprises: receiving messages by said multi-staged broker from said sensory adapter connected to at least one of said at least two infrastructure computing systems, wherein said messages are indicative of continuously changing characteristic values of said at least two infrastructure systems.

18. The method according to claim 3 , wherein said collecting first changing capabilities comprises: receiving messages by said multi-staged broker from a sensory adapter connected to at least one of said at least two infrastructure systems, wherein said messages are indicative of non-continuously changing characteristic values of said at least two infrastructure systems, wherein said collecting first changing capabilities comprises: receiving messages by said multi-staged broker from a sensory adapter connected to at least one of said at least two infrastructure systems, wherein said messages are indicative of non-continuously changing characteristic values of said at least two infrastructure systems, wherein said collecting second changing capabilities comprises: receiving messages by said multi-staged broker from said sensory adapter connected to at least one of said at least two infrastructure computing systems, wherein said messages are indicative of continuously changing characteristic values of said at least two infrastructure systems, wherein the event indicative of a change includes each of (a) an event indicative of a change of said first changing capabilities, (b) an event indicative of a change of said second changing capabilities, and (c) an event indicative of a change of said service capability profile.

19. The method of claim 3 , wherein the stopping said deploying of said service on the first most suitable infrastructure system includes stopping said deploying of said service on said first most suitable infrastructure system without deleting of said service on said first most suitable infrastructure system, wherein the method includes later restarting said service on said first most suitable infrastructure system.