A container-compatible method and related devices for application clustering deployment
By performing protocol conversion and target node matching in Android application containerization technology, the problem of poor compatibility of containerization platforms is solved, and efficient application cluster deployment and operation and maintenance are achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- GUANGDONG ZHONGXING NEWSTART TECH CO LTD
- Filing Date
- 2026-05-20
- Publication Date
- 2026-07-24
AI Technical Summary
Existing Android application containerization technologies require deep modifications to the container, resulting in poor compatibility with containerization platforms and impacting application operation and maintenance efficiency and flexibility.
By acquiring container instructions and performing protocol conversion, generating initial deployment instructions using a preset mapping table, determining the target node by combining preset configuration information and current hardware information, creating a target compatible container, and deploying the application, the protocol conversion between different platforms and applications is realized, and the application's configuration for the container cluster is extended.
It improves application compatibility and enhances the operational efficiency and flexibility of application cluster deployment.
Smart Images
Figure CN122450593A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular to a container-compatible method and related equipment for application cluster deployment. Background Technology
[0002] With the development of cloud-native technologies, cloud-native applications are deployed, scheduled, and monitored on container cluster platforms. Meanwhile, the demand for large-scale deployment of Android applications is growing, which has driven the development of Android application containerization technology. However, existing Android application containerization technologies require deep modifications to Android containers and have poor compatibility with containerization platforms, resulting in low application operation and maintenance efficiency and flexibility. Summary of the Invention
[0003] The main objective of this application is to propose a container-compatible method and related equipment for application cluster deployment, which can improve application compatibility.
[0004] To achieve the above objectives, one aspect of this application proposes a container-compatible method for application cluster deployment, the method comprising: Obtain container instructions, and perform protocol conversion between the container instructions and the first preset mapping table to obtain initial deployment instructions; The initial deployment instructions and preset configuration information are processed to obtain compatible deployment instructions. The compatible deployment instructions are then matched with the current hardware information to determine the target node. A container is created based on the target node and the compatible deployment instructions to obtain a target compatible container, and the application is deployed based on the target compatible container and the compatible deployment instructions.
[0005] In some embodiments, the method further includes: Information is collected from the target compatible container to obtain the container's basic status, and data is collected according to the compatible deployment instructions to obtain system log data; The container's basic state and the system log data are integrated to obtain a state information set; The protocol is converted according to the state information set and the second preset mapping table to obtain the target state code; and the cluster is synchronized according to the target state code.
[0006] In some embodiments, the step of performing protocol conversion based on the container instructions and the first preset mapping table to obtain the initial deployment instructions specifically includes: The target mapping set is determined by matching the container instructions with the first preset mapping table. The container instruction is decomposed according to the target mapping set to obtain several sub-instructions; The sub-instructions are transformed according to the target mapping set to obtain several operation instructions, and these operation instructions are used as the initial deployment instructions.
[0007] In some embodiments, the process of obtaining a compatible deployment instruction based on the initial deployment instruction and preset configuration information specifically includes: The preset configuration information is parsed to obtain a deployment configuration file, and the deployment configuration file is encapsulated according to preset fields to obtain extended fields; The compatible deployment instruction is obtained by dynamically concatenating the extended fields and the initial deployment instruction.
[0008] In some embodiments, the step of performing protocol conversion based on the state information set and the second preset mapping table to obtain the target state code specifically includes: The state information set is matched with the second preset mapping table to determine several standard states; and the state information set is decomposed according to the several standard states to obtain several sub-state information. The sub-state information is transformed according to the standard states to obtain the first state codes, and the first state codes are integrated to obtain the target state code.
[0009] In some embodiments, the method further includes: The target compatible container is subjected to multi-dimensional data collection at a preset frequency to obtain system status data; and anomaly identification is performed based on the system status data and preset identification rules to determine the container operation information. If the container operation information indicates normal operation, return to the step of performing multi-dimensional data collection on the target compatible container at a preset frequency to obtain system status data; If the container operation information indicates a container abnormality, the container operation information is parsed to determine the target abnormal container, and the target abnormal container is self-healed and restarted according to a preset pointer.
[0010] To achieve the above objectives, another aspect of this application proposes a container-compatible system for application cluster deployment, the system comprising: The conversion module is used to obtain container instructions, perform protocol conversion between the container instructions and a first preset mapping table, and obtain initial deployment instructions. The matching module is used to process the initial deployment instructions and preset configuration information to obtain compatible deployment instructions, and to match the compatible deployment instructions with the current hardware information to determine the target node; The deployment module is used to create a container based on the target node and the compatible deployment instructions to obtain a target compatible container, and to deploy the application based on the target compatible container and the compatible deployment instructions.
[0011] To achieve the above objectives, another aspect of this application provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the method described above.
[0012] To achieve the above objectives, another aspect of the embodiments of this application proposes a computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods described above.
[0013] To achieve the above objectives, another aspect of the embodiments of this application proposes a computer program product, including a computer program that, when executed by a processor, implements the aforementioned method.
[0014] The embodiments of this application include at least the following beneficial effects: This application provides a container-compatible method, system, electronic device, storage medium, and program product for application cluster deployment. This solution obtains container instructions and performs protocol conversion on the container instructions according to a first preset mapping table to obtain initial deployment instructions; it then performs configuration processing based on the initial deployment instructions and preset configuration information to obtain compatible deployment instructions; it performs matching analysis based on the compatible deployment instructions and current hardware technology to determine the target node for application cluster deployment, sends the compatible deployment instructions to the target node, and the target node creates a container according to the compatible deployment instructions to obtain a target compatible container. Finally, it deploys the corresponding application in the target compatible container according to the compatible deployment instructions, installing and running the corresponding application. Through protocol conversion, it achieves protocol conversion between different platforms and applications, expands the application's container cluster configuration, improves application compatibility, and thus improves the operational efficiency and flexibility of application cluster deployment. Attached Figure Description
[0015] Figure 1 This is a flowchart of a container-compatible method for application cluster deployment provided in an embodiment of this application; Figure 2 This is another flowchart of a container-compatible method for application cluster deployment provided in this application embodiment; Figure 3 yes Figure 1 The flowchart of step S101 in the text; Figure 4 yes Figure 1 The flowchart of step S102 in the document; Figure 5 yes Figure 2 The flowchart of step S203 in the process; Figure 6 This is a flowchart illustrating the monitoring and self-healing process in a container-compatible method for application cluster deployment provided in this application embodiment; Figure 7 This is a schematic diagram of the structure of a compatible adaptation system in a specific embodiment provided in this application. Figure 8 This is a flowchart illustrating protocol conversion in a specific embodiment provided in this application. Figure 9 This is a flowchart illustrating auxiliary adaptation in a specific embodiment provided in this application. Figure 10 This is a flowchart illustrating state synchronization and anomaly self-healing in a specific embodiment provided in this application. Figure 11 This is a schematic diagram of the structure of a container-compatible system for application cluster deployment provided in an embodiment of this application; Figure 12 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application. Detailed Implementation
[0016] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit it. In the following description, when referring to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of this application; they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this application as detailed in the appended claims.
[0017] It is understood that the terms “first,” “second,” etc., used in this application may be used herein to describe various concepts, but unless otherwise stated, these concepts are not limited by these terms. These terms are only used to distinguish one concept from another. For example, without departing from the scope of the embodiments of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the words “if,” “when,” or “in response to a determination” as used herein may be interpreted as “when…” or “when…” or “in response to a determination.”
[0018] As used in this application, the terms "at least one", "multiple", "each", "any", etc., "at least one" includes one, two or more, "multiple" includes two or more, "each" refers to each of the corresponding multiples, and "any" refers to any one of the multiples.
[0019] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.
[0020] Before providing a detailed description of the embodiments of this application, some of the nouns and terms involved in the embodiments of this application will be explained first. The nouns and terms involved in the embodiments of this application are subject to the following interpretations.
[0021] This application provides a container compatibility method for application cluster deployment, relating to the field of information technology. This method can be applied to terminals, servers, or software running on either a terminal or server. In some embodiments, the terminal can be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, or in-vehicle terminal, but is not limited thereto. The server can be configured as an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The server can also be a node server in a blockchain network. The software can be an application implementing a container compatibility method for application cluster deployment, but is not limited to the above forms.
[0022] This application can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. Examples include: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, and distributed computing environments including any of the above systems or devices. This application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform specific tasks or implement specific abstract data types. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.
[0023] Figure 1 This is an optional flowchart of a container-compatible method for application cluster deployment provided in an embodiment of this application. Figure 1 The method may include, but is not limited to, steps S101 to S103.
[0024] Step S101: Obtain container instructions, and perform protocol conversion between the container instructions and the first preset mapping table to obtain initial deployment instructions; Step S102: Process the initial deployment instructions and preset configuration information to obtain compatible deployment instructions, and match the compatible deployment instructions with the current hardware information to determine the target node; Step S103: Create a container based on the target node and the compatibility deployment instructions to obtain a target compatible container, and deploy the application based on the target compatible container and the compatibility deployment instructions.
[0025] Steps S101 to S103 as illustrated in this embodiment involve receiving application deployment configurations submitted by users through a platform interface before containerizing the application. The platform interface verifies the application deployment configurations and triggers a scheduler based on the verification results. The scheduler generates corresponding container instructions and sends these instructions to a protocol conversion module via an interface. In this embodiment, an adapter plugin performs protocol conversion on the received instructions or data. The protocol conversion module determines the source type of the received container instructions and, based on the source type, calls a pre-set protocol mapping table to perform protocol conversion on the container instructions, obtaining instruction operations that the deployed application can recognize and process. Then, based on the submitted application deployment configuration, the converted instruction operations are extended with additional fields to obtain compatible deployment instructions, enabling containerized applications to call corresponding dedicated configurations and improving the adaptability of application containerization. The system filters and matches the obtained compatible deployment instructions with the system hardware information of the containerized cluster platform to obtain nodes suitable for deploying the application. The system then distributes the generated compatible deployment instructions to these nodes, which create corresponding application deployment containers. These application deployment containers download, install, and run the corresponding applications according to the distributed compatible deployment instructions.
[0026] Please see Figure 2 In some embodiments, the container-compatible method for application cluster deployment provided in this application may include, but is not limited to, steps S201 to S203: Step S201: Collect information from the target compatible container to obtain the container's basic status, and collect data according to the compatible deployment instructions to obtain system log data; Step S202: Integrate the container's basic state and system log data to obtain a state information set; Step S203: Perform protocol conversion based on the status information set and the second preset mapping table to obtain the target status code; and perform cluster synchronization based on the target status code.
[0027] In step S201 of some embodiments, after the system deploys the application in a containerized manner, it collects information such as the current status and running process of the container and the deployed application through the corresponding data acquisition module, and integrates the collected information data to obtain the basic status of the container; at the same time, it collects information on the running status of the container cluster through the data acquisition module, such as the running status of the hardware, the generation of containers, resource allocation, etc., as system log data.
[0028] In step S202 of some embodiments, the system integrates the previously collected container basic status data and system log data to obtain a comprehensive status information set, which facilitates the system to perform unified protocol conversion processing and generate status information that can be processed by the container cluster platform.
[0029] In step S203 of some embodiments, the system performs protocol conversion based on the integrated state information set and the preset second preset mapping table to obtain the corresponding target state code; after obtaining the target state code, the system performs cluster synchronization processing through the node communication network.
[0030] Please see Figure 3 In some embodiments, step S101 may include, but is not limited to, steps S301 to S303: Step S301: Match the container instruction with the first preset mapping table to determine the target mapping set; Step S302: Decompose the container instruction according to the target mapping set to obtain several sub-instructions; Step S303: Convert several sub-instructions according to the target mapping set to obtain several operation instructions, and use the several operation instructions as initial deployment instructions.
[0031] In step S301 of some embodiments, the system matches the received container instructions with a first preset mapping table in the system to determine the corresponding mapping information of each standard container instruction in the container instructions in the first preset mapping table. The mapping table includes the mapping relationship between container instructions and corresponding application operation instructions. The system integrates the matched mapping information to obtain a target mapping set.
[0032] In step S302 of some embodiments, the system decomposes the received container instructions based on the obtained target mapping set to obtain sub-instructions composed of multiple standard container instructions, so that the system can perform corresponding protocol conversion on the obtained multiple standard container instructions respectively, so that the subsequently deployed applications can run on the container cluster platform.
[0033] In step S303 of some embodiments, the system converts the standard container instructions according to the application operation instructions corresponding to the container instructions in the target mapping set, and integrates the converted multiple application operation instructions as the initial deployment instructions.
[0034] Please see Figure 4 In some embodiments, step S102 may include, but is not limited to, steps S401 to S402: Step S401: Parse the preset configuration information to obtain the deployment configuration file, and encapsulate the deployment configuration file according to the preset fields to obtain the extended fields; Step S402: Dynamically concatenate the extended fields and initial deployment instructions to obtain compatible deployment instructions.
[0035] In step S401 of some embodiments, after receiving the initial deployment instruction, the system parses the preset configuration information submitted by the user and extracts the deployment configuration file corresponding to the deployment application. The system uses the deployment configuration file as the exclusive configuration information of the deployment application, and generates corresponding extended fields according to the preset field design and the extracted deployment configuration file, which are used to call the corresponding configuration in subsequent application deployment and operation.
[0036] In step S402 of some embodiments, the system dynamically concatenates the obtained extended field with the previously obtained initial deployment instruction, and concatenates the extended field into the parameters of the initial deployment instruction to obtain the corresponding compatible deployment instruction.
[0037] Please see Figure 5 In some embodiments, step S203 may include, but is not limited to, steps S501 to S502: Step S501: Match the state information set with the second preset mapping table to determine several standard states; and decompose the state information set according to the several standard states to obtain several sub-state information. Step S502: Based on several standard states, several sub-state information are transformed to obtain several first state codes, and the several first state codes are integrated to obtain the target state code.
[0038] In step S501 of some embodiments, after the application completes container deployment, the system collects data from the deployed container cluster and system operation logs according to a preset data collection module and data collection frequency, and integrates them to obtain a corresponding status information set. The system matches the information status set with a preset second preset mapping table in the system to determine the corresponding standard status that the container cluster platform can handle. In this embodiment, the second preset mapping table includes the mapping relationship between information such as application status and system log data and the standard status that the container cluster platform can recognize. The system decomposes the integrated status information set according to the multiple standard statuses determined by the matching to obtain multiple subsets corresponding to the standard statuses.
[0039] In step S502 of some embodiments, the system performs protocol conversion on multiple subsets of data obtained from decomposition according to the standard state determined by matching, and obtains multiple corresponding first status codes; the system integrates the multiple first status codes to obtain a target status code for transmission and identification by the container cluster platform; in this embodiment, the protocol conversion of instructions sent by the container cluster platform to the deployment application is defined as a forward status conversion, and the reverse is defined as a reverse status conversion, that is, instructions or data information of the deployment application and system status uploaded to the container cluster platform.
[0040] Please see Figure 6 In some embodiments, the container-compatible method for application cluster deployment provided in this application may also include, but is not limited to, steps S601 to S602: Step S601: Collect multi-dimensional data from the target compatible container at a preset frequency to obtain system status data; and identify anomalies based on the system status data and preset identification rules to determine container operation information. Step S602: If the container running information is normal, return to execute multi-dimensional data collection on the target compatible container according to the preset frequency to obtain system status data; Step S603: If the container operation information indicates a container abnormality, parse the container operation information, determine the target abnormal container, and perform self-healing restart on the target abnormal container according to the preset pointer.
[0041] In step S601 of some embodiments, after the application is deployed in a containerized manner, the system starts a corresponding status acquisition thread. The thread collects multi-dimensional status data on information such as containers, application systems, application status, and system hardware, and integrates them to obtain system status data. The system identifies anomalies in the system status data according to the preset anomaly identification rules corresponding to the status data of different dimensions, such as the thread survival rate of the application status and the occupancy threshold in the system hardware. Through anomaly identification, the corresponding container status information of the container deployed by the application is determined.
[0042] In step S602 of some embodiments, if the system determines that the container status information is that the container is running normally through anomaly identification, the system continues to collect multi-dimensional status data on information such as container, application system, application status, and system hardware according to a preset data collection cycle or frequency, and performs anomaly identification on the collected data to achieve real-time monitoring of application deployment and container operation.
[0043] In step S603 of some embodiments, if the system determines that the container status information is abnormal through anomaly identification, the system triggers the integrated liveness probe and ready probe to restart the abnormal container in order to restore the abnormal container; in this embodiment, for containers that fail to restart continuously, the system performs node migration through the controller and realizes corresponding elastic resource allocation.
[0044] The following is a detailed description and explanation of the solutions in the embodiments of the present invention, using specific application examples: Please see Figure 7 , Figure 7 This is a schematic diagram of the structure of a compatibility adaptation system for a container compatibility method for application cluster deployment, applied in a specific embodiment of this application; according to Figure 7 As shown, the compatibility and adaptation system adopts a three-tiered architecture. The cluster management layer reuses native K3s / K8s capabilities, the node adaptation layer undertakes core adaptation responsibilities, and the container runtime layer provides the Waydroid runtime environment. Components at each level collaborate to achieve a complete compatibility management process. Specifically, the cluster management layer includes an API server, scheduler, controller, and Waydroid-specific CRDs, responsible for receiving configurations, scheduling nodes, and managing the lifecycle of multiple replicas. Its core function is to extend Android-specific configuration capabilities through CRDs. The node adaptation layer includes a CRI-LXC adaptation plugin, a Sidecar auxiliary container, and a state synchronization and anomaly detection module, acting as a "protocol translator." Together with a "feature adapter," it enables instruction conversion, application deployment, and state synchronization. The container runtime layer includes the LXC / LXD runtime, the Waydroid Android container, and a hardware resource pool. It is responsible for hosting the Android system and applications, responding to operation instructions from the node adaptation layer, and meeting the hardware dependency requirements of Android applications. This compatibility adaptation system includes a CRI-LXC bidirectional protocol conversion mechanism, a Waydroid-specific CRD configuration mechanism, a Sidecar-assisted adaptation mechanism, and a bidirectional state synchronization and exception self-healing mechanism. The CRI-LXC bidirectional protocol conversion mechanism achieves bidirectional conversion between K3s / K8s CRI instructions and LXC APIs through a lightweight adaptation plugin, resolving the runtime ecosystem fragmentation issue without requiring modification to the core code of either side. Please refer to [link / reference]. Figure 8 , Figure 8This is a flowchart illustrating the bidirectional conversion of CRI commands to the LXC API. Bidirectional conversion is achieved by deploying an adapter plugin, which is deployed as a Linux system service and registered as a CRI-compatible runtime using the `--cri-socket` parameter. This causes the cluster to mistakenly perceive it as a standard runtime (such as containerd). Forward conversion uses a built-in "CRI command-LXC API mapping table" to break down CRD commands into their corresponding native LXC operations. Reverse conversion uses `lxc-info` to collect the container's basic status and uses Waydroid... Shell commands retrieve the Android system status (e.g., sys.boot_completed), map it to CRI standard status codes, and synchronize it to the cluster. Simultaneously, the system automatically monitors K3s / K8s, Waydroid, and LXC versions, and has built-in multiple adaptation rules to address protocol differences, supporting cross-version compatibility. The Waydroid-specific CRD configuration mechanism extends the K3s / K8s resource model through custom resource definitions (CRDs), accurately describing the unique attributes of the Android container and resolving resource description mismatch issues. Core fields such as Android system version, pre-installed APK list, hardware dependencies, Binder communication switch, and data partition size are designed as CRD fields, supporting mandatory validation and enumeration restrictions, and these fields are appended to the command parameters of the converted LXC native operations. Based on the configuration information, during application deployment, the container supports configuring APK download address, package name, permissions, installation timeout, etc. through the `spec.apps` field, achieving standardized deployment of Android applications. Simultaneously, the container supports configuring GPU model, sensors, network interfaces, etc., through the `spec.hardwareRequirements` field, providing the scheduler with node selection criteria. Through this mechanism, the system also supports integration with Deployment / StatefulSet, enabling multi-replica deployment and rolling updates by referencing CRD configurations through resource declarations. The Sidecar auxiliary adaptation mechanism addresses specific needs such as automatic deployment of Android applications, Binder communication forwarding, and log collection through Sidecar containers deployed in the same Pod as the Waydroid container. Please refer to [link to relevant documentation]. Figure 9The system uses this mechanism to read the APK configuration in the CRD, download it, and install it via the `waydroid shell pm install` command. It supports overwrite updates and automatic permission granting, and reports the installation status in real time. After completing application installation and deployment, and the corresponding system configuration, the `waydroid binder pass` command maps the container's Binder communication to the node's network namespace, opening specified ports for cluster services to access, ensuring communication continuity. The system integrates the Fluent Bit component, splitting logs by application and forwarding them to the cluster log system. Logs can be viewed directly via the `kubectl logs` command, and 7 days of logs are retained for troubleshooting. Built on an Alpine image, the logs are ≤30MB in size and ≤30MB in memory usage, making it suitable for resource-constrained environments. Furthermore, the system improves operational stability through bidirectional state synchronization and anomaly self-healing mechanisms. Through a bidirectional synchronization logic of "active collection + passive query," combined with native cluster probes and controllers, it achieves container state visualization and automatic anomaly recovery. Please refer to [link to relevant documentation]. Figure 10 The system control status module collects basic container status (running / stopped / abnormal), Android system status (READY / UNREADY / Crashed), application status (INSTALLED / RUNNING), and hardware status (GPU / sensor availability) every second, integrates them, and synchronizes them to the cluster, thus achieving proactive data collection. Simultaneously, passive querying is configured as redundancy. Upon responding to commands such as `kubectl describe`, the system quickly calls the LXC API and Waydroid interface to return complete status information (including application list and crash log path). After collecting data, the system identifies anomalies based on rules such as status thresholds (CPU / memory usage), process liveness (system_server), and log error frequency, and reports them to the cluster event center in real time. Upon receiving the reported information, the system triggers integrated liveness probes and ready probes, triggering container restarts in case of anomalies. If consecutive restarts fail, the controller migrates the Pod, and combined with HPA, enables elastic resource scaling.
[0045] Before deploying an Android application through this system, the system receives a user-written WaydroidContainer CRD configuration file, specifying the Android version, APK address, GPU dependencies, and a 15Gi data partition, and saves it as waydroid-crd.yaml. Then, it executes `kubectl apply -f waydroid-crd.yaml` to submit the configuration. After the API server verifies the fields' validity, the scheduler is triggered. The scheduler reads the hardware dependencies in the CRD, selects nodes with GPUs and deployed LXC / Waydroid environments, and sends deployment instructions to the kubelet on the target node. The kubelet sends the instructions to the CRI-LXC adapter plugin via the CRI interface. After parsing the configuration, the plugin generates commands such as `lxc-create -n xxx --android-version 15 --storage-size 15Gi`, which call the LXC API to create the Waydroid container. Simultaneously, the Sidecar container starts, reads the APK configuration, downloads it to the shared storage volume, and executes `pm`. The system installs the Android application, grants it the appropriate permissions, and starts the Binder communication forwarding service and log collection. The system's state synchronization module collects the container state (RUNNING), Android state (READY), and application state (INSTALLED), converts them to CRI standard states, and synchronizes them to the cluster. Users can check the state as Ready using `kubectl getwaydroidcontainers`. The system monitors the running status of the deployed Android application system. If an Android system crash is detected (the `system_server` process disappears), the state module reports the abnormal event, and a failed liveness probe triggers a container restart. After restarting, the state returns to normal, and self-healing is complete. Simultaneously, the system periodically checks the application version. If an application version update is needed, the APK address in the CRD is modified and resubmitted. The Deployment controller triggers a rolling update, and the Sidecar automatically uninstalls the old version and installs the new version, ensuring uninterrupted business operations throughout the process.
[0046] The embodiments of this application include at least the following beneficial effects: This application provides a container-compatible method, system, electronic device, storage medium, and program product for application cluster deployment. This solution obtains container instructions and performs protocol conversion on the container instructions according to a first preset mapping table to obtain initial deployment instructions; it then performs configuration processing based on the initial deployment instructions and preset configuration information to obtain compatible deployment instructions; it performs matching analysis based on the compatible deployment instructions and current hardware technology to determine the target node for application cluster deployment, sends the compatible deployment instructions to the target node, and the target node creates a container according to the compatible deployment instructions to obtain a target compatible container. Finally, it deploys the corresponding application in the target compatible container according to the compatible deployment instructions, installing and running the corresponding application. Through protocol conversion, it achieves protocol conversion between different platforms and applications, expands the application's container cluster configuration, improves application compatibility, and thus improves the operational efficiency and flexibility of application cluster deployment.
[0047] Please see Figure 11 This application also provides a container-compatible system for application cluster deployment, which can implement the above-described method. The system includes: The conversion module is used to obtain container instructions, perform protocol conversion between the container instructions and a first preset mapping table, and obtain initial deployment instructions. The matching module is used to process the initial deployment instructions and preset configuration information to obtain compatible deployment instructions, and to match the compatible deployment instructions with the current hardware information to determine the target node; The deployment module is used to create a container based on the target node and the compatible deployment instructions to obtain a target compatible container, and to deploy the application based on the target compatible container and the compatible deployment instructions.
[0048] It is understood that the content of the above method embodiments is applicable to the present device embodiments. The specific functions implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.
[0049] This application also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the above-described method. This electronic device can be any smart terminal, including tablet computers, in-vehicle computers, etc.
[0050] It is understood that the content of the above method embodiments is applicable to this device embodiment. The specific functions implemented by this device embodiment are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.
[0051] Please see Figure 12 , Figure 12 The hardware structure of an electronic device according to another embodiment is illustrated. The electronic device includes: The processor 1201 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application. The memory 1202 can be implemented as a read-only memory (ROM), static storage device, dynamic storage device, or random access memory (RAM). The memory 1202 can store the operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 1202 and is called and executed by the processor 1201 using the methods described in the embodiments of this application. The input / output interface 1203 is used to implement information input and output; The communication interface 1204 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.). Bus 1205 transmits information between various components of the device (e.g., processor 1201, memory 1202, input / output interface 1203, and communication interface 1204); The processor 1201, memory 1202, input / output interface 1203 and communication interface 1204 are connected to each other within the device via bus 1205.
[0052] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method.
[0053] It is understood that the content of the above method embodiments is applicable to this storage medium embodiment. The specific functions implemented in this storage medium embodiment are the same as those in the above method embodiments, and the beneficial effects achieved are also the same as those achieved in the above method embodiments.
[0054] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.
[0055] It is understood that the content of the above method embodiments is applicable to the embodiments of this program product. The specific functions implemented by the embodiments of this program product are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.
[0056] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
[0057] The embodiments described in this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.
[0058] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of this application, and may include more or fewer steps than shown, or combine certain steps, or different steps.
[0059] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.
[0060] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.
[0061] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0062] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.
[0063] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of the units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0064] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0065] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0066] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, 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. This computer software product is stored in a storage medium and includes multiple instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing programs, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0067] The preferred embodiments of the present application have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of the embodiments of the present application shall be within the scope of the claims of the present application.
Claims
1. A container-compatible method for application cluster deployment, characterized in that, The method includes: Obtain container instructions, and perform protocol conversion between the container instructions and the first preset mapping table to obtain initial deployment instructions; The initial deployment instructions and preset configuration information are processed to obtain compatible deployment instructions. The compatible deployment instructions are then matched with the current hardware information to determine the target node. A container is created based on the target node and the compatible deployment instructions to obtain a target compatible container, and the application is deployed based on the target compatible container and the compatible deployment instructions.
2. The method according to claim 1, characterized in that, The method further includes: Information is collected from the target compatible container to obtain the container's basic status, and data is collected according to the compatible deployment instructions to obtain system log data; The container's basic state and the system log data are integrated to obtain a state information set; The protocol is converted according to the state information set and the second preset mapping table to obtain the target state code; and the cluster is synchronized according to the target state code.
3. The method according to claim 1, characterized in that, The step of performing protocol conversion based on the container instructions and the first preset mapping table to obtain the initial deployment instructions specifically includes: The target mapping set is determined by matching the container instructions with the first preset mapping table. The container instruction is decomposed according to the target mapping set to obtain several sub-instructions; The sub-instructions are transformed according to the target mapping set to obtain several operation instructions, and these operation instructions are used as the initial deployment instructions.
4. The method according to claim 1, characterized in that, The process of processing the initial deployment instructions and preset configuration information to obtain compatible deployment instructions specifically includes: The preset configuration information is parsed to obtain a deployment configuration file, and the deployment configuration file is encapsulated according to preset fields to obtain extended fields; The compatible deployment instruction is obtained by dynamically concatenating the extended fields and the initial deployment instruction.
5. The method according to claim 2, characterized in that, The step of performing protocol conversion based on the state information set and the second preset mapping table to obtain the target state code specifically includes: The state information set is matched with the second preset mapping table to determine several standard states; and the state information set is decomposed according to the several standard states to obtain several sub-state information. The sub-state information is transformed according to the standard states to obtain the first state codes, and the first state codes are integrated to obtain the target state code.
6. The method according to claim 1, characterized in that, The method further includes: The target compatible container is subjected to multi-dimensional data collection at a preset frequency to obtain system status data; and anomaly identification is performed based on the system status data and preset identification rules to determine the container operation information. If the container operation information indicates normal operation, return to the step of performing multi-dimensional data collection on the target compatible container at a preset frequency to obtain system status data; If the container operation information indicates a container abnormality, the container operation information is parsed to determine the target abnormal container, and the target abnormal container is self-healed and restarted according to a preset pointer.
7. A container-compatible system for clustered application deployment, characterized in that, The system includes: The conversion module is used to obtain container instructions, perform protocol conversion between the container instructions and a first preset mapping table, and obtain initial deployment instructions. The matching module is used to process the initial deployment instructions and preset configuration information to obtain compatible deployment instructions, and to match the compatible deployment instructions with the current hardware information to determine the target node; The deployment module is used to create a container based on the target node and the compatible deployment instructions to obtain a target compatible container, and to deploy the application based on the target compatible container and the compatible deployment instructions.
8. An electronic device, characterized in that, include: At least one processor; At least one memory for storing at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements the method as described in any one of claims 1 to 6.
9. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1 to 6.
10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1 to 6.