Data processing method and system, device

Abstract

This specification provides data processing methods, systems, and apparatus. The data processing method applied to a first resource management platform includes: responding to an initial creation request from a resource user for a resource management unit, creating an initial resource management unit, and determining a target virtual node based on the resource configuration information of the initial resource management unit; using the virtual network interface of the target virtual node, sending a target creation request for the resource management unit to a second resource management platform, so that the second resource management platform responds to the target creation request, creates and runs the target resource management unit, wherein the virtual network interface is used to provide network connectivity between the first and second resource management platforms; while achieving resource pooling among different accounts within the same cloud and multi-cloud disaster recovery scheduling, it can reduce changes to the overall management architecture of the first and second resource management platforms.

Description

Technical Field

[0001] The embodiments in this specification relate to the field of cloud computing technology, and in particular to a data processing method, system, and apparatus. Background Technology

[0002] The goal of the unified resource pool project is to establish a general resource pool to improve resource utilization while ensuring security and stability. For example, an enterprise has purchased a batch of resources for a certain project through account A and launched its own product. However, the general resource pool is produced and managed by account B. How can this project use the general resources of account B without major changes to the management architecture and without affecting existing instances?

[0003] Alternatively, in order to improve the stability and reliability of the cloud by avoiding the impact of data center downtime on users through multi-cloud solutions, how can we reduce the degree of change in the management and control architecture during unified scheduling in a multi-cloud environment? Summary of the Invention

[0004] In view of this, the embodiments of this specification provide two data processing methods. One or more embodiments of this specification simultaneously involve two data processing devices, a data processing system, a computing device, a computer-readable storage medium, and a computer program product, in order to solve the technical defects in the prior art, where the management architecture changes greatly, resulting in a very complex overall architecture and increased difficulty in operation and maintenance, when solving the problems of resource pooling among different accounts in the same cloud and multi-cloud disaster recovery scheduling.

[0005] According to a first aspect of the embodiments of this specification, a data processing method is provided, applied to a first resource management platform, comprising: In response to the resource user's initial creation request for the resource management unit, an initial resource management unit is created, and the target virtual node is determined based on the resource configuration information of the initial resource management unit; Using the virtual network interface of the target virtual node, a target creation request for the resource management unit is sent to the second resource management platform, so that the second resource management platform responds to the target creation request, creates and runs the target resource management unit. The first resource management platform and the second resource management platform are resource management platforms corresponding to different resource accounts of the resource user. The virtual network interface is used to provide network connection between the first resource management platform and the second resource management platform. The target creation request carries the resource configuration information.

[0006] According to a first aspect of the embodiments of this specification, a data processing method is provided, applied to a second resource management platform, comprising: In response to a target creation request sent by the first resource management platform, the target resource management unit is created based on the resource configuration information carried in the target creation request. The target creation request is sent by the first resource management platform using the virtual network interface of the target virtual node when the first resource management platform creates an initial resource management unit in response to the initial creation request of the resource user for the resource management unit, and determines the target virtual node based on the resource configuration information of the initial resource management unit. The first resource management platform and the second resource management platform are resource management platforms corresponding to different resource accounts of the resource user. Determine the target node corresponding to the target resource management unit, and run the target resource management unit on the target node.

[0007] According to a third aspect of the embodiments of this specification, a data processing apparatus is provided, applied to a first resource management platform, comprising: The response module is configured to respond to an initial creation request from a resource user for a resource management unit, create an initial resource management unit, and determine a target virtual node based on the resource configuration information of the initial resource management unit. The sending module is configured to use the virtual network interface of the target virtual node to send a target creation request for the resource management unit to the second resource management platform, so that the second resource management platform responds to the target creation request, creates and runs the target resource management unit. The first resource management platform and the second resource management platform are resource management platforms corresponding to different resource accounts of the resource user. The virtual network interface is used to provide network connection between the first resource management platform and the second resource management platform. The target creation request carries the resource configuration information.

[0008] According to a fourth aspect of the embodiments of this specification, a data processing apparatus is provided, applied to a second resource management platform, comprising: The response module is configured to respond to a target creation request for a resource management unit sent by the first resource management platform, and to create the target resource management unit based on the resource configuration information carried in the target creation request. The target creation request is sent by the first resource management platform using the virtual network interface of the target virtual node when the first resource management platform creates an initial resource management unit in response to the initial creation request of the resource user for the resource management unit, and determines the target virtual node based on the resource configuration information of the initial resource management unit. The first resource management platform and the second resource management platform are resource management platforms corresponding to different resource accounts of the resource user. The determination module is configured to determine the target node corresponding to the target resource management unit and run the target resource management unit on the target node.

[0009] According to a fifth aspect of the embodiments of this specification, a data processing system is provided, including a first resource management platform and a second resource management platform, wherein... The first resource management platform is used to respond to the resource user's initial creation request for the resource management unit, create an initial resource management unit, determine the target virtual node according to the resource configuration information of the initial resource management unit, and send a target creation request for the resource management unit to the second resource management platform using the virtual network interface of the target virtual node. The second resource management platform is used to respond to the target creation request for the resource management unit sent by the first resource management platform, create the target resource management unit according to the resource configuration information carried in the target creation request, determine the target node corresponding to the target resource management unit, and run the target resource management unit on the target node.

[0010] According to a sixth aspect of the embodiments of this specification, a computing device is provided, comprising: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions, which, when executed by the processor, implement the steps of the above-described data processing method.

[0011] According to a seventh aspect of the embodiments of this specification, a computer-readable storage medium is provided that stores a computer program / instructions that, when executed by a processor, implement the steps of the data processing method described above.

[0012] According to an eighth aspect of the embodiments of this specification, a computer program product is provided, including a computer program / instructions that, when executed by a processor, implement the steps of the data processing method described above.

[0013] This specification provides a data processing method in one embodiment, applied to a first resource management platform. In response to an initial creation request from a resource user for a resource management unit, an initial resource management unit is created. Based on the resource configuration information of the initial resource management unit, a target virtual node is determined. The virtual network interface corresponding to this target virtual node can provide network connectivity between the first and second resource management platforms (which belong to different resource accounts of the resource user). Therefore, a target creation request for the resource management unit can be sent to the second resource management platform through the virtual network interface corresponding to the target virtual node. The second resource management platform then responds to the target creation request, creates and runs the target resource management unit. In other words, the first resource management platform can deploy and run the resource management unit on the second resource management platform through the virtual network interface corresponding to the target virtual node, utilizing the resources of the second resource management platform. By using the virtual network interface corresponding to the target virtual node, resource pooling between different accounts within the same cloud and multi-cloud disaster recovery scheduling can be achieved, while reducing changes to the overall management architecture of the first and second resource management platforms. Attached Figure Description Figure 1 This is a schematic diagram illustrating a data processing method provided in one embodiment of this specification. Figure 2 This is a flowchart illustrating a data processing method applied to a first resource management platform, as provided in one embodiment of this specification. Figure 3 This is a flowchart illustrating a data processing method applied to a second resource management platform, as provided in one embodiment of this specification. Figure 4 This is a schematic flowchart illustrating a data processing method applied to a data processing system according to one embodiment of this specification; Figure 5 This is a flowchart illustrating another data processing method applied to a data processing system, provided in one embodiment of this specification. Figure 6 This is a schematic diagram of the structure of a data processing apparatus provided in one embodiment of this specification; Figure 7 This is a schematic diagram of the structure of another data processing device provided in one embodiment of this specification; Figure 8 This is a schematic diagram of the structure of a data processing system provided in one embodiment of this specification; Figure 9 This is a structural block diagram of a computing device provided in one embodiment of this specification. Detailed Implementation

[0014] Many specific details are set forth in the following description to provide a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this specification. Therefore, this specification is not limited to the specific implementations disclosed below.

[0015] The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of this specification. The singular forms “a,” “described,” and “the” as used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0016] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this specification, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0017] Furthermore, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data authorized by the user or fully authorized by all parties. Moreover, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0018] First, the terms and concepts used in one or more embodiments of this specification will be explained.

