CN116795548A

CN116795548A - Interface processing method, device and system based on multi-cloud management and storage medium

Info

Publication number: CN116795548A
Application number: CN202310749474.5A
Authority: CN
Inventors: 李广聚; 陈继秋; 谢继刚; 张龙涛
Original assignee: China United Network Communications Group Co Ltd; Unicom Digital Technology Co Ltd; Unicom Cloud Data Co Ltd; China Unicom Western Innovation Research Institute Co Ltd
Current assignee: China United Network Communications Group Co Ltd; Unicom Digital Technology Co Ltd; Unicom Cloud Data Co Ltd; China Unicom Western Innovation Research Institute Co Ltd
Priority date: 2023-06-21
Filing date: 2023-06-21
Publication date: 2023-09-22

Abstract

The application provides an interface processing method, device, system and storage medium based on multi-cloud management, relating to the technical field of cloud computing, wherein the method comprises the following steps: the method comprises the steps of receiving an access request for accessing a cloud quotient interface to be accessed, which is sent by a service system, acquiring parameter data of the cloud quotient interface to be accessed from a yaml file according to a request parameter of the access request, acquiring an IP and a port of the cloud quotient interface to be accessed from cloud quotient management information according to the request parameter of the access request, accessing the cloud quotient interface to be accessed according to the access request, the parameter data and the IP and the port of the cloud quotient interface to be accessed, acquiring response parameters returned by the cloud quotient interface to be accessed, and sending the response parameters to the service system. According to the technical scheme, the parameter data of each cloud quotient interface is defined through the yaml file, so that the processing time and labor cost are effectively saved, and the processing efficiency is improved.

Description

Interface processing method, device and system based on multi-cloud management and storage medium

Technical Field

The present application relates to the field of cloud computing technologies, and in particular, to an interface processing method, device, system, and storage medium based on multi-cloud management.

Background

In the present cloud computing era, enterprises often choose to use cloud platforms of multiple cloud service providers to meet different requirements and business scenarios. In order to enable enterprises to more efficiently manage and utilize resources of multiple cloud service providers, multiple cloud management platforms have evolved.

The multi-cloud management platform is a tool or platform for uniformly managing and coordinating a plurality of cloud service providers, and the interface docking layer is an important part of the multi-cloud management platform and is mainly used for solving the differences of the access modes of resource interfaces of the cloud service providers, versions of the interfaces, data interfaces of the interfaces and the like. When an enterprise uses the cloud platform of a cloud service provider, a cloud service provider interface of the cloud service provider can be requested to a multi-cloud management platform through a business system of the enterprise, and the multi-cloud management platform interacts with the cloud service provider interface through an interface docking layer after receiving the request, so that the business system can access the cloud platform of the cloud service provider through the cloud service provider interface.

However, in the prior art, parameter definition needs to be modified by manually modifying codes, so that the processing efficiency is low and the labor cost is high.

Disclosure of Invention

The application provides an interface processing method, device and system based on multi-cloud management and a storage medium, which are used for solving the problems of lower processing efficiency and higher labor cost in the prior art when parameter definition is modified.

In a first aspect, the present application provides a method for processing an interface based on multi-cloud management, including:

receiving an access request sent by a service system and used for accessing a cloud provider interface;

according to the request parameters of the access request, acquiring parameter data of the cloud quotient interface to be accessed from a yaml file, wherein the parameter data comprises a request address, a request header parameter, a request parameter definition, a response parameter definition and an asynchronous response parameter definition;

according to the request parameters of the access request, the IP and the port of the cloud quotient interface to be accessed are obtained from cloud quotient nano-tube information, wherein the cloud quotient nano-tube information comprises the IP and the port of each cloud quotient interface;

accessing the cloud Shang Jiekou to be accessed according to the access request, the parameter data and the IP and the port of the cloud provider interface to be accessed;

acquiring response parameters returned by the cloud provider interface to be accessed;

and sending the response parameters to the service system.

In one possible implementation manner, the accessing the cloud provider interface to be accessed according to the access request, the parameter data and the IP and the port of the cloud provider interface to be accessed includes:

according to the request parameter definition, converting a parameter format of the request parameter of the access request into a parameter format corresponding to the cloud quotient interface to be accessed;

And accessing the cloud quotient interface to be accessed according to the converted request parameters, the parameter data and the IP and the port of the cloud quotient interface to be accessed.

