Various methods, systems, and use cases for a stable and automated transformation of a networked computing system are provided, to enable a transformation to the configuration of the computing system (e.g., software or firmware upgrade, hardware change, etc.). In an example, automated operations include: identifying a transformation to apply to a configuration of the computing system, for a transformation that affects a network service provided by the computing system; identifying operational conditions used to evaluate results of the transformation; attempting to apply the transformation, using a series of stages that have rollback positions when the identified operational conditions are not satisfied; and determining a successful or unsuccessful result of the attempt to apply the transformation. For an unsuccessful result, remediation may be performed to the configuration, with use of one or more rollback positions; for a successful result, a new restore state is established from the completion state.

Managing microservice changes and performing related analytics can include generating a plurality of process instance representations. Each process instance representation can be generated based on a corresponding process path that comprises an ordered sequence of operations that are performed by a process using multiple microservices. A microservices network representation can be constructed based on the plurality of process instance representations, each element of the microservices network corresponding to an interface between a pair of the microservices. Based on the microservices network representation, a relative frequency can be determined for each of the microservices, each relative frequency corresponding to a likelihood that a change in a microservice will affect the performance of at least one process using at least one of the microservices.

Example distributed storage systems, replication state engines, and methods manage replication state for guaranteed replication between data stores. An object data store may store data objects that have been determined for deletion and rendered inaccessible to a client application. A replication state may be queried for deleted data objects and, if the replication state indicates that replication to another object data store is incomplete, physical deletion may be delayed until the replication state indicates that replication is complete and the data object may be physically deleted.

Various embodiments disclosed herein are related to a non-transitory computer readable storage medium. In some embodiments, the medium includes instructions stored thereon that, when executed by a processor, cause the processor to detect, on a server, a first symptom observable on a first one or more clusters. In some embodiments, the first symptom is indicative of an issue. In some embodiments, the instructions cause the processor to trigger additional data collection by a plurality of edge processing units for the first one or more of clusters, detect, in a second one or more clusters within the first one or more clusters, a second symptom indicative of the issue, and generate a remediation action for a third one or more clusters having the first symptom and the second symptom. In some embodiments, the second one or more clusters include the third one or more clusters.

An information processing apparatus includes one or more units, wherein the one or more units include a unit controller, the unit controller includes a first sub-system and a second sub-system, and in a case where the first sub-system cannot communicate with the second sub-system when the information processing apparatus is booted, the first sub-system overwrites, with a recovery program, a program of the second sub-system stored in a memory in which the program of the second sub-system is stored.

A digital signal processor, a digital signal processing (DSP) system, and a method for accessing external memory space are disclosed. The digital signal processor may include: a digital signal processing (DSP) core; and a program port and a data port which are connected to the DSP core and configured to access an external memory, where the program port and the data port are respectively configured to communicate with a memory management unit configured for management of an access address.

Examples described herein are generally directed to backing up and restoring of container clusters. According to an example, the conventional tight coupling between namespaces and tenants is eliminated by providing within a container platform a tenant abstraction for each tenant of the container platform that shares resources of a container cluster. The tenant abstraction for a given tenant includes information indicative of a subset of namespaces of the container cluster assigned to the given tenant. Responsive to receipt via a user interface of the container platform of a request to backup a particular tenant of the container platform: the container platform determines the subset of namespaces assigned to the particular tenant; and for each namespace, causes a namespace-level backup/recovery tool to backup object data for the namespace within a backup location, and backup data associated with persistent volume claims for each unit of cluster replication within the namespace.

Techniques and mechanisms for supporting machine check functionality with a handler which is implemented in firmware. In an embodiment, a processor executes first firmware code to implement a machine check event (MCE) detector. The MCE detector detects a hardware error of a platform which includes the processor, and generates a call to invoke an MCE handler which the processor implements by executing second firmware code. The MCE handler is called, outside of a software context, to attempt a recovery from the hardware error. The call is performed independent of any system management interrupt being based on the detected hardware error. In another embodiment, another MCE handler of an operating system is conditionally invoked where it is determined that the attempted recovery by the first MCE handler was unsuccessful.

A virtual machine status probe method includes obtaining an invocation message and an identifier of a first virtual machine, invoking a probe script based on the invocation message, and transferring the identifier of the first virtual machine to the probe script, sending a probe packet to a source device by running the probe script, receiving feedback information sent by the source device, where the feedback information is used to indicate the status of the first virtual machine, and determining, based on the feedback information, whether to recreate the first virtual machine in the destination device.

An apparatus includes a processor to receive a request to provide a view of an object associated with a job flow, and in response to determining that the object is associated with a task type requiring access to a particular resource not accessible to a first interpretation routine: store, within a job queue, a job flow generation request message to cause generation of a job flow definition the defines another job flow for generating the requested view; within a task container in which a second interpretation routine that does have access to the particular resource is executed, generate the job flow definition; store, within a task queue, a job flow generation completion message that includes a copy of the job flow definition; use the job flow definition to perform the other job flow to generate the requested view; and transmit the requested view to the requesting device.