Dynamic provisioning of service components in a distributed system

• US 20060010234A1
• Filed: 08/30/2005
• Published: 01/12/2006
• Est. Priority Date: 09/07/2001
• Status: Active Grant

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Clarke, James B., Reedy, Dennis G.
• Granted Patent: US 8,103,760 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06F 2209/462 Lookup
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Systems and methods simplify the provision of complex services over a distributed network by breaking a complex service into a collection of simpler services. Systems and methods provide the tools to deconstruct a complex, provision service elements that are needed to make up the complex service, and monitor the service elements to ensure that the complex service is supported. Quality of service is provided by matching service requirements to compute resource capabilities.

Claims

1-32. -32. (canceled)

33. A method for providing a service in a distributed system, comprising:

receiving a list of service elements, wherein at least several of the service elements constitute the service; and

for each service element in the list,

determining whether an application corresponding to the service element is available in the distributed system, and

monitoring the application to detect whether the application fails.

34. The method of claim 33, further comprising

creating the application corresponding to the service element, if the application corresponding to the service element is not available in the distributed system

35. The method of claim 33, further comprising

recreating the application, if it is detected that the application fails.

36. The method of claim 33, wherein the creating further comprises:

determining requirements of the service element;

matching the requirements of the service element to a resource on the distributed system; and

sending the requirements of the service to the resource to initiate creation of the application.

37. A method in a distributed system for providing a service consisting of a collection of service elements, comprising:

determining whether an instance of each service element in the collection is available in the distributed system; and

for each service element in the collection that does not have an instance available in the distributed system, creating a new service element instance.

38. The method of claim 37, further comprising:

monitoring a running service element instance corresponding to each service element in the collection to determine if the running service element instance fails; and

creating a new service element instance, if the running service element instance fails.

39. The method of claim 37, wherein the determining further comprises:

using a lookup service to determine whether an instance of each service element in the collection is running in the distributed system.

40. A method for providing services in a distributed system, comprising:

receiving capabilities of a compute resource from an executable application on the compute resource;

receiving a request to add a new service to the distributed system, including information reflecting requirements of the new service;

matching the requirements of the new service to the capabilities of the. compute resource; and

directing the executable application running on the compute resource to instantiate the new service.

41. The method of claim 40, wherein the request further includes attributes of the new service and the directing further comprises:

sending the attributes of the new service to the compute resource.

42. The method of claim 40, wherein the compute resource is a Java™

virtual machine.

43. A method for providing a service in a distributed system, comprising:

receiving a list of service elements, wherein at least several of the service elements constitute the service; and

for each service element in the list,

determining whether an application corresponding to the service element is available in the distributed system,

creating the application corresponding to the service element, if the application corresponding to the service element is not available in the distributed system, and

monitoring the application to detect whether the application fails.

44. The method of claim 43, wherein creating the application corresponding to the service element further comprises:

determining a compute resource that previously advertised a capability to provide the application by registering as an event consumer; and

sending an event notification to the compute resource to instruct the compute resource to create the application corresponding to the service element.

45. The method of claim 44, wherein a plurality of compute resources previously advertised a capability to provide the application by registering as event consumers, and wherein sending an event notification further comprises:

determining an order in which to notify each of the plurality of compute resources, and

sending an event notification to each of the plurality of compute resources in the determined order.

46. The method of claim 45, further comprising:

sending the event notification to each of the plurality of compute resources in a random order.

47. The method of claim 45, further comprising:

sending the event notification to each of the plurality of compute resources in a round robin order.

48. A system for providing a service in a distributed system, comprising:

a receiving component configured to receive a list of service elements, wherein at least several of the service elements constitute the service;

a service determining component configured to determine, for each service element in the list, whether an application corresponding to the service element is available in the distributed system, and

a monitoring component configured to monitor the application to detect whether the application fails.

49. The system of claim 48, further comprising

a creating component configured to create the application corresponding to the service element, if the application corresponding to the service element is not available in the distributed system

50. The system of claim 48, further comprising

a recreating component configured to recreate the application, if it is detected that the application fails.

51. The system of claim 48, wherein the creating further comprises:

a requirements determining component configured to determine requirements of the service element;

a matching component configured to match the requirements of the service element to a resource on the distributed system; and

a sending component configured to send the requirements of the service to the resource to initiate creation of the application.

52. A system in a distributed system for providing a service consisting of a collection of service elements, comprising:

a determining component configured to determine whether an instance of each service element in the collection is available in the distributed system; and

a creating component configured to create a new service element instance for each service element in the collection that does not have an instance available in the distributed system.

53. The system of claim 52, further comprising:

a monitoring component configured to monitor a running service element instance corresponding to each service element in the collection to determine if the running service element instance fails; and

a failure creating component configured to create a new service element instance, if the running service element instance fails.

54. The system of claim 52, wherein the determining component further comprises:

a using component configured to use a lookup service to determine whether an instance of each service element in the collection is running in the distributed system.

55. A system for providing services in a distributed system, comprising:

a capabilities receiving component configured to receive capabilities of a compute resource from an executable application on the compute resource;

a request receiving component configured to receive a request to add a new service to the distributed system, including information reflecting requirements of the new service;

a matching component configured to match the requirements of the new service to the capabilities of the compute resource; and

a directing component configured to direct the executable application running on the compute resource to instantiate the new service.

56. The system of claim 55, wherein the request further includes attributes of the new service and the directing component further comprises:

a sending component configured to send the attributes of the new service to the compute resource.

57. The system of claim 55, wherein the compute resource is a Java™

virtual machine.

58. A system for providing a service in a distributed system, comprising:

a receiving component configured to receive a list of service elements, wherein at least several of the service elements constitute the service;

a first determining component configured to determine, for each service element in the list, whether an application corresponding to the service element is available in the distributed system;

a creating component configured to create the application corresponding to the service element, if the application corresponding to the service element is not available in the distributed system; and

a monitoring component configured to monitor the application to detect whether the application fails.

59. The system of claim 58, wherein the creating component further comprises:

a second determining component configured to determine a compute resource that previously advertised a capability to provide the application by registering as an event consumer; and

a sending component configured to send an event notification to the compute resource to instruct the compute resource to create the application corresponding to the service element.

60. The system of claim 59, wherein a plurality of compute resources have previously advertised a capability to provide the application by registering as event consumers, and wherein the sending component further comprises:

a third determining component configured to determine an order in which to notify each of the plurality of compute resources; and

a notifying component configured to send an event notification to each of the plurality of compute resources in the determined order.

61. The system of claim 60, wherein the notifying component further comprises:

a random sending component configured to send the event notification to each of the plurality of compute resources in a random order.

62. The system of claim 60, wherein the notifying component further comprises:

a round robin sending component configured to send the event notification to each of the plurality of compute resources in a round robin order.