A method for automatic construction and rapid integration of application services in a hybrid cloud

Abstract

The application provides a mixed cloud application service automatic construction and rapid integration method, comprising a containerized component construction module, a mixed cloud cross-domain cluster communication module and a rapid debugging module based on a container internal network; wherein the operation flow of the mixed cloud application service automatic construction and rapid integration method is as follows: S1, the containerized component construction module constructs an image in a container mode; when the required image construction is completed, the constructed environment image is run and the corresponding directory is mounted; after the construction in the container is completed, the mounted host computer; when environment migration or re-deployment is performed, the corresponding image is imported, and the image is run to complete the rapid construction. The mixed cloud application service automatic construction and rapid integration method provided by the application can avoid the influence of system environment dependent factors. When environment migration or re-deployment is performed, the corresponding image is imported, and the image is run to complete the rapid construction.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method for the automated construction and rapid integration of application services in a hybrid cloud. Background Technology

[0002] With the development of information technologies such as the Internet of Things and big data, cloud-native technologies have rapidly evolved. The Kubernetes technology system, since its inception, has continuously driven the development of the cloud-native open-source technology ecosystem. Kubernetes is Google's open-source container cluster management system. Based on container technologies such as Docker, it provides a complete set of functions for containerized applications, including deployment, operation, resource scheduling, service discovery, and dynamic scaling, facilitating the management of large-scale container clusters. However, in hybrid cloud environments, the construction and integration of application services still face many challenges. Because hybrid clouds involve both public and private clouds, and different cloud platforms have different operating systems, operating environments, and network environments, issues such as cross-operating system migration, rapid debugging under network security policy restrictions, and maintenance of cross-domain network cluster communication policies need to be addressed through technical means when building and integrating application services.

[0003] Therefore, it is necessary to provide a method for automating the construction and rapid integration of application services in hybrid clouds to solve the above-mentioned technical problems. Summary of the Invention

[0004] This invention provides a method for automated construction and rapid integration of application services in hybrid clouds, addressing the numerous challenges that still exist in the construction and integration of application services in hybrid cloud environments. Since hybrid clouds involve both public and private clouds, and different cloud platforms have different operating systems, runtime environments, and network environments, issues such as cross-operating system migration, rapid debugging under network security policy restrictions, and maintenance of cross-domain network cluster communication policies need to be addressed through technical means during the construction and integration of application services.

[0005] To address the aforementioned technical issues, the present invention provides an automated construction and rapid integration method for application services in a hybrid cloud, comprising: a containerized component construction module, a cross-domain cluster communication module in a hybrid cloud, and a rapid debugging module based on the container's internal network.

[0006] The workflow for the automated construction and rapid integration of application services in hybrid cloud is as follows:

[0007] The containerized component building module described in S1 uses containers to build images. Once the required image is built, the built environment image is run and the corresponding directory is mounted. After the image is built inside the container, it is mounted on the host machine. When the environment is migrated or redeployed, the corresponding image is imported and the image is run to complete the rapid build.

[0008] The cross-domain cluster communication module in the hybrid cloud described in S2 is used in cross-regional environments;

[0009] When a cluster needs to access clusters of nodes in other regions, network traffic will first be sent through the application server, and then through the traffic forwarding plugin to reach the unified egress server. The unified egress server is mainly used to provide unified network egress services. Using two or more unified network egress servers can realize network load balancing. The application server mainly provides business service capabilities, and business components generally run on the application server.

[0010] When application server resources are insufficient or there is a conflict between business processing resources and network resources, the unified egress server is reused. The traffic forwarding plugin will detect whether the bound unified egress server is in a normal state and select a normal and available unified egress service resource according to the configuration policy.

