Inter-cloud container management method, device and system, electronic equipment, medium and product

Abstract

The invention provides an inter-cloud container management method, device and system, electronic equipment, a medium and a product, and the system comprises inter-cloud interaction management and inter-cloud containerization application management. The inter-cloud interaction management is used for determining a mode role of a cloud service provider after obtaining the state update of the cloud service provider from the interface service; performing deployment constraint management according to the mode role switching strategy and the resource condition of the cloud service provider; and performing configuration change management on the cloud service provider according to the deployment constraint management. And the inter-cloud containerized application management is used for carrying out deployment management, application access management and application data management on the containerized application of the container in the cloud service provider.

Description

Technical Field

[0001] The present disclosure relates to the technical field of cloud computing, and in particular to a method, device, system, electronic device, medium and product for managing containers between clouds. Background Art

[0002] Cloud computing is a type of distributed computing. It means breaking down huge data computing programs into countless small programs through the network "cloud", and then processing and analyzing these small programs through a system composed of multiple servers to obtain results and return them to users. A cloud container can be configured with fixed resources, and multiple cloud containers can form a cloud container cluster to perform complex tasks.

[0003] In the current multi-cloud container cluster environment, there are several most commonly used multi-container cluster cloud service modes: peer to peer and intermediary. When implementing cross-cloud deployment, containerized applications usually first need to select the cloud interaction mode to ensure that the information flow exchange direction of application deployment and communication is preset in advance.

[0004] Since a fixed inter-cloud service mode needs to be selected in advance when deploying an application, if there is a new cloud service provider (CSP) in the multi-cloud container cluster or a CSP exits due to a failure, the inter-cloud service mode described above has the problem of re-access switching of container service access to IP service and service reconfiguration and deployment, which will cause interruption of business continuity. Summary of the invention

[0005] The embodiments of the present disclosure at least provide a cloud container management method, device, system, electronic device, medium and product.

[0006] In a first aspect, an embodiment of the present disclosure provides an inter-cloud container management system, including: inter-cloud interaction management and inter-cloud containerized application management;

[0007] The inter-cloud interaction management is used to determine the mode role of the cloud service provider after obtaining the status update of the cloud service provider from the interface service; perform deployment constraint management according to the mode role switching strategy and the resource situation of the cloud service provider; and perform configuration change management of the cloud service provider according to the deployment constraint management; the inter-cloud containerized application management is used to perform deployment management, application access management and application data management of containerized applications in the containers of the cloud service provider.

[0008] In an optional implementation manner, constraint management is deployed in the inter-cloud interaction management to:

[0009] In the case where the status update indicates that the primary cloud service provider exits, a new primary cloud service provider is determined according to the mode role switching strategy; wherein the mode role switching strategy includes a role switching mechanism in different modes;

[0010] The deployment constraints are updated according to the new primary cloud service provider.

[0011] In an optional implementation manner, the mode of the cloud service provider is a point-to-point mode; and the mode role switching strategy is used to:

[0012] Determining a first slave cloud service provider corresponding to the master cloud service provider;

[0013] The first slave cloud service provider is determined as the new master cloud service provider.

[0014] In an optional implementation manner, the mode of the cloud service provider is an intermediary mode; and the mode role switching strategy is used to:

[0015] Determine a second slave cloud service provider that has configured an interface to communicate with the master cloud service provider;

[0016] A cloud service provider whose resources are in an idle state is determined among the second slave cloud service providers as the new master cloud service provider.

[0017] In an optional implementation, the deployment constraints include at least: the mode role of the current cloud service provider, the mode role switching strategy, the total quota of containers required for application deployment, container service dependencies, and container scheduling strategy items.

[0018] In an optional implementation, the mode role switching strategy at least includes: a mechanism for re-electing the master cloud service provider when the master and slave cloud service providers change under the mode roles of different cloud service providers; wherein, when the cloud service provider's mode is a point-to-point mode, the mechanism is that if the master cloud service provider goes offline, the slave cloud service provider that is interconnected with its configured interface will switch to the master cloud service provider; when the cloud service provider's mode is an intermediary mode, the mechanism is that if the master cloud service provider goes offline, the slave service provider that is interconnected with its configured interface will be automatically selected as the master service provider in a resource idleness priority manner.

[0019] In an optional implementation manner, the configuration change management in the inter-cloud interaction management is used to:

[0020] According to the deployment constraint management, update at least one of the following resource configuration information of the cloud service provider: the mode role of the corresponding cloud service provider, the communication interface configuration between the corresponding cloud service providers, and the access address of the container application are synchronized to the new primary cloud service provider.

[0021] In an optional implementation manner, the inter-cloud resource management in the system is used to transmit the overall resource status of the container in the cloud service provider to the inter-cloud container scheduling;

[0022] The inter-cloud container scheduling is used to schedule inter-cloud containers in the cloud service provider according to the deployment constraint management and the overall resource status to obtain a container scheduling result.

[0023] In an optional implementation, the system further includes: inter-cloud resource management;

[0024] The inter-cloud interaction management is used to issue container deployment tasks to a single cloud container management function or other cloud service providers and obtain container deployment results when it is determined that the container deployment conditions are met;

[0025] The application deployment management in the inter-cloud containerized application management is used to obtain the container deployment results synchronized by the inter-cloud interactive management and manage the container deployment results.

[0026] In an optional implementation manner, the application deployment management is used to:

[0027] Receive a first request to deploy a containerized application between clouds, and / or receive a second request to update or delete a containerized application deployed between clouds; wherein the first request carries at least: resources required for the container by the application to be deployed and deployment constraints of the application to be deployed, wherein the deployment constraints of the application to be deployed include the total number of containers and container scheduling policy items of the application to be deployed.

[0028] In an optional implementation manner, the application data management in the inter-cloud containerized application management is used to:

[0029] In response to the data synchronization request, the application data and / or application deployment information is synchronized with the new primary cloud service provider and / or the newly added secondary cloud service provider.

[0030] In an optional implementation manner, the application access management in the inter-cloud containerized application management is used to:

[0031] After detecting an access request from a cloud user to an application, a load balancing address of the application is allocated to the cloud user.

[0032] In a second aspect, an embodiment of the present disclosure provides a cloud container management method, which is applied to the cloud container management system described in any one of the first aspects above, and the method includes:

[0033] After obtaining the status update of the cloud service provider from the interface service, determine the mode role of the cloud service provider;

[0034] Perform deployment constraint management according to the mode role switching strategy and the resource situation of the cloud service provider;

[0035] The cloud service provider is managed for configuration changes according to the deployment constraint management, and the containerized application deployment management, application access management and application data management are performed on the containers in the cloud service provider.

[0036] In an optional implementation, performing deployment constraint management according to the mode role switching strategy and the resource situation of the cloud service provider includes:

[0037] In the case where the status update indicates that the primary cloud service provider exits, a new primary cloud service provider is determined according to the mode role switching strategy; wherein the mode role switching strategy includes a role switching mechanism in different modes;

[0038] The deployment constraints are updated according to the new primary cloud service provider.

[0039] In an optional implementation, the mode of the cloud service provider is a point-to-point mode;

[0040] The determining a new primary cloud service provider according to the mode role switching strategy includes:

[0041] Determining a first slave cloud service provider corresponding to the master cloud service provider;

[0042] The first slave cloud service provider is determined as the new master cloud service provider.

[0043] In an optional implementation, the mode of the cloud service provider is an intermediary mode;

[0044] The determining a new primary cloud service provider according to the mode role switching strategy includes:

[0045] Determine a second slave cloud service provider that has configured an interface to communicate with the master cloud service provider;

[0046] A cloud service provider whose resources are in an idle state is determined among the second slave cloud service providers as the new master cloud service provider.

[0047] In an optional implementation, the deployment constraints include at least: the mode role of the new primary cloud service provider, the switching strategy, the total quota of containers required for application deployment, container service dependencies, and container scheduling strategy items.

[0048] In an optional implementation, the performing configuration change management on the cloud service provider according to the deployment constraint management includes:

[0049] According to the deployment constraint management, update at least one of the following resource configuration information of the cloud service provider: the mode role of the corresponding cloud service provider, the communication interface configuration between the corresponding cloud service providers, and the access address of the container application are synchronized to the new primary cloud service provider.

[0050] In an optional implementation manner, the method further includes:

[0051] Determine the overall resource status of the container in the cloud service provider;

[0052] Scheduling inter-cloud containers according to the deployment constraint management and the overall resource status to obtain a container scheduling result;

[0053] When it is determined that the container deployment condition is met, the containerized application is deployed according to the container scheduling result, the container deployment result is obtained, and the container deployment result is managed.

[0054] In an optional implementation, the deploying and managing containerized applications on containers in the cloud service provider includes:

