Propagation of unique device names in a cluster system

• US 9,069,571 B2
• Filed: 12/01/2010
• Issued: 06/30/2015
• Est. Priority Date: 12/01/2010
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Fried, Eric P., Mishra, Rajeev, Russell, Lance W., Schwendiman, Chris A., Tee, Stephen M., Tovcimak, Stephen J.
• Primary Examiner(s): Trujillo, James
• Assistant Examiner(s): MINA, FATIMA P
• Application Number:
  US12/957,980
• Publication Number:
  US 20120143892A1
• Time in Patent Office: 1,672 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/152 using file content signatures, e.g. hash values
• CPC Class Codes: G06F 16/1824 implemented using Network-attached Storage [NAS] architecture distributed or networked storage systems G06F3/067; protocols for distributed storage of data in a network H04L67/1097
• CPC Class Codes: G06F 9/4411 Configuring for operating with peripheral devices; Loading of device drivers

Abstract

A unique device name is assigned to each of a plurality of shared storage devices in a cluster configuration database defining membership of nodes in a cluster. A particular node among the nodes defined by the cluster configuration database as a member of the cluster searches the cluster configuration database for a device identifier matching a device identifier of a shared storage device hosted by the particular node. In response to finding a matching device identifier in the cluster configuration database, the particular node renames, in a local configuration maintained at the particular node, a storage device associated with the matching device identifier with the unique name assigned to that storage device in the cluster configuration database.

Claims

1. A method of data processing in a cluster system, the method comprising:

in a cluster configuration database residing on a trusted shared data storage device of a host node of a cluster, defining multiple nodes as members of the cluster;

with reference to the cluster configuration database, centrally assigning a respective one of a plurality of unique device names to each of a plurality of shared storage devices in the cluster without querying the plurality of shared storage devices for device names, wherein the assigning includes;

generating a portion of each of the plurality of unique device names of the plurality of shared storage devices utilizing a monotonically advancing counter maintained on the trusted shared storage device;

forming each of the plurality of unique device names by concatenating a value of the monotonically advancing counter with a reserved constant maintained on the trusted shared storage device;

a particular node among the nodes defined as members of the cluster by the cluster configuration database searching the cluster configuration database on the trusted shared storage device for a device identifier matching a device identifier of a shared storage device hosted by the particular node, wherein the particular node is a different node than the host node;

in response to finding a matching device identifier in the cluster configuration database, the particular node renaming, in a local configuration maintained at the particular node, a storage device associated with the matching device identifier with a unique device name assigned to that storage device in the cluster configuration database; and

in response to a stimulus indicating configuration of an added node into the cluster;

the added node determining whether or not the added node has a universally unique identifier (UUID) and, if not, the added node internally generating its own persistent self-assigned UUID;

the added node searching the cluster configuration database for a temporary identifier associated with the added node; and

in response to the added node locating the temporary identifier of the added node in the cluster configuration database, the added node writing its self-assigned UUID into the cluster configuration database and joining the cluster.

4. The method of claim 1, wherein the temporary identifier comprises an Internet Protocol (IP) address assigned to the added node.

2. A program product, comprising:

a computer readable storage device; and

program code stored within the computer readable storage device that, when executed by a computer, causes the computer to perform;

defining, in a cluster configuration database residing on a trusted shared data storage device of a host node of a cluster, multiple nodes as members of the cluster;

with reference to the cluster configuration database, centrally assigning a respective one of a plurality of unique device names to each of a plurality of shared storage devices in the cluster without querying the plurality of shared storage devices for device names, wherein the assigning includes;

generating a portion of each of the plurality of unique device names of the plurality of shared storage devices utilizing a monotonically advancing counter maintained on the trusted shared storage device;

forming each of the plurality of unique device names by concatenating a value of the monotonically advancing counter with a reserved constant maintained on the trusted shared storage device;

a particular node among the nodes defined as members of the cluster by the cluster configuration database searching the cluster configuration database on the trusted shared storage device for a device identifier matching a device identifier of a shared storage device hosted by the particular node, wherein the particular node is a different node than the host node; and

in response to finding a matching device identifier in the cluster configuration database, the particular node renaming in a local configuration maintained at the particular node a storage device associated with the matching device identifier with a unique device name assigned to that storage device in the cluster configuration database; and

in response to a stimulus indicating configuration of an added node into the cluster;

the added node determining whether or not the added node has a universally unique identifier (UUID) and, if not, the added node internally generating its own persistent self-assigned UUID;

the added node searching the cluster configuration database for a temporary identifier associated with the added node; and

in response to the added node locating the temporary identifier of the added node in the cluster configuration database, the added node writing its self-assigned UUID into the cluster configuration database and joining the cluster.

5. The program product of claim 2, wherein the temporary identifier comprises an Internet Protocol (IP) address assigned to the added node.

3. A cluster data processing system, comprising:

multiple nodes including processing resources and data storage, wherein the multiple nodes include at least a host node and a different local node, the local node including;

a processor;

local data storage coupled to the processor, the local data storage including a shared storage device, wherein the local data storage further stores a local configuration of the local node; and

program code stored within the data storage that, when executed by the data processing system, causes at least one of the multiple nodes to perform;

defining, in a cluster configuration database residing on a trusted shared data storage device of a host node of a cluster, the multiple nodes as members of the cluster;

with reference to the cluster configuration database, centrally assigning a respective one of a plurality of unique device names to each of a plurality of shared storage devices in the cluster without querying the plurality of shared storage devices for device names, wherein the assigning includes;

generating a portion of each of the plurality of unique device names of the plurality of shared storage devices utilizing a monotonically advancing counter maintained on the trusted shared storage device;

forming each of the plurality of unique device names by concatenating a value of the monotonically advancing counter with a reserved constant maintained on the trusted shared storage device;

wherein the program code further causes the local node to perform;

searching the cluster configuration database on the trusted shared storage device for a device identifier matching a device identifier of the shared storage device hosted by the local node; and

in response to finding a matching device identifier in the cluster configuration database, the local node renaming, in the local configuration maintained in the local data storage, a storage device associated with the matching device identifier with a unique device name assigned to that storage device in the cluster configuration database; and

wherein the program code further causes an added node to perform;

in response to a stimulus indicating configuration of the added node into the cluster;

the added node determining whether or not the added node has a universally unique identifier (UUID) and, if not, the added node internally generating its own persistent self-assigned UUID;

the added node searching the cluster configuration database for a temporary identifier associated with the added node; and

in response to the added node locating the temporary identifier of the added node in the cluster configuration database, the added node writing its self-assigned UUID into the cluster configuration database and joining the cluster.

6. The cluster data processing system of claim 3, wherein the temporary identifier comprises an Internet Protocol (IP) address assigned to the added node.