WO2022143653A1 - 基于微服务的多云接口适配方法、系统及存储介质 - Google Patents

基于微服务的多云接口适配方法、系统及存储介质 Download PDF

Info

Publication number
WO2022143653A1
WO2022143653A1 PCT/CN2021/142052 CN2021142052W WO2022143653A1 WO 2022143653 A1 WO2022143653 A1 WO 2022143653A1 CN 2021142052 W CN2021142052 W CN 2021142052W WO 2022143653 A1 WO2022143653 A1 WO 2022143653A1
Authority
WO
WIPO (PCT)
Prior art keywords
interface
interface adaptation
cloud
micro
cloud environment
Prior art date
Application number
PCT/CN2021/142052
Other languages
English (en)
French (fr)
Inventor
杨祥
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP21914387.2A priority Critical patent/EP4270204A4/en
Publication of WO2022143653A1 publication Critical patent/WO2022143653A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/382—Information transfer, e.g. on bus using universal interface adapter
    • G06F13/387—Information transfer, e.g. on bus using universal interface adapter for adaptation of different data processing systems to different peripheral devices, e.g. protocol converters for incompatible systems, open system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
    • G06F9/5022—Mechanisms to release resources
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/505—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the load
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5072—Grid computing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/541—Interprogram communication via adapters, e.g. between incompatible applications
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/5022—Workload threshold