[0055] Receive a first request to deploy a containerized application between clouds, and / or receive a second request to update or delete a containerized application deployed between clouds; wherein the first request carries at least: resources required for the container by the application to be deployed and deployment constraints of the application to be deployed, wherein the deployment constraints of the application to be deployed include the total number of containers and container scheduling policy items of the application to be deployed.

[0056] In an optional implementation manner, the performing application data management on the container in the cloud service provider includes:

[0057] In response to the data synchronization request, the application data and / or application deployment information is synchronized with the new primary cloud service provider and / or the newly added secondary cloud service provider.

[0058] In an optional implementation manner, the performing application access management on the container in the cloud service provider includes:

[0059] After detecting an access request from a cloud user to an application, a load balancing address of the application is allocated to the cloud user.

[0060] In a third aspect, an embodiment of the present disclosure provides a cloud container management device, the device comprising:

[0061] A determination unit, configured to determine the mode role of the cloud service provider after obtaining a status update of the cloud service provider from the interface service;

[0062] An updating unit, used to perform deployment constraint management according to the mode role switching strategy and the resource conditions of the cloud service provider;

[0063] A container deployment unit is used to manage configuration changes of the cloud service provider according to the deployment constraint management, and to perform deployment management, application access and application data management on containerized applications in the containers of the cloud service provider.

[0064] In a fourth aspect, an embodiment of the present disclosure further provides an electronic device, comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate via the bus, and when the machine-readable instructions are executed by the processor, the above-mentioned second aspect, or the steps in any possible implementation of the second aspect, are performed.

[0065] In a fifth aspect, an embodiment of the present disclosure further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned second aspect, or any possible implementation of the second aspect are executed.

[0066] In a sixth aspect, an embodiment of the present disclosure further provides a computer program product, which is stored in a storage medium and is executed by at least one processor to perform the steps in the above-mentioned second aspect, or any possible implementation of the second aspect.

[0067] The disclosed embodiments provide a method, device, system, electronic device, medium and product for managing containers between clouds. In the disclosed embodiments, after obtaining the status update of the cloud service provider from the interface service, the cloud interaction management can determine the mode role of the cloud service provider; perform deployment constraint management according to the mode role switching strategy and the resource situation of the cloud service provider; and perform configuration change management on the cloud service provider according to the deployment constraint management; thereafter, the cloud containerized application management can perform deployment management, application access and application data management on the containerized application in the cloud service provider.

[0068] In the above implementation, by setting up inter-cloud interaction management and inter-cloud containerized application management, it is possible to add deployment constraint management of containers and configuration change management of resource configuration information. When a cloud service provider CSP exits or joins, the switching of inter-cloud service modes, role switching, and update of deployment constraint management can be dynamically implemented, thereby solving the problem of business continuity interruption caused by the need to select a fixed inter-cloud service mode in advance when deploying applications across clouds, thereby enhancing the adaptability of inter-cloud clusters.

[0069] In order to make the above-mentioned objectives, features and advantages of the present disclosure more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the following is a brief introduction to the drawings required for use in the embodiments. The drawings herein are incorporated into the specification and constitute a part of the specification. These drawings illustrate embodiments consistent with the present disclosure and are used together with the specification to illustrate the technical solutions of the present disclosure. It should be understood that the following drawings only illustrate certain embodiments of the present disclosure and should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can also be obtained based on these drawings without creative work.

[0071] Figure 1 A schematic diagram of an inter-cloud container management system provided by an embodiment of the present disclosure is shown;

[0072] Figure 2 A schematic diagram of another cloud container management system provided by an embodiment of the present disclosure is shown;

[0073] Figure 3 A flow chart of a method for managing containers between clouds provided by an embodiment of the present disclosure is shown;

[0074] Figure 4 An interactive flow chart of a cloud container management method provided by an embodiment of the present disclosure is shown;

[0075] Figure 5 An interactive flow chart of a method for managing containers between clouds in a point-to-point mode provided by an embodiment of the present disclosure is shown;

[0076] Figure 6 An interactive flow chart of a method for managing cloud containers in an intermediary mode provided by an embodiment of the present disclosure is shown;

[0077] Figure 7 A schematic diagram of a cloud container management device provided by an embodiment of the present disclosure is shown;

[0078] Figure 8 A schematic diagram of an electronic device provided by an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0079] In order to make the purpose, technical scheme and advantages of the embodiments of the present disclosure clearer, the technical scheme in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all of the embodiments. The components of the embodiments of the present disclosure generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present disclosure provided in the drawings is not intended to limit the scope of the present disclosure for protection, but merely represents the selected embodiments of the present disclosure. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present disclosure.

[0080] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, further definition and explanation thereof is not required in subsequent drawings.

[0081] The term "and / or" herein only describes an association relationship, indicating that three relationships may exist. For example, A and / or B may represent the following three situations: A exists alone, A and B exist at the same time, and B exists alone. In addition, the term "at least one" herein represents any combination of at least two of any one or more of a plurality of. For example, including at least one of A, B, and C may represent including any one or more elements selected from the set consisting of A, B, and C.

[0082] Cloud computing is a type of distributed computing. It means breaking down huge data computing programs into countless small programs through the network "cloud", and then processing and analyzing these small programs through a system composed of multiple servers to obtain results and return them to users. A cloud container can be configured with fixed resources, and multiple cloud containers can form a cloud container cluster to perform complex tasks.

[0083] In the current multi-cloud container cluster environment, there are several most commonly used multi-container cluster cloud service modes: peer to peer and intermediary. When implementing cross-cloud deployment, containerized applications usually first need to select the cloud interaction mode to ensure that the information flow exchange direction of application deployment and communication is preset in advance.

[0084] For the point-to-point mode, when containerized applications are deployed in cross-cloud scenarios, two cloud service providers CSP interact with each other using peer CSP services. Assume that the two cloud service providers are CSP A and CSP B, with CSP A as the master CSP and CSP B as the slave CSP. CSP A deploys containers that provide services X and Y to its own cloud users CSC. Both CSP A and CSP B have functional components that support inter-cloud container management and container management of a single cloud. The Application Programming Interface (API) between CSP A and CSP B can be used to exchange container deployment tasks and container deployment results of CSP B and the resource status of CSP B.

[0085] In the broker mode, the CSP interacts with one or more peer CSPs and aggregates and schedules the services provided by the above peer CSPs. Assume that the cloud service provider CSP A interacts with CSP B, CSP C, CSP D and CSP E. CSP A is the primary CSP to deploy containers for providing services to its own CSCs. All CSPs between clouds should support both inter-cloud container management and single-cloud container management functional components. The API between CSP A and other CSPs unidirectionally exchanges container deployment tasks, container deployment results and resource status of other CSPs. In this state, the container application selects the broker mode to be turned on during deployment, and configures a master CSP and a federated group slave CSP.

[0086] When deploying container applications, you need to set a configuration file, which is used to configure the following information: inter-cloud service mode (for example, broker mode or peer-to-peer mode), set the role of the CSP inter-cloud service provider cluster (Master and member), and configure the interface service API Server of the CSP service provider cluster.

[0087] When a new CSP exits or joins:

[0088] Scenario 1: Any CSP cloud service provider infrastructure fails. Since there is two-way communication in point-to-point mode, the cloud service access IP of the primary CSP container can drift to the secondary CSP. However, the container service deployed on the failed CSP will still be disconnected or need to be redeployed to a new CSP container cluster; in the intermediary mode, if the primary CSP fails, due to the one-way communication mechanism and service pre-configuration, it will directly affect the container service access.

[0089] Scenario 2: A new CSP cloud service provider dynamically joins the inter-cloud service. In this case, the default broker mode is selected. According to the master-slave configuration of the container, the CSP container cluster and roles (Master and Member) need to be fixed in the cluster configuration file. Any newly added CSP cloud service provider container cluster needs to be added and modified through the interface or manually.

[0090] Based on the above research, the present disclosure provides a method, device, system, electronic device, medium and product for managing containers between clouds. In the embodiments of the present disclosure, after obtaining the status update of the cloud service provider from the interface service, the cloud interaction management can determine the mode role of the cloud service provider; perform deployment constraint management according to the mode role switching strategy and the resource situation of the cloud service provider; and perform configuration change management on the cloud service provider according to the deployment constraint management; thereafter, the cloud containerized application management can perform deployment management, application access and application data management on the containerized application in the cloud service provider.

[0091] In the above implementation, by setting up inter-cloud interaction management and inter-cloud containerized application management, it is possible to add deployment constraint management of containers and configuration change management of resource configuration information. When a cloud service provider CSP exits or joins, the switching of inter-cloud service modes, role switching, and update of deployment constraint management can be dynamically implemented, thereby solving the problem of business continuity interruption caused by the need to select a fixed inter-cloud service mode in advance when deploying applications across clouds, thereby enhancing the adaptability of inter-cloud clusters.