[0019] Unified resource pool: All products share resources through containerization and mixed deployment technologies, solving the problems of resource fragmentation and low sales rate, and maximizing resource utilization.

[0020] VK: Virtual Kubelet, is a Kubernetes (K8s) broker that allows Kubernetes clusters to interact with other cloud services or edge computing resources, thereby scaling computing resources. It is primarily used to schedule Kubernetes clusters to cloud services (such as Azure, AWS, or custom container platforms) to run workloads on these platforms.

[0021] Multi-cloud disaster recovery: This means that a user's project is deployed simultaneously in multiple cloud vendor environments to ensure the stability and reliability of the project.

[0022] This specification provides two data processing methods, and also relates to two data processing devices, a data processing system, a computing device, a computer-readable storage medium, and a computer program product, which will be described in detail in the following embodiments.

[0023] See Figure 1 , Figure 1 A schematic diagram of a data processing method according to an embodiment of this specification is shown. Specifically, this data processing method is implemented using a data processing system, which includes a first resource management platform and a second resource management platform.

[0024] Specifically, the resource user can send an initial creation request for the resource management unit to the first resource management platform in the server 104 through the end device 102 corresponding to the resource user.

[0025] In response to the resource user's initial creation request for a resource management unit, the first resource management platform creates an initial resource management unit, determines a target virtual node based on the resource configuration information of the initial resource management unit, and sends a target creation request for the resource management unit to the second resource management platform using the virtual network interface of the target virtual node.

[0026] The second resource management platform responds to the first resource management platform by sending a target creation request for a resource management unit. Based on the resource configuration information carried in the target creation request, it creates a target resource management unit, determines the target node corresponding to the target resource management unit, and runs the target resource management unit on the target node.

[0027] When the target resource management unit is running, the server 104 returns a creation success response to the end device 102 corresponding to the resource user.

[0028] The edge device 102 may include a browser, an app (application), or a web application such as an H5 (Hypertext Markup Language 5) application, a lightweight application (also known as a mini-program), or a cloud application. The edge device can be developed based on a software development kit (SDK) provided by the server, such as a real-time communication (RTC) SDK. The edge device can be deployed in an electronic device and depends on the device's operation or certain apps within the device to run. The electronic device may have a display screen and support information browsing, such as a personal mobile terminal like a mobile phone, tablet, or personal computer. Various other types of applications can also be configured in the electronic device, such as human-computer interaction applications, model training applications, text processing applications, web browser applications, shopping applications, search applications, instant messaging tools, email clients, and social media platform software.

[0029] Server 104 can be understood as a server providing various services, including physical servers and cloud servers. Examples include servers providing communication services to multiple clients, servers supporting backend training of models used on clients, and servers processing data sent by clients. It's important to note that Server 104 can be implemented as a distributed server cluster composed of multiple servers, or as a single server. Server 104 can also be a server in a distributed system, or a server integrated with blockchain. Server 104 can also be a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms, or an intelligent cloud computing server or intelligent cloud host with artificial intelligence technology.

[0030] This specification provides a data processing method in one embodiment. In response to an initial creation request from a resource user for a resource management unit, a first resource management platform creates an initial resource management unit and determines a target virtual node based on the resource configuration information of the initial resource management unit. The virtual network interface corresponding to this target virtual node can provide network connectivity between the first and second resource management platforms (which belong to different resource accounts of the resource user). Therefore, a target creation request for the resource management unit can be sent to the second resource management platform through the virtual network interface corresponding to the target virtual node. In response to this request, the second resource management platform creates and runs the target resource management unit. That is, the first resource management platform can deploy and run the resource management unit on the second resource management platform through the virtual network interface corresponding to the target virtual node, utilizing the resources of the second resource management platform. By using the virtual network interface corresponding to the target virtual node, resource pooling between different accounts within the same cloud and multi-cloud disaster recovery scheduling can be achieved, while reducing changes to the overall management architecture of the first and second resource management platforms. See Figure 2 , Figure 2 A flowchart of a data processing method applied to a first resource management platform according to an embodiment of this specification is shown, which specifically includes the following steps.

[0031] Step 202: In response to the resource user's initial creation request for the resource management unit, create an initial resource management unit and determine the target virtual node based on the resource configuration information of the initial resource management unit.

[0032] In this context, resource users can be individual users, enterprise users, or other types of entities. Resource users can use the resources of the first resource management platform. The first resource management platform can be understood as Kubernetes (or simply K8s). The initial resource management unit can be understood as a pod to be created (at this point, the pod has not actually been created; it can be regarded as a specification containing the resource configuration information of the pod to be created, defining the attributes and behaviors of the pod. The pod is only truly created and running after a series of operations such as pulling the image and starting the container). A pod is the basic unit of deployment and management in a Kubernetes cluster. It is a collection of one or more containers, usually used to encapsulate a group of closely related service processes.

[0033] Resource configuration information includes, but is not limited to, the amount of resources required by the pod (CPU, memory, etc.), the container to be run and its image, the container configuration, network settings, and storage volumes (persistent storage requirements).

[0034] A node can be understood as a worker node in the first resource management platform, responsible for providing the runtime environment required to run a pod. A virtual node can be understood as a node in the first resource management platform that is associated with the second resource management platform. Specifically, a virtual node is obtained by configuring a virtual network interface for the node, thus establishing a network connection between the first and second resource management platforms. A target virtual node can be understood as the virtual node corresponding to the initial resource management unit; that is, the initial resource management unit will be scheduled to this target virtual node.

[0035] The second resource management platform can be understood as another Kubernetes cluster that is independent of the first resource management platform. It is isolated from the first resource management platform. The second resource management platform can be a Kubernetes cluster under a different account in the same cloud service provider environment as the first resource management platform (cross-account), or the second resource management platform can be in the same cloud service provider environment as the first resource management platform (cross-cloud).

[0036] Specifically, when Kubernetes receives an initial pod creation request sent by a resource user through a client, it creates the pod, obtains the resource configuration information corresponding to the pod, and determines the target virtual node corresponding to the pod based on the pod's resource configuration information.

[0037] In one or more embodiments of this specification, the first resource management platform includes a control unit, which serves as the entry point for control of the first resource management platform. This control unit exposes the application programming interface (API) of the first resource management platform to clients and receives and processes requests from clients. Specific implementation methods are described below: The step of creating an initial resource management unit in response to an initial creation request from a resource user includes: The control unit receives the initial creation request for the resource management unit from the resource user, obtains the resource configuration information of the resource management unit, and creates the initial resource management unit.

[0038] The management unit can be understood as the K8s API Server (Application Programming Interface Server), which provides the API interfaces required for cluster management, including the creation and management of resources such as pods and services.

[0039] Specifically, when a resource user sends an initial creation request for a resource management unit (such as a pod) to the Kubernetes cluster, the request is sent to the Kubernetes API Server. The API Server retrieves the resource configuration information of the resource management unit carried in the request and performs a series of actions based on it, including verifying the request's validity, updating the status in etcd, and notifying the scheduler to schedule the pod. Once the scheduler finds a suitable node, it creates the pod on that node using a Kubelet (a proxy component on the node). The data processing method provided in the embodiments of this specification can receive initial creation requests sent by resource users to the resource management unit through the control unit, thereby efficiently realizing the interaction between the first resource management platform and the resource users, and accurately processing the initial creation requests of the resource users.

[0040] In one or more embodiments of this specification, when the scheduler schedules the initial resource management unit, it can reasonably schedule the initial resource management unit based on the resource configuration information of the initial resource management unit, and determine the target virtual node corresponding to the initial resource management unit. Specific implementation methods are described below: The resource configuration information includes resource space occupancy information or affinity information; determining the target virtual node based on the resource configuration information of the initial resource management unit includes: If, based on the resource space occupancy information of the initial resource management unit, it is determined that the first resource management platform does not meet the conditions for running the initial resource management unit, the scheduler is used to determine the target virtual node; or The target virtual node is determined using the scheduler based on the affinity information of the initial resource management unit.