In one possible implementation manner, when the cloud provider interface to be accessed is an asynchronous interface, the obtaining the response parameter returned by the cloud provider interface to be accessed includes:

and acquiring response parameters from a cloud quotient message queue corresponding to the cloud quotient interface to be accessed, wherein the cloud quotient message queue is used for storing data which are generated by the cloud quotient interface to be accessed and are to be sent.

In a possible implementation manner, the obtaining the response parameter from the cloud quotient message queue corresponding to the cloud quotient interface to be accessed includes:

monitoring the cloud quotient message queues corresponding to the cloud quotient interfaces to be accessed according to connection information and queue information, wherein the connection information is used for representing the connection relation between each cloud quotient message queue and each cloud quotient interface, and the queue information is used for representing the type of each cloud quotient message queue;

and acquiring the response parameters when the response parameters of the cloud quotient message queue are monitored.

In one possible implementation manner, the sending the response parameter to the service system includes:

Converting the parameter format of the response parameter into a parameter format corresponding to the service system;

and sending the converted response parameters to the service system.

In one possible implementation manner, when the cloud provider interface to be accessed is an asynchronous interface, the converting the parameter format of the response parameter into the parameter format corresponding to the service system includes:

analyzing the response parameters to obtain request identification numbers (IDs) of the response parameters;

determining interface information corresponding to the response parameters according to the request ID of the response parameters;

according to the interface information, determining asynchronous response parameter definition in a yaml file corresponding to the interface information;

and according to the asynchronous response parameter definition, converting the parameter format of the response parameter into the parameter format corresponding to the service system.

In one possible implementation, the method further includes:

receiving a queue processing instruction, wherein the queue processing instruction is used for indicating to execute at least one of the following processes on a target cloud quotient message queue: inquiring monitoring state, stopping monitoring, restarting monitoring and starting monitoring;

and executing the processing corresponding to the queue processing instruction on the target cloud quotient message queue.

In one possible implementation, the method further includes:

receiving yaml file processing instructions for performing at least one of the following on parameter data in a target yaml file: adding, deleting, modifying and inquiring;

and executing the processing corresponding to the yaml file processing instruction on the target yaml file.

In one possible implementation, the method further includes:

abstracting the resource pool environment of each cloud service provider into a corresponding cloud Shang Jiekou;

and configuring each cloud quotient interface according to the cloud quotient nano-tube information.

In a possible implementation manner, the configuring each cloud provider interface according to the cloud provider nanotube information includes:

and configuring IP, port, tenant information, corresponding yaml file, corresponding connection information and queue information of the cloud business message queues of each cloud business interface according to the cloud business management information.

In a second aspect, the present application provides an interface processing system based on multi-cloud management, including:

the receiving module is used for receiving an access request which is sent by the service system and used for accessing the cloud provider interface;

the first acquisition module is used for acquiring parameter data of the cloud quotient interface to be accessed from a yaml file according to the request parameter of the access request, wherein the parameter data comprises a request address, a request header parameter, a request parameter definition, a response parameter definition and an asynchronous response parameter definition;

The second acquisition module is used for acquiring the IP and the port of the cloud quotient interface to be accessed from cloud quotient nano-tube information according to the request parameters of the access request, wherein the cloud quotient nano-tube information comprises the IP and the port of each cloud quotient interface;

the access module is used for accessing the cloud Shang Jiekou to be accessed according to the access request, the parameter data and the IP and the port of the cloud quotient interface to be accessed;

the third acquisition module is used for acquiring response parameters returned by the cloud quotient interface to be accessed;

and the sending module is used for sending the response parameters to the service system.

In one possible implementation manner, the access module is specifically configured to:

In one possible implementation manner, when the cloud provider interface to be accessed is an asynchronous interface, the third obtaining module is specifically configured to:

In one possible implementation manner, the third obtaining module is specifically configured to:

In one possible implementation manner, the sending module is specifically configured to:

and sending the converted response parameters to the service system.

In one possible implementation manner, when the cloud provider interface to be accessed is an asynchronous interface, the sending module is specifically configured to:

In one possible implementation manner, the interface processing system based on multi-cloud management further includes:

the receiving module is further configured to receive a queue processing instruction, where the queue processing instruction is configured to instruct to perform at least one of the following processing on the target cloud quotient message queue: inquiring monitoring state, stopping monitoring, restarting monitoring and starting monitoring;

