Abstract: A plurality of different virtualization system images are configured for deployment to a plurality of nodes in heterogeneous environments. Individual ones of the virtualization system images are configured such that once deployed, the nodes form a computer cluster having a storage pool that is shared across the nodes. When configuring the virtualization system images, information that describes the heterogeneous computing environments is accessed, and constraints pertaining the heterogeneous computing environments are reconciled in advance of configuring the different virtualization system images. A common subnet across the heterogeneous environments is established. The plurality of different virtualization system images are configured to access the common subnet once deployed. The common subnet serves as a storage I/O communication path over which a cluster-wide storage pool is implemented.

Abstract: A cluster configuration request to form a hyperconverged computing infrastructure (HCI) cluster in a cloud computing environment is processed. Based on the cluster configuration request and any other cluster specifications, a plurality of bare metal computing nodes of the cloud computing environment are configured to operate as an HCI cluster. First, a tenant-specific secure network overlay is formed on a first set of tenant-specific networking hardware resources. Then, the tenant-specific secure network overlay is used by an orchestrator to provision a second set of tenant-specific networking hardware resources. The second set of tenant-specific networking hardware resources are configured to interconnect node-local storage devices into a shared storage pool having a contiguous address space. Top-of-rack switches are configured to form a network overlay on the first set of tenant-specific networking hardware resources.

Abstract: A plurality of different virtualization system images are configured for deployment to a plurality of nodes in heterogeneous environments. Individual ones of the virtualization system images are configured such that once deployed, the nodes form a computer cluster having a storage pool that is shared across the nodes. When configuring the virtualization system images, information that describes the heterogeneous computing environments is accessed, and constraints pertaining the heterogeneous computing environments are reconciled in advance of configuring the different virtualization system images. A common subnet across the heterogeneous environments is established. The plurality of different virtualization system images are configured to access the common subnet once deployed. The common subnet serves as a storage I/O communication path over which a cluster-wide storage pool is implemented.

Abstract: A cluster configuration request to form a hyperconverged computing infrastructure (HCI) cluster in a cloud computing environment is processed. Based on the cluster configuration request and any other cluster specifications, a plurality of bare metal computing nodes of the cloud computing environment are configured to operate as an HCI cluster. First, a tenant-specific secure network overlay is formed on a first set of tenant-specific networking hardware resources. Then, the tenant-specific secure network overlay is used by an orchestrator to provision a second set of tenant-specific networking hardware resources. The second set of tenant-specific networking hardware resources are configured to interconnect node-local storage devices into a shared storage pool having a contiguous address space. Top-of-rack switches are configured to form a network overlay on the first set of tenant-specific networking hardware resources.

Abstract: The described technology is generally directed towards improving indexes and queries for files by indexing file directories. According to an embodiment, a system can comprise a memory and a processor that can execute the components stored in the memory. The components can comprise a data interface to couple to a database system comprising a database storing metadata describing a file system, wherein the database comprises records that correspond to ones of directories of the file system, and wherein the records comprise a field that corresponds to files logically stored in the directories of the file system. The system can further comprise an indexing component that creates an index for the records based on an index key and an analysis of the ones of the files and the directories to which the records correspond, wherein the index comprises links between instances of the index key and ones of the directories.

Abstract: A plurality of different virtualization system images are configured for deployment to a plurality of nodes in heterogeneous environments. Individual ones of the virtualization system images are configured such that once deployed, the nodes form a computer cluster having a storage pool that is shared across the nodes. When configuring the virtualization system images, information that describes the heterogeneous computing environments is accessed, and constraints pertaining the heterogeneous computing environments are reconciled in advance of configuring the different virtualization system images. A common subnet across the heterogeneous environments is established. The plurality of different virtualization system images are configured to access the common subnet once deployed. The common subnet serves as a storage I/O communication path over which a cluster-wide storage pool is implemented.

Abstract: A cluster configuration request to form a hyperconverged computing infrastructure (HCI) cluster in a cloud computing environment is processed. Based on the cluster configuration request and any other cluster specifications, a plurality of bare metal computing nodes of the cloud computing environment are configured to operate as an HCI cluster. First, a tenant-specific secure network overlay is formed on a first set of tenant-specific networking hardware resources. Then, the tenant-specific secure network overlay is used by an orchestrator to provision a second set of tenant-specific networking hardware resources. The second set of tenant-specific networking hardware resources are configured to interconnect node-local storage devices into a shared storage pool having a contiguous address space. Top-of-rack switches are configured to form a network overlay on the first set of tenant-specific networking hardware resources.