[0041] Among them, the resource space occupancy information can be understood as the amount of resources required for the operation of the initial resource management unit in the above embodiments, such as the amount of CPU and memory resources occupied; the affinity information can be understood as the affinity and anti-affinity attribute setting information when pod is scheduled. By setting the affinity information of pod, it is possible to determine whether the pod should be scheduled to a node with a specific label, or to avoid scheduling to certain nodes.

[0042] The scheduler is responsible for scheduling the initial resource management unit to the appropriate node. It can determine the appropriate node based on the pod's resource requirements and affinity information.

[0043] Specifically, after obtaining the resource configuration information of the initial resource management unit, the resource space occupancy information of the initial resource management unit can be determined, that is, the resource requirements of the initial resource management unit. If the available resources in the first resource management platform are less than the resource requirements of the initial resource management unit, it can be determined that the first resource management platform does not meet the conditions for running the initial resource management unit. In other words, the initial resource management unit can run on the first resource management platform. At this time, the scheduler is used to determine the target virtual node from multiple nodes, thereby scheduling the initial resource management unit to the target virtual node.

[0044] Alternatively, if the initial resource management unit is determined to be inclined to avoid being scheduled to a node running a specific project on the first resource management platform based on the affinity information, the scheduler can determine appropriate scheduling rules based on the affinity information, identify the target virtual node from multiple nodes, and thus, in the case of scheduling the initial resource management unit to the target virtual node, the initial resource management unit can be actually deployed on the second resource management platform based on the target virtual node, away from the node running a specific project on the first resource management platform.

[0045] Of course, in practical applications, the scheduler can determine the scheduling node corresponding to the initial resource management unit according to the load balancing rules (considering the resource usage of multiple nodes). If the scheduling node is a virtual node, the virtual network interface of the target virtual node is used to send a target creation request for the resource management unit to the second resource management platform; if the scheduling node is not a virtual node, the initial resource management unit is started and run directly on the scheduling node.

[0046] The data processing method provided in the embodiments of this specification can determine the resource space occupancy information or affinity information in the resource configuration information through the resource configuration information of the initial resource management unit. Based on the resource space occupancy information or affinity information, the scheduler can reasonably determine the target virtual node corresponding to the initial resource management unit, thereby realizing the reasonable scheduling of the initial resource management unit.

[0047] Step 204: Using the virtual network interface of the target virtual node, send a target creation request for the resource management unit to the second resource management platform, so that the second resource management platform responds to the target creation request, creates and runs the target resource management unit. The first resource management platform and the second resource management platform are resource management platforms corresponding to different resource accounts of the resource user. The virtual network interface is used to provide network connection between the first resource management platform and the second resource management platform. The target creation request carries the resource configuration information.

[0048] In the above embodiments, the second resource management platform can be understood as a separate Kubernetes cluster independent of the first resource management platform. It is isolated from the first resource management platform. The second resource management platform can be a Kubernetes cluster located in the same cloud service provider environment as the first resource management platform but under a different account (cross-account), or the second resource management platform and the first resource management platform can be located in different cloud service provider environments (cross-cloud). Therefore, the meaning of "the first resource management platform and the second resource management platform belong to different resource accounts of the resource user" is that the first resource management platform and the second resource management platform belong to different resource accounts of the resource user (different accounts within the same cloud or accounts under different clouds).

[0049] A virtual network interface can be understood as an ENI (Elastic Network Interface), which allows network communication between different Virtual Private Clouds (VPCs). A VPC provides an isolated network environment, enabling Kubernetes clusters to run in a secure and private network.

[0050] Specifically, through the virtual network interface of the target virtual node, a target creation request for a resource management unit can be sent to the second resource management platform of different VPCs. The target creation request carries the resource configuration information of the resource management unit. Upon receiving the target creation request, the second resource management platform creates the target resource management unit, determines the target node in the second resource management platform, and uses the scheduler to schedule the target resource management unit to the target node, where the target resource management unit runs.

[0051] In one or more embodiments of this specification, to enable the target virtual node to send requests to the second resource management platform through a virtual network interface, thereby achieving network communication between the first and second resource management platforms, a virtual network interface is configured for the target virtual node. Specific implementation methods are described below: Before creating the initial resource management unit in response to the resource user's initial creation request, the method further includes: In response to the node configuration request from the resource user for the target virtual node, the virtual network interface is configured for the target virtual node based on the resource account information of the resource user on the second resource management platform carried in the node configuration request. The virtual network interface is used to provide network connectivity between the first resource management platform and the second resource management platform.

[0052] Among them, the node configuration request is used to configure the virtual network interface for the node; the resource account information of the second resource management platform can be understood as the account details of the resource user on the second resource management platform. The resource account information includes, but is not limited to, username, password, application interface key and other information, which are used to verify identity and permissions.

[0053] Specifically, since the virtual network interface is used to enable network communication between different resource management platforms, it is necessary to obtain the resource account information of the resource user on the second resource management platform. For example, the first resource management platform is Kubernetes on cloud service provider A, and the second resource management platform is Kubernetes on cloud service provider B. Some services are deployed on Kubernetes on cloud service provider A, and some services are deployed on Kubernetes on cloud service provider B. If it is desired to interconnect the target virtual node of the first resource management platform with the second resource management platform so that the resources in the second resource management platform can be utilized, a node configuration request for the target virtual node can be initiated to the first resource management platform. The node configuration request contains the resource account information corresponding to the second resource management platform.

[0054] The first resource management platform can use the resource account information in the request to configure a virtual network interface on the target virtual node, thereby enabling the virtual network interface to establish a secure and stable network connection with the second resource management platform. In this way, even if the first and second resource management platforms are not physically directly connected, the virtual network interface of the target virtual node in the first resource management platform can be used to communicate smoothly with the services on the second resource management platform, realizing cross-cloud resource collaboration.

[0055] Of course, when the first resource management platform and the second resource management platform are resource management platforms under different accounts within the same cloud, the above-mentioned node configuration for the target virtual node can be used to successfully communicate with the services on the second resource management platform through the virtual network interface of the target virtual node in the first resource management platform, thus realizing cross-account resource collaboration.

[0056] The data processing method provided in the embodiments of this specification enables the target virtual node to achieve network communication between the first resource management platform and the second resource management platform through the virtual network interface by configuring a virtual network interface for the target virtual node, thereby realizing cross-cloud or cross-account resource collaboration.

[0057] In one or more embodiments of this specification, the virtual network interface includes a listening interface and a request interface; the listening interface is used to obtain the resource configuration information of the initial resource management unit, and the request interface is used to send a target creation request to the second resource management platform. Specific implementation methods are as follows: Using the virtual network interface of the target virtual node, a target creation request for the resource management unit is sent to the second resource management platform, including: The initial resource management unit is scheduled to the target virtual node using a scheduler. The resource configuration information of the initial resource management unit is obtained by using the listening interface of the target virtual node; Using the request interface of the target virtual node, a target creation request for the resource management unit is sent to the second resource management platform according to the resource configuration information.

[0058] Specifically, the step of using the virtual network interface of the target virtual node to send a target creation request for the resource management unit to the second resource management platform includes: The node information of the target virtual node is sent to the control unit using a scheduler; Using the control unit, an association is established between the initial resource management unit and the target virtual node, and the initial resource management unit is scheduled to the target virtual node; The target virtual node accesses the management and control unit through its listening interface, and listens to and obtains the resource configuration information of the initial resource management unit from the management and control unit. Using the request interface of the target virtual node, a target creation request for the resource management unit is sent to the second resource management platform according to the resource configuration information.

[0059] Among them, the virtual network interface can be understood as a virtual network card, the listening interface can be understood as the first virtual network card (e.g., eth0, with access limited to the virtual private cloud corresponding to the first resource management platform) used to access the virtual private cloud corresponding to the first resource management platform, and the request interface can be understood as the second virtual network card (e.g., eth1, with access limited to the virtual private cloud corresponding to the second resource management platform) used to interact with the virtual private cloud corresponding to the second resource management platform.

