Dynamic allocation of workload deployment units across a plurality of clouds

Abstract

A method of selectively allocating a plurality of deployment units among a plurality of clouds. The method can include identifying a first context of a first deployment unit of a workload and identifying a second context of a second deployment unit of the workload. Based on the first context, a first of the plurality of clouds that satisfies at least one requirement indicated by the first context can be identified and the first deployment unit can be automatically allocated to the first cloud. Based on the second context, a second of the plurality of clouds that satisfies at least one requirement indicated by the second context can be identified, wherein the first cloud does not satisfy the requirement indicated by the second context, and the second deployment unit can be automatically allocated to the second cloud.

What is claimed is: 
     
       1. A computer-implemented method of selectively allocating a plurality of deployment units among a plurality of clouds, comprising:
 identifying a first context indicating a first functional requirement or non-functional requirement of a first deployment unit within a workload; 
 identifying a second context indicating a second functional requirement or non-functional requirement of a second deployment unit within the workload; 
 identifying, using the first context indicating the first functional requirement or non-functional requirement of the first deployment unit within the workload, a first cloud of the plurality of clouds that satisfies the first functional requirement or non-functional requirement; 
 automatically allocating the first deployment unit to the first cloud; 
 identifying, using the second context indicating the second functional requirement or non-functional requirement of the second deployment unit within the workload, a second cloud of the plurality of clouds that satisfies the second functional requirement or non-functional requirement; 
 automatically allocating the second deployment unit to the second cloud, wherein the first cloud does not satisfy the second functional requirement or non-functional requirement. 
 
     
     
       2. The method of  claim 1 , wherein
 a deployment plan that identifies to which of the first and second clouds the first and second deployment units are allocated is automatically created based upon the first and second contexts. 
 
     
     
       3. The method of  claim 2 , wherein
 the automatically allocating the first deployment unit to the first cloud is based upon the deployment plan; and 
 the automatically allocating the second deployment unit to the second cloud comprises is based upon the deployment plan. 
 
     
     
       4. The method of  claim 1 , wherein:
 the identifying the first context includes identifying metadata associated with the first deployment unit that indicates a first functional requirement of the first deployment unit; and 
 the identifying the second context includes identifying metadata associated with the second deployment unit that indicates a second functional requirement of the second deployment unit. 
 
     
     
       5. The method of  claim 4 , wherein
 the first and second functional requirements are each performance requirements. 
 
     
     
       6. The method of  claim 1 , wherein:
 identifying the first context includes identifying metadata associated with the first deployment unit that indicates a first non-functional requirement of the first deployment unit; and 
 identifying the second context includes identifying metadata associated with the second deployment unit that indicates a second non-functional requirement of the second deployment unit. 
 
     
     
       7. The method of  claim 6 , wherein
 the first and second non-functional requirement are each security requirements. 
 
     
     
       8. The method of  claim 1 , wherein
 a determination is made whether the first cloud continues to satisfy the first functional requirement after the first and second deployment units have been respectively allocated to the first and second clouds; 
 upon the first cloud not satisfying the first functional requirement, another cloud that satisfies the first functional requirement is identified; and 
 the first deployment unit is automatically allocated to the another cloud. 
 
     
     
       9. A computer hardware system, comprising: a hardware processor configured to initiate the following executable operations:
 identifying a first context indicating a first functional requirement or non-functional requirement of a first deployment unit within a workload; 
 identifying a second context indicating a second functional requirement or non-functional requirement of a second deployment unit within the workload; 
 identifying, using the first context indicating the first functional requirement or non-functional requirement of the first deployment unit within the workload, a first cloud of the plurality of clouds that satisfies the first functional requirement or non-functional requirement; 
 automatically allocating the first deployment unit to the first cloud; 
 identifying, using the second context indicating the second functional requirement or non-functional requirement of the second deployment unit within the workload, a second cloud of the plurality of clouds that satisfies the second functional requirement or non-functional requirement; 
 automatically allocating the second deployment unit to the second cloud, wherein:
 the first cloud does not satisfy the second functional requirement or non-functional requirement. 
 
 
     
     
       10. The system of  claim 9 , wherein
 a deployment plan that identifies to which of the first and second clouds the first and second deployment units are allocated is automatically created based upon the first and second contexts. 
 
     
     
       11. The system of  claim 10 , wherein
 the automatically allocating the first deployment unit to the first cloud is based upon the deployment plan; and 
 the automatically allocating the second deployment unit to the second cloud comprises is based upon the deployment plan. 
 
     
     
       12. The system of  claim 9 , wherein:
 the identifying the first context includes identifying metadata associated with the first deployment unit that indicates a first functional requirement of the first deployment unit; and 
 the identifying the second context includes identifying metadata associated with the second deployment unit that indicates a second functional requirement of the second deployment unit. 
 
     
     
       13. The system of  claim 12 , wherein
 the first and second functional requirements are each performance requirements. 
 
     
     
       14. The system of  claim 9 , wherein:
 identifying the first context includes identifying metadata associated with the first deployment unit that indicates a first non-functional requirement of the first deployment unit; and 
 identifying the second context includes identifying metadata associated with the second deployment unit that indicates a second non-functional requirement of the second deployment unit. 
 
     
     
       15. The system of  claim 14 , wherein
 the first and second non-functional requirement are each security requirements. 
 
     
     
       16. The system of  claim 9 , wherein
 a determination is made whether the first cloud continues to satisfy the first functional requirement after the first and second deployment units have been respectively allocated to the first and second clouds; 
 upon the first cloud not satisfying the first functional requirement, another cloud that satisfies the first functional requirement is identified; and 
 the first deployment unit is automatically allocated to the another cloud. 
 
     
     
       17. A computer program product, comprising:
 a hardware storage device having program code stored therein, 
 the program code, which when executed by a computer hardware system, causes the computer hardware system to perform:
 identifying a first context indicating a first functional requirement or non-functional requirement of a first deployment unit within a workload; 
 identifying a second context indicating a second functional requirement or non-functional requirement of a second deployment unit within the workload; 
 identifying, using the first context indicating the first functional requirement or non-functional requirement of the first deployment unit within the workload, a first cloud of the plurality of clouds that satisfies the first functional requirement or non-functional requirement; 
 automatically allocating the first deployment unit to the first cloud; 
 identifying, using the second context indicating the second functional requirement or non-functional requirement of the second deployment unit within the workload, a second cloud of the plurality of clouds that satisfies the second functional requirement or non-functional requirement; 
 automatically allocating the second deployment unit to the second cloud, 
 wherein:
 the first cloud does not satisfy the second functional requirement or non-functional requirement. 
 
 
 
     
     
       18. The computer program product of  claim 17 , wherein
 a deployment plan that identifies to which of the first and second clouds the first and second deployment units are allocated is automatically created based upon the first and second contexts. 
 
     
     
       19. The computer program product of  claim 18 , wherein
 the automatically allocating the first deployment unit to the first cloud is based upon the deployment plan; and 
 the automatically allocating the second deployment unit to the second cloud comprises is based upon the deployment plan. 
 
     
     
       20. The computer program product of  claim 17 , wherein
 a determination is made whether the first cloud continues to satisfy the first functional requirement after the first and second deployment units have been respectively allocated to the first and second clouds; 
 upon the first cloud not satisfying the first functional requirement, another cloud that satisfies the first functional requirement is identified; and 
 the first deployment unit is automatically allocated to the another cloud.