Abstract: An information handling system includes a shared device, first and second compute nodes, and a chassis management controller. The first compute node includes a first management controller, which initiates a firmware update for firmware in the shared device. The first management controller detects that that the firmware update is complete. In response to the firmware update being completed, the management controller sends rollback information for the firmware to the chassis controller. The chassis controller stores the rollback information as a rollback image within a storage location of a memory. The chassis controller further sends the rollback information to the second compute node. The second compute node includes a second management controller, which in turn receives the rollback information from the chassis controller, and updates the rollback information within the second compute node.

Abstract: An information handling system includes a processor, and a system memory device to store program instructions executable by the processor. The processor mounts a boot media, and executes the boot media. During the executing of the boot media, the processor fetches a firmware inventory for the information handling system and generates a firmware compliance report to the firmware inventory. Based on the firmware compliance report, the processor generates a firmware download capsule for firmware updates for the firmware inventory. Based on the firmware download capsule, the processor downloads supported firmware update packages.

Abstract: An information handling system includes a shared device, first and second compute nodes, and a chassis management controller. The first compute node includes a first management controller, which initiates a firmware update for firmware in the shared device. The first management controller detects that that the firmware update is complete. In response to the firmware update being completed, the management controller sends rollback information for the firmware to the chassis controller. The chassis controller stores the rollback information as a rollback image within a storage location of a memory. The chassis controller further sends the rollback information to the second compute node. The second compute node includes a second management controller, which in turn receives the rollback information from the chassis controller, and updates the rollback information within the second compute node.

Abstract: An information handling system includes a shared device, first and second compute nodes, and a chassis management controller. The first compute node includes a first management controller, which initiates a firmware update for firmware in the shared device. The first management controller detects that that the firmware update is complete. In response to the firmware update being completed, the management controller sends rollback information for the firmware to the chassis controller. The chassis controller stores the rollback information as a rollback image within a storage location of a memory. The chassis controller further sends the rollback information to the second compute node. The second compute node includes a second management controller, which in turn receives the rollback information from the chassis controller, and updates the rollback information within the second compute node.

Abstract: A service enables a command that refers to a file system object using a hierarchical namespace identifier to be executed against the file system object in a flat namespace. The service selectively distributes the command to one of a plurality of name resolution nodes based on a directory name included in the hierarchical namespace identifier. The identified node resolves the directory name to a flat namespace identifier that is used to execute the command against the flat namespace. After communicating with at least one storage node to resolve a directory name, each name resolution node stores a mapping of the directory name to the corresponding flat namespace identifier in a cache, so that subsequent resolutions of that directory name may be performed more efficiently. Cache entries may be invalidated when an operation occurs that impacts the relevant mapping and/or based on system considerations such as cache expiry.

Abstract: An information handling system includes a shared device, first and second compute nodes, and a chassis management controller. The first compute node includes a first management controller, which initiates a firmware update for firmware in the shared device. The first management controller detects that that the firmware update is complete. In response to the firmware update being completed, the management controller sends rollback information for the firmware to the chassis controller. The chassis controller stores the rollback information as a rollback image within a storage location of a memory. The chassis controller further sends the rollback information to the second compute node. The second compute node includes a second management controller, which in turn receives the rollback information from the chassis controller, and updates the rollback information within the second compute node.

Abstract: Methods, systems, and computer programs are presented for providing file system functions on a cloud storage system based on blob storage. A cloud storage system comprises storage clusters, and each storage cluster comprises a plurality of storage nodes (each including a partition layer that stores data in blobs organized within containers, and a stream layer for streaming blob data), a hierarchical namespace service for implementing file system functions on the data stored in the blobs and, a front end layer for processing user requests to access and manage data stored on the blobs. The file system functions include flat namespace functions and hierarchical namespace functions. Further, the front end layer accesses the partition layer to access the blobs based on addresses of blobs and accesses the hierarchical namespace service to identify the blobs.

