G06F2209/5015

SERVICE PROCESSING METHOD AND APPARATUS, AND STORAGE MEDIUM
20230049501 · 2023-02-16 ·

A service processing method, performed by a cloud application management server, includes: upon receiving an allocation request from a target terminal, acquiring N pieces of selection reference information corresponding to a pending edge server and related to the target terminal and running reference information, the pending edge server being one of P edge servers connected to the cloud application management server; upon determining that the pending edge server meets a requirement of providing a running service of a target cloud application for the target terminal, determining a connection reference score corresponding to the pending edge server; storing the connection reference score and identification information about the pending edge server into a candidate set; and transmitting the candidate set to the target terminal.

Generation of cloud service inventory

A data model characterizing a plurality of resources is received. The data model associates a first resource within a first remote computing environment with a first tag and a second resource within a second remote computing environment with a second tag. The data model is received from a database that is separate from the first remote computing environment and the second remote computing environment. The plurality of resources is grouped based on the first tag and the second tag. The grouping can form a first group associated with the first tag and a second group associated with the second tag. A first list of resources characterizing the first group and a second list of resources characterizing the second group is provided. Related apparatus, systems, techniques and articles are also described.

Method and system for predicting resource reallocation in a power zone group

A method for managing data includes obtaining, by a first data node, a notification, wherein the first data node is associated with a first power zone group (PZG), and in response to the notification: selecting a second data node, wherein the second data node is not associated with the first PZG, sending a data processing request to the second data node, obtaining a response based on the data processing request, wherein the response specifies a confirmation by the second data node to service the data processing request, storing a ledger entry in a ledger service that indicates the confirmation, and initiating a data transfer based on the data processing request, wherein the first data node is associated with the PZG based on a primary power source of the first data node.

Unified container orchestration controller

A system to facilitate a container orchestration cloud service platform is described. The system includes a controller to manage Kubernetes cluster life-cycle operations created by each of a plurality of providers. The controller includes one or more processors to execute a controller micro service to discover a provider plugin associated with each of the plurality of providers, and perform the cluster life-cycle operations at a container orchestration platform as a broker for each of a plurality of providers.

AUTOMATED SERVICES EXCHANGE
20230015524 · 2023-01-19 ·

Methods, apparatus, and processor-readable storage media for providing an automated services exchange are described herein. An example computer-implemented method includes obtaining provider requests from one or more service providers, wherein each of the provider requests comprises an indication of at least one type of service provided by the corresponding service provider and attributes associated with the at least one type of the service; processing the provider requests, wherein the processing for a respective one of the provider requests comprises generating a corresponding set of metrics associated with the at least one type of service and the attributes of the respective provider request; and matching a given one of the provider requests to at least one consumer request based at least in part on: the processing and constraints identified in the at least one consumer request with respect to at least a portion of the attributes of the given provider request.

Systems and methods for recommending optimized virtual-machine configurations

An example method is provided for recommending VM configurations, including one or more servers upon which one or more VMs can run. A user wishing to run these VMs can request a recommendation for an appropriate server or set of servers. The user can indicate a category corresponding to the type of workload that pertains to the VMs. The system can receive the request and identify a pool of servers available to the user. Using industry specifications and benchmarks, the system can classify the available servers into multiple categories. Within those categories, similar servers can be clustered and then ranked based on their levels of optimization. The sorted results can be displayed to the user, who can select a particular server (or group of servers) and customize the deployment as needed. This process allows a user to identify and select an optimized setup quickly and accurately.

Systems and methods for providing uniform access in a multi-tenant system

Receive, by a central controller engine, a user request to perform one or more operations associated with user data, wherein the user data includes first data and second data. Select, by the central controller engine based on the user request, a first service provider interface (SPI) integrated into a first service, the first SPI being configured to operate on the first data in a first datastore associated with the first service. The first SPI including a first service interface component configured based on a uniform access specification. Obtain, by the first SPI, the first data, the first data being formatted according to a first service data specification. Transform, by the first SPI based on the uniform access specification, the first data, thereby generating transformed first data formatted according to the uniform access specification. Provide, by the first SPI, the transformed first data to a target service.

MULTI-CLOUD DEPLOYMENT STRATEGY BASED ON ACTIVITY WORKLOAD

Multi-cloud deployment strategy is based on automated analysis of context and requirements for an activity workload. The activity workload is defined by user input including information regarding project cost, performance requirements, and geographical preferences. Selection of cloud-based resources for handling the activity workload is based in part on service availability record, projected cost of resources, and physical geographic locations. A cloud services registry provides cloud service provider data for selection to perform aspects of the activity workload.

CLOUD SERVICE PROVIDER SELECTION BASED ON DIGITAL TWIN SIMULATION

A processor may automatically select a cloud service provider. A processor may receive one or more parameters associated with an entity and a cloud service dataset associated with a provider. A processor may generate a digital twin of the entity using the one or more parameters. A processor may simulate the digital twin of the entity and the cloud service dataset. A processor may identify, responsive to simulating the digital twin of the entity and the cloud service dataset, one or more predicted conditions of cloud service dataset on the entity. A processor may select the provider based, at least in part, on the one or more predicted conditions.

Enhanced self-assembling and self-configuring microservices

A method for managing systems with interrelated microservices with self-assembling and self-configuring microservices includes receiving at a first micro service a service request from a client. A determination is the made whether the first micro service is capable of processing the service request. If the first micro service is capable of processing the service requests, then processing the service request; if the first micro service cannot process the service request then routing the service request to a first stem service. The first stem service determines whether there is a second micro service that can process the service request. If the second micro service that can process the service requests exists, then forwarding the service request to the second micro service for processing. If there is no second micro service that can service the service requests then morphing the first stem service into a micro service that can service the service request.