Definitions

  • the embodiments of the present application relate to the technical field of cloud platforms, and in particular, to a microservice-based multi-cloud interface adaptation method, system, and storage medium.
  • the adaptation technology between multi-cloud platforms still has the following defects:
  • the adaptation technology between multi-cloud platforms usually adopts the method shown in Figure 1 and is implemented based on a single software architecture.
  • all the functions of the cloud management platform are in a war package, and there are basically no external dependencies except the WEB container. It needs to construct different request bodies, call different interfaces, and perform different business logic processing for each cloud platform according to different vendor types. In actual use, it is usually necessary to deploy redundant and repetitive code, the system has poor robustness, severe coupling, insufficient scalability and flexibility, and it is not convenient to update and maintain, and cannot meet the needs of rapid deployment.
  • embodiments of the present application provide a microservice-based multi-cloud interface adaptation method, system, and storage medium.
  • the embodiment of the present application proposes a micro-service-based multi-cloud interface adaptation method. After receiving a user request, it calls an interface defined by the interface adaptation micro-server, and transmits the user request to the interface adaptation micro-server to trigger the interface adaptation micro-server.
  • the micro-server internally performs the following steps in response to the user request: converting and encapsulating the user request, generating a resource access request, and sending the resource access request to the corresponding cloud environment interface; After the response result, the response result is converted into response information in a standard format for displaying to the user.
  • the embodiment of the present application also provides a micro-service-based multi-cloud interface adaptation system, including: a resource management micro-service unit, which is configured to call the interface defined by the interface adaptation micro-server after receiving a user request, and send The interface adaptation microserver transmits the user request with the target cloud environment interface identifier and standard request parameter information; the interface adaptation microserver is set to: the standard request parameter information in the user request is determined according to the target cloud environment interface identifier.
  • a resource management micro-service unit which is configured to call the interface defined by the interface adaptation micro-server after receiving a user request, and send
  • the interface adaptation microserver transmits the user request with the target cloud environment interface identifier and standard request parameter information; the interface adaptation microserver is set to: the standard request parameter information in the user request is determined according to the target cloud environment interface identifier.
  • the corresponding standard format is converted and encapsulated, a resource access request is generated, and the resource access request is sent to the corresponding cloud environment interface;
  • the interface adaptation microserver is also set to: after receiving the response result returned by the cloud environment interface , and convert the response result into response information in a standard format for display to the user; the resource management microservice and the interface adaptation microserver interact through a northbound REST interface.
  • Embodiments of the present application further provide a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, implements the microservice-based multi-cloud interface adaptation method described in any of the above. step.
  • Fig. 1 is a schematic diagram of the adaptation mode between multi-cloud platforms under the existing single architecture mode
  • FIG. 2 is a schematic diagram of a microservice-based multi-cloud interface adaptation system according to an embodiment of the present application
  • FIG. 3 is an interface adaptation microserver call sequence diagram in the microservice-based multi-cloud interface adaptation method according to an embodiment of the present application
  • FIG. 4 is a schematic flowchart of a microservice-based multi-cloud interface adaptation method according to an embodiment of the present application
  • FIG. 5 is a schematic diagram of implementing horizontal expansion based on microservices in the microservice-based multi-cloud interface adaptation system according to an embodiment of the present application
  • FIG. 6 is a schematic flowchart of steps for implementing the horizontal expansion function shown in FIG. 5 .
  • connection may be a direct connection between components and units, or an indirect connection between components and units through other components.
  • the embodiment of the present application proposes a micro-service-based multi-cloud interface adaptation method. After receiving a user request, it calls an interface defined by the interface adaptation micro-server, and transmits the user request to the interface adaptation micro-server to trigger the interface adaptation micro-server.
  • the micro-server internally performs the following steps in response to the user request: converting and encapsulating the user request, generating a resource access request, and sending the resource access request to the corresponding cloud environment interface; After the response result, the response result is converted into response information in a standard format for displaying to the user.
  • the micro-service-based multi-cloud interface adaptation method described above wherein the interface adaptation micro-server is provided with: a unified entry unit, the unified entry unit is defined with different resources for different resources.
  • the northbound REST interface to receive different user requests.
  • the microservice-based multi-cloud interface adaptation method described above wherein the user request includes: at least one target cloud environment interface identifier, and standard request parameters corresponding to the requested resource information.
  • the microservice-based multi-cloud interface adaptation method described above wherein the interface adaptation microserver is further provided with: a message processing unit; the message processing unit is configured to: The standard request parameter information in the user request is converted and encapsulated according to the standard format corresponding to the target cloud environment interface identifier, a resource access request is generated, and the resource access request is sent to the corresponding cloud environment interface; the message processing unit further It is set to: after receiving the response result returned by the cloud environment interface, convert the response result into response information in a standard format, and the standard format matches the cloud environment interface that returns the response result.
  • the microservice-based multi-cloud interface adaptation method described above wherein after receiving the user request, the unified entry unit invokes an application program interface corresponding to the message processing unit to deliver the Corresponding target cloud environment interface identifier and standard request parameter information.
  • the microservice-based multi-cloud interface adaptation method as described above wherein the interface adaptation microserver has multiple copies, each copy is executed by a respective independent computing unit, and each copy is follows the steps below to register or unregister with API Gateway, and API Gateway will uniformly distribute the received user requests: after N consecutive judgment cycles judge that the computing load of the existing copy exceeds the upper limit of the performance index, trigger the registration of a new copy, and allocate user requests to the new replica; after N consecutive judgment cycles determine that the computing load of the existing replica is lower than the lower limit of the performance index, stop allocating user requests to the replica with the lowest computing load, and trigger the cancellation of the replica.
  • the embodiment of the present application also provides a micro-service-based multi-cloud interface adaptation system, including: a resource management micro-service unit, which is configured to call the interface defined by the interface adaptation micro-server after receiving a user request, and send The interface adaptation microserver transmits the user request with the target cloud environment interface identifier and standard request parameter information; the interface adaptation microserver is set to: the standard request parameter information in the user request is determined according to the target cloud environment interface identifier.
  • a resource management micro-service unit which is configured to call the interface defined by the interface adaptation micro-server after receiving a user request, and send
  • the interface adaptation microserver transmits the user request with the target cloud environment interface identifier and standard request parameter information; the interface adaptation microserver is set to: the standard request parameter information in the user request is determined according to the target cloud environment interface identifier.
  • the corresponding standard format is converted and encapsulated, a resource access request is generated, and the resource access request is sent to the corresponding cloud environment interface;
  • the interface adaptation microserver is also set to: after receiving the response result returned by the cloud environment interface , and convert the response result into response information in a standard format for display to the user; the resource management microservice and the interface adaptation microserver interact through a northbound REST interface.
  • the microservice-based multi-cloud interface adaptation system described above wherein the number of the interface adaptation microservers is not less than 2, and the interface adaptation microservers are independent based on containers.
  • each interface adaptation microserver registers or deregisters with the API Gateway according to the following steps, and the API Gateway uniformly distributes the user requests it receives:
  • the existing interface adaptation microserver is judged to operate After the load exceeds the upper limit of the performance index, the registration of a new interface adaptation micro-server is triggered, and user requests are allocated to the new interface adaptation micro-server; the calculation of the existing interface adaptation micro-server is judged in N consecutive judgment cycles After the load is lower than the lower limit of the performance index, stop allocating user requests to the interface adaptation microserver with the lowest computing load, and trigger the logout of the interface adaptation microserver.
  • each of the interface adaptation micro-servers includes: a unified entry unit, the unified entry unit is defined with different The northbound REST interface of the resource is used to receive different user requests; the message processing unit, which interacts with the unified entry unit through the application program interface, is set to correspond to the standard request parameter information in the user request according to the target cloud environment interface identifier It is also set to: after receiving the response result returned by the cloud environment interface, convert the response result into a standard format Format of the response information.
  • Embodiments of the present application further provide a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, implements the microservice-based multi-cloud interface adaptation method described in any of the above. step.
  • Figure 1 shows an existing cloud management platform based on a single software architecture. It concentrates all functions in a war package, and has basically no external dependencies except the WEB container.
  • This architecture is an architecture with outstanding advantages and disadvantages: its advantages are centralized management, simple development, and no loss of distributed calls, but its disadvantages are also obvious: poor system robustness, severe coupling with the system, and flexible scalability Insufficient flexibility to meet the needs of rapid deployment.
  • an embodiment of the present application first provides a microservice-based multi-cloud interface adaptation system, which includes:
  • resource management microservice units set in the business layer are set to call the interface defined by the interface adaptation microserver after receiving the user request, and pass the interface identifier and standard request parameters with the target cloud environment to the interface adaptation microserver User requests for information;
  • the system also includes a number of container-based and horizontally scalable interface adaptation micro-servers.
  • Each interface adaptation microserver is set to: receive the call from the resource management microservice unit, convert and encapsulate the standard request parameter information contained in the user request according to the standard format corresponding to the target cloud environment interface identifier, and generate a resource access request , and send the resource access request to the corresponding cloud environment interface;
  • each interface adaptation micro-server is also set to: after receiving the response result returned by the cloud environment interface, convert the response result into response information in a standard format to for display to users.
  • the standard format corresponding to the response information here can be matched according to the cloud environment interface that returns the response result, or it can directly correspond to the third-party application or user UI module that calls the response information.
  • a common data standard between different countries, and the response result is converted according to the data standard.
  • the user UI module in the system is set to receive a request for accessing resources sent by the user terminal, and send the corresponding user request to the corresponding service component module.
  • An agent or API Gateway is generally set between the N resource management micro-service units in the background of the business component module and the UI.
  • the function is to provide the aggregation of background services for the foreground, provide a unified service outlet, and release the coupling between them;
  • the business component module in the system be set to receive and process the user request sent by the user UI module, and require that at least one target cloud environment interface identifier and the standard request parameter information corresponding to the resource requested thereof be carried in the above-mentioned request;
  • the interface adaptation micro-server is set to receive user requests sent by each service component module, and according to the cloud environment interface identifier and standard request parameter information carried in the request, according to the standard format required by different types of cloud environment interfaces, the standard request parameters
  • the information is converted and encapsulated, a resource access request is generated, and then the request is sent to the corresponding cloud environment interface;
  • the interface adaptation microserver is also set to convert the result into a standard after receiving the response result returned by the cloud environment interface
  • the response information in the format, so that the third-party application or user UI module can display the resource access request result to the user according to the response information.
  • the interface adaptation micro-server can be divided into two sub-units, namely: a unified entry unit and a message processing unit.
  • the unified entry unit defines the northbound (Northbound Interface, that is, the interface that accesses and manages the network for manufacturers or operators, that is, the interface provided upward) REST (Representational State Transfer) interface that matches various resources, such as, Cloud host related interfaces, cloud hard disk related interfaces, cloud mirroring related interfaces, etc., to receive different types of user requests;
  • Northbound Interface that is, the interface that accesses and manages the network for manufacturers or operators, that is, the interface provided upward
  • REST Real State Transfer
  • the message processing unit is responsible for processing the parameter information in the user request: determining the standard format of different cloud environment interfaces according to the target cloud environment interface identifier, and then encapsulating the standard request parameter information in the user request according to the standard format. , generate a resource access request, and then call the corresponding interface of the cloud environment interface to send the resource access request to the corresponding cloud.
  • the message processing unit after receiving the response structure data of the cloud environment interface to the request, the message processing unit also needs to The response structure of the interface is converted into response information in a unified standard format.
  • the interaction between the unified entry unit and the message processing unit can be realized by way of API (Application Programming Interface).
  • Step 1 After receiving the user request through the user UI, the business component of the business layer calls the interface defined by the unified entry unit in the interface adaptation microserver, and transmits the user request to the interface adaptation microserver to trigger the interface adaptation microserver. Internally perform steps 2 to 2 in response to the user request;
  • Step 2 After receiving the user request, the unified entry unit in the interface adaptation micro-server calls the API (Application Programming Interface) corresponding to the message processing unit, and triggers the message processing unit to process the parameters in the user request , convert and standardize it according to the standard format of the cloud environment interface corresponding to the user request, and generate a resource access request;
  • API Application Programming Interface
  • Step 3 the message processing unit sends a resource access request to the corresponding cloud environment interface according to the cloud environment interface identifier
  • Step 4 The message processing unit converts the response result returned by the cloud environment interface to a unified standard format, and returns the response information to the client.
  • Micro Service Architecture can decompose functions into discrete services, thereby reducing the coupling of the system and providing more flexible service support. Therefore, the above-mentioned several interface adaptation microservers based on the microservice mode architecture in this embodiment of the present application can extract and decouple the interface calling layer from the business layer, and publish it as a separate interface adaptation service, thereby realizing the independence of this module. Develop, manage and iterate.
  • the interface adaptation microserver used in the above solutions of the embodiments of the present application is a stateless microservice, which can be extended horizontally, and share traffic through multiple copies of the interface adaptation microserver, each of which is independently controlled by the container.
  • the operation unit executes, and realizes the above-mentioned processing of the corresponding parameters of the user request through the cooperative invocation of the CPU and the memory. Therefore, in other implementation manners, the embodiment of the present application can also provide the routing algorithm shown in FIG. 6 through the API Gateway set between the N resource management micro-service units and the UI in the background of the business component module, as shown in FIG. 5 .
  • the load balancing and fuse governance functions under the architecture realize the balanced distribution of client requests between different instances, ensuring that even if one of the microservices goes offline, it will not affect the normal operation of the system.
  • Upper and lower thresholds The upper and lower thresholds of performance indicators such as CPU usage and memory usage are used to judge the computing load of the existing interface adapting to the micro-server;
  • Judgment period the interval time for judging the operation load status
  • Number of index samples the number of judgment cycles to determine whether to trigger the elastic shrinkage.
  • the elastic shrinking mechanism is triggered after the computing load exceeds the upper or lower limit in the Nth consecutive judgment cycle;
  • the upper and lower limit of the number of replicas the upper and lower limit of the number of microservice replicas.
  • API Gateway is responsible for uniformly distributing all user requests and assumes the role of load balancer. All interface adaptation microserver copies need to be registered with API Gateway;
  • the monitoring of CPU and memory usage can be implemented by a performance monitoring task that is repeatedly triggered according to the judgment period; Check whether the frequency or duration of abnormal performance indicators reaches the set number of index samples; if not, the process of the elastic and shrinking check tasks ends, and returns to the performance monitoring task to continue monitoring in the next cycle; otherwise, go to To perform specific elastic and shrink tasks, automatically increase or decrease copies by registering or canceling.
  • the copies can be sorted according to the lowest CPU usage, and the system overhead can be reduced by automatic destruction.
  • the copy that has not been destroyed keeps the interface differences between the cloud environment interfaces of different cloud vendors in the following ways, so as to realize the sending and response to user requests:
  • Step 1 Receive the resource access request initiated by the user from the UI through the resource management microservice, such as creating a virtual machine, carrying parameters such as the virtual machine name, image ID, specification ID, network ID, etc., and then choose to call a certain interface according to the routing algorithm.
  • the resource management microservice such as creating a virtual machine, carrying parameters such as the virtual machine name, image ID, specification ID, network ID, etc., and then choose to call a certain interface according to the routing algorithm.
  • Step 3 Receive the corresponding user request through the unified entry unit in the interface adaptation micro-server;
  • Step 4 the unified entry unit calls the application program interface of the corresponding message processing unit to transmit the target cloud environment interface identifier and standard request parameter information corresponding to the above-mentioned user request;
  • Step 5 An abstract factory IBaseFactory is defined in the message processing unit, and the specific factory implementation is obtained according to the cloud environment interface type (DcType) corresponding to different target cloud environment interface identifiers, such as: OpenStackFactory/AliCloudFactory, etc.;
  • DcType cloud environment interface type
  • Step 5 After obtaining the response results of the different types of cloud environment interfaces to the user request, the message processing unit shields the differences between the different cloud environment interfaces by adapting the conversion between the response parameter information and the standard response parameter information , convert the response result into standard format response information. Therefore, for the upper-layer service, the upper-layer service can directly obtain an undifferentiated response through the operation of the message processing unit, thereby greatly improving the development efficiency.
  • the embodiments of the present application can address the problem that a single microservice cannot withstand high concurrent traffic in an actual production scenario.
  • the microservice is horizontally expanded according to the size of the business traffic, and multiple copies of the microservice are used to jointly bear the flow.
  • the implementation of threshold-based rules adopted in this embodiment of the present application can dynamically increase or decrease instances based on performance indicators such as CPU usage and memory usage, so as to increase or decrease the number of instances when the computing load is high.
  • the number of copies of the micro-server is allocated, and the traffic is shared by multiple copies of the micro-service; and the system overhead is reduced by reducing the number of copies of the interface to adapt to the micro-server when the operational compliance is low.
  • the embodiment of the present application provides a unified management interface service through the resource management microservice unit, replaces the traditional monolithic application by adapting the microserver through the interface of the microservice architecture, and performs corresponding transformation and corresponding transformation on the user request according to the interface of different target cloud environment. package.
  • the embodiments of the present application can shield interface differences between cloud environment interfaces of different cloud vendors, support rapid iterative deployment and horizontal expansion based on a micro-service architecture, and implement a set of tools to manage multiple clouds, simplify multi-cloud management operations, and reduce multi-cloud management. maintenance cost purposes.
  • the embodiment of the present application also dynamically manages the horizontal expansion of the microservice according to the size of the business traffic based on the API Gateway.
  • the embodiment of the present application adopts threshold-based rules, which can adapt the number of copies of the micro-server by increasing the interface when the computing load is high, and share the traffic through multiple copies of the micro-service; and when the computing load is relatively low At the same time, the system overhead is reduced by reducing the number of copies of the interface adaptation microserver.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种基于微服务的多云接口适配方法、系统及存储介质。该方法通过资源管理微服务单元提供统一的管理接口服务，通过采用微服务架构的接口适配微服务器替代传统的单体应用，针对不同目标云环境接口分别对用户请求进行相应的转换和封装。

