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

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

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

Abstract: A Hyper-Converged Infrastructure (HCl) system that includes a plurality of HCl log generating components and an HCl storage system that provides at least a portion of a log database. The HCl system receives a request from a management system to store a first log bundle of the plurality of HCl log generating components and determines the at least one second log bundle that is stored in the log database is at least a size threshold. The HCl system performs a log database clean operation on the at least one second log bundle and determines that the log database clean operation on the at least one second log bundle has provided an available storage capacity in the log database that is sufficient to store the first log bundle. The HCl system then stores the first log bundle in the log database.

Abstract: A FDO protocol computing device ordering/manufacturing system includes a computing device manufacturer system coupled to a voucher management system. The computing device manufacturer system identifies, as part of an ordering process for a computing device being ordered by a subsequent owner, rendezvous system reachability information for a rendezvous system. The computing device manufacturer system provides the rendezvous system reachability information in the computing device prior to its transfer to the subsequent owner.

Abstract: A voucher management system receives, from a computing device manufacturer system, an ownership voucher that transfers ownership of a computing device from the computing device manufacturer system to the voucher management system, and a hardware attestation certificate for the computing device, and associates them with the computing device in a voucher management database. When the voucher management system determines that the ownership of the computing device should be transferred to an end user system, it automatically generates second ownership transfer data by signing an end user system public key with a voucher management system private key, provides the second ownership transfer data in the ownership voucher in order to transfer ownership of the computing device from the voucher management system to the end user system, and provides the ownership voucher and the hardware attestation certificate to the end user system.

Abstract: A networked system includes a first owner system and a second owner system coupled to a voucher management system. The voucher management system receives, from the first owner system, an ownership voucher having first ownership transfer data including a voucher management system public key that has been signed by a first owner system private key in order to transfer ownership of a computing device from the first owner system to the voucher management system. The voucher management system determines that the ownership of the computing device should be transferred to the second owner system and, in response, automatically generates second ownership transfer data by signing a second owner system public key with a voucher management system private key, and provides the second ownership transfer data in the ownership voucher in order to transfer ownership of the computing device from the voucher management system to the second owner system.

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

Abstract: Disclosed subject matter includes a testing method that 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 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.

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

Abstract: An information handling system may include at least one processor and a memory. The information handling system may be configured to: receive, from a cloud management portal, a request to execute a management task, wherein the request includes information regarding a cloud identity associated with the request; determine a local identity that corresponds to the cloud identity; determine whether the local identity has sufficient privileges to execute the management task; and in response to a determination that the local identity does have sufficient privileges to execute the management task, cause the management task to be executed.

Abstract: An information handling system may include at least one processor and a memory. The information handling system may be configured to: store a cryptographic lockbox that is secured by a first set of secrets and that is accessible from a first virtual machine; modify the cryptographic lockbox such that the cryptographic lockbox is secured based on a second set of secrets that includes a strict subset of the first set of secrets and a user-supplied secret; and access the cryptographic lockbox from a second virtual machine.

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

Abstract: Methods and systems disclosed herein extend an entity's private cloud security model to the entity's public cloud. Public cloud access permissions are defined, in accordance with a security model implemented in the entity's private cloud, for one or more of the entity's public cloud resources. The public cloud permissions are pushed or otherwise provided to an access module within the private cloud. Upon receiving a request to access a public cloud resource, the private cloud access module is invoked to grant or deny the access request in accordance with the public cloud access permissions. Similarly, upon receiving a request to access a private cloud resource, the private cloud access module is invoked to process the access request in accordance with private cloud access permissions, thereby beneficially enabling users to interact with a single access interface regardless of whether the resource reside within the entity's cloud platform.

Abstract: An information handling system may include at least one processor and a memory. The information handling system may be configured to: receive a management request from an administrator device regarding management of a remote information handling system located at a particular datacenter; and provide the administrator device access to a selected set of management operations, wherein the set is selected based on a determination of whether or not the administrator device is on-premises at the particular datacenter.

Abstract: 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 performing, 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 maintain management agent software within the customer's private cloud. The on-premises resources a multi-node cluster provided by a node or nodes of a one or more HCI appliances.

Abstract: A disclosed microservice scaling operation obtains information indicating dependencies between a function associated with an external API call and microservices spanned by the external API call. Functions invoked by managed resources are monitored and, responsive to detecting the function being invoked, a scaling service is launched to access the dependency information, identify the applicable microservices, and perform a scale up operation instantiating each of the microservices. The dependency information may be obtained by recording and analyzing traces for instances of the external API call to determine a dependency tree that indicates branches spanned by the external API call and a sequence of microservices corresponding to each branch. The microservices may be scaled up in parallel or in a prioritized parallel manner wherein in early span microservices are launched before late span microservices. The API may be a RESTful API and each microservice may correspond to an internal API call.

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

Abstract: An information handling system may include at least one processor and a memory. The information handling system may be configured to determine names for a plurality of other information handling systems that are on-premises at a particular datacenter having a local network associated therewith; poll a selected subset of the plurality of other information handling systems via the local network; based on results of the polling, determine whether the information handling system is on-premises at the particular datacenter; and in response to a determination that the information handling system is on-premises at the particular datacenter, enable access to at least one sensitive administration operation associated with the particular datacenter.

Abstract: A disclosed method for managing access to cloud infrastructure include responding to receiving a user request to access a cloud resource, such as a cluster associated with a hyper-converged infrastructure appliance, associated with an entity by performing a layered authentication of the user. The layered authentication includes determining first layer privileges based on first user credentials associated with a first authentication module and determining second layer privileges based on second user credentials associated with a second authentication module. The request is granted or denied based on a combination of the user's first and second layer privileges. The first authentication module may be associated with a first authentication domain such as an authentication domain of a cloud service provider or an OEM of cloud infrastructure resources. The second authentication module may comprise an authentication module maintained by the entity associated with the resource targeted by the user request.