Utilizing federation relationship settings among different systems

Patent metadata

Field	Value
Publication number	US-2023079199-A1
Application number	US-202117475085-A
Country	US
Kind code	A1
Filing date	Sep 14, 2021
Priority date	Sep 14, 2021
Publication date	Mar 16, 2023
Grant date	—

Abstract

A computer-implemented method, according to one embodiment, includes: determining, for each pair of HCI systems where each pair includes a first HCI system coupled to another HCI system, a federation relationship setting that corresponds to each pair. The federation relationship settings are used to control a flow of data, as well as to control a flow of workload scheduling, between the first HCI system and the other HCI systems in the respective pairs. Moreover, determining a federation relationship setting that corresponds to a pair includes: determining whether a risk score which corresponds to the pair is outside a predetermined range. In response to determining that the risk score is outside the predetermined range, a restrictive federation relationship setting is assigned to the pair, and in response to determining that the risk score is not outside the predetermined range, a permissive federation relationship setting is assigned to the pair.

First claim

What is claimed is:

1 . A computer-implemented method, comprising:
determining, for each pair of a plurality of pairs of hyperconverged infrastructure (HCI) systems where each pair includes a first HCI system coupled to another HCI system, a federation relationship setting that corresponds to each pair, wherein determining a federation relationship setting that corresponds to a pair includes:
determining whether a risk score which corresponds to the pair is outside a predetermined range,
in response to determining that the risk score is outside the predetermined range, assigning a restrictive federation relationship setting to the pair;
in response to determining that the risk score is not outside the predetermined range, assigning a permissive federation relationship setting to the pair;
using the federation relationship settings to control a flow of data between the first HCI system and the other HCI systems in the respective pairs; and using the federation relationship settings to control a flow of workload scheduling between the first HCI system and the other HCI systems in the respective pairs.

2 . The computer-implemented method of claim 1 , wherein determining a federation relationship setting that corresponds to a pair includes:
inspecting compliance policies associated with the first HCI system and the other HCI system in the pair; determining whether the first HCI system and/or the other HCI system is subject to one or more location based constraints; and in response to determining that the first HCI system and/or the other HCI system is subject to at least one location based constraint, assigning the restrictive federation relationship setting to the pair.

3 . The computer-implemented method of claim 2 , wherein determining a federation relationship setting that corresponds to a pair includes:
in response to determining that the first HCI system and the other HCI system in the pair are not subject to any location based constraints, assigning a permissive federation relationship setting to the pair.

4 . The computer-implemented method of claim 1 , wherein the permissive federation relationship setting is selected from the group consisting of: a full federation setting that does not restrict a flow of data or of workload scheduling between the first HCI system and the other HCI system in the pair, and a semi federation setting that restricts a flow of predetermined types of data and/or of predetermined types of workload scheduling between the first HCI system and the other HCI system in the pair.

5 . The computer-implemented method of claim 1 , wherein the restrictive federation relationship setting is selected from the group consisting of: a banned federation setting that restricts a flow of all data and of all workload scheduling between the first HCI system and the other HCI system in the pair, and an on-hold federation setting that delays a flow of all data and/or of all workload scheduling between the first HCI system and the other HCI system in the pair.

6 . The computer-implemented method of claim 1 , comprising:
monitoring information associated with a status of each respective pair; and using the information to dynamically update the federation relationship settings.

7 . The computer-implemented method of claim 6 , comprising:
using the federation relationship settings to create a HCI federation list at the first HCI system, wherein each entry in the HCI federation list corresponds to a unique one of the pairs, wherein using the information to dynamically update the federation relationship settings includes: updating the corresponding entries in the HCI federation list.

8 . The computer-implemented method of claim 7 , wherein each entry in the HCI federation list includes: the federation relationship setting that corresponds to the respective pair, and supplemental information associated with the respective pair.

9 . A computer program product comprising, a computer readable storage medium having program instructions embodied therewith, the program instructions are readable and/or executable by a processor to cause the processor to:
determine, by the processor for each pair of a plurality of pairs of hyperconverged infrastructure (HCI) systems where each pair includes a first HCI system coupled to another HCI system, a federation relationship setting that corresponds to each pair, wherein determining a federation relationship setting that corresponds to a pair includes:
determining whether a risk score which corresponds to the pair is outside a predetermined range,
in response to determining that the risk score is outside the predetermined range, assigning a restrictive federation relationship setting to the pair;
in response to determining that the risk score is not outside the predetermined range, assigning a permissive federation relationship setting to the pair;
use, by the processor, the federation relationship settings to control a flow of data between the first HCI system and the other HCI systems in the respective pairs; and use, by the processor, the federation relationship settings to control a flow of workload scheduling between the first HCI system and the other HCI systems in the respective pairs.

10 . The computer program product of claim 9 , wherein determining a federation relationship setting that corresponds to a pair includes:
inspecting compliance policies associated with the first HCI system and the other HCI system in the pair; determining whether the first HCI system and/or the other HCI system is subject to one or more location based constraints; and in response to determining that the first HCI system and/or the other HCI system is subject to at least one location based constraint, assigning the restrictive federation relationship setting to the pair.

11 . The computer program product of claim 10 , wherein determining a federation relationship setting that corresponds to a pair includes:
in response to determining that the first HCI system and the other HCI system in the pair are not subject to any location based constraints, assigning a permissive federation relationship setting to the pair.

12 . The computer program product of claim 9 , wherein the permissive federation relationship setting is selected from the group consisting of: a full federation setting that does not restrict a flow of data or of workload scheduling between the first HCI system and the other HCI system in the pair, and a semi federation setting that restricts a flow of predetermined types of data and/or of predetermined types of workload scheduling between the first HCI system and the other HCI system in the pair.

13 . The computer program product of claim 9 , wherein the restrictive federation relationship setting is selected from the group consisting of: a banned federation setting that restricts a flow of all data and of all workload scheduling between the first HCI system and the other HCI system in the pair, and an on-hold federation setting that delays a flow of all data and/or of all workload scheduling between the first HCI system and the other HCI system in the pair.

14 . The computer program product of claim 9 , wherein the program instructions are readable and/or executable by the processor to cause the processor to:
monitor, by the processor, information associated with a status of each respective pair; and use, by the processor, the information to dynamically update the federation relationship settings.

15 . The computer program product of claim 14 , wherein the program instructions are readable and/or executable by the processo

Assignees

• IBM

Inventors

• Patil Sandeep Ramesh
• Muppidi Sridhar
• Hsu Yu-Cheng
• Raut Smita J
• Mohammed Shajeer K
• Chaudhary Piyush

Classifications

• G06Q10/0635 Primary

  Risk analysis of enterprise or organisation activities · CPC title

• G06F9/505

  considering the load · CPC title

• G06F9/5072

  Grid computing · CPC title

• G06F21/577 Primary

  Assessing vulnerabilities and evaluating computer system security · CPC title