[0011] S23 When one of the servers goes down or resources are unavailable, network traffic can still be sent normally. When application server traffic passes through the traffic forwarding plugin, the traffic forwarding plugin mainly forwards the traffic through the internal network IP to the configured unified egress server through NAT forwarding. The firewall policy of the unified egress server is enabled for the VIP (Virtual IP) firewall policy of other regional nodes, ensuring that the VIP of other regional nodes can receive network traffic normally.

[0012] When the VIP bound to other regional nodes receives traffic, it will communicate with the internal IP of the current node server through the internal IP configured in the VIP. After the network traffic passes through the Kubernetes Services traffic load balancer, the application server can receive the network traffic accessed by other nodes.

[0013] In a hybrid cloud network environment, the rapid debugging module based on the container internal network described in S3 only allows connections to the server via bastion host Shell, Xftp, WinSCP, and VNC in the enterprise's internal security settings, and does not allow clients to access the visual application services deployed on the server by enabling firewall policies.

[0014] Preferably, the environment in which the containerized component building module builds the image is a Go environment, a Maven environment, a Node environment, or a Java environment.

[0015] Preferably, in step S3, an Ubuntu / CentOS image is built on the server using a container, and a VNC server and related visualization desktop programs are configured in the built container. After the container is started on the server, the container interface can be accessed using the VNC-5900 port provided by the bastion host. Since the network of the container and the network of the container on the host machine are interconnected, the service components can be debugged in a visual way through the browser in the container, and the interface application can be accessed, thus accelerating the completion of container building and integration debugging.

[0016] Preferably, it also includes containerized component construction methods that do not rely on the operating system, cross-domain cluster communication methods in hybrid cloud environments, and rapid debugging methods based on the container's internal network under network security policy restrictions on application service access.

[0017] Preferably, the containerized component building method that is independent of the operating system cannot determine the server's operating system before deployment in a hybrid cloud environment. Component building requires the installation of environment dependencies, and different systems require different environment versions.

[0018] Preferably, the fast communication method between cross-domain clusters in the hybrid cloud provides a unified entry strategy for multiple containers through Kubernetes service discovery and load balancing mechanisms. However, since a unified exit issue also needs to be considered in the hybrid cloud environment, and because the components are deployed in a distributed architecture, the communication needs of multiple regional cluster services require the opening of factorial firewall port rules, resulting in excessively high maintenance manpower costs and low security.

[0019] Preferably, under the network security policy restricting application service access, the rapid debugging method based on the container's internal network, deployed in a hybrid cloud environment with application services in multi-region network isolation environments, requires the use of a visual interface for integration debugging to verify the correctness of the integrated interface application. However, due to security considerations, enterprises do not allow client browsers to open firewall port rules for interface applications, thus failing to meet the requirement for verifying the correctness of interface application deployments.

[0020] Compared with related technologies, the method for automated construction and rapid integration of application services in hybrid cloud provided by this invention has the following beneficial effects:

[0021] This invention designs a method for automated construction, cross-regional cluster communication, and rapid debugging, which can be applied to quickly build a full-process service architecture in a hybrid cloud environment, saving time, debugging, and maintenance costs. Attached Figure Description

[0022] Figure 1 A design diagram of a containerized component building module for the automated construction and rapid integration method of application services in hybrid cloud provided by the present invention;

[0023] Figure 2 Design diagram of cross-domain cluster communication module in hybrid cloud for the method of automated construction and rapid integration of application services in hybrid cloud provided by the present invention;

[0024] Figure 3 The present invention provides a design diagram of a rapid debugging module based on an internal container network for an automated construction and rapid integration method of application services in hybrid cloud. Detailed Implementation

[0025] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0026] Please refer to the following: Figure 1 , Figure 2 and Figure 3 ,in, Figure 1 A design diagram of a containerized component building module for the automated construction and rapid integration method of application services in hybrid cloud provided by the present invention;

[0027] Figure 2 Design diagram of cross-domain cluster communication module in hybrid cloud for the method of automated construction and rapid integration of application services in hybrid cloud provided by the present invention;