[0092] To facilitate understanding of this embodiment, a cloud container management system disclosed in an embodiment of the present disclosure is first introduced in detail.

[0093] See also Figure 1 As shown, it is a flow chart of an inter-cloud container management system provided by an embodiment of the present disclosure. The inter-cloud container management system 100 includes: inter-cloud interaction management 10 and inter-cloud containerized application management 20.

[0094] Here, a corresponding inter-cloud container management system 100 may be deployed in each cloud service provider. Each inter-cloud container management system 100 includes at least inter-cloud interaction management 10 and inter-cloud containerized application management 20. Inter-cloud container management systems of different cloud service providers CSP communicate through inter-cloud interaction management.

[0095] Inter-cloud interaction management 10 is used to determine the mode role of the cloud service provider after obtaining the status update of the cloud service provider from the interface service; perform deployment constraint management according to the mode role switching strategy and the resource situation of the cloud service provider; and perform configuration change management on the cloud service provider according to the deployment constraint management.

[0096] Inter-cloud containerized application management 20 is used to manage deployment, application access and application data of containerized applications in containers in the cloud service provider.

[0097] In the disclosed embodiment, the status update includes the cloud service provider CSP exiting the cluster or the cloud service provider CSP joining the cluster. The resource status update of the CSP can be monitored through the service interface of the cloud container management system, such as adding, deleting or updating. For example, the master CSP exits, the slave CSP joins, or any CSP joins.

[0098] Here, the mode role of the cloud service provider includes the mode and role of the cloud service provider. For example, the mode of the cloud service provider can be understood as an inter-cloud interaction mode. For example, the inter-cloud interaction mode can be a point-to-point mode or an intermediary mode. For another example, the role of the cloud service provider can be the role of the cloud service provider in the corresponding inter-cloud interaction mode. For example, the cloud service provider can be the primary CSP or the secondary CSP.

[0099] Here, the mode role switching strategy can be understood as the role switching strategy of the cloud service provider CSP after exiting or joining in various cloud interaction modes. At this time, the mode role switching strategy at least includes a mechanism for re-electing the master cloud service provider when the master and slave cloud service providers change under the mode roles of different cloud service providers.

[0100] For example, when the cloud service provider's mode is point-to-point mode, the mechanism can be that if the master CSP goes offline, the slave CSP that is interconnected with its configured interface will automatically switch to the master CSP; when the cloud service provider's mode is intermediary mode, the mechanism can be that the slave CSP going offline has no impact, and if the master CSP goes offline, the slave CSP that is interconnected with its configured interface can be automatically selected as the master CSP according to resource idleness priority and other methods.

[0101] The above process will be described in detail below in conjunction with specific implementation methods.

[0102] From the above description, it can be seen that after detecting the status update of the cloud service provider, it can be determined whether the cloud service provider is the primary cloud service provider; if it is determined to be the primary cloud service provider, the step of determining the mode role of the cloud service provider is executed; if it is determined to be not the primary cloud service provider but a secondary cloud service provider, the step of determining the mode role of the cloud service provider is not executed.

[0103] Here, the mode and role of each cloud service provider in the cloud service provider cluster can be determined. For example, for CSP A and CSP B in the point-to-point mode, if CSP A exits as the primary cloud service provider, the mode and role of CSP A and CSP B can be determined; for example, it can be determined that the mode of CSP A and CSP B is the point-to-point mode, and the roles are the primary cloud service provider P and the secondary cloud service provider S respectively.

[0104] After determining the mode role of the cloud service provider, containerized application deployment management (for example, updating deployment constraints), application access management, and application data management can be performed based on the switching strategy corresponding to the mode role and the resource conditions of the cloud service provider.

[0105] In an optional embodiment, if Figure 2 As shown, inter-cloud interaction management 10 includes: deployment constraint management 101 .

[0106] Deployment constraint management is used to: when the status update indicates that the primary cloud service provider exits, determine a new primary cloud service provider according to the mode role switching strategy; wherein the mode role switching strategy includes a role switching mechanism under different modes; and update the deployment constraints according to the new primary cloud service provider.

[0107] Here, the deployment constraints include at least: the mode role of the current cloud service provider (e.g., mode and role), switching strategy, total quota of containers required for application deployment, container service dependency, and container scheduling strategy items. The mode role of the current CSP in the deployment constraint can periodically perceive the inter-cloud container resource information according to the interface service, and switch according to the mode role switching strategy to update the deployment constraint information.

[0108] The container scheduling policy item includes: specifying the way to distribute containers among clouds, for example, evenly distributing containers among all CSPs, or weightedly distributing containers among different master and slave CSPs, etc.

[0109] In the embodiment of the present disclosure, when the deployment constraint management determines that the master cloud service provider exits based on the status update of the cloud service provider CSP, the mode and role of the master cloud service provider and the slave cloud service provider corresponding to the master cloud service provider can be determined. Then, a new master cloud service provider is determined according to the mode role switching strategy.

[0110] Here, the method of determining the target cloud service provider is different according to the different cloud-to-cloud interaction modes of cloud service providers.

[0111] After determining the new primary cloud service provider, the deployment constraints can be updated according to the new primary cloud service provider. For example, the mode role of the current cloud service provider can be updated, the mode role of the new primary cloud service provider at the current moment can be updated, the mode role of the secondary cloud service provider can be updated, the total quota of containers required for application deployment of the current cloud service provider (new primary cloud service provider and / or secondary cloud service provider) can be updated, the container service dependencies deployed in the container of the current cloud service provider can be updated, and the container scheduling policy items of the application deployed in the container of the current cloud service provider can be updated.

[0112] The updated deployment constraints can determine the mode and role of each cloud provider, the total quota of containers scheduled for each cloud provider, and information such as the applications deployed in each container.

[0113] The following will introduce the process of determining a new primary cloud service provider for the point-to-point model and the intermediary model respectively.

[0114] Mode 1: The cloud service provider’s mode is point-to-point mode.

[0115] In this case, the mode role switching strategy is used to:

[0116] Determining a first slave cloud service provider corresponding to the master cloud service provider;

[0117] The first slave cloud service provider is determined as the new master cloud service provider.

[0118] In an embodiment of the present disclosure, in point-to-point mode, if it is detected that the master cloud service provider exits, a slave CSP with which an interface has been configured for intercommunication with the master cloud service provider is determined to obtain the first slave cloud service provider described above. At this time, the first slave cloud service provider can be determined as the new master cloud service provider.

[0119] In the case of the main cloud service provider's exit, a new cloud service provider can be automatically added. Next, it can be determined whether the resources of the new cloud service provider can meet the capacity requirements of the resources on the main cloud service provider. The capacity requirements can be understood as the quota and number of Pod containers on the main cloud service provider. If it is determined that the resources of the new cloud service provider can meet the capacity requirements of the resources on the main cloud service provider, the new cloud service provider can be determined as a secondary cloud service provider.

[0120] Model 2: The cloud service provider’s model is the intermediary model.

[0121] In this case, the mode role switching strategy is used to:

[0122] Determine a second slave cloud service provider that has configured an interface to communicate with the master cloud service provider;

[0123] A cloud service provider whose resources are in an idle state is determined among the second slave cloud service providers as the new master cloud service provider.

[0124] In the embodiment of the present disclosure, in the intermediary mode, if it is detected that the master cloud service provider exits, a slave CSP with which an interface has been configured for intercommunication with the master cloud service provider is determined to obtain the second slave cloud service provider described above.

[0125] Next, a cloud service provider whose resources are in an idle state may be determined from the second slave cloud service providers, and then a new master cloud service provider may be determined based on the cloud service provider.

[0126] Here, if there are multiple cloud service providers whose resources are in an idle state, a cloud service provider whose resources can meet the capacity requirements of the resources on the primary cloud service provider can be determined from the multiple cloud service providers as the new primary cloud service provider. If the resources of each cloud service provider whose resources are in an idle state can meet the capacity requirements of the resources on the primary cloud service provider, any cloud service provider can be determined from the multiple cloud service providers as the new primary cloud service provider.

[0127] For the point-to-point mode and the intermediary mode, after determining the new primary cloud service provider in the manner described above, the deployment constraints can be updated according to the new primary cloud service provider, and the resource configuration information of the cloud service provider can be updated according to the deployment constraints, thereby realizing configuration change management of the cloud service provider.

[0128] In an optional embodiment, if Figure 2 As shown, the cloud-to-cloud interaction management 10 includes: configuration change management 102. The configuration change management is used to:

[0129] According to the deployment constraint management, update at least one of the following resource configuration information of the cloud service provider: the mode role of the corresponding cloud service provider, the communication interface configuration between the corresponding cloud service providers, and the access address of the container application are synchronized to the new primary cloud service provider.

