Cross-architecture management switching method and system based on container cloud platform

Abstract

The embodiment of the invention relates to the technical field of cloud computing, and discloses a cross-architecture management switching method based on a container cloud platform, which comprises the following steps: building an infrastructure of the container cloud platform; constructing a corresponding application abstraction layer, and determining each application interface module of the application abstraction layer and a data interaction mode between each application interface module and the container cloud platform; and when it is detected that the upper-layer application needs to perform hardware operation on the container in the container cloud platform, calling a corresponding application interface module through a uniform interface provided by the application abstraction layer to call a corresponding function of the bottom-layer virtualization platform so as to realize operation on the container. According to the cross-architecture management switching method based on the container cloud platform in the embodiment of the invention, the application abstraction layer is constructed, so that physical hardware resources can be packaged and abstracted into resources which can be directly called by the application. According to the abstract mechanism, the upper-layer application does not need to care about specific implementation details of bottom-layer hardware or containers, so that the complexity of cross-architecture management is simplified.

Description

Technical Field

[0001] The present invention relates to the field of cloud computing technology, and in particular to a cross-architecture management switching method and system based on a container cloud platform. Background Art

[0002] At present, in the construction of the current alternative environment for information innovation, various information systems are facing problems such as differences in different environments (such as Kylin and CentOS), differences in chip instruction sets, and problems in the utilization of existing infrastructure in the process of promoting cloud platform management. Traditional application management methods usually lack the ability to uniformly manage applications and orchestrate services, resulting in complex and inefficient application management. With the development of business, the calls and dependencies between applications have become more and more complex. Therefore, designing a solution that can efficiently manage cloud platforms has become a technical problem that needs to be solved urgently by those skilled in the art. Summary of the invention

[0003] In response to the above-mentioned defects, an embodiment of the present invention discloses a cross-architecture management and switching method based on a container cloud platform, which can support the simultaneous operation of servers with multiple different chip architectures. This architecture breaks the traditional cloud platform's dependence on a single chip architecture and realizes resource integration and efficient utilization across chip architectures.

[0004] The first aspect of the embodiment of the present invention discloses a cross-architecture management switching method based on a container cloud platform, including:

[0005] Build the infrastructure of the container cloud platform; wherein the infrastructure of the container cloud platform includes a front-end architecture and a back-end architecture, the front-end architecture includes a user interface and an application interface gateway, and the back-end architecture includes multiple functional components, and the multiple functional components interact with external systems through a state transfer interface;

[0006] Construct a corresponding application abstraction layer, determine the application interface modules of the application abstraction layer and the data interaction mode between each application interface module and the container cloud platform, and the application abstraction layer is used to encapsulate and abstract physical hardware resources into application call resources;

[0007] When it is detected that the upper-layer application needs to perform hardware operations on the container in the container cloud platform, the unified interface provided by the application abstraction layer is used to call the corresponding application interface module to call the corresponding function of the underlying virtualization platform to implement the operation of the container; the application abstraction layer is used to implement cross-architecture management of multiple container clusters in the container cloud platform.

[0008] As an optional implementation, in the first aspect of the embodiment of the present invention, the container cloud platform includes multiple container clusters, and the container cluster includes multiple containers; the container is used to package the application and its dependencies in one container to implement iteration and deployment of the application;

[0009] The container cloud platform is configured with a cluster monitoring component, which is used to monitor the CPU, memory, network and disk;

[0010] The container cloud platform includes a management node and computing nodes of multiple CPU architectures. The management method of the container cloud platform of multiple CPU architectures includes:

[0011] Performing a registration operation on the new computing node so that the management node adds the new computing node to the container cloud platform and configures attribute information of the new computing node;

[0012] Identify a container image architecture corresponding to the container application based on the container application scheduling requirement;

[0013] Corresponding computing nodes are allocated to the container application according to the container image architecture and key information of each computing node in the container cloud platform.

[0014] As an optional implementation, in the first aspect of the embodiment of the present invention, the container is constructed by the following steps:

[0015] Write the corresponding original program code based on user demand information;

[0016] Processing the original program code according to a pre-configured standardized processing logic to obtain processed standard code information, and packaging the standard code information into a corresponding standard container image;

[0017] When it is detected that the corresponding application needs to be run, the environment information of the device to be run is determined, and the corresponding compilation logic is obtained according to the environment information;

[0018] The standard container image is translated according to the compilation logic to obtain corresponding application code, and the application code is run on the device to be run.

[0019] As an optional implementation, in the first aspect of the embodiment of the present invention, the unified interface provided by the application abstraction layer is used to call the corresponding application interface module to call the corresponding function of the underlying virtualization platform to implement the operation of the container, and further includes:

[0020] Reading chip ID information or register information through a unified interface or protocol provided by the application abstraction layer;

[0021] Parsing the ID information or register information of the chip to obtain basic attributes of the chip, wherein the basic attributes of the chip include chip model and manufacturer information;

[0022] The corresponding chip architecture type is determined according to the basic attributes of the chip, and the corresponding application interface module is determined based on the chip architecture type, and the corresponding function of the underlying virtualization platform is called through the application interface module to implement the operation of the container.

