Containerized deployment method and system for hardware control application

Abstract

The invention provides a containerized deployment method and system for a hardware control application. A containerized deployment platform constructs a deployment template library and a deployment resource library in advance; when deployment is prepared, a user constructs a standardized CRD template containing templates and resource parameters required by business application deployment, and packages the CRD template into a business packet and sends the business packet to the platform control center; the platform control center analyzes the CRD template, calls a deployment template and deployment resources, registers events needing to be monitored and interfaces needing to be called of business applications, and displays necessary parameters needing to be filled in on a visual interface; and finally, the user fills in parameters on the visual interface, and the platform control center carries out deployment template assembly and service application final deployment. Through a general service application deployment method of'parameter structured definition + interface dynamic generation + general deployment template driving ', the method is suitable for various industrial services, and the deployment efficiency and the system maintainability are improved.

Description

Technical Field

[0001] This invention belongs to the field of industrial automation and intelligent control, and in particular relates to a containerized deployment method and system for hardware control applications. Background Technology

[0002] With the advancement of intelligent manufacturing in industry, the concept of a Universal Control System (UCS) has been proposed, aiming to reduce costs by cloudifying all hardware controllers and related business applications in industry. However, in industrial scenarios, the cloudification of industrial business applications also brings certain installation and deployment difficulties. The definitions of deployment parameters vary greatly for each type of business application, and the deployment process also suffers from problems such as strong customization, poor portability, and inconsistent parameters.

[0003] Existing patent CN120872358A discloses a component deployment method, apparatus, and deployment tool for a software platform, which can improve deployment efficiency. The component deployment method for the software platform includes: generating a preset parameter template and parameter optimization scheme based on the historical implementation data of the target component; mapping the preset parameter template and parameter optimization scheme into graphical buttons and dropdown menus to generate a graphical deployment tool; deploying the graphical deployment tool into the implementation environment, and simultaneously installing the download source of the deployment medium during the deployment process; wherein the implementation environment includes a test environment and a tool environment; and deploying the target component into the implementation environment based on the graphical deployment tool. Summary of the Invention

[0004] Currently, although Kubernetes, a commonly used business application deployment platform in production environments, provides CRDs (Custom Resource Definitions) to extend native resource types, in actual industrial systems, CRDs are mostly used as operation and maintenance interfaces and lack a standardized, structured description mechanism, making it difficult to achieve visualized deployment and templated abstraction at the business application level. The lack of a unified framework and common template parameter definitions leads to repeated development of deployment processes for different business applications, resulting in high maintenance costs and a high rate of configuration errors.

[0005] To address the aforementioned technical problems, the present invention provides a method for containerized deployment of hardware control applications, comprising the following steps: S1, a containerized deployment platform that builds deployment template libraries and deployment resource libraries; S2. Users build standardized CRD templates containing templates and resource parameters required for business application deployment, and package the CRD templates into business packages and send them to the platform control center. S3. The platform control center parses the CRD template, retrieves the business application deployment template and deployment resources, registers the events that the business application needs to monitor and the interfaces that need to be called, and displays the necessary parameters that need to be filled in on the visual interface. S4. Users fill in parameters on the visual interface, and the platform control center assembles the deployment template and finally deploys the business application.

[0006] Specifically, the deployment resource library built by the containerized deployment platform in S1 includes the visual controls required by various business applications. The platform control center framework ultimately renders these controls for interface display.

[0007] Specifically, the CRD templates built by users in S2 also include the specific parameters of the visual controls required by the business application, as well as the monitoring events and running logic between the various controls.

[0008] Specifically, in S2, when users build standardized CRD templates, they uniformly use the description field of the business application to save the templates and resource parameters required for the deployment of the business application.

[0009] Specifically, after the S3 platform control center parses the CRD template, it restarts the application monitoring tool. After restarting, the application monitoring tool registers with the API interface control center the events that the business application deployment needs to monitor and the interfaces that need to be called, which are contained in the CRD template.