Abstract: The described technology is generally directed towards incremental aggregation of metadata for a file storage system. According to an embodiment, a system can comprise a memory and a processor that can execute the components stored in the memory. The components can comprise a scanner component that can accessing a data structure storage component that can store a first data structure, and a branch of the first data structure can comprise a node that comprises at least one descendent link to a descendant node. The scanner component can further traverse from a first node to a second node by employing a first descendent link. Further, the method comprises a data collector that can collect node data from the first node and the second node. The system can further comprise a rollup data generator to aggregate, upon occurrence of a condition, the node data, resulting in aggregated node data.

Abstract: The described technology is generally directed towards reducing the amount of data stored in a sequence of data blocks by combining deduplication and compression. According to an embodiment, a system can comprise a memory that can store computer executable components, and a processor that can execute the components stored in the memory. The components can comprise a receiver component to receive metadata describing directories in a data store, wherein the metadata comprises, for the respective ones of the directories, a descendant directory. The system can further comprise a data structure component to create a tree data structure, comprising nodes corresponding to the directories, and comprising links corresponding to the metadata of the respective ones of the directories. Further, the system, can comprise a curation component to cull non-useful portions of the metadata from the tree data structure periodically.

Abstract: The described technology is generally directed towards incremental aggregation of metadata for a file storage system. According to an embodiment, a system can comprise a memory and a processor that can execute the components stored in the memory. The components can comprise a scanner component that can accessing a data structure storage component that can store a first data structure, and a branch of the first data structure can comprise a node that comprises at least one descendent link to a descendant node. The scanner component can further traverse from a first node to a second node by employing a first descendent link. Further, the method comprises a data collector that can collect node data from the first node and the second node. The system can further comprise a rollup data generator to aggregate, upon occurrence of a condition, the node data, resulting in aggregated node data.

Abstract: The described technology is generally directed towards improving indexes and queries for files by indexing file directories. According to an embodiment, a system can comprise a memory and a processor that can execute the components stored in the memory. The components can comprise a data interface to couple to a database system comprising a database storing metadata describing a file system, wherein the database comprises records that correspond to ones of directories of the file system, and wherein the records comprise a field that corresponds to files logically stored in the directories of the file system. The system can further comprise an indexing component that creates an index for the records based on an index key and an analysis of the ones of the files and the directories to which the records correspond, wherein the index comprises links between instances of the index key and ones of the directories.

Abstract: Systems for managing firmware updates in a computing system. A computing system comprises multiple computing nodes. A plurality of computing nodes include firmware-upgradable components from multiple vendors. When upgrading the firmware of components of the computing system, a firmware management agent is invoked to interact with firmware management plug-ins through an abstraction layer. The abstraction layer translates vendor-agnostic firmware operations into vendor-specific firmware operations. The firmware management agent determines the then-current status of the firmware-upgradable components and issues a series of vendor-agnostic firmware commands to initiate firmware upgrades over the computing nodes of the computing system. The firmware management agent generates and manages a firmware update schedule to sequence or parallelize firmware updates across multiple nodes of the computing system.

Abstract: Systems for virtual memory computing systems. A set of hardware or software operational elements of a computing system performs virtualized memory paging. The operational elements serve to identify a random access memory device and at least one random access persistent memory device (RAPM) in a computing system. The random access persistent memory device is configured as a swap device that is apportioned as having at least some address space for swap. At least some of the swap address space is assigned to one or more virtualized entities in the computing system. When a page swap event is detected by the computing system, one or more of the operational elements execute one or more paging operations based on characteristics of the page swap event. The paging operations perform swap-in or swap-out of at least one page between the random access memory device and the random access persistent memory device.