Abstract: Methods, systems, and programs provide for executing distributed transactions in a cloud storage system with a hierarchical namespace. One method includes receiving a request with operations to be executed atomically. Further, nodes are identified for executing the operations, each node having a respective clock and having at least part of a transactions table for controlling updates to entities. Each clock is one of a loosely-synchronized, a strictly-synchronized clock, a logical, or a physical clock. Additionally, the nodes process the operations, which includes setting a commit timestamp (CS) to a value of the clock in the node if the node is a first node in the processing. One node coordinates the transactions, and may be one of the nodes executing transactions. If the clock in the node is less than a current value of the CS, the node waits for the clock to reach the current value of the CS and the CS is updated.

Abstract: A service enables a command that refers to a file system object using a hierarchical namespace identifier to be executed against the file system object in a flat namespace. The service selectively distributes the command to one of a plurality of name resolution nodes based on a directory name included in the hierarchical namespace identifier. The identified node resolves the directory name to a flat namespace identifier that is used to execute the command against the flat namespace. After communicating with at least one storage node to resolve a directory name, each name resolution node stores a mapping of the directory name to the corresponding flat namespace identifier in a cache, so that subsequent resolutions of that directory name may be performed more efficiently. Cache entries may be invalidated when an operation occurs that impacts the relevant mapping and/or based on system considerations such as cache expiry.

Abstract: Methods, systems, and apparatuses are provided for a storage system that implements a hierarchical namespace service. A storage system includes a plurality of physical nodes and a plurality of sets of virtual nodes. Each set of virtual nodes is managed by a corresponding physical node. Each virtual node is configured to manage a respective set of directory blocks. Each directory block is a respective partition of a storage namespace and is managed by a corresponding single virtual node. Each virtual node maintains a directory block map. The directory block map maps file system object names in a hierarchical namespace to entity block identifiers in the flat namespace for entity blocks (files and folders) stored in directories corresponding to the managed set of directory blocks. Load balancing may be performed by moving virtual nodes between physical nodes, and by splitting directory blocks.

Abstract: A service enables a command that refers to a file system object using a hierarchical namespace identifier to be executed against the file system object in a flat namespace. The service selectively distributes the command to one of a plurality of name resolution nodes based on a directory name included in the hierarchical namespace identifier. The identified node resolves the directory name to a flat namespace identifier that is used to execute the command against the flat namespace. After communicating with at least one storage node to resolve a directory name, each name resolution node stores a mapping of the directory name to the corresponding flat namespace identifier in a cache, so that subsequent resolutions of that directory name may be performed more efficiently. Cache entries may be invalidated when an operation occurs that impacts the relevant mapping and/or based on system considerations such as cache expiry.

Abstract: Systems and methods provide a storage controller with write-back caching capabilities that may be used during scenarios where the storage controller is required to provide write-through caching, and thus unable to utilize internal cache memory for write-back caching. The storage controller utilizes an allocation of persistent memory that is made available by the host IHS (Information Handling System), to which the storage controller is coupled. In scenarios where the storage controller is required to provide write-through caching, the storage controller may be configured to route received write data to the allocated host memory. In this manner, the data integrity provided by write-through operations is maintained, while also providing the host IHS with the speed of write-back operations. When ready to store the write data, the storage controller may request the flushing of write data from the allocated host memory.

Abstract: In accordance with embodiments of the present disclosure, a method may be implemented to respond to receiving data A to be stored in a storage system that includes a plurality of N spans, each including a plurality of M drives. The method may include performing data storing operations. The data storing operations may include storing the data A in N portions across the plurality of spans, generating a Za parity based on an XOR operation applied to the N portions of the data A, storing the Za parity in N?1 portions across a subset of the plurality of spans, determining a Zap parity based on an XOR operation applied to the N?1 portions of the Za parity, and storing the Zap parity.

Abstract: A service enables a command that refers to a file system object using a hierarchical namespace identifier to be executed against the file system object in a flat namespace. The service selectively distributes the command to one of a plurality of name resolution nodes based on a directory name included in the hierarchical namespace identifier. The identified node resolves the directory name to a flat namespace identifier that is used to execute the command against the flat namespace. After communicating with at least one storage node to resolve a directory name, each name resolution node stores a mapping of the directory name to the corresponding flat namespace identifier in a cache, so that subsequent resolutions of that directory name may be performed more efficiently. Cache entries may be invalidated when an operation occurs that impacts the relevant mapping and/or based on system considerations such as cache expiry.