[0010] Specifically, in S4, after users fill in the parameters required for deploying business applications in the visual interface, the application monitoring tool automatically assembles and generates a complete business application template file based on the necessary parameters, the retrieved deployment template, deployment resources, and registered events and interfaces. This template file is then applied to the containerized platform cluster to complete the automated deployment of business applications.

[0011] Specifically, a complete business application template file covers all resource definitions and dependency configurations required for business application deployment.

[0012] This invention also provides a containerized deployment system for hardware control applications, using the aforementioned containerized deployment method for hardware control applications. The system includes a containerized deployment platform with a built-in deployment template library and deployment resource library. The containerized deployment platform has a platform control center. The platform control center receives service packages sent by the service application deployment template generation module, parses the CRD templates in the service packages, and retrieves the templates and resources required for service application deployment from the containerized deployment platform. The platform control center also has a visual interface for user interaction to fill in necessary parameters for service application deployment. Furthermore, the platform control center includes an application monitoring tool that assembles and generates complete service application template files and registers the events and interfaces required by the service application with the API interface control center.

[0013] Specifically, the application monitoring tool manages all business applications on the containerized deployment platform according to standardized processes.

[0014] Specifically, the API interface control center serves as the hub for internal and external interactions within the containerized deployment platform cluster, managing the interaction interfaces and resource operation requests of all business applications on the containerized deployment platform.

[0015] The beneficial effects of this invention are: it transforms cumbersome configuration files into parameterized forms, allowing users to complete application deployment simply by filling in business application parameters, avoiding direct manipulation of underlying configuration files; a general-purpose template rendering engine is used for deployment orchestration, forming a "parameter-driven deployment template" mechanism, reducing the repetitiveness of template writing; it dynamically parses parameters in CRD templates and automatically generates parameter input interfaces, forming a "low-code / zero-code" deployment interface generation method, greatly improving the platform's scalability; it allows users to use their existing engineering experience and operating habits without needing to master the underlying resource definitions and dependencies of the containerized deployment platform, thereby significantly reducing learning costs and improving system availability. Attached Figure Description

[0016] Figure 1 This is a flowchart of the method of the present invention. Detailed Implementation

[0017] The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0018] Example 1: A method for containerizing and deploying hardware control applications, comprising the following steps: S1, a containerized deployment platform that builds deployment template libraries and deployment resource libraries; S2. Users build standardized CRD templates containing templates and resource parameters required for business application deployment, and package the CRD templates into business packages and send them to the platform control center. S3. The platform control center parses the CRD template, retrieves the business application deployment template and deployment resources, registers the events that the business application needs to monitor and the interfaces that need to be called, and displays the necessary parameters that need to be filled in on the visual interface. S4. Users fill in parameters on the visual interface, and the platform control center assembles the deployment template and finally deploys the business application.

[0019] The deployment resource library built by the containerized deployment platform in S1 includes visual controls required by various business applications, such as input boxes, selection boxes, drop-down boxes, password boxes, radio buttons, etc. The platform control center framework ultimately renders these controls for interface display.

[0020] In S2, the CRD templates built by users also include specific parameters of the visual controls required by the business application, as well as monitoring events and operational logic between the various controls. Different business applications can define different business application parameter fields according to the same preset CRD template. When building a standardized CRD template, the template and resource parameters required for business application deployment are uniformly saved through the description field of the business application. This design transforms the cumbersome business application configuration files into parameterized forms in the CRD template. Users only need to fill in the business application parameters to complete the application deployment, avoiding direct manipulation of the underlying configuration files. This allows users to use their existing engineering experience and operating habits without having to understand the underlying resource definitions and dependencies of the containerized deployment platform, thus significantly reducing the learning cost and improving system availability. At the same time, users only need to write the relevant parameter information for the CRD template. Subsequent business application deployment and configuration are automated by the platform control center. The containerized deployment platform automatically retrieves relevant resources from the deployment template library and deployment resource library to perform automated container deployment. The overall business application deployment speed is faster and the operation is simpler for users. This standardized process is suitable for the deployment of diverse business applications in the industrial field, balancing automation and pluggability, and greatly improving the platform's scalability.

