Abstract: A method for servicing a section of a first flow line of a redundant flow line system with a second flow line in a closed-loop liquid cooling system. The method can include draining liquid from the first flow line through a liquid transfer assembly and servicing the section of the first flow line. The method can also include transferring liquid from the second flow line to the first flow line through the liquid transfer assembly and decoupling the liquid transfer assembly from the first flow line and the second flow line. The method can also include coupling the liquid transfer assembly to and between the first flow line and the second flow line.

Abstract: Systems and methods take into account the criticality of workloads, the warranty needs of workloads, the warranty available time, and the lifetime of a workload to provide an optimal solution that ensures servers are used to highest extent. The warranty health of servers is computed and categorized as critical, warning, or healthy based on the number of days remaining in warranty. Workloads are tagged as short-term or long-term workloads. Workloads are also classified based on criticality. The quarantine mode for proactive high availability of servers is divided into multiple modes, including a long-time, critical-workload quarantine mode, a critical-workload quarantine mode, and a standard quarantine mode. Servers that are in quarantine mode are assigned new workloads based upon the warranty health, workload term, and workload criticality.

Abstract: An indexing technique provides an index data structure for efficient retrieval of a snapshot from a long-term storage service (LTSS) of an archival storage system. The snapshot is generated from typed data of a logical entity, such as a virtual disk (vdisk). The data of the snapshot is replicated to a frontend data service of the LTSS sequentially and organized as one or more data objects for storage by a backend data service of LTSS in an object store of the archival storage system. Metadata associated with the snapshot (i.e., snapshot metadata) is recorded as a log and persistently stored on storage media local to the frontend data service. The snapshot metadata includes information describing the snapshot data, e.g., a logical offset range of a snapshot of the vdisk and, thus, is used to construct the index data structure. Notably, construction of the index data structure is deferred until after the entirety of the snapshot data has been replicated and received by the frontend data service.

Abstract: Systems and methods provide a logical-physical warranty that is applied to nodes at a logical grouping level, such as a cluster. A logical warranty is associated with the nodes in the logical group or cluster in addition to each node's original individual warranty. The logical warranty stretches the expiration dates for individual warranties to a worst-case date inside the logical group. Customers build, teardown and extend the clusters, and the logical warranty is assigned to nodes in the cluster. The logical warranty is associated with a cluster of a defined size, such as a number of nodes expected, which can be expanded in the future as needed. The logical warranty ensures that there is uniform Service Level Agreement (SLA) for the nodes in the cluster during the warranty lifetime thereby simplifying the support for the cluster.

Abstract: A disclosed workload distribution method determines a yield index for each microservice associated with a containerized application executing on a potentially heterogeneous cluster information handling systems. Each microservice is then assigned to one of N priority categories based on its yield index, where three is an acceptable, but not exclusive, value of N. Resource configuration profiles are maintained for each of the priority categories. Each resource configuration profile assigns a resource configuration to each microservice. An information handling resource associated with a particular microservice is configured in accordance with the resource configuration assigned to the particular microservice by a particular resource configuration profile corresponding to the yield index. In this manner, workloads can be assigned and resources configured in accordance with the containerized application's priorities as exposed by the value indices.

Abstract: Systems and methods are disclosed for warranty recommendations for users based upon warranty selections of peer users. The users are clustered into peer groups based upon industry or market segment based upon user data including primary variables, such as workload type data and market segment data, and secondary variables, such as virtual machine size or number, cluster size, cost, and downtime. New users are matched to a top similar user within their peer group based upon a vector distance, wherein the vector comprises the primary and secondary variables. A current warranty of the top similar user is recommended to the new user. Warranty changes by members of a peer group cause trigger an updated ranking of the peer group warranties. Expert user comments and rankings are used to generate expert user recommendations. A cost-based impact assessment may also be used for warranty recommendations by highlighting favorable and unfavorable warranty properties.

