System and method for managing distributed cluster identity
Methods and systems for managing distributed group identity may involve exchanging, at a node in a group, node identifiers with another node in the group, sorting the node identifiers, selecting an identifier from the sorted identifier, proposing the selected identifier as a persistent group name, setting the persistent group name based on the proposed identifier, setting a user administered name based on the proposed identifier, determining that the user administered name is consistent across the group, and updating the user administered name to resolve the inconsistency. The persistent group name is common across the group.
1. A method for managing distributed group identity, comprising:
exchanging, at a node in a group, node identifiers with another node in the group;
sorting the node identifiers;
selecting an identifier from the sorted node identifiers;
proposing the selected identifier as a persistent group name to the other node in the group;
setting the persistent group name based on the proposed identifier, wherein the persistent group name is common across the group;
setting a user administered name based on the proposed identifier;
updating the user administered name to a second user administered name during a cluster identity change configuration, wherein the persistent group name is maintained during the cluster identity change configuration;
determining that the second user administered name is inconsistent across the group based on a node in the group maintaining the user administered name after the cluster identity change configuration; and
updating the second user administered name to resolve the inconsistency.
2. The method of claim 1 , wherein the second user administered name is updated to a unified user administered name identified by a master of the group based on a node in the group with a most recent timestamp.
3. The method of claim 1 , further comprising:
determining that the persistent group name is inconsistent across the group; and
resolving the inconsistent persistent group name by setting the persistent group name to a unified persistent group name.
4. The method of claim 1 , wherein the node in the group maintains the user administered name after the cluster identity change configuration due to data corruption at the node.
5. The method of claim 2 , wherein the most recent timestamp represents when the node joined the group, the timestamp including at least one of a Lamport timestamp and a Unix-based timestamp.
6. The method of claim 3 , wherein the node is a master of the group and further comprising:
distributing the persistent group name from the master to the other node in the group; and
distributing the unified persistent group name to resolve the inconsistent persistent group name.
7. An information handling system, comprising:
a processor subsystem having access to a first memory;
a management controller comprising a secondary processor having access to a second memory, the second memory including an embedded storage partition and the second memory storing instructions executable by the secondary processor to:
exchange, at a node in a group, node identifiers with another node in the group;
sort the node identifiers;
select an identifier from the sorted node identifiers;
propose the selected identifier as a persistent group name to the other node in the group;
set the persistent group name based on the proposed identifier, wherein the persistent group name is common across the group;
set a user administered name based on the proposed identifier;
update the user administered name to a second user administered name during a cluster identity change configuration, wherein the persistent group name is maintained during the cluster identity change configuration;
determine that the second user administered name is inconsistent across the group based on a node in the group maintaining the user administered name after the cluster identity change configuration; and
update the second user administered name to resolve the inconsistency.
8. The information handling system of claim 7 , wherein the second user administered name is updated to a unified user administered name identified by a master of the group based on a node in the group with a most recent timestamp.
9. The information handling system of claim 7 , further comprising instructions executable by the secondary processor to:
determine that the persistent group name is inconsistent across the group; and
resolve the inconsistent persistent group name by setting the persistent group name to a unified persistent group name.
10. The information handling system of claim 7 , wherein the node in the group maintains the user administered name after the cluster identity change configuration due to data corruption at the node.
11. The information handling system of claim 8 , wherein the most recent timestamp represents when the node joined the group, the timestamp including at least one of a Lamport timestamp and a Unix-based timestamp.
12. The information handling system of claim 9 , wherein the node is a master of the group and further comprising instructions to:
distribute the persistent group name from the master to the other node in the group; and
distribute the unified persistent group name to resolve the inconsistent persistent group name.
13. The information handling system of claim 9 , wherein the instructions to determine that the persistent group name is inconsistent across the group is based on the group being moved within a network.
14. A management controller for an information handling system having a primary processor and a primary memory, the management controller comprising:
a secondary processor having access to a second memory, the second memory including an embedded storage partition and the second memory storing instructions executable by the secondary processor to:
exchange, at a node in a group, node identifiers with another node in the group;
sort the node identifiers;
select an identifier from the sorted node identifiers;
propose the selected identifier as a persistent group name;
set the persistent group name based on the proposed identifier, wherein the persistent group name is common across the group;
set a user administered name based on the proposed identifier;
update the user administered name to a second user administered name during a cluster identity change configuration, wherein the persistent group name is maintained during the cluster identity change configuration;
determine that the second user administered name is inconsistent across the group based on a node in the group maintaining the user administered name after the cluster identity change configuration; and
update the second user administered name to resolve the inconsistency.
15. The management controller of claim 14 , wherein the second user administered name is updated to a unified user administered name identified by a master of the group based on a node in the group with a most recent timestamp.
16. The management controller of claim 14 , further comprising instructions executable by the secondary processor to:
determine that the persistent group name is inconsistent across the group; and
resolve the inconsistent persistent group name by setting the persistent group name to a unified persistent group name.
17. The management controller of claim 14 , wherein the node in the group maintains the user administered name after the cluster identity change configuration data corruption at the node.
18. The management controller of claim 15 , wherein the most recent timestamp represents when the node joined the group, the timestamp including at least one of a Lamport timestamp and a Unix-based timestamp.
19. The management controller of claim 16 , wherein the node is a master of the group and further comprising instructions to:
distribute the persistent group name from the master to the other node in the group; and
distribute the unified persistent group name to resolve the inconsistent persistent group name.
20. The management controller of claim 16 , wherein the instructions to determine that the persistent group name is inconsistent across the group is based on the group being moved within a network.