[0021] After parsing the CRD template, the S3 platform control center restarts the application monitoring tool. Upon restart, the application monitoring tool registers the events and API calls required for monitoring the business application deployment contained in the CRD template with the API interface control center. The application monitoring tool is a module in the containerized deployment platform that automates the deployment, operation, and lifecycle management of applications. The API interface control center is a core component of the containerized deployment platform cluster, acting as the front end of the control plane, handling all API requests, and serving as the hub for internal and external interactions within the cluster. Using the application monitoring tool and the API interface control center for unified management of the entire lifecycle of business application deployment, and controlling the deployment of all business applications according to standard processes, is more suitable for the diverse business application deployments in the industrial sector, balancing automation and pluggability.

[0022] After parsing the CRD template, the platform control center displays the necessary parameters (such as site address, domain address, IP address, etc.) required for business application deployment on a visual interface. In S4, after users fill in the required parameters on the visual interface, the application monitoring tool automatically assembles and generates a complete business application template file based on these parameters, retrieving the deployment template, deployment resources, and registered events and interfaces. This template file is then applied to the containerized platform cluster, completing the automated deployment of the business application. In this way, engineering users no longer need to directly write and maintain cumbersome configuration files; instead, they indirectly drive the platform control center's deployment process by filling in parameters through the visual interface, achieving efficient, low-barrier, and standardized application delivery. The management center platform dynamically parses the parameters in the CRD template and automatically generates a parameter input interface, forming a "low-code / zero-code" deployment interface generation method, greatly improving the platform's scalability.

[0023] A complete business application template file covers all resource definitions and dependency configurations required for business application deployment. The application monitoring tool includes a general template rendering engine for deployment orchestration, forming a "parameter-driven deployment template" mechanism that reduces the repetitiveness of template writing.

[0024] This embodiment also provides a containerized deployment system for hardware control applications, including a containerized deployment platform with a built-in deployment template library and deployment resource library. The containerized deployment platform has a platform control center, which receives business packages sent by the business application deployment template generation module, parses the CRD templates in the business packages, and retrieves the templates and resources required for business application deployment from the containerized deployment platform. The platform control center also has a visual interface for users to interactively fill in the necessary parameters for business application deployment. The platform control center also has an application monitoring tool that assembles and generates complete business application template files and registers the events and interfaces required by the business application with the API interface control center.

[0025] This embodiment transforms cumbersome configuration files into parameterized forms, allowing users to complete application deployment simply by filling in business application parameters, avoiding direct manipulation of underlying configuration files. A general template rendering engine is used for deployment orchestration, forming a "parameter-driven deployment template" mechanism that reduces the repetitiveness of template writing. Parameters in the CRD template are dynamically parsed, automatically generating parameter input interfaces, resulting in a "low-code / zero-code" deployment interface generation method, greatly enhancing the platform's scalability. Users can leverage their existing engineering experience and operating habits without needing to understand the underlying resource definitions and dependencies of the containerized deployment platform, thus significantly reducing learning costs and improving system availability.

[0026] Example 2: A method for containerizing and deploying hardware control applications, comprising the following steps: S1, a containerized deployment platform that builds deployment template libraries and deployment resource libraries; S2. Users build standardized CRD templates containing templates and resource parameters required for business application deployment, and package the CRD templates into business packages and send them to the platform control center. S3. The platform control center parses the CRD template, retrieves the business application deployment template and deployment resources, registers the events that the business application needs to monitor and the interfaces that need to be called, and displays the necessary parameters that need to be filled in on the visual interface. S4. Users fill in parameters on the visual interface, and the platform control center assembles the deployment template and finally deploys the business application.

[0027] The deployment resource library built by the containerized deployment platform in S1 includes visual controls required by various business applications, such as input boxes, selection boxes, drop-down boxes, password boxes, radio buttons, etc. The platform control center framework ultimately renders these controls for interface display.

