SYSTEM AND METHOD FOR CLOUD CONNECTION POOL

• US 20150006726A1
• Filed: 12/13/2013
• Published: 01/01/2015
• Est. Priority Date: 06/28/2013
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Yuan, Hong, Jaiswal, Tarun
• Granted Patent: US 9,948,571 B2
• Time in Patent Office: Days
• US Class Current: 709/225
• CPC Class Codes: G06F 2209/5011 Pool
• CPC Class Codes: G06F 9/5072 Grid computing
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• 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

Abstract

Today'"'"'s cloud software, especially cloud management software, faces a complex, distributed, cross platform environment with extremely diversified software components. Cloud Connection Pool (CCP) is a technique to obtain a connection in such an environment and is more complex than a traditional connection pool. CCP allows requesting components to establish connections to target components. CCP uses cloud mapping data that associates cloud components with each other and stores pool data that identifies connection pools for components (or “managing components”) that manage target components. In response to a request for a connection from a requesting component, the CCP determines a managing component that is associated with the requested target component and identifies (or creates) a connection pool that is associated with the managing component. The CCP then retrieves a connection from the connection pool and returns the connection to the requesting component.

Claims

1. A method for providing connections to managed components in a cloud environment, the method comprising:

receiving, from a requesting component, a request for a connection to a target component;

in response to receiving the request, determining, from among a plurality of managing components that are different than the target component, a managing component that is associated with the target component;

identifying a connection pool for the managing component;

determining whether the connection pool includes a connection that is available;

in response to determining that a connection is available in the connection pool, providing the connection to the requesting component;

wherein the method is performed by one or more computing devices.

2. The method of claim 1, wherein the requesting component is a first requesting component, the method further comprising:

receiving, from a second requesting component that is different than the first requesting component, a second request for a connection to a second target component;

in response to receiving the second request, determining, from among the plurality of managing components, that the managing component is associated with the second requesting component;

determining whether the connection pool includes one or more connections that are available;

in response to determining that a second connection is available in the connection pool, providing the second connection to the second requesting component.

3. The method of claim 1, wherein the requesting component is a first requesting component, the managing component is a first managing component, and the target component is a first target component, the method further comprising:

receiving, from a second requesting component that is different than the first requesting component, a second request for a connection to a second target component that is different than the first target component, wherein the first target component belongs to a domain that is different than the domain to which the second target component belongs;

in response to receiving the second request, determining, from among the plurality of managing components, a second managing component that is associated with the second requesting component and that is different than the first managing component;

determining that a second connection pool exists for the second managing component;

in response to determining that the second connection pool exists for the second managing component, determining whether the second connection pool includes one or more connections that are available;

in response to determining that a second connection is available in the second connection pool, providing the second connection to the second requesting component.

4. The method of claim 3, wherein the first target component belongs to a first software platform and the second target component belongs to a second software platform that is different than the first software platform.

5. The method of claim 1, wherein:

the request includes an identifier that identifies the target component;

the method further comprising determining the target component based on the identifier.

6. The method of claim 1, wherein:

the request does not include an identifier that identifies the target component;

the method further comprising;

determining a particular identifier for the target component based on an execution context of the request;

determining the target component based on the particular identifier.

7. The method of claim 1, wherein:

determining the managing component comprises identifying, based on cloud mapping data and an identifier of the target component, a particular domain, from among a plurality of domains, to which the target component belongs;

the cloud mapping data associates domains with target components.

8. The method of claim 1, further comprising:

prior to identifying the connection pool for the managing component, determining whether a connection pool exists for the managing component;

in response to determining that no connection pool exists for the managing component, creating the connection pool;

creating one or more connections for the connection pool and adding the one or more connections to the connection pool.

9. The method of claim 8, further comprising:

determining a particular software platform associated with the managing component;

wherein creating the one or more connections is based on the particular software platform.

10. The method of claim 1, further comprising, prior to identifying the connection pool for the managing component:

storing pool data that identifies;

for each managing component of the plurality of managing components, a connection pool that is associated with said each managing component;

for each connection pool of a plurality of connection pools, data about one or more connections that belong to said each connection pool;

determining, based on the pool data, whether a connection pool exists for the managing component.

11. One or more non-transitory computer-readable media carrying instructions which, when executed by one or more processors, cause:

receiving, from a requesting component, a request for a connection to a target component;

in response to receiving the request, determining, from among a plurality of managing components that are different than the target component, a managing component that is associated with the target component;

identifying a connection pool for the managing component;

determining whether the connection pool includes a connection that is available;