Abstract: A system for allocating resources across equipment that operate to serve one or more loads of a building. The system includes one or more memory devices storing instructions that cause one or more processors to receive operational data defining at least one of planned loads to be served by the equipment or utility rates for one or more time steps within a simulation period, determine whether the operational data define the planned loads or the utility rates for each time step within the simulation period, and in response to a determination that the operational data do not define the planned loads or the utility rates for each time step within the simulation period, identify one or more time steps for which the planned loads or the utility rates are not defined and initiate an action to define the planned loads or the utility rates for the identified time steps.

Abstract: The use of multiple horizon optimization for vehicle dynamics and powertrain control of a vehicle is provided. Long horizon optimization for a trip of the vehicle is performed, and an optimal value function is determined. Data is received from powertrain and/or connectivity features from one or more of components of the vehicle. Short horizon optimization for the trip is performed using a rollout algorithm, the optimal value function, and the received data. The operation of the vehicle is adjusted using results of the short horizon optimization.

Abstract: The techniques described herein enable a virtual private network (VPN) gateway to select a VPN connection, from multiple VPN connections established between a network VPN gateway and a remote VPN gateway, based on performance factors such as throughput. A system may measure throughput in megabytes per second (Mbps). More specifically, a VPN gateway (e.g., a remote VPN gateway or a network VPN gateway) can configure a routing preference that selects a VPN connection that is more performant based on a cryptographic algorithm that is used for the VPN connection. The VPN gateway can update the routing preference to select an alternative VPN connection when the performance of the VPN connection suffers.

Abstract: Methods, systems and computer program products for high-availability computing. In a computing configuration comprising a primary node, a first backup node, and a second backup node, a particular data state is restored to the primary node from a backup snapshot at the second backup node. Firstly, a snapshot coverage gap is identified between a primary node snapshot at the primary node and the backup snapshot at the second backup node. Next, intervening snapshots at the first backup node that fills the snapshot coverage gap are identified and located. Having both the backup snapshot from the second backup node and the intervening snapshots from the first backup node, the particular data state at the primary node is restored by performing differencing operations between the primary node snapshot, the backup snapshot from the second backup node, and the intervening snapshots of the first backup node.

Abstract: In one or more embodiments, one or more systems, one or more methods, and/or one or more processes may: receive performance information for a base workload; determine multiple threshold values of multiple storage media layers of each IHS of a storage cluster based at least on the performance information for the base workload and multiple inventory information respectively associated with multiple storage media layers of each IHS of the storage cluster; receive multiple condition values respectively associated with the multiple storage media layers of an IHS of the storage cluster; determine that a condition value of the multiple condition values associated with a storage media layer of the multiple storage media layers is at or below a threshold value of the multiple threshold values associated with the storage media layer of the multiple storage media layers; and reduce a storage workload of a specific IHS of the storage cluster.

Abstract: Exemplary methods, apparatuses, and systems include a file system process inserting a first key/value pair and a second key/value pair into a first tree. The second key is a duplicate of the first key and the value of the second key/value pair is an operation changing the value. In response to a request for a range of key/value pairs, the process reads the second key/value pair and inserts it in a second tree. The process reads the first pair and determines, while inserting the first pair in the second tree, that the second key is a duplicate of the first key. The file system process determines an updated value of the first value by applying the operation in the second value to first value. The file system operation updates the second key/value pair in the second tree with the updated value and returns the requested range of key/value pairs.

Abstract: Relay functionality may be provided. A network device may receive a response packet and may determine that one of Option-82 and Option-18 information is not present in the received response packet. Next, in response to determining that one of Option-82 and Option-18 information is not present in the received response packet, a database may be queried for information associated with the response packet. Then, based on the information associated with the response packet, the response packet may be sent to a client device associated with the response packet.