[0023] As an optional implementation manner, in the first aspect of the embodiment of the present invention, the unified interface of the application abstraction layer is obtained by the following steps:

[0024] Identify the types and properties of underlying hardware resources;

[0025] According to the identification results, corresponding virtual resources or logical resources are created;

[0026] Uniform attributes and interfaces are defined for the virtual resources or logical resources.

[0027] As an optional implementation, in the first aspect of the embodiment of the present invention, the container cloud platform is automatically deployed through the following steps:

[0028] Split each module in the system into corresponding microservices according to the pre-set splitting logic;

[0029] Package the split microservices to obtain corresponding microservice files;

[0030] Automatically deploy and expand the microservice files based on containerization technology;

[0031] The container cloud platform is provided with a load balancing module and an elastic scaling module. The load balancing module is used to distribute traffic to multiple container instances, and the load balancing module supports polling algorithm, IP calculation and minimum connection; the elastic scaling module is used to automatically adjust the size of computing resources according to the load changes of the application. When the load of the application increases, the container cloud platform automatically increases computing resources to meet performance requirements; when the load decreases, the container cloud platform automatically reduces resources to save costs.

[0032] As an optional implementation manner, in the first aspect of the embodiment of the present invention, the cross-architecture management method further includes:

[0033] The container cloud platform sets resource isolation information and corresponding resource isolation management strategies;

[0034] Determine a resource operation interface, configure corresponding isolation detection information for the resource operation interface according to the resource isolation information, and call a corresponding resource isolation management strategy according to the isolation detection information to detect the incoming data resource and obtain the first resource data;

[0035] A corresponding resource filtering strategy and a resource query interface are determined, wherein the resource query interface calls the resource isolation filtering strategy according to the first resource data to filter the first resource data.

[0036] A second aspect of an embodiment of the present invention discloses a cross-architecture management system based on a container cloud platform, including:

[0037] Building module: used to build the infrastructure of the container cloud platform; wherein the infrastructure of the container cloud platform includes a front-end architecture and a back-end architecture, the front-end architecture includes a user interface and an application interface gateway, and the back-end architecture includes multiple functional components, and the multiple functional components interact with external systems through a state transfer interface;

[0038] Construction module: used to construct the corresponding application abstraction layer, determine the various application interface modules of the application abstraction layer and the data interaction mode between each application interface module and the container cloud platform. The application abstraction layer is used to encapsulate and abstract physical hardware resources into application call resources;

[0039] Management module: When it is detected that the upper-layer application needs to perform hardware operations on the container in the container cloud platform, the management module calls the corresponding application interface module through the unified interface provided by the application abstraction layer to call the corresponding function of the underlying virtualization platform to implement the operation of the container; the application abstraction layer is used to implement cross-architecture management of multiple container clusters in the container cloud platform.

[0040] The third aspect of an embodiment of the present invention discloses an electronic device, comprising: a memory storing executable program code; a processor coupled to the memory; the processor calls the executable program code stored in the memory to execute the cross-architecture management switching method based on the container cloud platform disclosed in the first aspect of the embodiment of the present invention.

[0041] A fourth aspect of an embodiment of the present invention discloses a computer-readable storage medium storing a computer program, wherein the computer program enables a computer to execute the cross-architecture management switching method based on a container cloud platform disclosed in the first aspect of an embodiment of the present invention.

[0042] Compared with the prior art, the embodiments of the present invention have the following beneficial effects:

[0043] In the embodiment of the present invention, the cross-architecture management switching method based on the container cloud platform builds an application abstraction layer, which can encapsulate and abstract physical hardware resources into resources that can be directly called by applications. This abstract mechanism makes it unnecessary for upper-layer applications to care about the specific implementation details of the underlying hardware or containers, thereby simplifying the complexity of cross-architecture management.

[0044] The unified interface provided by the application abstraction layer allows upper-layer applications to call the functions of the underlying virtualization platform through these interfaces to operate the hardware resources in the container. This unified interface design makes cross-architecture management more efficient and consistent. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0046] Figure 1 It is a flow chart of a cross-architecture management switching method based on a container cloud platform disclosed in an embodiment of the present invention;

[0047] Figure 2 It is a schematic diagram of a process of registering a new computing node disclosed in an embodiment of the present invention;

[0048] Figure 3 It is a schematic diagram of the process of constructing a container disclosed in an embodiment of the present invention;

[0049] Figure 4 It is a schematic diagram of the process of container operation disclosed in the embodiment of the present invention;

[0050] Figure 5 It is a structural diagram of a cross-architecture management system based on a container cloud platform provided by an embodiment of the present invention;

[0051] Figure 6 It is a structural schematic diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0052] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0053] It should be noted that the terms "first", "second", "third", "fourth", etc. in the specification and claims of the present invention are used to distinguish different objects rather than to describe a specific order. The terms "including" and "having" in the embodiments of the present invention and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device including a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0054] In the current construction of the alternative environment for information innovation, various information systems are faced with differences in different environments (such as Kylin and CentOS), differences in chip instruction sets, and problems in the utilization of existing infrastructure in the process of promoting cloud platform management. Traditional application management methods usually lack unified management and service orchestration capabilities for applications, resulting in complex and inefficient application management. With the development of business, the calls and dependencies between applications become more and more complex. Based on this, an embodiment of the present invention discloses a cross-architecture management switching method, system, electronic device, and storage medium based on a container cloud platform. By constructing an application abstraction layer, the method can encapsulate and abstract physical hardware resources into resources that can be directly called by applications. This abstract mechanism enables upper-level applications to not need to care about the specific implementation details of the underlying hardware or containers, thereby simplifying the complexity of cross-architecture management.