Description

基于微服务的多云接口适配方法、系统及存储介质
相关申请的交叉引用
本申请基于申请号为202011612974.7、申请日为2020年12月30日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请实施例涉及云平台技术领域，具体而言涉及一种基于微服务的多云接口适配方法、系统及存储介质。
背景技术
随着云计算技术的发展，关于哪种云部署模型最适合组织一直存在着争论。越来越多的应用场景表明，由于每个企业、每个行业其需求及目标各不相同，依赖单一类型的云平台很难普适于全部应用情形。由此，“混合云”(Hybrid Cloud)和“多云”(Multi-Cloud)战略应运而生。
不管是多云还是混合云，其均需涉及多个独立的云环境。每个云提供商都有自己的一套用于关键运维任务的管理工具。各云平台之间，在云资源管理、云使用监控等等关键运维功能的运行、调取方式上均存在明显区别。对于企业管理员而言，其通常需要一个可以跨越多个云的、专注于运维任务的工具，才能满足其不同云平台之间的运维需求。
但是，在一些情形下多云平台间适配技术尚存在以下缺陷：
在一些情形下的多云平台间适配技术通常采用图1方式，基于单体软件架构实现。该在一些情形下云管理平台所有的功能都在一个war包中，除了WEB容器基本没有外部依赖。其需根据不同的厂商类型，分别针对各云平台构造不 同的请求体、调用不同的接口、再进行不同的业务逻辑处理。实际使用中，通常需部署冗余重复的代码，系统健壮性差、耦合严重、扩展性灵活性不足，并且不方便更新维护，无法满足快速部署的需求。
发明内容
有鉴于此，本申请实施例提供一种基于微服务的多云接口适配方法、系统及存储介质。
本申请实施例提出一种基于微服务的多云接口适配方法，其在接收到用户请求后，调用接口适配微服务器所定义的接口，向接口适配微服务器传递用户请求，以触发接口适配微服务器内部响应于所述用户请求执行以下步骤：对所述用户请求进行转换和封装，生成资源访问请求，向相应的云环境接口发送所述资源访问请求；在接收到云环境接口返回的响应结果后，将该响应结果转换为标准格式的响应信息，以供向用户展示。
同时，本申请实施例还提供一种基于微服务的多云接口适配系统，包括：资源管理微服务单元，被设置为在接收到用户请求后，调用接口适配微服务器所定义的接口，向接口适配微服务器传递具有目标云环境接口标识和标准请求参数信息的用户请求；所述接口适配微服务器被设置为：对所述用户请求中的标准请求参数信息按照目标云环境接口标识所对应的标准格式进行转换和封装，生成资源访问请求，向相应的云环境接口发送所述资源访问请求；所述接口适配微服务器还被设置为：在接收到云环境接口返回的响应结果后，将该响应结果转换为标准格式的响应信息，以供向用户展示；所述资源管理微服务与所述接口适配微服务器之间通过北向REST接口交互。
本申请实施例还提供一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时，实现如以上任一项所述的基于微服务的多云 接口适配方法的步骤。本申请实施例的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请实施例而了解。
附图说明
附图用来提供对本申请实施例的进一步理解，并且构成说明书的一部分，并与本申请实施例的实施例一起，用于解释本申请实施例，并不构成对本申请实施例的限制。在附图中：
图1是已有单体架构方式下的多云平台间适配方式示意图；
图2是本申请实施例的基于微服务的多云接口适配系统示意图；
图3是本申请实施例的基于微服务的多云接口适配方法中接口适配微服务器调用时序图；
图4是使用本申请实施例的基于微服务的多云接口适配方法的流程示意图；
图5是本申请实施例的基于微服务的多云接口适配系统中基于微服务实现水平扩展的示意图；
图6为实现图5所示水平扩展功能的步骤流程示意图。
具体实施方式
为使本申请实施例的目的和技术方案更加清楚，下面将结合本申请实施例的附图，对本申请实施例的技术方案进行清楚、完整地描述。显然，所描述的实施例是本申请实施例的一部分实施例，而不是全部的实施例。基于所描述的本申请的实施例，本领域普通技术人员在无需创造性劳动的前提下所获得的所有其他实施例，都属于本申请保护的范围。
本技术领域技术人员可以理解，除非另外定义，这里使用的所有术语(包括技术术语和科学术语)具有与本申请实施例所属领域中的普通技术人员的一 般理解相同的意义。还应该理解的是，诸如通用字典中定义的那些术语应该被理解为具有与现有技术的上下文中的意义一致的意义，并且除非像这里一样定义，不会用理想化或过于正式的含义来解释。
本申请实施例中所述的“连接”的含义可以是部件、单元之间的直接连接也可以是部件、单元间通过其它部件的间接连接。
本申请实施例提出一种基于微服务的多云接口适配方法，其在接收到用户请求后，调用接口适配微服务器所定义的接口，向接口适配微服务器传递用户请求，以触发接口适配微服务器内部响应于所述用户请求执行以下步骤：对所述用户请求进行转换和封装，生成资源访问请求，向相应的云环境接口发送所述资源访问请求；在接收到云环境接口返回的响应结果后，将该响应结果转换为标准格式的响应信息，以供向用户展示。
在一些实施例中，如上任一所述的基于微服务的多云接口适配方法，其中，所述接口适配微服务器中设置有：统一入口单元，所述统一入口单元定义有分别针对不同资源的北向REST接口以接收不同用户请求。
在一些实施例中，如上任一所述的基于微服务的多云接口适配方法，其中，所述用户请求中包含：至少一个目标云环境接口标识，以及对应于所请求的资源的标准请求参数信息。
在一些实施例中，如上任一所述的基于微服务的多云接口适配方法，其中，所述接口适配微服务器中还设置有：消息处理单元；所述消息处理单元被设置为：对所述用户请求中的标准请求参数信息按照目标云环境接口标识所对应的标准格式进行转换和封装，生成资源访问请求，向相应的云环境接口发送所述资源访问请求；所述消息处理单元还被设置为：在接收到云环境接口返回的响 应结果后，将该响应结果转换为标准格式的响应信息，所述标准格式与返回响应结果的云环境接口相匹配。
在一些实施例中，如上任一所述的基于微服务的多云接口适配方法，其中，所述统一入口单元在接收到用户请求后，调用对应于所述消息处理单元的应用程序接口以传递相应的目标云环境接口标识和标准请求参数信息。
在一些实施例中，如上任一所述的基于微服务的多云接口适配方法，其中，所述接口适配微服务器具有多个副本，各副本分别由各自独立的运算单元执行，各副本均按照以下步骤向API Gateway注册或注销，并由API Gateway统一分配其所接收的用户请求：在连续的N个判决周期均判断现有副本的运算负荷超出性能指标上限后，触发注册新的副本，并向所述新的副本分配用户请求；在连续的N个判决周期均判断现有副本的运算负荷低于性能指标下限后，停止向运算负荷最低的副本分配用户请求，并触发注销该副本。
同时，本申请实施例还提供一种基于微服务的多云接口适配系统，包括：资源管理微服务单元，被设置为在接收到用户请求后，调用接口适配微服务器所定义的接口，向接口适配微服务器传递具有目标云环境接口标识和标准请求参数信息的用户请求；所述接口适配微服务器被设置为：对所述用户请求中的标准请求参数信息按照目标云环境接口标识所对应的标准格式进行转换和封装，生成资源访问请求，向相应的云环境接口发送所述资源访问请求；所述接口适配微服务器还被设置为：在接收到云环境接口返回的响应结果后，将该响应结果转换为标准格式的响应信息，以供向用户展示；所述资源管理微服务与所述接口适配微服务器之间通过北向REST接口交互。
在一些实施例中，如上任一所述的基于微服务的多云接口适配系统，其中， 所述接口适配微服务器的数量不低于2个，各接口适配微服务器之间基于容器独立运行，各接口适配微服务器均按照以下步骤向API Gateway注册或注销，并由API Gateway统一分配其所接收的用户请求：在连续的N个判决周期均判断现有接口适配微服务器的运算负荷超出性能指标上限后，触发注册新的接口适配微服务器，并向所述新的接口适配微服务器分配用户请求；在连续的N个判决周期均判断现有接口适配微服务器的运算负荷低于性能指标下限后，停止向运算负荷最低的接口适配微服务器分配用户请求，并触发注销该接口适配微服务器。
在一些实施例中，如上任一所述的基于微服务的多云接口适配系统，其中，每一个所述接口适配微服务器均包括：统一入口单元，所述统一入口单元定义有分别针对不同资源的北向REST接口以接收不同用户请求；消息处理单元，其通过应用程序接口与所述统一入口单元交互，被设置为对所述用户请求中的标准请求参数信息按照目标云环境接口标识所对应的标准格式进行转换和封装，生成资源访问请求，向相应的云环境接口发送所述资源访问请求；还被设置为：在接收到云环境接口返回的响应结果后，将该响应结果转换为标准格式的响应信息。
本申请实施例还提供一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时，实现如以上任一项所述的基于微服务的多云接口适配方法的步骤。
图1为已有的基于单体软件架构的云管理平台。其将所有的功能都集中在一个war包中，除了WEB容器以外基本没有外部依赖。这种架构是一种优缺点都很突出的架构：其优点是集中式管理、开发简单、没有分布式调用的损耗， 但是其缺点也很明显：系统健壮性差、与系统耦合严重、扩展性灵活性不够，因而无法满足快速部署的需求。
参考图2，本申请实施例首先提供一种基于微服务的多云接口适配系统，其包括：
若干设置在业务层的资源管理微服务单元，被设置为在接收到用户请求后，调用接口适配微服务器所定义的接口，向接口适配微服务器传递具有目标云环境接口标识和标准请求参数信息的用户请求；
该系统还包括若干基于容器运行，且可水平扩展的接口适配微服务器。各接口适配微服务器被设置为：接收资源管理微服务单元的调用，对用户请求中所包含的标准请求参数信息按照目标云环境接口标识所对应的标准格式进行转换和封装，生成资源访问请求，向相应的云环境接口发送所述资源访问请求；各接口适配微服务器还被设置为：在接收到云环境接口返回的响应结果后，将该响应结果转换为标准格式的响应信息，以供向用户展示。这里响应信息所对应的标准格式可以根据返回响应结果的云环境接口而相应进行匹配，也可直接对应于调取响应信息的第三方应用或者用户UI模块，设置一个在各应用各用户UI模块之间通用的数据标准，依据该数据标准转换响应结果。
如图2所示，该系统中的用户UI模块：被设置为接收用户端发送的访问资源的请求,并将对应的用户请求发送至对应的业务组件模块。
业务组件模块后台中的N个资源管理微服务单元和UI之间一般会设置一个代理或者叫API Gateway，作用是为前台提供后台服务的聚合，提供统一的服务出口，解除他们之间的耦合；
该系统中的业务组件模块：被设置为接收并处理用户UI模块所发送的用 户请求，要求上述请求中至少携带一个目标云环境接口标识以及与其所请求的资源相对应的标准请求参数信息；
接口适配微服务器被设置为接收各业务组件模块所发送的用户请求，根据请求中所携带的云环境接口标识和标准请求参数信息，按不同类型云环境接口接口所需标准格式对标准请求参数信息进行转换和封装，生成资源访问请求，然后将该请求发送至对应的云环境接口；接口适配微服务器还被设置为在接收到云环境接口返回的响应结果后,将该结果转换为标准格式的响应信息,以便第三方应用或者用户UI模块根据该响应信息向用户展示资源访问请求结果。
其中的接口适配微服务器具体又可以划分为两个子单元，分别是：统一入口单元和消息处理单元。
其中，统一入口单元定义了匹配于各种资源的北向(Northbound Interface，即，为厂家或运营商进行接入和管理网络的接口，即向上提供的接口)REST(Representational State Transfer)接口，如，云主机相关接口，云硬盘相关接口、云镜像相关接口等，以接收不同类型的用户请求；
其中的消息处理单元，则负责对用户请求中的参数信息进行处理：分别按照目标云环境接口标识确定不同云环境接口的标准格式，然后根据该标准格式对用户请求中的标准请求参数信息进行封装，生成资源访问请求，然后调用云环境接口的相应接口，向相应的云端发送所述资源访问请求，此外在接收到云环境接口对请求的响应结构数据后，消息处理单元还需要将不同云环境接口的响应结构转换为统一的标准格式的响应信息。统一入口单元和消息处理单元之间可具体通过API(Application Programming Interface，应用程序接口)方式实现交互。
该系统的具体运行时序可参照图3所示，通过如下步骤进行：
步骤1：业务层的业务组件在通过用户UI接收到用户请求后，调用接口适配微服务器中统一入口单元所定义的接口，向接口适配微服务器传递用户请求，以触发接口适配微服务器内部响应于所述用户请求执行步骤2至步骤；
步骤2：接口适配微服务器中的统一入口单元在接收到用户请求后，调用消息处理单元所对应的API(Application Programming Interface，应用程序接口)，触发消息处理单元对用户请求中的参数进行处理，将其按照用户请求所对应的云环境接口的标准格式进行转换和标准化封装，生成资源访问请求；
步骤3：消息处理单元根据云环境接口标识向对应的云环境接口发送资源访问请求；
步骤4：消息处理单元对云环境接口返回的响应结果进行统一的标准格式的转换，将响应信息返回给客户端。
由于微服务架构(Micro Service Architecture)可以将功能分解到离散的各个服务当中，从而降低系统的耦合性，并提供更加灵活的服务支持。因此，本申请实施例基于微服务方式架构的上述若干个接口适配微服务器可以将接口调用层从业务层面抽取并解耦，作为单独的接口适配服务发布，从而实现对这一模块的独立开发、管理和迭代。
本申请实施例上述方案中所使用的接口适配微服务器是一个无状态微服务，其可进行水平扩展，通过多个接口适配微服务器副本共同承担流量，各副本分别由容器中各自独立的运算单元执行，通过CPU和内存的协同调用实现上述用户请求对应参数的处理。因此，在其他实现方式下，本申请实施例还可以通过图6所示的路由算法，通过业务组件模块后台中N个资源管理微服务单元 和UI之间所设置的API Gateway提供图5所示架构下的负载均衡、熔断治理功能，实现客户端请求在不同实例之间的均衡分配，保证即使在其中某一个微服务出现问题下线的情况下，也能不会影响系统的正常运行。
其具体实现步骤如下：
1：在系统启动阶段，设置多云适配微服务弹缩策略参数，设置相应的对应于CPU使用率、内存使用率的性能指标的上下限阈值，设置判决周期，设置指标样本数N，以及接口适配微服务器副本数量的上下限等参数。考虑到初始状态下流量相对较小，因此一般仅需要向API Gateway注册一个副本由API Gateway统一分配其所接收的用户请求至该副本就可以处理业务流量；
上述各参数可具体定义如下：
上下限阈值：应于CPU使用率、内存使用率等性能指标的上限数值和下限数值，用于判断现有接口适配微服务器的运算负荷；
判决周期：判断运算负荷状况的间隔时间；
指标样本数：决定是否需要触发弹缩的判决周期个数，在连续第N个判决周期均判断运算负荷超过上限或下限后触发弹缩机制；
副本数上下限：微服务副本数量的上下限。
2：由API Gateway负责统一分发所有用户请求，承担负载均衡器的角色，所有接口适配微服务器副本均需要向API Gateway注册；
3：执行性能监控任务，监控副本的CPU、内存使用率，以便在外部用户请求增多，单个接口适配微服务器副本负载过高时，经过N个判决周期的判断，确定CPU使用率达到上限阈值的次数已经达到指标样本数N后触发弹缩机制，自动向API Gateway注册以扩展新副本，由API Gateway向所述新的接口适配 微服务器分配用户请求以对外部流量进行分流；而与之对应地，在连续的N个判决周期均判断现有接口适配微服务器的运算负荷低于性能指标下限后，停止向运算负荷最低的接口适配微服务器分配用户请求，并触发注销该接口适配微服务器。
具体流程如附图6所示，上述弹缩机制中可分别将：对CPU、内存使用率的监控以一个被反复按照判决周期被触发的性能监控任务实现；性能监控任务判断异常后触发执行弹缩检查任务，检查性能指标出现异常的频度或持续时间是否达到设置的指标样本数；若未达到，则弹缩检查任务流程结束，返回执行性能监控任务，继续下一个周期的监控；否则转至执行具体的弹缩任务，自动通过注册或注销而相应的增加或者减少副本。副本具体可按照CPU使用率最低排序，通过自动销毁方式降低系统开销。而未被销毁的副本则保持通过以下方式屏蔽不同云厂商云环境接口之间的接口差异，实现对用户请求的发送和响应：
步骤1：通过资源管理微服务接收用户从UI发起的资源访问请求，如创建虚拟机，携带参数如虚拟机名称、镜像ID、规格ID、网络ID等，然后根据路由算法选择调用某个接口适配微服务器统一入口单元定义的北向REST接口；
步骤3：通过接口适配微服务器中的统一入口单元接收相应的用户请求；
步骤4：统一入口单元调用对应消息处理单元的应用程序接口以传递对应于上述用户请求的目标云环境接口标识和标准请求参数信息；
步骤5：消息处理单元中定义了一个抽象工厂IBaseFactory，根据不同目标云环境接口标识所对应的云环境接口类型(DcType)获取到具体的工厂实现，如：OpenStackFactory/AliCloudFactory等；
消息处理单元的具体工厂实现中，定义了各类资源的具体实现类，比如 CreateInstanceImpl、CreateImageImpl、CreateVolumeImpl等，这些实现类负责将用户请求中对应的标准请求参数信息构造成对应目标云环境接口类型的标准请求体，生成资源访问请求，然后调用对应于目标云环境接口的接口，向相应的云环境接口发送所述资源访问请求；
步骤5：消息处理单元还在获取到不同类型云环境接口的对用户请求的响应结果后，通过适配响应参数信息与标准响应参数信息之间的转换，屏蔽不同云环境接口之间的差异性，将该响应结果转换为标准格式的响应信息。由此，对于上层服务而言，上层服务可通过消息处理单元的运算而直接获取到无差别的响应，从而大大提升开发的效率。
由此，本申请实施例可以针对实际生产场景下，单个微服务承受不住高并发流量的问题，在一些实施例中根据业务流量的大小对微服务进行水平扩展，使用多个微服务副本共同承担流量。本申请实施例所采用的基于阈值的规则(threshold-based rules)实现方式，可基于CPU使用率、内存使用率等性能指标，动态增加或减少实例，以在运算负荷较高时通过增加接口适配微服务器的副本数量，通过多个微服务副本共同承担流量；而在运算符合较低时通过减少接口适配微服务器的副本数量降低系统开销。
本申请实施例通过资源管理微服务单元提供统一的管理接口服务，通过采用微服务架构的接口适配微服务器替代传统的单体应用，针对不同目标云环境接口分别对用户请求进行相应的转换和封装。本申请实施例能够屏蔽不同云厂商云环境接口之间的接口差异，并支持基于微服务架构的快速迭代部署、水平扩展，能够实现一套工具管理多个云，达到简化多云管理操作，降低多云维护成本的目的。
此外，考虑到单个微服务往往承受不住高并发，因此，本申请实施例还基于API Gateway根据业务流量的大小对微服务的水平扩展进行动态管理。本申请实施例采用基于阈值的规则(threshold-based rules)，可以在运算负荷较高时通过增加接口适配微服务器的副本数量，通过多个微服务副本共同承担流量；而在运算符合较低时通过减少接口适配微服务器的副本数量降低系统开销。
以上仅为本申请实施例的实施方式，其描述较为具体和详细，但并不能因此而理解为对本申请实施例专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请实施例构思的前提下，还可以做出若干变形和改进，这些均属于本申请实施例的保护范围。