and the processing module is used for executing the processing corresponding to the queue processing instruction on the target cloud quotient message queue.

In a possible implementation manner, the receiving module is further configured to receive a yaml file processing instruction, where the yaml file processing instruction is configured to perform at least one of the following processing on parameter data in the target yaml file: adding, deleting, modifying and inquiring;

the processing module is further used for executing processing corresponding to the yaml file processing instruction on the target yaml file.

In one possible implementation, the processing module is further configured to:

In a possible implementation manner, the processing module is specifically configured to:

In a third aspect, the present application provides an electronic device comprising: a processor, a transceiver, a memory and computer program instructions stored on the memory and executable on the processor for implementing the method provided by the first aspect and each possible design when the computer program instructions are executed by the processor.

In a fourth aspect, the application may provide a computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method of the first aspect and each of the possible designs.

In a fifth aspect, the application provides a computer program product comprising a computer program for implementing the method of the first aspect and each possible design provision when executed by a processor.

According to the method, an access request for accessing the cloud business interface to be accessed is received, parameter data of the cloud business interface to be accessed is obtained from a yaml file according to a request parameter of the access request, IP and port of the cloud business interface to be accessed are obtained from cloud business management information according to the request parameter of the access request, the cloud business interface to be accessed is accessed according to the access request, the parameter data and the IP and port of the cloud business interface to be accessed, response parameters returned by the cloud business interface to be accessed are obtained, and the response parameters are sent to the service system. According to the technical scheme, the parameter data of each cloud quotient interface is defined through the yaml file, the data can be analyzed and converted according to the yaml file, when the structure or the field of the parameter data of the cloud quotient interface needs to be modified, the yaml file can be directly modified without modifying codes or upgrading and modifying a system, the processing time and the labor cost are effectively saved, and the processing efficiency is improved.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

Fig. 1 is a flow chart of an interface processing method based on multi-cloud management according to an embodiment of the present application;

fig. 2 is a schematic diagram of a configuration process of a cloud provider interface according to an embodiment of the present application;

fig. 3 is a monitoring process flow of a cloud provider message queue provided in an embodiment of the present application;

FIG. 4 is a process flow of yaml files provided by an embodiment of the present application;

fig. 5 is a schematic diagram of a service data flow of an interface processing method based on multi-cloud management according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of an interface processing system based on multi-cloud management according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Specific embodiments of the present application have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

Before describing the embodiments of the present application, an application background of the embodiments of the present application will be explained first:

the multi-cloud management platform is a new generation cloud management platform under the promotion of cloud computing development, and can realize unified multi-cloud management strategy, approval process, resource quota, unified management of mirror image templates, unified arrangement of service resources, cross-cloud service, multi-cloud monitoring alarm and centralized operation and maintenance, and has cross-cloud arrangement capacity, so that the business monitoring requirements of clients are met.

The interface interfacing layer is an important part in the multi-cloud management platform and is mainly used for solving the differences of the access modes of resource interfaces of a plurality of cloud service providers, versions of the interfaces, data interfaces of the interfaces and the like. With the rapid development of cloud computing, interfaces require rapid upgrade deployment to respond to user demands. The interface docking layer can dynamically dock and adapt to the interface and dynamically manage the environmental resources, so that the multi-cloud management platform is easier to respond to the change of the requirements and the rapid upgrading and deployment.

Currently, in practical application, an enterprise may request a cloud provider interface of a cloud service provider to a multi-cloud management platform through a business system of the enterprise, and after receiving the request, the multi-cloud management platform interacts with the cloud provider interface through an interface docking layer, so that the business system can access the cloud platform of the cloud service provider through the cloud provider interface.

In the prior art, a major concern of the docking layer is how to dock interfaces of different cloud vendors to provide stable interface calls. And upgrading the interface version of the butt-joint cloud provider and adjusting the parameter structure, and synchronously upgrading the service transformation. That is, when the parameter definition in the modification request is required, the modification needs to be performed manually, the whole modification process is complicated, and repeated tests are required after the modification, so that the problems of low processing efficiency and high labor cost exist.

