A pattern based configuration method for minimizing the impact of component failures

Patent metadata

Field	Value
Publication number	US-2016335161-A1
Application number	US-201415112973-A
Country	US
Kind code	A1
Filing date	Jan 23, 2014
Priority date	Jan 23, 2014
Publication date	Nov 17, 2016
Grant date	—

Abstract

A configuration is generated for a software that is to be deployed for providing high service availability to satisfy configuration requirements. One or more configuration patterns are identified, each of which specifies a set of attribute values and an actual recovery action for a failed component as a configuration option of the software. The unchangeable attribute values of the software are matched with the configuration patterns to obtain a matching configuration pattern, whose actual recovery action incurs a smallest component failure recovery impact zone. The matching configuration pattern is selected as at least a portion of the configuration of the software. Then the changeable attribute values of the software are set to the corresponding attribute values of the matching configuration pattern to satisfy the configuration requirements.

First claim

1 . A computer-implemented method for generating a configuration of a software to be deployed for providing high service availability to satisfy configuration requirements, the method comprising the steps of:
identifying, by a computer system, one or more configuration patterns, each of which specifies a set of attribute values and an actual recovery action for a failed component as a configuration option of the software; matching unchangeable attribute values of the software with the configuration patterns to obtain a matching configuration pattern whose actual recovery action incurs a smallest component failure recovery impact zone; selecting the matching configuration pattern as at least a portion of the configuration of the software; and setting changeable attribute values of the software to corresponding attribute values of the matching configuration pattern to satisfy the configuration requirements.

2 . The method of claim 1 , wherein the step of identifying further comprises the step of identifying the one or more configuration patterns that have a same redundancy model and a same recommended recovery action for the failed component as the software.

3 . The method of claim 1 , further comprising the steps of:
mapping the unchangeable attribute values and the changeable attribute values of Entity Types File (ETF) prototypes specified in the matching configuration pattern to corresponding attribute values of Availability Management Framework (AMF) types; and creating AMF entities based on the AMF types.

4 . The method of claim 1 , wherein the configuration patterns provide configuration options for ETF prototypes, AMF types and AMF entities.

5 . The method of claim 1 , further comprising the steps of:
creating a table having rows that are ranked in an increasing order of component failure recovery impact zones, wherein each row contains one of the configuration patterns and a corresponding actual recovery action; and searching for the matching configuration pattern from top toward bottom of the rows until the matching configuration pattern is found.

6 . The method of claim 1 , further comprising the step of:
eliminating the configuration patterns having component failure recovery impact zones greater than requested by the configuration requirements.

7 . The method of claim 1 , wherein each configuration pattern specifies the set of attribute values for one or more levels of a type stack hierarchy.

8 . The method of claim 7 , wherein the type stack hierarchy includes one or more of a component level, a service unit level, a service group level and an application level.

9 . The method of claim 1 , further comprising the step of:
analyzing component prototypes based on the recommended recovery action and one or more attributes to determine the actual recovery action.

10 . The method of claim 1 , wherein the software has at least an attribute, which, when assigned an unchangeable attribute value, cannot change its assigned value, and wherein assigning the unchangeable attribute value to the attribute results in a larger component failure recovery impact zone than assigning a changeable attribute value to the attribute.

11 . A system adapted to generate a configuration of a software to be deployed for providing high service availability to satisfy configuration requirements, the system comprising:
a memory to store a data structure which further stores a set of configuration patterns; and one or more processors coupled to the memory, the one or more processors adapted to:
identify one or more of the configuration patterns, each of which specifies a set of attribute values and an actual recovery action for a failed component as a configuration option of the software;
match unchangeable attribute values of the software with the configuration patterns to obtain a matching configuration pattern whose actual recovery action incurs a smallest component failure recovery impact zone;
select the matching configuration pattern as at least a portion of the configuration of the software; and
set changeable attribute values of the software to corresponding attribute values of the matching configuration pattern to satisfy the configuration requirements.

12 . The system of claim 11 , wherein the identified one or more configuration patterns have a same redundancy model and a same recommended recovery action for the failed component as the software.

13 . The system of claim 11 , wherein the one or more processors are further adapted to:
map the unchangeable attribute values and the changeable attribute values of Entity Types File (ETF) prototypes specified in the matching configuration pattern to corresponding attribute values of Availability Management Framework (AMF) types; and create AMF entities based on the AMF types.

14 . The system of claim 11 , wherein the configuration patterns provide configuration options for ETF prototypes, AMF types and AMF entities.

15 . The system of claim 11 , wherein the one or more processors are further adapted to:
create a table having rows that are ranked in an increasing order of component failure recovery impact zones, wherein each row contains one of the configuration patterns and a corresponding actual recovery action; and search for the matching configuration pattern from top toward bottom of the rows until the matching configuration pattern is found.

16 . The system of claim 11 , wherein the one or more processors are further adapted to eliminate the configuration patterns having component failure recovery impact zones greater than requested by the configuration requirements.

17 . The system of claim 11 , wherein each configuration pattern specifies the set of attribute values for one or more levels of a type stack hierarchy.

18 . The system of claim 17 , wherein the type stack hierarchy includes one or more of a component level, a service unit level, a service group level and an application level.

19 . The system of claim 11 , wherein the one or more processors are further adapted to analyze component prototypes based on the recommended recovery action and one or more attributes to determine the actual recovery action.

20 . The system of claim 11 , wherein the software has at least an attribute, which, when assigned an unchangeable attribute value, cannot change its assigned value, and wherein assigning the unchangeable attribute value to the attribute results in a larger component failure recovery impact zone than assigning a changeable attribute value to the attribute.

21 . (canceled)

Assignees

• Toeroe Maria
• Pourali Parsa
• ERICSSON TELEFON AB L M (publ)

Inventors

• Toeroe Maria
• Pourali Parsa

Classifications

• G06F8/60

  Software deployment · CPC title

• G06F2201/805

  Real-time · CPC title

• G06F11/3051

  Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs (verification or detection of system hardware configuration G06F11/2247) · CPC title

• G06F11/143

  with loss of software functionality · CPC title

• G06F2201/85

  Active fault masking without idle spares · CPC title