Abstract: 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.

Abstract: Methods and systems for managing the operation of data processing systems are disclosed. To manage the operation of the data processing systems, containerized services may be deployed. Once deployed, desired services may be provided. Prior to deployment, images and metadata used in the deployment may be analyzed. The analysis may reduce threats presented by the deployment of the containerized services. During the analysis, the integrity of the images and metadata may be verified, and the privilege of containerized services based on the metadata and images may be reviewed.

Abstract: 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.

Abstract: Methods and systems for managing services provided by a data processing system are disclosed. A service of the services may be managed by accounting for other services and dependencies on which the service of the service relies. To account for the other services, the dependencies may need to be validated. To validate the dependencies, the other services may be checked to see if they are implemented. If the other services are not implemented, the other services may be supplemented. Otherwise, the other services may be validated and therefore the dependencies may be validated. Once the other services and the dependencies are validated, then a service of the services may be deployed.

Abstract: 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.

Abstract: Methods and systems for managing operation of a distribute system are disclosed. To manage the distributed system, a distributed ledger may be used to track the condition of the system. The distribute ledger may be managed in accordance with a consensus based approach. The consensus based approach may limit the impact of compromised entities by reducing the ability of the compromised entities from introducing malicious data into the data upon which management decision are made. Additionally, the distributed ledger may provide a shared understanding the condition of the distributed system across the distributed system.

Abstract: Methods and systems for managing distributed systems are disclosed. The distributed system may be managed by monitoring for overloaded data processing systems of the distributed system. If identified, workloads from the overloaded data processing systems may be migrated to other data processing systems that are not overloaded to improve the likelihood of timely generating results from the workloads. The results may be used in distributed processes that may require the results to be timely. If the results are not timely obtained, the distributed processes may be impacted.

Abstract: 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.

Abstract: Methods and systems for managing operation of endpoint devices are disclosed. The operation of the endpoint devices may be managed by restricting the communication capabilities of the endpoint devices. For services that are to be provided by the endpoint devices, some communication capabilities may be selectively enabled. The selective enablement of the communication capabilities may be evaluated prior to implementation through simulation using a digital twin. The selective enablement may only be implemented if it meets criteria.

Abstract: 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.

Abstract: 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.

Abstract: Methods and systems for securing software architectures are disclosed. The software architectures may be secured through the implementation of threat models. The threat models may include design threat models that indicate vulnerabilities that software based on an architecture may exhibit, and build threat models that indicate vulnerabilities of implementation of the software based on the architecture may exhibit. The threat models may be used to select where and how to deploy software to limit exploitable vulnerabilities to be within acceptable levels.

Abstract: 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.

Abstract: A system can determine respective health statuses for respective microservices of respective instances of a group of microservices. The system can monitor the requests to determine a correlation between respective requests of the requests and respective subgroups of microservices of the group of microservices that carry out the respective requests. The system can determine a subgroup of container clusters of container clusters that are available to serve a first request type, based on determining an intersection between the respective subgroups of microservices of the group of microservices that carry out the respective requests, and the respective health statuses for respective microservices of respective instances of the group of microservices. The system can, in response to receiving a first request of the first request type, assign, by a load balancer, the first request to be served by a first container cluster of the subgroup of container clusters.

Abstract: A system can receive, at an integration and deployment component, a changeset for an updated microservice and an identifier of a user account that is configured to access the updated microservice, wherein a current version of the microservice is deployed to a service mesh that comprises a group of microservices. The system can instantiate the updated microservice to the service mesh. The system can update routing rules for the service mesh to indicate that any traffic in the service mesh that is associated with the user account and that is directed to the current version of the microservice is to be routed to the updated microservice. The system can, in response to receiving traffic determined to be associated with the user account and directed to the current version of the microservice, route the traffic to the updated microservice instead of routing the traffic to the current version of the microservice.

Abstract: A system, method, and computer-readable medium for performing a data center management and monitoring operation. The data center management and monitoring operation includes: identifying a plurality of process flows; identifying a plurality of microservices associated with each of the plurality of process flows; mapping each of the plurality of microservices associated with each of the plurality of process flows; calculating a centrality value for each of the plurality of microservices associated with each of the plurality of process flows based upon the mapping; and, testing at least some of the plurality of microservices based upon the centrality value for each of the plurality of microservices.

Abstract: 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.

Abstract: Methods and systems for managing pods and containers that provide computer implemented services are disclosed. The pods and containers may be managed to improve efficiency of resource use and reduce exposure to threats to operation of systems that host the pods and containers. To ascertain how to manage the pods and containers, the pods and containers may be monitored and analyzed. The results of the monitoring and analyzation may be used to select how to change the pods and containers over time.

Abstract: 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.

Abstract: A system can determine complexity data representative of a complexity of changes to computer code that is executable to operate at least one microservice that is part of a group of microservices, wherein a portion of the changes corresponds to a library on which the computer code depends. The system can generate a progressive deployment plan for the at least one microservice based on the complexity of changes. The system can progressively direct traffic to the at least one microservice based on the progressive deployment plan.