US20170286088A1

US20170286088A1 - Configuration of automated update routines

Info

Publication number: US20170286088A1
Application number: US15/467,444
Authority: US
Inventors: Alexander Litvinsky
Original assignee: International Business Machines Corp
Current assignee: Workday Inc
Priority date: 2016-03-29
Filing date: 2017-03-23
Publication date: 2017-10-05
Also published as: US20190065119A1; US20190171394A1; US20170286154A1; US20170286226A1; US20170286015A1; US10416906B2; US10146458B2; US10216436B2; US11385803B2; US10140061B2; US20170289250A1; US10678451B2; US20190146690A1; US10241697B2; US11182082B2; US20200257458A1; US10831381B2; US20190065120A1; US10001950B2; US20170289173A1

Abstract

A method for executing a software update within a dispersed storage network (DSN) includes determining, by a management unit of the DSN, a type of the software update. The method further includes generating, based on the type of the software update, a software update plan for updating a set of storage unit groups of the DSN, where a first storage unit group of the set of storage unit groups includes one or more storage units and stores first encoded data slices of pluralities of sets of encoded data slices, and where the software update plan aggressively takes storage units of the set of storage unit groups offline for executing the software update when the type of the software update requires urgency while maintaining a sufficient number of storage units online to fulfill DSN access requests. The method further includes executing, by the management unit, the software update plan to update the set of groups of storage units with the software update.

Description

CROSS REFERENCE TO RELATED PATENTS

The present U.S. Utility patent application claims priority pursuant to 35 U.S.C. §119(e) to U.S. Provisional Application No. 62/314,792, entitled “SELECTING A PROCESSING UNIT IN A DISPERSED STORAGE NETWORK,” filed Mar. 29, 2016, which is incorporated herein by reference in its entirety and made part of the present U.S. Utility patent application for all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC

Not applicable.

BACKGROUND OF THE INVENTION

Technical Field of the Invention

This invention relates generally to computer networks and more particularly to dispersing error encoded data.

Description of Related Art

Computing devices are known to communicate data, process data, and/or store data. Such computing devices range from wireless smart phones, laptops, tablets, personal computers (PC), work stations, and video game devices, to data centers that support millions of web searches, stock trades, or on-line purchases every day. In general, a computing device includes a central processing unit (CPU), a memory system, user input/output interfaces, peripheral device interfaces, and an interconnecting bus structure.
As is further known, a computer may effectively extend its CPU by using “cloud computing” to perform one or more computing functions (e.g., a service, an application, an algorithm, an arithmetic logic function, etc.) on behalf of the computer. Further, for large services, applications, and/or functions, cloud computing may be performed by multiple cloud computing resources in a distributed manner to improve the response time for completion of the service, application, and/or function. For example, Hadoop is an open source software framework that supports distributed applications enabling application execution by thousands of computers.
In addition to cloud computing, a computer may use “cloud storage” as part of its memory system. As is known, cloud storage enables a user, via its computer, to store files, applications, etc. on an Internet storage system. The Internet storage system may include a RAID (redundant array of independent disks) system and/or a dispersed storage system that uses an error correction scheme to encode data for storage. When unplanned, software update execution within a dispersed storage system may cause system optimization issues.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a schematic block diagram of an embodiment of a dispersed or distributed storage network (DSN) in accordance with the present invention;

FIG. 2 is a schematic block diagram of an embodiment of a computing core in accordance with the present invention;

FIG. 3 is a schematic block diagram of an example of dispersed storage error encoding of data in accordance with the present invention;

FIG. 4 is a schematic block diagram of a generic example of an error encoding function in accordance with the present invention;

FIG. 5 is a schematic block diagram of a specific example of an error encoding function in accordance with the present invention;

FIG. 6 is a schematic block diagram of an example of a slice name of an encoded data slice (EDS) in accordance with the present invention;

FIG. 7 is a schematic block diagram of an example of dispersed storage error decoding of data in accordance with the present invention;

FIG. 8 is a schematic block diagram of a generic example of an error decoding function in accordance with the present invention;

FIG. 9 is a schematic block diagram of an embodiment of executing a software update within a dispersed storage network (DSN) in accordance with the present invention; and

