Container application service configuration method and device based on multi-cloud environment and readable medium

Abstract

The invention relates to a container application service configuration method and device based on a multi-cloud environment and a readable medium. The invention provides a container application service configuration method based on a multi-cloud environment, and the method comprises the steps: selecting a source cloud environment in a target cloud environment, and enabling the source cloud environment to comprise a to-be-copied application service; obtaining configuration information of the to-be-copied application service from the source cloud environment; configuring a target application service according to the configuration information; and creating the target application service in the target cloud environment. According to the container application service configuration method, the source cloud environment is selected from the target cloud environment, the configuration information of the to-be-copied application service is acquired from the source cloud environment, the target application service is configured according to the configuration information, and the target application service is created in the target cloud environment. The application service can be freely copied among different environments, and the problem that manpower and material resources are wasted due to the fact that the application service needs to be repeatedly configured and repeatedly created is solved.

Description

Technical Field

[0001] This application mainly relates to the field of cloud computing, and specifically relates to a method, device, and computer-readable medium for configuring container application services based on a multi-cloud environment. Background Art

[0002] In recent years, cloud computing has been developing vigorously. Enterprises of all sizes have started to migrate their applications to the cloud and use cloud computing to provide reliable and stable computing services for their applications. Larger companies have even started to build or have already built private clouds to provide reliable cloud computing services for hundreds or thousands of applications within the enterprise. In the construction system of private clouds, the industry generally adopts a construction plan of two data centers in different locations and three centers in total. The involved clouds are the development and test cloud for development and testing, the production cloud for production, and the disaster recovery cloud for off-site disaster recovery. Therefore, a multi-cloud environment has emerged, and the same set of systems needs to be deployed in the multi-cloud environment. In addition, the development and test cloud is further divided into a development environment, a test environment, and a stress testing environment according to functional areas, and the disaster recovery cloud is divided into a pre-production environment and an emergency production environment according to functional areas.

[0003] To deploy a standard container application service to the production cloud, the following steps are usually required: First, a development environment is set up in the functional area of the development and test cloud for developers to carry out development and debugging work. Then, a test environment is also set up in the functional area of the development and test cloud for testers to conduct functional tests. After that, a production environment is set up on the production cloud to provide official external services. Finally, a disaster recovery environment is set up on the disaster recovery cloud as a guarantee for emergency handling of the production environment. In addition, depending on the importance of the application, a stress testing environment and a pre-production environment may also need to be set up.

[0004] Taking the well-known Alibaba Cloud in the industry as an example, the process of migrating an application to the cloud is roughly as follows: First, create an application group (i.e., application system), then create an application module, then create an application service, then create basic resources (such as Persistent Volume Claim (PVC), Server Load Balancer (SLB), configuration items, secret dictionaries), then configure the application service (including pod template configuration, replica configuration, access configuration, deployment and scheduling configuration, etc.), and finally generate an available version to complete the configuration. In the whole configuration process, a complex application may involve hundreds of configuration points. For those who are familiar with Kubernetes (K8s) containers, it takes about half a day to one day to complete the configuration; while for those who are not proficient, it may take one day to several days, and the process is both time-consuming and cumbersome.

[0005] An important application service needs to be deployed to three clouds: the development and test cloud, the production cloud, and the disaster recovery cloud. The operation needs to be repeated at least 3 times and may be repeated up to 6 times, which greatly wastes manpower and material resources. Among them, the operations that need to be repeated include: repeatedly creating application modules, repeatedly creating application services, repeatedly creating configuration items, repeatedly creating configuration groups, repeatedly setting replica information, repeatedly setting POD template configurations, repeatedly setting access control configurations, and repeatedly setting deployment scheduling configurations. Summary of the Invention

[0006] In view of the above problems, the present application provides a method for configuring container application services based on a multi-cloud environment to solve the problem of waste of manpower and material resources caused by repeated configuration and repeated creation of application services.

[0007] A method for configuring container application services based on a multi-cloud environment provided by the present application includes: selecting a source cloud environment in a target cloud environment, where the source cloud environment includes an application service to be replicated; obtaining configuration information of the application service to be replicated from the source cloud environment; configuring a target application service according to the configuration information; and creating the target application service in the target cloud environment.

[0008] In an embodiment of the present application, configuring the target application service according to the configuration information includes: configuring application modules, where the application modules include multiple target application services with different functions; and configuring objects to be configured for each of the target application services, where the objects to be configured include any of replica configuration, pod template configuration, access control configuration, and deployment scheduling configuration.