Based on the above, the application provides an interface processing method based on multi-cloud management, which can manage request addresses, request header parameters, request parameter definitions, response parameter definitions and asynchronous response parameter definitions through yaml files. In practical application, the parameter data of the corresponding cloud quotient interface can be obtained according to the request parameters of the access request, and the cloud quotient interface is accessed. When the parameter definition corresponding to the cloud quotient port needs to be modified, only the corresponding part of the yaml file corresponding to the cloud quotient port needs to be modified, the yaml file can be immediately validated after being modified, testing is not needed, the modification mode is simple, the processing efficiency is effectively improved, and the labor cost is reduced.

The technical scheme of the application is described in detail through specific embodiments.

It should be noted that the following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.

Fig. 1 is a flow chart of an interface processing method based on multi-cloud management according to an embodiment of the present application. As shown in fig. 1, the interface processing method based on multi-cloud management may include the following steps:

s101, receiving an access request which is sent by a service system and used for accessing a cloud provider interface to be accessed.

The execution subject of the embodiment of the application can be electronic equipment and also can be an interface processing system based on multi-cloud management, which is arranged in the electronic equipment. For ease of understanding, hereinafter, an interface processing system in which an execution subject is based on multi-cloud management will be described as an example.

In this step, since the service system needs to access multiple cloud provider interfaces to meet different requirements and service scenarios, however, different cloud provider interfaces are developed by different cloud providers, the data formats used are different, and the service system cannot identify the data with different data formats from different cloud provider interfaces at the same time. Therefore, in practical application, when the service system needs to access the cloud provider interface, the service system needs to send an access request to the interface processing system based on multi-cloud management. The interface processing system based on the multi-cloud management can be in communication interaction with the service system and the cloud business interface, has the related functions of an interface docking layer in the prior art, aligns the data formats of the service system and the cloud business interface, and achieves the purpose of helping the service system to access the cloud business interface.

S102, acquiring parameter data of a cloud provider interface to be accessed from a yaml file according to request parameters of an access request.

In this step, after receiving an access request, the interface processing system based on multi-cloud management needs to access the cloud quotient interface to be accessed corresponding to the access request, so as to obtain a response of the cloud quotient interface to be accessed. The business system can only use the cloud business interface to be accessed after the cloud business interface to be accessed responds.

However, accessing the to-be-accessed cloud provider interface requires parameter data, internet protocol (Internet Protocol, IP) and ports of the to-be-accessed cloud provider interface, and thus requires the data to be acquired first.

The yaml file includes parameter data for each cloud quotient interface, the parameter data including a request address, a request header parameter, a request parameter definition, a response parameter definition, and an asynchronous response parameter definition. The yaml files and the cloud quotient interfaces are in one-to-one correspondence, that is, each cloud quotient interface has a corresponding yaml file. After the access request is acquired, a yaml file corresponding to the cloud quotient interface to be accessed can be searched from all yaml files according to the request parameters of the access request, and the yaml file is analyzed, so that the parameter data of the cloud quotient interface to be accessed is acquired.

S103, according to the request parameters of the access request, the IP and the port of the cloud provider interface to be accessed are obtained from the cloud provider management information.

In this step, after acquiring the parameter data of the cloud provider interface to be accessed, in order to access the cloud provider interface to be accessed, the IP and the port of the cloud provider interface to be accessed need to be acquired.

The cloud quotient nano-tube information comprises the IP and the ports of all cloud quotient interfaces.

Optionally, the cloud merchant nanotube information is obtained from the console in advance. The user can send the cloud quotient nano-tube information to the interface processing system based on the multi-cloud management through the console, and the interface processing system based on the multi-cloud management receives the cloud quotient nano-tube information.

Furthermore, after the cloud quotient management information is acquired, each cloud quotient interface can be configured. Fig. 2 is a schematic diagram of a configuration process of a cloud provider interface according to an embodiment of the present application. As shown in fig. 2, the configuration process of the cloud quotient nano-tube information includes: and abstracting the resource pool environment of each cloud service provider into corresponding cloud provider interfaces, and configuring the cloud provider interfaces according to cloud provider management information.

Specifically, the resource pool environment of each cloud service provider is abstracted into a corresponding cloud provider interface, and according to the cloud provider management information, the IP, port, tenant information, a corresponding yaml file (not shown in fig. 2) of each cloud provider interface, and connection information and queue information of a corresponding cloud provider message queue are configured. If the information such as the parameter data and version of any cloud quotient interface is related to the parameter data and version of the existing cloud quotient interface in the interface processing system based on the multi-cloud management, the existing yaml file can be directly copied into the cloud quotient interface.

