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.

An apparatus comprises a processing device configured to identify, at a first microservice, a service call that is to be transmitted to a second microservice, and to modify the service call to include context information, the context information characterizing a current state of execution of one or more tasks by one of the first microservice and the second microservice. The processing device is further configured to provide, from the first microservice to the second microservice, the modified service call including the context information. The context information enables re-initiation of said one of the first microservice and the second microservice to continue execution of the one or more tasks from the current state.

Current configuration information indicates current configuration of an information system. Past configuration information indicates past configuration case information attained from different past configuration cases for the information system. The current configuration information and the past configuration information are each constituted of items each assigned with a bit. A value of each bit assigned to each item indicates one of two states defined in each item. Handling method information associates a relationship between a bit sequence of the current configuration information and a bit sequence of the past configuration case information with a handling method for a configuration error. A management system selects past configuration case information from the past configuration information, selects, from the handling method information, a handling method based on the relationship between the bit sequence of the past configuration case information and the bit sequence of the current configuration information, and presents the selected handling method.

A storage device is disclosed. The storage device may include first storage for a data. A controller may manage access to the data in the storage. A second storage may store a first identifier and a second identifier, the first identifier for an event and the second identifier for a program. A processor may receive the event and execute the program based at least in part on the event table.

An online system, such as a multi-tenant system ensures high availability of systems, for example, database management systems. The online system replicates the databases across multiple datacenters including: (1) a master node that receives read and write requests (2) a read-replica that receives only read requests and (3) a spare node that does not receive requests but acts as standby for high availability. One or more application servers may send read and write requests to the databases. The system performs a sweep of upgrades of the database nodes and also performs traffic quiescing of the requests received from the application servers to redirect the traffic across the database nodes as the upgrade sweep is orchestrated. The sweep of upgrades ensures that the availability of the database management system to the end users is maximized during the upgrade process.

Embodiments of systems and methods for platform framework error handling are described. A platform framework may receive registration requests from framework participants that provide operation of a plurality of hardware devices of an IHS (Information Handling System). The framework registration requests by participants specify remediation policies for addressing error conditions related to respective participants. The received remediation policies are mapped to the registered participants, where remediation policies may include handles for invoking remediation procedures for a registered participant. Error conditions are detected during operation of the platform framework. The registered participant is identified as a source of the error condition and a remediation policy that is mapped to the registered participant is identified. Handles in the remediation policy are used to invoke remediation procedures for the registered participant. Remediation procedures invoked by the handles may be provided by a remediation agent that provides support for registered participants.

A method and apparatus for performing disk management of an all flash array (AFA) server are provided. The method may include: utilizing a disk manager module among multiple program modules running on any node of multiple nodes of the AFA server to trigger a hardware layer of the any node to perform disk switching control in HA architecture of the AFA server, for controlling the any node to enable a set of disk switching paths between the any node and a group of storage devices among multiple sets of disk switching paths between the multiple nodes and multiple groups of storage devices; and utilizing the disk manager module to perform multiple groups of operations respectively corresponding to multiple disk pools in a parallel processing manner, for managing the group of storage devices with the multiple disk pools, wherein the multiple disk pools may include active, inserted, and failure disk pools.

Various embodiments may include methods and systems for reconfiguring memory channel routing within a system-on-a-chip (SoC). A method may include obtaining first error information in response to misbehavior in a first memory channel communicatively connected to a network interface unit (NIU) of the SoC. The method may further include storing the first error information in non-volatile memory that is read upon booting of the SoC, and rebooting the SoC including the first memory channel. The method may further include configuring the first memory channel to be communicatively disconnected from the NIU and configuring a second memory channel to be communicatively connected to the NIU in response to reading the stored first error information during reboot.

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.

The subject disclosure is directed towards components in different server clusters, e.g., comprising software components such as components of a distributed computing system. Components are available for use by distributed computing system applications, yet managed by the distributed computing system runtime such that only a single instance can be activated and exist within communicating (non-partitioned) clusters. Also described is recovery from a situation in which no longer partitioned clusters each have created the same component.