WO2018006872A1 - 一种混合云的接口调用方法及装置 - Google Patents

一种混合云的接口调用方法及装置 Download PDF

Info

Publication number
WO2018006872A1
WO2018006872A1 PCT/CN2017/092259 CN2017092259W WO2018006872A1 WO 2018006872 A1 WO2018006872 A1 WO 2018006872A1 CN 2017092259 W CN2017092259 W CN 2017092259W WO 2018006872 A1 WO2018006872 A1 WO 2018006872A1
Authority
WO
WIPO (PCT)
Prior art keywords
cloud
interface
cloud platform
platform
target
Prior art date
Application number
PCT/CN2017/092259
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
Priority claimed from CN201610539009.9A external-priority patent/CN107592237B/zh
Priority claimed from CN201610539500.1A external-priority patent/CN106101258B/zh
Application filed by 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Priority to EP17823684.0A priority Critical patent/EP3484125B1/en
Publication of WO2018006872A1 publication Critical patent/WO2018006872A1/zh
Priority to US16/191,323 priority patent/US10965772B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0894—Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/565—Conversion or adaptation of application format or content
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3226—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using a predetermined code, e.g. password, passphrase or PIN
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3297—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving time stamps, e.g. generation of time stamps

Definitions

  • the present invention relates to the field of cloud computing technologies, and more particularly to an interface calling method and apparatus for a hybrid cloud.
  • Cloud computing is an add-on, use, and delivery model of Internet-based related services that typically involves providing dynamically scalable and often virtualized resources over the Internet.
  • Cloud platforms can be classified into Openstack cloud platform, Qcloud cloud platform or AWS cloud platform according to cloud computing.
  • a cloud computing technology that combines a public cloud platform with a private cloud platform is called a hybrid cloud.
  • a hybrid cloud A cloud computing technology that combines a public cloud platform with a private cloud platform.
  • enterprises have both external and internal services.
  • external services due to cost considerations, enterprises hope to apply public cloud platforms.
  • in-service services for security reasons, enterprises hope A private cloud platform can be applied, so hybrid clouds are becoming more and more popular.
  • the resource monitoring of the hybrid cloud needs to be performed alternately between different types of cloud platforms, that is, after the user needs to perform resource monitoring on one of the cloud platforms, Switching to another cloud platform to continue resource monitoring results in very low resource monitoring efficiency for hybrid clouds.
  • the present invention provides a method and apparatus for invoking an interface of a hybrid cloud to implement uniformity of interface calls to a hybrid cloud.
  • An embodiment of the present application provides a method for invoking an interface of a hybrid cloud, where the method includes:
  • An embodiment of the present invention further provides an interface calling device of a hybrid cloud, where the device includes:
  • a receiving module configured to receive an interface call request to the hybrid cloud sent by the caller, where the interface call request is used to indicate an interface of the first target cloud platform that the caller requests to invoke;
  • a determining module configured to determine an interface of the first target cloud platform according to the interface call request
  • a sending module configured to send the interface call request to an interface of the first target cloud platform.
  • an interface call request to the hybrid cloud sent by the caller is received, where the interface call request is used to indicate an interface of the first target cloud platform that the caller requests to invoke; and the request is determined according to the interface call request.
  • An interface of the first target cloud platform; the interface is The call request is sent to the interface of the first target cloud platform.
  • 1 is a schematic diagram of a system framework of an existing hybrid cloud
  • FIG. 2 is a schematic diagram of a system framework of a hybrid cloud according to an embodiment of the present application.
  • FIG. 3 is a flowchart of a method for invoking an interface of a hybrid cloud according to an embodiment of the present application
  • FIG. 4 is a flowchart of another hybrid cloud interface calling method according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic diagram of an application example of an interface calling method of a hybrid cloud according to an embodiment of the present disclosure
  • FIG. 6 is a structural block diagram of an interface calling device of a hybrid cloud according to an embodiment of the present application.
  • FIG. 7 is another structural block diagram of an interface calling device of a hybrid cloud according to an embodiment of the present application.
  • FIG. 8 is a structural diagram of a determining module according to an embodiment of the present application.
  • FIG. 9 is a structural diagram of an authentication module according to an embodiment of the present application.
  • FIG. 10 is a block diagram showing a hardware structure of an interface calling device of a hybrid cloud according to an embodiment of the present application.
  • FIG. 11 is a structural diagram of an interface calling system of a hybrid cloud according to an embodiment of the present application.
  • FIG. 12 is a flowchart of a hybrid cloud resource monitoring method according to an embodiment of the present application.
  • FIG. 13 is a flowchart of a method for determining a second target cloud platform of the hybrid cloud according to the resource monitoring request of the hybrid cloud according to an embodiment of the present disclosure
  • FIG. 14 is a schematic diagram of an application example of a hybrid cloud resource monitoring method according to an embodiment of the present disclosure.
  • FIG. 15 is a structural block diagram of a hybrid cloud resource monitoring system according to an embodiment of the present application.
  • FIG. 16 is a structural diagram of a determining module according to an embodiment of the present application.
  • FIG. 17 is another structural block diagram of a hybrid cloud resource monitoring system according to an embodiment of the present application.
  • the embodiments of the present application are mainly applied to a hybrid cloud.
  • the system framework of the existing hybrid cloud and the system framework of the hybrid cloud of the present application are described in detail below.
  • FIG. 1 is a schematic diagram of a system framework of a conventional hybrid cloud.
  • the hybrid cloud includes cloud system A and cloud system B, and the two systems are independently deployed.
  • the application programming interface API-A corresponding to the cloud system A is relatively independent of the application programming interface API-B corresponding to the cloud system B. Therefore, there is no relationship between the cloud system A and the cloud system B. Based on this, when the user needs to schedule the interfaces of the cloud platform A and the cloud platform B through the application layer platform to implement the processing of the user service, only the API-A and the API-B can be respectively called, and the unified call cannot be implemented.
  • FIG. 2 is a schematic diagram of a system framework of a hybrid cloud according to an embodiment of the present application.
  • the hybrid cloud includes a standard application programming interface API, cloud system A, and cloud system B.
  • the standard application programming interface API simultaneously connects the application programming interface API-A corresponding to the cloud system A and the application programming interface API-B corresponding to the cloud system B
  • the cloud system A and the cloud system B have a certain relationship. Association relationship.
  • the interface of the cloud platform A and the cloud platform B can be uniformly scheduled by calling the standard application programming interface API.
  • the embodiment of the present application provides a hybrid cloud interface calling method, which can uniformly aggregate the cloud interface call, thereby making the hybrid cloud system application and maintenance more convenient.
  • the execution body of the interface calling method of the hybrid cloud provided by the embodiment of the present application may be a background server.
  • the background server can be a background server for the standard application programming interface API.
  • FIG. 3 is a flowchart of a method for invoking an interface of a hybrid cloud according to an embodiment of the present application.
  • the method may include:
  • Step S300 Receive an interface call request to the hybrid cloud sent by the caller, where the interface call request is used to indicate an interface of the first target cloud platform that the caller requests to invoke.
  • the caller can be the background server of the application layer platform.
  • the interface of the target cloud platform may be an application programming interface API corresponding to different functions of the cloud platform (for example, resource scheduling, resource monitoring, resource management, etc.), which is not limited in this embodiment.
  • Step S310 Determine an interface of the first target cloud platform according to the interface call request.
  • the interface of the hybrid cloud may carry the parameters related to the interface of the first target cloud platform, and the interfaces of the target cloud platform may be determined by using the parameters, which are specifically described in the following embodiments.
  • Step S320 Send the interface call request to an interface of the first target cloud platform.
  • the method for invoking an interface of the hybrid cloud includes: receiving an interface call request to the hybrid cloud sent by the caller, where the interface call request is used to indicate an interface of the first target cloud platform that the caller requests to invoke; Determining, according to the interface call request, an interface of the first target cloud platform; and sending the interface call request to an interface of the first target cloud platform.
  • FIG. 4 is a flowchart of another hybrid cloud interface calling method provided by an embodiment of the present application. Referring to FIG. 4, the method may include:
  • Step S400 Receive an interface call request to the hybrid cloud sent by the caller, where the interface call request is used to indicate an interface of the first target cloud platform that the caller requests to invoke.
  • an interface call request that includes a uniform resource locator URL address sent by the caller may be received.
  • step S410 the interface call request is authenticated. If the authentication is passed, step S420 to step S430 are performed. If the authentication fails, the entire process is ended.
  • the embodiment of the present application also discloses an interface call request authentication mode, which will be specifically described below.
  • the caller needs to apply for an account to the background server of the standard application programming interface API.
  • the account includes at least two parameters, AccessKey and SecretKey.
  • the AccessKey is used to identify the identity of the caller, and the SecretKey is used to encrypt the signature string and
  • the background server side of the standard API verifies the key of the signature string.
  • the caller may send an interface call request generated by an HTTP (Hyper Text Transfer Protocol) protocol to the standard API to implement scheduling of resources of the hybrid cloud.
  • the interface call request includes a request type (HTTP Method, eg, GET/POST/PATCH/PUT/DELETE, etc.) and a URL (Uniform Resource Locator) address. Since the hybrid cloud includes multiple different types of cloud platforms, the type of the first target cloud platform invoked by the HTTP request may be represented by adding a cloud type parameter to the URL address, for example, tocloud represents the first target requested to be invoked.
  • the type of the cloud platform is Openstack cloud platform
  • tacloud indicates that the type of the first target cloud platform requested to be invoked is AWS
  • tqcloud indicates that the type of the first target cloud platform requested to be called is Qcloud.
  • the area of the interface of the first target cloud platform invoked by the HTTP request may be represented by adding a region parameter to the URL address.
  • region-002 represents an interface of the second area.
  • HTTP requests GTE http://api.cloud.com/v1.0/tacloud/servers? Region region-002 indicates that the caller wants to call the interface of the second region whose cloud platform type is AWS.
  • the HTTP header storing the public parameters as shown in Table 1 needs to be simultaneously sent to the standard API.
  • the Signature is based on the HMAC-SHA1 algorithm, and uses the key parameter SecretKey corresponding to the user authentication code AccessKey to perform a string consisting of the request type HTTP Method, the timestamp parameter Timestamp, the URL address, the platform verification code AppKey, and the user verification code AccessKey.
  • the signature string obtained by the signature and then encoded by Base64.
  • the caller pre-includes the account requested by the backend server of the standard API.
  • the parameter values of AccessKey and SecretKey are as follows:
  • AccessKey AKIAIOSFODNN7EXAMPLE
  • the interface call request sent by the call direction standard API is:
  • Timestamp and AppKey are as follows:
  • AppKey APP-001
  • the HTTP header sent by the caller to the standard API is as follows:
  • Timestamp 1462333570 AppKey APP-001 AccessKey AKIAIOSFODNN7EXAMPLE Signature 42ClT5XIHcX8KNZnoZ/g0R8bDTM
  • the standard API transmits the received interface call request and the HTTP header to its backend server, and its backend server queries the database to obtain the parameter SecretKey pre-allocated to the caller, and authenticates the Signature through the parameter, if the HTTP obtained after authentication Method,
  • the values in the string consisting of Timestamp, URL, AppKey, and AccessKey are exactly the same as the values of the interface call request received by the standard API and the HTTP header, indicating that the authentication is passed, that is, the caller can call the standard API.
  • Step S420 Determine an interface of the first target cloud platform according to the interface call request.
  • the interface of the first target cloud platform may be determined by: determining a type of the first target cloud platform according to the cloud platform type parameter in the URL address; determining the first according to the region parameter in the URL address. An area of the interface of the target cloud platform; determining, according to the type of the first target cloud platform and the interface of the interface of the first target cloud platform, that the interface in the area is an interface of the first target cloud platform.
  • Step S430 Send the interface call request to an interface of the first target cloud platform.
  • the foregoing authentication mode is added to ensure that the legitimate user successfully schedules the standard API, and the non-legal user cannot successfully schedule the standard API, thereby further ensuring the scheduling security of the hybrid cloud resource.
  • the hybrid cloud to be scheduled by user A through the application layer includes cloud platform A, cloud platform B, and cloud platform C.
  • Cloud platform A, cloud platform B, and cloud platform C are respectively API-A, API-B, and API-C. correspond.
  • the cloud platform A is of the Openstack cloud platform, and the computer room area is the North China region, including the cloud servers a1, a2, and a3.
  • the corresponding resource scheduling API is API-A
  • the cloud platform B is AWS
  • the computer room area is South China.
  • the cloud server b1, b2, and b3, the corresponding resource scheduling API is API-B
  • the cloud platform C is Qcloud
  • the computer room area is Central China
  • the cloud server is c1, c2, and c3, and the corresponding resource scheduling API is API-C.
  • the application layer platform provides an interface call application interface, and user A invokes the interface.
  • the application interface triggers the application interface call button to generate an interface call request to the hybrid cloud.
  • the interface call request is specifically GTE http://api.cloud.com/v1.0/tocloud/servers?
  • the interface call request is sent to the background server corresponding to the standard API, and the background server corresponding to the standard API determines that the interface of the target cloud platform corresponding to the interface call request is API-A, and the standard API
  • the corresponding background server sends the hybrid cloud interface call request to the cloud platform A through the API-A, and the cloud platform A schedules its own resources, obtains the corresponding resource scheduling result, and sequentially passes the resource scheduling result through the API-A and the standard.
  • the API feeds back to the background server of the application layer platform, and the background server of the application layer platform displays the application interface to the user A through the interface.
  • the interface calling device of the hybrid cloud provided by the embodiment of the present application.
  • the interface calling device of the hybrid cloud described below may refer to the interface calling method of the hybrid cloud above.
  • FIG. 6 is a structural block diagram of an interface calling device of a hybrid cloud according to an embodiment of the present disclosure, where the interface calling device of the hybrid cloud may be a background server.
  • the interface calling device of the hybrid cloud may include:
  • the receiving module 60 is configured to receive an interface call request to the hybrid cloud sent by the caller, where the interface call request is used to indicate an interface of the first target cloud platform that the caller requests to invoke;
  • a determining module 61 configured to determine an interface of the first target cloud platform according to the interface call request
  • the sending module 62 is configured to send the interface call request to an interface of the first target cloud platform.
  • FIG. 7 is another structural block diagram of an interface calling device of a hybrid cloud according to an embodiment of the present disclosure.
  • the interface calling device of the hybrid cloud may be a background server.
  • the interface calling device of the hybrid cloud may include:
  • the receiving module 70 is configured to receive an interface call request to the hybrid cloud sent by the caller, where the interface call request is used to indicate an interface of the first target cloud platform that the caller requests to invoke;
  • the authentication module 71 is configured to perform authentication on the interface call request before determining the interface of the first target cloud platform according to the interface call request; if the authentication is passed, the trigger determining module 72 is configured according to the The interface call request determines an interface of the first target cloud platform.
  • a determining module 72 configured to determine an interface of the first target cloud platform according to the interface call request
  • the sending module 73 is configured to send the interface call request to an interface of the first target cloud platform.
  • the receiving module is specifically configured to:
  • the interface call request sent by the caller including the uniform resource locator URL address is received.
  • FIG. 8 shows a structural diagram of the determining module.
  • the determining module specifically includes:
  • the determining unit 80 is configured to determine, according to the cloud platform type parameter in the URL address, a type of the first target cloud platform;
  • the area determining unit 81 is configured to determine an area of the interface of the first target cloud platform according to the region parameter in the URL address;
  • the interface determining unit 82 of the target cloud platform is configured to determine that the interface in the area is an interface of the first target cloud platform.
  • FIG. 9 is a structural diagram of an authentication module.
  • the authentication module specifically includes:
  • the receiving unit 90 is configured to receive an HTTP header sent by the caller, where the HTTP header includes a timestamp parameter Timestamp, a platform verification code AppKey, a user verification code AccessKey, and a signature string Signature;
  • the query unit 91 is configured to obtain a key parameter SecretKey pre-allocated to the caller;
  • the processing unit 92 is configured to use the key parameter SecretKey to authenticate the signature string Signature, and obtain a string consisting of an HTTP Method, a Timestamp, a URL address, an AppKey, and an AccessKey;
  • the request type in the interface call request is the same, and the URL address in the string is consistent with the URL address in the interface call request, and the Timestamp in the string is consistent with the Timestamp in the HTTP header, and
  • the AppKey in the character string is consistent with the AppKey in the HTTP header, and when the AccessKey in the string matches the AccessKey in the HTTP header, the authentication is passed.
  • the interface calling device of the hybrid cloud may be a hardware device, a software, or a hardware instruction software.
  • the modules and units described above may be provided in functional modules within the interface calling device of the hybrid cloud.
  • 10 is a block diagram showing the hardware structure of the interface calling device of the hybrid cloud.
  • the interface calling device of the hybrid cloud may include: a processor 1, a communication interface 2, a memory 3, and a communication bus 4; wherein the processor 1 and the communication The interface 2 and the memory 3 complete communication with each other via the communication bus 4.
  • the communication interface 2 can be an interface of a communication module, such as an interface of a GSM module.
  • the processor 1 is for executing a program; the memory 3 is for storing a program; the program may include program code, and the program code includes computer operation instructions.
  • the processor 1 may be a central processing unit CPU, or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.
  • the memory 3 may include a high speed RAM memory and may also include a non-volatile memory such as at least one disk memory.
  • the program can be specifically used to:
  • the structure diagram of the interface system of the hybrid cloud is as shown in FIG. 11, and includes a background server 10 of the application layer platform and a background server 20 of the standard API.
  • the background server of the application layer platform is configured to receive an interface call request sent by the user to the hybrid cloud, and send the interface call request to a background server of a standard API, where the interface call request is used to indicate the caller request
  • a background server of the standard API configured to receive an interface call request sent by a background server of the application layer platform, and determine an interface of the first target cloud platform according to the interface call request, and send the interface call request to the The interface of the first target cloud platform.
  • the background server of the standard API is further configured to: after determining the interface of the first target cloud platform according to the interface call request, authenticating the interface call request; After the right is passed, the interface of the first target cloud platform is determined according to the interface call request.
  • the background server of the standard API is specifically configured to receive an interface call request that includes a uniform resource locator URL address sent by a background server of the application layer platform.
  • the background server of the standard API is specifically used to:
  • the HTTP header includes a timestamp parameter Timestamp, a platform verification code AppKey, a user verification code AccessKey, and a signature string Signature;
  • the embodiment of the present application further provides a hybrid cloud resource monitoring method, which can uniformly monitor the resources of the hybrid cloud and improve the resource monitoring efficiency of the hybrid cloud.
  • the execution body of the hybrid cloud resource monitoring method provided by the embodiment of the present application may be a background server.
  • the background server may be a server corresponding to the cloud service self-service platform.
  • the server also records the resource information table generated when the hybrid cloud is created, and receives the resource monitoring for the hybrid cloud. After the request, determining, according to the resource monitoring request for the hybrid cloud, at least one second target cloud platform of the hybrid cloud, and establishing a signal path between the server and each second target cloud platform to implement unified control of each second target cloud platform Obtain the respective resource monitoring data to obtain the resource monitoring data of the hybrid cloud.
  • the background server may also be a server of a standard application programming interface API.
  • the server of the standard API records a resource information table generated when the hybrid cloud is created, and receives resource monitoring of the hybrid cloud sent by the user through the cloud service self-service platform.
  • determining, according to the resource monitoring request for the hybrid cloud, at least one second target cloud platform of the hybrid cloud, and establishing a signal path between the server and each second target cloud platform to implement unified control of each second target cloud platform Obtain the respective resource monitoring data, and then obtain the resource monitoring data of the hybrid cloud, and feed back the resource monitoring data of the obtained hybrid cloud to the cloud service self-service platform for display to the user.
  • the hybrid cloud resource monitoring method includes:
  • FIG. 12 is a flowchart of a hybrid cloud resource monitoring method according to an embodiment of the present application.
  • the method may include:
  • Step S1200 Receive a resource monitoring request for the hybrid cloud, where the resource monitoring request for the hybrid cloud is used to indicate that the resource monitoring data of the hybrid cloud is requested to be acquired.
  • the resource monitoring request for the hybrid cloud may be sent by the user through the cloud service self-service platform, and is configured to acquire the resource monitoring data of the hybrid cloud to understand the running status of the hybrid cloud, and timely make the hybrid cloud according to the running status of the hybrid cloud. preventive solution.
  • multiple resource monitoring data of the hybrid cloud may be acquired.
  • the central processor CPU resource of the cloud server of the hybrid cloud, the memory resource of the cloud server, the intranet bandwidth resource of the cloud server, and the cloud server may be received. Any one or more of the disk resources Monitoring request.
  • the central processing unit CPU resource of the cloud server includes the CPU utilization and the average CPU load.
  • the memory resources of the cloud server include the memory usage and the memory usage rate, and the intranet bandwidth resources of the cloud server include the outgoing bandwidth, the incoming bandwidth, and the outbound packet.
  • Volume, inbound packet, cloud server disk resources include disk read utilization and disk write utilization.
  • Step S1210 Determine a second target cloud platform of the hybrid cloud according to a resource monitoring request for the hybrid cloud.
  • the resource monitoring request of the hybrid cloud includes instance ID information of each cloud server in the hybrid cloud.
  • the second target cloud platform of the hybrid cloud may be determined according to instance ID information of each cloud server in the hybrid cloud.
  • Step S1220 Send a resource monitoring request to the second target cloud platform to the determined second target cloud platform, where the resource monitoring request of the second target cloud platform is used to indicate that the second target cloud platform is requested to be acquired. Resource monitoring data.
  • the resource monitoring request of one hybrid cloud may be split into multiple second target cloud platforms by using the foregoing steps.
  • the resource monitoring request is sent to the corresponding second target cloud platform, so that the plurality of second target cloud platforms acquire the resource monitoring data of the second target cloud platform.
  • Step S1230 Receive resource monitoring data fed back by each second target cloud platform.
  • the obtained resource monitoring data is fed back to the background server.
  • Step S1240 Integrate resource monitoring data fed back by each second target cloud platform to obtain resource monitoring data of the hybrid cloud.
  • the background server may integrate the resource monitoring data fed back by the second target cloud platform to obtain the resource of the hybrid cloud. Source monitoring data.
  • the integration mentioned in the embodiment may specifically integrate the resource monitoring data fed back by each second target cloud platform into a resource monitoring data for indicating the running status of the hybrid cloud.
  • the resource monitoring data of the hybrid cloud may also be displayed.
  • the resource monitoring method of the hybrid cloud includes: receiving a resource monitoring request for the hybrid cloud, where the resource monitoring request for the hybrid cloud is used to indicate that the resource monitoring data of the hybrid cloud is requested to be acquired;
  • the resource monitoring request of the hybrid cloud determines at least one second target cloud platform of the hybrid cloud; and sends a resource monitoring request for the second target cloud platform to the determined second target cloud platform, where the second target cloud platform
  • the resource monitoring request is used to indicate that the resource monitoring data of the second target cloud platform is requested to be acquired; the resource monitoring data fed back by each second target cloud platform is received; and the resource monitoring data fed back by each second target cloud platform is integrated to obtain the hybrid Cloud resource monitoring data.
  • the resources of the hybrid cloud can be uniformly monitored, thereby improving the resource monitoring efficiency of the hybrid cloud.
  • FIG. 13 is a flowchart of a method for determining at least one second target cloud platform of the hybrid cloud according to a resource monitoring request for the hybrid cloud according to an embodiment of the present application.
  • the method can include:
  • Step S1300 Read instance ID information of each cloud server in the hybrid cloud included in the resource monitoring request of the hybrid cloud.
  • Step S1310 retrieve a resource information table generated when the hybrid cloud is created.
  • a resource information table is stored in the background server.
  • the resource information table generated when the hybrid cloud is created may be retrieved to determine at least one second target of the hybrid cloud.
  • Step S1320 According to instance ID information of each cloud server in the hybrid cloud, and The resource information table determines an access address of the second target cloud platform corresponding to each cloud server of the hybrid cloud, and obtains an access address of the at least one second target cloud platform of the hybrid cloud.
  • the resource information table includes resource related information of the hybrid cloud, for example, instance ID information of each cloud server in the hybrid cloud, and computer room information corresponding to instance ID information of each cloud server.
  • the information about the equipment room includes at least an access address of the second target cloud platform corresponding to each cloud server of the hybrid cloud.
  • determining the access address of the second target cloud platform corresponding to each cloud server of the hybrid cloud according to the instance ID information of each cloud server in the hybrid cloud and the resource information table may be as follows Realizing: reading the equipment room information corresponding to the instance ID information of each cloud server in the hybrid cloud, and the second information corresponding to each cloud server in the hybrid cloud The access address of the target cloud platform; the access address of the second target cloud platform corresponding to each cloud server of the hybrid cloud is determined according to the room information corresponding to the instance ID information of each cloud server in the hybrid cloud.
  • the resource monitoring request of the target cloud platform is sent to the at least one second target cloud platform, include:
  • the hybrid cloud to be monitored by user A through the cloud service self-service platform includes cloud platform A, cloud platform B, and cloud platform C as examples, and cloud platform A, cloud platform B, and cloud platform C are respectively API-A, API-B, API-C corresponds.
  • the cloud room A has a computer room area of North China, including cloud servers a1, a2, and a3.
  • the corresponding cloud platform access address is API-A
  • the cloud room B's computer room area is South China, including cloud servers b1, b2, and b3.
  • the corresponding cloud platform access address is API-B
  • the cloud room C's computer room area is Central China, including cloud servers c1, c2, and c3, and the corresponding cloud platform access address is API-C.
  • the cloud service self-service platform provides a resource monitoring application interface, and the user A triggers a resource monitoring button on the resource monitoring application interface to generate a resource monitoring request for the hybrid cloud, where the resource monitoring request is used to indicate that the cloud server a1 and a2 are acquired.
  • the cloud service self-service platform sends the resource monitoring request of the hybrid cloud to the background server corresponding to the standard API, and the background server corresponding to the standard API determines the cloud server a1 according to the stored resource information table.
  • the information about the equipment room corresponding to a2 and a3 is the North China area.
  • the access address of the corresponding cloud platform in the area is API-A.
  • the information about the equipment room corresponding to the cloud servers b1, b2, and b3 is the South China area.
  • the API-B and the computer room information corresponding to the cloud servers c1, c2, and c3 are Central China, and the corresponding cloud platform access address of the area is API-C, and the background server corresponding to the standard API will mix the cloud resource monitoring request.
  • the resource monitoring device of the hybrid cloud provided by the embodiment of the present invention is introduced.
  • the resource monitoring device of the hybrid cloud described below may be associated with the resource monitoring method of the hybrid cloud. Photo.
  • FIG. 15 is a structural block diagram of a hybrid cloud resource monitoring system according to an embodiment of the present disclosure.
  • the hybrid cloud resource monitoring device may be a background server.
  • the hybrid cloud resource monitoring device may include:
  • the receiving module 50 is configured to receive a resource monitoring request for the hybrid cloud, where the resource monitoring request for the hybrid cloud is used to indicate that the resource monitoring data of the hybrid cloud is requested to be acquired;
  • a determining module 51 configured to determine, according to a resource monitoring request for the hybrid cloud, at least one second target cloud platform of the hybrid cloud;
  • a sending module 52 configured to send, to each of the determined second target cloud platforms, a resource monitoring request for each second target cloud platform, where the resource monitoring request of the second target cloud platform is used to indicate that the second target is requested to be acquired Resource monitoring data of the cloud platform;
  • the receiving module 50 is further configured to receive resource monitoring data fed back by each second target cloud platform;
  • the integration module 53 is configured to integrate resource monitoring data fed back by each second target cloud platform to obtain resource monitoring data of the hybrid cloud.
  • FIG. 16 shows a structural diagram of the determining module 51.
  • the determining module 51 specifically includes:
  • the instance ID information reading unit 510 is configured to read instance ID information of each cloud server in the hybrid cloud included in the resource monitoring request of the hybrid cloud;
  • a resource information table retrieving unit 511 configured to retrieve a resource information table generated when the hybrid cloud is created
  • the access address determining unit 512 is configured to determine an access address of the second target cloud platform corresponding to each cloud server in the hybrid cloud according to the instance ID information of each cloud server in the hybrid cloud and the resource information table, and obtain The access address of the at least one second target cloud platform corresponding to the hybrid cloud.
  • the access address determining unit is specifically configured to:
  • the sending module includes:
  • An API determining unit configured to determine, according to an access address of the second target cloud platform corresponding to each cloud server, an application programming interface API of the second target cloud platform corresponding to each cloud server;
  • a sending unit configured to send, by using an application programming interface API of each second target cloud platform, a resource monitoring request of the target cloud platform to each second target cloud platform, where the resource monitoring request of the second target cloud platform is used to indicate the request to obtain Resource monitoring data of each cloud server corresponding to the second target cloud platform.
  • the receiving module is specifically configured to:
  • FIG. 17 is another structural block diagram of a hybrid cloud resource monitoring system according to an embodiment of the present invention. As shown in FIG. 15, the hybrid cloud resource monitoring system further includes:
  • the display module 54 is configured to display the resource monitoring data of the hybrid cloud after the resource monitoring data fed back by the second target cloud platform is obtained, and the resource monitoring data of the hybrid cloud is obtained.
  • the resource monitoring system of the hybrid cloud includes: a receiving module, configured to receive a resource monitoring request for the hybrid cloud, where the resource monitoring request for the hybrid cloud is used to indicate a request Obtaining, by the resource module, the resource monitoring data of the hybrid cloud, the determining module, configured to determine, according to the resource monitoring request for the hybrid cloud, at least one second target cloud platform of the hybrid cloud, and a sending module, configured to The second target cloud platform sends a resource monitoring request for each second target cloud platform, where the resource monitoring request of the second target cloud platform is used to indicate that the resource monitoring data of the second target cloud platform is requested to be acquired; the receiving module The resource monitoring data is further received by the second target cloud platform, and the integration module is configured to integrate the resource monitoring data fed back by the second target cloud platform to obtain resource monitoring data of the hybrid cloud. Based on the above system, the resources of the hybrid cloud can be uniformly monitored, thereby improving the resource monitoring efficiency of the hybrid cloud.
  • the hybrid cloud resource monitoring system may be a hardware device, a software, or a hardware instruction software.
  • the modules and units described above may be provided in functional modules within the hybrid cloud resource monitoring system.
  • FIG. 10 is also a hardware structural block diagram of a resource monitoring device of a hybrid cloud.
  • the resource monitoring system of the hybrid cloud may include: a processor 1, a communication interface 2, a memory 3, and a communication bus 4; wherein the processor 1 and the communication The interface 2 and the memory 3 complete communication with each other via the communication bus 4.
  • the communication interface 2 can be an interface of a communication module, such as an interface of a GSM module.
  • the processor 1 is for executing a program; the memory 3 is for storing a program; the program may include program code, and the program code includes computer operation instructions.
  • the processor 1 may be a central processing unit CPU, or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application;
  • the memory 3 may include a high speed RAM memory. It may also include a non-volatile memory, such as at least one disk storage.
  • the program can be specifically used to:
  • the steps of a method or algorithm described in connection with the embodiments disclosed herein can be implemented directly in hardware, a software module executed by a processor, or a combination of both.
  • the software module can be placed in random access memory (RAM), memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or technical field. Any other form of storage medium known.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer And Data Communications (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请提供了一种混合云的接口调用方法及装置，包括：接收调用方发送的混合云的接口调用请求，所述接口调用请求用于指示所述调用方请求调用第一目标云平台的接口；根据所述接口调用请求确定所述第一目标云平台的接口；将所述接口调用请求发送至所述第一目标云平台的接口。通过上述混合云的接口调用方法、装置及系统，能够统一混合云的接口调用，进而使混合云的系统应用及维护更加方便。

Description

一种混合云的接口调用方法及装置
本申请要求于2016年07月08日提交中国专利局、申请号为201610539500.1、发明名称为“一种混合云的接口调用方法、装置及系统”的中国专利申请，以及于2016年07月08日提交中国专利局、申请号为201610539009.9、发明名称为“一种混合云的资源监控方法及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及云计算技术领域，更具体的说，是涉及一种混合云的接口调用方法和装置。
背景技术
云计算是基于互联网的相关服务的增加、使用和交付模式，通常涉及通过互联网来提供动态易扩展且经常是虚拟化的资源。随着云计算技术的发展，出现了很多不同类型的云平台，云平台可以按照云计算方式划分为Openstack云平台、Qcloud云平台或AWS云平台等。
融合了公有的云平台及私有的云平台的云计算技术的称为混合云。目前，越来越多的企业具有对外及对内两种服务，在对外服务时，出于成本节约考虑，企业希望可以应用公有的云平台，在对内服务时，出于安全考虑，企业希望可以应用私有的云平台，因此，混合云越来越流行。
由于混合云融合的不同类型的云平台都是独立部署的，不同类型的云平台间的接口调用标准不同，因此，一个混合云中存在多种不同的接口调用方法，无法统一，给混合云的系统应用及维护带来了极大的不便。
另外，在云计算的应用过程中，需要监控云平台的资源(如，表征云平台的运行状态的各项指标)，以帮助用户了解云平台的运行状况。由于现有技术中不同类型的云平台间的资源监控标准不同，因此，混合云的资源监控需要在不同类型的云平台之间轮换执行，即用户需要在其中一个云平台执行完资源监控之后，切换到另一个云平台继续执行资源监控，导致混合云的资源监控效率非常低。
发明内容
有鉴于此，本发明提供了一种混合云的接口调用方法及装置，以实现对混合云的接口调用的统一。
本申请实施例提供了一种混合云的接口调用方法，所述方法包括：
接收调用方发送的对混合云的接口调用请求，所述接口调用请求用于指示所述调用方请求调用的第一目标云平台的接口；
根据所述接口调用请求确定所述第一目标云平台的接口；
将所述接口调用请求发送至所述第一目标云平台的接口。
本发明实施例还提供了一种混合云的接口调用装置，所述装置包括：
接收模块，用于接收调用方发送的对混合云的接口调用请求，所述接口调用请求用于指示所述调用方请求调用的第一目标云平台的接口；
确定模块，用于根据所述接口调用请求确定所述第一目标云平台的接口；
发送模块，用于将所述接口调用请求发送至所述第一目标云平台的接口。
根据本申请实施例，接收调用方发送的对混合云的接口调用请求，所述接口调用请求用于指示所述调用方请求调用的第一目标云平台的接口；根据所述接口调用请求确定所述第一目标云平台的接口；将所述接口 调用请求发送至所述第一目标云平台的接口。以上述方式，能够统一混合云的接口调用，进而使混合云的系统应用及维护更加方便。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据提供的附图获得其他的附图。
图1为现有混合云的系统框架示意图；
图2为本申请实施例提供的混合云的系统框架示意图；
图3为本申请实施例提供的一种混合云的接口调用方法的流程图；
图4为本申请实施例提供的另一种混合云的接口调用方法的流程图；
图5为本申请实施例提供的混合云的接口调用方法的应用例示意图；
图6为本申请实施例提供的混合云的接口调用装置的结构框图；
图7为本申请实施例提供的混合云的接口调用装置的另一结构框图；
图8为本申请实施例提供的确定模块的结构图；
图9为本申请实施例提供的鉴权模块的结构图；
图10为本申请实施例提供的混合云的接口调用装置的硬件结构框图；
图11为本申请实施例提供的混合云的接口调用系统的结构图；
图12为本申请实施例提供的一种混合云的资源监控方法的流程图；
图13为本申请实施例提供的根据所述混合云的资源监控请求确定所述混合云的第二目标云平台的方法流程图；
图14为本申请实施例提供的一种混合云的资源监控方法的应用例示意图；
图15为本申请实施例提供的一种混合云的资源监控系统的结构框图；
图16为本申请实施例提供的确定模块的结构图；
图17为本申请实施例提供的混合云的资源监控系统的另一结构框图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本申请实施例主要应用于混合云。下面对分别对现有混合云的系统框架和本申请混合云的系统框架进行详细介绍。
请参阅图1，图1为现有混合云的系统框架示意图。如图1所示，混合云包括云系统A和云系统B，两套系统是独立部署的。其中，云系统A对应的应用程序编程接口API-A与云系统B对应的应用程序编程接口API-B相对独立，因此，云系统A与云系统B之间没有任何关联关系。基于此，当用户通过应用层平台需要调度云平台A和云平台B的接口以实现用户业务的处理时，只能分别调用API-A以及API-B，无法实现统一调用。
本申请提供了一种新型混合云，请参阅图2，图2为根据本申请实施例的混合云的系统框架示意图。如图2所示，混合云包括标准应用程序编程接口API、云系统A和云系统B。其中，由于标准应用程序编程接口API同时连接云系统A对应的应用程序编程接口API-A以及云系统B对应的应用程序编程接口API-B，因此，云系统A与云系统B之间具备一定的关联 关系。基于此，当用户通过应用层平台需要调用云平台A和云平台B的接口以实现用户业务的处理时，可以通过调用标准应用程序编程接口API实现统一调度云平台A和云平台B的接口。
基于图2所示的混合云系统，本申请实施例提供了一种混合云的接口调用方法，能够统一混合云的接口调用，进而使混合云的系统应用及维护更加方便。本申请实施例提供的混合云的接口调用方法的执行主体可以为后台服务器。该后台服务器可以为标准应用程序编程接口API的后台服务器。
请参阅图3，图3为本申请实施例提供的一种混合云的接口调用方法的流程图。参照图3，所述方法可以包括：
步骤S300、接收调用方发送的对混合云的接口调用请求，所述接口调用请求用于指示所述调用方请求调用的第一目标云平台的接口。
需要说明的是，调用方可以为应用层平台的后台服务器。目标云平台的接口可以为对应于云平台的不同功能(比如，资源调度，资源监控，资源管理等)的应用程序编程接口API，对此，本实施例不进行任何限定。
步骤S310、根据所述接口调用请求确定所述第一目标云平台的接口。
所述混合云的接口调用请求中可以携带一些与所述第一目标云平台的接口相关的参数，通过这些参数即可确定所述目标云平台的接口，具体将通过以下实施例详细说明。
步骤S320、将所述接口调用请求发送至所述第一目标云平台的接口。
本发明实施例提供的混合云的接口调用方法包括：接收调用方发送的对混合云的接口调用请求，所述接口调用请求用于指示所述调用方请求调用的第一目标云平台的接口；根据所述接口调用请求确定所述第一目标云平台的接口；将所述接口调用请求发送至所述第一目标云平台的接口。通过上述接口调用方法，能够统一混合云的接口调用，进而使混合云的系 统应用及维护更加方便。
图4示出了本申请实施例提供的另一种混合云的接口调用方法的流程图。参照图4，所述方法可以包括：
步骤S400、接收调用方发送的对混合云的接口调用请求，所述接口调用请求用于指示所述调用方请求调用的第一目标云平台的接口。
具体的，在本实施例中，可以接收调用方发送的包括有统一资源定位符URL地址的接口调用请求。
步骤S410、对所述接口调用请求进行鉴权，如果鉴权通过，则执行步骤S420至步骤S430，如果鉴权不通过，则结束整个流程。
为保证上述标准API的调用安全性，本申请实施例还公开了一种接口调用请求鉴权方式，具体将通过如下内容说明。
调用方预先需要向标准应用程序编程接口API的后台服务器申请一个账户，该账户至少包括AccessKey和SecretKey这两个参数，其中，AccessKey用于标识调用者的身份，SecretKey是用于加密签名字符串和标准API的后台服务器端验证签名字符串的密钥。
在本实施例中，调用方可以向标准API发送基于HTTP(Hyper Text Transfer Protocol，超文本传输)协议生成的接口调用请求以实现对混合云的资源的调度。接口调用请求包括请求类型(HTTP Method，如，GET/POST/PATCH/PUT/DELETE等)和URL(Uniform Resource Locator，统一资源定位符)地址。由于混合云中包括多种不同类型的云平台，因此，可以通过在URL地址中增加云类型参数来表示该HTTP请求调用的第一目标云平台的类型，比如，tocloud表示请求调用的第一目标云平台的类型为Openstack云平台，tacloud表示请求调用的第一目标云平台的类型为AWS，tqcloud表示请求调用的第一目标云平台的类型为Qcloud。另外，由于同一种类型的目标云平台下可能包含多个不同区域(即，机房)的接口，因此， 可以通过在URL地址中增加region参数来表示该HTTP请求调用的第一目标云平台的接口的区域，比如，region-002表示第二区域的接口。比如，HTTP请求GTE http://api.cloud.com/v1.0/tacloud/servers？region＝region-002表示调用方想调用云平台类型为AWS的第二区域的接口。
在调用方将接口调用请求发送至标准API时，需要将存储有如表1所示的公共参数的HTTP Header同时发送至标准API。其中，Signature是基于HMAC-SHA1算法，使用用户验证码AccessKey对应的密钥参数SecretKey对由请求类型HTTP Method、时间戳参数Timestamp、URL地址、平台验证码AppKey以及用户验证码AccessKey组成的字符串进行签名再使用Base64进行编码得到的签名串。
表1
Figure PCTCN2017092259-appb-000001
比如，调用方预先向标准API的后台服务器申请的账户中包括的 AccessKey和SecretKey的参数值分别如下：
AccessKey：AKIAIOSFODNN7EXAMPLE；
SecretKey：wJalrXUtnFEMIK7MDENGbPxRfiCYEXAMPLEKEY；
调用方向标准API发送的接口调用请求为：
GEThttp://api.cloud.com/v1.0/openstack-0001/servers？name＝my_server；
Timestamp以及AppKey的参数值分别如下：
Timestamp：1462333570；
AppKey：APP-001；
则对字符串‘GET’+‘1462333570’+http://api.cloud.com/v1.0/openstack-0001/servers？name＝my_server’+‘APP-001’+‘AKIAIOSFODNN7EXAMPLE’使用HMAC-SHA1算法和wJalrXUtnFEMIK7MDENGbPxRfiCYEXAMPLEKEY签名，得到hex＝e360a54f95c81dc5fc28d667a19fe0d11f1b0d33，将hex使用Base64进行编码即可获得Signature＝42ClT5XIHcX8KNZnoZ/g0R8bDTM。
因此，调用方发送至标准API的接口调用请求如下：
GET http://api.cloud.com/v1.0/openstack-0001/servers？name＝my_server
调用方发送至标准API的HTTP Header如下：
Timestamp 1462333570
AppKey APP-001
AccessKey AKIAIOSFODNN7EXAMPLE
Signature 42ClT5XIHcX8KNZnoZ/g0R8bDTM
标准API将接收到的接口调用请求以及HTTP Header传输至其后台服务器，其后台服务器查询数据库得到预先分配给调用方的参数SecretKey，并通过该参数对Signature进行鉴权，如果鉴权之后获得的HTTP Method、 Timestamp、URL、AppKey以及AccessKey组成的字符串中各项值与标准API接收到的接口调用请求以及HTTP Header中的值完全一致，则表示鉴权通过，也即，该调用方可以调用标准API，如果鉴权之后获得的HTTP Method、Timestamp、URL、AppKey以及AccessKey组成的字符串中各项值与标准API的将收到的接口调用请求以及HTTP Header中的值不完全一致，则表示鉴权未通过，也即，该调用方不可以调用标准API。
步骤S420、根据所述接口调用请求确定所述第一目标云平台的接口。
在本步骤中，可采用如下方式确定第一目标云平台的接口：根据所述URL地址中的云平台类型参数确定第一目标云平台的类型；根据所述URL地址中的region参数确定第一目标云平台的接口的区域；根据所述第一目标云平台的类型和所述第一目标云平台的接口的区域确定处于所述区域内的接口为所述第一目标云平台的接口。
步骤S430、将所述接口调用请求发送至所述第一目标云平台的接口。
在本实施例中，增加了上述鉴权方式，能够保证合法用户成功调度标准API，而非合法用户则无法成功调度标准API，进一步保证了混合云资源的调度安全性。
本申请实施例提供的混合云的接口调用方法的应用例可以如下：
以用户甲通过应用层要调度的混合云包含云平台A、云平台B、云平台C为例，云平台A、云平台B、云平台C分别于API-A、API-B、API-C对应。云平台A的类型为Openstack云平台，机房区域为华北地区，包括云服务器a1、a2、a3，其对应的资源调度API为API-A，云平台B的类型为AWS，机房区域为华南地区，包括云服务器b1、b2、b3，其对应的资源调度API为API-B，云平台C的类型为Qcloud，机房区域为华中地区，包括云服务器c1、c2、c3，其对应的资源调度API为API-C。
请参阅图5，应用层平台提供接口调用申请界面，用户甲在接口调用 申请界面触发申请接口调用按钮，则生成对混合云的接口调用请求。例如，该接口调用请求具体为GTE http://api.cloud.com/v1.0/tocloud/servers？region＝region-001，用于指示调度云服务器a1、a2、a3的资源。应用层平台获取上述接口调用请求之后，将该接口调用请求发送给标准API对应的后台服务器，标准API对应的后台服务器确定该接口调用请求对应的目标云平台的接口为API-A，则标准API对应的后台服务器将混合云的接口调用请求通过API-A发送至云平台A，云平台A对自身的资源进行调度，获取相应的资源调度结果，并将资源调度结果依次通过API-A和标准API反馈至应用层平台的后台服务器，应用层平台的后台服务器通过接口调用申请界面展示给用户甲。
下面对本申请实施例提供的混合云的接口调用装置进行介绍，下文描述的混合云的接口调用装置可与上文混合云的接口调用方法相互对应参照。
图6为本申请实施例提供的混合云的接口调用装置的结构框图，该混合云的接口调用装置具体可以为后台服务器。参照图6，该混合云的接口调用装置可以包括：
接收模块60，用于接收调用方发送的对混合云的接口调用请求，所述接口调用请求用于指示所述调用方请求调用的第一目标云平台的接口；
确定模块61，用于根据所述接口调用请求确定所述第一目标云平台的接口；
发送模块62，用于将所述接口调用请求发送至所述第一目标云平台的接口。
图7为本申请实施例提供的混合云的接口调用装置的另一结构框图，该混合云的接口调用装置具体可以为后台服务器。参照图7，该混合云的接口调用装置可以包括：
接收模块70，用于接收调用方发送的对混合云的接口调用请求，所述接口调用请求用于指示所述调用方请求调用的第一目标云平台的接口；
鉴权模块71，用于在所述根据所述接口调用请求确定所述第一目标云平台的接口之前，对所述接口调用请求进行鉴权；如果鉴权通过，则触发确定模块72根据所述接口调用请求确定所述第一目标云平台的接口。
确定模块72，用于根据所述接口调用请求确定所述第一目标云平台的接口；
发送模块73，用于将所述接口调用请求发送至所述第一目标云平台的接口。
在一种实现方式中，所述接收模块具体用于：
接收调用方发送的包括有统一资源定位符URL地址的接口调用请求。
在一种实现方式中，图8示出了确定模块的结构图，参阅图8，该确定模块具体包括：
类型确定单元80，用于根据所述URL地址中的云平台类型参数确定第一目标云平台的类型；
区域确定单元81，用于根据所述URL地址中的region参数确定第一目标云平台的接口的区域；
目标云平台的接口确定单元82，用于确定处于所述区域内的接口为所述第一目标云平台的接口。
在一种实现方式中，图9示出了鉴权模块的结构图，参阅图9，该鉴权模块具体包括：
接收单元90，用于接收调用方发送的HTTP Header，所述HTTP Header中包含时间戳参数Timestamp、平台验证码AppKey、用户验证码AccessKey以及签名串Signature；
查询单元91，用于获得预先分配给所述调用方的密钥参数SecretKey；
处理单元92，用于使用所述密钥参数SecretKey对所述签名串Signature进行鉴权，获得HTTP Method、Timestamp、URL地址、AppKey以及AccessKey组成的字符串；当所述字符串中HTTP Method与所述接口调用请求中的请求类型一致，且，所述字符串中URL地址与所述接口调用请求中的URL地址一致，且，所述字符串中Timestamp与所述HTTP Header中的Timestamp一致，且，所述字符串中AppKey与所述HTTP Header中的AppKey一致，且，所述字符串中AccessKey与所述HTTP Header中的AccessKey一致时，表示鉴权通过。
在一种实现方式中，混合云的接口调用装置可以为硬件设备，也可以为软件，也可以为硬件指令软件。上文描述的模块、单元可以设置于混合云的接口调用装置内的功能模块。图10示出了混合云的接口调用装置的硬件结构框图，参照图10，混合云的接口调用装置可以包括：处理器1，通信接口2，存储器3和通信总线4；其中处理器1、通信接口2、存储器3通过通信总线4完成相互间的通信。通信接口2可以为通信模块的接口，如GSM模块的接口。
处理器1，用于执行程序；存储器3，用于存放程序；程序可以包括程序代码，所述程序代码包括计算机操作指令。
处理器1可能是一个中央处理器CPU，或者是特定集成电路ASIC(Application Specific Integrated Circuit)，或者是被配置成实施本申请实施例的一个或多个集成电路。存储器3可能包含高速RAM存储器，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。
其中，程序可具体用于：
接收调用方发送的对混合云的接口调用请求，所述接口调用请求用 于指示所述调用方请求调用的第一目标云平台的接口；
根据所述接口调用请求确定所述第一目标云平台的接口；
将所述接口调用请求发送至所述第一目标云平台的接口。
下面对本发明提供的混合云的接口调用系统进行介绍，该混合云的接口调用系统的结构图如图11所示，包括，应用层平台的后台服务器10和标准API的后台服务器20。
其中，应用层平台的后台服务器，用于接收用户发送的对混合云的接口调用请求并将所述接口调用请求发送至标准API的后台服务器，所述接口调用请求用于指示所述调用方请求调用的第一目标云平台的接口；
标准API的后台服务器，用于接收所述应用层平台的后台服务器发送的接口调用请求，并根据所述接口调用请求确定所述第一目标云平台的接口，将所述接口调用请求发送至所述第一目标云平台的接口。
在一种实现方式中，所述标准API的后台服务器还用于在所述根据所述接口调用请求确定所述第一目标云平台的接口之前，对所述接口调用请求进行鉴权；如果鉴权通过，则根据所述接口调用请求确定所述第一目标云平台的接口。
在一种实现方式中，所述标准API的后台服务器具体用于接收所述应用层平台的后台服务器发送的包括有统一资源定位符URL地址的接口调用请求。
在一种实现方式中，所述标准API的后台服务器具体用于：
根据所述URL地址中的云平台类型参数确定第一目标云平台的类型；
根据所述URL地址中的region参数确定第一目标云平台的接口的区域；
确定处于所述区域内的接口为所述第一目标云平台的接口。
所述标准API的后台服务器具体用于：
接收调用方发送的HTTP Header，所述HTTP Header中包含时间戳参数Timestamp、平台验证码AppKey、用户验证码AccessKey以及签名串Signature；
获得预先分配给所述调用方的密钥参数SecretKey；
使用所述密钥参数SecretKey对所述签名串Signature进行鉴权，获得由请求类型HTTP Method、时间戳参数Timestamp、URL地址、平台验证码AppKey以及用户验证码AccessKey组成的字符串；
当所述字符串中请求类型HTTP Method与所述接口调用请求中的请求类型一致，且，所述字符串中URL地址与所述接口调用请求中的URL地址一致，且，所述字符串中时间戳参数Timestamp与所述HTTP Header中的时间戳参数Timestamp一致，且，所述字符串中平台验证码AppKey与所述HTTP Header中的平台验证码AppKey一致，且，所述字符串中用户验证码AccessKey与所述HTTP Header中的用户验证码AccessKey一致时，表示鉴权通过。
另外，本申请实施例还提供了一种混合云的资源监控方法，能够实现统一监控混合云的资源，提高混合云的资源监控效率。本申请实施例提供的混合云的资源监控方法的执行主体可以为后台服务器。
后台服务器可为云服务自助平台对应的服务器，该服务器除了具备普通的云服务功能之外，还记录有创建所述混合云时生成的资源信息表，并且，在接收到对混合云的资源监控请求后，根据所述对混合云的资源监控请求确定所述混合云的至少一个第二目标云平台，并建立服务器与各第二目标云平台间的信号通路实现统一控制各个第二目标云平台获取各自的资源监控数据，进而得到混合云的资源监控数据。
后台服务器也可以为标准应用程序编程接口API的服务器，该标准API的服务器记录有创建所述混合云时生成的资源信息表，在接收到用户通过云服务自助平台发送的对混合云的资源监控请求之后，根据所述对混合云的资源监控请求确定所述混合云的至少一个第二目标云平台，并建立服务器与各第二目标云平台间的信号通路实现统一控制各个第二目标云平台获取各自的资源监控数据，进而得到混合云的资源监控数据，并将得到的混合云的资源监控数据反馈给云服务自助平台，以展示给用户。
具体地，本申请实施例提供的一种混合云的资源监控方法包括：
接收对所述混合云的资源监控请求，所述资源监控请求用于指示请求获取所述混合云的资源监控数据；
根据所述资源监控请求确定所述混合云的第二目标云平台；
向所述第二目标云平台发送对所述第二目标云平台的资源监控请求，所述对所述第二目标云平台的资源监控请求用于指示请求获取所述第二目标云平台的资源监控数据；以及
接收所述第二目标云平台反馈的资源监控数据。
请参阅图12，图12为本申请实施例提供的一种混合云的资源监控方法的流程图。参照图12，所述方法可以包括：
步骤S1200、接收对混合云的资源监控请求，所述对混合云的资源监控请求用于指示请求获取所述混合云的资源监控数据。
在本实施例中，对混合云的资源监控请求可以是用户通过云服务自助平台发出的，旨在获取混合云的资源监控数据以了解混合云的运行状况，并根据混合云的运行状况及时作出应对策略。
在本实施例中，可以获取混合云的多种资源监控数据，具体的，可以接收混合云的云服务器的中央处理器CPU资源、云服务器的内存资源、云服务器的内网带宽资源以及云服务器的磁盘资源中任意一种或多种资源 的监控请求。其中，云服务器的中央处理器CPU资源包括CPU利用率以及CPU平均负载，云服务器的内存资源包括内存使用量以及内存使用率，云服务器的内网带宽资源包括出带宽、入带宽，以及出包量、入包量，云服务器的磁盘资源包括磁盘读利用率以及磁盘写利用率。
步骤S1210、根据对所述混合云的资源监控请求确定所述混合云的第二目标云平台。
所述混合云的资源监控请求中包括所述混合云中各个云服务器的实例ID信息。在一个实现方式中，可以根据所述混合云中各个云服务器的实例ID信息确定所述混合云的第二目标云平台。具体方式将通过以下实施例详细说明。
步骤S1220、向所确定的第二目标云平台发送对所述第二目标云平台的资源监控请求，对所述第二目标云平台的资源监控请求用于指示请求获取所述第二目标云平台的资源监控数据。
当确定待监控的混合云的资源包括多个第二目标云平台的资源时，在本实施例中，通过上述步骤可以将一个混合云的资源监控请求拆分成多个第二目标云平台的资源监控请求，并把多个第二目标云平台的资源监控请求分别发送给对应的第二目标云平台，以使多个第二目标云平台同步获取自身的资源监控数据。
步骤S1230、接收各第二目标云平台反馈的资源监控数据。
各第二目标云平台同步获取自身的资源监控数据之后，将获取的资源监控数据反馈至后台服务器。
步骤S1240、整合各第二目标云平台反馈的资源监控数据，得到所述混合云的资源监控数据。
后台服务器接收各第二目标云平台反馈的资源监控数据之后，可以对各第二目标云平台反馈的资源监控数据进行整合，得到所述混合云的资 源监控数据。
需要说明的是，本实施例中所提到的整合具体可以将各第二目标云平台反馈的资源监控数据整合为一个用于表示所述混合云的运行状况的资源监控数据。
在一个实现方式中，在得到混合云的资源监控数据之后，还可以显示所述混合云的资源监控数据。
本发明实施例提供的混合云的资源监控方法包括：接收对混合云的资源监控请求，对所述混合云的资源监控请求用于指示请求获取所述混合云的资源监控数据；根据对所述混合云的资源监控请求确定所述混合云的至少一个第二目标云平台；向所确定的各第二目标云平台发送对第二目标云平台的资源监控请求，所述第二目标云平台的资源监控请求用于指示请求获取所述第二目标云平台的资源监控数据；接收各第二目标云平台反馈的资源监控数据；整合各第二目标云平台反馈的资源监控数据，得到所述混合云的资源监控数据。基于上述方法，能够统一监控混合云的资源，进而能够提高混合云的资源监控效率。
图13示出了本申请实施例提供的根据对所述混合云的资源监控请求确定所述混合云的至少一个第二目标云平台的方法流程图。参照图13，该方法可以包括：
步骤S1300、读取对所述混合云的资源监控请求中包含的所述混合云中的各个云服务器的实例ID信息。
步骤S1310、调取创建所述混合云时生成的资源信息表。
在所述混合云创建成功之后，会在后台服务器存储一个资源信息表，本实施例中，可以调取创建所述混合云时生成的资源信息表来确定所述混合云的至少一个第二目标云平台，具体将通过下述内容详细说明。
步骤S1320、根据所述混合云中的各个云服务器的实例ID信息以及 所述资源信息表确定所述混合云的各个云服务器对应的第二目标云平台的访问地址，得到所述混合云的至少一个第二目标云平台的访问地址。
需要说明的是，上述资源信息表中记载有所述混合云的资源相关信息，比如，所述混合云中各个云服务器的实例ID信息，与各个云服务器的实例ID信息对应的机房信息，所述机房信息至少包括所述混合云的各个云服务器对应的第二目标云平台的访问地址。则，在本实施例中，根据所述混合云中各个云服务器的实例ID信息以及所述资源信息表确定所述混合云的各个云服务器对应的第二目标云平台的访问地址可以通过如下方式实现：读取所述资源信息表中记载的与所述混合云中的各个云服务器的实例ID信息对应的机房信息，所述机房信息中包括所述混合云中的各个云服务器对应的第二目标云平台的访问地址；根据与所述混合云中的各个云服务器的实例ID信息对应的机房信息确定所述混合云的各个云服务器对应的第二目标云平台的访问地址。
在确定所述混合云的各个云服务器对应的第二目标云平台的访问地址之后，在一种实现方式中，所述向所述至少一个第二目标云平台发送目标云平台的资源监控请求，包括：
根据各个云服务器对应的第二目标云平台的访问地址，确定各个云服务器对应的第二目标云平台的应用程序编程接口API；
通过各第二目标云平台的应用程序编程接口API向各第二目标云平台发送对第二目标云平台的资源监控请求，对所述第二目标云平台的资源监控请求用于指示请求获取与所述第二目标云平台对应的各个云服务器的资源监控数据。
本发明实施例提供的混合云的资源监控方法的应用例可以如下：
以用户甲通过云服务自助平台要监控的混合云包含云平台A、云平台B、云平台C为例，云平台A、云平台B、云平台C分别于API-A、API-B、 API-C对应。云平台A的机房区域为华北地区，包括云服务器a1、a2、a3，其对应的云平台访问地址为API-A，云平台B的机房区域为华南地区，包括云服务器b1、b2、b3，其对应的云平台访问地址为API-B，云平台C的机房区域为华中地区，包括云服务器c1、c2、c3，其对应的云平台访问地址为API-C。
请参阅图5，云服务自助平台提供资源监控申请界面，用户甲在资源监控申请界面触发资源监控按钮，则生成对混合云的资源监控请求，该资源监控请求用于指示获取云服务器a1、a2、a3、b1、b2、b3、c1、c2及c3的内存资源监控数据。云服务自助平台获取上述混合云的资源监控请求之后，将该混合云的资源监控请求发送给标准API对应的后台服务器，标准API对应的后台服务器根据自身存储的资源信息表确定与上述云服务器a1、a2、a3对应的机房信息为华北地区，该地区对应的云平台访问地址为API-A，与上述云服务器b1、b2、b3对应的机房信息为华南地区，该地区对应的云平台访问地址为API-B，以及与上述云服务器c1、c2、c3对应的机房信息为华中地区，该地区对应的云平台访问地址为API-C，则标准API对应的后台服务器将混合云的资源监控请求拆分为云平台A的资源监控请求、云平台B的资源监控请求以及云平台C的资源监控请求，并将上述云平台A的资源监控请求通过API-A发送至云平台A，将上述云平台B的资源监控请求通过API-B发送至云平台B，将上述云平台C的资源监控请求通过API-C发送至云平台C，云平台A、云平台B、云平台C则分别对自身的内存资源进行监控，获取相应的内存资源监控数据，并将获取的内存资源监控数据依次通过API-A、API-B、API-C、标准API反馈至云服务自助平台，云服务自助平台通过界面展示给用户甲。
下面对本发明实施例提供的混合云的资源监控装置进行介绍，下文描述的混合云的资源监控装置可与上文混合云的资源监控方法相互对应参 照。
图15为本申请实施例提供的一种混合云的资源监控系统的结构框图，该混合云的资源监控装置具体可以为后台服务器，参照图15，该混合云的资源监控装置可以包括：
接收模块50，用于接收对混合云的资源监控请求，对所述混合云的资源监控请求用于指示请求获取所述混合云的资源监控数据；
确定模块51，用于根据对所述混合云的资源监控请求确定所述混合云的至少一个第二目标云平台；
发送模块52，用于向所确定的各第二目标云平台发送对各第二目标云平台的资源监控请求，所述第二目标云平台的资源监控请求用于指示请求获取所述第二目标云平台的资源监控数据；
所述接收模块50还用于接收各第二目标云平台反馈的资源监控数据；
整合模块53，用于整合各第二目标云平台反馈的资源监控数据，得到所述混合云的资源监控数据。
在一种实现方式中，图16示出了确定模块51的结构图，参阅图16，该确定模块51具体包括：
实例ID信息读取单元510，用于读取对所述混合云的资源监控请求中包含的所述混合云中的各个云服务器的实例ID信息；
资源信息表调取单元511，用于调取创建所述混合云时生成的资源信息表；
访问地址确定单元512，用于根据所述混合云中的各个云服务器的实例ID信息以及所述资源信息表确定所述混合云中的各个云服务器对应的第二目标云平台的访问地址，得到所述混合云对应的至少一个第二目标云平台的访问地址。
在一种实现方式中，所述访问地址确定单元具体用于；
读取所述资源信息表中记载的与所述混合云中的各个云服务器的实例ID信息对应的机房信息，所述机房信息中包括所述混合云中的各个云服务器对应的第二目标云平台的访问地址；
根据与所述混合云中各个云服务器的实例ID信息对应的机房信息确定所述混合云的各个云服务器对应的第二目标云平台的访问地址。
在一种实现方式中，所述发送模块包括：
API确定单元，用于根据各个云服务器对应的第二目标云平台的访问地址，确定各个云服务器对应的第二目标云平台的应用程序编程接口API；
发送单元，用于通过各第二目标云平台的应用程序编程接口API向各第二目标云平台发送目标云平台的资源监控请求，所述第二目标云平台的资源监控请求用于指示请求获取与所述第二目标云平台对应的各个云服务器的资源监控数据。
在一种实现方式中，所述接收模块具体用于：
接收混合云的云服务器的中央处理器CPU资源、云服务器的内存资源、云服务器的内网带宽资源以及云服务器的磁盘资源中任意一种或多种资源的监控请求。
在一种实现方式中，图17示出了本发明实施例提供的混合云的资源监控系统的另一结构框图，结合图15所示，该混合云的资源监控系统还包括：
显示模块54，用于在所述整合各第二目标云平台反馈的资源监控数据，得到所述混合云的资源监控数据之后，显示所述混合云的资源监控数据。
本申请实施例提供的混合云的资源监控系统包括：接收模块，用于接收对混合云的资源监控请求，对所述混合云的资源监控请求用于指示请 求获取所述混合云的资源监控数据；确定模块，用于根据对所述混合云的资源监控请求确定所述混合云的至少一个第二目标云平台；发送模块，用于向所确定的各第二目标云平台发送对各第二目标云平台的资源监控请求，所述第二目标云平台的资源监控请求用于指示请求获取所述第二目标云平台的资源监控数据；所述接收模块还用于接收各第二目标云平台反馈的资源监控数据；整合模块，用于整合各第二目标云平台反馈的资源监控数据，得到所述混合云的资源监控数据。基于上述系统，能够统一监控混合云的资源，进而能够提高混合云的资源监控效率。
在一种实现方式中，混合云的资源监控系统可以为硬件设备，也可以为软件，也可以为硬件指令软件。上文描述的模块、单元可以设置于混合云的资源监控系统内的功能模块。图10也可以作为混合云的资源监控装置的硬件结构框图，参照图10，混合云的资源监控系统可以包括：处理器1，通信接口2，存储器3和通信总线4；其中处理器1、通信接口2、存储器3通过通信总线4完成相互间的通信。通信接口2可以为通信模块的接口，如GSM模块的接口。
处理器1，用于执行程序；存储器3，用于存放程序；程序可以包括程序代码，所述程序代码包括计算机操作指令。
处理器1可能是一个中央处理器CPU，或者是特定集成电路ASIC(Application Specific Integrated Circuit)，或者是被配置成实施本申请实施例的一个或多个集成电路；存储器3可能包含高速RAM存储器，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。
其中，程序可具体用于：
接收对混合云的资源监控请求，对所述混合云的资源监控请求用于指示请求获取所述混合云的资源监控数据；
根据对所述混合云的资源监控请求确定所述混合云的第二目标云平 台；
向所述第二目标云平台发送对所述第二目标云平台的资源监控请求，所述第二目标云平台的资源监控请求用于指示请求获取所述第二目标云平台的资源监控数据；
接收所述第二目标云平台反馈的资源监控数据。
在不冲突的情况下，上述混合云的接口调用方法和资源监控方法可以互相结合。
本说明书中各个实施例采用递进的方式描述，每个实施例重点说明的都是与其他实施例的不同之处，各个实施例之间相同相似部分互相参见即可。对于实施例公开的装置而言，由于其与实施例公开的方法相对应，所以描述的比较简单，相关之处参见方法部分说明即可。
专业人员还可以进一步意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
结合本文中所公开的实施例描述的方法或算法的步骤可以直接用硬件、处理器执行的软件模块，或者二者的结合来实施。软件模块可以置于随机存储器(RAM)、内存、只读存储器(ROM)、电可编程ROM、电可擦除可编程ROM、寄存器、硬盘、可移动磁盘、CD-ROM、或技术领域内所公知的任意其它形式的存储介质中。
对所公开的实施例的上述说明，使本领域专业技术人员能够实现或使用本发明。对这些实施例的多种修改对本领域的专业技术人员来说将是 显而易见的，本文中所定义的一般原理可以在不脱离本发明的精神或范围的情况下，在其它实施例中实现。因此，本发明将不会被限制于本文所示的这些实施例，而是要符合与本文所公开的原理和新颖特点相一致的最宽的范围。

Claims (20)

  1. 一种混合云的接口调用方法，其特征在于，所述方法包括：
    接收调用方发送的对混合云的接口调用请求，所述接口调用请求用于指示所述调用方请求调用的第一目标云平台的接口；
    根据所述接口调用请求确定所述第一目标云平台的接口；
    将所述接口调用请求发送至所述第一目标云平台的接口。
  2. 根据权利要求1所述的方法，其特征在于，所述接口调用请求包括统一资源定位符URL地址，
    所述根据所述接口调用请求确定所述第一目标云平台的接口，包括：
    根据所述URL地址中的云平台类型参数确定所述第一目标云平台的类型；
    根据所述URL地址中的region参数确定所述第一目标云平台的接口的区域；
    确定处于所述区域内的接口为所述第一目标云平台的接口。
  3. 根据权利要求2所述的方法，其特征在于，在所述根据所述接口调用请求确定所述第一目标云平台的接口之前，所述方法还包括：
    对所述接口调用请求进行鉴权；
    如果鉴权通过，则根据所述接口调用请求确定所述第一目标云平台的接口。
  4. 根据权利要求3所述的方法，其特征在于，所述接口调用请求还包括请求类型HTTP Method，所述方法还包括：
    接收调用方发送的HTTP Header，所述HTTP Header中包含时间戳参数Timestamp、平台验证码AppKey、用户验证码AccessKey以及签名串Signature；
    则所述对所述接口调用请求进行鉴权，包括：
    获得预先分配给所述调用方的密钥参数SecretKey；
    使用所述密钥参数SecretKey对所述签名串Signature进行鉴权，获得由 请求类型HTTP Method、时间戳参数Timestamp、URL地址、平台验证码AppKey以及用户验证码AccessKey组成的字符串；
    当所述字符串中请求类型HTTP Method与所述接口调用请求中的请求类型一致，且，所述字符串中URL地址与所述接口调用请求中的URL地址一致，且，所述字符串中时间戳参数Timestamp与所述HTTP Header中的时间戳参数Timestamp一致，且，所述字符串中平台验证码AppKey与所述HTTP Header中的平台验证码AppKey一致，且，所述字符串中用户验证码AccessKey与所述HTTP Header中的用户验证码AccessKey一致时，表示鉴权通过。
  5. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    接收对所述混合云的资源监控请求，所述资源监控请求用于指示请求获取所述混合云的资源监控数据；
    根据所述资源监控请求确定所述混合云的第二目标云平台；
    向所述第二目标云平台发送对所述第二目标云平台的资源监控请求，所述对所述第二目标云平台的资源监控请求用于指示请求获取所述第二目标云平台的资源监控数据；
    接收所述第二目标云平台反馈的资源监控数据。
  6. 根据权利要求5所述的方法，其特征在于，所述第二目标云平台有多个，所述方法还包括：
    整合所述多个第二目标云平台反馈的资源监控数据，得到所述混合云的资源监控数据。
  7. 根据权利要求6所述的方法，其特征在于，所述根据所述资源监控请求确定所述混合云的第二目标云平台，包括：
    读取对所述混合云的资源监控请求中包含的所述混合云中的各个云服务器的实例ID信息；
    调取创建所述混合云时生成的资源信息表；
    根据所述混合云中的各个云服务器的实例ID信息以及所述资源信息表确定所述混合云中的各个云服务器对应的第二目标云平台的访问地址，得 到所述混合云的第二目标云平台的访问地址。
  8. 根据权利要求7所述的方法，其特征在于，所述根据所述混合云中的各个云服务器的实例ID信息以及所述资源信息表确定所述混合云中的各个云服务器对应的第二目标云平台的访问地址，包括；
    读取所述资源信息表中记载的与所述混合云中的各个云服务器的实例ID信息对应的机房信息，所述机房信息中包括所述混合云的各个云服务器对应的第二目标云平台的访问地址；
    根据与所述混合云中的各个云服务器的实例ID信息对应的机房信息确定所述混合云中的各个云服务器对应的第二目标云平台的访问地址。
  9. 根据权利要求8所述的方法，其特征在于，所述向所述第二目标云平台发送对所述第二目标云平台的资源监控请求，包括：
    根据各个云服务器对应的第二目标云平台的访问地址，确定各个云服务器对应的第二目标云平台的应用程序编程接口API；
    通过第二目标云平台的应用程序编程接口API向第二目标云平台发送对第二目标云平台的资源监控请求，所述对第二目标云平台的资源监控请求用于指示请求获取与所述第二目标云平台对应的各个云服务器的资源监控数据。
  10. 根据权利要求6所述的方法，其特征在于，所述接收对混合云的资源监控请求包括：
    接收对混合云的云服务器的中央处理器CPU资源、云服务器的内存资源、云服务器的内网带宽资源以及云服务器的磁盘资源中任意一种或多种资源的监控请求。
  11. 一种混合云的接口调用装置，其特征在于，所述装置包括：
    接收模块，用于接收调用方发送的对混合云的接口调用请求，所述接口调用请求用于指示所述调用方请求调用的第一目标云平台的接口；
    确定模块，用于根据所述接口调用请求确定所述第一目标云平台的接口；
    发送模块，用于将所述接口调用请求发送至所述第一目标云平台的接口。
  12. 根据权利要求11所述的装置，其特征在于，所述接口调用请求包括统一资源定位符URL地址，
    所述确定模块包括：
    类型确定单元，用于根据所述URL地址中的云平台类型参数确定所述第一目标云平台的类型；
    区域确定单元，用于根据所述URL地址中的region参数确定所述第一目标云平台的接口的区域；
    目标云平台的接口确定单元，用于确定处于所述区域内的接口为所述第一目标云平台的接口。
  13. 根据权利要求12所述的装置，其特征在于，所述装置还包括：
    鉴权模块，用于在所述根据所述接口调用请求确定所述第一目标云平台的接口之前，对所述接口调用请求进行鉴权；如果鉴权通过，则触发确定模块根据所述接口调用请求确定所述第一目标云平台的接口。
  14. 根据权利要求13所述的装置，其特征在于，所述接口调用请求还包括请求类型HTTP Method，所述鉴权模块包括：
    接收单元，用于接收调用方发送的HTTP Header，所述HTTP Header中包含时间戳参数Timestamp、平台验证码AppKey、用户验证码AccessKey以及签名串Signature；
    查询单元，用于获得预先分配给所述调用方的密钥参数SecretKey；
    处理单元，用于使用所述密钥参数SecretKey对所述签名串Signature进行鉴权，获得由请求类型HTTP Method、时间戳参数Timestamp、URL地址、平台验证码AppKey以及用户验证码AccessKey组成的字符串；当所述字符串中请求类型HTTP Method与所述接口调用请求中的请求类型一致，且，所述字符串中URL地址与所述接口调用请求中的URL地址一致，且，所述字符串中时间戳参数Timestamp与所述HTTP Header中的时间戳参数Timestamp一致，且，所述字符串中平台验证码AppKey与所述HTTP Header 中的平台验证码AppKey一致，且，所述字符串中用户验证码AccessKey与所述HTTP Header中的用户验证码AccessKey一致时，表示鉴权通过。
  15. 根据权利要求11所述的装置，其特征在于，
    所述接收模块，用于接收对所述混合云的资源监控请求，所述对所述混合云的资源监控请求用于指示请求获取所述混合云的资源监控数据；
    所述确定模块，用于根据对所述混合云的资源监控请求确定所述混合云的第二目标云平台；
    所述发送模块，用于向所述第二目标云平台发送对所述第二目标云平台的资源监控请求，所述对所述第二目标云平台的资源监控请求用于指示请求获取所述第二目标云平台的资源监控数据；
    所述接收模块还用于接收所述第二目标云平台反馈的资源监控数据。
  16. 根据权利要求15所述的装置，其特征在于，所述第二目标云平台有多个，所述装置还包括：
    整合模块，用于整合所述多个第二目标云平台反馈的资源监控数据，得到所述混合云的资源监控数据。
  17. 根据权利要求16所述的装置，其特征在于，所述确定模块包括：
    实例ID信息读取单元，用于读取对所述混合云的资源监控请求中包含的所述混合云中的各个云服务器的实例ID信息；
    资源信息表调取单元，用于调取创建所述混合云时生成的资源信息表；
    访问地址确定单元，用于根据所述混合云中的各个云服务器的实例ID信息以及所述资源信息表确定所述混合云中的各个云服务器对应的第二目标云平台的访问地址，得到所述混合云的第二目标云平台的访问地址。
  18. 根据权利要求17所述的装置，其特征在于，所述访问地址确定单元具体用于：
    读取所述资源信息表中记载的与所述混合云中的各个云服务器的实例ID信息对应的机房信息，所述机房信息中包括所述混合云中的各个云服务器对应的第二目标云平台的访问地址；
    根据与所述混合云中的各个云服务器的实例ID信息对应的机房信息确 定所述混合云中的各个云服务器对应的第二目标云平台的访问地址。
  19. 根据权利要求18所述的装置，其特征在于，所述发送模块包括：
    API确定单元，用于根据各个云服务器对应的第二目标云平台的访问地址，确定各个云服务器对应的第二目标云平台的应用程序编程接口API；
    发送单元，用于通过所述第二目标云平台的应用程序编程接口API向所诉第二目标云平台发送对所述第二目标云平台的资源监控请求，所述对所述第二目标云平台的资源监控请求用于指示请求获取与所述第二目标云平台对应的各个云服务器的资源监控数据。
  20. 根据权利要求16所述的装置，其特征在于，所述接收模块具体用于：
    接收混合云的云服务器的中央处理器CPU资源、云服务器的内存资源、云服务器的内网带宽资源以及云服务器的磁盘资源中任意一种或多种资源的监控请求。
PCT/CN2017/092259 2016-07-08 2017-07-07 一种混合云的接口调用方法及装置 WO2018006872A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17823684.0A EP3484125B1 (en) 2016-07-08 2017-07-07 Method and device for scheduling interface of hybrid cloud
US16/191,323 US10965772B2 (en) 2016-07-08 2018-11-14 Interface invocation method and apparatus for hybrid cloud

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201610539009.9A CN107592237B (zh) 2016-07-08 2016-07-08 一种混合云的资源监控方法及系统
CN201610539500.1 2016-07-08
CN201610539500.1A CN106101258B (zh) 2016-07-08 2016-07-08 一种混合云的接口调用方法、装置及系统
CN201610539009.9 2016-07-08

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/191,323 Continuation-In-Part US10965772B2 (en) 2016-07-08 2018-11-14 Interface invocation method and apparatus for hybrid cloud

Publications (1)

Publication Number Publication Date
WO2018006872A1 true WO2018006872A1 (zh) 2018-01-11

Family

ID=60912013

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/092259 WO2018006872A1 (zh) 2016-07-08 2017-07-07 一种混合云的接口调用方法及装置

Country Status (3)

Country Link
US (1) US10965772B2 (zh)
EP (1) EP3484125B1 (zh)
WO (1) WO2018006872A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108848165A (zh) * 2018-06-20 2018-11-20 中国平安人寿保险股份有限公司 业务请求处理方法、装置、计算机设备和存储介质
CN110650216A (zh) * 2019-10-24 2020-01-03 北京天润融通科技股份有限公司 云服务请求方法和装置
CN111641676A (zh) * 2020-04-28 2020-09-08 广州市申迪计算机系统有限公司 一种第三方云监控服务的构建方法及装置
EP3764330A1 (en) 2019-06-18 2021-01-13 Cleveron AS Automated parcel terminal

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180082073A1 (en) * 2016-09-22 2018-03-22 Spectra Logic Corporation Administration over a hybrid cloud
US10749771B2 (en) * 2018-05-18 2020-08-18 Microsoft Technology Licensing, Llc Extensible, secure and efficient monitoring and diagnostic pipeline for hybrid cloud architecture
CN110213092A (zh) * 2019-05-21 2019-09-06 深信服科技股份有限公司 混合云的资源访问方法、平台管理设备、存储介质及装置
US11586507B2 (en) * 2019-07-12 2023-02-21 Trilio Data, Inc. Scalable cloud-based backup method
CN110795182B (zh) * 2019-09-18 2024-09-13 平安科技（深圳）有限公司 云主机创建方法和系统
CN113055410B (zh) * 2019-12-26 2024-07-23 阿里巴巴集团控股有限公司 云资源管理方法、装置、设备、系统及可读存储介质
CN111125232A (zh) * 2019-12-31 2020-05-08 北京奇艺世纪科技有限公司 一种公有云资产信息接入的方法及装置
CN111797414B (zh) * 2020-06-24 2024-08-06 北京青云科技股份有限公司 一种混合云管理方法、系统及云服务平台
CN114024978B (zh) * 2020-07-15 2024-09-03 中移(苏州)软件技术有限公司 一种云资源的同步方法、装置、节点及存储介质
CN112230857B (zh) * 2020-10-22 2023-06-23 深圳软通动力信息技术有限公司 一种混合云系统、混合云盘申请方法和数据存储方法
CN112671859A (zh) * 2020-12-15 2021-04-16 中国人寿保险股份有限公司 一种混合云管理的方法及一种混合云系统
US11805127B1 (en) * 2021-04-16 2023-10-31 Citicorp Credit Services, Inc. (Usa) Processing tokens in identity assertions for access control to resources
CN113438540A (zh) * 2021-06-24 2021-09-24 广州欢网科技有限责任公司 基于广告曝光率的广告预加载播放方法及装置
CN113596128B (zh) * 2021-07-21 2024-02-09 华云数据控股集团有限公司 一种多云平台的资源同步方法、系统及电子设备
CN113872951B (zh) * 2021-09-22 2023-05-26 绿盟科技集团股份有限公司 混合云安全策略下发方法、装置、电子设备和存储介质
CN114928636B (zh) * 2022-07-20 2022-11-04 北京达佳互联信息技术有限公司 接口调用请求处理方法、装置、设备、存储介质和产品
CN115913795B (zh) * 2023-03-10 2023-05-05 湖南泛联新安信息科技有限公司 一种基于多fpga原型验证混合云平台的加密方法和系统
CN117201507A (zh) * 2023-11-08 2023-12-08 苏州元脑智能科技有限公司 云平台切换方法、装置、电子设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102255933A (zh) * 2010-05-20 2011-11-23 中兴通讯股份有限公司 云服务中介、云计算方法及云系统
CN102546735A (zh) * 2011-01-04 2012-07-04 中兴通讯股份有限公司 一种云计算系统、方法及云
CN103701761A (zh) * 2012-09-28 2014-04-02 中国电信股份有限公司 开放接口调用的认证方法与系统
CN104935568A (zh) * 2015-04-20 2015-09-23 成都康赛信息技术有限公司 一种面向云平台接口鉴权签名方法
CN105306534A (zh) * 2015-09-21 2016-02-03 拉扎斯网络科技（上海）有限公司 一种基于开放平台的信息校验方法和开放平台
CN106101258A (zh) * 2016-07-08 2016-11-09 腾讯科技（深圳）有限公司 一种混合云的接口调用方法、装置及系统

Family Cites Families (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110072489A1 (en) * 2009-09-23 2011-03-24 Gilad Parann-Nissany Methods, devices, and media for securely utilizing a non-secured, distributed, virtualized network resource with applications to cloud-computing security and management
US8477350B2 (en) * 2010-03-16 2013-07-02 Google Inc. Cloud-based print service
CN102255935B (zh) * 2010-05-20 2016-06-15 中兴通讯股份有限公司 云服务消费方法、云服务中介及云系统
US9253252B2 (en) * 2011-05-06 2016-02-02 Citrix Systems, Inc. Systems and methods for cloud bridging between intranet resources and cloud resources
US8813190B2 (en) * 2011-05-18 2014-08-19 International Business Machines Corporation Resource upload
US8570572B2 (en) * 2011-05-26 2013-10-29 Xerox Corporation Method and apparatus for printing web-based content via cloud print service
US9767480B1 (en) * 2011-06-20 2017-09-19 Pathmatics, Inc. Systems and methods for discovery and tracking of web-based advertisements
US8745753B1 (en) * 2011-06-20 2014-06-03 Adomic, Inc. Systems and methods for blocking of web-based advertisements
US8924546B1 (en) * 2012-03-21 2014-12-30 Trend Micro Incorporated Roaming bandwidth guidance for mobile computing devices
EP2685697B1 (en) * 2012-07-13 2018-09-12 Awingu Nv A method to obtain a virtual desktop stored in a cloud storage system, a corresponding cloud broker and cloud desktop agent
EP2704398A1 (en) * 2012-08-27 2014-03-05 Awingu Nv A method for content change notification in a cloud storage system, a corresponding cloud broker and cloud agent
EP2706467A1 (en) * 2012-09-05 2014-03-12 Awingu Nv Method for accessing a content item in a cloud storage system, and a corresponding cloud broker, cloud cache agent and client application
KR101547498B1 (ko) 2013-08-08 2015-08-26 삼성전자주식회사 하이브리드 클라우드 환경에서 데이터를 분산하는 방법 및 장치
US9755858B2 (en) 2014-04-15 2017-09-05 Cisco Technology, Inc. Programmable infrastructure gateway for enabling hybrid cloud services in a network environment
US9560037B2 (en) * 2014-06-19 2017-01-31 Microsoft Technology Licensing, Llc Integrated APIs and UIs for consuming services across different distributed networks
CN104113595B (zh) 2014-07-09 2018-01-02 武汉邮电科学研究院 一种基于安全等级划分的混合云存储系统及方法
US10223549B2 (en) * 2015-01-21 2019-03-05 Onion ID Inc. Techniques for facilitating secure, credential-free user access to resources
CN104657220B (zh) 2015-03-12 2018-04-17 广东石油化工学院 混合云中基于截止时间和费用约束的调度模型及方法
US10412166B2 (en) * 2015-07-27 2019-09-10 Presidio Llc Hybrid cloud information management system
US10582001B2 (en) * 2015-08-11 2020-03-03 Oracle International Corporation Asynchronous pre-caching of synchronously loaded resources
CN105610909B (zh) * 2015-12-21 2019-01-18 北京大学 一种基于云-端协同的移动浏览器资源加载优化方法
US10129177B2 (en) * 2016-05-23 2018-11-13 Cisco Technology, Inc. Inter-cloud broker for hybrid cloud networks
US10116725B2 (en) * 2016-05-27 2018-10-30 Intuit Inc. Processing data retrieval requests in a graph projection of an application programming interfaces (API)
US10693947B2 (en) * 2016-09-09 2020-06-23 Microsoft Technology Licensing, Llc Interchangeable retrieval of sensitive content via private content distribution networks
CN112860479A (zh) * 2016-12-26 2021-05-28 华为技术有限公司 存储数据的方法及云数据中心
US10708358B1 (en) * 2019-10-03 2020-07-07 Starfish Technologies LLC Cloud-based scanning systems and remote image processing methods

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102255933A (zh) * 2010-05-20 2011-11-23 中兴通讯股份有限公司 云服务中介、云计算方法及云系统
CN102546735A (zh) * 2011-01-04 2012-07-04 中兴通讯股份有限公司 一种云计算系统、方法及云
CN103701761A (zh) * 2012-09-28 2014-04-02 中国电信股份有限公司 开放接口调用的认证方法与系统
CN104935568A (zh) * 2015-04-20 2015-09-23 成都康赛信息技术有限公司 一种面向云平台接口鉴权签名方法
CN105306534A (zh) * 2015-09-21 2016-02-03 拉扎斯网络科技（上海）有限公司 一种基于开放平台的信息校验方法和开放平台
CN106101258A (zh) * 2016-07-08 2016-11-09 腾讯科技（深圳）有限公司 一种混合云的接口调用方法、装置及系统

Non-Patent Citations (1)

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

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108848165A (zh) * 2018-06-20 2018-11-20 中国平安人寿保险股份有限公司 业务请求处理方法、装置、计算机设备和存储介质
CN108848165B (zh) * 2018-06-20 2022-10-18 中国平安人寿保险股份有限公司 业务请求处理方法、装置、计算机设备和存储介质
EP3764330A1 (en) 2019-06-18 2021-01-13 Cleveron AS Automated parcel terminal
US11625969B2 (en) 2019-06-18 2023-04-11 Cleveron As Automated parcel terminal
EP4254287A2 (en) 2019-06-18 2023-10-04 Cleveron AS Automated parcel terminal
US11922755B2 (en) 2019-06-18 2024-03-05 Cleveron As Automated parcel terminal
CN110650216A (zh) * 2019-10-24 2020-01-03 北京天润融通科技股份有限公司 云服务请求方法和装置
CN110650216B (zh) * 2019-10-24 2022-02-01 北京天润融通科技股份有限公司 云服务请求方法和装置
CN111641676A (zh) * 2020-04-28 2020-09-08 广州市申迪计算机系统有限公司 一种第三方云监控服务的构建方法及装置
CN111641676B (zh) * 2020-04-28 2023-04-18 广州市申迪计算机系统有限公司 一种第三方云监控服务的构建方法及装置

Also Published As

Publication number Publication date
US10965772B2 (en) 2021-03-30
EP3484125A4 (en) 2019-12-25
EP3484125B1 (en) 2022-09-07
EP3484125A1 (en) 2019-05-15
US20190082026A1 (en) 2019-03-14

Similar Documents

Publication Publication Date Title
WO2018006872A1 (zh) 一种混合云的接口调用方法及装置
CN106101258B (zh) 一种混合云的接口调用方法、装置及系统
US9426142B2 (en) Systems and methods for logging into an application on a second domain from a first domain in a multi-tenant database system environment
WO2018112940A1 (zh) 区块链节点的业务执行方法、装置及节点设备
US10659453B2 (en) Dual channel identity authentication
US11632247B2 (en) User security token invalidation
US9589122B2 (en) Operation processing method and device
EP3682364B1 (en) Cryptographic services utilizing commodity hardware
US11265167B2 (en) Methods and systems for network security using a cryptographic firewall
TW202046143A (zh) 資料儲存方法、裝置及設備
WO2015074443A1 (en) An operation processing method and device
US20210092111A1 (en) Network traffic distribution using certificate scanning in agent-based architecture
US11783066B2 (en) Securely sharing files with user devices based on location
CN114500082A (zh) 接入认证方法及装置、设备、服务器、存储介质和系统
WO2015027931A1 (en) Method and system for realizing cross-domain remote command
WO2023021306A1 (en) Systems and methods for data linkage and entity resolution of continuous and un-synchronized data streams
US11968238B2 (en) Policy management system to provide authorization information via distributed data store
CN108809927B (zh) 身份认证方法及装置
US9363274B2 (en) Methods and systems for broadcasting pictures
WO2014201789A1 (zh) 一种业务处理方法、装置及系统
US20240323180A1 (en) Automatically determining authenticated online statuses of edge devices
CN107592229B (zh) 一种服务调用方法、装置及系统
CN114741683A (zh) 访问信息处理方法、装置、计算机设备、存储介质
CN114095173A (zh) 基于区块链的用户认证方法、设备及可读存储介质
CN117354255A (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: 17823684

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: 2017823684

Country of ref document: EP

Effective date: 20190208