Claims (10)

  1. 一种基于微服务的多云接口适配方法，包括：
    在接收到用户请求后，调用接口适配微服务器所定义的接口，向接口适配微服务器传递用户请求，以触发接口适配微服务器内部响应于所述用户请求执行以下步骤：
    对所述用户请求进行转换和封装，生成资源访问请求，向相应的云环境接口发送所述资源访问请求；
    在接收到云环境接口返回的响应结果后，将该响应结果转换为标准格式的响应信息，以供向用户展示。
  2. 如权利要求1所述的基于微服务的多云接口适配方法，其中，所述接口适配微服务器中设置有：统一入口单元，所述统一入口单元定义有分别针对不同资源的北向REST接口以接收不同用户请求。
  3. 如权利要求2所述的基于微服务的多云接口适配方法，其中，所述用户请求中包含：至少一个目标云环境接口标识，以及对应于所请求的资源的标准请求参数信息。
  4. 如权利要求3所述的基于微服务的多云接口适配方法，其中，所述接口适配微服务器中还设置有：消息处理单元；
    所述消息处理单元被设置为：对所述用户请求中的标准请求参数信息按照目标云环境接口标识所对应的标准格式进行转换和封装，生成资源访问请求，相应的向该目标云环境接口标识所对应的云环境接口发送所述资源访问请求；
    所述消息处理单元还被设置为：在接收到云环境接口返回的响应结果后，将该响应结果转换为标准格式的响应信息，所述标准格式与返回响应结果的云环境接口相匹配。
  5. 如权利要求4所述的基于微服务的多云接口适配方法，其中，所述统一入口单元在接收到用户请求后，调用对应于所述消息处理单元的应用程序接口以传递相应的目标云环境接口标识和标准请求参数信息。
  6. 如权利要求1所述的基于微服务的多云接口适配方法，其中，所述接口适配微服务器具有多个副本，各副本分别由各自独立的运算单元执行，各副本均按照以下步骤向API Gateway注册或注销，并由API Gateway统一分配其所接收的用户请求：
    在连续的N个判决周期均判断现有副本的运算负荷超出性能指标上限后，触发注册新的副本，并向所述新的副本分配用户请求；
    在连续的N个判决周期均判断现有副本的运算负荷低于性能指标下限后，停止向运算负荷最低的副本分配用户请求，并触发注销该副本。
  7. 一种基于微服务的多云接口适配系统，包括：
    资源管理微服务单元，被设置为在接收到用户请求后，调用接口适配微服务器所定义的接口，向接口适配微服务器传递具有目标云环境接口标识和标准请求参数信息的用户请求；
    所述接口适配微服务器被设置为：对所述用户请求中的标准请求参数信息按照目标云环境接口标识所对应的标准格式进行转换和封装，生成资源访问请求，向相应的云环境接口发送所述资源访问请求；所述接口适配微服务器还被设置为：在接收到云环境接口返回的响应结果后，将该响应结果转换为标准格式的响应信息，以供向用户展示；
    所述资源管理微服务与所述接口适配微服务器之间通过北向REST接口交互。
  8. 如权利要求7所述的基于微服务的多云接口适配系统，其中，所述接口适配微服务器的数量不低于2个，各接口适配微服务器之间基于容器独立运行，各接口适配微服务器均按照以下步骤向API Gateway注册或注销，并由API Gateway统一分配其所接收的用户请求：
    在连续的N个判决周期均判断现有接口适配微服务器的运算负荷超出性能指标上限后，触发注册新的接口适配微服务器，并向所述新的接口适配微服务器分配用户请求；
    在连续的N个判决周期均判断现有接口适配微服务器的运算负荷低于性能指 标下限后，停止向运算负荷最低的接口适配微服务器分配用户请求，并触发注销该接口适配微服务器。
  9. 如权利要求7所述的基于微服务的多云接口适配系统，其中，每一个所述接口适配微服务器均包括：
    统一入口单元，定义有分别针对不同资源的北向REST接口以接收不同用户请求；
    消息处理单元，其通过应用程序接口与所述统一入口单元交互，被设置为对所述用户请求中的标准请求参数信息按照目标云环境接口标识所对应的标准格式进行转换和封装，生成资源访问请求，向相应的云环境接口发送所述资源访问请求；所述消息处理单元还被设置为：在接收到云环境接口返回的响应结果后，将该响应结果转换为标准格式的响应信息。
  10. 一种计算机可读存储介质，其中，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时，实现如权利要求1至6任一项所述的基于微服务的多云接口适配方法的步骤。
