Abstract: A service band management system includes management device(s) coupled to a workload provisioning infrastructure. The management device(s) identify a first workload provisioning system in a workload provisioning infrastructure, and determine its first workload provisioning capability. Based on the first workload provisioning capability, the management device(s) map the first workload provisioning system to a first service band, and provision a workload using the first workload provisioning system based on the first service band satisfying a workload requirement for the workload. Subsequently, the management device(s) identify that a second workload provisioning system has been added to the workload provisioning infrastructure, and determine its second workload provisioning capability.

Abstract: A data deduplication system includes a data deduplication subsystem coupled to each of a host system and a storage system. The data deduplication system receives data from the host system, generates a data deduplication identifier for the data, and determines whether the data deduplication identifier for the data is stored in a data deduplication database. In response to determining that the data deduplication identifier is not stored in the data deduplication database, the data deduplication system stores the data deduplication identifier for the data in the data deduplication database in association with a data counter for the data, and transmits the data to the storage system for storage. In response to determining that the data deduplication identifier is stored in the data deduplication database, the data deduplication system increments a data counter that is associated with the data deduplication identifier in the data deduplication database, and discards the data.

Abstract: A data replication system includes a first data replication subsystem coupled to a first storage system. The first data replication subsystem identifies a data deduplication identifier for data being written to or already stored on the first storage system, and determines whether the data deduplication identifier is in a data deduplication database. If so, the first data replication subsystem transmits the data for storage in a second storage system. If not, the first data replication subsystem transmits a data counter update instruction. In response to receiving the data, a second data replication subsystem stores the data deduplication identifier in the data deduplication database in association with a data counter; and stores the data in the second storage system. In response to receiving the data counter update instruction, the second data replication subsystem updates a data counter associated with the data deduplication identifier in the data deduplication database.

Abstract: A networking-based file share witness system includes a cluster system including a plurality of node devices, and a first networking device that is coupled to a network and to each of the node devices in the cluster system. The first networking device includes a first networking engine that transmits data between the network and the node devices in the cluster system. The first networking device also includes a first file share that stores a quorum file that is configured to provide, subsequent to the unavailability of at least one of the node devices in the cluster system, a first file share witness vote that is configured to be utilized with at least one node vote provided by at least one of the node devices in the cluster system that remains available in order to reach a quorum and allow the cluster system to continue to operate.

Abstract: A Hyper-Converged Infrastructure (HCI) networking configuration system includes HCI node subsystems with different configuration requirements, and a networking subsystem coupled HCI node subsystems via respective port(s). The networking subsystem identifies each of the HCI node subsystems and, based on that determine, based on those identifications, determines respective different configuration requirements for each of the HCI node subsystems. Based on those respective configuration requirements, the networking subsystem generates a networking subsystem configuration, and applies the networking subsystem configuration to the networking subsystem such that each of its respective ports coupled to the HCI node subsystems is configured to provide communication between the networking subsystem and that HCI node subsystem.

Abstract: A networking-device-based HCI edge controller system includes a networking device coupled to a master controller system via a network, as well as locally to an HCI node system including HCI node(s). The networking device and the HCI node system are provided at an edge location in a network, and the networking device operates to identify HCI node components that are included in the HCI node(s) in the HCI node system, and retrieve respective software inventory information for each of the HCI node component in the HCI node(s). The networking device receives first updated software from the master controller system via the network, determines that the respective software inventory information for at least one of the HCI node components does not comply with the first updated software for those HCI node components and, in response, provides the first updated software on those HCI node components.

Abstract: A composable infrastructure update system includes a composable infrastructure management system coupled to a composable infrastructure system including composable infrastructure components. The composable infrastructure management system identifies workload solutions that are being provided by at least one of the composable infrastructure components and, for each workload solution, generates a respective workload solution catalog that identifies the at least one of the composable infrastructure components that are providing that workload solution. The composable infrastructure management system then receive a software update for a first composable infrastructure component, determines that the first composable infrastructure component is being used to provide at least two of the workload solutions, and schedules the performance of the software update for the first composable component in consideration of the at least two of the workload solutions.

Abstract: A deployment orchestrator for managing deployment of a solution architecture includes persistent storage that stores a deployment plan and a deployment manager that orchestrates display, to a user of a user device of the solution architecture, of a graphical user interface (GUI) based on the deployment plan; obtains a task completion indicator for a task specified by the deployment plan via the graphical user interface; updates, based on the task completion indicator, at least one of a task GUI element of the GUI that is associated with the task and a relationship indicator of the GUI that is associated with the task to obtain an updated GUI; after updating the GUI: performs an automated validation task associated with the task; and makes a determination, based on the automated validation task, that the task is completed; and updates the updated GUI, based on the determination, to obtain a second updated GUI.