[0055] Embodiment 1

[0056] See also Figure 1 , Figure 1 It is a flow chart of the cross-architecture management switching method based on the container cloud platform disclosed in the embodiment of the present invention. Among them, the execution subject of the method described in the embodiment of the present invention is an execution subject composed of software and / or hardware, and the execution subject can receive relevant information by wired or / and wireless means, and can send certain instructions. Of course, it can also have certain processing functions and storage functions. The execution subject can control multiple devices, such as a remote physical server or cloud server and related software, or it can be a local host or server and related software that performs related operations on a device placed somewhere. In some scenarios, multiple storage devices can also be controlled, and the storage devices can be placed in the same place or different places as the devices. For example Figure 1 As shown, the cross-architecture management switching method based on the container cloud platform includes the following steps:

[0057] S101: Building an infrastructure of a container cloud platform; wherein the infrastructure of the container cloud platform includes a front-end architecture and a back-end architecture, the front-end architecture includes a user interface and an application interface gateway, and the back-end architecture includes multiple functional components, and the multiple functional components interact with external systems through a state transfer interface;

[0058] S102: Construct a corresponding application abstraction layer, determine each application interface module of the application abstraction layer and a data interaction mode between each application interface module and the container cloud platform, wherein the application abstraction layer is used to encapsulate and abstract physical hardware resources into application call resources;

[0059] S103: When it is detected that the upper-layer application needs to perform hardware operations on the container in the container cloud platform, the corresponding application interface module is called through the unified interface provided by the application abstraction layer to call the corresponding function of the underlying virtualization platform to implement the operation of the container; the cross-architecture management of multiple container clusters in the container cloud platform is implemented through the application abstraction layer.

[0060] The embodiment of the present invention constructs an application abstraction layer, and the method can encapsulate and abstract physical hardware resources into resources that can be directly called by applications. This abstract mechanism makes it unnecessary for upper-layer applications to care about the specific implementation details of the underlying hardware or containers, thereby simplifying the complexity of cross-architecture management.

[0061] The unified interface provided by the application abstraction layer allows upper-layer applications to call the functions of the underlying virtualization platform through these interfaces to operate the hardware resources in the container. This unified interface design makes cross-architecture management more efficient and consistent. Because the application abstraction layer encapsulates and abstracts physical hardware resources, upper-layer applications can dynamically request and release resources as needed. This flexible resource configuration method improves resource utilization and enables upper-layer applications to better adapt to different workloads and performance requirements.

[0062] Cross-architecture management enables the container cloud platform to support a variety of different hardware architectures and operating systems, thus providing wider compatibility. This allows upper-layer applications to be seamlessly migrated and deployed in different environments, improving the flexibility and scalability of the system.

[0063] Multiple functional components in the backend architecture of the embodiment of the present invention exchange information with external systems through the state transfer interface, which ensures the consistency and real-time performance of data between systems. The design of the state transfer interface enables the system to accurately track and update the state of the container, thereby improving the reliability and stability of the system. Through the application abstraction layer, the upper-layer application can easily obtain the state information of the container and make corresponding decisions and adjustments based on this information. This efficient information interaction method makes cross-architecture management more intelligent and automated.

[0064] More preferably, the container cloud platform includes multiple container clusters, and the container cluster includes multiple containers; the containers are used to package the application and its dependencies in one container to implement iteration and deployment of the application;

[0065] The container cloud platform is configured with a cluster monitoring component, which is used to monitor the CPU, memory, network and disk;

[0066] like Figure 2 As shown, the container cloud platform includes a management node and computing nodes of multiple CPU architectures, and the management method of the container cloud platform of multiple CPU architectures includes:

[0067] S1011: Perform a registration operation on the new computing node so that the management node adds the new computing node to the container cloud platform and configures attribute information of the new computing node;

[0068] S1012: Identify a container image architecture corresponding to the container application based on the container application scheduling requirement;

[0069] S1013: Allocate corresponding computing nodes to the container application according to the container image architecture and key information of each computing node in the container cloud platform.

[0070] The embodiment of the present invention packages the application and its dependencies in a container, so that the container cloud platform can more flexibly implement the iteration and deployment of the application. This containerization method helps to reduce the differences between applications in different environments, thereby improving the portability and deployment efficiency of the application.

[0071] The container cloud platform includes multiple container clusters, each of which contains multiple containers. This structure allows resources to be allocated and managed more flexibly, dynamically adjust resources according to actual needs, and improve resource utilization. The cluster monitoring component configured in the container cloud platform can monitor the usage of key resources such as CPU, memory, network, and disk in real time, which helps to promptly discover and resolve potential performance bottlenecks or failures and ensure the stable operation of the system. The data provided by the monitoring component can also provide strong support for management decisions such as resource scheduling and load balancing, further improving the overall performance of the system and user experience.

