Abstract: A critical executable image is used to instantiate an instance on a computing device. The executable image is further saved on the storage device. In response to a failure of the instance, the instance may be restored from the locally stored executable image. The executable image may be of a container and corresponding application image. The computing device may receive a specification, e.g., container specification, to instantiate the instance, the specification including an annotation instructing the computing device to locally store the executable image after instantiation.

Abstract: A method and system for automatically triggering alerts for at least one anomaly are disclosed. The method includes receiving a plurality of data logs associated with a plurality of applications. Next, the method includes trimming the plurality of data logs into a set of data logs and comparing the set of data logs with each of a plurality of previously stored set of data logs. Next, the method includes identifying a set of new events associated with the at least one anomaly. Next, the method includes analyzing the set of new events to identify a pattern associated with the at least one anomaly and displaying, via a display, the pattern associated with the at least one anomaly to at least one entity. Thereafter, the method includes automatically triggering the alerts for the at least one anomaly based on the identification of the pattern associated with the at least one anomaly.

Abstract: A storage method includes: calculating M check blocks of N first data blocks based on a first erasure coding (EC) technology; respectively storing the N first data blocks and the M check blocks of the N first data blocks into (N+M) storage nodes in a storage system; updating the first EC technology to a second EC technology; calculating R check blocks of S second data blocks based on the second EC technology, where S is greater than N, a ratio of S to R is greater than a ratio of N to M, S, R, N, and M are all positive integers, and the second data block is a data block received after the first EC technology is updated to the second EC technology.

Abstract: The subject technology initiates a reinstallation process of a key-value storage device and locking the key-value storage device. The subject technology performs a bootstrap process for a blob manager and a blob worker. The subject technology performs a restoration process of a storage server. The subject technology applies a set of mutation logs to the storage server. The subject technology unlocks the key-value storage device and enabling network traffic for the key-value storage device.

Abstract: A method and a system for forecasting technology-related incidents and/or failures using artificial intelligence models and machine learning techniques are provided. The method includes: receiving a data set that relates to a system; analyzing the data set to identify a potential problem with respect to the system; and generating a report that includes a forecast that relates to the identified potential problem. The analysis is performed by applying an artificial intelligence (AI) algorithm that is trained by using historical data that relates to incidents and failures associated with the system.

Abstract: Systems and methods are provided for implementing improved root cause analysis (“RCA”)-based node recovery. After instructing a node to enter a debug mode and based on a determination that an expected response timeout duration has elapsed, a controller instructs the node to enter a system management mode (“SMM”), and exposes a shared buffer to an SMM handler of the node. The shared buffer includes instructions for the SMM handler to set a trap flag in a saved state area of an operating system (“OS”) of the node and to use a resume execution instruction after setting the trap flag. The trap flag causes the OS to transfer control of problematic code to a trap handler, which performs operations or calls a hypervisor for a virtual machine extension (“VMX”) root mode depending on whether the problematic code execution occurs in a non-maskable interrupt (“NMI”) handler.

Abstract: Systems and methods for assessing display health in response to accidents are described. In some embodiments, an Information Handling System (IHS) may include an Embedded Controller (EC) and a memory coupled to the EC, where the memory comprises program instructions that, upon execution by the EC, cause the IHS to initiate an integrated display's Built-In-Self-Test (BIST) in response to a determination that the IHS suffered an accident.

Abstract: Disclosed are a firmware detection system and method for a recoverable fault, a storage medium, and a server. The method includes: acquiring target fault information stored in a fault register, and transmitting the target fault information to a baseboard management controller (BMC); parsing the target fault information by the BMC, and determining a fault type; controlling, by the BMC, a virtual external device to transmit a target heartbeat request to a server operating system according to a preset transmission period when the fault type of the target fault information is a recoverable fault, and receiving response data fed back by the server operating system and determining, by the BMC, that the server operating system has a crash if detecting that the response data fed back by the operating system is interrupted within a preset time period, and determining a faulty component in the server according to the target fault information.

Abstract: Disclosed is a fail-closed conformance control layer for machine-assisted decision artifacts. The system generates replay-verifiable receipts that commit to a canonical artifact digest, evidence and snapshot identifiers, assumptions, toolchain identifiers, and a policy pack identifier and policy version digest. A deterministic validator evaluates a receipt under the versioned policy pack to output PASS, FAIL, or HOLD with reason codes from a reason-code registry, including time-stamped modeled-variability codes. Downstream side effects are gated in a control path and permitted only on PASS; otherwise they are withheld or routed to remediation or human review. The system may emit portable conformance packs and revalidate receipts over time to detect drift and manage a certification lifecycle.

Abstract: A system and method for providing automated event of interest detection and reporting for software testing. The technology described herein uses natural language processing to identify events of interest based on natural language included in log files messages and/or telemetry event items of software under test. Identified events of interest are reported to one or more downstream services. In some examples, events of interest are mapped to action sequences of interest that can be replayed to reproduce events of interest without requiring event of interest criteria to be defined. In some examples, events of interest are reported to a health/status dashboard and/or a listener that responds to reported events of interest.