FIG. 10 is a logic diagram of an example of a method for executing a software update within a dispersed storage network (DSN) in accordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a schematic block diagram of an embodiment of a dispersed, or distributed, storage network (DSN) 10 that includes a plurality of computing devices 12-16, a managing unit 18, an integrity processing unit 20, and a DSN memory 22. The components of the DSN 10 are coupled to a network 24, which may include one or more wireless and/or wire lined communication systems; one or more non-public intranet systems and/or public internet systems; and/or one or more local area networks (LAN) and/or wide area networks (WAN).
The DSN memory 22 includes a plurality of storage units 36 that may be located at geographically different sites (e.g., one in Chicago, one in Milwaukee, etc.), at a common site, or a combination thereof. For example, if the DSN memory 22 includes eight storage units 36, each storage unit is located at a different site. As another example, if the DSN memory 22 includes eight storage units 36, all eight storage units are located at the same site. As yet another example, if the DSN memory 22 includes eight storage units 36, a first pair of storage units are at a first common site, a second pair of storage units are at a second common site, a third pair of storage units are at a third common site, and a fourth pair of storage units are at a fourth common site. Note that a DSN memory 22 may include more or less than eight storage units 36. Further note that each storage unit 36 includes a computing core (as shown in FIG. 2, or components thereof) and a plurality of memory devices for storing dispersed error encoded data.
Each of the computing devices 12-16, the managing unit 18, and the integrity processing unit 20 include a computing core 26, which includes network interfaces 30-33. Computing devices 12-16 may each be a portable computing device and/or a fixed computing device. A portable computing device may be a social networking device, a gaming device, a cell phone, a smart phone, a digital assistant, a digital music player, a digital video player, a laptop computer, a handheld computer, a tablet, a video game controller, and/or any other portable device that includes a computing core. A fixed computing device may be a computer (PC), a computer server, a cable set-top box, a satellite receiver, a television set, a printer, a fax machine, home entertainment equipment, a video game console, and/or any type of home or office computing equipment. Note that each of the managing unit 18 and the integrity processing unit 20 may be separate computing devices, may be a common computing device, and/or may be integrated into one or more of the computing devices 12-16 and/or into one or more of the storage units 36.
Each interface 30, 32, and 33 includes software and hardware to support one or more communication links via the network 24 indirectly and/or directly. For example, interface 30 supports a communication link (e.g., wired, wireless, direct, via a LAN, via the network 24, etc.) between computing devices 14 and 16. As another example, interface 32 supports communication links (e.g., a wired connection, a wireless connection, a LAN connection, and/or any other type of connection to/from the network 24) between computing devices 12 and 16 and the DSN memory 22. As yet another example, interface 33 supports a communication link for each of the managing unit 18 and the integrity processing unit 20 to the network 24.
Computing devices 12 and 16 include a dispersed storage (DS) client module 34, which enables the computing device to dispersed storage error encode and decode data (e.g., data 40) as subsequently described with reference to one or more of FIGS. 3-8. In this example embodiment, computing device 16 functions as a dispersed storage processing agent for computing device 14. In this role, computing device 16 dispersed storage error encodes and decodes data on behalf of computing device 14. With the use of dispersed storage error encoding and decoding, the DSN 10 is tolerant of a significant number of storage unit failures (the number of failures is based on parameters of the dispersed storage error encoding function) without loss of data and without the need for a redundant or backup copies of the data. Further, the DSN 10 stores data for an indefinite period of time without data loss and in a secure manner (e.g., the system is very resistant to unauthorized attempts at accessing the data).
In operation, the managing unit 18 performs DS management services. For example, the managing unit 18 establishes distributed data storage parameters (e.g., vault creation, distributed storage parameters, security parameters, billing information, user profile information, etc.) for computing devices 12-14 individually or as part of a group of user devices. As a specific example, the managing unit 18 coordinates creation of a vault (e.g., a virtual memory block associated with a portion of an overall namespace of the DSN) within the DSN memory 22 for a user device, a group of devices, or for public access and establishes per vault dispersed storage (DS) error encoding parameters for a vault. The managing unit 18 facilitates storage of DS error encoding parameters for each vault by updating registry information of the DSN 10, where the registry information may be stored in the DSN memory 22, a computing device 12-16, the managing unit 18, and/or the integrity processing unit 20.
The managing unit 18 creates and stores user profile information (e.g., an access control list (ACL)) in local memory and/or within memory of the DSN memory 22. The user profile information includes authentication information, permissions, and/or the security parameters. The security parameters may include encryption/decryption scheme, one or more encryption keys, key generation scheme, and/or data encoding/decoding scheme.
The managing unit 18 creates billing information for a particular user, a user group, a vault access, public vault access, etc. For instance, the managing unit 18 tracks the number of times a user accesses a non-public vault and/or public vaults, which can be used to generate a per-access billing information. In another instance, the managing unit 18 tracks the amount of data stored and/or retrieved by a user device and/or a user group, which can be used to generate a per-data-amount billing information.
As another example, the managing unit 18 performs network operations, network administration, and/or network maintenance. Network operations includes authenticating user data allocation requests (e.g., read and/or write requests), managing creation of vaults, establishing authentication credentials for user devices, adding/deleting components (e.g., user devices, storage units, and/or computing devices with a DS client module 34) to/from the DSN 10, and/or establishing authentication credentials for the storage units 36. Network administration includes monitoring devices and/or units for failures, maintaining vault information, determining device and/or unit activation status, determining device and/or unit loading, and/or determining any other system level operation that affects the performance level of the DSN 10. Network maintenance includes facilitating replacing, upgrading, repairing, and/or expanding a device and/or unit of the DSN 10.
The integrity processing unit 20 performs rebuilding of ‘bad’ or missing encoded data slices. At a high level, the integrity processing unit 20 performs rebuilding by periodically attempting to retrieve/list encoded data slices, and/or slice names of the encoded data slices, from the DSN memory 22. For retrieved encoded slices, they are checked for errors due to data corruption, outdated version, etc. If a slice includes an error, it is flagged as a ‘bad’ slice. For encoded data slices that were not received and/or not listed, they are flagged as missing slices. Bad and/or missing slices are subsequently rebuilt using other retrieved encoded data slices that are deemed to be good slices to produce rebuilt slices. The rebuilt slices are stored in the DSN memory 22.
FIG. 2 is a schematic block diagram of an embodiment of a computing core 26 that includes a processing module 50, a memory controller 52, main memory 54, a video graphics processing unit 55, an input/output (TO) controller 56, a peripheral component interconnect (PCI) interface 58, an IO interface module 60, at least one IO device interface module 62, a read only memory (ROM) basic input output system (BIOS) 64, and one or more memory interface modules. The one or more memory interface module(s) includes one or more of a universal serial bus (USB) interface module 66, a host bus adapter (HBA) interface module 68, a network interface module 70, a flash interface module 72, a hard drive interface module 74, and a DSN interface module 76.
The DSN interface module 76 functions to mimic a conventional operating system (OS) file system interface (e.g., network file system (NFS), flash file system (FFS), disk file system (DFS), file transfer protocol (FTP), web-based distributed authoring and versioning (WebDAV), etc.) and/or a block memory interface (e.g., small computer system interface (SCSI), internet small computer system interface (iSCSI), etc.). The DSN interface module 76 and/or the network interface module 70 may function as one or more of the interface 30-33 of FIG. 1. Note that the IO device interface module 62 and/or the memory interface modules 66-76 may be collectively or individually referred to as IO ports.
FIG. 3 is a schematic block diagram of an example of dispersed storage error encoding of data. When a computing device 12 or 16 has data to store it disperse storage error encodes the data in accordance with a dispersed storage error encoding process based on dispersed storage error encoding parameters. The dispersed storage error encoding parameters include an encoding function (e.g., information dispersal algorithm, Reed-Solomon, Cauchy Reed-Solomon, systematic encoding, non-systematic encoding, on-line codes, etc.), a data segmenting protocol (e.g., data segment size, fixed, variable, etc.), and per data segment encoding values. The per data segment encoding values include a total, or pillar width, number (T) of encoded data slices per encoding of a data segment (i.e., in a set of encoded data slices); a decode threshold number (D) of encoded data slices of a set of encoded data slices that are needed to recover the data segment; a read threshold number (R) of encoded data slices to indicate a number of encoded data slices per set to be read from storage for decoding of the data segment; and/or a write threshold number (W) to indicate a number of encoded data slices per set that must be accurately stored before the encoded data segment is deemed to have been properly stored. The dispersed storage error encoding parameters may further include slicing information (e.g., the number of encoded data slices that will be created for each data segment) and/or slice security information (e.g., per encoded data slice encryption, compression, integrity checksum, etc.).
In the present example, Cauchy Reed-Solomon has been selected as the encoding function (a generic example is shown in FIG. 4 and a specific example is shown in FIG. 5); the data segmenting protocol is to divide the data object into fixed sized data segments; and the per data segment encoding values include: a pillar width of 5, a decode threshold of 3, a read threshold of 4, and a write threshold of 4. In accordance with the data segmenting protocol, the computing device 12 or 16 divides the data (e.g., a file (e.g., text, video, audio, etc.), a data object, or other data arrangement) into a plurality of fixed sized data segments (e.g., 1 through Y of a fixed size in range of Kilo-bytes to Tera-bytes or more). The number of data segments created is dependent of the size of the data and the data segmenting protocol.
The computing device 12 or 16 then disperse storage error encodes a data segment using the selected encoding function (e.g., Cauchy Reed-Solomon) to produce a set of encoded data slices. FIG. 4 illustrates a generic Cauchy Reed-Solomon encoding function, which includes an encoding matrix (EM), a data matrix (DM), and a coded matrix (CM). The size of the encoding matrix (EM) is dependent on the pillar width number (T) and the decode threshold number (D) of selected per data segment encoding values. To produce the data matrix (DM), the data segment is divided into a plurality of data blocks and the data blocks are arranged into D number of rows with Z data blocks per row. Note that Z is a function of the number of data blocks created from the data segment and the decode threshold number (D). The coded matrix is produced by matrix multiplying the data matrix by the encoding matrix.
FIG. 5 illustrates a specific example of Cauchy Reed-Solomon encoding with a pillar number (T) of five and decode threshold number of three. In this example, a first data segment is divided into twelve data blocks (D1-D12). The coded matrix includes five rows of coded data blocks, where the first row of X11-X14 corresponds to a first encoded data slice (EDS 1_1), the second row of X21-X24 corresponds to a second encoded data slice (EDS 2_1), the third row of X31-X34 corresponds to a third encoded data slice (EDS 3_1), the fourth row of X41-X44 corresponds to a fourth encoded data slice (EDS 4_1), and the fifth row of X51-X54 corresponds to a fifth encoded data slice (EDS 5_1). Note that the second number of the EDS designation corresponds to the data segment number.
Returning to the discussion of FIG. 3, the computing device also creates a slice name (SN) for each encoded data slice (EDS) in the set of encoded data slices. A typical format for a slice name 80 is shown in FIG. 6. As shown, the slice name (SN) 80 includes a pillar number of the encoded data slice (e.g., one of 1-T), a data segment number (e.g., one of 1-Y), a vault identifier (ID), a data object identifier (ID), and may further include revision level information of the encoded data slices. The slice name functions as, at least part of, a DSN address for the encoded data slice for storage and retrieval from the DSN memory 22.
As a result of encoding, the computing device 12 or 16 produces a plurality of sets of encoded data slices, which are provided with their respective slice names to the storage units for storage. As shown, the first set of encoded data slices includes EDS 1_1 through EDS 5_1 and the first set of slice names includes SN 1_1 through SN 5_1 and the last set of encoded data slices includes EDS 1_Y through EDS 5_Y and the last set of slice names includes SN 1_Y through SN 5 Y.
FIG. 7 is a schematic block diagram of an example of dispersed storage error decoding of a data object that was dispersed storage error encoded and stored in the example of FIG. 4. In this example, the computing device 12 or 16 retrieves from the storage units at least the decode threshold number of encoded data slices per data segment. As a specific example, the computing device retrieves a read threshold number of encoded data slices.
To recover a data segment from a decode threshold number of encoded data slices, the computing device uses a decoding function as shown in FIG. 8. As shown, the decoding function is essentially an inverse of the encoding function of FIG. 4. The coded matrix includes a decode threshold number of rows (e.g., three in this example) and the decoding matrix in an inversion of the encoding matrix that includes the corresponding rows of the coded matrix. For example, if the coded matrix includes rows 1, 2, and 4, the encoding matrix is reduced to rows 1, 2, and 4, and then inverted to produce the decoding matrix.
FIG. 9 is a schematic block diagram of an embodiment of executing a software update within a dispersed storage network (DSN). The DSN of FIG. 9 includes a management unit 82 and a plurality of storage units is arranged as a set of storage unit groups. Storage unit group 1 includes storage units SU#0_0-SU#0_4, storage unit group 2 includes storage units SU#1_0-SU#1_4, storage unit group 3 includes storage units SU#2_0-SU#2_4, storage unit group 4 includes storage units SU#3_0-SU#3_4, storage unit group 5 includes storage units SU#4_0-SU#4_4, and storage unit group 6 includes storage units SU#5_0-SU#5_4. Storage units SU#0_0, SU#1_0, SU#2_0, SU#3_0, SU#4_0, and SU#5_0 are affiliated with vault 1_1 and vault 2_1. Storage units SU#0_1, SU#1_1, SU#2_1, SU#3_1, SU#4_1, and SU#5_1 are affiliated with vault 1_2 and vault 3_1. Storage units SU#0_2, SU#1_2, SU#2_2, SU#3_2, SU#4_2, and SU#5_2 are affiliated with vault 2_2 and vault 3_2. Storage units SU#0_3, SU#1_3, SU#2_3, SU#3_3, SU#4_3, and SU#5_3 are affiliated with vault 3_3. When the management unit 82 receives software updates 86 for implementation in the DSN, the management unit 82 develops a software update plan 84 to execute the software update(s) 86 in the most efficient and effective manner possible.
In an example of operation, the management unit 82 first determines the type of software update(s) 86 that is to be implemented. The type of software update includes at least one of a critical security vulnerability fix, a major release, a minor release, a patch release, a beta release, an alpha/development release, and a digitally signed release. Based on the type of software update and general timing restrictions (e.g., permitted days of the week and/or hours during the day for software updates) the management unit 82 generates a software update plan 84. The software update plan aggressively takes storage units of the set of storage unit groups offline for executing the software update when the type of the software update requires urgency while maintaining a sufficient number of storage units online to fulfill DSN access requests.
Some software update types require more urgency or aggressiveness in their implementation. For instance, a critical security vulnerability fix software update may require a more aggressive software update plan while a major software update release may require a more conservative plan. The aggressiveness of the update involves the number of storage units to update at a time, the closeness of the number of storage unit groups taken offline to the write threshold number/availability threshold number of vaults, the time period to wait between storage unit updates, and the fraction of storage units to update for a trial period.
For example, the software update plan 84 can take n-k storage unit groups of the set of storage unit groups offline for an urgent software update (e.g., the critical security vulnerability fix software update), where n is the total number of groups of the set of storage unit groups which corresponds to a total number of error encoded data slices in the set of encoded data slices of a data object, and where k is a decode threshold number. A decode threshold number is the number of slices of encoded data slices of a set of encoded data slices that are needed to recover the data segment. For example, FIG. 9 includes 6 storage groups and a decode threshold number of 3 storage groups. Therefore, according to this software update plan, a total of 3 storage groups may be taken offline to execute the software update.
When the software update is less urgent (e.g., a full software release), the software update plan 84 may determine to take 1 storage unit group offline at a time for the software update. As another example, the software update plan 84 may take n-r storage unit groups offline for the software update, where r is a read threshold number. A read threshold number of encoded data slices is a number of encoded data slices per set to be read from storage for decoding of the data segment. For example, FIG. 9 includes 6 storage groups and a read threshold number of 4. Therefore, according to this software update plan, a total of 2 storage groups may be taken offline to execute the software update. As another example, the software update plan 84 may take n-w storage unit groups offline for the software update, where w is a write threshold number. A write threshold is a number of encoded data slices per set that must be accurately stored before the encoded data segment is deemed to have been properly stored. For example, FIG. 9 includes 6 storage groups and a write threshold number of 4. Therefore, according to this software update plan, a total of 2 storage groups may be taken offline to execute the software update.
New software updates will be prioritized according to urgency but also based on the priority of other pending software updates. The management unit 82 can access a list of pending software updates for the set of storage unit groups, where the pending software updates are prioritized based on respective types. The management unit 82 adds the new software update to the list of pending software updates based on the type of software update, and generate a plurality of software plans for the updated list of pending software updates. The management unit 82 is operable to generate and execute an individual software plan for each storage unit of the set of storage unit groups (as well as a plan for the set as a whole). The management unit 82 is also operable to send the corresponding software update plan to each storage unit of the set of storage unit groups for execution. The management unit 82 can execute more than one software update plan at a time, and can coordinate storage units that are offline from each plan.
For example, the management unit 82 may determine a software update plan 84 to take n-k storage groups offline (as discussed above) to perform an urgent software update (e.g., the critical security vulnerability fix software update). However, another software update plan may still be pending. For example, the pending software update plan was for a full software release where 1 storage unit was taken offline at a time. The management unit 82 is operable to coordinate the new plan while taking into account the pending plan. For instance, if storage unit group 1 is offline according to the pending software update plan, the new plan may instruct storage unit group 1 to install the urgent software update while offline and instruct another two storage unit groups (e.g., storage unit groups 2 and 3) to also go offline for the urgent software update.
Alternatively, or in addition to analyzing pending software updates, and the timing and aggressiveness of the current software update, the management unit 82 obtains status information 88 from at least some of the storage units of the set of storage unit groups to generate the software update plan 84. The status information 88 includes one or more of: a list of current versions of installed software and an activity level indicator (e.g., storage unit usage). For example, the storage units of the set of storage unit groups have provided the management unit 82 with status information 88. Based on the status information 88 the management unit 82 generates the software update plan 84 of the at least some of the storage units that provided the status information. As shown, the management unit 82 has generated a software update plan 84 for all the storage units of the set of storage unit groups but has sent the storage units of storage unit group 6 (SU#5_0-SU#5-4) individual software update plans based on the provided status information 85 that differs from the software update plan 84 sent to other storage unit groups. For instance, the storage units of storage group 6 may have sent status information 88 indicating a high activity level. The software update plans based on the provided status information 85 may then include instructions to wait for the activity level to reduce prior to performing the software update.
Generating the software update plan also includes determining user configuration information 90 for a group of users of the DSN. The user configuration information 90 includes one or more of: vault information, user identification information, data type storage information, and DSN subscription information. The user configuration information 90 provides the management unit 82 information regarding the quality of service and reliability expected as well as the bandwidth, throughput, and storage volume of the group of users. The management unit 82 identifies the set of storage unit groups that support the group of users and generates the software update plan for those identified storage units. For example, after analyzing the user configuration information 90, the management unit 82 determines that users associated with vault 1_2 expect a higher level of service and reliability than users associated with other vaults. The management unit 82 identifies the storage units associated with vault 1_2 (SU#0_1-SU#5_1) and sends individual software update plans based on the user configuration information 87 to SU#0_1-SU#5_1.
When the software update plan 84 is generated, the management unit 82 executes the software update plan to update the set of groups of storage units with the software update. The management unit 82 may also instruct the storage units to utilize a previous version of software until all storage units of the set of storage unit groups are updated or until a last number of storage units of the set of storage unit groups are taken offline for the software update.
FIG. 10 is a logic diagram of an example of a method for executing a software update within a dispersed storage network (DSN). The method begins with step 92 where the management unit of the DSN determines the type of software update that is to be implemented. The type of software update includes at least one of a critical security vulnerability fix, a major release, a minor release, a patch release, a beta release, an alpha/development release, and a digitally signed release.
The method continues with step 94 where, based on the type of software update and general timing restrictions (e.g., permitted days of the week and/or hours during the day for software updates) the management unit generates a software update plan for updating a set of storage unit groups of the DSN. A first storage unit group of the set of storage unit groups includes one or more storage units and stores first encoded data slices of pluralities of sets of encoded data slices. A decode threshold number of encoded data slices of a set of encoded data slices of the pluralities of sets of encoded data slices is needed to recover a data segment of a data object of a plurality of data objects. The software update plan aggressively takes storage units of the set of storage unit groups offline for executing the software update when the type of the software update requires urgency while maintaining a sufficient number of storage units online to fulfill DSN access requests. Some software update types require more urgency or aggressiveness in their implementation. For instance, a critical security vulnerability fix software update may require a more aggressive software update plan. The aggressiveness of the update involves the number of storage units to update at a time, the closeness of the number of storage unit groups taken offline to the write threshold number/availability threshold number of vaults, the time period to wait between storage unit update, and the fraction of storage units to update for a trial period. Therefore, for the critical security vulnerability fix software update, the software update plan may take as many storage unit groups as possible offline at a time to perform the update.
For example, the software update plan may take n-k storage unit groups of the set of storage unit groups offline for an urgent software update, where n is the total number of groups of the set of storage unit groups which corresponds to a total number of error encoded data slices in the set of encoded data slices of a data object, and where k is a decode threshold number. A decode threshold number is the number of slices of encoded data slices of a set of encoded data slices that are needed to recover the data segment. When the urgency is lower, the software update plan may take n-r storage unit groups offline for the software update, where r is a read threshold number. A read threshold number of encoded data slices is a number of encoded data slices per set to be read from storage for decoding of the data segment. Further, the software update plan may take n-w storage unit groups offline for the software update, where w is a write threshold number. A write threshold is a number of encoded data slices per set that must be accurately stored before the encoded data segment is deemed to have been properly stored. The software update plan may also determine to take one storage unit group offline at a time for lower priority software updates (e.g., a full software release).
New software updates will be prioritized according to urgency but also based on the priority of other pending software updates. The management unit accesses a list of pending software updates for the set of storage unit groups, where the pending software updates are prioritized based on respective types. The management unit adds the new software update to the list of pending software updates based on the type of software update, and generate a plurality of software plans for the updated list of pending software updates. The management unit is operable to generate an individual software plan for each storage unit of the set of storage unit groups (as well as for the set of storage unit groups as a whole). The management unit is also operable to send the corresponding software update plan to each storage unit of the set of storage unit groups for execution. The management unit can execute more than one software update plan at a time, and can coordinate storage units that are offline from each plan.
Alternatively, or in addition to analyzing pending software updates, and the timing and aggressiveness of the current software update, the management unit may also obtain status information from at least some of the storage units of the set of storage unit groups to generate the software update plan. The status information includes one or more of: a list of current versions of installed software and an activity level indicator (e.g., storage unit usage). Based on the status information, the management unit generates the software update plan of the at least some of the storage units that provided the status information.
Generating the software update plan also includes determining user configuration information for a group of users of the DSN. The user configuration information includes one or more of: vault information, user identification information, data type storage information, and DSN subscription information. The user configuration information provides the management unit information as to the quality of service and reliability expected as well as the bandwidth, throughput, and storage volume of the group of users. The management unit identifies the set of storage unit groups that support the group of users and generate the software update plan for the identified storage units.
When the software update plan is generated, the method continues to step 96 where the management unit executes the software update plan to update the set of groups of storage units with the software update. The management unit may also instruct the storage units to utilize a previous version of software until all storage units of the set of storage unit groups are updated or until a last number of storage units of the set of storage unit groups are taken offline for the software update.
It is noted that terminologies as may be used herein such as bit stream, stream, signal sequence, etc. (or their equivalents) have been used interchangeably to describe digital information whose content corresponds to any of a number of desired types (e.g., data, video, speech, audio, etc. any of which may generally be referred to as ‘data’).
As may be used herein, the terms “substantially” and “approximately” provides an industry-accepted tolerance for its corresponding term and/or relativity between items. Such an industry-accepted tolerance ranges from less than one percent to fifty percent and corresponds to, but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. Such relativity between items ranges from a difference of a few percent to magnitude differences. As may also be used herein, the term(s) “configured to”, “operably coupled to”, “coupled to”, and/or “coupling” includes direct coupling between items and/or indirect coupling between items via an intervening item (e.g., an item includes, but is not limited to, a component, an element, a circuit, and/or a module) where, for an example of indirect coupling, the intervening item does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As may further be used herein, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two items in the same manner as “coupled to”. As may even further be used herein, the term “configured to”, “operable to”, “coupled to”, or “operably coupled to” indicates that an item includes one or more of power connections, input(s), output(s), etc., to perform, when activated, one or more its corresponding functions and may further include inferred coupling to one or more other items. As may still further be used herein, the term “associated with”, includes direct and/or indirect coupling of separate items and/or one item being embedded within another item.
As may be used herein, the term “compares favorably”, indicates that a comparison between two or more items, signals, etc., provides a desired relationship. For example, when the desired relationship is that signal 1 has a greater magnitude than signal 2, a favorable comparison may be achieved when the magnitude of signal 1 is greater than that of signal 2 or when the magnitude of signal 2 is less than that of signal 1. As may be used herein, the term “compares unfavorably”, indicates that a comparison between two or more items, signals, etc., fails to provide the desired relationship.
As may also be used herein, the terms “processing module”, “processing circuit”, “processor”, and/or “processing unit” may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module, module, processing circuit, and/or processing unit may be, or further include, memory and/or an integrated memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of another processing module, module, processing circuit, and/or processing unit. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that if the processing module, module, processing circuit, and/or processing unit includes more than one processing device, the processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) or may be distributedly located (e.g., cloud computing via indirect coupling via a local area network and/or a wide area network). Further note that if the processing module, module, processing circuit, and/or processing unit implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. Still further note that, the memory element may store, and the processing module, module, processing circuit, and/or processing unit executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in one or more of the Figures. Such a memory device or memory element can be included in an article of manufacture.
One or more embodiments have been described above with the aid of method steps illustrating the performance of specified functions and relationships thereof. The boundaries and sequence of these functional building blocks and method steps have been arbitrarily defined herein for convenience of description. Alternate boundaries and sequences can be defined so long as the specified functions and relationships are appropriately performed. Any such alternate boundaries or sequences are thus within the scope and spirit of the claims. Further, the boundaries of these functional building blocks have been arbitrarily defined for convenience of description. Alternate boundaries could be defined as long as the certain significant functions are appropriately performed. Similarly, flow diagram blocks may also have been arbitrarily defined herein to illustrate certain significant functionality.
To the extent used, the flow diagram block boundaries and sequence could have been defined otherwise and still perform the certain significant functionality. Such alternate definitions of both functional building blocks and flow diagram blocks and sequences are thus within the scope and spirit of the claims. One of average skill in the art will also recognize that the functional building blocks, and other illustrative blocks, modules and components herein, can be implemented as illustrated or by discrete components, application specific integrated circuits, processors executing appropriate software and the like or any combination thereof.
In addition, a flow diagram may include a “start” and/or “continue” indication. The “start” and “continue” indications reflect that the steps presented can optionally be incorporated in or otherwise used in conjunction with other routines. In this context, “start” indicates the beginning of the first step presented and may be preceded by other activities not specifically shown. Further, the “continue” indication reflects that the steps presented may be performed multiple times and/or may be succeeded by other activities not specifically shown. Further, while a flow diagram indicates a particular ordering of steps, other orderings are likewise possible provided that the principles of causality are maintained.
The one or more embodiments are used herein to illustrate one or more aspects, one or more features, one or more concepts, and/or one or more examples. A physical embodiment of an apparatus, an article of manufacture, a machine, and/or of a process may include one or more of the aspects, features, concepts, examples, etc. described with reference to one or more of the embodiments discussed herein. Further, from figure to figure, the embodiments may incorporate the same or similarly named functions, steps, modules, etc. that may use the same or different reference numbers and, as such, the functions, steps, modules, etc. may be the same or similar functions, steps, modules, etc. or different ones.
Unless specifically stated to the contra, signals to, from, and/or between elements in a figure of any of the figures presented herein may be analog or digital, continuous time or discrete time, and single-ended or differential. For instance, if a signal path is shown as a single-ended path, it also represents a differential signal path. Similarly, if a signal path is shown as a differential path, it also represents a single-ended signal path. While one or more particular architectures are described herein, other architectures can likewise be implemented that use one or more data buses not expressly shown, direct connectivity between elements, and/or indirect coupling between other elements as recognized by one of average skill in the art.
The term “module” is used in the description of one or more of the embodiments. A module implements one or more functions via a device such as a processor or other processing device or other hardware that may include or operate in association with a memory that stores operational instructions. A module may operate independently and/or in conjunction with software and/or firmware. As also used herein, a module may contain one or more sub-modules, each of which may be one or more modules.
As may further be used herein, a computer readable memory includes one or more memory elements. A memory element may be a separate memory device, multiple memory devices, or a set of memory locations within a memory device. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. The memory device may be in a form a solid state memory, a hard drive memory, cloud memory, thumb drive, server memory, computing device memory, and/or other physical medium for storing digital information.
While particular combinations of various functions and features of the one or more embodiments have been expressly described herein, other combinations of these features and functions are likewise possible. The present disclosure is not limited by the particular examples disclosed herein and expressly incorporates these other combinations.

Claims

What is claimed is:

1. A method for executing a software update within a dispersed storage network (DSN), the method comprises:

determining, by a management unit of the DSN, a type of the software update;

based on the type of the software update, generating, by the management unit, a software update plan for updating a set of storage unit groups of the DSN, wherein a first storage unit group of the set of storage unit groups includes one or more storage units and stores first encoded data slices of pluralities of sets of encoded data slices, wherein a decode threshold number of encoded data slices of a set of encoded data slices of the pluralities of sets of encoded data slices is needed to recover a data segment of a data object of a plurality of data objects, wherein the software update plan aggressively takes storage units of the set of storage unit groups offline for executing the software update when the type of the software update requires urgency while maintaining a sufficient number of storage units online to fulfill DSN access requests; and

executing, by the management unit, the software update plan to update the set of storage unit groups with the software update.

2. The method of claim 1, wherein the type of software update comprises at least one of:

a critical security vulnerability fix;

a major release;

a minor release;

a patch release;

a beta release;

an alpha development release; and

a digitally signed release.

3. The method of claim 1 further comprises:

accessing, by the management unit, a list of pending software updates for the set of storage unit groups, wherein the pending software updates are prioritized based on respective types;

adding, by the management unit, the software update to the list of pending software updates based on the type of software update; and

generating, by the management unit, a plurality of software plans for the updated list of pending software updates.

4. The method of claim 1 further comprises:

obtaining, by the management unit, status information from at least some of the storage units of the set of storage unit groups, wherein the status information includes one or more of: a list of current versions of installed software, and an activity level indicator; and

generating, by the management unit, the software update plan based on the status information of the at least some of the storage units.

5. The method of claim 1, wherein the generating the software update plan further comprises:

generating, by the management unit, an individual software update plan for each storage unit of the set of storage unit groups; and

sending, by the management unit, the corresponding individual software update plan to each storage unit of the set of storage unit groups.

6. The method of claim 1, wherein the generating the software update plan comprises one of:

taking n-k storage unit groups of the set of storage unit groups offline for the software update, wherein n is the total number of groups of the set of storage unit groups which corresponds to a total number of error encoded data slices in the set of encoded data slices, and wherein k is a decode threshold number;

taking n-r storage unit groups offline for the software update, wherein r is a read threshold number;

taking n-w storage unit groups offline for the software update, wherein w is a write threshold number; and

taking one storage unit group offline at a time for the software update.

7. The method of claim 1 further comprises:

instructing, by the management unit, to utilize a previous version of software until all storage units of the set of storage unit groups are updated or until a last number of storage units of the set of storage unit groups are taken offline for the software update.

8. The method of claim 1, wherein the generating the software update plan comprises:

determining, for a group of users, user configuration information that includes one or more of: vault information, user identification information, data type storage information, and DSN subscription information;

identifying storage units of the set of storage unit groups that support the group of users; and

generating the software update plan for the identified storage units in accordance with the user configuration information.

9. A management unit for executing a software update within a dispersed storage network (DSN), the management unit comprises:

an interface;

memory; and

a processing module operably coupled to the memory and the interface, wherein the processing module is operable to:

determine a type of the software update;

based on the type of the software update, generate a software update plan for updating a set of storage unit groups of the DSN, wherein a first storage unit group of the set of storage unit groups includes one or more storage units and stores first encoded data slices of pluralities of sets of encoded data slices, wherein a decode threshold number of encoded data slices of a set of encoded data slices of the pluralities of sets of encoded data slices is needed to recover a data segment of a data object of a plurality of data objects, wherein the software update plan aggressively takes storage units of the set of storage unit groups offline for executing the software update when the type of the software update requires urgency while maintaining a sufficient number of storage units online to fulfill DSN access requests; and

execute the software update plan to update the set of storage unit groups with the software update.

10. The management unit of claim 9, wherein the type of software update comprises at least one of:

a critical security vulnerability fix;

a major release;

a minor release;

a patch release;

a beta release;

an alpha development release; and

a digitally signed release.

11. The management unit of claim 9, wherein the processing module is further operable to:

access a list of pending software updates for the set of storage unit groups, wherein the pending software updates are prioritized based on respective types;

add the software update to the list of pending software updates based on the type of software update; and

generate a plurality of software plans for the updated list of pending software updates.

12. The management unit of claim 9, wherein the processing module is further operable to:

obtain status information from at least some of the storage units of the set of storage unit groups, wherein the status information includes one or more of: a list of current versions of installed software, and an activity level indicator; and

generate the software update plan based on the status information of the at least some of the storage units.

13. The management unit of claim 9, wherein the processing module is further operable to generate the software update plan by:

generating an individual software update plan for each storage unit of the set of storage unit groups; and

sending the corresponding individual software update plan to each storage unit of the set of storage unit groups.

14. The management unit of claim 9, wherein the processing module is further operable to generate the software update plan by:

taking one storage unit group offline at a time for the software update.

15. The management unit of claim 9, wherein the processing module is further operable to:

instruct to utilize a previous version of software until all storage units of the set of storage unit groups are updated or until a last number of storage units of the set of storage unit groups are taken offline for the software update.

16. The management unit of claim 9, wherein the processing module is further operable to generate the software update plan by: