CONFIGURING CLOUD RESOURCES

• US 20140136717A1
• Filed: 01/22/2014
• Published: 05/15/2014
• Est. Priority Date: 06/09/2010
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: KUMAR, ARCHANA, SUKTHANKAR, VIJAY K., BALANI, NAVEEN G.
• Granted Patent: US 9,363,195 B2
• Time in Patent Office: Days
• US Class Current: 709/226
• CPC Class Codes: G06F 9/5072 Grid computing
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

A method, system, and program product for identifying cloud resources are provided, and further a method, system, and program product for configuring cloud resources are provided. The method for identifying cloud resources may include receiving a request with respect to at least one resource in a cloud and determining a set of resources among the at least one resource in the cloud in accordance with the received request. Determining the set of resources may include consulting an ontology including metadata associated with the at least one resource in the cloud and computing the set of resources based on the metadata and the received request. Additionally, the method may include computing a cost factor with respect to the determined set of resources. Furthermore, the method may include rendering, in response to the received request, the determined set of resources and the cost factor with respect to the determined set of resources.

Claims

1-9. -9. (canceled)

10. A method comprising:

identifying at least one new resource to add to a cloud, the cloud comprising at least one preexisting resource;

creating, by operation of at least one processor, an ontology extension for the at least one new resource including metadata associated with the at least one new resource;

creating a relationship between the at least one new resource and the at least one preexisting resource, and storing information regarding the relationship among the metadata included in the ontology extension; and

storing the ontology extension.

11. The method of claim 10, further comprising propagating information with respect to the at least one new resource to the at least one preexisting resource.

23. The method of claim 10, wherein the metadata associated with the at least one new resource is stored in a repository along with metadata associated with the at least one preexisting resource.

24. The method of claim 23, wherein the repository stores the metadata associated with the at least one new resource in one of a structured format, an unstructured format, or a combination of structured and unstructured formats.

25. The method of claim 10, wherein the metadata associated with the at least one new resource comprises cost factor information for each of the at least one resource.

26. The method of claim 10, wherein the metadata associated with the at least one new resource comprises instance information that includes capabilities supported by each of the at least one new resource.

27. The method of claim 10, wherein the relationship between the at least one new resource and the at least one preexisting resource is represented by a look up table.

12-20. -20. (canceled)

21. A computer program product comprising a computer-readable storage medium having computer-readable program code instructions stored therein comprising:

a first set of instructions for identifying at least one new resource to add to a cloud, the cloud comprising at least one preexisting resource;

a second set of instructions for creating an ontology extension for the at least one new resource including metadata associated with the at least one new resource;

a third set of instructions for creating a relationship between the at least one new resource and the at least one preexisting resource and for storing information regarding the relationship among the metadata included in the ontology extension; and

a fourth set of instructions for storing the ontology extension.

22. The computer program product of claim 21, further comprising a fifth set of instructions for propagating information with respect to the at least one new resource to the at least one preexisting resource.

28. The computer program product of claim 21, wherein the metadata associated with the at least one new resource is stored in a repository along with metadata associated with the at least one preexisting resource.

29. The computer program product of claim 28, wherein the repository stores the metadata associated with the at least one new resource in one of a structured format, an unstructured format, or a combination of structured and unstructured formats.

30. The computer program product of claim 21, wherein the metadata associated with the at least one new resource comprises cost factor information for each of the at least one resource.

31. The computer program product of claim 21, wherein the metadata associated with the at least one new resource comprises instance information that includes capabilities supported by each of the at least one new resource.

32. The computer program product of claim 21, wherein the relationship between the at least one new resource and the at least one preexisting resource is represented by a look up table.

33. A system comprising:

at least one processor; and

a memory storing a program, which, when executed on the at least one processor, performs an operation comprising;

identifying at least one new resource to add to a cloud, the cloud comprising at least one preexisting resource;

creating an ontology extension for the at least one new resource including metadata associated with the at least one new resource;

creating a relationship between the at least one new resource and the at least one preexisting resource, and storing information regarding the relationship among the metadata included in the ontology extension; and

storing the ontology extension.

34. The system of claim 33, wherein the operation further comprises propagating information with respect to the at least one new resource to the at least one preexisting resource.

35. The system of claim 33, wherein the metadata associated with the at least one new resource is stored in a repository along with metadata associated with the at least one preexisting resource.

36. The system of claim 35, wherein the repository stores the metadata associated with the at least one new resource in one of a structured format, an unstructured format, or a combination of structured and unstructured formats.

37. The system of claim 33, wherein the metadata associated with the at least one new resource comprises cost factor information for each of the at least one resource.

38. The system of claim 33, wherein the metadata associated with the at least one new resource comprises instance information that includes capabilities supported by each of the at least one new resource.