[0130] In the disclosed embodiment, after the deployment constraint management is performed on the cloud service provider, the resource configuration information needs to be updated through configuration change management, and the continuity of application access can be guaranteed by updating the resource configuration information. Here, the target information in the resource configuration information can be updated, wherein the target information is information that can ensure the continuity of application access, for example, the target information can be the mode role of the corresponding cloud service provider, the communication interface configuration between the corresponding cloud service providers, and the access address of the container application synchronized to the new primary cloud service provider.

[0131] During specific implementation, the mode role of the corresponding cloud service provider in the resource configuration information can be modified. For example, for CSP A and CSP B in point-to-point mode, if the main cloud service provider CSP A exits and a new cloud service provider CSP C is added, at this time, the main cloud service provider can be updated to CSP B in the resource configuration information, and the slave cloud service provider can be updated to CSP C. The communication interface configuration of the service interface in the resource configuration information, that is, the communication configuration direction, can also be modified. For example, if the main cloud service provider CSPA exits, the main cloud service provider is updated to CSP B, and a new cloud service provider CSP C is added as the slave cloud service provider of CSP B. At this time, the communication interface between CSP B and CSP C can be configured from CSP B to CSP C. The access address of the container application in the resource configuration information can also be modified. For example, the access address of the container application deployed in the exited main cloud service provider can be synchronized to the new main cloud service provider. For example, the access address of the container application deployed in CSP A can be synchronized to CSP B.

[0132] Through the above processing, the continuity of application access can be guaranteed, thereby solving the problem of business continuity interruption caused by the need to select a fixed inter-cloud service mode in advance when the application is deployed across clouds, thereby enhancing the adaptability of the inter-cloud cluster.

[0133] In an optional embodiment, if Figure 1 and Figure 2 As shown, the system also includes: inter-cloud resource management 40.

[0134] Inter-cloud resource management 40, for transmitting the overall resource status of the container in the cloud service provider to the inter-cloud container scheduling;

[0135] Inter-cloud container scheduling 30 is used to schedule inter-cloud containers in the cloud service provider according to the deployment constraint management and the overall resource status to obtain the container scheduling result.

[0136] In the disclosed embodiment, the cloud interaction management 10 can obtain the resource status of the cloud service provider or the resource status of the newly joined cloud service provider, for example, Figure 1 As shown, cloud service providers can transfer resource status through inter-cloud interaction management. Afterwards, inter-cloud interaction management can send the resource status of the new master cloud service provider and the corresponding slave cloud service provider to inter-cloud resource management. After obtaining the resource status of the new master cloud service provider and the corresponding slave cloud service provider, inter-cloud resource management can feed back the resource status of the new master cloud service provider and the corresponding slave cloud service provider as the overall resource status to inter-cloud container scheduling.

[0137] After obtaining the overall resource status of the current inter-cloud container, the inter-cloud container scheduling can reschedule the container in the new primary cloud service provider and the secondary cloud service provider according to the overall resource status and the deployment constraints described above, thereby obtaining the container scheduling result.

[0138] For the point-to-point mode, if the inter-cloud container scheduling determines based on the deployment constraints and overall resource status that the containers in the new master cloud service provider and the slave cloud service provider do not need to be rescheduled, the container scheduling result is determined according to the deployment status of the containers in the master cloud service provider and the slave cloud service provider at the current moment.

[0139] For the intermediary mode, if the inter-cloud container scheduling determines that the containers in the new primary cloud service provider and the secondary cloud service provider need to be rescheduled based on the deployment constraints and the overall resource status, the inter-cloud container scheduling can schedule the inter-cloud containers according to the deployment constraints and the overall resource status described above, obtain the container scheduling results, and send the container scheduling results to the inter-cloud interaction management.

[0140] In an optional embodiment, if Figure 1 and Figure 2 As shown, inter-cloud containerized application management 20 includes: application deployment management 201 .

[0141] Inter-cloud interaction management 10, used to send container deployment tasks to single-cloud container management functions or other cloud service providers and obtain container deployment results when it is determined that container deployment conditions are met;

[0142] Application deployment management 201 is used to obtain the container deployment results synchronized by the inter-cloud interaction management and manage the container deployment results.

[0143] In an embodiment of the present disclosure, application deployment management can be set in inter-cloud containerized application management, wherein the application deployment management can also receive requests to update or delete application containers deployed between clouds, and manage container deployment results of all containerized applications.

[0144] In the embodiment of the present disclosure, the cloud-to-cloud interaction management can issue container deployment tasks to a single-cloud container management function or other cloud service providers and obtain container deployment results when it is determined that the container deployment conditions are met.

[0145] After obtaining the container deployment result, the container deployment result may be synchronized with the application deployment management in the inter-cloud containerized application management so as to manage the container deployment result through the application deployment management.

[0146] It can be seen from the above description that inter-cloud container scheduling can schedule inter-cloud containers according to deployment constraints and overall resource status, thereby obtaining container scheduling results, and transmitting the container scheduling results to inter-cloud interaction management.

[0147] After receiving the container scheduling result, the cloud-to-cloud interaction management needs to deploy the container according to the container scheduling policy item of the application in the deployment constraint. In specific implementation, the cloud-to-cloud interaction management can issue container deployment tasks to the single-cloud container management function or other cloud service providers. The single-cloud container management function or other cloud service providers execute the container deployment task to obtain the container deployment result, and feed back the container deployment task to the cloud-to-cloud interaction management. After obtaining the container deployment result, the cloud-to-cloud interaction management can synchronize the container deployment result with the application deployment management of the cloud-to-cloud containerized application management, so as to manage the container deployment result through the application deployment management.

[0148] In the disclosed embodiment, after the inter-cloud interaction management obtains the container scheduling result, if the application deployment management perceives that the containerized application needs to be redeployed, the container scheduling and inter-cloud interaction management can automatically trigger the issuance of container deployment tasks to the single cloud container management function or other cloud service providers. At this time, the inter-cloud interaction management obtains the container scheduling result, which means that the container deployment conditions are met.

[0149] Here, when the user needs to redeploy the containerized application, he can send a redeployment request to the application deployment management. After receiving the redeployment request, the application deployment management can trigger the inter-cloud interaction management to send the container deployment task to the single cloud container management function or other cloud service providers, and obtain the container deployment result.

[0150] In an optional implementation, application deployment management is used to:

[0151] Receive a first request to deploy a containerized application between clouds, and / or receive a second request to update or delete a containerized application deployed between clouds; wherein the first request carries at least: resources required for the container by the application to be deployed and deployment constraints of the application to be deployed, wherein the deployment constraints of the application to be deployed include the total number of containers and container scheduling policy items of the application to be deployed.

[0152] In the embodiments of the present disclosure, in addition to managing the container deployment results, the application deployment management can also receive a first request sent externally to deploy a containerized application between clouds. Through the first request, the resources required for the container by the application to be deployed and the deployment constraints of the application to be deployed can be determined, for example, the total number of required containers and the container scheduling policy items of the application to be deployed.

[0153] After receiving the first request, the application deployment management can deploy the application to be deployed in the container according to the first request. For example, the application deployment management can send the deployment task of the application to be deployed to the unit container management function or other cloud service providers through inter-cloud interaction management, and obtain the application deployment result of the application to be deployed.

[0154] The application deployment management may also receive a second request to update or delete the containerized application deployed between clouds. At this time, the application deployment management may issue the task of updating or deleting the containerized application to the unit container management function or other cloud service providers through the cloud interaction management.

[0155] In an optional embodiment, if Figure 2 As shown, the inter-cloud containerized application management includes: application data management 202, wherein the application data management 202 is used to:

[0156] In response to the data synchronization request, the application data and / or application deployment information is synchronized with the new primary cloud service provider and / or the newly added secondary cloud service provider.

[0157] In the disclosed embodiment, the cloud container management system supports synchronization and replication of containerized application data across different CSPs in different clouds. The application data includes the service status of the containerized application, local configuration data generated by the service operation, and other data, which are not specifically limited here.

[0158] Here, after detecting the data synchronization request of the designated cloud service provider, the application data management can synchronize the application data of the cloud service provider corresponding to the cloud container management system to the cloud interaction management. Afterwards, the application data and / or application deployment information can be synchronized to the designated cloud service provider (for example, the new primary cloud service provider and / or the newly added secondary cloud service provider) through the service interface of the cloud interaction management. For example, the application data and / or application deployment information can be synchronized to the new primary cloud service provider, and to the newly added secondary cloud service provider, and the application data and / or application deployment information can be synchronized to the new primary cloud service provider and the newly added secondary cloud service provider at the same time.

[0159] In addition, application data management can also regularly synchronize application data to inter-cloud interaction management, and inter-cloud interaction management can be synchronized to the designated cloud service provider CSP through the service interface.

