Dell Products Inc.

Emc IP Holding Company LLC

Dell & Products L.p.

Igor Dubrovsky

Boris Shpilyuck

Nisan Haimov

Jehuda Shemer

Maxim Balin

Stav Sapir

Ofir Ezrielev

Yair Yotam

Methods and systems for managing systems are disclosed. To manage the systems, backups of data used by the systems may be generated and stored for future use. To limit overhead for generation and storage of the backups, portions of data may be evaluated for relative importance using an automated evaluation process. The automated evaluation process may take into account entities involved in data access chains, access frequency, data location, and/or other factors. The resulting evaluations may be used to selectively deploy limited computing resources for backing up of different portions of data.

Edge computing-enhanced system for business priority-based resource allocation

Methods and systems for managing operation of a deployment are disclosed. The deployment may be managed by employing redundant devices within the deployment. The redundant devices may serve to replace operation of failed devices. Despite replacement of operations of a failed device, the redundant device may not have similar functionality as the failed device. To make the functionality similar to the failed device, a correction factor may be applied to the redundant device. In applying the correction factor, the output from the redundant device may be expected to match output from the failed device. In matching output from the failed device, the redundant device may operate in place of the failed device.

Employing redundant devices in a deployment

Methods and systems for prioritizing resources are disclosed. The resources in a deployment may be prioritized by training machine learning models for use in repairing impaired devices with failures of operation. The trained machine learning models may learn differences in operation. Differences in operation may pertain to output between each device of the set of devices and the digital twin in the deployment. The differences in operation may be used to prioritize a list of impaired devices that may be repaired. The prioritized list of impaired devices may be followed when available resources may be expended to repair the impaired devices.

Prioritizing resources for addressing impaired devices

Methods and systems for managing operation of a deployment are disclosed. The operation of the deployment may be managed by simulating devices with a digital twin within the deployment. The digital twin may serve to replace operation of failed devices. By replacing failed devices with the digital twin, cooperative processes requiring participation of the failed devices may be continued while the failed devices are unable to participate.

Simulating devices with a digital twin in a deployment

Systems and methods for risk assessment of user accesses to data resources are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include: a processor; and a memory coupled to the processor, where the memory includes program instructions store thereon that, upon execution by the processor, cause the IHS to: obtain a plurality of resource risk weights of a respective plurality of resources, and a plurality of access permissions of a user for the respective plurality of resources; and generate based, at least in part, on the plurality of resource risk weights and the plurality of access permissions of the user, a risk score for the user that represents a level of security impact of the user on the plurality of resources.

Systems and methods for risk assessment of user accesses to data resources

Methods and systems for securing blueprints are disclosed. A blueprint may be secured by requiring sufficient privilege to implement the blueprint. The sufficient privilege may be obtained through an analysis of permissions of a blueprint user and the blueprint authors. An analysis of the permissions of the blueprint user and the blueprint authors may include reviewing privileges of the blueprint user and the blueprint authors. When the sufficient privilege may be found for the blueprint user and the blueprint authors, use of the blueprint may be permitted on an edge device.

Securing blueprints for implementation in edge devices

A system can determine that there is a failed configuration in a microservices architecture, wherein the microservices architecture comprises a group of microservices. The system can order the microservices of the group to produce an ordered group of microservices, wherein the ordering first comprises failed microservices of the group of microservices, then dependent microservices of the group of microservices, and wherein respective failed microservices of the failed microservices depend on respective dependent microservices of the dependent microservices. The system can perform iterations of, splitting the ordered group of microservices into two subgroups of microservices, and reverting changes to one of the two subgroups of microservices. The system can determine that a microservice of the group of microservices has the failed configuration based on a result of the performing of the iterations.

Detecting configuration issues during pre-canary deployment