Abstract: Methods, systems, and apparatuses are provided for a storage system that implements a hierarchical namespace service. A storage system includes a plurality of physical nodes and a plurality of sets of virtual nodes. Each set of virtual nodes is managed by a corresponding physical node. Each virtual node is configured to manage a respective set of directory blocks. Each directory block is a respective partition of a storage namespace and is managed by a corresponding single virtual node. Each virtual node maintains a directory block map. The directory block map maps file system object names in a hierarchical namespace to entity block identifiers in the flat namespace for entity blocks (files and folders) stored in directories corresponding to the managed set of directory blocks. Load balancing may be performed by moving virtual nodes between physical nodes, and by splitting directory blocks.

Abstract: Methods, systems, and computer programs are presented for providing file system functions on a cloud storage system based on blob storage. A cloud storage system comprises storage clusters, and each storage cluster comprises a plurality of storage nodes (each including a partition layer that stores data in blobs organized within containers, and a stream layer for streaming blob data), a hierarchical namespace service for implementing file system functions on the data stored in the blobs and, a front end layer for processing user requests to access and manage data stored on the blobs. The file system functions include flat namespace functions and hierarchical namespace functions. Further, the front end layer accesses the partition layer to access the blobs based on addresses of blobs and accesses the hierarchical namespace service to identify the blobs.

Abstract: Methods, systems, and programs provide for executing distributed transactions in a cloud storage system with a hierarchical namespace. One method includes receiving a request with operations to be executed atomically. Further, nodes are identified for executing the operations, each node having a respective clock and having at least part of a transactions table for controlling updates to entities. Each clock is one of a loosely-synchronized, a strictly-synchronized clock, a logical, or a physical clock. Additionally, the nodes process the operations, which includes setting a commit timestamp (CS) to a value of the clock in the node if the node is a first node in the processing. One node coordinates the transactions, and may be one of the nodes executing transactions. If the clock in the node is less than a current value of the CS, the node waits for the clock to reach the current value of the CS and the CS is updated.

Abstract: Methods, systems, and computer programs are presented for providing multi-protocol access to a cloud storage system. One method includes an operation for providing a first application programming interface (API), by a cloud storage system that stores data in blobs organized within containers, and a second API, where the APIs provide operations for a flat namespace (FN) and a hierarchical namespace (HN) for accessing data. FN is for accessing data based on account, container, and blob and the HN is for accessing data based on account, directory, and file. When a command is received for FN, the command is performed utilizing containers and blob identifiers. When the command is received for HN, the hierarchical namespace service is accessed to translate directories and files included to one or more blob identifiers. Further, a response is sent to the user device.

Abstract: In accordance with embodiments of the present disclosure, a method may be implemented to respond to receiving data A to be stored in a storage system that includes a plurality of N spans, each including a plurality of M drives. The method may include performing data storing operations. The data storing operations may include storing the data A in N portions across the plurality of spans, generating a Za parity based on an XOR operation applied to the N portions of the data A, storing the Za parity in N-1 portions across a subset of the plurality of spans, determining a Zap parity based on an XOR operation applied to the N-1 portions of the Za parity, and storing the Zap parity.

Abstract: Systems and methods provide a storage controller with write-back caching capabilities that may be used during scenarios where the storage controller is required to provide write-through caching, and thus unable to utilize internal cache memory for write-back caching. The storage controller utilizes an allocation of persistent memory that is made available by the host IHS (Information Handling System), to which the storage controller is coupled. In scenarios where the storage controller is required to provide write-through caching, the storage controller may be configured to route received write data to the allocated host memory. In this manner, the data integrity provided by write-through operations is maintained, while also providing the host IHS with the speed of write-back operations. When ready to store the write data, the storage controller may request the flushing of write data from the allocated host memory.