[0009] In an embodiment of the present application, after configuring the target application service according to the configuration information, it further includes: in response to the result of configuring the target application service being successful, generating an import order, where the import order includes information of the objects to be configured; and in response to the result of configuring the target application service being failed, abandoning the configuration of the target application service, or re-executing the step of configuring the target application service according to the configuration information.

[0010] In an embodiment of the present application, creating the target application service in the target cloud environment includes: creating the target application service according to the import order and the configuration information, including any of creating application modules, creating application services, creating confidential fields, creating configuration items, creating PVC, creating SLB, and issuing combined configurations.

[0011] In an embodiment of the present application, creating the target application service in the target cloud environment further includes: obtaining the import result of the import order; and in response to the import result being a failure, generating a reason for the failure, modifying the configuration service according to the reason for the failure, or re-executing the import order.

[0012] Before generating the import order in an embodiment of the present application, it further includes: marking the target application service as configured.

[0013] After selecting the source cloud environment in the target cloud environment in an embodiment of the present application, it further includes: selecting the functional area where the application service to be replicated is located; selecting the source system where the application service to be replicated is located; and selecting the application service to be replicated.

[0014] In an embodiment of the present application, API interfaces are respectively set in multiple cloud environments, and the API interfaces are used to enable mutual access between the multiple cloud environments, where the multiple cloud environments include the target cloud environment and the source cloud environment.

[0015] The present application also provides a container application service configuration device based on a multi-cloud environment, including: a memory for storing instructions executable by a processor; and a processor for executing the instructions to implement the above-mentioned application service configuration method based on a multi-cloud environment.

[0016] The present application also provides a computer-readable medium storing computer program code, and the computer program code implements the above-mentioned container application service configuration method based on a multi-cloud environment when executed by a processor.

[0017] The container application service configuration method of the present application selects a source cloud environment in the target cloud environment, obtains the configuration information of the application service to be replicated from the source cloud environment, configures the target application service according to the configuration information, and creates the target application service in the target cloud environment, enabling the free replication of application services between different environments, and solving the problem of waste of manpower and material resources caused by repeated configuration and repeated creation of application services. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] To make the above objects, features, and advantages of the present application more obvious and understandable, the following detailed description of the specific embodiments of the present application is provided in conjunction with the accompanying drawings, where:

[0019] Figure 1 is a flowchart of the container application service configuration method according to an embodiment of the present application;

[0020] Figure 2 is a flowchart of the container application service configuration method according to another embodiment of the present application;

[0021] Figure 3 is a flowchart of a container application service configuration method according to another embodiment of the present application; and

[0022] Figure 4 is a system block diagram of a container application service configuration device according to an embodiment of the present application. Detailed Embodiments

[0023] To make the above objects, features, and advantages of the present application more obvious and understandable, the following will describe the detailed embodiments of the present application in conjunction with the accompanying drawings.

[0024] In the following description, many specific details are set forth in order to fully understand the present application. However, the present application may also be implemented in other ways different from those described herein. Therefore, the present application is not limited by the specific embodiments disclosed below.

[0025] As shown in the present application, unless the context clearly indicates an exception, words such as "a", "an", "one", and / or "the" are not specifically singular and may also include the plural. Generally speaking, the terms "including" and "comprising" only indicate the inclusion of the clearly identified steps and elements, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.

[0026] The container application service configuration method proposed by the present application is applicable to the application service configuration in a multi-cloud environment, and can realize the one-key replication of application services between different functional areas of the same cloud and between different clouds. For example, a development environment is built in the functional area of the development and test cloud, and the one-key import function is enabled in the test environment of the development and test cloud to import the application service in the development environment into the test environment. The one-key import function is enabled in the production cloud to import the service in the test environment into the production environment in one key. In the disaster recovery cloud, the application service in the production cloud is imported into the emergency production environment of the disaster recovery cloud in one key. The above import process can be configured in combination with its own business logic and imported arbitrarily. In addition, this process only requires the user to perform one configuration, and only extremely simple work needs to be done subsequently to realize the free replication of application services between different environments, making the application service go to the cloud from multiple repeated replications to one configuration, greatly improving the efficiency.

[0027] Next, the container application service configuration method of the present application will be described in conjunction with the accompanying drawings.