[0028] In S2, the CRD templates built by users also include specific parameters of the visual controls required by the business application, as well as monitoring events and operational logic between the various controls. Different business applications can define different business application parameter fields according to the same preset CRD template. When building a standardized CRD template, the template and resource parameters required for business application deployment are uniformly saved through the description field of the business application. This design transforms the cumbersome business application configuration files into parameterized forms in the CRD template. Users only need to fill in the business application parameters to complete the application deployment, avoiding direct manipulation of the underlying configuration files. This allows users to use their existing engineering experience and operating habits without having to understand the underlying resource definitions and dependencies of the containerized deployment platform, thus significantly reducing the learning cost and improving system availability. At the same time, users only need to write the relevant parameter information for the CRD template. Subsequent business application deployment and configuration are automated by the platform control center. The containerized deployment platform automatically retrieves relevant resources from the deployment template library and deployment resource library to perform automated container deployment. The overall business application deployment speed is faster and the operation is simpler for users. This standardized process is suitable for the deployment of diverse business applications in the industrial field, balancing automation and pluggability, and greatly improving the platform's scalability.

[0029] After parsing the CRD template, the S3 platform control center restarts the application monitoring tool. Upon restart, the application monitoring tool registers the events and API calls required for monitoring the business application deployment contained in the CRD template with the API interface control center. The application monitoring tool is a module in the containerized deployment platform that automates the deployment, operation, and lifecycle management of applications. The API interface control center is a core component of the containerized deployment platform cluster, acting as the front end of the control plane, handling all API requests, and serving as the hub for internal and external interactions within the cluster. Using the application monitoring tool and the API interface control center for unified management of the entire lifecycle of business application deployment, and controlling the deployment of all business applications according to standard processes, is more suitable for the diverse business application deployments in the industrial sector, balancing automation and pluggability.

[0030] After parsing the CRD template, the platform control center displays the necessary parameters (such as site address, domain address, IP address, etc.) required for business application deployment on a visual interface. In S4, after users fill in the required parameters on the visual interface, the application monitoring tool automatically assembles and generates a complete business application template file based on these parameters, retrieving the deployment template, deployment resources, and registered events and interfaces. This template file is then applied to the containerized platform cluster, completing the automated deployment of the business application. In this way, engineering users no longer need to directly write and maintain cumbersome configuration files; instead, they indirectly drive the platform control center's deployment process by filling in parameters through the visual interface, achieving efficient, low-barrier, and standardized application delivery. The management center platform dynamically parses the parameters in the CRD template and automatically generates a parameter input interface, forming a "low-code / zero-code" deployment interface generation method, greatly improving the platform's scalability.

[0031] A complete business application template file covers all resource definitions and dependency configurations required for business application deployment. The application monitoring tool includes a general template rendering engine for deployment orchestration, forming a "parameter-driven deployment template" mechanism that reduces the repetitiveness of template writing.

[0032] This embodiment also provides a containerized deployment system for hardware control applications, including a containerized deployment platform with a built-in deployment template library and deployment resource library. The containerized deployment platform has a platform control center, which receives business packages sent by the business application deployment template generation module, parses the CRD templates in the business packages, and retrieves the templates and resources required for business application deployment from the containerized deployment platform. The platform control center also has a visual interface for users to interactively fill in the necessary parameters for business application deployment. The platform control center also has an application monitoring tool that assembles and generates complete business application template files and registers the events and interfaces required by the business application with the API interface control center.

[0033] This embodiment transforms cumbersome configuration files into parameterized forms, allowing users to complete application deployment simply by filling in business application parameters, avoiding direct manipulation of underlying configuration files. A general template rendering engine is used for deployment orchestration, forming a "parameter-driven deployment template" mechanism that reduces the repetitiveness of template writing. Parameters in the CRD template are dynamically parsed, automatically generating parameter input interfaces, resulting in a "low-code / zero-code" deployment interface generation method, greatly enhancing the platform's scalability. Users can leverage their existing engineering experience and operating habits without needing to understand the underlying resource definitions and dependencies of the containerized deployment platform, thus significantly reducing learning costs and improving system availability.