[0072] The container cloud platform supports computing nodes with multiple CPU architectures, which means it can adapt to the needs of different hardware environments and improve the compatibility and scalability of the system. After the management node registers and configures the new computing node, the system can intelligently allocate the most suitable computing node for the container application based on the image architecture of the container application and the key information of the computing node. This intelligent resource allocation method helps to improve the operating efficiency and resource utilization of the system. Through the management node of the container cloud platform, the container clusters and computing nodes in the entire platform can be centrally managed and monitored, which simplifies the management process and reduces management costs. The application of containerization technology also helps to reduce the differences and complexity of applications in different environments and reduce maintenance costs.

[0073] The resources provided by the nodes in the container cloud cluster are mainly computing resources. Computing resources are measurable basic resources that can be applied for, allocated and used. The computing resources in the current cluster mainly include CPU, GPU and Memory. Most conventional applications do not use GPU. Here we focus on the resource management of CPU and Memory. CPU and Memory are used by Pods. Therefore, when configuring Pods, you can specify the required CPU and Memory for each container through the parameters CPU Request and Memory Request. The container cloud platform will find a Node with sufficient resources to schedule the Pod based on the value of Request. If not, the scheduling fails. The computing resource measurement unit of the container cloud platform is size-sensitive. m indicates the default resource request in byte units expressed in binary. Use the project administrator account project-admin to log in to the container cloud platform to manage quota information. By default, there is no upper limit on the usage of resources in the project. Quota management supports setting upper limits for various types of resources, such as workload, CPU, memory and other resources. Click Edit Quota to set the upper limit for the usage of various resources.

[0074] More preferably, Figure 3 As shown, the container is constructed by the following steps:

[0075] S100a: writing corresponding original program codes based on user requirement information;

[0076] S100b: Processing the original program code according to a pre-configured standardized processing logic to obtain processed standard code information, and packaging the standard code information into a corresponding standard container image;

[0077] S100c: When it is detected that a corresponding application needs to be run, determining environment information of the device to be run, and acquiring corresponding compilation logic according to the environment information;

[0078] S100d: performing a translation operation on the standard container image according to the compilation logic to obtain corresponding application code, and running the application code on the device to be run.

[0079] The embodiment of the present invention writes the original program code based on the user demand information, ensuring that the development process is closely aligned with the user demand and improving the pertinence and efficiency of the development. The standard code information is packaged and encapsulated to form a standard container image, which ensures the consistency and stability of the container in different environments.

[0080] Select appropriate compilation logic based on the environment information of the device to be run to translate the standard container image and generate application code suitable for the environment. This dynamic compilation method enhances the compatibility of the container, enables the container to run in a variety of different hardware and software environments, and improves the portability of the container. Selecting compilation logic based on the environment information of the device to be run helps optimize the performance of the application in a specific environment. For example, the optimal compilation option can be selected based on factors such as the device's CPU architecture and operating system type, thereby improving the running speed and efficiency of the application.

[0081] At the same time, since containers only contain applications and their dependencies and do not rely on specific hardware or operating system environments, resources can be allocated and managed more flexibly, improving resource utilization. The application of containerization technology simplifies the deployment and operation and maintenance process of applications. Once a standard container image is built, applications can be quickly deployed and run in any environment that supports container technology without the need for tedious environment configuration and dependency installation.

[0082] More preferably, Figure 4 As shown, the unified interface provided by the application abstraction layer is used to call the corresponding application interface module to call the corresponding function of the underlying virtualization platform to implement the operation of the container, and further includes:

[0083] S1031: Reading chip ID information or register information through a unified interface or protocol provided by the application abstraction layer;

[0084] S1032: Parse the chip ID information or register information to obtain basic attributes of the chip, where the basic attributes of the chip include chip model and manufacturer information;

[0085] S1033: Determine a corresponding chip architecture type according to basic attributes of the chip, determine a corresponding application interface module based on the chip architecture type, and call corresponding functions of the underlying virtualization platform through the application interface module to implement operations on the container.

[0086] The embodiment of the present invention reads the chip ID information or register information through step S1031, and the system can identify the hardware characteristics of the current operating environment, especially the basic attributes of the chip. Step S1032 parses this information so that the system can accurately understand the model and manufacturer information of the chip, which is the basis for selecting the correct application interface module. The chip architecture type is determined according to the basic attributes of the chip (step S1033), and the system can dynamically select the application interface module that best suits the current hardware environment, thereby improving the compatibility and flexibility of the system.

[0087] Selecting an application interface module that matches the chip architecture can ensure that container operations can fully utilize hardware resources and reduce unnecessary performance loss. Especially in heterogeneous computing environments, chips with different architectures may have different performance characteristics and optimization space. By accurately identifying the chip architecture, the system can select the most optimized operation path, thereby improving overall performance.

[0088] Traditional container management platforms may require manual configuration of hardware compatibility information or rely on specific hardware environments. Through the above process, the system can automatically identify and adapt to different hardware environments, simplifying the configuration and management process.

[0089] More preferably, the unified interface of the application abstraction layer is obtained by the following steps:

[0090] Identify the types and properties of underlying hardware resources;