Abstract: Systems for cooperative management of multiple types of memory. A method embodiment implements cooperative management of multiple types of memory among virtual machines running in a host computing system. The method commences upon identifying virtual machines and a hypervisor that runs in the host computing system. The hypervisor is configured to respond to memory allocation requests from the virtual machines. Upon receiving (a) a first memory allocation request for a first memory type having a first set of characteristics and (b) a second memory allocation request for a second memory type having a second set of characteristics, the hypervisor responds to the requestor with allocations from the first memory type and allocations from the second memory type. Different pools of memory are formed of the different types of memory devices. A multi-memory pool type combines memory devices of a first memory type and memory devices of a second memory type.

Abstract: A memory subsystem is interfaced to a CPU through memory controllers. The memory subsystem is composed of a first tier of first memory devices having a first set of performance characteristics and a second tier of second memory devices having a second set of performance characteristics that are different from the first set of performance characteristics. A content addressable memory stores the memory addresses that are used to access the first memory devices and/or second memory devices. Logic is provided that updates one or more registers or memory structures to count the frequency and timing of occurrences of the memory address accesses. Both the content addressable memory and logic can be implemented on the same semiconductor substrate. The content addressable memory may be interfaced to a random access memory that stores counters. The logic may comprise one or more state machines implemented on the same semiconductor substrate as the CPU.

Abstract: Storage device groups are formed with respect to data consistency policies and/or quantified probabilities. A method embodiment commences upon identifying a computing system having a plurality of storage devices that are accessed by a plurality of computing nodes. A user interface serves for collecting policies, data loss parameters, and data rebuild parameters. Based on the policies and/or values of the data loss parameters, and values of the data rebuild parameters, sets of storage device groups are formed to achieve particular data loss and rebuild time properties. Data storage containers such as files or virtual disks that hold persistent datasets are assigned to respective storage device groups that are appropriate to the nature of the dataset. The objective pertaining to an acceptable likelihood of data loss as well as the objective of an acceptable time for rebuild are achieved as a result of assignments of certain storage devices into a group.

Abstract: Systems for enforcing virtualization quality-of-service policies to manage multi-tiered swap spaces. A method commences upon identifying a first storage area in a first data storage device of a first type and identifying a second storage area in a second data storage device of a second type. A swap space that comprises at least a portion of the first storage area and at least a portion of the second storage area is configured for use by an operating system or by a hypervisor or container or by a virtual machine or any other virtualized entity. An initial portion of the first storage area is allocated. Swap space events associated with the swap space are detected, at which point the virtualization quality-of-service policies are applied to the swap space event to determine one or more swap space management operations. The determined swap space management operations are executed over the multi-tiered swap space.

Abstract: Systems for management of a large computing cluster. A set of computing nodes within the cluster are identified. The identified nodes are to be reimaged with an operating system image and parameters. One or more reimaging algorithms in the form of computer code are stored in a networked storage device within a storage pool that comprises the networked storage device and a plurality of local storage devices that correspond to respective individual ones of the set of computing nodes. An agent that can execute the reimaging algorithm code is configured to run on any one of the set of computing nodes, wherein the agent is further configured to retrieve reimaging data from a storage device that is within the storage pool. An agent running on a leader node initiates reimaging of a second node. The second node initiates reimaging of a third node. The third node reimages the leader node.

Abstract: Systems for management of a large computing cluster. A set of computing nodes within the cluster are identified. The identified nodes are to be reimaged with an operating system image and parameters. One or more reimaging algorithms in the form of computer code are stored in a networked storage device within a storage pool that comprises the networked storage device and a plurality of local storage devices that correspond to respective individual ones of the set of computing nodes. An agent that can execute the reimaging algorithm code is configured to run on any one of the set of computing nodes, wherein the agent is further configured to retrieve reimaging data from a storage device that is within the storage pool. An agent running on a leader node initiates reimaging of a second node. The second node initiates reimaging of a third node. The third node reimages the leader node.

Abstract: Systems for computing cluster management. A boot media source node is connected to a computing cluster. Boot image patching operations commence upon receiving, by the boot media source node, communications from at least one computing node of a plurality of computing nodes of the computing cluster. Such a communication comprises an indication of an address range of a requested segment of a boot image. The boot media source node retrieves a patch to be applied over the requested segment. The overlap range of the retrieved patch and the requested segment are calculated. The boot media source node processes the patch by allocating a segment in volatile memory of the server node, and forming an in-memory patched segment without storing the patched segment to non-volatile memory. The in-memory patched segment is delivered to the requestor and the boot media source node receives next segments from the same or different computing nodes.