[0028] Figure 1 shows a flowchart of a container application service configuration method 10 according to an embodiment of the present application. As Figure 1 shown, the container application service configuration method 10 proposed by the present application includes:

[0029] Step S1: Select a source cloud environment in the target cloud environment, where the source cloud environment includes the application service to be replicated;

[0030] Step S2: Obtain the configuration information of the application service to be replicated from the source cloud environment;

[0031] Step S3: Configure the target application service according to the configuration information; and

[0032] Step S4: Create the target application service in the target cloud environment.

[0033] The container application service configuration method of the present application solves the problem of waste of manpower and material resources caused by repeated configuration and repeated creation of application services by selecting the source cloud environment in the target cloud environment, obtaining the configuration information of the application service to be replicated from the source cloud environment, configuring the target application service according to the configuration information, and creating the target application service in the target cloud environment, enabling the free replication of application services between different environments.

[0034] In some embodiments, for selecting the source cloud environment in the target cloud environment in Step S1, one can first log in to the target cloud environment, click Import in the target cloud environment, and then select the source cloud environment by dropping down.

[0035] It should be understood that in some embodiments, when the cloud where the target cloud environment is located includes multiple different functional areas, Step S1 further includes clicking Import in the functional area where the application service to be imported is located. For example, in the development environment of the development and test cloud, click Import and select the source cloud environment.

[0036] In some embodiments, the target cloud environment and the source cloud environment can be in different clouds. For example, the target cloud environment is in the production cloud and the source cloud environment is in the development and test cloud. In some embodiments, the target cloud environment and the source cloud environment can be in the same cloud. For example, the target cloud environment is the test environment of the development and test cloud, and the source cloud environment is the development environment of the development and test cloud; in this case, both the target cloud environment and the source cloud environment are in the development and test cloud.

[0037] In some embodiments, after selecting the source cloud environment in the target cloud environment in Step S1, it further includes: selecting the functional area where the application service to be replicated is located; selecting the source system where the application service to be replicated is located; and selecting the application service to be replicated.

[0038] It should be understood that in some embodiments, the cloud where the source cloud environment is located includes at least one functional area, the functional area includes at least one source system, and the source system includes at least one application service. In some embodiments, in the cloud where the source cloud environment is located, one can click on the functional area corresponding to the source cloud environment, then select the source system where the application service to be replicated is located to obtain the authorized system information. The selected source system will list all subordinate application services, and then select the application service to be replicated.

[0039] After selecting the source cloud environment in step S1, step S2 is performed.

[0040] In some embodiments, the configuration information of the application service to be copied obtained in step S2 is stored in the cloud computing management. In some embodiments, after the application service of the source cloud environment is containerized, the configuration information corresponding to the application service is stored in the database.

[0041] In some embodiments, the container orchestration tool includes: Docker Swarm and K8s. Preferably, the container orchestration tool is K8s.

[0042] In some embodiments, the configuration information of the application service to be copied can be obtained from the source cloud environment in step S2 with the help of an API interface. In some embodiments, API interfaces are respectively set in multiple cloud environments, and the API interfaces are used to achieve mutual access between multiple cloud environments, wherein the multiple cloud environments include a target cloud environment and a source cloud environment. The container application service configuration method of the present application achieves interconnection between the target cloud environment and the source cloud environment by respectively setting API interfaces in multiple cloud environments, thereby achieving one-click replication of application services between different functional areas of the same cloud and between different clouds.

[0043] After obtaining the configuration information of the application service to be copied in step S2, step S3 is executed.

[0044] In some embodiments, configuring the target application service according to the configuration information in step S3 includes: configuring an application module, the application module includes multiple target application services with different functions; and configuring an object to be configured for each target application service, the object to be configured includes: any one of replica configuration, pod template configuration, access control configuration, and deployment scheduling configuration.

[0045] In some embodiments, configuring the application module in step S3 includes grouping application services with similar functions into one group.

[0046] In some embodiments, configuring the target application service in step S3 also includes selecting a target cluster, configuring any item of the SLB, namespace, data volume, and network of the target application service. In some embodiments, the user can add or delete the configuration of the application service according to actual needs.

