Abstract: Disclosed herein are systems and method for detecting problematic performance on a software instance. In one aspect, the method includes: receiving, from a first software instance, a log file that lists actions performed on a computing device over a period of time; parsing the log file to identify, from the actions, a first sequence of actions performed on a given object; analyzing similarity between the first sequence of actions performed on the given object and at least one other sequence of actions performed on at least one other object of a same type, wherein the at least one other sequence of actions is indicative of problematic performance; in response to determining, based on the analysis of similarity, that the first sequence of actions is similar to the at least one other sequence of actions, generating an alert indicating the problematic performance on the first software instance.

Abstract: Disclosed herein are systems and methods for updating software object instances on a plurality of nodes. An exemplary method may comprise monitoring a software repository for an update to the software object instance installed on the plurality of nodes. In response to detecting the update, the method may comprise initiating installation of the update to the software object instance on a first subset of the plurality of nodes in accordance with an installation schedule. The method may comprise determining whether a functionality or performance issue in the software object instance or a respective node of the first subset was detected subsequent to updating the software object instance. In response to determining that the functionality or performance issue was not detected, the method may comprise updating the software object instance on a second subset of the plurality of nodes in accordance with the installation schedule.

Abstract: Disclosed herein are systems and method for gradually updating software object instances on a plurality of computer nodes. In an exemplary aspect, in response to receiving a notification from a software object instance, a system may register the software object instance at an update server. The system may store and deploy a plurality of links, wherein each deployed link uniquely corresponds to a registered software object instance. The system may then associate two or more subsets of the plurality of links with two or more update locations, in accordance with an update policy. The system may place an update to the software object instance at the two or more update locations in accordance with an update policy. In response to receiving an update request via a link from a computing node, the system may further redirect the update request to an update location associated with the link.

Abstract: Disclosed herein are systems and method for booting servers in a distributed storage to improve fault tolerance. In one aspect, an exemplary method comprises, during a booting of a hardware server belonging to the distributed storage, starting a boot component from on any one physical block device from at least two or more physical block devices of the hardware server, wherein the at least two or more physical block devices of the hardware server are bootable and each physical block device stores the boot component, wherein an Operating System (OS) of the hardware server is installed on a virtual disk, and wherein the virtual disk is stored on the distributed storage, and by the boot component, accessing the distributed storage to obtain access to the virtual disk, mounting the virtual disk as a root file system of the OS, and booting the OS from the mounted virtual disk.

Abstract: Disclosed herein are systems and method for deploying servers in a distributed storage to improve fault tolerance. In one aspect, an exemplary method comprises, on a hardware server, installing an OS on a virtual disk, putting the virtual disk on the distributed storage, configuring the hardware server so that at least two physical block devices of the hardware server are bootable by putting, on each physical block device of the at least two physical block devices, a boot component, and configuring the boot component on any one physical block device of the at least two physical block devices, the configuration of the boot component including enabling the boot component to perform at least one of: mounting the virtual disk as a root file system of the OS, and booting the OS from the mounted virtual disk during a booting of the hardware server.

Abstract: Disclosed herein are systems and method for gradually updating software object instances on a plurality of computer nodes. In an exemplary aspect, in response to receiving a notification from a software object instance, a system may register the software object instance at an update server. The system may store and deploy a plurality of links, wherein each deployed link uniquely corresponds to a registered software object instance. The system may then associate two or more subsets of the plurality of links with two or more update locations, in accordance with an update policy. The system may place an update to the software object instance at the two or more update locations in accordance with an update policy. In response to receiving an update request via a link from a computing node, the system may further redirect the update request to an update location associated with the link.

Abstract: Disclosed herein are systems and method for collecting an optimal set of log files for generating error reports. In one aspect, a method may comprise detecting an error in a software component and retrieving a function call trace associated with the software component. The method may comprise comparing the retrieved function call trace with a plurality of known call traces, wherein each respective known call trace of the plurality of known call traces is associated with a respective set of log files to be collected for error analysis. The method may comprise identifying, based on the comparison, a known call trace for which a similarity value with the retrieved function call trace is greater than a threshold similarity value. The method may comprise collecting a set of log files for the error based on an associated set of log files for the known call trace and generating an error report.