Further, after each item is configured, checking or verification is required, for example, checking whether the IP and the port of the cloud provider interface are connected, checking whether tenant information is correct, and checking whether the cloud provider message queue is connected with the cloud provider interface. If either check or check fails, the configuration is reconfigured until the check or check is passed.

It should be understood that the cloud quotient message queues are used for storing data which is generated by the corresponding cloud quotient interfaces and is to be sent, and the queue information is used for representing the types of the cloud quotient message queues.

S104, accessing the cloud quotient interface to be accessed according to the access request, the parameter data and the IP and the port of the cloud quotient interface to be accessed.

In this step, the cloud quotient interface to be accessed may be accessed according to the parameter data, the IP and the port of the cloud quotient interface to be accessed, so as to obtain a response of the cloud quotient interface to be accessed.

In one possible implementation manner, because the parameter format of the service system is different from the parameter format of the cloud quotient interface to be accessed, the parameter format of the request parameter of the access request is converted into the parameter format corresponding to the cloud quotient interface to be accessed according to the request parameter definition, so that the cloud quotient interface to be accessed is accessed according to the converted request parameter, the parameter data, the IP and the port of the cloud quotient interface to be accessed.

S105, acquiring response parameters returned by the cloud provider interface to be accessed.

In this step, after accessing the cloud provider interface to be accessed, a response parameter returned by the cloud provider interface to be accessed needs to be acquired, so that the response parameter is sent to the service system subsequently.

In one possible implementation manner, when the cloud quotient interface to be accessed is an asynchronous interface, the response parameter may be obtained from a cloud quotient message queue corresponding to the cloud quotient interface to be accessed, where the cloud quotient message queue is used for storing data generated by the cloud quotient interface and to be sent.

In practical application, the interface processing system based on the multi-cloud management can query the connection information and the queue information of the managed cloud business message queues and monitor the managed cloud business message queues. That is, in this implementation, the cloud provider message queue corresponding to the cloud provider interface to be accessed may be monitored according to the connection information and the queue information. The connection information is used for representing the connection relation between each cloud quotient message queue and the cloud quotient interface, and the queue information is used for representing the type of each cloud quotient message queue. So that when the response parameters of the cloud quotient message queue are monitored, the response parameters are acquired.

S106, sending the response parameters to the service system.

In this step, after the response parameter is obtained, the response parameter needs to be sent to the service system, so that the service system calls the cloud provider interface to be accessed according to the response parameter.

In one possible implementation manner, since the parameter format of the service system is different from the parameter format of the cloud provider interface to be accessed, it is also necessary to convert the parameter format of the response parameter into the parameter format corresponding to the service system, and send the converted response parameter to the service system.

When the cloud quotient interface to be accessed is an asynchronous interface, the response parameters can be analyzed, request identity numbers (Identity document, ID) of the response parameters are obtained, interface information corresponding to the response parameters is determined according to the request ID of the response parameters, asynchronous response parameter definitions in yaml files corresponding to the interface information are determined according to the interface information, the response parameters are assembled and converted according to the asynchronous response parameter definitions, parameter formats of the response parameters are converted into parameter formats corresponding to a service system, and finally the converted response parameters are sent to the service system.

According to the interface processing method based on the multi-cloud management, an access request for accessing the cloud business interface to be accessed is sent by a service system, parameter data of the cloud business interface to be accessed is obtained from a yaml file according to the request parameter of the access request, the IP and the port of the cloud business interface to be accessed are obtained from cloud business nano-tube information according to the request parameter of the access request, the cloud business interface to be accessed is accessed according to the access request, the parameter data and the IP and the port of the cloud business interface to be accessed, response parameters returned by the cloud business interface to be accessed are obtained, and the response parameters are sent to the service system. According to the technical scheme, the parameter data of each cloud quotient interface is defined through the yaml file, the data can be analyzed and converted according to the yaml file, when the structure or the field of the parameter data of the cloud quotient interface needs to be modified, the yaml file can be directly modified without modifying codes or upgrading and modifying a system, the processing time and the labor cost are effectively saved, and the processing efficiency is improved.

Optionally, in some embodiments, a queue processing instruction may also be received, and a process corresponding to the queue processing instruction is performed on the target cloud provider message queue. The queue processing instructions are configured to instruct at least one of the following to be performed on the target cloud quotient message queue: inquiring the monitoring state, stopping monitoring, restarting monitoring and starting monitoring.

