Management of network devices within a dispersed data storage network

• US 8,819,781 B2
• Filed: 04/20/2009
• Issued: 08/26/2014
• Est. Priority Date: 04/20/2009
• Status: Active Grant

• Current Assignee: Pure Storage, Inc.
• Original Assignee: Cleversafe Incorporated (International Business Machines Corporation)
• Inventors: Kumar, Sanjaya, Hoffman, Steve, Cilfone, Bart
• Primary Examiner(s): SIMITOSKI, MICHAEL J
• Application Number:
  US12/426,807
• Publication Number:
  US 20100266131A1
• Time in Patent Office: 1,954 Days
• Field of Search: 713/155, 713/191, 726/4, 726/29, 380/285
• US Class Current: 726/4
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: H04L 41/14 Network analysis or design
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/104 Grouping of entities
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1042 using topology management mechanisms
• CPC Class Codes: H04L 67/1061 using node-based peer discovery mechanisms static access to replicated servers H04L67/1006; service discovery H04L67/51
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 9/321 involving a third party or a trusted authority
• CPC Class Codes: H04L 9/3271 using challenge-response

Abstract

A method of managing devices in a dispersed data storage network is disclosed. A device list is maintained including entries for every device in the dispersed data storage network. Each entry lists a public key, a network address, and hardware identifier for the corresponding device. On startup each device sends a request to join the network. The request includes the device'"'"'s public key, network address, and hardware identifier. The request is compared with the device list, and, based on the comparison, and, in some cases, administrator action, the request is granted or denied.

Claims

1. A method of managing devices in a dispersed data storage network, the method comprises:

receiving a device approval request from a slice server;

determining whether the device approval request is to add the slice server to a dispersed data storage network (DDSN) or is to update the slice server in a device list based on replacement of a failed hard drive;

when the device approval request is to add the slice server to the DDSN;

initiating an approval process regarding the slice server;

when the slice server is approved, updating the device list to include the slice server, wherein the slice server is one of a set of slice servers that stores data slices of an encoded data segment, wherein “

m”

of “

n”

of the stored data slices are needed to reconstruct a data segment; and

when the device approval request to update the slice server in the device list based on replacement of a failed hard drive, updating the device list.

2. The method of claim 1, wherein the device approval request comprises:

a public key, a network address, and a hardware identifier.

3. The method of claim 1, wherein the determining whether the device approval request is to add the slice server comprises:

determining that there are no matches of a network address of the device approval request in the device list.

4. The method of claim 1, wherein the determining whether the device approval request is to add the slice server comprises:

determining that there are no matches of a hardware identifier of the device approval request in the device list.

5. The method of claim 1 further comprises:

determining that the device approval request is to update the slice server in the device list based on update of hardware characteristics of the slice server, wherein the hardware characteristics includes one or more of number of hard drives, amount of total storage, and amount of memory.

6. A managing device of a data dispersed storage network comprises:

a network port operable to receive a device approval request via a network from a slice server;

memory for storing a device list; and

a processor operable to;

determine whether the device approval request is to add the slice server to a dispersed data storage network (DDSN) or is to update the slice server in a device list based on replacement of a failed hard drive;

when the device approval request is to add the slice server to the DDSN;

initiate an approval process regarding the slice server;

when the slice server is approved, update the device list to include the slice server, wherein the slice server is one of a set of slice servers that stores data slices of an encoded data segment, wherein “

m”

of “

n”

of the stored data slices are needed to reconstruct a data segment; and

when the device approval request to update the slice server in the device list based on replacement of a failed hard drive, update the device list.

7. The managing device of claim 6, wherein the device approval request comprises:

a public key, a network address, and a hardware identifier.

8. The managing device of claim 6, wherein the processor is further operable to determine whether device approval request is to add the slice server by:

determining that there are no matches of a network address of the device approval request in the device list.

9. The managing device of claim 6, wherein the processor is further operable to determine whether the device approval request is to add the slice server by:

determining that there are no matches of a hardware identifier of the device approval request in the device list.

10. The managing device of claim 6, wherein the processor is further operable to:

determine that the device approval request is to update the slice server in the device list based on update of hardware characteristics of the slice server, wherein the hardware characteristics includes one or more of number of hard drives, amount of total storage, and amount of memory.

11. A storage device comprises:

a first section for storing a software routine that, when executing by a computer, causes the computer to determine whether the device approval request is to add the slice server to a dispersed data storage network (DDSN);

a second section for storing a software routine that, when executing by the computer, causes the computer to, when the device approval request is to add the slice server to the DDSN, initiate an approval process regarding the slice server;

a third section for storing a software routine that, when executing by the computer, causes the computer to, when the slice server is approved, update the device list to include the slice server, wherein the slice server is one of a set of slice servers that stores data slices of an encoded data segment, wherein “

m”

of “

n”

of the stored data slices are needed to reconstruct a data segment; and

a fourth section for storing a software routine that, when executing by the computer, causes the computer to determine that the device approval request is to update the slice server in the device list based on update of hardware characteristics of the slice server, wherein the hardware characteristics includes one or more of number of hard drives, amount of total storage, and amount of memory.

12. The storage device of claim 11, wherein the device approval request comprises:

a public key, a network address, and a hardware identifier.

13. The storage device of claim 11, wherein the first section further causes the processor to determine that the device approval request is to add the slice server by:

determining that there are no matches of a network address of the device approval request in the device list.

14. The storage device of claim 11, wherein the first section further causes the processor to determine whether the device approval request is to add the slice server by:

determining that there are no matches of a hardware identifier of the device approval request in the device list.