[0060] Specifically, when the scheduler selects a target virtual node, the scheduler notifies the management unit of the scheduling decision, which includes the node information of the target virtual node. The management unit then binds the initial resource management unit to the selected target virtual node. The target virtual node's eth0 can access the management unit of the first resource management platform in VPC-A (the VPC corresponding to the first resource management platform), thereby listening to the creation of a new initial resource management unit on the target virtual node and obtaining the resource configuration information of the initial resource management unit; through the target virtual node's eth1, based on the obtained resource configuration information, it sends a target creation request for the resource management unit to the second resource management platform in VPC-B (the VPC corresponding to the second resource management platform) to create a real target resource management unit in the second resource management platform.

[0061] The data processing method provided in the embodiments of this specification can connect the networks between two different resource accounts through listening interfaces and request interfaces, enabling the first resource management platform to use resources from other accounts or other cloud service providers, thereby achieving a unified resource pool and improving resource utilization.

[0062] The data processing method provided in the embodiments of this specification can achieve cross-account resource integration or multi-cloud resource integration while keeping the management and control architecture unchanged, thereby achieving the desired effect of unified resource pool and multi-cloud disaster recovery.

[0063] See Figure 3 , Figure 3 A flowchart of a data processing method applied to a second resource management platform according to an embodiment of this specification is shown, which specifically includes the following steps.

[0064] Step 302: In response to the target creation request sent by the first resource management platform for the resource management unit, create the target resource management unit according to the resource configuration information carried in the target creation request.

[0065] The target creation request is sent by the first resource management platform using the virtual network interface of the target virtual node when the first resource management platform creates an initial resource management unit in response to the initial creation request of the resource user for the resource management unit, and determines the target virtual node based on the resource configuration information of the initial resource management unit. The first resource management platform and the second resource management platform are resource management platforms corresponding to different resource accounts of the resource user.

[0066] The target resource management unit can also be understood as a pod to be created, which is created on the second resource management platform.

[0067] Specifically, when the first resource management platform sends a target creation request to the second resource management platform through the virtual network interface of the target virtual node, the second resource management platform creates a target resource management unit using the resource configuration information carried in the target creation request.

[0068] In one or more embodiments of this specification, the second resource management platform is a hybrid cloud resource management platform. In this case, a pre-allocation operation needs to be performed on the second resource management platform to determine the pre-allocated node as the target node, so that when scheduling the target resource management unit, it is scheduled to the target node. Specific implementation methods are as follows: Before creating the target resource management unit in response to the target creation request sent by the first resource management platform, based on the resource configuration information carried in the target creation request, the process further includes: The resource scheduler monitors the resource specifications of the pre-allocated resources in the first resource management platform, wherein the pre-allocated resources are pre-allocated resources created by the first resource management platform according to the resource configuration information of the initial resource management unit and corresponding to the initial resource management unit; The resource scheduler performs a pre-occupancy operation on the target node of the hybrid cloud resource management platform, updates the pre-occupancy status of the pre-occupancy resource to a pre-occupancy success status, and returns a pre-occupancy success message to the first resource management platform. This enables the first resource management platform to send a target creation request to the second resource management platform based on the pre-occupancy success message. The pre-occupancy success message includes the pre-occupancy success status update information and the node information of the target node.

[0069] The hybrid cloud resource management platform can be understood as a second resource management platform that not only provides resources for the first resource management platform but also has its own running projects, occupying a portion of the resources. Reserved resources can be understood as reserved CRs (Custom Resources), which are resources pre-created in the first resource management platform. These resources are temporarily reserved, awaiting further operations. Reserved CRs allow for preparatory work before actual resource use, such as reserving resources and setting configuration parameters.

[0070] Resource specifications can be understood as the specific configuration information of the reserved resources, such as CPU, memory, and storage information, including the size of the reserved resources. The resource scheduler can be understood as the Lafile scheduler, responsible for monitoring and managing the allocation and scheduling of resources. The target node can be understood as the node that actually performs the pre-reservation operation; that is, the reserved resources occupy the resources in the target node. The pre-reservation operation can be understood as marking the resources on the target node as successfully reserved, ensuring that these resources will not be used by other tasks. The successful pre-reservation status can be understood as the resource status being updated to successful pre-reservation after the pre-reservation operation is completed, indicating that the resource has been successfully reserved.

[0071] Specifically, since the second resource management platform is a hybrid cloud resource management platform, when the resources in the second resource management platform are used by the first resource management platform, conflicts may arise between the resources used by the project itself. When the resources in the second resource management platform are scheduled using the Lafile scheduler, the Lafile scheduler needs to be able to perceive the size of the resources that the first resource management platform will use.

[0072] In practical applications, the first resource management platform schedules the initial resource management unit to the target virtual node upon request. The target virtual node creates a pre-occupied CR corresponding to the initial resource management unit based on the resources required by the initial resource management unit. There is a one-to-one correspondence between the initial resource management unit and the pre-occupied CR, and the resource size of the pre-occupied CR is the resource size required by the initial resource management unit.

[0073] The Lafile scheduler can monitor the size of reserved resource CRs and perform resource reservation operations in the second resource management platform. The reserved node is the target node (e.g., the target node is Node-X). The status of the reserved CR is updated, for example, the status is updated to reserved successfully. A reserved successful message is returned to the first resource management platform. This reserved successful message can contain not only the reserved successful status update information but also the node information of the target node. That is, the target node can be Node-X and put into the reserved successful message so that the first resource management platform can determine that the resource reservation is successful based on the reserved successful message and send a target creation request to the second resource management platform.

[0074] The data processing method provided in the embodiments of this specification creates corresponding pre-allocated resources on the first resource management platform based on the resource configuration information of the initial resource management unit. The resource scheduler of the second resource management platform can listen to the pre-allocated resources and perform the pre-allocation operation. When the resource scheduler can listen to the pre-allocated resources and reserve resources for the first resource management platform, resources can be scheduled in a unified manner, thereby improving the effective utilization of resources.

[0075] Step 304: Determine the target node corresponding to the target resource management unit, and run the target resource management unit on the target node.

[0076] When the second resource management platform is not a hybrid cloud resource management platform, the resources in the second resource management platform are used by the first resource management platform. In this case, the target node corresponding to the target resource management unit can be randomly selected by the scheduler in the second resource management platform or selected based on the load balancing mechanism. However, when the second resource management platform is a hybrid cloud resource management platform, the target node corresponding to the target resource management unit is the node that performs the pre-occupancy operation based on the pre-occupancy resources in the above embodiment.

[0077] When the target resource management unit is scheduled to the target node, the target resource management unit runs on the target node and uses the resources of the target node.

[0078] In one or more embodiments of this specification, when the first resource management platform sends a target creation request to the second resource management platform based on the pre-occupancy success message, the target creation request may carry node information of the target node. The second resource management platform can determine the target node corresponding to the target resource management unit based on the node information in the target creation request. Specific implementation methods are as follows: Determining the target node corresponding to the target resource management unit and running the target resource management unit on the target node includes: The target node corresponding to the target resource management unit is determined based on the target creation request, and the target resource management unit is run on the target node.

[0079] The data processing method provided in the embodiments of this specification determines the target node to perform the pre-occupation operation through the node information of the target creation request, so as to correctly schedule the target resource management unit to the target node that has reserved resources for the target resource management unit, thereby realizing the reasonable scheduling of the target resource management unit.

[0080] In one or more embodiments of this specification, running the target resource management unit requires pulling an image, creating and starting a container. To pull the correct image, the initial image repository address corresponding to the first resource management platform is converted to the target image repository address corresponding to the second resource management platform. Specific implementation methods are as follows: The step of determining the target node corresponding to the target resource management unit and running the target resource management unit on the target node includes: The target node corresponding to the target resource management unit is determined, and the target scheduler of the second resource management platform is used to schedule the target resource management unit to the target node; On the target node, based on the resource configuration information of the target resource management unit, the initial image repository address corresponding to the first resource management platform is determined, and the initial image repository address is converted into the target image repository address corresponding to the second resource management platform. Pull the target image corresponding to the target resource management unit from the target image repository address, create and start the target container corresponding to the target resource management unit based on the target image, and run the target resource management unit.