[0160] In an optional embodiment, if Figure 2 As shown, the cloud containerized application management 20 includes: application access management 203, wherein the application access management 203 is used to:

[0161] After detecting a cloud user's access request to an application, an access address of the application is allocated to the cloud user.

[0162] In the disclosed embodiment, when a cloud user CSC is monitored to request access to an application, the application access management can act as a DNS (Domain Name System) server and load balancer, through which the application access address can be provided, that is, the address of the application load balanced among different CSPs of the CSC by accessing the IP.

[0163] The following will be combined Figure 1 and Figure 2 This article introduces the overall process of the cloud container management system.

[0164] like Figure 1 As shown, a corresponding inter-cloud container management system 100 can be deployed in each cloud service provider. Each inter-cloud container management system 100 includes at least inter-cloud interaction management 10, inter-cloud containerized application management 20, inter-cloud container scheduling 30, and inter-cloud resource management 40. The inter-cloud container management systems of different cloud service providers CSP communicate through inter-cloud interaction management.

[0165] like Figure 2 As shown, inter-cloud interaction management 10 includes deployment constraint management 101 and configuration change management 102 ; inter-cloud containerized application management 20 includes application deployment management 201 , application data management 202 and application access management 203 .

[0166] After obtaining the status update of the cloud service provider from the interface service, the cloud interaction management can determine the mode role of the cloud service provider; then, according to the mode role switching strategy and the resource situation of the cloud service provider, perform deployment constraint management, for example, update deployment constraints; and perform configuration change management for the cloud service provider based on the deployment constraint management.

[0167] In addition, the cloud-to-cloud interaction management can also obtain the resource status of the cloud service provider transmitted by the cloud-to-cloud interaction management of other cloud service providers, for example, recorded as the resource status of CSP B. The cloud-to-cloud interaction management can also transmit container deployment tasks to other cloud service providers and obtain the container deployment results of the cloud service provider for the container deployment task.

[0168] After acquiring the resource status of the other cloud service provider, the inter-cloud interaction management can pass the resource status to the inter-cloud resource management. Here, the single cloud container management function of the current cloud service provider can also pass the resource status of the current cloud service provider to the inter-cloud resource management, for example, recorded as the resource status of CSP A.

[0169] After obtaining the resource status of CSP A and the resource status of CSP B, the inter-cloud resource management can obtain the overall resource status of the current inter-cloud container; then, the overall resource status can be synchronized to the inter-cloud container scheduling.

[0170] Inter-cloud container scheduling can schedule inter-cloud containers in cloud service providers based on deployment constraint management and overall resource status to obtain container scheduling results.

[0171] After implementing the scheduling of inter-cloud containers, inter-cloud interaction management can also issue container deployment tasks to single-cloud container management functions or other cloud service providers and obtain container deployment results when it is determined that the container deployment conditions are met. Application deployment management in inter-cloud containerized application management can obtain the container deployment results synchronized by the inter-cloud interaction management and manage the container deployment results.

[0172] Here, for the intermediary mode, inter-cloud container scheduling can schedule inter-cloud containers according to deployment constraints and overall resource status, obtain container scheduling results, and send container scheduling results to inter-cloud interaction management. Inter-cloud interaction management can execute container deployment tasks through the single cloud container management function when it is determined that the container deployment conditions are met, obtain container deployment results, and pass container deployment results to application deployment management.

[0173] In the disclosed embodiment, the application data management can synchronize application data and / or application deployment information with the new primary cloud service provider and / or the newly added secondary cloud service provider after detecting the data synchronization request. Afterwards, the application data can be synchronized with the designated cloud service provider through the service interface of the cloud-to-cloud interaction management.

[0174] In the embodiment of the present disclosure, when a cloud user CSC is monitored to request access to an application, the application access management can act as a DNS server and load balancer, through which the application access address can be provided, that is, the address of the application load balanced among different CSPs of the CSC by accessing the IP.

[0175] It can be seen from the above description that in the embodiment of the present disclosure, the following functions are added in the “inter-cloud interaction management”:

[0176] Responsible for managing other CSP cloud service providers in the interactive cloud, and using the single cloud container management function to implement container deployment tasks. The information exchanged between CSPs in the cloud includes container deployment tasks and container deployment results, as well as the resource status of different CSPs in the cloud.

[0177] Deployment constraint management in inter-cloud interaction management has the following functions:

[0178] Deployment constraint management can add, delete, and update deployment constraints based on application requests and the status of inter-cloud resources. Deployment constraints include the current CSP mode (point-to-point mode or intermediary mode) and role (Master / member), mode role switching strategy, and the total quota of containers required for application deployment, container service dependencies, and container scheduling strategy items of applications. In deployment constraints, the CSP mode role can periodically perceive inter-cloud container resource information based on the interface service, and switch according to the mode role switching strategy to update the deployment constraint information.

[0179] The mode role switching strategy includes: in point-to-point mode, if the master CSP goes offline, the slave CSP that communicates with its configured interface can automatically switch to the new master CSP; in intermediary mode, the slave CSP going offline has no impact. When the master CSP goes offline, you can choose to automatically select a slave CSP from the slave CSPs that communicate with its configured interface as the new master CSP according to resource idle priority and other methods.

[0180] The container scheduling policy item includes: specifying the way to distribute containers among clouds, for example, evenly distributing containers among all CSPs, or weightedly distributing containers among different master and slave CSPs, etc.

[0181] Configuration change management in cloud-to-cloud interaction management has the following functions:

[0182] When there is a CSP joining or leaving the cloud, the primary CSP supports rescheduling containers between clouds based on the reconfigured deployment constraints. When the deployment constraints are updated, the configuration change management needs to modify the corresponding configuration information so that the access IP of the container application can be synchronized to the primary CSP in time to ensure the continuity of application access.

[0183] In the embodiment of the present disclosure, the following functions are added to the "inter-cloud containerized application management" function group:

[0184] Responsible for receiving application deployment requests (i.e., the first request) for deploying containerized applications between clouds, and managing application access and deployment access. The required resources specify information such as CPU, memory, and storage for each container in the application deployment request. Deployment constraints are also specified in the application deployment request, and the deployment constraints focus on the total number of containers and the container scheduling policy items for this application. In addition, inter-cloud containerized application management is also responsible for receiving requests to update or delete application containers deployed between clouds (i.e., the second request) and managing all containerized application deployment results.

[0185] Application access management in inter-cloud containerized application management has the following functions: When a CSC requests access to an application, the application access management acts as a DNS server and load balancer to provide IP addresses for application loads balanced across different CSPs of the CSC.

[0186] Application deployment management in inter-cloud containerized application management has the following functions: communicating application cross-cluster deployment constraints and container scheduling policy items with inter-cloud container scheduling, obtaining synchronized container deployment results, and deploying containers.

[0187] Application data management in inter-cloud containerized application management has the following functions: Supports synchronization and replication of containerized application data and application deployment information across different CSPs in different clouds. Application data includes the service status of container applications, local configuration data generated by service operation, etc., which will be regularly synchronized to the inter-cloud interaction function group and synchronized to the CSP with related container deployment services through the service interface.

[0188] See also Figure 3 FIG. 1 is a flowchart of a method for managing cloud containers provided by an embodiment of the present disclosure, wherein the method comprises the following steps:

[0189] S301: After obtaining the status update of the cloud service provider from the interface service, determine the mode role of the cloud service provider;

[0190] S302: Performing deployment constraint management according to the mode role switching strategy and the resource situation of the cloud service provider;

[0191] S303: Perform configuration change management on the cloud service provider according to the deployment constraint management, and perform deployment management, application access management, and application data management on containerized applications in the containers of the cloud service provider.

[0192] In the above implementation, by setting up inter-cloud interaction management and inter-cloud containerized application management, it is possible to add deployment constraint management of containers and configuration change management of resource configuration information. When a cloud service provider CSP exits or joins, the switching of inter-cloud service modes, role switching, and update of deployment constraint management can be dynamically implemented, thereby solving the problem of business continuity interruption caused by the need to select a fixed inter-cloud service mode in advance when deploying applications across clouds, thereby enhancing the adaptability of inter-cloud clusters.

[0193] In an optional implementation, performing deployment constraint management according to the mode role switching strategy and the resource situation of the cloud service provider includes:

[0194] In the case where the status update indicates that the primary cloud service provider exits, a new primary cloud service provider is determined according to the mode role switching strategy; wherein the mode role switching strategy includes a role switching mechanism in different modes;

[0195] The deployment constraints are updated according to the new primary cloud service provider.

[0196] Specific implementation methods are as described in the above-mentioned embodiments of the cloud container management system, which will not be described in detail here.

[0197] In an optional implementation, when the mode of the cloud service provider is a point-to-point mode, determining a new primary cloud service provider according to the mode role switching strategy includes:

[0198] Determining a first slave cloud service provider corresponding to the master cloud service provider;