[0047] In some embodiments, based on API mutual access and container orchestration tools, configuring the target application service according to the configuration information in step S3 can be configured as: the system automatically completes the configuration of the target application service. For example, when the user clicks on "Configure" to enter the configuration page, after the user confirms the correctness of the automatically assembled parameters, the copied configuration information can be sent to K8s through the API. K8s automatically pulls the configuration information of the application service to be copied from the source cloud environment and automatically configures the target application service information according to the standard assembly parameters.

[0048] The container application service configuration method of the present application is based on API mutual access and container orchestration tools, obtains the configuration information of the application service to be copied from the source cloud environment, imports the configuration information of the containerized application service to be copied into the target cloud environment, realizes the replication of the application service between the target cloud environment and the source cloud environment, and completes the configuration of the target application service in the target cloud environment. In addition, the container application service configuration method of the present application is based on API mutual access and container orchestration tools, and can realize the automatic configuration of the target application service by the system, avoiding repeated configuration by the user.

[0049] In some embodiments, after configuring the target application service according to the configuration information, it further includes: in response to the result of configuring the target application service being successful configuration, generating an import order, where the import order includes information about the object to be configured; and in response to the result of configuring the target application service being failed configuration, abandoning the configuration of the target application service, or re-executing the configuration of the target application service according to the configuration information.

[0050] In some embodiments, after the configuration of the target application service in step S3 is successfully configured, an import order is generated. The import order includes past events, the execution entity, and the specific configuration done in step S3. By generating the import order, the convenience of tracking or retrying subsequent tasks is improved.

[0051] In some embodiments, before generating the import order, it further includes: marking the target application service as configured. By marking the target application service as configured, it is possible to avoid repeated configuration of the target application service and also avoid forgetting to configure.

[0052] In some embodiments, after the user confirms that the configuration is completed, the target application service is marked as configured. At this time, the configuration result of the target application service meets the expectations. When the result of configuring the target application service is failed configuration, the target application service will not be marked as configured. Since the configuration result does not meet the user's expectations, generating an import order is not allowed.

[0053] After configuring the target application service according to the configuration information in step S3, step S4 is executed.

[0054] In some embodiments, creating the target application service in the target cloud environment in step S4 includes: creating the target application service according to the imported order and configuration information, including any one of creating application modules, creating application services, creating confidential fields, creating configuration items, creating PVCs, creating SLBs, and issuing combined configurations.

[0055] In some embodiments, according to the imported order and configuration information, the system can automatically create the target application service. In some embodiments, the imported order includes an order number, and the order number is associated with the configuration information. Taking K8s as an example, the copied configuration information can be sent to K8s through the API. After that, K8s assembles the parameters according to the standard and automatically completes the creation of the target application service according to the imported order and configuration information.

[0056] Automatically creating the target application service through the imported order and configuration information further solves the problem in the prior art that creating items such as application modules, application services, and configuration items needs to be repeated in the application service configuration, resulting in waste of manpower.

[0057] In some embodiments, creating the target application service in the target cloud environment further includes: obtaining the import result of the imported order; and in response to the import result being a failure, generating a failure reason, modifying the configuration service according to the failure reason, or re-executing the imported order. In some embodiments, the creation result of each step of creating the application service will be tracked and recorded in the imported order. When the import result of the imported order is successful, the application service will be displayed in the target environment without the user having to create it. When any step of the imported order fails, the import result will be a failure. After the failure, the failure reason can be viewed in the imported order. The user can choose to modify the configuration service according to the failure reason or re-execute the imported order.

[0058] Next, it will be combined with Figure 2 and Figure 3 to illustrate the implementation process of the container application service configuration method of this application.

[0059] Figure 2 shows the flowchart of the container application service configuration method 20 according to another embodiment of this application. As Figure 2 shown, the container application service configuration method 20 of this application includes:

[0060] Step S21: Click to import into the target environment;

[0061] Step S22: Select the source cloud environment;

[0062] Step S23: Query the application services that can be imported;

[0063] Step S24: Configure the application service;

[0064] Step S25: Import; and

[0065] Step S26: Generate a version.

[0066] In Figure 2 the illustrated embodiment, in Step S21, the target environment is equivalent to the target cloud environment described above. Enter the target environment, and click Import in the target environment to enter Step S22. Steps S22 - S23 are equivalent to Step S1 described above. In Step S22, the source environment is equivalent to the source cloud environment described above. Then Step S23 is executed. Step S23 includes: selecting the functional area where the application service to be replicated is located and the source system where the application service to be replicated is located, and then querying the importable application service, that is, the configuration information of the application service to be replicated in Step S1. Then Step S24 is executed. Step S24 is equivalent to Steps S2 and S3 described above. In Step S24, the importable application service in Step S23 is obtained, and the target application service is configured. Then Step S25 is executed. Step S25 is equivalent to Step S4 described above. The import in Step S25 means: creating the target application service in the target cloud environment according to the importable application service in Step S23 and the configuration in Step S24. Then Step S26 is executed. Based on the configuration in Step S24 and the import in Step S25, a version is generated for subsequent use such as application release.