[0081] In practical applications, since the resource user sends the initial creation request to the first resource management platform, the resource configuration information is related to the first resource management platform. For example, the image repository address in the resource configuration information is the initial image repository address corresponding to the first resource management platform. Therefore, in order to correctly run the target resource management unit on the second resource management platform, VK (Virtual Kubelet) provides the ability to transform the image repository, converting the initial image repository address into a target image repository address that can be accessed by the cluster where the instance pod (target resource management unit) is located, thereby achieving image synchronization.

[0082] Pull the target image corresponding to the target resource management unit from the target image repository address, and then create and start the correct target container based on the target image to run the target resource management unit.

[0083] In practical applications, the target storage resource to be mounted to the target resource management unit (the storage resources within the target storage resource that the container can access and use at runtime) also needs to be mounted to the target resource management unit. Therefore, it is necessary to add comments to the persistent storage resource request to create the target storage resource on the second resource management platform where the target resource management unit resides, avoiding the creation of the target storage resource on the first resource management platform. The specific implementation method is as follows: The step of running the target resource management unit on the target node includes: In response to a storage resource request carrying target data, a target storage resource is created on the second resource management platform, the target storage resource is mounted to the target resource management unit, and the target resource management unit is run on the target node.

[0084] A storage resource request can be understood as a pcv (Persistent Volume Claim), used to request and manage persistent storage resources. The target storage resource can be understood as a persistent storage resource, such as a storage volume or cloud disk.

[0085] By adding annotations (i.e. target data) in PVC, the creation of target storage resources on both the first and second resource management platforms is avoided. The target storage resources are fixed to the second resource management platform where the target resource management unit is located. Furthermore, by mounting the target storage resources to the target resource management unit, containers in the target resource management unit can access and use the storage resources in the target storage resources, ensuring the normal operation of the target resource management unit.

[0086] The data processing method provided in the embodiments of this specification can correctly mount the target storage resource to the target resource management unit by carrying a storage resource request carrying the target data, and ensure that the data still exists after the target resource management unit is restarted or rescheduled, thus ensuring that the data is not lost.

[0087] In one or more embodiments of this specification, after running the target resource management unit on the target node, applications or projects can be deployed on the target resource management unit. Since the target resource management unit can access other services, and if the services accessed by the target resource management unit are deployed on the first resource management platform, it is necessary to establish a container network between the first resource management platform and the second resource management platform. Specific implementation methods are described below: After running the target resource management unit on the target node, the method further includes: The target resource management unit receives service access requests for the target service through its target access interface, wherein the service access requests carry attribute information of the target service. If it is determined that the target service is deployed on the first resource management platform based on the attribute information of the target service, a domain name resolution request for the target service is sent to the first resource management platform based on the domain name information in the attribute information. The system receives the resolution result corresponding to the domain name resolution request returned by the first resource management platform, and accesses the target service through the management and control interaction interface based on the resolution result.

[0088] The target access interface is used to access the user's virtual private cloud and can be understood as a network interface card (NIC). The user accesses the target resource management unit through this interface. The target service's attribute information may include its domain name. The management interaction interface is used to interact with the management unit in the first resource management platform.

[0089] Specifically, users can initiate a service access request for a target service to the target resource management unit through the target access interface. If the target service is deployed on the first resource management platform, the user can send a domain name resolution request for the target service to the first resource management platform. The first resource management platform can parse the domain name information of the target service in the domain name resolution request and obtain the resolution result (the resolution result includes the IP address, port and other information of the target service). The user can then access the target service through the IP address of the target service based on the management and control interaction interface.

[0090] In one or more embodiments of this specification, a Load Balance (LB) type service is added to the CoreDNS server (the default DNS server of Kubernetes, responsible for resolving service names and pod names, making communication between services more convenient and efficient) in the first resource management platform. This service is a domain name resolution forwarding service used to forward domain name resolution requests to the CoreDNS server.

[0091] The step of sending a domain name resolution request for the target service to the first resource management platform based on the domain name information in the attribute information includes: Based on the domain name information in the attribute information, determine the domain name resolution request and the target transport protocol for sending the domain name resolution request; According to the target transmission protocol, the domain name resolution request is sent to the domain name resolution forwarding service in the first resource management platform that corresponds to the target transmission protocol, so as to use the domain name resolution forwarding service to send the domain name resolution request to the domain name resolution server of the first resource management platform and obtain the resolution result corresponding to the domain name resolution request.

[0092] In practical applications, when creating an LB-type service for the CoreDNS server in the first resource management platform, since the CoreDNS server supports both TCP and UDP protocols, and the LB-type service only supports one protocol, it is necessary to create two services that support TCP and UDP protocols respectively.

[0093] Determine the target transport protocol (TCP or UDP) for sending the domain name resolution request, and send the domain name resolution request to the domain name resolution forwarding service corresponding to the target transport protocol according to the target transport protocol. The domain name resolution forwarding service will then send the domain name resolution request to the domain name resolution server (CoreDNS server) of the first resource management platform to obtain the resolution result corresponding to the domain name resolution request.

[0094] The data processing method provided in the embodiments of this specification creates a domain name resolution forwarding service of type LB that supports different transmission protocols for the CoreDNS server in the first resource management platform. This allows domain name resolution requests sent through different transmission protocols to be forwarded to the domain name resolution server of the first resource management platform, and the resolution efficiency can also be improved through the load balancing mechanism.

[0095] See Figure 4 , Figure 4 A schematic flowchart of a data processing method applied to a data processing system, according to an embodiment of this specification, is shown.

[0096] Specifically, taking the newly created resource scenario of applying the data processing method to the resources of the second resource management platform for use by the first resource management platform as an example, the data processing method is explained in detail through the configuration stage, creation stage, and application stage.

[0097] Configuration phase: The virtual nodes in cluster A are at the availability zone level, meaning each virtual node corresponds to a resource in a specific availability zone of account B; the clusters in account B are at the availability zone level, meaning each cluster includes a database node in a specific availability zone; each cluster in account B corresponds one-to-one with each virtual node in account A. The cluster (First Resource Management Platform) corresponding to account A contains nodes and virtual nodes. The nodes are used to run and deploy the project of account A itself, while the virtual nodes are used to connect with other accounts or the cloud.

[0098] To enable network communication between VPC-A (the virtual private cloud corresponding to account A) and VPC-B (the virtual private cloud corresponding to account B) in the cluster, two network interface cards (NICs) are mounted on the virtual node: One eth0 in VPC-A accesses the management unit (kube-apiserver, i.e., APIServer in the diagram) in VPC-A to monitor the distributed Pod resources; the other eth1 in VPC-B is used to create real instance Pods for the cluster in VPC-B. For user instance Pods in a VPC-B cluster, three network interface cards (NICs) can be mounted: One eth0 port for VPC-A (optional, can be left unconnected) is used to interact with the management unit of VPC-A; one eth1 port for the user VPC is used for access to the user VPC; and one virtual network interface ansm0 is mainly used to establish a single link from the host to the pod, making it convenient for operations personnel to perform operations and maintenance (optional, can be left unconnected), while denying access links from the pod to the host.

[0099] The DNS of the cluster pods in VPC-B is pointed to the address in VPC-A (this is achieved by configuring dnsConfig in the pod, which allows users to specify the DNS server for the pod). This forwards the DNS query requests of the instance pods in VPC-B to the CoreDNS server in VPC-A for resolution. In order to achieve cross-VPC DNS query request forwarding, two load balancer (LB) type services are created for CoreDNS in the VPC-A cluster. One service is used for the TCP protocol and the other is used for the UDP protocol, so as to meet the requirement that CoreDNS supports two protocols at the same time.