Abstract: A method for managing data includes identifying, by a compute acceleration device (CAD) of a persistent storage device, a first chunk, stored in the persistent storage device, to be health-checked using storage metadata, generating a first chunk identifier using the first chunk, making a determination that the first chunk identifier does not match a second chunk identifier stored in the storage metadata, and in response to the determination: obtaining a plurality of chunks associated with the first chunk from a plurality of persistent storage devices of a storage system, wherein the storage system comprises the persistent storage device and the plurality of persistent storage devices, regenerating the first chunk using the plurality of chunks to generate a new first chunk, storing the new first chunk in the persistent storage device, and updating the storage metadata based on storage of the new first chunk.

Abstract: A client recovery orchestrator for recovering clients after faults includes a persistent storage and a recovery manager. The persistent storage stores a fault correction script. The recovery manager obtains a fault profile associated with a client of the clients, matches the fault profile to a corrective action based on an associative model that associates dimensions of the fault profile and the corrective action, obtains the fault correction script based on the corrective action, orchestrates execution of the fault correction script to obtain an updated client, and updates the associative model based on the updated client.

Abstract: A configurable device for use in a solution architecture includes computing resources. The configurable device further includes a computing resources state manager. The computing resources state manager obtains an out-of-band modification to the computing resources. The computing resources state manager, in response to obtaining the out-of-band modification, generates an out-of-band configuration based on the out-of-band modification. The computing resources state manager further, in response to obtaining the out-of-band modification, updates restoration information for the computing resources based on the out-of-band configuration.

Abstract: A data storage system includes accelerated storages that store data encoded using a first data integrity scheme. The data storage system also includes a global enumerator that obtains a request to use a second data integrity scheme to store the data; in response to obtaining the request: performs a recoding process for the data including: reading data chunks, corresponding to the data, from the storages; generating new data chunks based on: the read data chunks and the second data integrity scheme; storing the new data chunks in the accelerated storages in an arrangement specified by the second data integrity scheme; and deleting the data chunks after storing the new data chunks.

Abstract: In general, embodiments of the invention relate to storing data and managing the stored data in linked nodes. More specifically, embodiments of the invention relate to nodes linked together in a daisy chain configuration such as, but not limited to, a single-chain configuration and a dual-chain configuration, which use data protection domain (DPD) information to determine where and/or how to store the data.

Abstract: A data storage system includes a first region, a second region, and a global enumerator. The first region stores a first copy of data. The second region stores a second copy of the data. The global enumerator performs a data control analysis of the data to identify that the first region is a high regulation region and the second region is a low regulation region; in response to making the identification: updates first metadata associated with the first copy of the data to regulate access to the first copy of the data; and updates second metadata associated with the second copy of the data to deregulate access to the second copy of the data.

Abstract: A data storage system includes storage and a global enumerator. The storage stores data chunks, object level metadata associated with portions of the data chunks, and chunk level metadata associated with respective data chunks. The global enumerator obtains an update request including a metadata characteristic and update data; in response to obtaining the update request: matches the metadata characteristic to at least one selected from a group consisting of a portion of the object level metadata and a portion of the chunk level metadata to identify an implicated metadata portion; and modifies, based on the update data, the implicated metadata portion.

Abstract: A data storage system includes storage and a global enumerator. The storage stores data chunks, object level metadata associated with portions of the data chunks, and chunk level metadata associated with respective data chunks. The global enumerator obtains a data access request that includes a metadata characteristic; in response to obtaining the data access request: matches the metadata characteristic to at least one of the data chunks based on at least one selected from a group consisting of the object level metadata and the chunk level metadata; and provides a response based on the at least one data chunk of the data chunks in response to the data access request.

Abstract: In general, embodiments of the invention relate to storing data and managing the stored data in linked nodes. More specifically, embodiments of the invention relate to nodes linked together in a daisy chain configuration such as, but not limited to, a single-chain configuration and a dual-chain configuration, which use data protection domain (DPD) information to determine where and/or how to store the data.

Abstract: In general, embodiments of the invention relate to storing data and managing the stored data in linked nodes. More specifically, embodiments of the invention relate to nodes linked together in a daisy chain configuration such as, but not limited to, a single-chain configuration and a dual-chain configuration, which use data protection domain (DPD) information to determine where and/or how to store the data.

Abstract: In general, embodiments of the invention relate to storing data and managing the stored data in linked nodes. More specifically, embodiments of the invention relate to nodes linked together in a daisy chain configuration such as, but not limited to, a single-chain configuration and a dual-chain configuration, which use data protection domain (DPD) information to determine where and/or how to store the data.

Abstract: In general, embodiments of the invention relate to storing data and managing the stored data in linked nodes. Managing the data in the linked nodes includes updating erasure coded data in a manner that reduces the transmission of data chunks and parity chunks between the linked nodes.