Fig. 3 is a flow of a monitoring process of a cloud provider message queue according to an embodiment of the present application. As shown in fig. 3, from all the cloud quotient message queues, querying the managed cloud quotient message queue, and monitoring the managed cloud quotient message queue. When the response message exists in any cloud quotient message queue, converting the response parameter according to the asynchronous response parameter definition of the cloud quotient interface corresponding to the cloud quotient message queue, and pushing the converted response parameter to a service message queue of a service system.

Meanwhile, in the monitoring process, the interface processing system based on the multi-cloud management can provide an interface, can receive a queue processing instruction through the interface, and execute at least one of inquiring monitoring state, stopping monitoring, restarting monitoring and starting monitoring on the target cloud business message queue according to the queue processing instruction, so that dynamic configuration management on the cloud business message queue is realized.

Optionally, in some embodiments, yaml file processing instructions may also be received, and a process corresponding to the yaml file processing instructions may be performed on the target yaml file. The yaml file processing instructions are for performing at least one of the following processing on the parameter data in the target yaml file: add, delete, modify, query.

Fig. 4 is a process flow of yaml files provided in an embodiment of the present application. As shown in fig. 4, a yaml file processing instruction sent by the console may be received, the target yaml file may be added, deleted, changed, and searched according to the yaml file processing instruction, and the modified target yaml file may be stored in the database, and the interface processing system based on the multi-cloud management may access the corresponding cloud provider interface according to the modified target yaml file.

The interface processing system based on the multi-cloud management defines yaml files for the managed cloud Shang Jiekou and supports online operations of adding, deleting, modifying and inquiring the yaml files. The format or the field of the parameter data of the cloud quotient interface is modified, the corresponding yaml file is modified online, and the modification is effective in an interface processing system based on multi-cloud management. When a new cloud provider interface needs to be docked, a yaml file which is pre-written by a user can be acquired, the yaml file is stored into a database through a yaml file management module, and the yaml file is effective immediately, so that an interface processing system based on multi-cloud management provides the capability of accessing the cloud provider interface.

Based on the interface processing method based on the multi-cloud management provided by the embodiment, the service data flow of the method is explained by a specific example.

Fig. 5 is a schematic diagram of a service data flow of an interface processing method based on multi-cloud management according to an embodiment of the present application. As shown in fig. 5, after the service of the service system sends an access request to the interface processing system based on the multi-cloud management, the interface processing system based on the multi-cloud management receives the access request, searches yaml files corresponding to the access request from all yaml files used for defining parameter data of a cloud business interface according to request parameters in the access request, and analyzes the yaml files to obtain parameter data: the method comprises the steps of requesting address, requesting header parameters, requesting parameter definition, responding parameter definition and asynchronous responding parameter definition, and converting the parameter format of the requesting parameter of the access request into the parameter format corresponding to the cloud quotient interface to be accessed according to the requesting parameter definition. Further, according to the request parameters of the access request, the IP and the port of the cloud business interface to be accessed are obtained from the cloud business management information, according to the request parameters, the IP and the port of the cloud business interface to be accessed, the cloud business interface is accessed by using the combined interface, the response parameters returned by the cloud business interface are obtained, the response parameters are converted and assembled according to the response parameter definition, and the processed response parameters are sent to the service of the service system.

Further, when the cloud quotient interface is an asynchronous interface, after the request response is completed and the cloud quotient interface executes the task, the obtained data is sent to the interface processing system based on multi-cloud management by using the cloud quotient message queue, the interface processing system based on multi-cloud management assembles and converts the obtained data according to the asynchronous response parameter definition, and then the converted data is pushed to the business message queue of the business service by using the message processing module, so that the business service monitors the business message queue.

The following are examples of the apparatus of the present application that may be used to perform the method embodiments of the present application. For details not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the method of the present application.

Fig. 6 is a schematic structural diagram of an interface processing system based on multi-cloud management according to an embodiment of the present application. As shown in fig. 6, the interface processing system 600 based on multi-cloud management includes:

the receiving module 601 is configured to receive an access request sent by the service system and used for accessing the cloud provider interface.

The first obtaining module 602 is configured to obtain, from the yaml file, parameter data of the cloud quotient interface according to a request parameter of the access request, where the parameter data includes a request address, a request header parameter, a request parameter definition, a response parameter definition, and an asynchronous response parameter definition.