[0100] Creation phase: The user sends an initial creation request to cluster A under account A to create a Pod. The kube-apiserver of cluster A receives the initial creation request and creates the pod according to the initial creation request (i.e., the initial resource management unit in the above embodiment. At this time, the pod is not actually created. The pod is only actually created after a series of operations such as pulling the image and starting the container). The scheduler selects the node to run the pod.

[0101] When the scheduler selects a virtual node, the scheduler notifies the kube-apiserver of the scheduling decision. The kube-apiserver binds the pod to the selected virtual node. The eth0 port of the virtual node can access the kube-apiserver of cluster A in VPC-A, thereby listening to the creation of a new pod on the virtual node and obtaining the pod's resource configuration information (resources required by the pod, the container to run, the container configuration, and network settings).

[0102] Using eth1 mounted on the virtual node, a real instance pod is created in cluster B (i.e., the second resource management platform in the above embodiment, which corresponds to the virtual node) in account B according to the pod's resource configuration information; in cluster B, the scheduler of cluster B is used to schedule the pod to a specific node.

[0103] In practical applications, since the user sends the pod creation request to account A, the pod's resource configuration information is related to cluster A of account A. For example, when creating a pod or pulling the image corresponding to the container in the pod, it is pulled from the image repository corresponding to cluster A. Therefore, VK (Virtual Kubelet) provides the ability to convert image repository addresses into image repository addresses that can be accessed by the cluster where the instance pod is located, thereby achieving image synchronization.

[0104] For example, when creating a pod instance in cluster B and pulling an image, the image repository address 1 corresponding to cluster A is converted to an image repository address 2 that cluster B can access. The image in image repository address 1 is converted to an image in image repository address 2. The container is created and started by pulling the image from image repository address 2.

[0105] The cloud disk that will be mounted to the pod (the storage resources of the cloud disk that the container can access and use at runtime) also needs to be mounted to the instance pod. Therefore, the cloud disk needs to be created in cluster B where the instance pod is located by adding comments in the persistent storage request, so as to avoid creating the cloud disk in cluster A.

[0106] Application phase: When an instance pod in cluster B wants to access a target service in cluster A, the user initiates a service access request for the target service through the instance pod's eth1. Based on the service access request, the instance pod sends a DNS query request for the target service. This DNS query request is then sent to the corresponding LB-type domain name resolution forwarding service in cluster A according to the appropriate transport protocol. The domain name resolution forwarding service forwards the DNS query request to the CoreDNS server in cluster A for resolution, obtaining the resolution result (i.e., the IP address corresponding to the domain name). Based on the resolution result, the instance pod interacts with the kube-apiserver in cluster A via eth0 to achieve access to the target service.

[0107] See Figure 5 , Figure 5 The diagram shows a flowchart illustrating another data processing method applied to a data processing system, as provided in one embodiment of this specification.

[0108] This specification provides an example of a data processing method applied to a scenario where the second resource management platform is a hybrid cloud resource management platform. The data processing method is described in detail through the configuration phase, creation phase, and application phase.

[0109] The specific implementation of the configuration and application phases is the same as in the above embodiments, and will not be repeated here.

[0110] Creation phase: A user sends a Pod creation request through account A. The kube-apiserver of cluster A receives the initial creation request, creates the Pod, and the scheduler A of cluster A schedules the Pod to a virtual node. The virtual node creates a pre-allocated CR (custom resource) for the Pod based on the resources required by the Pod. There is a one-to-one correspondence between the Pod and the pre-allocated CR, and the resource size of the pre-allocated CR is the resource size required by the Pod.

[0111] The Lafile scheduler in VPC-B can monitor the resource size of the reserved CR and perform the reserved resource operation in the VPC-B cluster B, reserved node Node-X, and update the status of the reserved CR (for example, update the status to reserved successfully and the reserved node to Node-X). When a virtual node creates an instance pod in cluster B within VPC-B, the scheduler of cluster B will schedule the pod to node Node-X based on the previous pre-allocation results.

[0112] The data processing method provided in the embodiments of this specification, through the VK (VirtualKubelet) solution, can utilize resources from other accounts or other clouds without changing the management framework. By simulating different resource accounts as corresponding user accounts and combining the capabilities of multiple network cards, the network is made transparent to the product, thus avoiding the need to explicitly connect the networks of two VPCs, which would significantly increase costs. By adding a load balancer type service to CoreDNS and configuring dnsConfig in the pod, container networks of different accounts or cloud service provider Kubernetes clusters can be connected.

[0113] Corresponding to the above method embodiments, this specification also provides data processing apparatus embodiments. Figure 6 A schematic diagram of the structure of a data processing apparatus according to one embodiment of this specification is shown. Figure 6 As shown, the device is applied to a first resource management platform and includes: The response module 602 is configured to respond to an initial creation request from a resource user for a resource management unit, create an initial resource management unit, and determine a target virtual node based on the resource configuration information of the initial resource management unit. The sending module 604 is configured to use the virtual network interface of the target virtual node to send a target creation request for the resource management unit to the second resource management platform, so that the second resource management platform responds to the target creation request, creates and runs the target resource management unit, wherein the first resource management platform and the second resource management platform are resource management platforms corresponding to different resource accounts of the resource user, the virtual network interface is used to provide network connection between the first resource management platform and the second resource management platform, and the target creation request carries the resource configuration information.

[0114] Optionally, the response module 602 is further configured to: If, based on the resource space occupancy information of the initial resource management unit, it is determined that the first resource management platform does not meet the conditions for running the initial resource management unit, the scheduler is used to determine the target virtual node; or The target virtual node is determined using the scheduler based on the affinity information of the initial resource management unit.

[0115] Optionally, the sending module 604 is further configured to: The initial resource management unit is scheduled to the target virtual node using a scheduler. The resource configuration information of the initial resource management unit is obtained by using the listening interface of the target virtual node; Using the request interface of the target virtual node, a target creation request for the resource management unit is sent to the second resource management platform according to the resource configuration information.

[0116] Optionally, the response module 602 is further configured to: The control unit receives the initial creation request for the resource management unit from the resource user, obtains the resource configuration information of the resource management unit, and creates the initial resource management unit.

[0117] Optionally, the sending module 604 is further configured to: The node information of the target virtual node is sent to the control unit using a scheduler; Using the control unit, an association is established between the initial resource management unit and the target virtual node, and the initial resource management unit is scheduled to the target virtual node; The monitoring interface of the target virtual node is used to access the management and control unit, and the resource configuration information of the initial resource management unit is monitored and obtained from the management and control unit. Using the request interface of the target virtual node, a target creation request for the resource management unit is sent to the second resource management platform based on the resource configuration information.

[0118] The apparatus further includes: a configuration module configured to, in response to a node configuration request from the resource user for a target virtual node, configure the virtual network interface for the target virtual node based on the resource account information of the resource user on the second resource management platform carried in the node configuration request, wherein the virtual network interface is used to provide network connectivity between the first resource management platform and the second resource management platform.

[0119] The above is an illustrative scheme of a data processing apparatus according to this embodiment. It should be noted that the technical solution of this data processing apparatus and the technical solution of the data processing method described above belong to the same concept. For details not described in detail in the technical solution of the data processing apparatus, please refer to the description of the technical solution of the data processing method described above.

[0120] Corresponding to the above method embodiments, this specification also provides another data processing apparatus embodiment. Figure 7 A schematic diagram of another data processing apparatus provided in one embodiment of this specification is shown. Figure 7 As shown, the device is applied to a second resource management platform and includes: The response module 702 is configured to respond to a target creation request for a resource management unit sent by the first resource management platform, and to create a target resource management unit based on the resource configuration information carried in the target creation request. The target creation request is sent by the first resource management platform using the virtual network interface of the target virtual node when the first resource management platform creates an initial resource management unit in response to an initial creation request for a resource management unit from the resource user and determines the target virtual node based on the resource configuration information of the initial resource management unit. The first resource management platform and the second resource management platform are resource management platforms corresponding to different resource accounts of the resource user. The determination module 704 is configured to determine the target node corresponding to the target resource management unit and run the target resource management unit on the target node.