[0199] The first slave cloud service provider is determined as the new master cloud service provider.

[0200] Here, when it is determined that the resources of the first slave cloud service provider meet the capacity requirements of the resources on the master cloud service provider, the first slave cloud service provider is determined to be the new master cloud service provider.

[0201] Specific implementation methods are as described in the above-mentioned embodiments of the cloud container management system, which will not be described in detail here.

[0202] In an optional implementation, when the mode of the cloud service provider is the intermediary mode, determining a new primary cloud service provider according to the mode role switching strategy includes:

[0203] Determine a second slave cloud service provider that has configured an interface to communicate with the master cloud service provider;

[0204] A cloud service provider whose resources are in an idle state is determined among the second slave cloud service providers as the new master cloud service provider.

[0205] Specific implementation methods are as described in the above-mentioned embodiments of the cloud container management system, which will not be described in detail here.

[0206] In an optional implementation, the deployment constraints include at least: the mode role of the current cloud service provider, the mode role switching strategy, the total quota of containers required for application deployment, container service dependencies, and container scheduling strategy items of the application program.

[0207] Specific implementation methods are as described in the above-mentioned embodiments of the cloud container management system, which will not be described in detail here.

[0208] In an optional implementation, the performing configuration change management on the cloud service provider according to the deployment constraint management includes:

[0209] According to the deployment constraint management, update at least one of the following resource configuration information of the cloud service provider: the mode role of the corresponding cloud service provider, the communication interface configuration between the corresponding cloud service providers, and the access address of the container application are synchronized to the new primary cloud service provider.

[0210] Specific implementation methods are as described in the above-mentioned embodiments of the cloud container management system, which will not be described in detail here.

[0211] In an optional embodiment, the method further comprises:

[0212] Determine the overall resource status of the container in the cloud service provider;

[0213] Scheduling inter-cloud containers according to the deployment constraint management and the overall resource status to obtain a container scheduling result;

[0214] When it is determined that the container deployment condition is met, the containerized application is deployed according to the container scheduling result, the container deployment result is obtained, and the container deployment result is managed.

[0215] Specific implementation methods are as described in the above-mentioned embodiments of the cloud container management system, which will not be described in detail here.

[0216] In an optional implementation, deploying and managing containerized applications on containers in the cloud service provider includes:

[0217] Receive a first request to deploy a containerized application between clouds, and / or receive a second request to update or delete a containerized application deployed between clouds; wherein the first request carries at least: resources required for the container by the application to be deployed and deployment constraints of the application to be deployed, wherein the deployment constraints of the application to be deployed include the total number of containers and container scheduling policy items of the application to be deployed.

[0218] In an optional implementation, the performing application data management on the container in the cloud service provider includes:

[0219] In response to the data synchronization request, the application data and / or application deployment information is synchronized with the new primary cloud service provider and / or the newly added secondary cloud service provider.

[0220] Specific implementation methods are as described in the above-mentioned embodiments of the cloud container management system, which will not be described in detail here.

[0221] In an optional implementation, the performing application access management on the container in the cloud service provider includes:

[0222] After detecting an access request from a cloud user to an application, a load balancing address of the application is allocated to the cloud user.

[0223] Specific implementation methods are as described in the above-mentioned embodiments of the cloud container management system, which will not be described in detail here.

[0224] Combine the following Figure 4 This article provides an overall introduction to the above-mentioned cloud container management system. Figure 4 As shown, the specific process includes the following:

[0225] S41: The deployment constraint management detects a status update of CSP A through a service interface.

[0226] S42: Deployment constraint management performs deployment constraints according to the switching strategy of the mode role and the resource conditions of the cloud service provider.

[0227] S43: The deployment constraint management pushes the updated deployment constraint to the configuration change management.

[0228] S44: Configuration change management updates the cloud service provider's resource configuration information according to the deployment constraints.

[0229] The resource configuration information specifically includes at least one of the following: a mode role corresponding to the cloud service provider, a communication interface configuration between corresponding cloud service providers, and an access address of the container application synchronized to the new primary cloud service provider.

[0230] S45: Configuration change management synchronizes resource changes to container resource management in the inter-cloud resource manager.

[0231] S46: The container resource management synchronizes the overall resource status of the current inter-cloud container to the container scheduling.

[0232] S47: The container scheduling schedules the inter-cloud containers in the cloud service provider according to the deployment constraint management and the overall resource status, thereby obtaining the container scheduling result, and synchronizing the container scheduling result to the inter-cloud interaction management.

[0233] S48: The container scheduling deploys the inter-cloud container according to the container scheduling policy item of the application, obtains the container deployment result, and synchronizes the container deployment result.

[0234] In the disclosed embodiment, the cloud-to-cloud interaction management can issue container deployment tasks to the single-cloud container management function or other cloud service providers and obtain container deployment results when it is determined that the container deployment conditions are met. The application deployment management can obtain the container deployment results synchronized by the cloud-to-cloud interaction management and manage the container deployment results.

[0235] Here, after obtaining the container scheduling results, the inter-cloud interaction management can directly send container deployment tasks to the single-cloud container management function or other cloud service providers and obtain the container deployment results, thereby realizing the automatic deployment of containerized applications. Figure 4 Not shown in the figure.

[0236] Here, when the user needs to redeploy the containerized application, he can send a redeployment request to the application deployment management. After the application deployment management perceives the redeployment of the containerized application based on the redeployment request, it can trigger the inter-cloud interaction management to send the container deployment task to the single cloud container management function or other cloud service providers, and obtain the container deployment result. Figure 4 As shown, the application deployment management can deploy cloud containers according to the container scheduling policy items of the application program through container scheduling, obtain container deployment results, and synchronize the container deployment results. Specifically, the container scheduling can instruct the cloud interaction management to deploy cloud containers according to the container scheduling policy items of the application program, obtain container deployment results, and thus instruct the cloud interaction management to synchronize the container deployment results to the application deployment management.

[0237] S49: Application deployment management triggers synchronization of application data to a new primary cloud service provider and / or a newly added secondary cloud service provider.

[0238] S410: The application deployment management can also update the application deployment information;

[0239] S411: The application data management synchronizes the application data to the new primary cloud service provider and / or the newly added secondary cloud service provider.

[0240] S412: The application deployment management synchronizes the application deployment information to the new primary cloud service provider and / or the newly added secondary cloud service provider.

[0241] S413: The cloud user sends an access request for the containerized application to the application access management through the service interface.

[0242] S414: After receiving the access request, the application access management may determine the load balancing address of the application for the cloud user.

[0243] The following describes the above-described cloud container management system in different scenarios.

[0244] Scenario 1: The cloud-to-cloud interaction mode is point-to-point.

[0245] In this scenario, CSP A is the master CSP and CSP B is the slave CSP. When CSP A exits due to a fault, it automatically joins the CSPC. Figure 5 As shown, the following process can be performed:

[0246] The deployment constraint management detects the status update of CSP A through the service interface of the cloud-to-cloud interaction management. For example, it is detected that CSP A exits due to a fault.

[0247] Deployment constraint management updates deployment constraints based on the mode role switching strategy and the cloud service provider's resource conditions. Figure 5 As shown, the deployment constraint management determines that the mode is point-to-point mode, CSP A is the master CSP, CSP B is the slave CSP, and CSP B and CSP A are configured with communication interfaces to communicate by default, then CSP B is determined to be the new master CSP, and CSP C is the slave CSP.

[0248] In specific implementation, deployment constraint management can determine the mode roles of CSP A and CSP B, and determine whether CSP B and CSP A are configured with communication interface intercommunication by default; for example, it can be determined that the mode is point-to-point mode, CSP A is the master CSP, and CSP B is the slave CSP, that is, (CSP A: P, CSP B: S); if it is determined that CSP B and CSP A are configured with communication interface intercommunication by default, CSP B is determined as the new master CSP, and CSP C is the slave CSP, that is, (CSP B: P, CSP C: S). After determining the new master CSP and slave CSP, the deployment constraints can be updated; and the updated deployment constraints can be pushed to the configuration change management.

[0249] Deployment constraint management can push updated deployment constraints to configuration change management. Configuration change management can update the cloud provider's resource configuration information based on deployment constraints.

[0250] like Figure 5 As shown, the configuration change management can update CSP B as the new master CSP and CSP C as the slave CSP; set the communication interface configuration from CSP B to CSP C; and synchronize the access address of the container application to CSP B.

[0251] Configuration change management can synchronize resource changes with container resource management, and container resource management can synchronize the overall resource status of current inter-cloud containers with container scheduling. Container scheduling schedules inter-cloud containers based on the overall resource status and deployment constraints.