PCT/CN2021/142052 2020-12-30 2021-12-28 基于微服务的多云接口适配方法、系统及存储介质 WO2022143653A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP21914387.2A EP4270204A4 (en) 2020-12-30 2021-12-28 METHOD AND SYSTEM FOR ADJUSTING A MULTI-CLOUD INTERFACE BASED ON A MICROSERVICE AND STORAGE MEDIUM

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011612974.7 2020-12-30
CN202011612974.7A CN114691567A (zh) 2020-12-30 2020-12-30 基于微服务的多云接口适配方法、系统及存储介质

Publications (1)

Publication Number Publication Date
WO2022143653A1 true WO2022143653A1 (zh) 2022-07-07

Family

ID=82131874

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/142052 WO2022143653A1 (zh) 2020-12-30 2021-12-28 基于微服务的多云接口适配方法、系统及存储介质

Country Status (3)

Country Link
EP (1) EP4270204A4 (zh)
CN (1) CN114691567A (zh)
WO (1) WO2022143653A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115168061A (zh) * 2022-09-09 2022-10-11 北京镜舟科技有限公司 一种计算存储分离方法、系统、电子设备及存储介质
CN115883405A (zh) * 2022-11-25 2023-03-31 上海浦东发展银行股份有限公司 一种服务检测系统
TWI826182B (zh) * 2022-12-13 2023-12-11 奔騰網路科技股份有限公司 雲平台管理系統

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115550093A (zh) * 2022-09-13 2022-12-30 海尔优家智能科技（北京）有限公司 应用调研方法、存储介质及电子装置
CN116708552B (zh) * 2022-09-30 2024-06-18 腾讯云计算（北京）有限责任公司 一种地铁微服务注册方法、装置、设备及可读存储介质
CN116010126B (zh) * 2023-02-09 2023-06-27 中国证券登记结算有限责任公司 一种服务聚合方法、装置及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170213174A1 (en) * 2016-01-16 2017-07-27 International Business Machines Corporation Order optimization in hybrid cloud networks
CN107659624A (zh) * 2017-09-06 2018-02-02 国云科技股份有限公司 一种适用于云计算的异构云管理系统及方法
CN108449418A (zh) * 2018-03-29 2018-08-24 新华三云计算技术有限公司 一种混合云平台管理系统及方法
CN109561147A (zh) * 2018-11-30 2019-04-02 武汉烽火信息集成技术有限公司 一种异构云管理方法及系统、异构云管理系统构建方法
CN111858101A (zh) * 2020-07-28 2020-10-30 平安医疗健康管理股份有限公司 面向云架构系统的适配方法、装置、设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170213174A1 (en) * 2016-01-16 2017-07-27 International Business Machines Corporation Order optimization in hybrid cloud networks
CN107659624A (zh) * 2017-09-06 2018-02-02 国云科技股份有限公司 一种适用于云计算的异构云管理系统及方法
CN108449418A (zh) * 2018-03-29 2018-08-24 新华三云计算技术有限公司 一种混合云平台管理系统及方法
CN109561147A (zh) * 2018-11-30 2019-04-02 武汉烽火信息集成技术有限公司 一种异构云管理方法及系统、异构云管理系统构建方法
CN111858101A (zh) * 2020-07-28 2020-10-30 平安医疗健康管理股份有限公司 面向云架构系统的适配方法、装置、设备及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4270204A4 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115168061A (zh) * 2022-09-09 2022-10-11 北京镜舟科技有限公司 一种计算存储分离方法、系统、电子设备及存储介质
CN115168061B (zh) * 2022-09-09 2022-12-20 北京镜舟科技有限公司 一种计算存储分离方法、系统、电子设备及存储介质
CN115883405A (zh) * 2022-11-25 2023-03-31 上海浦东发展银行股份有限公司 一种服务检测系统
TWI826182B (zh) * 2022-12-13 2023-12-11 奔騰網路科技股份有限公司 雲平台管理系統