The technology described herein is directed towards combining multiple sidecar (e.g., Envoy-based) proxies into a single sidecar or reduced number of sidecars for use in association with a service. Described is identifying sidecars for merging, grouping by version compatibility, and determining their functions and configuration data. Any conflicts in the configuration data are resolved. A merged sidecar is built by combining functional code and configuration data. The merged sidecar is deployed along with its relevant service, e.g., deployed as a container in a Kubernetes environment. The merging facilitates reduction of resource utilization by having only a merged sidecar, instead of multiple sidecars, support a service.

Cloud proxy-based sidecar coalescence

Methods and systems for managing the operation of data processing systems are disclosed. To manage the operation of the data processing systems, access control standards for software may be enforced during development and/or deployment of software. The access control standards may indicate the extent of access controls for data that are to be in place for various pieces of software. The access control standards may also indicate a level of consistency in the sources of truth for permissions enforced by the access controls.

Access control management for systems

A system can identify, by a control plane, that a base image has been registered to a first registry that is stored outside of the computing cluster. The system can identify, by the control plane, a trust bundle that corresponds to the base image. The system can send, by the control plane and to a secure pipeline that operates outside of the control plane, a message to update the base image. The system can create, by the secure pipeline, an updated image based on the base image and the trust bundle. The system can send, by the secure pipeline, the updated image to the control plane. The system can store, by the control plane, the updated image in a local registry that is stored on the computing cluster.

Securing serverless computing workloads in a cold start

Methods and systems for managing operation of a distributed system comprising a data center and edge devices. The operation of the distributed system may be managed by monitoring the edge devices. The edge devices may be monitored by identifying the health state of an edge device. The health state of the edge device may be identified by collecting data from operation of similar edge devices and the edge device and comparing the differences in between the data. If the differences between the data from the operation of the similar edge devices and operation of the edge device may exceed criteria for deviation, then the edge device may be determined to be in an unhealthy health state.

Identifying the health state of edge devices

Methods and systems for managing a backup system are disclosed. Edge infrastructures may be made up of large numbers of edge devices that produce and store a wide variety of data. A data backup system is implemented to locate and monitor locations of data stored in these edge infrastructures such that users wanting to backup data from these edge infrastructures are not required to know an exact location and/or an exact name of the data to be backed up. In particular, the data backup system could backup data using only natural language descriptions of the data that is provided by the user.

System and method for backing up data from edge infrastructures

Methods and systems for managing trust in distributed are disclosed. To manage trust, a behavior and characteristic based trust model may be used. The trust model may utilize similarity between devices and public activity of devices over time to ascertain levels of trust that should be afforded devices of the distributed system. The levels of trust may be used to ascertain whether requests from devices of the distributed systems should be honored, or rejected. The trust models may facilitate establishment of trust in environments where physical intrusion based threats are present.

Trust management in distributed systems

A system can determine complexity data representative of a complexity of changes to computer code that is executable to operate at least one updated microservice that is part of a group of microservices, wherein at least one current microservice is deployed, and wherein the at least one updated microservice corresponds to an update of the at least one current microservice. The system can determine a rate at which invocations of the at least one current microservice are made. The system can determine a threshold number of calls to be processed to proceed from a first stage of a progressive deployment plan to a second stage of the progressive deployment plan based on the complexity data and the rate. The system can progressively direct traffic to the at least one updated microservice based on the progressive deployment plan.

Automatic canary deployments with dynamically updating call thresholds

Methods and systems for device shutdown in a deployment are disclosed. Device shutdown may be considered to conserve energy and simplify processes in a deployment. To conserve energy and simplify processes, all devices within a deployment may undergo a redundancy analysis and qualification analysis. The redundancy analysis may produce lists of redundant and non-redundant devices. All redundant devices may be candidates for device shutdown. Next, qualification analysis may qualify devices for shutdown by energy consumption and output data accuracy and uncertainty qualification. Devices that may not meet prescribed qualifiers may also be candidates for shutdown. With all devices that may be candidates for shutdown assembled in a list, device shutdown may commence in the deployment.

Growing community of inventors

Beer Sheva, Israel

Igor Dubrovsky