[0067] Figure 3 shows a flowchart of a container application service configuration method 300 according to another embodiment of the present application. As Figure 3 shown, the container application service configuration method 300 of the present application includes:

[0068] Step S301: Click Import in the target environment. Step S301 is equivalent to Step S21. Among them, the target environment is equivalent to the target cloud environment described above. Enter the target environment, and after clicking Import in the target environment, enter Step S302.

[0069] Step S302: Select the source environment. Among them, the source environment is equivalent to the source cloud environment described above. Step S302 is equivalent to Step S22 described above.

[0070] Step S303: Select the functional area.

[0071] Step S304: Select the source system.

[0072] Step S305: Select the application service.

[0073] The above Steps 301 - Step S305 are equivalent to Step S1 described above. The above Steps S302 - S305 are equivalent to Step S23 described above.

[0074] Step S306: Module configuration. The module configuration is the configuration application module described above.

[0075] Step S307: Service configuration. The service configuration is the configured target application service described above.

[0076] Step S308: Replica configuration.

[0077] Step S309: Pod template configuration.

[0078] Step S310: Access control configuration.

[0079] Step S311: Deployment scheduling configuration.

[0080] The above steps S308 to S311 are equivalent to step S3 or step S24 described above. The execution order of the above steps S308 to S311 is not sequential. Steps S308 to S311 are the specific configurations for the service in step S307.

[0081] Step S312: Configuration check. When the configuration fails or is not completed, the user can choose to execute step S313 or return to step S301. When the configuration is successful, execute step S314.

[0082] Step S313: Abandon import.

[0083] Step S314: Mark the service as configured.

[0084] Step S315: Generate an import order.

[0085] Step S316: Execution. Among them, execution refers to creating a target application service according to the import order, including steps S317 to S324. Execution also includes judging the execution result. When any one of steps S317 to S324 fails, the execution result will be a failure. When the execution result is a failure, execute step S325.

[0086] After step S316 is executed, it enters the execution process, and steps S317 to S324 are executed.

[0087] Step S317: Create an application module.

[0088] Step S318: Create an application service.

[0089] Step S319: Create a confidential field.

[0090] Step S320: Create a configuration item.

[0091] Step S321: Create a PVC.

[0092] Step S322: Create an SLB.

[0093] Among them, the execution order of steps S319 to S323 is not in a specific sequence.

[0094] Step S323: Distribute the combined configuration. This step means stringing together the previously separately created security fields, configuration items, PVCs, SLBs, etc. to form a large YAML file.

[0095] The above steps S317 to S323 are equivalent to steps S4 or S25 described above.

[0096] Step S324: Generate a version. Step S324 is equivalent to step S26 described above.

[0097] Step S325: Check the reason for execution failure. In step 325, the user can choose to modify according to the failure reason and return to step S307 or directly return to step S316.

[0098] In some embodiments, in step S301, the user clicks to import in the production cloud environment; then step S302 is executed, and the development and test cloud is selected by dropping down in the source cloud environment. Then step S303 is executed, click on the source function area to obtain the function area and select the function area as test. Then step S304 is executed, the user clicks on the source system to obtain the authorized system information, and all subordinate application services are listed according to the selected system. Then step S305 is executed, select the target application service, click on configuration to enter the automatic configuration page. Then steps S308 to S311 are executed, and the system automatically configures the target application service. The user selects the target cluster and namespace and confirms whether the automatically assembled parameters are correct, and clicks OK to complete the configuration. Then step S312 is executed. When the configuration fails or is not completed, the user selects to execute step S313 or return to step S301; when the configuration is completed, step 314 is executed to mark the target application service as configured, and then step S315 is executed to generate an import order. Then step S316 is executed, the user clicks to execute, and the system sequentially executes according to the import order in steps S317 to S324. If the execution is successful, the application service will be displayed in the target environment, and an available version will be provided for subsequent application releases, etc. If the execution fails, it will stop at the failed step node and give the specific reason. The user can return to step S307 to reconfigure the target application service according to the reason, or directly re-execute step S316.