[0121] The device further includes: The pre-allocation module is configured to use a resource scheduler to monitor the resource specifications of pre-allocated resources in the first resource management platform. The pre-allocated resources are pre-allocated resources created by the first resource management platform based on the resource configuration information of the initial resource management unit and corresponding to that initial resource management unit. The module uses the resource scheduler to perform a pre-allocation operation on the target node of the hybrid cloud resource management platform, updates the pre-allocation status of the pre-allocated resources to a pre-allocation success status, and returns a pre-allocation success message to the first resource management platform. This allows the first resource management platform to send a target creation request to the second resource management platform based on the pre-allocation success message. The pre-allocation success message includes the pre-allocation success status update information and the node information of the target node.

[0122] Optionally, the determining module 704 is further configured to: The target node corresponding to the target resource management unit is determined based on the target creation request, and the target resource management unit is run on the target node.

[0123] Optionally, the determining module 704 is further configured to: The target node corresponding to the target resource management unit is determined, and the target scheduler of the second resource management platform is used to schedule the target resource management unit to the target node; On the target node, based on the resource configuration information of the target resource management unit, the initial image repository address corresponding to the first resource management platform is determined, and the initial image repository address is converted into the target image repository address corresponding to the second resource management platform. Pull the target image corresponding to the target resource management unit from the target image repository address, create and start the target container corresponding to the target resource management unit based on the target image, and run the target resource management unit.

[0124] Optionally, the determining module 704 is further configured to: In response to a storage resource request carrying target data, a target storage resource is created on the second resource management platform, the target storage resource is mounted to the target resource management unit, and the target resource management unit is run on the target node.

[0125] The apparatus further includes: an access module configured to receive a service access request for a target service through a target access interface of the target resource management unit, wherein the service access request carries attribute information of the target service; if it is determined that the target service is deployed on a first resource management platform based on the attribute information of the target service, the module sends a domain name resolution request for the target service to the first resource management platform based on the domain name information in the attribute information; receives a resolution result corresponding to the domain name resolution request returned by the first resource management platform, and accesses the target service through a control interaction interface based on the resolution result.

[0126] Optionally, the access module is further configured to: Based on the domain name information in the attribute information, determine the domain name resolution request and the target transport protocol for sending the domain name resolution request; According to the target transmission protocol, the domain name resolution request is sent to the domain name resolution forwarding service in the first resource management platform that corresponds to the target transmission protocol, so as to use the domain name resolution forwarding service to send the domain name resolution request to the domain name resolution server of the first resource management platform and obtain the resolution result corresponding to the domain name resolution request.

[0127] The above is an illustrative scheme of a data processing apparatus according to this embodiment. It should be noted that the technical solution of this data processing apparatus and the technical solution of the data processing method described above belong to the same concept. For details not described in detail in the technical solution of the data processing apparatus, please refer to the description of the technical solution of the data processing method described above.

[0128] Corresponding to the above method embodiments, this specification also provides a data processing system embodiment. Figure 8 A schematic diagram of the structure of a data processing system according to one embodiment of this specification is shown. Figure 8 As shown, the system includes a first resource management platform 802 and a second resource management platform 804, wherein, The first resource management platform 802 is used to respond to the initial creation request of the resource user for the resource management unit, create an initial resource management unit, determine the target virtual node according to the resource configuration information of the initial resource management unit, and send a target creation request for the resource management unit to the second resource management platform 804 using the virtual network interface of the target virtual node. The second resource management platform 804 is used to respond to the target creation request for the resource management unit sent by the first resource management platform 802, create the target resource management unit according to the resource configuration information carried in the target creation request, determine the target node corresponding to the target resource management unit, and run the target resource management unit on the target node.

[0129] This specification provides a data processing system in one embodiment. A first resource management platform creates an initial resource management unit in response to an initial creation request from a resource user. Based on the resource configuration information of the initial resource management unit, it determines a target virtual node. The virtual network interface corresponding to this target virtual node provides a network connection between the first and second resource management platforms (which belong to different resource accounts of the resource user). Therefore, a target creation request for the resource management unit can be sent to the second resource management platform through the virtual network interface corresponding to the target virtual node. The second resource management platform responds to this request by creating and running the target resource management unit. In other words, the first resource management platform can deploy and run the resource management unit on the second resource management platform through the virtual network interface corresponding to the target virtual node, utilizing the resources of the second resource management platform. By using the virtual network interface corresponding to the target virtual node, resource pooling between different accounts within the same cloud and multi-cloud disaster recovery scheduling are achieved, while reducing changes to the overall management architecture of the first and second resource management platforms. The above is an illustrative scheme of a data processing system according to this embodiment. It should be noted that the technical solution of this data processing system and the technical solution of the data processing method described above belong to the same concept. For details not described in detail in the technical solution of the data processing system, please refer to the description of the technical solution of the data processing method described above.

[0130] Figure 9 A structural block diagram of a computing device 900 according to one embodiment of this specification is shown. The components of the computing device 900 include, but are not limited to, a memory 910 and a processor 920. The processor 920 is connected to the memory 910 via a bus 930, and a database 950 is used to store data.

[0131] The computing device 900 also includes an access device 940, which enables the computing device 900 to communicate via one or more networks 960. Examples of these networks include Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or combinations of communication networks such as the Internet. The access device 940 may include one or more of any type of wired or wireless network interface (e.g., a network interface card (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Wi-MAX (Worldwide Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, or a Near Field Communication (NFC) interface.

[0132] In one embodiment of this specification, the aforementioned components of the computing device 900 and Figure 9 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 9 The block diagram of the computing device shown is for illustrative purposes only and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0133] The computing device 900 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or personal computers (PCs). The computing device 900 can also be a mobile or stationary server.

[0134] The processor 920 is used to execute the following computer program / instructions, which, when executed by the processor, implement the steps of the above-described data processing method.

[0135] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the computing device embodiments are basically similar to the data processing method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the data processing method embodiments.

[0136] An embodiment of this specification also provides a computer-readable storage medium storing a computer program / instructions that, when executed by a processor, implement the steps of the above-described data processing method.

[0137] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the computer-readable storage medium embodiments are basically similar to the data processing method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the data processing method embodiments.

[0138] An embodiment of this specification also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the above-described data processing method.

[0139] The above is an illustrative scheme of a computer program product according to this embodiment. It should be noted that the technical solution of this computer program product and the technical solution of the data processing method described above belong to the same concept. For details not described in detail in the technical solution of the computer program product, please refer to the description of the technical solution of the data processing method described above.

[0140] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0141] The computer instructions include computer program code, which may be in the form of source code, object code, executable file, or certain intermediate forms. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium may be appropriately added or removed according to the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media may not include electrical carrier signals and telecommunication signals.

[0142] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments in this specification are not limited to the described order of actions, because according to the embodiments in this specification, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the embodiments in this specification.

[0143] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0144] The preferred embodiments disclosed above are merely illustrative of this specification. The optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the embodiments described herein. These embodiments are selected and specifically described in this specification to better explain the principles and practical applications of the embodiments, thereby enabling those skilled in the art to better understand and utilize this specification. This specification is limited only by the claims and their full scope and equivalents.

Claims

1. A data processing method, applied to a first resource management platform, comprising: In response to the resource user's initial creation request for the resource management unit, an initial resource management unit is created, and the target virtual node is determined based on the resource configuration information of the initial resource management unit; Using the virtual network interface of the target virtual node, a target creation request for the resource management unit is sent to the second resource management platform, so that the second resource management platform responds to the target creation request, creates and runs the target resource management unit. The first resource management platform and the second resource management platform are resource management platforms corresponding to different resource accounts of the resource user. The virtual network interface is used to provide network connection between the first resource management platform and the second resource management platform. The target creation request carries the resource configuration information.