[0028] Figure 3 This invention provides a design diagram of a rapid debugging module based on a container internal network for an automated construction and rapid integration method of application services in hybrid clouds. The method includes: a containerized component construction module, a cross-domain cluster communication module in a hybrid cloud, and a rapid debugging module based on a container internal network.

[0029] The workflow for the automated construction and rapid integration of application services in hybrid cloud is as follows:

[0030] Specific scheme design as follows: Figure 1 As shown;

[0031] The containerized component building module described in S1 uses containers to build images. Once the required image is built, the built environment image is run and the corresponding directory is mounted. After the image is built inside the container, it is mounted on the host machine. When the environment is migrated or redeployed, the corresponding image is imported and the image is run to complete the rapid build.

[0032] The environment in which the containerized component building module builds the image is a Go environment, a Maven environment, a Node environment, or a Java environment;

[0033] This method avoids being affected by system environment dependencies.

[0034] Specific scheme design as follows: Figure 2As shown;

[0035] The cross-domain cluster communication module in the hybrid cloud described in S2 is used in cross-regional environments;

[0036] When a cluster needs to access clusters of nodes in other regions, network traffic will first be sent through the application server, and then through the traffic forwarding plugin to reach the unified egress server. The unified egress server is mainly used to provide unified network egress services. Using two or more unified network egress servers can realize network load balancing. The application server mainly provides business service capabilities, and business components generally run on the application server.

[0037] When application server resources are insufficient or there is a conflict between business processing resources and network resources, the unified egress server is reused. The traffic forwarding plugin will detect whether the bound unified egress server is in a normal state and select a normal and available unified egress service resource according to the configuration policy.

[0038] S23 When one of the servers goes down or resources are unavailable, network traffic can still be sent normally. When application server traffic passes through the traffic forwarding plugin, the traffic forwarding plugin mainly forwards the traffic to the configured unified egress server through the internal network IP via NAT forwarding. The firewall policy of the unified egress server is enabled to enable the firewall policy of other regional node VIPs, ensuring that other regional node VIPs can receive network traffic normally.

[0039] VIP stands for VirtualIP;

[0040] When the VIP bound to other regional nodes receives traffic, it will communicate with the internal IP of the current node server through the internal IP configured in the VIP. After the network traffic passes through the Kubernetes Services traffic load balancer, the application server can receive the network traffic accessed by other nodes.

[0041] Specific scheme design as follows: Figure 3 As shown;

[0042] In a hybrid cloud network environment, the rapid debugging module based on the container internal network described in S3 only allows connections to the server via bastion host Shell, Xftp, WinSCP, and VNC in the enterprise's internal security settings, and does not allow clients to access the visual application services deployed on the server by enabling firewall policies.

[0043] In step S3, an Ubuntu / CentOS image is built on the server using a container, and a VNC server and related visualization desktop applications are configured in the built container. After the container is started on the server, the container interface can be accessed using the VNC-5900 port provided by the bastion host. Since the network of the container and the network of the container on the host machine are interconnected, the service components can be debugged in a visual way through the browser in the container, and the interface application can be accessed, thus accelerating the completion of container building and integration debugging.

[0044] The browser can be a browser, Navicat, JMeter, etc.

[0045] It also includes methods for building containerized components that do not depend on the operating system, methods for cross-domain cluster communication in hybrid cloud environments, and methods for rapid debugging based on the container's internal network under network security policy restrictions on application service access.

[0046] The containerized component building method that does not depend on the operating system cannot be determined before deployment in a hybrid cloud environment. Component building requires the installation of environment dependencies, and different systems require different environment versions.

[0047] This approach builds components inside containers, and the container configuration is mounted and mapped to the host machine, which improves the versatility of the components.