[0099] The container application service configuration method of the present application selects a source cloud environment in a target cloud environment, obtains the configuration information of the application service to be replicated from the source cloud environment, configures the target application service according to the configuration information, and creates the target application service in the target cloud environment, enabling the free replication of application services between different environments, and solving the problem of waste of human and material resources caused by repeated configuration and repeated creation of application services; based on API mutual access and container orchestration tools, obtains the configuration information of the application service to be replicated from the source cloud environment, and imports the configuration information of the containerized application service to be replicated into the target cloud environment, realizing the replication of application services between the target cloud environment and the source cloud environment, and completing the configuration of the target application service in the target cloud environment; automatically creates the target application service by importing orders and configuration information, further solving the problem of wasting manpower caused by the need to repeatedly create multiple items such as application modules, application services, and configuration items in the application service configuration in the prior art. Compared with the prior art, the container application service configuration method of the present application also has the following advantages: flexible and scalable, freely combinable and replicable between environments, and the replicated services can be added or deleted according to the situation; improving configuration consistency, maximizing the configuration same between cloud environments, and facilitating error troubleshooting; reducing repetitive work and improving efficiency.

[0100] The present application also includes a container application service configuration device, including a memory and a processor. Among them, the memory is used to store instructions executable by the processor; the processor is used to execute the instructions to implement the above-mentioned container application service configuration method.

[0101] Figure 4 It is the system block diagram of the container application service configuration device according to an embodiment of the present application. Refer to Figure 4As shown, the container application service configuration device 400 may include an internal communication bus 401, a processor 402, a read-only memory (ROM) 403, a random access memory (RAM) 404, and a communication port 405. When the application is on a personal computer, the container application service configuration device 400 may further include a hard disk 406. The internal communication bus 401 can enable data communication between components of the container application service configuration device 400. The processor 402 can make judgments and issue prompts. In some embodiments, the processor 402 may be composed of one or more processors. The communication port 405 can enable data communication between the container application service configuration device 400 and the outside. In some embodiments, the container application service configuration device 400 can send and receive information and data from a network through the communication port 405. The container application service configuration device 400 may further include different forms of program storage units and data storage units, such as the hard disk 406, the read-only memory (ROM) 403, and the random access memory (RAM) 404, which can store various data files used for computer processing and / or communication, as well as possible program instructions executed by the processor 402. The processor executes these instructions to implement the main part of the method. The result processed by the processor is transmitted to the user device through the communication port and displayed on the user interface.

[0102] The above-described container application service configuration method can be implemented as a computer program, stored in the hard disk 406, and loaded into the processor 402 for execution to implement the container application service configuration method of this application.

[0103] This application also includes a computer-readable medium storing computer program code, which, when executed by a processor, implements the container application service configuration method described above.

[0104] When the container application service configuration method is implemented as a computer program, it can also be stored in a computer-readable storage medium as an article of manufacture. For example, the computer-readable storage medium may include, but is not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs), digital versatile disks (DVDs)), smart cards, and flash memory devices (e.g., electrically erasable programmable read-only memories (EPROMs), cards, sticks, key drives). In addition, the various storage media described herein can represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media (and / or storage media) that can store, contain, and / or carry code and / or instructions and / or data.

[0105] It should be understood that the embodiments described above are merely illustrative. The embodiments described herein can be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the processor can be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, and / or other electronic units designed to perform the functions described herein, or a combination thereof.

[0106] Some aspects of the present application can be executed entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. The above hardware or software can be referred to as a "block", "module", "engine", "unit", "component", or "system". The processor can be one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DAPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or a combination thereof. In addition, aspects of the present application may be embodied as a computer product located in one or more computer readable media, which includes computer readable program code. For example, the computer readable media may include, but is not limited to, magnetic storage devices (such as hard disks, floppy disks, magnetic tapes...), optical disks (such as compact disks CD, digital versatile disks DVD...), smart cards, and flash memory devices (such as cards, sticks, key drives...).

