Emc IP Holding Company LLC

Dell Products Inc.

Raymond Ramsden

Curtis Robert

Antony Richards

David Leimbach

Harsha Mahuli

Michael Frank

Mark Ranger

Steven Soumpholphakdy

Ryan Libby

Jahanvi Bishnoi

Joshua Nelson

The technology described herein is directed towards automating/orchestrating removal of one or more nodes of a node cluster, including in a cloud computing environment in which nodes in a cluster map to deployed virtual machines. An automated workflow can be started based on user input specifying an amount of capacity to remove, which corresponds to one or more nodes to remove. In a node cluster with associated nodes arranged into pools of nodes, node removal is per node pool. An orchestrated workflow performs pre-validation based on satisfying appropriate removal criteria, followed by data move and node removal jobs, and post-validation to check that removed capacity is generally as specified and that the remaining node layout is appropriate. Data of any removed node is re-protected, such as by restoring data from removed nodes to remaining cluster nodes in a manner that maintains the data with a data protection scheme.

Orchestrated node removal to reduce cluster capacity in a clustered file system

Shielding a storage device of a storage system from one or more storage performance enhancement procedures (SPEPs) is disclosed. A SPEP can be regarded as a procedure that manipulates data stored via a storage device in a manner that attempts to improve performance of the storage system. As such, SPEPs are generally distinct from basic reading and writing of data that is not associated with storage system performance optimization. A SPEP can typically be effectively run without storage device performance degradation, however some conditions, such as very full drives, etc., can result in substantial storage device performance degradation where one or more SPEP is performed. As such, shielding can restrict permission to perform one or more SPEPs at a storage device expected to, or actually experiencing, a threshold level of performance degradation. Shielding is distinct from conventional techniques marking a drive as failed, failing, etc., as is disclosed herein.

Shielding a storage device of a storage system

Methods, systems and computer program products for maintaining components of networked nodes with distributed data dependencies are described. For example, in accordance with one or more embodiments, a method can comprise identifying, by a device comprising a processor, in a group of dependent nodes of a cluster of nodes, a first portion of the dependent nodes for which an update is implicated. The method can further comprise selecting, by the device, from the first portion, a second portion of the dependent nodes that are predicted to be able to be updated with the update without affecting access to data of the group of dependent nodes. Further, the method can comprise communicating, by the device, the update to the second portion of the dependent nodes.

Maintaining components of networked nodes with distributed data dependencies

Facilitating device compatibility is provided herein. A system can comprise a processor and a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations. The operations can comprise evaluating a parameter of a device to a defined parameter of a device pool based on receipt of a request to add the device to the device pool and based on a determination that a device type of the device does not match a defined device type of the device pool. Further, the operations can comprise either allowing the device to be included in the device pool based on the evaluating, or denying the device to be included in the device pool based on the evaluating. If the inclusion of the device is denied, the operations can comprise providing information indicative of a denial to add the device to the device pool.

Device compatibility in a communication architecture

Policy-based performance of storage management operations on objects of a file system using an index of the file system is presented herein. An object policy component maintains an object policy specifying that an operation is to be performed on an object of objects that have been stored in a system in response to a determination that a state of the object satisfies a defined policy condition. Further, a job component periodically accesses an index data structure of the system comprising respective attributes of the objects that have been stored in the system, and in response to the state of the object being determined, based on a group of attributes of the respective attributes of the object, to satisfy the defined policy condition, performs the operation on the object.

Growing community of inventors

Seattle, WA, United States of America

Raymond Ramsden