[0091] According to the identification results, corresponding virtual resources or logical resources are created;

[0092] Uniform attributes and interfaces are defined for the virtual resources or logical resources.

[0093] By identifying the types and properties of underlying hardware resources, the application abstraction layer can accurately understand the characteristics and capabilities of the hardware resources, thereby creating corresponding virtual resources or logical resources.

[0094] This resource abstraction and encapsulation method eliminates the need for upper-level applications to pay direct attention to the specific implementation of the underlying hardware. They only need to interact with virtual resources or logical resources through a unified interface, thereby simplifying the complexity of application development.

[0095] In the embodiment of the present invention, since the application abstraction layer defines unified attributes and interfaces for virtual resources or logical resources, when the underlying hardware resources change (such as hardware upgrade, replacement, etc.), only the corresponding part in the application abstraction layer needs to be updated without modifying the upper layer application. This design enables the system to flexibly adapt to different hardware environments, and also facilitates the expansion and upgrade of the system.

[0096] By applying the abstraction layer, the system can manage and schedule the underlying hardware resources more efficiently. For example, it can implement dynamic resource allocation, load balancing, and fault recovery based on the attributes and interface information of virtual or logical resources.

[0097] This resource management and scheduling method helps improve the overall performance and resource utilization of the system, while also enhancing the stability and reliability of the system. The application abstraction layer defines unified properties and interfaces for virtual resources or logical resources on different hardware platforms, which helps achieve cross-platform compatibility and interoperability. This means that upper-layer applications can run seamlessly on different hardware platforms without additional adaptation or modification, thereby reducing the cost of application development and deployment.

[0098] In the one-cloud-multi-core architecture, the container cloud platform supports seamless switching between servers with different chip architectures. When a server with a certain chip architecture fails or encounters a performance bottleneck, the container cloud platform can automatically migrate applications to servers with other chip architectures to ensure business continuity and stability. This seamless switching capability greatly reduces the risk of business interruption caused by hardware failure or performance issues.

[0099] The container cloud platform abstracts and encapsulates the underlying hardware resources, so that upper-layer applications do not need to care about the specific implementation and differences of the underlying hardware. This greatly reduces the development and maintenance costs of applications. At the same time, the container cloud platform also provides a wealth of monitoring and management functions, allowing operation and maintenance personnel to easily monitor and manage the underlying hardware resources and the operating status of applications.

[0100] More preferably, the container cloud platform is automatically deployed through the following steps:

[0101] Split each module in the system into corresponding microservices according to the pre-set splitting logic;

[0102] Package the split microservices to obtain corresponding microservice files;

[0103] Automatically deploy and expand the microservice files based on containerization technology;

[0104] The container cloud platform is provided with a load balancing module and an elastic scaling module. The load balancing module is used to distribute traffic to multiple container instances, and the load balancing module supports polling algorithm, IP calculation and minimum connection; the elastic scaling module is used to automatically adjust the size of computing resources according to the load changes of the application. When the load of the application increases, the container cloud platform automatically increases computing resources to meet performance requirements; when the load decreases, the container cloud platform automatically reduces resources to save costs.

[0105] The embodiment of the present invention splits each module in the system into corresponding microservices through pre-set splitting logic, so that each microservice is focused on completing specific functions or business logic. This modular design helps to reduce system complexity, improve code readability and maintainability, and also facilitates troubleshooting and performance optimization.

[0106] The split microservices can be independently packaged as microservice files and automatically deployed and expanded using containerization technology. Containerization technology allows microservices to run easily in different hardware and software environments without tedious environment configuration and dependency installation. At the same time, the container cloud platform supports dynamic expansion of microservices, and can increase or decrease the number of container instances according to actual needs to meet changing business needs. The load balancing module set up in the container cloud platform can distribute traffic to multiple container instances according to preset algorithms (such as polling algorithm, IP hash and minimum connection) to achieve load balancing and traffic control. This design helps to avoid overloading a single container instance and improve the overall performance and stability of the system. The elastic scaling module can automatically adjust the size of computing resources according to the load changes of the application, ensuring that the system can obtain sufficient resource support in time when the load increases, and can release excess resources to save costs when the load decreases.

[0107] Microservice architecture is a method of building an application as a series of small, autonomous, loosely coupled services. Each service runs in its own independent process and communicates using lightweight communication mechanisms (such as RESTful APIs). The container cloud platform provides an ideal carrier for microservices. The specific implementation process and principles include: Service splitting and independence: On the container cloud platform, each microservice can be independently packaged, deployed, and managed. The coupling between services is reduced, which improves the flexibility and scalability of the system. Automated deployment and expansion: Utilize containerization (such as Docker) and automated operation and maintenance tools (such as Kubernetes) to achieve rapid deployment and elastic scaling of microservices. This helps to quickly respond to changes in business needs and improve the responsiveness and reliability of the system. Service registration and discovery: Service registration and discovery is one of the core components in the microservice architecture. It implements automatic registration and discovery of microservices, allowing services to be dynamically called and load balanced. Under the container cloud platform, service registration centers such as Eureka and Nacos can be used to implement this function. API Gateway: As the entrance to external access, the API Gateway is responsible for request routing, security authentication, current limiting and other functions. On the container cloud platform, you can use Spring Cloud Gateway, Zuul and other API gateways to implement these functions.