in response to determining that a connection is available in the connection pool, providing the connection to the requesting component.

12. The one or more non-transitory computer-readable media of claim 11, wherein the requesting component is a first requesting component, wherein the instructions, when executed by the one or more processors, further cause:

receiving, from a second requesting component that is different than the first requesting component, a second request for a connection to a second target component;

in response to receiving the second request, determining, from among the plurality of managing components, that the managing component is associated with the second requesting component;

determining whether the connection pool includes one or more connections that are available;

in response to determining that a second connection is available in the connection pool, providing the second connection to the second requesting component.

13. The one or more non-transitory computer-readable media of claim 11, wherein the requesting component is a first requesting component, the managing component is a first managing component, and the target component is a first target component, wherein the instructions, when executed by the one or more processors, further cause:

receiving, from a second requesting component that is different than the first requesting component, a second request for a connection to a second target component that is different than the first target component, wherein the first target component belongs to a domain that is different than the domain to which the second target component belongs;

in response to receiving the second request, determining, from among the plurality of managing components, a second managing component that is associated with the second requesting component and that is different than the first managing component;

determining that a second connection pool exists for the second managing component;

in response to determining that the second connection pool exists for the second managing component, determining whether the second connection pool includes one or more connections that are available;

in response to determining that a second connection is available in the second connection pool, providing the second connection to the second requesting component.

14. The one or more non-transitory computer-readable media of claim 13, wherein the first target component belongs to a first software platform and the second target component belongs to a second software platform that is different than the first software platform.

15. The one or more non-transitory computer-readable media of claim 11, wherein:

the request includes an identifier that identifies the target component;

the instructions, when executed by the one or more processors, further cause determining the target component based on the identifier.

16. The one or more non-transitory computer-readable media of claim 11, wherein:

the request does not include an identifier that identifies the target component;

the instructions, when executed by the one or more processors, further cause;

determining a particular identifier for the target component based on an execution context of the request;

determining the target component based on the particular identifier.

17. The one or more non-transitory computer-readable media of claim 11, wherein:

determining the managing component comprises identifying, based on cloud mapping data and an identifier of the target component, a particular domain, from among a plurality of domains, to which the target component belongs;

the cloud mapping data associates domains with target components.

18. The one or more non-transitory computer-readable media of claim 11, wherein the instructions, when executed by the one or more processors, further cause:

prior to identifying the connection pool for the managing component, determining whether a connection pool exists for the managing component;

in response to determining that no connection pool exists for the managing component, creating the connection pool;

creating one or more connections for the connection pool and adding the one or more connections to the connection pool.

19. The one or more non-transitory computer-readable media of claim 18, wherein the instructions, when executed by the one or more processors, further cause:

determining a particular software platform associated with the managing component;

wherein creating the one or more connections is based on the particular software platform.

20. The one or more non-transitory computer-readable media of claim 11, wherein the instructions, when executed by the one or more processors, further cause, prior to identifying the connection pool for the managing component:

storing pool data that identifies;

for each managing component of the plurality of managing components, a connection pool that is associated with said each managing component;

for each connection pool of a plurality of connection pools, data about one or more connections that belong to said each connection pool;

determining, based on the pool data, whether a connection pool exists for the managing component.

21. One or more non-transitory computer-readable media carrying instructions which, when executed by one or more processors, cause:

receiving, from a first requesting component, a first request for a connection to a first target component;

in response to receiving the first request, determining whether a first connection pool for the first target component includes a connection that is available;

in response to determining that a first connection is available in the first connection pool, providing the first connection to the first requesting component;

receiving, from a second requesting component, a second request for a connection to a second target component that is different than the first target component;

in response to receiving the second request, determining whether a second connection pool for the second target component includes a connection that is available, wherein the second connection pool is different than the first connection pool;

in response to determining that a second connection is available in the second connection pool, providing the second connection to the second requesting component.

22. The one or more non-transitory computer-readable media of claim 21, wherein the instructions, when executed by the one or more processors, further cause:

in response to receiving the first request, determining, based on pool data that maps connection pools to target components, whether a connection pool exists for the first target component;

wherein determining whether the first connection pool includes a connection that is available comprises determining whether the first connection pool includes a connection that is available in response to determining that a connection pool exists for the first target component;

in response to receiving the second request, determining, based on the pool data, whether a connection pool exists for the second target component;

wherein determining whether the second connection pool includes a connection that is available comprises determining whether the second connection pool includes a connection that is available in response to determining that a connection pool exists for the second target component.