[0252] Container scheduling can deploy cloud containers according to the container scheduling policy items of the application, obtain container deployment results, and synchronize the container deployment results to the application deployment management. After receiving the container deployment results, the application deployment management manages the container deployment results. The specific implementation process is as follows: Figure 4 The description is not repeated here.

[0253] Here, the application deployment management triggers the application data management to synchronize the application data to the newly joined slave cloud service provider CSP C. The application deployment management can update the application deployment information and synchronize the application deployment information to the newly joined slave cloud service provider CSP C.

[0254] Here, the cloud user can send an access request for the containerized application to the application access management through the service interface. The application access management can also determine the load balancing address of the application for the cloud user after detecting the cloud user's access to the container service.

[0255] Scenario 2: The cloud-to-cloud interaction mode is the intermediary mode.

[0256] In this scenario, CSP A is the master CSP and CSP B is the slave CSP. When CSP A exits due to a fault, CSP C automatically joins. Figure 6 As shown, the following process can be performed:

[0257] The deployment constraint management detects the status update of CSP A through the service interface of the cloud-to-cloud interaction management, for example, detecting that CSP A exits due to a failure.

[0258] Afterwards, the deployment constraint management updates the deployment constraints according to the mode role switching strategy and the cloud service provider’s resource conditions. Figure 6 As shown, the deployment constraint management can determine the mode roles of CSP A and CSP B, and the resource conditions of CSP B and CSP C, and update the deployment constraints according to the resource conditions.

[0259] For example, it can be determined that the mode is an intermediary mode, CSP A is the main CSP, and CSP B is the slave CSP. At this time, the cloud service provider whose resources among CSP B and CSP C meet the capacity requirements of resources on CSP A can be determined as the new main cloud service provider based on the resource situation of CSP B and CSP C. For example, if only one of the resources of CSP B and CSP C meets the capacity requirements of resources on CSP A, it will be used as the new main cloud service provider. For another example, if the resources of CSP B and CSP C both meet the capacity requirements of resources on CSP A, the cloud service provider with high idle resources can be selected as the new main cloud service provider based on the principles of idle priority and latency priority. Assuming that CSP C has the highest idleness, CSP C can be determined as the new main cloud service provider.

[0260] Deployment constraint management can push updated deployment constraints to configuration change management. Configuration change management can update the cloud provider's resource configuration information based on deployment constraints.

[0261] like Figure 6As shown, the configuration change management can update CSP C as the new master CSP and CSP B as the slave CSP; set the communication interface configuration from CSP C to CSP B; and synchronize the access address of the container application to CSP C.

[0262] Configuration change management can synchronize resource changes with container resource management, and container resource management can synchronize the overall resource status of current inter-cloud containers with container scheduling. Container scheduling schedules inter-cloud containers based on the overall resource status and deployment constraints.

[0263] Container scheduling can deploy cloud containers according to the container scheduling policy items of the application, obtain container deployment results, and synchronize the container deployment results to the application deployment management. After receiving the container deployment results, the application deployment management manages the container deployment results. The specific implementation process is as follows: Figure 4 The description is not repeated here.

[0264] Here, the application deployment management triggers the application data management to synchronize the application data to the new primary cloud service provider and the newly joined cloud service provider. The application deployment management can update the application deployment information and synchronize the application deployment information to the newly joined cloud service provider CSP C.

[0265] Here, the application access management can also determine the load balancing address of the application for the cloud user after detecting the cloud user's access to the container service.

[0266] Those skilled in the art will appreciate that, in the above method of specific implementation, the order in which the steps are written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of the steps should be determined by their functions and possible internal logic.

[0267] Based on the same inventive concept, an inter-cloud container management device corresponding to the inter-cloud container management method is also provided in the embodiment of the present disclosure. Since the principle of solving the problem by the device in the embodiment of the present disclosure is similar to the above-mentioned inter-cloud container management method in the embodiment of the present disclosure, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0268] Reference Figure 7 , which is a schematic diagram of a cloud container management device provided by an embodiment of the present disclosure, the device includes: a determination unit 71, an update unit 72, and a container deployment unit 73; wherein,

[0269] A determination unit, configured to determine the mode role of the cloud service provider after obtaining a status update of the cloud service provider from the interface service;

[0270] An updating unit, used to perform deployment constraint management according to the mode role switching strategy and the resource conditions of the cloud service provider;

[0271] The container deployment unit is used to manage configuration changes of the cloud service provider according to the deployment constraint management, and to perform deployment management, application access management and application data management on containerized applications in the containers of the cloud service provider.

[0272] In a possible implementation manner, the updating unit is further configured to:

[0273] In the case where the status update indicates that the primary cloud service provider exits, a new primary cloud service provider is determined according to the mode role switching strategy; wherein the mode role switching strategy includes a role switching mechanism in different modes;

[0274] The deployment constraints are updated according to the new primary cloud service provider.

[0275] In a possible implementation manner, the updating unit is further configured to:

[0276] In the case where the mode of the cloud service provider is a point-to-point mode, determining a first slave cloud service provider corresponding to the master cloud service provider;

[0277] The first slave cloud service provider is determined as the new master cloud service provider.

[0278] In a possible implementation manner, the updating unit is further configured to:

[0279] In the case where the mode of the cloud service provider is the intermediary mode, determining a second slave cloud service provider that has configured an interface to communicate with the master cloud service provider;

[0280] A cloud service provider whose resources are in an idle state is determined among the second slave cloud service providers as the new master cloud service provider.

[0281] In a possible implementation, the deployment constraints include at least: the mode role of the new primary cloud service provider, the mode role switching strategy, the total quota of containers required for application deployment, container service dependencies, and container scheduling strategy items.

[0282] In a possible implementation manner, the container deployment unit is further used to:

[0283] According to the deployment constraint management, update at least one of the following resource configuration information of the cloud service provider: the mode role of the corresponding cloud service provider, the communication interface configuration between the corresponding cloud service providers, and the access address of the container application are synchronized to the new primary cloud service provider.

[0284] In a possible implementation manner, the container deployment unit is further used to:

[0285] Determine the overall resource status of the container in the cloud service provider;

[0286] Scheduling inter-cloud containers according to the deployment constraint management and the overall resource status to obtain a container scheduling result;

[0287] When it is determined that the container deployment condition is met, the containerized application is deployed according to the container scheduling result, the container deployment result is obtained, and the container deployment result is managed.

[0288] In a possible implementation, the container deployment unit is further used to: receive a first request to deploy a containerized application between clouds, and / or receive a second request to update or delete a containerized application deployed between clouds; wherein the first request carries at least: resources required for the container by the application to be deployed and deployment constraints of the application to be deployed, wherein the deployment constraints of the application to be deployed include the total number of containers and container scheduling policy items of the application to be deployed.

[0289] In a possible implementation manner, the container deployment unit is further used to:

[0290] In response to the data synchronization request, the application data and / or application deployment information is synchronized with the new primary cloud service provider and / or the newly added secondary cloud service provider.

[0291] In a possible implementation manner, the device is further used for:

[0292] After detecting an access request from a cloud user to an application, a load balancing address of the application is allocated to the cloud user.

[0293] For descriptions of the processing flow of each module in the device and the interaction flow between each module, reference may be made to the relevant descriptions in the above method embodiment, which will not be described in detail here.

[0294] Corresponds to Figure 1 In the cloud container management method, the embodiment of the present disclosure also provides an electronic device 800, such as Figure 8 FIG. 8 is a schematic diagram of the structure of an electronic device 800 provided in an embodiment of the present disclosure, including:

[0295] Processor 81, memory 82, and bus 83; memory 82 is used to store execution instructions, including internal memory 821 and external memory 822; the internal memory 821 is also called internal memory, which is used to temporarily store the operation data in the processor 81 and the data exchanged with the external memory 822 such as a hard disk. The processor 81 exchanges data with the external memory 822 through the internal memory 821. When the electronic device 800 is running, the processor 81 communicates with the memory 82 through the bus 83, so that the processor 81 executes the following instructions:

[0296] After obtaining the status update of the cloud service provider from the interface service, determine the mode role of the cloud service provider;

[0297] Perform deployment constraint management according to the mode role switching strategy and the resource situation of the cloud service provider;

[0298] The cloud service provider is managed for configuration changes according to the deployment constraint management, and the containerized application in the container of the cloud service provider is managed for deployment, application access management and application data management.

[0299] The present disclosure also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the cloud container management method described in the above method embodiment are executed. The storage medium may be a volatile or non-volatile computer-readable storage medium.

[0300] The embodiments of the present disclosure also provide a computer program product, which carries a program code. The instructions included in the program code can be used to execute the steps of the cloud container management method described in the above method embodiment. For details, please refer to the above method embodiment, which will not be repeated here.

[0301] The computer program product may be implemented in hardware, software or a combination thereof. In one optional embodiment, the computer program product is implemented as a computer storage medium. In another optional embodiment, the computer program product is implemented as a software product, such as a software development kit (SDK).