[0034] In this specific application, the Kubernetes environment is used as the containerized deployment platform. Kubernetes is an open-source container orchestration platform used to automate the deployment, scaling, and management of containerized applications. It originated from Google's internal Borg system and aims to simplify the deployment and management process of containerized applications. Kubernetes has built-in CRD (Custom Resource Definition) templates for configuring built-in Kubernetes resources. Kubernetes uses AppOperator as the application monitoring tool. AppOperator is responsible for managing the service framework that creates application software, such as creating software controllers, configuring, and monitoring application services.

[0035] Kubernetes uses the APIServer as its API interface control center. The APIServer is a core component of the Kubernetes cluster, acting as the front end of the control plane, handling all RESTful API requests, and serving as a hub for internal and external cluster interactions. All operations on Kubernetes resources (such as creating, modifying, and deleting Pods, Services, Deployments, etc.) are performed through the APIServer. Users send requests via the kubectl command-line tool or client libraries, which the APIServer translates into internal operation commands. Cluster components (such as the Controller Manager, Scheduler, and kubelet) share state and communicate through the APIServer. For example, the scheduler obtains node resource information through the APIServer and allocates Pods to appropriate nodes. The APIServer supports multiple authentication methods (such as TLS certificates, tokens, and username / password) to verify the identity of the request initiator. Based on the RBAC (Role-Based Access Control) mechanism, it checks whether the user has permission to execute the requested operation (such as creating a Pod or modifying configuration). Additional validation and modifications are performed on the request (such as canonical value writing and rate limiting) to ensure that the operation conforms to cluster specifications. It supports plug-in extensions, such as Mutating Webhook (modifying object values) and Validating Webhook (validating object values).

[0036] AppOperator is responsible for installing, updating, monitoring, and maintaining applications in a Kubernetes cluster, ensuring that applications meet expectations. For example, it manages application versions, replica counts, storage volumes, and other resources through declarative configuration. AppOperator can define application configurations via YAML files or Helm Charts and complete deployment with a single click. It also performs status monitoring, checking application health in real time and automatically restarting or rescheduling failed containers; it manages elastic scaling, automatically adjusting the number of application instances based on load to optimize resource utilization. Furthermore, AppOperator is responsible for upgrading business applications in Kubernetes, supporting rolling updates, blue-green deployments, and other strategies to ensure zero downtime during upgrades; it also has self-healing capabilities, automatically handling common errors (such as full disks or exhausted connection pools) to reduce manual intervention.

[0037] In the actual implementation process, business applications define CRDs and deploy related templates according to actual needs. At the same time, a description field is added to each parameter in the CRD template to define the parameters of the visual control.

[0038] Business applications package custom CRD templates, deployment templates, and business application images into a business package, upload the business package through the platform control center, and the platform control center backend parses the CRD template parameters and automatically applies the corresponding CRD resources to the target cluster to define the custom resource types required by the business application.

[0039] After the user uploads the business package, it will trigger the AppOperator to restart. When it starts, the AppOperator will register with the APIServer all the CRD information events of the business application that it needs to care about, so as to trigger the deployment job to complete the deployment of the business application.

[0040] Users can access the installation and deployment function for a specific business application in the management center's visual interface. They fill in the necessary parameters for deployment (e.g., site address, domain address, IP address, etc.). At this point, users can also confirm the final visual effect of the deployed application. If issues arise, the deployment can be interrupted, and the CRD template can be redefined. After completing the necessary parameters and confirming the deployment, the user sends the deployment request to the platform control center backend. The AppOperator component in the platform control center backend then assembles the specific business application template parameters.

[0041] When AppOperator detects the creation of a new business application, it receives Kubernetes event callbacks, retrieves the parameter information from these callbacks, and automatically assembles a complete Kubernetes YAML template file based on these parameters. This YAML template file covers all resource definitions and dependency configurations required for the business application deployment. AppOperator then applies this file to the cluster, thereby completing the automated deployment of the business application.

