Preventing extreme coresidency hazards in cloud computing
AssigneeAlcatel Lucent
InventorsEric J. Bauer, Randee S. Adams, Daniel W. Eustace, Kedar S. Namjoshi, Lyle D. Kipp
Life of this patent
Estimating the term…
Abstract
Various exemplary embodiments relate to a method of preventing extreme coresidency hazards among application instances in a cloud network. The method includes determining a first failure group of a first instance of an application; establishing a connection with a second instance of a peer application; determining a second failure group of the second instance; comparing the first failure group to the second failure group; and establishing a second connection with a third instance of the peer application if the first failure group and the second failure group share a failure point.
Claims23
A method comprising:
- determining, by a processor communicatively connected to a memory, a first failure group of a first instance of an application;
- establishing a connection between the first instance and a second instance associated with a peer application;
- determining a second failure group of the second instance;
- comparing the first failure group to the second failure group;
- and
- establishing a second connection between the first instance and a third instance corresponding to the peer application if the first failure group and the second failure group share a failure point.
A tangible non-transitory machine-readable storage medium encoded with instructions that when executed by a processor, performs a method of preventing extreme single point of failure hazards of application instances within a cloud network, the tangible non-transitory machine-readable storage medium comprising:
- instructions for determining a first failure group of a first instance of an application;
- instructions for establishing a connection with a second instance corresponding to a peer application;
- instructions for determining a second failure group of the second instance;
- instructions for comparing the first failure group to the second failure group;
- and
- instructions for establishing a second connection with a third instance corresponding to the peer application if the first failure group and the second failure group share a failure point.
A cloud network comprising:
- a data center having a plurality of computing resources including a plurality of processors;
- a cloud manager configured to:
- manage a plurality of application instances by assigning computing resources including at least one processor to each application instance;
- provide a universally unique identifier to an application instance identifying the at least one processor assigned to the application instance;
- provide a listing of network addresses of a plurality of peer application instances providing a service,
- wherein at least one of the application instances is configured to:
- determine a first universally unique identifier of a processor assigned to the application instance and a second universally unique identifier of a processor assigned to a peer application instance;
- determine whether the first universally unique identifier and the second universally unique identifier are members of a failure group;
- and
- select another network address from the listing if the first universally unique identifier and the second universally unique identifier are members of a failure group.
An apparatus for reducing risks from a single point of failure in a cloud network, the apparatus comprising:
- a data storage;
- and
- a processor communicatively connected to the data storage, the processor being configured to:
- determine a first failure group of a first instance of an application;
- establish a connection with a second instance corresponding to a peer application;
- determine a second failure group of the second instance;
- compare the first failure group to the second failure group;
- and
- establish a second connection with a third instance corresponding to the peer application if the first failure group and the second failure group share a failure point.
Dependencies are inferred from the claim text.