[0302] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, the specific working process of the system and device described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here. In the several embodiments provided in the present disclosure, it should be understood that the disclosed system, device and method can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of the device or unit can be electrical, mechanical or other forms.

[0303] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0304] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0305] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present disclosure, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0306] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present disclosure, which are used to illustrate the technical solutions of the present disclosure, rather than to limit them. The protection scope of the present disclosure is not limited thereto. Although the present disclosure is described in detail with reference to the above-described embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-described embodiments within the technical scope disclosed in the present disclosure, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure, and should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

1. A cloud container management system, characterized in that: include: Inter-cloud interaction management and inter-cloud containerized application management; The inter-cloud interaction management is used to determine the mode role of the cloud service provider after obtaining the status update of the cloud service provider from the interface service; Performing deployment constraint management according to the mode role switching strategy and the resource situation of the cloud service provider; and performing configuration change management on the cloud service provider according to the deployment constraint management; The inter-cloud containerized application management is used to perform deployment management, application access and application data management on the containerized applications in the cloud service provider.

2. The system according to claim 1, characterized in that The constraint management is deployed in the inter-cloud interaction management to: In the case where the status update indicates that the primary cloud service provider exits, a new primary cloud service provider is determined according to the mode role switching strategy; wherein the mode role switching strategy includes a role switching mechanism in different modes; The deployment constraints are updated according to the new primary cloud service provider.

3. The system according to claim 2, characterized in that The mode of the cloud service provider is a point-to-point mode; the mode role switching strategy is used to: Determining a first slave cloud service provider corresponding to the master cloud service provider; The first slave cloud service provider is determined as the new master cloud service provider.

4. The system according to claim 2, characterized in that The mode of the cloud service provider is the intermediary mode; the mode role switching strategy is used to: Determine a second slave cloud service provider that has configured an interface to communicate with the master cloud service provider; A cloud service provider whose resources are in an idle state is determined among the second slave cloud service providers as the new master cloud service provider.

5. The system according to claim 2, characterized in that The deployment constraints include at least: the mode role of the current cloud service provider, the mode role switching strategy, the total quota of containers required for application deployment, container service dependencies, and container scheduling strategy items.

6. The system according to claim 5, characterized in that The mode role switching strategy at least includes: a mechanism for re-electing the master cloud service provider when the master and slave cloud service providers change under different cloud service provider mode roles; wherein, when the cloud service provider mode is point-to-point mode, the mechanism is that if the master cloud service provider goes offline, the slave cloud service provider that is interconnected with the configured interface is switched to the master cloud service provider; when the cloud service provider mode is intermediary mode, the mechanism is that if the master cloud service provider goes offline, the slave service provider that is interconnected with the configured interface is automatically selected as the master service provider in a resource idleness priority manner from the slave service providers that are interconnected with the configured interface.

7. The system according to claim 1, characterized in that Configuration change management in the inter-cloud interaction management is used to: According to the deployment constraint management, update at least one of the following resource configuration information of the cloud service provider: the mode role of the corresponding cloud service provider, the communication interface configuration between the corresponding cloud service providers, and the access address of the container application synchronized to the new primary cloud service provider.

8. The system according to claim 1, characterized in that Inter-cloud resource management in the system is used to schedule and transmit the overall resource status of the container in the cloud service provider to the inter-cloud container; The inter-cloud container scheduling is used to schedule inter-cloud containers in the cloud service provider according to the deployment constraint management and the overall resource status to obtain a container scheduling result.

9. The system according to claim 8, characterized in that The inter-cloud interaction management is used to issue container deployment tasks to a single cloud container management function or other cloud service providers and obtain container deployment results when it is determined that the container deployment conditions are met; The application deployment management in the inter-cloud containerized application management is used to obtain the container deployment results synchronized by the inter-cloud interactive management and manage the container deployment results.

10. The system according to claim 9, characterized in that The application deployment management is used to: Receive a first request to deploy a containerized application between clouds, and / or receive a second request to update or delete a containerized application deployed between clouds; wherein the first request carries at least: resources required for the container by the application to be deployed and deployment constraints of the application to be deployed, wherein the deployment constraints of the application to be deployed include the total number of containers and container scheduling policy items of the application to be deployed.

11. The system according to claim 1, characterized in that The application data management in the inter-cloud containerized application management is used to: In response to the data synchronization request, the application data and / or application deployment information is synchronized with the new primary cloud service provider and / or the newly added secondary cloud service provider.

12. The system according to claim 1, characterized in that The application access management in the inter-cloud containerized application management is used to: After detecting an access request from a cloud user to an application, a load balancing address of the application is allocated to the cloud user.

13. A method for managing containers between clouds, characterized in that: Applied to the cloud container management system according to any one of claims 1 to 11, the method comprising: After obtaining the status update of the cloud service provider from the interface service, determine the mode role of the cloud service provider; Perform deployment constraint management according to the mode role switching strategy and the resource situation of the cloud service provider; The cloud service provider is managed for configuration changes according to the deployment constraint management, and the containerized application in the container of the cloud service provider is managed for deployment, application access management and application data management.

14. The method according to claim 13, characterized in that The deployment constraint management is performed according to the mode role switching strategy and the resource situation of the cloud service provider, including: In the case where the status update indicates that the primary cloud service provider exits, a new primary cloud service provider is determined according to the mode role switching strategy; wherein the mode role switching strategy includes a role switching mechanism in different modes; The deployment constraints are updated according to the new primary cloud service provider.

15. The method according to claim 14, characterized in that The mode of the cloud service provider is a point-to-point mode; The determining a new primary cloud service provider according to the mode role switching strategy includes: Determining a first slave cloud service provider corresponding to the master cloud service provider; The first slave cloud service provider is determined as the new master cloud service provider.

16. The method according to claim 14, characterized in that The model of the cloud service provider is an intermediary model; The determining a new primary cloud service provider according to the mode role switching strategy includes: Determine a second slave cloud service provider that has configured an interface to communicate with the master cloud service provider; A cloud service provider whose resources are in an idle state is determined among the second slave cloud service providers as the new master cloud service provider.

17. The method according to claim 14, characterized in that The deployment constraints include at least: the mode role of the current cloud service provider, the mode role switching strategy, the total quota of containers required for application deployment, container service dependencies, and container scheduling strategy items.

18. The method according to claim 13, characterized in that The performing configuration change management on the cloud service provider according to the deployment constraint management includes: According to the deployment constraint management, update at least one of the following resource configuration information of the cloud service provider: the mode role of the corresponding cloud service provider, the communication interface configuration between the corresponding cloud service providers, and the access address of the container application synchronized to the new primary cloud service provider.

19. The method according to claim 13, characterized in that The method further comprises: Determine the overall resource status of the container in the cloud service provider; Scheduling inter-cloud containers according to the deployment constraint management and the overall resource status to obtain a container scheduling result; When it is determined that the container deployment condition is met, the containerized application is deployed according to the container scheduling result, the container deployment result is obtained, and the container deployment result is managed.

20. The method according to claim 13, characterized in that The deploying and managing containerized applications of containers in the cloud service provider includes: Receive a first request to deploy a containerized application between clouds, and / or receive a second request to update or delete a containerized application deployed between clouds; wherein the first request carries at least: resources required for the container by the application to be deployed and deployment constraints of the application to be deployed, wherein the deployment constraints of the application to be deployed include the total number of containers and container scheduling policy items of the application to be deployed.

21. The method according to claim 13, characterized in that The performing application data management on the container in the cloud service provider includes: In response to the data synchronization request, the application data and / or application deployment information is synchronized with the new primary cloud service provider and / or the newly added secondary cloud service provider.

22. The method according to claim 13, characterized in that The performing application access management on the container in the cloud service provider includes: After detecting an access request from a cloud user to an application, a load balancing address of the application is allocated to the cloud user.

23. A cloud container management device, characterized in that: The device comprises: A determination unit, configured to determine the mode role of the cloud service provider after obtaining a status update of the cloud service provider from the interface service; An updating unit, used to perform deployment constraint management according to the mode role switching strategy and the resource conditions of the cloud service provider; The container deployment unit is used to manage the configuration changes of the cloud service provider according to the deployment constraint management, and to perform deployment management, application access management and application data management on the containerized applications in the containers of the cloud service provider.

24. An electronic device, characterized in that: include: A processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate via the bus, and when the machine-readable instructions are executed by the processor, the steps of the cloud container management method as described in any one of claims 13 to 22 are performed.

25. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed by a processor, executes the steps of the cloud container management method as described in any one of claims 13 to 22.

26. A computer program product, characterized in that The computer program product is stored in a storage medium, and the program product is executed by at least one processor to implement the steps of the inter-cloud container management method as described in any one of claims 13 to 22.

Images