The second obtaining module 603 is configured to obtain, according to a request parameter of the access request, an IP and a port of the cloud quotient interface from cloud quotient management information, where the cloud quotient management information includes the IP and the port of each cloud quotient interface.

And the access module 604 is used for accessing the cloud provider interface according to the access request, the parameter data and the IP and the port of the cloud provider interface.

And a third obtaining module 605, configured to obtain response parameters returned by the cloud provider interface.

A sending module 606, configured to send the response parameter to the service system.

In one possible implementation, the access module 604 is specifically configured to:

and according to the definition of the request parameters, converting the parameter format of the request parameters of the access request into the parameter format corresponding to the cloud provider interface to be accessed.

And accessing the cloud provider interface according to the converted request parameters, the converted parameter data and the IP and the port of the cloud provider interface.

In one possible implementation manner, when the cloud provider interface is an asynchronous interface, the third obtaining module 605 is specifically configured to:

and acquiring response parameters from a cloud quotient message queue corresponding to the cloud quotient interface, wherein the cloud quotient message queue is used for storing data which are generated by the cloud quotient interface and are to be sent.

In one possible implementation manner, the third obtaining module 605 is specifically configured to:

Monitoring the cloud quotient message queues corresponding to the cloud quotient interfaces according to the connection information and the queue information, wherein the connection information is used for representing the connection relation between each cloud quotient message queue and the cloud quotient interfaces, and the queue information is used for representing the types of each cloud quotient message queue.

And acquiring response parameters when the response parameters of the cloud quotient message queue are monitored.

In one possible implementation, the sending module 606 is specifically configured to:

and converting the parameter format of the response parameters into a parameter format corresponding to the service system.

And sending the converted response parameters to a service system.

In one possible implementation, when the cloud provider interface is an asynchronous interface, the sending module 606 is specifically configured to:

and analyzing the response parameters to obtain the request identification number ID of the response parameters.

And determining interface information corresponding to the response parameters according to the request ID of the response parameters.

And determining asynchronous response parameter definition in the yaml file corresponding to the interface information according to the interface information.

And according to the asynchronous response parameter definition, converting the parameter format of the response parameter into a parameter format corresponding to the service system.

In one possible implementation, the interface processing system 600 based on multi-cloud management further includes:

The receiving module 601 is further configured to receive a queue processing instruction, where the queue processing instruction is configured to instruct to perform at least one of the following processing on the target cloud provider message queue: inquiring the monitoring state, stopping monitoring, restarting monitoring and starting monitoring.

In a possible implementation, the receiving module 601 is further configured to receive yaml file processing instructions, where the yaml file processing instructions are configured to perform at least one of the following on parameter data in the target yaml file: add, delete, modify, query.

And the processing module is also used for executing the processing corresponding to the yaml file processing instruction on the target yaml file.

In one possible implementation, the processing module is further configured to:

the resource pool environment of each cloud service provider is abstracted into a corresponding cloud provider interface.

In one possible implementation, the processing module is specifically configured to:

configuring IP, port, tenant information, corresponding yaml file, corresponding cloud business message queue connection information and queue information of each cloud business interface.

It should be appreciated that the third acquisition module 605 may be the message processing module in fig. 6.

The interface processing system 600 based on multi-cloud management provided in the embodiment of the present application may be used to execute the interface processing method based on multi-cloud management in any of the above embodiments, and its implementation principle and technical effects are similar, and will not be described herein.

It should be noted that, it should be understood that the division of the modules of the above apparatus is merely a division of a logic function, and may be fully or partially integrated into a physical entity or may be physically separated. And these modules may all be implemented in software in the form of calls by the processing element; or can be realized in hardware; the method can also be realized in a form of calling software by a processing element, and the method can be realized in a form of hardware by a part of modules. In addition, all or part of the modules may be integrated together or may be implemented independently. The processing element described herein may be an integrated circuit having signal processing capabilities. In implementation, each step of the above method or each module above may be implemented by an integrated logic circuit of hardware in a processor element or an instruction in a software form.

The interface processing system based on the multi-cloud management can be independently deployed on one electronic device in any environment, and fig. 7 is a schematic structural diagram of the electronic device according to the embodiment of the present application. As shown in fig. 7, the electronic device 700 may include: the system comprises a processor 701, a memory 702, a transceiver 703 and computer program instructions stored on the memory 702 and executable on the processor 701, wherein the processor 701 implements the interface processing method based on multi-cloud management provided in any of the foregoing embodiments when executing the computer program instructions.