[0108] More preferably, the cross-architecture management method further includes:

[0109] The container cloud platform sets resource isolation information and corresponding resource isolation management strategies;

[0110] Determine a resource operation interface, configure corresponding isolation detection information for the resource operation interface according to the resource isolation information, and call a corresponding resource isolation management strategy according to the isolation detection information to detect the incoming data resource and obtain the first resource data;

[0111] A corresponding resource filtering strategy and a resource query interface are determined, wherein the resource query interface calls the resource isolation filtering strategy according to the first resource data to filter the first resource data.

[0112] By setting resource isolation information and corresponding management policies, the container cloud platform of the embodiment of the present invention can ensure that resources between different users or applications are isolated from each other to prevent resource abuse or data leakage. The configuration of isolation detection information enables the system to automatically detect and apply corresponding isolation policies when processing incoming data resources, thereby ensuring the legality and security of resources. The setting of resource operation interface and resource query interface provides users with flexible resource management means. Users can query, allocate, release and other operations on resources through these interfaces. At the same time, the configuration of resource isolation management strategy and filtering strategy enables the system to manage and control resources in a refined manner according to actual needs, thereby improving the flexibility and controllability of resource management.

[0113] By filtering the first resource data through the resource filtering strategy, the system can remove redundant or invalid resource data to ensure that only qualified resources are used. This filtering mechanism helps to reduce resource waste and improve resource utilization, while also helping to optimize system performance and ensure stable system operation. Automated resource isolation and filtering mechanisms reduce the need for manual intervention and reduce operation and maintenance costs. At the same time, the real-time monitoring and alarm functions provided by these mechanisms can help operation and maintenance personnel to promptly discover and solve potential problems and improve operation and maintenance efficiency.

[0114] The container cloud platform can automatically adjust the number of containers according to the actual load of the application. When the number of application requests is monitored to increase, the platform can automatically increase the number of container instances to cope with higher traffic; conversely, it can reduce the number of instances during low periods to save resource costs. This dynamic scaling capability ensures efficient resource utilization and business continuity. The container cloud platform uses container orchestration systems (such as Kubernetes) to automatically deploy, roll out, and automatically scale containerized applications. These orchestration systems can intelligently determine which node the container runs on, achieving efficient resource utilization and load balancing.

[0115] In a distributed environment, containers may be started, stopped, or migrated frequently. The container cloud platform provides a service discovery mechanism so that applications in containers can automatically find and connect to other services. At the same time, through the built-in load balancing function, the platform can distribute network traffic to ensure that there is no single point of overload, improving the stability and response speed of the system.

[0116] In the specific implementation, an enterprise space can be created under the cluster of the container cloud platform to group and manage different projects. Projects and DevOps projects can be created under the enterprise space; projects and DevOps projects are the lowest level of version permission management at present, and consume cluster resources to deploy and build applications.

[0117] When a user creates an enterprise space, the user becomes the administrator (admin) of the enterprise space and has the right to view and manage all objects (projects, DevOps projects) in the enterprise space. The administrator will also inherit the management permissions of the projects and projects in the enterprise space. The cluster-admin and workspaces-manager roles in the cluster have the permission to manage enterprise spaces and support viewing, creating, editing, or deleting enterprise spaces. This document describes the common functions for managing enterprise spaces.

[0118] The creator of a project is the admin of the project, who can invite members of the same enterprise space to join the project and authorize them. After entering the enterprise space to which they belong, the enterprise space administrator can view, create, edit or delete all projects under the current enterprise space.

[0119] The basis of resource management in the container cloud platform is the resource configuration of containers and Pods (Rrequests and Llimits). The resource configuration of containers specifies the resources requested by the container and the upper limit of the resources that the container can use, while the resource configuration of Pods specifies the resources requested by all containers in the Pod and the upper limit of the resources that the container can use. Through the resource quota mechanism, the total amount of resources used by all Pods in the namespace can be limited, and the number of specified types in this namespace can also be limited. Using scopes allows resource quotas to be limited only to objects that meet a specific range, so the scope mechanism can make resource quota strategies richer and more flexible.

[0120] When implementing it, you can also configure the label setting page, which is used to specify one or more sets of labels (Labels) corresponding to the resource. Labels are attached to any object in the form of key-value pairs, such as Pod, Service, Node, etc. After defining the label, other objects can reference the object through the label. The most common usage is to reference the object through the node selector. Generally speaking, we can define multiple labels for a Pod (or other object) to facilitate configuration, deployment and other management tasks. For example, deploy different versions of applications to different environments; or monitor and analyze applications (logging, monitoring, alarming, etc.). By setting multiple labels, we can manage objects in a refined manner in multiple dimensions.

[0121] In the embodiment of the present invention, the cross-architecture management switching method based on the container cloud platform constructs an application abstraction layer, which can encapsulate and abstract physical hardware resources into resources that can be directly called by applications. This abstraction mechanism makes it unnecessary for upper-layer applications to care about the specific implementation details of the underlying hardware or containers, thereby simplifying the complexity of cross-architecture management. The unified interface provided by the application abstraction layer enables upper-layer applications to call the functions of the underlying virtualization platform through these interfaces to implement operations on hardware resources in the container. This unified interface design makes cross-architecture management more efficient and consistent.

