Abstract: A boot image is modified to require authentication based on stable system values that are uniquely associated with a storage array. The stable system values may be used as a key to decrypt a password. The modified boot image will not allow booting to proceed without the decrypted password. The password cannot be decrypted based on different stable system values such as the stable system values of other storage arrays.

Abstract: A data processing device includes persistent storage and a software development manager. The persistent storage stores a code repository. The software development manager generates commit impact information based on: pre-commit code for a code base stored in the code repository, and dependency data based on committed code of the code base; displays a pre-commit analysis graphic user interface (GUI) reflecting the commit impact information and testing information for the pre-commit code; obtains, using the displayed pre-commit analysis GUI, reviewer feedback regarding approval of the pre-commit code; makes a determination, based on the reviewer feedback, that the pre-commit code has been approved; in response to the determination: performs limited testing of the code base based upon the dependency data to obtain testing results; and commits the pre-commit code to the committed code when the testing results match a predetermined behavior.

Abstract: A boot image is modified to require authentication based on stable system values that are uniquely associated with a storage array. The stable system values may be used as a key to decrypt a password. The modified boot image will not allow booting to proceed without the decrypted password. The password cannot be decrypted based on different stable system values such as the stable system values of other storage arrays.

Abstract: A data processing device includes persistent storage and a software development manager. The persistent storage stores a code repository. The software development manager generates commit impact information based on: pre-commit code for a code base stored in the code repository, and dependency data based on committed code of the code base; displays a pre-commit analysis graphic user interface (GUI) reflecting the commit impact information and testing information for the pre-commit code; obtains, using the displayed pre-commit analysis GUI, reviewer feedback regarding approval of the pre-commit code; makes a determination, based on the reviewer feedback, that the pre-commit code has been approved; in response to the determination: performs limited testing of the code base based upon the dependency data to obtain testing results; and commits the pre-commit code to the committed code when the testing results match a predetermined behavior.

Abstract: Data Virtual Data Movers (VDM) are assigned to nodes of the storage cluster and a backup node is assigned for each data VDM. A system VDM on each node collects node statistics including operational parameters of the node and activity levels of the data VDMs on the node. A cluster manager collects the node statistics from each of the system VDMs and uses weighted collected node statistics to assign a node score to each node in the storage cluster. The cluster manager uses the node scores to identify possible data VDM movement combinations within the storage cluster by applying a set of hard rules and a set of soft rules to evaluate the possible data VDM movement combinations. If a VDM movement combination is selected, it is implemented by moving at least some of the data VDMs within the cluster to attempt to equalize node scores within the cluster.