Alternatively, the above-mentioned devices of the electronic apparatus 700 may be connected through a system bus.

The memory 702 may be a separate memory unit or may be a memory unit integrated into the processor. The number of processors is one or more.

Optionally, the transceiver 703 constitutes a communication interface.

It should be appreciated that the processor 701 may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in a processor for execution.

The system bus may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus, among others. The system bus may be classified into an address bus, a data bus, a control bus, and the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus. The memory may include random access memory (random access memory, RAM) and may also include non-volatile memory (NVM), such as at least one disk memory.

All or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a readable memory. The program, when executed, performs steps including the method embodiments described above; and the aforementioned memory (storage medium) includes: read-only memory (ROM), RAM, flash memory, hard disk, solid state disk, magnetic tape, floppy disk, optical disk (optical disc), and any combination thereof.

The electronic device provided by the embodiment of the present application may be used to execute the interface processing method for multi-cloud management provided by any of the above method embodiments, and its implementation principle and technical effects are similar, and are not described herein again.

The embodiment of the application provides a computer readable storage medium, wherein computer execution instructions are stored in the computer readable storage medium, and when the computer execution instructions run on a computer, the computer is caused to execute the interface processing method for multi-cloud management.

The computer readable storage medium described above may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as static random access memory, electrically erasable programmable read-only memory, magnetic memory, flash memory, magnetic disk or optical disk. A readable storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

In the alternative, a readable storage medium is coupled to the processor such that the processor can read information from, and write information to, the readable storage medium. In the alternative, the readable storage medium may be integral to the processor. The processor and the readable storage medium may reside in an application specific integrated circuit (Application Specific Integrated Circuits, ASIC). The processor and the readable storage medium may reside as discrete components in a device.

Embodiments of the present application also provide a computer program product, where the computer program product includes a computer program, where the computer program is stored in a computer readable storage medium, and at least one processor may read the computer program from the computer readable storage medium, and the at least one processor may implement the interface processing method for multi-cloud management when executing the computer program.

It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. An interface processing method based on multi-cloud management is characterized by comprising the following steps:

receiving an access request sent by a service system and used for accessing a cloud provider interface to be accessed;

according to the request parameters of the access request, acquiring the Internet Protocol (IP) and the port of the cloud quotient interface to be accessed from cloud quotient nano-tube information, wherein the cloud quotient nano-tube information comprises the IP and the port of each cloud quotient interface;

and sending the response parameters to the service system.

2. The method of claim 1, wherein accessing the to-be-accessed cloud provider interface according to the access request, the parameter data, and the IP and port of the to-be-accessed cloud provider interface comprises:

3. The method of claim 1, wherein when the cloud quotient interface to be accessed is an asynchronous interface, the obtaining response parameters returned by the cloud quotient interface to be accessed comprises:

4. The method of claim 3, wherein the obtaining the response parameter from the cloud provider message queue corresponding to the cloud provider interface to be accessed comprises:

5. The method according to any one of claims 1-4, wherein said sending the response parameters to the service system comprises:

and sending the converted response parameters to the service system.

6. The method of claim 5, wherein when the cloud provider interface to be accessed is an asynchronous interface, the converting the parameter format of the response parameter into the parameter format corresponding to the service system comprises:

7. The method according to claim 4, wherein the method further comprises:

8. The method according to any one of claims 1-4, further comprising:

9. The method according to any one of claims 1-4, further comprising:

10. The method of claim 9, wherein configuring each cloud provider interface according to the cloud provider nanotube information comprises:

11. An interface processing system based on multi-cloud management, comprising:

the receiving module is used for receiving an access request which is sent by the service system and used for accessing the cloud quotient interface to be accessed;

the second obtaining module is configured to obtain, according to a request parameter of the access request, an internet protocol IP and a port of the cloud quotient interface to be accessed from cloud quotient management information, where the cloud quotient management information includes the IP and the port of each cloud quotient interface;

12. An electronic device, comprising: a processor, a transceiver, a memory and computer program instructions stored on the memory and executable on the processor, wherein the processor is configured to implement the method of any one of claims 1 to 10 when executing the computer program instructions.

13. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method of any one of claims 1 to 10.