[0042] In this way, engineering users no longer need to write and maintain cumbersome YAML files themselves. Instead, they can indirectly drive the deployment process of business applications by filling in parameters through a visual interface, thus achieving efficient, low-threshold, and standardized application delivery.

[0043] This embodiment transforms the cumbersome Kubernetes YAML configuration into a parameterized form. Users only need to fill in the business application parameters to complete application deployment, avoiding direct manipulation of the underlying configuration files. A template rendering engine is used for deployment orchestration, forming a "parameter-driven deployment template" mechanism, reducing the repetitive nature of template writing. The management center platform dynamically parses the parameters in the CRD template and automatically generates the parameter input interface, forming a "low-code / zero-code" deployment interface generation method, greatly improving the platform's scalability. This embodiment allows users to leverage existing engineering experience and operating habits without needing to master the underlying Kubernetes resource definitions and dependencies, thus significantly reducing the learning cost and improving system availability.

Claims

1. A method for containerizing and deploying hardware control applications, characterized in that, Includes the following steps: S1, a containerized deployment platform that builds a deployment template library and deployment resource library for hardware control business applications; S2. Users construct standardized CRD templates containing templates and resource parameters required for deploying hardware control business applications, and package the CRD templates into business packages and send them to the platform control center. S3. The platform control center parses the CRD template, retrieves the deployment templates and resources required by the business application, registers the events that the business application needs to monitor and the interfaces that need to be called, and displays the necessary parameters that need to be filled in on the visual interface. S4. Users fill in parameters on the visual interface, and the platform control center assembles the deployment template and performs the final deployment of the business application.

2. The containerized deployment method for hardware control applications according to claim 1, characterized in that, The deployment resource library built by the containerized deployment platform in S1 includes visual controls required by various business applications. The platform control center framework ultimately renders these controls for interface display.

3. The containerized deployment method for hardware control applications according to claim 1, characterized in that, The CRD templates built by users in S2 also include the specific parameters of the visual controls required by the business application, as well as the monitoring events and running logic between the various controls.

4. The containerized deployment method for hardware control applications according to claim 1 or 2, characterized in that, In S2, when users build standardized CRD templates, the description field of the business application is used to save the templates and resource parameters required for the deployment of the business application.

5. The containerized deployment method for hardware control applications according to claim 1, characterized in that, After the S3 platform control center parses the CRD template, it restarts the application monitoring tool. After restarting, the application monitoring tool registers with the API interface control center the events that need to be monitored and the interfaces that need to be called for the business deployment contained in the CRD template.

6. The containerized deployment method for hardware control applications according to claim 1, characterized in that, In S4, after users fill in the parameters required for deploying business applications in the visual interface, the application monitoring tool automatically assembles and generates a complete business application template file based on the necessary parameters, the retrieved deployment template, deployment resources, and registered events and interfaces. This template file is then applied to the containerized platform cluster to complete the automated deployment of business applications.

7. The containerized deployment method for hardware control applications according to claim 6, characterized in that, A complete business application template file covers all resource definitions and dependency configurations required for business application deployment.

8. A containerized deployment system for hardware control applications, using the containerized deployment method for hardware control applications according to any one of claims 1-7, characterized in that, The containerized deployment platform includes a built-in deployment template library and deployment resource library. The platform control center receives business packages sent by the deployment template generation module, parses the CRD templates within the business packages, and retrieves the templates and resources required for business application deployment from the containerized deployment platform. The platform control center also features a visual interface for users to interact with and fill in necessary business deployment parameters. Furthermore, the platform control center includes application monitoring tools that assemble and generate complete business application template files and register the events and interfaces required by the business application with the API interface control center.

9. The hardware control application containerized deployment system according to claim 8, characterized in that, Application monitoring tools manage all business applications on the containerized deployment platform according to standardized processes.

10. The hardware control application containerization deployment system according to claim 8, characterized in that, The API interface control center serves as the hub for internal and external interactions within the containerized deployment platform cluster, managing the interaction interfaces and resource operation requests of all business applications on the containerized deployment platform.

Images