[0107] The computer readable media may contain a propagated data signal having computer program code therein, for example, on a baseband or as part of a carrier wave. The propagated signal may have various manifestations, including electromagnetic form, optical form, etc., or a suitable combination thereof. The computer readable media can be any computer readable media other than a computer readable storage media, which can be connected to an instruction execution system, apparatus, or device to implement communication, propagation, or transmission for use of the program. The program code located on the computer readable media can be propagated through any suitable media, including radio, cable, fiber optic cable, radio frequency signal, or similar media, or any combination of the above media.

[0108] The basic concepts have been described above. Obviously, for those skilled in the art, the above invention disclosure is only an example and does not constitute a limitation to the present application. Although not explicitly stated here, those skilled in the art may make various modifications, improvements, and corrections to the present application. Such modifications, improvements, and corrections are proposed in the present application, so such modifications, improvements, and corrections still fall within the spirit and scope of the exemplary embodiments of the present application.

[0109] Meanwhile, specific terms are used in this application to describe the embodiments of this application. For example, "one embodiment", "an embodiment", and / or "some embodiments" mean a certain feature, structure, or characteristic related to at least one embodiment of this application. Therefore, it should be emphasized and noted that the "one embodiment" or "an embodiment" or "an alternative embodiment" mentioned twice or more at different positions in this specification does not necessarily refer to the same embodiment. In addition, certain features, structures, or characteristics in one or more embodiments of this application can be appropriately combined.

[0110] In some embodiments, numbers are used to describe the components and the quantity of attributes. It should be understood that such numbers used to describe the embodiments are, in some examples, modified by the modifiers "about", "approximately", or "substantially". Unless otherwise stated, "about", "approximately", or "substantially" indicate that the said numbers allow a variation of ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification are approximate values, and these approximate values can change according to the required characteristics of individual embodiments. In some embodiments, the numerical parameters should consider the specified significant digits and adopt the method of retaining the general number of digits. Although the numerical ranges and parameters used to confirm the breadth of the scope in some embodiments of this application are approximate values, in specific embodiments, such numerical settings are made as precise as possible within the feasible range.

Claims

1. A method for configuring container application services based on a multi-cloud environment, comprising: Selecting a source cloud environment in a target cloud environment, wherein the source cloud environment includes application services to be replicated; Obtaining configuration information of the application services to be replicated from the source cloud environment; Configuring target application services according to the configuration information; and Creating the target application services in the target cloud environment.

2. The container application service configuration method according to claim 1, characterized in that, The configuring target application services according to the configuration information includes: Configuring application modules, where the application modules include multiple target application services with different functions; and Configuring objects to be configured for each of the target application services, where the objects to be configured include any one of replica configuration, pod template configuration, access control configuration, and deployment scheduling configuration.

3. The container application service configuration method according to claim 2, wherein After the configuring target application services according to the configuration information, it further includes: In response to the result of configuring the target application services being successful, generating an import order, where the import order includes information of the objects to be configured; and In response to the result of configuring the target application services being failed, abandoning the configuration of the target application services, or re-executing the configuring target application services according to the configuration information.

4. The container application service configuration method according to claim 3, wherein The creating the target application services in the target cloud environment includes: Creating the target application services according to the import order and the configuration information, including any one of creating application modules, creating application services, creating confidential fields, creating configuration items, creating PVCs, creating SLBs, and issuing combined configurations.

5. The container application service configuration method according to claim 4, wherein, The creating the target application services in the target cloud environment further includes: Obtaining the import result of the import order; and In response to the import result being failed, generating a failure reason, modifying the configuration service according to the failure reason, or re-executing the import order.

6. The container application service configuration method according to claim 3, wherein, Before generating the import order, it further includes: marking the target application services as configured.

7. The container application service configuration method according to claim 1, characterized in that, After selecting the source cloud environment in the target cloud environment, it further includes: Selecting the functional area where the application services to be replicated are located; Selecting the source system where the application services to be replicated are located; and Selecting the application services to be replicated.

8. The method for configuring a container application service according to claim 1, wherein, Including: Setting API interfaces in multiple cloud environments respectively, where the API interfaces are used to enable mutual access between multiple cloud environments, and the multiple cloud environments include the target cloud environment and the source cloud environment.

9. A device for configuring container application services based on a multi-cloud environment, comprising: A memory for storing instructions executable by a processor; A processor for executing the instructions to implement the method for configuring application services based on a multi-cloud environment according to any one of claims 1-8.

10. A computer-readable medium storing computer program code, where the computer program code, when executed by a processor, implements a method for configuring container application services based on a multi-cloud environment according to any one of claims 1-8.

Images