Dell Products Inc.

Haijun Zhong

Muzhar S Khokhar

Xiaojun Wu

Michael G Varteresian

Wenfeng Li

Bin Hu

Xiaoye Jiang

Qing Li

Donald Mace

Baoli Chen

HongYao Tang

Yuyan Chen

Stéphane Meng

Chen Liang

Jing J Chen

Vivian Jian

A microservice management method responds to receiving a function request, comprising a request for a particular function, by collecting function metadata for the particular function and sending the function request and the function metadata to a cloud side orchestrator. The function metadata include one or more prerequisite for an execution environment. Suitable microservices for the particular function are identified, in accordance with the function metadata. The identified microservices are sent to an edge side orchestrator that installs, initializes, and monitors these microservices and, responsive to detecting complete execution of the particular function, terminates one or more of the suitable microservices. The identification of suitable microservices may be based, at least in part, on one or more preference factors including a dependency factor, indicative of a historical dependency between the particular function and one or more microservices and a relevance factor indicative of whether a microservice edge-type microservice.

Life cycle management of run time services in edge computing environment

An information handling system cluster may include a plurality of nodes, each node including at least one processor and a memory. A particular node of the information handling system cluster may be configured to: receive management instructions from a central management system; cause the management instructions to be executed by other nodes of the information handling system cluster; receive result information from the other nodes; and transmit the result information to the central management system.

Autonomous edge computing system management

Disclosed methods and systems for managing on-premises information handling resources establish, by an in-cloud web portal, an agentless connection to an on-premises information handling resource and perform, via the agentless connection, a configuration management operation to modify a configuration of the on-premises handling resource. Establishing the agentless connection and performing the configuration management operation may include one or more appropriate API calls. Disclosed teachings enable a web-accessible, public cloud portal to perform active configuration management of on-premises resources scattered across any number of distinct and potentially isolated customer sites without deploying and maintaining management agent software within the customer's private cloud. The on-premises resources may include a multi-node cluster provided by a node or nodes of one or more HCI appliances.

Centralized and agentless in-cloud management of on-premises resources

A disclosed method for managing access control in cloud based environment with on-premises and off-premises access portals includes storing account mapping information, indicative of an association between on-premises accounts off-premises accounts, to a lockbox in each of the plurality of clusters and deploying an off-premises agent in each of the clusters. One or more of the clusters may exist within a hyper-converged infrastructure system. Each off-premises agent may be configured to retrieve cluster access information indicative of access permissions for the on-premises node cluster and upload the cluster access information to an off-premises access control service. The access permissions for the on-premises cluster and the off-premises access permissions may comprise role based access permissions. The off-premises access control service is coupled to an off-premises portal and enables the off-premises portal to switch its access control permissions between on-premises access permissions and off-premises permissions in accordance with the targeted resource.

Managing on-premises and off-premises access control

A disclosed security broker receives a request message addressed to a message queue associated with an edge resource, identifies the message source, and leverages an authentication module to verify that the source has authorization to access the targeted message queue. The security broker may then deliver the request message to the targeted edge resource message queue. If the edge resource and security broker are physically isolated, the security broker may format the request message as a file, store the file to a storage device, and transfer the storage device to the edge resource, which may then process the file and upload the request message to the edge resource's message queue module. The security broker also monitors a response message from the edge resource, purges sensitive data from the response. If the broker and cloud resource are physically isolated, the response may be formatted and delivered as a file.

Security broker for edge computing environment

An information handling system may include at least one processor and a memory. The information handling system may be configured to receive a heartbeat message from a second information handling system via a network, wherein the second information handling is system not publicly accessible via the network, and wherein the heartbeat message is operable to establish a communication channel between the information handling system and the second information handling system; and transmit a response to the second information handling system via the communication channel, wherein the response indicates whether any management tasks should be executed by the second information handling system.

Zero touch management from cloud

An information handling system may include at least one processor and a memory. The information handling system may be configured to: receive an instruction to join an information handling system cluster; deploy at least one prerequisite service from the information handling system to the information handling system cluster; and cause a master node of the information handling system cluster to join the information handling system to the information handling system cluster.

Deployment of infrastructure management services

A testing method accesses tracing data comprising a plurality of tracing records corresponding to a plurality of test cases executed on a target system. The target system includes a plurality of microservices configured in accordance with a REST API. A dynamic test analyzer accesses the tracing data and imports a definition of the REST API. The analyzer checks each tracing record for consistency with the API definition. Based on this checking of the tracing records, one or more coverage metrics may be calculated. If any one or more of the one or more coverage metrics fails to exceed a threshold coverage, a testing action may be required. In some cases, the testing action may be selected from either seeking additional coverage of the APIs included in the target system or seeking additional test result coverage.

Dynamic analysis of rest API testing in microservice architecture

An information handling system may include at least one processor and a memory. The information handling system may be configured to: execute an application comprising a plurality of microservices on the at least one processor, wherein the application is configured to service external requests by executing a plurality of application programming interface (API) calls among the plurality of microservices; and for each API call: determine a span ID associated with such API call; determine a trace ID associated with a particular external request that is associated with such API call; and log the span ID and the trace ID.

Locating failures in microservice system

A method for managing information handling resource versions includes maintaining one or more snapshots of one or more validated release versions for a group of components. Each validated release version indicates a component version for each component in the group. Each component version in a higher validated release version is required to be greater than or equal to a corresponding component version in a lower validated release version. Responsive to identifying an instance of the component group in an non-validated state, disclosed methods identify a lowest validated release version that 'covers' the non-validated state, wherein a validated release version covers any state in which no component version is greater than its corresponding component version in the validated release version. The instance of the component group is updated to a validated release version that equals or exceeds the lowest validated version.

Validated state control in edge computing

A disclosed method includes obtaining, by a cluster manager, first zero configuration information, from one or more unconfigured nodes of an information handling system cluster. A service on the cluster manager may then generate custom zero configuration information for each of the unconfigured nodes and stored the custom zero configuration information in a zero configuration management store. Each unconfigured node may then retrieve its custom zero configuration information from the zero configuration management store and modify one or more zero configuration parameters of the unconfigured node in accordance with the custom zero configuration information. Disclosed methods may determine zero configuration criteria for configuring a node and identify, based on the custom zero configuration information in the zero configuration management store, unconfigured nodes of the cluster matching the zero configuration criteria. A zero touch configuration of the identified nodes may then be performed.

Managing cloud native zero configuration features of on premises resources

A method for managing a cloud computing platform including an edge-side and a cloud-side sends a data collection service from the cloud side to the edge side environment to collect edge data indicative of one or more microservice architecture (MSA) parameters associated with one or more microservices in the edge side. An measurement of the edge data is performed to identify dependencies between one or more MSA parameters and one or more edge environment settings. Based at least in part on the MSA measurement, one or more edge environment optimizations are identified and one or more appropriate fixes are implemented within a cloud-side modified edge environment. Before distributing the modified edge environment to the edge, an in-cloud verification of the cloud-side modified edge environment.

Growing community of inventors

Shanghai, China

Haijun Zhong