Also Published As

Publication number Publication date
EP4270204A1 (en) 2023-11-01
EP4270204A4 (en) 2024-02-21
CN114691567A (zh) 2022-07-01

Similar Documents

Publication Publication Date Title
WO2022143653A1 (zh) 基于微服务的多云接口适配方法、系统及存储介质
US10701139B2 (en) Life cycle management method and apparatus
US11088944B2 (en) Serverless packet processing service with isolated virtual network integration
US10044622B2 (en) Load balancing for a virtual networking system
US11936724B2 (en) Configuring service mesh networking resources for dynamically discovered peers or network functions
WO2019233273A1 (zh) 管理容器服务的方法和装置
US10397132B2 (en) System and method for granting virtualized network function life cycle management
AU2014278314A1 (en) Distributed lock management in a cloud computing environment
CN113596110A (zh) 一种面向异构云的云原生微服务平台
WO2017185251A1 (zh) Vnfm的确定方法和网络功能虚拟化编排器
CN111949364A (zh) 容器化vnf的部署方法和相关设备
WO2020103925A1 (zh) 一种容器化虚拟网络功能的部署方法和装置
WO2017161562A1 (zh) 网络功能虚拟化环境下应用的管理方法和装置
WO2019047835A1 (zh) 虚拟网络功能的实例化方法
US11082343B2 (en) Client connection failover
US20220398119A1 (en) Apparatus and method for providing virtual multi-cloud service
WO2022140945A1 (zh) 容器集群的管理方法和装置
WO2020108443A1 (zh) 一种虚拟化管理方法及装置
US20200403912A1 (en) Serverless packet processing service with configurable exception paths
CN112015515B (zh) 一种虚拟网络功能的实例化方法及装置
CN112073449B (zh) 基于Kubernetes的环境切换处理方法和设备
US20230205505A1 (en) Computer system, container management method, and apparatus
WO2023066224A1 (zh) 一种部署容器服务的方法及装置
CN112073358B (zh) 基于Kubernetes的协议转换处理方法和设备
CN116668467A (zh) 一种资源访问方法、装置、云托管系统及电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21914387

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021914387

Country of ref document: EP

Effective date: 20230728