2. The data processing method according to claim 1, wherein the resource configuration information includes resource space occupancy information or affinity information; The step of determining the target virtual node based on the resource configuration information of the initial resource management unit includes: If, based on the resource space occupancy information of the initial resource management unit, it is determined that the first resource management platform does not meet the conditions for running the initial resource management unit, the scheduler is used to determine the target virtual node. or The target virtual node is determined using the scheduler based on the affinity information of the initial resource management unit.

3. The data processing method according to claim 1 or 2, wherein the virtual network interface includes a listening interface and a request interface; Using the virtual network interface of the target virtual node, a target creation request for the resource management unit is sent to the second resource management platform, including: The initial resource management unit is scheduled to the target virtual node using a scheduler. The resource configuration information of the initial resource management unit is obtained by using the listening interface of the target virtual node; Using the request interface of the target virtual node, a target creation request for the resource management unit is sent to the second resource management platform according to the resource configuration information.

4. The data processing method according to any one of claims 1 or 2, wherein creating an initial resource management unit in response to an initial creation request from a resource user for a resource management unit comprises: The control unit receives the initial creation request for the resource management unit from the resource user, obtains the resource configuration information of the resource management unit, and creates the initial resource management unit.

5. The data processing method according to claim 4, wherein sending a target creation request for the resource management unit to the second resource management platform using the virtual network interface of the target virtual node includes: The node information of the target virtual node is sent to the control unit using a scheduler; Using the control unit, an association is established between the initial resource management unit and the target virtual node, and the initial resource management unit is scheduled to the target virtual node; The target virtual node accesses the management and control unit through its listening interface, and listens to and obtains the resource configuration information of the initial resource management unit from the management and control unit. Using the request interface of the target virtual node, a target creation request for the resource management unit is sent to the second resource management platform according to the resource configuration information.

6. The data processing method according to claim 1, further comprising, before creating the initial resource management unit in response to the resource user's initial creation request for the resource management unit: In response to the node configuration request from the resource user for the target virtual node, the virtual network interface is configured for the target virtual node based on the resource account information of the resource user on the second resource management platform carried in the node configuration request. The virtual network interface is used to provide network connectivity between the first resource management platform and the second resource management platform.

7. A data processing method applied to a second resource management platform, comprising: In response to a target creation request sent by the first resource management platform, the target resource management unit is created based on the resource configuration information carried in the target creation request. The target creation request is sent by the first resource management platform using the virtual network interface of the target virtual node when the first resource management platform creates an initial resource management unit in response to the initial creation request of the resource user for the resource management unit, and determines the target virtual node based on the resource configuration information of the initial resource management unit. The first resource management platform and the second resource management platform are resource management platforms corresponding to different resource accounts of the resource user. Determine the target node corresponding to the target resource management unit, and run the target resource management unit on the target node.

8. The data processing method according to claim 7, wherein the second resource management platform is a hybrid cloud resource management platform; Before creating the target resource management unit in response to the target creation request sent by the first resource management platform, based on the resource configuration information carried in the target creation request, the process further includes: The resource scheduler monitors the resource specifications of the pre-allocated resources in the first resource management platform, wherein the pre-allocated resources are pre-allocated resources created by the first resource management platform according to the resource configuration information of the initial resource management unit and corresponding to the initial resource management unit; The resource scheduler performs a pre-occupancy operation on the target node of the hybrid cloud resource management platform, updates the pre-occupancy status of the pre-occupancy resource to a pre-occupancy success status, and returns a pre-occupancy success message to the first resource management platform. This enables the first resource management platform to send a target creation request to the second resource management platform based on the pre-occupancy success message. The pre-occupancy success message includes the pre-occupancy success status update information and the node information of the target node.

9. The data processing method according to claim 8, wherein determining the target node corresponding to the target resource management unit and running the target resource management unit on the target node comprises: The target node corresponding to the target resource management unit is determined based on the target creation request, and the target resource management unit is run on the target node.

10. The data processing method according to any one of claims 7-9, wherein determining the target node corresponding to the target resource management unit and running the target resource management unit on the target node comprises: The target node corresponding to the target resource management unit is determined, and the target scheduler of the second resource management platform is used to schedule the target resource management unit to the target node; On the target node, based on the resource configuration information of the target resource management unit, the initial image repository address corresponding to the first resource management platform is determined, and the initial image repository address is converted into the target image repository address corresponding to the second resource management platform. Pull the target image corresponding to the target resource management unit from the target image repository address, create and start the target container corresponding to the target resource management unit based on the target image, and run the target resource management unit.

11. The data processing method according to any one of claims 7-9, wherein running the target resource management unit on the target node comprises: In response to a storage resource request carrying target data, a target storage resource is created on the second resource management platform, the target storage resource is mounted to the target resource management unit, and the target resource management unit is run on the target node.

12. The data processing method according to any one of claims 7-9, further comprising, after running the target resource management unit on the target node: The target resource management unit receives service access requests for the target service through its target access interface, wherein the service access requests carry attribute information of the target service. If it is determined that the target service is deployed on the first resource management platform based on the attribute information of the target service, a domain name resolution request for the target service is sent to the first resource management platform based on the domain name information in the attribute information. The system receives the resolution result corresponding to the domain name resolution request returned by the first resource management platform, and accesses the target service through the management and control interaction interface based on the resolution result.

13. The data processing method according to claim 12, wherein sending a domain name resolution request for the target service to the first resource management platform based on the domain name information in the attribute information includes: Based on the domain name information in the attribute information, determine the domain name resolution request and the target transport protocol for sending the domain name resolution request; According to the target transmission protocol, the domain name resolution request is sent to the domain name resolution forwarding service in the first resource management platform that corresponds to the target transmission protocol, so as to use the domain name resolution forwarding service to send the domain name resolution request to the domain name resolution server of the first resource management platform and obtain the resolution result corresponding to the domain name resolution request.

14. A data processing system, comprising a first resource management platform and a second resource management platform, wherein, The first resource management platform is used to respond to the resource user's initial creation request for the resource management unit, create an initial resource management unit, determine the target virtual node according to the resource configuration information of the initial resource management unit, and send a target creation request for the resource management unit to the second resource management platform using the virtual network interface of the target virtual node. The second resource management platform is used to respond to the target creation request for the resource management unit sent by the first resource management platform, create the target resource management unit according to the resource configuration information carried in the target creation request, determine the target node corresponding to the target resource management unit, and run the target resource management unit on the target node.

15. A data processing apparatus, applied to a first resource management platform, comprising: The response module is configured to respond to an initial creation request from a resource user for a resource management unit, create an initial resource management unit, and determine a target virtual node based on the resource configuration information of the initial resource management unit. The sending unit is configured to use the virtual network interface of the target virtual node to send a target creation request for the resource management unit to the second resource management platform, so that the second resource management platform responds to the target creation request, creates and runs the target resource management unit. The first resource management platform and the second resource management platform are resource management platforms corresponding to different resource accounts of the resource user. The virtual network interface is used to provide network connection between the first resource management platform and the second resource management platform. The target creation request carries the resource configuration information.

16. A data processing apparatus, applied to a second resource management platform, comprising: The response module is configured to respond to a target creation request for a resource management unit sent by the first resource management platform, and to create the target resource management unit based on the resource configuration information carried in the target creation request. The target creation request is sent by the first resource management platform using the virtual network interface of the target virtual node when the first resource management platform creates an initial resource management unit in response to the initial creation request of the resource user for the resource management unit, and determines the target virtual node based on the resource configuration information of the initial resource management unit. The first resource management platform and the second resource management platform are resource management platforms corresponding to different resource accounts of the resource user. The determination module is configured to determine the target node corresponding to the target resource management unit and run the target resource management unit on the target node.

17. A computing device, comprising: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions, which, when executed by the processor, implement the steps of the data processing method according to any one of claims 1 to 13.

18. A computer-readable storage medium storing a computer program / instructions that, when executed by a processor, implement the steps of the data processing method according to any one of claims 1 to 13.

19. A computer program product comprising a computer program / instructions that, when executed by a processor, implement the steps of the data processing method according to any one of claims 1 to 13.

Images