Abstract: The techniques described herein enable the establishment of two simultaneous virtual private network (VPN) connections between a VPN gateway and a VPN client. The system is configured to update a routing table advertised to network resources when a VPN server instance fails and/or is taken offline. When a first VPN server instance fails and/or is taken offline, the first VPN server instance releases a claim of ownership on its range of IP addresses. After this release occurs, the second VPN server instance is configured to claim ownership of the range of IP addresses that used to be owned by the first VPN server instance. This updated claim of ownership is captured in an updated routing table that can then be advertised to the network resources. Consequently, the network resources use this updated routing table to correctly determine which VPN server instance to send data intended for the VPN client.

Abstract: The techniques described herein enable the establishment of two simultaneous virtual private network (VPN) connections for a VPN client operating on a remote computing device. The VPN client can establish first VPN connection with a first VPN server instance of a VPN gateway and a second VPN connection with a second VPN server instance of the VPN gateway. To establish two simultaneous VPN connections, the VPN client is configured to create and/or use two Transmission Control Protocol (TCP) sockets. In one example, a first VPN connection can be a primary VPN connection and a second VPN connection can be a dormant VPN connection configured as a backup in case of a service interruption with the first VPN connection. In another example, a data flow can be split across the first and second VPN connections, or alternate between using the first and second VPN connections, based on performance parameters.

Abstract: Methods, apparatus, and processor-readable storage media for learning machine behavior related to install base information and determining event sequences based thereon are provided herein. An example computer-implemented method includes parsing data storage information based at least in part on parameters related to install base information comprising temporal parameters and event-related parameters; formatting the parsed set of data storage information into a parsed set of sequential data storage information compatible with a neural network model; training the neural network model using the parsed set of sequential data storage information and additional training parameters; predicting, by applying the trained neural network model to the parsed set of sequential data storage information, a future data unavailability event and/or a future data loss event; and outputting an alert based at least in part on the predicted future data unavailability event and/or predicted future data loss event.

Abstract: As described herein, a system, method, and computer program are provided for AWS autoscaling of Tuxedo systems. In use, an AWS cloud based deployment of a Tuxedo system is identified. Further, autoscaling of the Tuxedo system is provided in accordance with an autoscaling configuration of the AWS, using a Tuxedo registrar that maps AWS EC2 DNS names or internet protocol (IP) addresses with Tuxedo-compliant names capable of being used by the Tuxedo system.

Abstract: A technique creates a compact state of snapshot metadata and associated selected snapshots that are frequently used and maintained in memory of a node of a cluster to facilitate processing of workflow operations associated with a logical entity in a disaster recovery (DR) environment. The compact state represents a minimal subset of snapshot metadata that is frequently used to perform operations in accordance with the DR workflow operations. In addition, metadata associated with the progress of the DR workflow operations processed by the node is periodically consolidated within the compact state. Illustratively, the selected frequently used snapshots of the logical entity include (i) a recently created snapshot; (ii) one or more reference snapshots; (iii) a snapshot scheduled for replication; and (iv) any snapshot that is queued for a current or future-scheduled operation.

Abstract: Embodiments described herein are related to a method of scanning a B-tree. For example, a method comprises receiving a scan request to scan a B-tree having a plurality of levels, each level comprising one or more nodes, wherein for each of one or more levels of the plurality of levels, nodes are grouped into groups, where nodes of any given group are stored across sequential disk blocks. The method further comprises generating a queue for each level of the B-tree. For each queue, the method further comprises loading into memory a next group of nodes based upon determining a storage location of a node of the next group of nodes.

Abstract: The present disclosure relates to platform configured for executing and rendering templates to enable automation of control and data exploration across systems in an interactive and non-interactive mode. Initially, the platform is configured to add template to an exploration either on user request or system driven request and execute the template by extracting execution model associated with the template. Further, the target system is configured to run the execution plan in interactive mode wherein the user may provide inputs or non-interactive mode wherein the target system is configured to run the execution plan without user inputs. The target system is further configured to receive data generated by the target systems in response to the operation executed by the execution engine. On receiving the data from target systems in the data store, the target system is configured to visualize the data on the template rendered on the GUI.