[0048] The proposed method for rapid communication between cross-domain clusters in hybrid clouds, along with Kubernetes service discovery and load balancing mechanisms, provides a unified entry strategy for multiple containers. However, since a unified exit point also needs to be considered in a hybrid cloud environment, and due to the distributed architecture deployment of components and the communication needs of multiple regional cluster services, factorial firewall port rules must be opened, resulting in excessively high maintenance manpower costs and low security.

[0049] This solution uses a container traffic forwarding plugin, which only requires opening firewall port rules for a unified egress service, thus improving component scalability and communication security.

[0050] Under the network security policy restricting application service access, a rapid debugging method based on the container's internal network is needed in a hybrid cloud environment where application services are deployed in multi-region network isolation environments. This requires integration and debugging using a visual interface to verify the correctness of the integrated application. However, due to security considerations, enterprises do not allow client browsers to open firewall port rules for the application, thus failing to meet the requirement for verifying the correctness of the deployed interface application.

[0051] This solution uses VNC provided by the server management console to build a graphical interface based on containers, enabling visual integration and debugging within the containers. Environment isolation via containers ensures network security while improving debugging efficiency.

[0052] The above description is merely an embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent structural or procedural transformations made based on the content of the present invention specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A hybrid cloud application service automatic construction and rapid integration method, characterized in that, The running process of the hybrid cloud application service automatic construction and rapid integration method is as follows: S1, a containerized component construction module is used to construct an image in the form of a container, when the required image construction is completed, the constructed environment image is run and the corresponding directory is mounted, and when the environment migration or re-deployment is performed, the corresponding image is imported, and the rapid construction is completed by running the image; S2, the hybrid cloud cross-domain cluster communication module is used in a cross-regional environment; S21, when a cluster needs to access the cluster of other regional nodes, the network traffic is first sent through the application server, and then reaches the unified exit server through the traffic forwarding plug-in, the unified exit server is used to provide unified network exit service, and two or more unified network exit services are used to realize network load, the application server provides business service capability, and the business component runs on the application server; S22, when the application server resources are insufficient or the business processing resources and network resources are in conflict, the unified exit server is reused, the traffic forwarding plug-in detects whether the bound unified exit server is in a normal state, and selects the normal available unified exit service resource according to the configuration strategy; S23, when one of the servers is down or the resources are unavailable, the network traffic can still be normally sent, when the application server traffic passes through the traffic forwarding plug-in, the traffic forwarding plug-in forwards the traffic to the configured unified exit server through the intranet IP by the Nat forwarding mode, the firewall strategy of the unified exit server is opened to the firewall strategy of the other regional node VIP, and it is ensured that the other regional node VIP can normally receive the network traffic; S24, when the other regional node bound VIP receives the traffic, the internal IP of the current node server is communicated through the internal IP configured by the VIP, and after the network traffic passes through the Services traffic load of Kubernetes, the application server can receive the network traffic accessed by the other node; In step S3, Ubuntu / CentOS images are constructed in the form of a container on the server, and Vnc server and visual related desktop programs are configured in the constructed container, after the server starts the container, the Vnc-5900 port provided by the bastion host can be used to access the container interface, since the network of the container and the network of the container on the host are in communication with each other, the service component can be debugged and the interface application can be accessed through the browser in the container, thereby accelerating the container construction and integration joint debugging work.

2. The method for application service automated build and rapid integration in hybrid cloud according to claim 1, characterized in that, The environment of the image constructed by the containerized component construction module is a Go environment, a Maven environment, a Node environment or a Java environment.

3. The method for application service automated build and rapid integration in hybrid cloud as claimed in claim 1, wherein, In step S3, Ubuntu / CentOS images are constructed in the form of a container on the server, and Vnc server and visual related desktop programs are configured in the constructed container, after the server starts the container, the Vnc-5900 port provided by the bastion host can be used to access the container interface, since the network of the container and the network of the container on the host are in communication with each other, the service component can be debugged and the interface application can be accessed through the browser in the container, thereby accelerating the container construction and integration joint debugging work.

Images