Distributed platform management for high availability systems

• US 7,716,517 B2
• Filed: 12/21/2006
• Issued: 05/11/2010
• Est. Priority Date: 12/21/2006
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Toeroe, Maria
• Primary Examiner(s): GUYTON, PHILIP A
• Application Number:
  US11/614,728
• Publication Number:
  US 20080155303A1
• Time in Patent Office: 1,237 Days
• Field of Search: 714/3, 714/47, 709223-226
• US Class Current: 714/3
• CPC Class Codes: G06F 11/1482 by means of middleware or OS functionality
• CPC Class Codes: G06F 2201/815 Virtual middleware or OS functionality using virtual machines to implement generic software techniques for error detection or fault masking G06F11/1484

Abstract

A distributed model for availability management (AM) functions is described. Core AM functionality is provided by at a global level, while supplemental AM functionality is provided at a local (e.g., cluster) level. Extension entities can be provided to supplement provided AM functions.

Claims

1. A system comprising:

a hardware platform for supporting a service;

an availability management (AM) software entity which supports availability of said service, said AM software entity being distributed to include;

a first global availability management core (AMC_g) portion, at a first hierarchical level, having a first set of AM functions associated therewith;

a first plurality of local AMC (AMC_l) portions, at a second hierarchical level, having a second set of AM functions associated therewith; and

a first plurality of AMC components, at a third hierarchical level, which are supplied with said first and second sets of AM functions to support availability of said service; and

a first AM extension portion having a third set of one or more AM functions associated therewith, said first AM extension portion being a plug-in software entity located at said first hierarchical level and said third set of AM functions being mutually exclusive of said first and second sets of AM functions.

2. The system of claim 1, wherein said first plurality of AMC components, provided at said third hierarchical level, are each managed by a respective one of said plurality of local AMC portions and provide redundancy for said first AM extension portion.

3. The system of claim 1, wherein said first set of AM functions includes at least one of:

(a) a function for monitoring a health of entities managed by said global AMC portion, (b) a function for notifying dependent entities of a status of entities upon which they are dependent, (c) a function for managing lifecycles of said entities, (d) a function for assigning service roles;

(e) a function for role assumption;

(f) a function for communicating with said first AM extension portion and (g) a function for restarting one or more of said global AMC portion and said first AM extension portion.

4. The system of claim 1, wherein said third set of functions includes:

at least one of;

(a) a function for enabling lifecycle control of said first AM extension portion by said system global AMC portion, (b) a function for communicating with said global AMC portion, (c) a function for operating in accordance with one of a plurality of service roles, and (d) a function for providing an application program interface (API) associated with said first AM extension portion'"'"'s function.

5. The system of claim 1, wherein said third set of AM functions associated with said first AM extension portion provides for a redundancy model which is not supported by said first set of AM functions.

6. The system of claim 1, wherein said first global availability management core (AMC_g) portion, said first plurality of local AMC (AMC_l) portions and said first plurality of AMC components are all associated with a first virtual cluster, said system further comprising a second virtual cluster having:

a second global availability management core (AMC_g) portion, at said first hierarchical level, having a fourth set of AM functions associated therewith;

a second plurality of local AMC (AMC_l) portions, at said second hierarchical level, having a fifth set of AM functions associated therewith; and

a second plurality of AMC components, provided at said third hierarchical level, which are supplied with said fourth and fifth sets of AM functions to support availability of said service.

7. The system of claim 6, further comprising:

a second AM extension portion having a sixth set of one or more AM functions associated therewith; and

wherein said second plurality of AMC components, provided at said third hierarchical level, are each managed by a respective one of said second plurality of local AMC components, to redundantly provide said second AM extension portion.

8. The system of claim 7, wherein said sixth set of AM functions associated with said second AM extension portion provides for a role arbitration function which is not supported by said fourth set of AM functions.

9. The system of claim 6, further comprising:

a system-level AMC_g disposed at a hierarchical level above said first hierarchical level for communicating with, and coordinating availability management between, said first and second virtual clusters.

10. A method comprising the steps of:

providing, by a hardware platform, a service;

distributing an availability management (AM) software entity which supports availability of said service, said AM software entity being distributed to include;

a first global availability management core (AMC_g) portion, at a first hierarchical level, having a first set of AM functions associated therewith;

a first plurality of local AMC (AMC_l) portions, at a second hierarchical level, having a second set of AM functions associated therewith; and

a first plurality of AMC components, at a third hierarchical level, which are supplied with said first and second sets of AM functions to support availability of said service; and

providing a first AM extension portion having a third set of one or more AM functions associated therewith, said first AM extension portion being a plug-in software entity located at said first hierarchical level and said third set of AM functions being mutually exclusive of said first and second sets of AM functions.

11. The method of claim 10, wherein said first plurality of AMC components, provided at said third hierarchical level, are each managed by a respective one of said plurality of local AMC portions and provide redundancy for said first AM extension portion.

12. The method of claim 10, wherein said first set of AM functions includes at least one of:

(a) a function for monitoring a health of entities managed by said global AMC portion, (b) a function for notifying dependent entities of a status of entities upon which they are dependent, (c) a function for managing lifecycles of said entities, (d) a function for assigning service roles;

(e) a function for role assumption;

(f) a function for communicating with said first AM extension portion, and (g) a function for restarting one or more of said global AMC portion and said first AM extension portion.

13. The method of claim 10, wherein said third set of functions includes:

at least one of;

(a) a function for enabling lifecycle control of said first AM extension portion by said system global AMC portion, (b) a function for communicating with said global AMC portion, (c) a function for operating in accordance with one of a plurality of service roles, and (d) a function for providing an application program interface (API) associated with said first AM extension portion'"'"'s function.

14. The method of claim 10, wherein said third set of AM functions associated with said first AM extension portion provides for a redundancy model which is not supported by said first set of AM functions.

15. The method of claim 10, wherein said first global availability management core (AMC_g) portion, said first plurality of local AMC (AMC_l) portions and said first plurality of AMC components are all associated with a first virtual cluster, said method further comprising the step of providing a second virtual cluster having:

a second global availability management core (AMC_g) portion, at said first hierarchical level, having a fourth set of AM functions associated therewith;

a second plurality of local AMC (AMC_l) portions, at said second hierarchical level, having a fifth set of AM functions associated therewith; and

a second plurality of AMC components, provided at said third hierarchical level, which are supplied with said fourth and fifth sets of AM functions to support availability of said service.

16. The method of claim 15, further comprising the step of:

providing a second AM extension portion having a sixth set of one or more AM functions associated therewith; and

wherein said second plurality of AMC components, provided at said third hierarchical level, are each managed by a respective one of said second plurality of local AMC portions, to redundantly provide said second AM extension portion.

17. The method of claim 16, wherein said sixth set of AM functions associated with said second AM extension portion provides for a role arbitration function which is not supported by said fourth set of AM functions.

18. The method of claim 15, further comprising the step of:

providing a system-level AMC_g disposed at a hierarchical level above said first hierarchical level for communicating with, and coordinating availability management between, said first and second virtual clusters.