[0122] Embodiment 2

[0123] See also Figure 5 , Figure 5 Schematic diagram of the structure of a cross-architecture management system based on a container cloud platform disclosed in an embodiment of the present invention. Figure 5 As shown, the cross-architecture management system based on the container cloud platform may include:

[0124] Building module 21: used to build the infrastructure of the container cloud platform; wherein the infrastructure of the container cloud platform includes a front-end architecture and a back-end architecture, the front-end architecture includes a user interface and an application interface gateway, and the back-end architecture includes multiple functional components, and the multiple functional components interact with external systems through a state transfer interface;

[0125] Construction module 22: used to construct a corresponding application abstraction layer, determine each application interface module of the application abstraction layer and the data interaction mode between each application interface module and the container cloud platform, and the application abstraction layer is used to encapsulate and abstract physical hardware resources into application call resources;

[0126] Management module 23: When it is detected that the upper-layer application needs to perform hardware operations on the container in the container cloud platform, the management module 23 is used to call the corresponding application interface module through the unified interface provided by the application abstraction layer to call the corresponding function of the underlying virtualization platform to implement the operation of the container; the application abstraction layer is used to implement cross-architecture management of multiple container clusters in the container cloud platform.

[0127] In the embodiment of the present invention, the cross-architecture management switching method based on the container cloud platform constructs an application abstraction layer, which can encapsulate and abstract physical hardware resources into resources that can be directly called by applications. This abstraction mechanism makes it unnecessary for upper-layer applications to care about the specific implementation details of the underlying hardware or containers, thereby simplifying the complexity of cross-architecture management. The unified interface provided by the application abstraction layer enables upper-layer applications to call the functions of the underlying virtualization platform through these interfaces to implement operations on hardware resources in the container. This unified interface design makes cross-architecture management more efficient and consistent.

[0128] Embodiment 3

[0129] See also Figure 6 , Figure 6 Schematic diagram of the structure of an electronic device disclosed in an embodiment of the present invention. The electronic device may be a computer, a server, etc. Of course, in certain circumstances, it may also be a smart device such as a mobile phone, a tablet computer, a monitoring terminal, and an image acquisition device with processing functions. Figure 6 As shown, the electronic device may include:

[0130] A memory 510 storing executable program codes;

[0131] a processor 520 coupled to the memory 510;

[0132] The processor 520 calls the executable program code stored in the memory 510 to execute some or all of the steps in the cross-architecture management switching method based on the container cloud platform in the first embodiment.

[0133] An embodiment of the present invention discloses a computer-readable storage medium storing a computer program, wherein the computer program enables a computer to execute part or all of the steps in the cross-architecture management switching method based on a container cloud platform in Embodiment 1.

[0134] An embodiment of the present invention also discloses a computer program product, wherein when the computer program product runs on a computer, the computer executes part or all of the steps in the cross-architecture management switching method based on a container cloud platform in Embodiment 1.

[0135] An embodiment of the present invention also discloses an application publishing platform, wherein the application publishing platform is used to publish a computer program product, wherein when the computer program product runs on a computer, the computer executes part or all of the steps in the cross-architecture management switching method based on a container cloud platform in Embodiment 1.

[0136] In various embodiments of the present invention, it should be understood that the size of the serial numbers of the processes does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0137] 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, i.e., they may be located in one place or distributed over multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0138] In addition, each functional unit in each embodiment of the present invention 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. The integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0139] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-accessible memory. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a memory and includes several requests for a computer device (which can be a personal computer, a server or a network device, etc., specifically a processor in a computer device) to perform some or all of the steps of the method described in each embodiment of the present invention.

[0140] In the embodiments provided by the present invention, it should be understood that "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.

[0141] A person of ordinary skill in the art can understand that some or all of the steps in the various methods of the embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium, and the storage medium includes a read-only memory (ROM), a random access memory (RAM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), a one-time programmable read-only memory (OTPROM), an electronically erasable rewritable read-only memory (EEPROM), a compact disc (CD-ROM) or other optical disc storage, magnetic disk storage, magnetic tape storage, or any other computer-readable medium that can be used to carry or store data.

[0142] The above is a detailed introduction to the cross-architecture management switching method, system, electronic device and storage medium based on the container cloud platform disclosed in the embodiments of the present invention. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for general technical personnel in this field, according to the ideas of the present invention, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims

1. A cross-architecture management switching method based on a container cloud platform, characterized in that: include: Build the infrastructure of the container cloud platform; wherein the infrastructure of the container cloud platform includes a front-end architecture and a back-end architecture, the front-end architecture includes a user interface and an application interface gateway, and the back-end architecture includes multiple functional components, and the multiple functional components interact with external systems through a state transfer interface; Construct a corresponding application abstraction layer, determine the application interface modules of the application abstraction layer and the data interaction mode between each application interface module and the container cloud platform, and the application abstraction layer is used to encapsulate and abstract physical hardware resources into application call resources; When it is detected that the upper-layer application needs to perform hardware operations on the container in the container cloud platform, the unified interface provided by the application abstraction layer is used to call the corresponding application interface module to call the corresponding function of the underlying virtualization platform to implement the operation of the container; the application abstraction layer is used to implement cross-architecture management of multiple container clusters in the container cloud platform.