Abstract: Apparatuses and techniques for implementing usage-based-disturbance alert signaling are described. The technology allows usage-based-disturbance (UBD) alerts to be externally communicated from a memory device without a dedicated external interface. Rather, UBD alerts are combined with memory error/alert signals and communicated on a shared alert-related interface. UBD tracking occurs at the memory bank level, with corresponding independent UBD alert signals. These signals are efficiently combined to generate an overall UBD alert. A temporary backoff signal is generated when an overall UBD alert is sent. The backoff signal ensures requisite external timing parameters are met while allowing the individual memory banks to generate persistent UBD alerts.

Abstract: Disclosed are various embodiments for performing fault injection tests on services, systems, or applications while they are under load. First, a load level for an application is identified. Then, load traffic is sent to the application, wherein the load traffic causes the application to operate at the load level. Then, a fault injection test is performed on the application while the application is at the load level.

Abstract: A method includes generating a second encoded data slice of a second subset of encoded data slices of a set of encoded data slices, where the second subset of encoded data slices is not currently stored in a set of storage units of the storage network, where the set of encoded data slices include a first subset of encoded data slices that is stored in the set of storage units and includes at least a decode threshold number of encoded data slices of the set of encoded data slices, and where a first encoded data slice of the first subset requires rebuilding. The method further includes sending the second encoded data slice to the set of storage units for storage therein, where when the second encoded data slice is stored, the second encoded data slice no longer included in the second subset of encoded data slices.

Abstract: A technique includes receiving information relating to wear of computer nodes. Based on the information relating to the wear, the technique includes ranking the computer nodes according to respective expected remaining lifetimes of the computer nodes. The technique includes, responsive to an event that corresponds to at least one of a spare computer node being added to the system or a given computer node being removed from the system, reconfiguring the system based on the ranking.

Abstract: A method, system, and computer program product for estimating propagation time for an injected fault are configured to: determine normal execution times of respective services in a call graph of an application; determine normal execution times of respective network communications between ones of the services; determine faulty execution times of respective ones of the services; and generate a propagation time for a particular type of fault injected at a particular fault injection location in the call graph based on the determined normal execution times of respective services, the determined normal execution times of respective network communications, and the determined faulty execution times of respective ones of the services.

Abstract: Embodiments described herein provide methods and apparatuses for selecting Nnext Fault Management Models, FMMs, where Nnext is an integer value, to run at an edge site in a cloud system during an ith time period. A method in a Fault Management System, FMS includes: in a deployment agent, DA: selecting the Nnext FMMs from a first set of FMMs based at least in part on respective probability functions associated with each of the first set of FMMs, wherein each respective probability function indicates how likely a fault associated with the respective FMM is to occur as a function of time; and initiating running of the Nnext FMMs at the edge site during the ith time period.

Abstract: Embodiments provide diagnostic operations on user input devices of an Information Handling System (IHS). Sensor capabilities of the IHS are used to detect when a user of the IHS is not in proximity to the IHS. Upon detecting when the user is not in proximity to the IHS, monitoring is initiated for inputs detected by one or more of the user input devices of the IHS. When the monitoring detects an input to a first user input device while the user is not in proximity to the IHS, diagnostics are initiated to identify whether the detected input is a spurious event, or results from a fault in the first user input device. The diagnostics are exited upon detecting the user in proximity to the IHS and faults identified by the diagnostics are reported to the user.

Abstract: A method of verifying processing logic of a graphics processing unit receives a test task including a predefined set of instructions for execution on the graphics processing unit, the predefined set of instructions being configured to perform a predetermined set of operations on the graphics processing unit when executed for predefined input data. In a test phase, the test task is processed by executing the predefined set of instructions for the predefined input data first and second times at the graphics processing unit so as to, respectively, generate first and second outputs. A fault signal is raised if the first and second outputs do not match.

Abstract: A data management method may include receiving a use case, and receiving a configuration specific to the use case associated with an item type having a plurality of attributes. The configuration may define a target data store, a subset of the plurality of attributes associated with the use case, and a subset of optimal data sources from a plurality of available data sources each configured to provide one or more attributes within the subset of the plurality of attributes. The data management method may further include, based on the configuration, accessing, from the subset of optimal data sources, values corresponding to the subset of the plurality of attributes, and storing the values in the target data store.

Abstract: Methods and systems for managing a data processing system are disclosed. A data processing system may detect one or more actions being taken by a user to resolve a current or predicted issue of the data processing system. Based on the detection, the data processing system may generate predictive implications to notify and/or alert the user of the implications (e.g., consequences) of these actions. These predictive implications may be used (e.g., by the user or by the data processing system itself) to advantageously prevent further, uninformed and unintended, complications to the data processing system.