Abstract: 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.

Abstract: The technologies described herein are generally directed toward increasing a storage capacity of a storage cluster. In an embodiment, a method can include identifying a cluster for a change in storage capacity, the cluster having been deployed using a set of node devices that support the cluster. The method can further include, based on a capacity specification, deploying a virtual machine on a node device that is not part of the set of node devices. Further, the method can include, based on a capacity specification, merging the node device into the set of node devices, resulting in a merged set of node devices to support the cluster and achieve the change in storage capacity.

Abstract: The technologies described herein are generally directed toward migrating a function between virtual machines. In an embodiment, a method can include identifying a cluster for scaling, deployed using a first node device of a set of node devices supporting the cluster, wherein the first node device has a first virtual machine deployed thereon to support a function of functions of the cluster. The method can further include, based on a scaling specification, deploying, by the system, a second virtual machine on a second node device. Finally, the method can include, based on the scaling specification, migrating, by the system, the function, from the first virtual machine to the second virtual machine.

Abstract: 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.

Abstract: The technology described herein is directed towards automating the replacement of a virtual machine when the hardware underlying the virtual machine fails, including in a cloud computing environment in which nodes in a cluster map to virtual machines being deployed within that cloud provider. An automated workflow to perform cluster self-healing is started upon detection of an unrecoverable instance failure of a virtual machine, e.g., because of underlying hardware failure. The failed virtual machine is terminated, and a new, replacement virtual machine that matches characteristics of the failed virtual machine is created to join the cluster. Data of the failed node is re-protected, such as by restoring data maintained with a protection scheme to remaining virtual machines of the cluster. When the data is re-protected and the replacement virtual machine has joined the cluster, the data is rebalanced across the cluster nodes, including to the new virtual machine.

Abstract: The technology described herein is directed towards automating the replacement of a virtual machine when the hardware underlying the virtual machine fails, including in a cloud computing environment in which nodes in a cluster map to virtual machines being deployed within that cloud provider. An automated workflow to perform cluster self-healing is started upon detection of an unrecoverable instance failure of a virtual machine, e.g., because of underlying hardware failure. The failed virtual machine is terminated, and a new, replacement virtual machine that matches characteristics of the failed virtual machine is created to join the cluster. Data of the failed node is re-protected, such as by restoring data maintained with a protection scheme to remaining virtual machines of the cluster. When the data is re-protected and the replacement virtual machine has joined the cluster, the data is rebalanced across the cluster nodes, including to the new virtual machine.

Abstract: A system can validate multiple nonvolatile random-access memory (NVRAM) devices in parallel. The system can concurrently write a first data to a first volatile memory of a first NVRAM device and a second NVRAM device. The system can modify a first electrical power source that provides an electrical power output that is received by the first NVRAM device and is received by the second NVRAM device to modify a voltage of the electrical power from a first value to a second value to initiate the first NVRAM device and the second NVRAM device to respectively perform a vault. The system can reset the first electrical power source, causing the first NVRAM device and the second NVRAM device to reset. The system can verify whether the first NVRAM device and the second NVRAM device respectively store the first data in volatile memory subsequent to performing the resetting.

Abstract: A system can validate multiple nonvolatile random-access memory (NVRAM) devices in parallel. The system can concurrently write a first data to a first volatile memory of a first NVRAM device and a second NVRAM device. The system can modify a first electrical power source that provides an electrical power output that is received by the first NVRAM device and is received by the second NVRAM device to modify a voltage of the electrical power from a first value to a second value to initiate the first NVRAM device and the second NVRAM device to respectively perform a vault. The system can reset the first electrical power source, causing the first NVRAM device and the second NVRAM device to reset. The system can verify whether the first NVRAM device and the second NVRAM device respectively store the first data in volatile memory subsequent to performing the resetting.