2. The cross-architecture management switching method based on the container cloud platform according to claim 1, characterized in that: The container cloud platform includes multiple container clusters, and the container clusters include multiple containers; the containers are used to package the application and its dependencies in one container to implement iteration and deployment of the application; The container cloud platform is configured with a cluster monitoring component, which is used to monitor the CPU, memory, network and disk; The container cloud platform includes a management node and computing nodes of multiple CPU architectures. The management method of the container cloud platform of multiple CPU architectures includes: Performing a registration operation on the new computing node so that the management node adds the new computing node to the container cloud platform and configures attribute information of the new computing node; Identify a container image architecture corresponding to the container application based on the container application scheduling requirement; Corresponding computing nodes are allocated to the container application according to the container image architecture and key information of each computing node in the container cloud platform.

3. The cross-architecture management switching method based on the container cloud platform according to claim 2, characterized in that: The container is constructed by the following steps: Write the corresponding original program code based on user demand information; Processing the original program code according to a pre-configured standardized processing logic to obtain processed standard code information, and packaging the standard code information into a corresponding standard container image; When it is detected that the corresponding application needs to be run, the environment information of the device to be run is determined, and the corresponding compilation logic is obtained according to the environment information; The standard container image is translated according to the compilation logic to obtain corresponding application code, and the application code is run on the device to be run.

4. The cross-architecture management switching method based on the container cloud platform according to claim 2, characterized in that: The method of calling the corresponding application interface module through the unified interface provided by the application abstraction layer to call the corresponding function of the underlying virtualization platform to implement the operation on the container also includes: Reading chip ID information or register information through a unified interface or protocol provided by the application abstraction layer; Parsing the ID information or register information of the chip to obtain basic attributes of the chip, wherein the basic attributes of the chip include chip model and manufacturer information; The corresponding chip architecture type is determined according to the basic attributes of the chip, and the corresponding application interface module is determined based on the chip architecture type, and the corresponding function of the underlying virtualization platform is called through the application interface module to implement the operation of the container.

5. The cross-architecture management switching method based on the container cloud platform according to claim 2, characterized in that: The unified interface of the application abstraction layer is obtained by the following steps: Identify the types and properties of underlying hardware resources; According to the identification results, corresponding virtual resources or logical resources are created; Uniform attributes and interfaces are defined for the virtual resources or logical resources.

6. The cross-architecture management switching method based on the container cloud platform according to claim 2, characterized in that: The container cloud platform is automatically deployed through the following steps: Split each module in the system into corresponding microservices according to the pre-set splitting logic; Package the split microservices to obtain corresponding microservice files; Automatically deploy and expand the microservice files based on containerization technology; The container cloud platform is provided with a load balancing module and an elastic scaling module. The load balancing module is used to distribute traffic to multiple container instances, and the load balancing module supports polling algorithm, IP calculation and minimum connection; the elastic scaling module is used to automatically adjust the size of computing resources according to the load changes of the application. When the load of the application increases, the container cloud platform automatically increases computing resources to meet performance requirements; when the load decreases, the container cloud platform automatically reduces resources to save costs.

7. The cross-architecture management switching method based on the container cloud platform according to claim 1, characterized in that: The cross-architecture management method further includes: The container cloud platform sets resource isolation information and corresponding resource isolation management strategies; Determine a resource operation interface, configure corresponding isolation detection information for the resource operation interface according to the resource isolation information, and call a corresponding resource isolation management strategy according to the isolation detection information to detect the incoming data resource and obtain the first resource data; A corresponding resource filtering strategy and a resource query interface are determined, wherein the resource query interface calls the resource isolation filtering strategy according to the first resource data to filter the first resource data.

8. A cross-architecture management system based on a container cloud platform, characterized in that: include: Building module: used to build the infrastructure of the container cloud platform; wherein the infrastructure of the container cloud platform includes a front-end architecture and a back-end architecture, the front-end architecture includes a user interface and an application interface gateway, and the back-end architecture includes multiple functional components, and the multiple functional components interact with external systems through a state transfer interface; Construction module: used to construct the corresponding application abstraction layer, determine the various application interface modules of the application abstraction layer and the data interaction mode between each application interface module and the container cloud platform. The application abstraction layer is used to encapsulate and abstract physical hardware resources into application call resources; Management module: When it is detected that the upper-layer application needs to perform hardware operations on the container in the container cloud platform, the management module calls the corresponding application interface module through the unified interface provided by the application abstraction layer to call the corresponding function of the underlying virtualization platform to implement the operation of the container; the application abstraction layer is used to implement cross-architecture management of multiple container clusters in the container cloud platform.

9. An electronic device, characterized in that: include: A memory storing executable program code; a processor coupled to the memory; The processor calls the executable program code stored in the memory to execute the cross-architecture management switching method based on the container cloud platform as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program enables a computer to execute the cross-architecture management switching method based on a container cloud platform according to any one of claims 1 to 7.

Images