Container scheduling and deployment method, device, and domain controller system

Abstract

The application provides a container scheduling and deployment method and device and a domain controller system, and relates to the field of communication. The container scheduling and deployment method comprises the following steps: if the current application environment of the domain controller system is a formal environment, then based on the domain controller node of the domain controller system, the container corresponding to the domain controller node is scheduled and deployed; if the current application environment of the domain controller system is a development and test environment, then based on the remote server of the domain controller system, the container corresponding to the domain controller node is scheduled and deployed. Through the scheme in the application, different subjects can be flexibly selected to schedule and deploy the container of the domain controller node for different application environments, so as to complete the dynamic management of the domain controller system and guarantee the high expansibility and high availability of the domain controller system.

Description

Technical Field

[0001] This application relates to the field of communication technology, specifically to a container scheduling and deployment method, apparatus, and domain controller system. Background Technology

[0002] Container technology is a kernel-lightweight operating system-level virtualization technology that isolates processes and resources. Compared to traditional virtualization technologies, which are cumbersome in terms of environment creation, application deployment, and application portability, container technology can easily achieve flexible migration and deployment across various environments.

[0003] However, the current container scheduling and deployment methods within the domain controller system cannot achieve load balancing for containers within the domain controller, nor can they dynamically adjust the allocation and deployment of containers within the domain controller. This results in a degraded user experience for a particular node within the domain controller under high load, and also affects the performance of the entire domain controller system. Summary of the Invention

[0004] To address the aforementioned technical problems, this application is proposed. Embodiments of this application provide a container scheduling and deployment method, apparatus, and domain controller system.

[0005] In a first aspect, one embodiment of this application provides a container scheduling and deployment method applied to a vehicle domain controller system. The method includes: if the current application environment of the domain controller system is a production environment, then scheduling and deploying containers corresponding to the domain controller nodes based on the domain controller nodes of the domain controller system; if the current application environment of the domain controller system is a development and testing environment, then scheduling and deploying containers corresponding to the domain controller nodes based on the remote server of the domain controller system.

[0006] In conjunction with the first aspect, in some implementations of the first aspect, the containers corresponding to the domain controller nodes of the domain controller system are scheduled and deployed, including: based on the current operating status of the domain controller system, the containers corresponding to the domain controller nodes are expanded or reduced in size using the domain controller nodes.

[0007] In conjunction with the first aspect, in some implementations of the first aspect, based on the domain controller node of the domain controller system, the containers corresponding to the domain controller node are scheduled and deployed, including: if the container corresponding to the domain controller node is a failed container, the failed container is deleted using the domain controller node, and a new container corresponding to the failed container is created.

[0008] In conjunction with the first aspect, in some implementations of the first aspect, the remote server of the domain controller system schedules and deploys containers corresponding to the domain controller nodes, including: based on the usage scenario of the domain controller system, the remote server distributes container applications corresponding to the usage scenario to the domain controller nodes of the domain controller system so that the domain controller nodes can complete the application deployment.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, the container uses the containerd container, which is used to decouple functional components within a domain controller node.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the container adopts the K3s deployment method.

[0011] Secondly, one embodiment of this application provides a container scheduling and deployment device applied to a vehicle domain controller system. The device includes: a first scheduling and deployment module, used to schedule and deploy containers corresponding to domain controller nodes based on the domain controller nodes of the domain controller system if the current application environment of the domain controller system is a production environment; and a second scheduling and deployment module, used to schedule and deploy containers corresponding to domain controller nodes based on a remote server of the domain controller system if the current application environment of the domain controller system is a development and testing environment.

[0012] Thirdly, one embodiment of this application provides a domain controller system, including: a domain controller node, used to schedule and deploy containers corresponding to the domain controller node when the current application environment of the domain controller system is a production environment; and a remote server, used to schedule and deploy containers corresponding to the domain controller node when the current application environment of the domain controller system is a development and testing environment.

[0013] In conjunction with the third aspect, in some implementations of the third aspect, the domain controller system also includes: a storage server, which is used to store containers.

[0014] Fourthly, one embodiment of this application provides a computer-readable storage medium storing a computer program for executing the container scheduling and deployment method described in the first aspect.

[0015] Fifthly, one embodiment of this application provides an electronic device, the electronic device comprising: a processor; a memory for storing processor-executable instructions; the processor being configured to execute the container scheduling and deployment method described in the first aspect.

[0016] The container scheduling and deployment method provided in this application embodiment schedules and deploys containers corresponding to domain controller nodes based on the domain controller nodes when the current application environment of the domain controller system is a production environment; and schedules and deploys containers corresponding to domain controller nodes based on the remote server of the domain controller system when the current application environment of the domain controller system is a development and testing environment. Through the technical solution in this application embodiment, the scheduling and deployment of containers on domain controller nodes at different application stages is realized, achieving dynamic adjustment of the domain controller system and ensuring its high scalability and high availability performance. Attached Figure Description

[0017] The above and other objects, features, and advantages of this application will become more apparent from the more detailed description of the embodiments of this application in conjunction with the accompanying drawings. The drawings are provided to further illustrate the embodiments of this application and form part of the specification. They are used together with the embodiments of this application to explain this application and do not constitute a limitation thereof. In the drawings, the same reference numerals generally represent the same components or steps.

[0018] Figure 1 The diagram shown is a scenario applicable to an embodiment of this application.

[0019] Figure 2 The diagram shown is a flowchart illustrating a container scheduling and deployment method provided in an exemplary embodiment of this application.

[0020] Figure 3 The above is a schematic diagram illustrating the process of scheduling and deploying containers corresponding to domain controller nodes, provided as an exemplary embodiment of this application.

[0021] Figure 4 The diagram shown is a structural schematic of a container scheduling and deployment apparatus provided in an exemplary embodiment of this application.

[0022] Figure 5 The diagram shown is a schematic diagram of the structure of a domain controller system provided in an exemplary embodiment of this application.

[0023] Figure 6 The diagram shown is a schematic representation of the structure of a domain controller system provided in another exemplary embodiment of this application.

[0024] Figure 7 The diagram shown is a structural schematic of an electronic device provided in an embodiment of this application. Detailed Implementation

[0025] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0026] Application Overview

[0027] A cluster is a group of independent computers, where each cluster node is an independent server running its own services.

[0028] Orchestration, based on the coupling relationships between deployed objects and the dependencies of the deployed object's environment, specifies the execution order of each task in the deployment process, the storage location and retrieval method of the dependency files required during deployment, and how to verify successful deployment.

[0029] Deployment: Following the content and process specified in the orchestration, the environment initialization specified in the orchestration is performed on the target machine, the specified dependencies and files are stored, the specified deployment actions are run, and finally the deployment is confirmed to be successful according to the rules in the orchestration.

[0030] The importance of container scheduling and deployment methods to domain controller systems is self-evident. In related technologies, Docker-related commands are typically installed on the storage servers of the storage cluster, the storage servers are hierarchically divided, and Docker images are pushed to each level of storage servers according to the hierarchical division, as well as Docker container creation and start requests are sent to each level of storage servers. The storage servers can then start Docker containers based on the Docker images. However, this approach only provides Docker container deployment according to the storage server hierarchy, lacking dynamic management of the storage cluster, thus resulting in a lack of high availability and scalability for the entire cluster.

[0031] Furthermore, the relevant container scheduling and deployment methods also include obtaining the characteristic identifiers of compute nodes and binding them to the compute nodes to be bound based on these identifiers. Then, the application to be deployed is obtained based on the characteristics of the use case. Further, the characteristics of the application are transmitted to the compute nodes so that they can complete the application deployment. However, this solution also cannot achieve dynamic adjustment and seamless updates of functional modules.

[0032] In view of this, embodiments of this application provide a container scheduling and deployment method. When the current application environment of the domain controller system is determined to be a production environment, containers corresponding to the domain controller nodes are scheduled and deployed based on the domain controller nodes of the domain controller system. When the current application environment of the domain controller system is determined to be a development / testing environment, containers corresponding to the domain controller nodes are scheduled and deployed based on the remote server of the domain controller system. This application can flexibly select either domain controller nodes or remote servers for scheduling and deployment to suit different application environments, thereby achieving cluster management at different application stages.

[0033] Exemplary application scenarios

[0034] Figure 1 The diagram illustrates a scenario applicable to an embodiment of this application. This scenario includes a domain controller and a remote server, with the domain controller comprising multiple domain controller nodes. Specifically, if the current application environment of the domain controller system is a production environment, containers on the domain controller nodes are scheduled and deployed through the domain controller nodes. These domain controller nodes include, but are not limited to, Electronic Control Units (ECUs). Furthermore, if the current application environment of the domain controller system is a development / testing environment, containers on the domain controller nodes are scheduled and deployed through a remote server to adapt to the management needs of different application stages of the domain controller system.

[0035] Exemplary methods

[0036] Figure 2 The diagram illustrates a flowchart of a container scheduling and deployment method provided in an exemplary embodiment of this application. Exemplarily, this container scheduling and deployment method is applied to a vehicle's domain controller system. Figure 2 As shown in the embodiments of this application, the container scheduling and deployment method includes the following steps.

[0037] Step S210: If the current application environment of the domain controller system is a production environment, then based on the domain controller node of the domain controller system, schedule and deploy the containers corresponding to the domain controller node.

[0038] Specifically, the production environment is the real application environment. When the current application environment of the domain controller system is the production environment, the containers on the domain controller nodes are scheduled and deployed using the domain controller nodes to achieve self-healing of the cluster within the domain controller system.

[0039] The domain controller system includes, but is not limited to, the Advanced Driver Assistance Systems (ADAS) domain controller system, and the domain controller node includes, but is not limited to, the ECU node.

[0040] Step S220: If the current application environment of the domain controller system is a development and testing environment, then the containers corresponding to the domain controller nodes are scheduled and deployed based on the remote server of the domain controller system.

[0041] Specifically, a development test environment refers to a description of the software and hardware environment running on it, as well as any other software that interacts with the software under test.

[0042] First, the remote server obtains the characteristic identifier of the domain controller node to be bound and binds it to the domain controller node based on the obtained characteristic identifier. Then, it obtains the current usage scenario characteristics of the domain controller node and distributes the corresponding container application to the domain controller node according to the usage scenario characteristics, so that the domain controller node can complete the application deployment.

[0043] In addition, the use case refers to the application scenario of the domain controller node. For example, use cases include vehicle-to-everything (V2X) scenarios or ADAS scenarios.

[0044] The scheme described in this application embodiment allows for flexible selection of different scheduling and deployment methods based on the application environment of the domain controller system at different stages. Specifically, when the domain controller system is in a production environment, containers on its nodes are scheduled and deployed using the domain controller nodes; when the domain controller system is in a development and testing environment, containers on its nodes are scheduled and deployed using a remote server, thereby ensuring the dynamic adjustment of the domain controller system and guaranteeing its high scalability and high availability. Furthermore, compared to common virtual machine solutions, virtual machine configurations involve a virtualization layer, thus facing greater potential risks. The scheduling and deployment of containers on nodes by the domain controller nodes or remote servers in this application embodiment reduces the risk of network attacks.

[0045] Figure 3 The above is a schematic diagram illustrating the process of scheduling and deploying containers corresponding to domain controller nodes, provided as an exemplary embodiment of this application. Figure 2 Extending from the illustrated embodiment Figure 3 The illustrated embodiment will be described in detail below. Figure 3 The illustrated embodiments and Figure 2 The differences between the embodiments shown are not repeated here, and the similarities are not repeated here.

[0046] like Figure 3As shown, the scheduling and deployment of containers corresponding to the domain controller nodes based on the domain controller system includes the following steps.

[0047] Step S310: Based on the current operating status of the domain controller system, use the domain controller node to perform expansion or reduction operations on the container corresponding to the domain controller node.

[0048] Step S320: If the container corresponding to the domain controller node is a failed container, then the domain controller node is used to delete the failed container and create a new container corresponding to the failed container.

[0049] It should be noted that steps S310 and S320 are not sequential; they can be performed simultaneously, or only the methods in either step can be executed. In other words, when using a domain controller node to schedule and deploy containers on a node, the domain controller node can be used to expand or shrink the container based on the current operating status of the domain controller system. If the container on the node is in a failed state, the domain controller node can simultaneously delete the failed container and create a new container corresponding to it.

[0050] This application illustrates a specific scheduling and deployment method for domain controller nodes when the domain controller system is in a production environment. In real-world application environments with higher performance requirements, scheduling and deploying containers on nodes using domain controller nodes within the cluster will yield better performance metrics.

[0051] In an exemplary embodiment of this application, scheduling and deploying containers corresponding to domain controller nodes based on a remote server of a domain controller system includes: distributing container applications corresponding to the usage scenario to the domain controller nodes of the domain controller system using a remote server, so that the domain controller nodes can complete application deployment.

[0052] Specifically, as mentioned earlier, the remote server binds to the domain controller node based on its characteristic identifier. Then, based on the usage scenario characteristics of the domain controller system, it distributes the corresponding container application to the domain controller node for application deployment.

[0053] Furthermore, when a domain controller system requires updates to its application model algorithms or functionalities, the system can continue to collect the characteristic identifiers of the domain controller nodes with such requirements and push the relevant update container applications to the designated domain controller nodes, enabling those nodes to smoothly upgrade the relevant model algorithms and functional application containers. If the upgrade fails, it can also be quickly rolled back to the original state.

[0054] During the development and debugging phase, developers typically perform application or code development on their own servers or personal computers. At this time, based on the communication network, remote servers can be used to easily distribute and deploy container applications to be debugged to the corresponding domain controller nodes.

[0055] In an exemplary embodiment of this application, the container is a containerd container.

[0056] Specifically, containerd is a simple, robust, and portable container used for decoupling functional components within a domain controller node.

[0057] Furthermore, the containerd container used in the domain controller system of this application embodiment is an optimized version of the domain controller system. Components unsuitable for the domain controller system's usage scenarios have been removed, and optimizations for specific scenarios have been added. These specific scenarios refer to implementing scenarios on the domain controller that have higher performance and security requirements than those on a remote server.

[0058] In this embodiment, the functional components within the domain controller node are decoupled based on containers, and the containers are completely isolated. This avoids the situation in traditional application systems where an anomaly in one component module leads to the abnormal operation of the entire system. In other words, the solution in this embodiment ensures the basic stability of the system. Furthermore, the decoupling of functional components within the domain controller node based on containerized containers also enables plug-in-style expansion and reuse of the domain controller system, reducing the difficulty of porting the domain controller system. Developers can smoothly migrate their algorithm model containers and functional containers without operating system sensitivity, effectively reducing the development difficulty for users and achieving reusability of functional components. Plug-in-style expansion also allows for the addition and deletion of new functions in the containers without affecting the normal operation of other services.

[0059] In an exemplary embodiment of this application, the container may also be a Docker container.

[0060] In an exemplary embodiment of this application, the container adopts the K3s deployment method.

[0061] The K3s used in this application embodiment is also an optimized version of the domain controller system. It removes related components that are not suitable for the use cases of the domain controller system and adds optimizations for specific scenarios.

[0062] Specifically, K3s deployment is a fully certified, lightweight Kubernetes distribution highly optimized for edge computing and other scenarios. It minimizes external dependencies and effectively reduces cluster resource consumption, adapting to and meeting the use cases and performance requirements of domain controllers. Furthermore, K3s eliminates the hypervisor found in common virtual machine configurations. The absence of a hypervisor layer reduces the complexity of the domain controller system, simplifying its construction and troubleshooting. Moreover, the streamlined configuration of K3s makes managing and deploying software for the domain controller system easier.

[0063] In the configuration and distribution of domain controller systems, compared to common methods that use a hypervisor layer for system deployment and management, the k3s orchestration deployment method provides higher performance guarantees. Furthermore, applications can directly access the CPU, RAM, and other hardware resources, achieving lower system latency and maximizing resource utilization. The absence of a hypervisor layer also means better performance for latency-sensitive modules. Similarly, any application or workload with high hardware requirements can benefit from direct system access, especially in CPU- and GPU-intensive scenarios like domain controller systems with large memory usage. Compared to common virtualization solutions, adjacent virtual machines can exhaust resources, severely impacting system performance. Moreover, the k3s deployment method allows for smooth upgrades of containers within domain controller nodes without shutting down the system; additionally, it allows for reverting to the previous state in case of upgrade failure.

[0064] In an exemplary embodiment of this application, the container is deployed using Kubernetes.

[0065] Exemplary devices and systems

[0066] The above text combined Figures 1 to 3 The present application describes in detail the embodiments of the container scheduling and deployment method. The following is a combination of... Figures 4 to 6 This application provides a detailed description of the apparatus and system embodiments. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus and system embodiments; therefore, any parts not described in detail can be found in the foregoing method embodiments.

[0067] Figure 4 The diagram shown is a structural schematic of a container scheduling and deployment apparatus provided in an exemplary embodiment of this application. Figure 4 As shown, the container scheduling and deployment apparatus 40 provided in this embodiment includes:

[0068] The first scheduling and deployment module 410 is used to schedule and deploy containers corresponding to the domain controller nodes based on the domain controller nodes of the domain controller system if the current application environment of the domain controller system is a production environment.

[0069] The second scheduling and deployment module 420 is used to schedule and deploy containers corresponding to domain controller nodes based on the remote server of the domain controller system if the current application environment of the domain controller system is a development and testing environment.

[0070] In one embodiment of this application, the first scheduling and deployment module 410 is further configured to perform expansion or contraction operations on the containers corresponding to the domain controller nodes based on the current operating status of the domain controller system.

[0071] In one embodiment of this application, the first scheduling and deployment module 410 is further configured to delete the failed container using the domain controller node and create a new container corresponding to the failed container if the container corresponding to the domain controller node is a failed container.

[0072] In one embodiment of this application, the second scheduling and deployment module 420 is further configured to distribute container applications corresponding to the usage scenarios of the domain controller system to the domain controller nodes of the domain controller system via a remote server, so that the domain controller nodes can complete the application deployment.

[0073] In one embodiment of this application, the container is a containerd container, which is used to decouple functional components within a domain controller node.

[0074] In one embodiment of this application, the container adopts the K3s deployment method.

[0075] Figure 5 The diagram shown is a schematic representation of the structure of a domain controller system provided in an exemplary embodiment of this application. Figure 5 As shown, the domain controller system 50 provided in this application embodiment includes:

[0076] Domain controller node 510 is used to schedule and deploy containers corresponding to the domain controller node when the current application environment of the domain controller system is a production environment.

[0077] Remote server 520 is used to schedule and deploy containers corresponding to domain controller nodes when the current application environment of the domain controller system is a development and testing environment.

[0078] Figure 6 The diagram shown is a schematic representation of the structure of a domain controller system provided in another exemplary embodiment of this application. Figure 6As shown in the embodiment of this application, the domain controller system 50 further includes a storage server 530, which is used to store containers. Specifically, the storage server is a server that stores containers containing related model algorithms and functional requirements.

[0079] When the current application environment of the domain controller system is a development and testing environment, the customized model algorithm and functional requirement containers are first distributed to the corresponding storage servers according to customer needs. Then, based on the feature identifiers of the domain controller nodes obtained from the remote server and the usage scenarios of the domain controller system, the containers are distributed to each domain controller node to realize the relevant deployment of model algorithms and functional requirement containers according to different needs.

[0080] Below, for reference Figure 7 This describes an electronic device according to embodiments of the present application. Figure 7 The diagram shown is a structural schematic of an electronic device provided in an exemplary embodiment of this application.

[0081] like Figure 7 As shown, the electronic device 70 includes one or more processors 701 and memory 702.

[0082] The processor 701 may be a central processing unit (CPU) or other form of processing unit with data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device 70 to perform desired functions.

[0083] The memory 702 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 701 may execute the program instructions to implement the container scheduling and deployment methods of the various embodiments of this application described above, and / or other desired functions. The computer-readable storage medium may also store various content such as containers corresponding to domain controller nodes, scheduling and deployment schemes, and current operating status data of the domain controller system.

[0084] In one example, the electronic device 70 may also include an input device 703 and an output device 704, which are interconnected via a bus system and / or other forms of connection mechanism (not shown).

[0085] The input device 703 may include, for example, a keyboard, a mouse, etc.

[0086] The output device 704 can output various information to the outside, including containers corresponding to domain controller nodes, scheduling and deployment schemes, and current operating status data of the domain controller system. The output device 704 may include, for example, a display, speaker, printer, and communication network and its connected remote output devices, etc.

[0087] Of course, for the sake of simplicity, Figure 7 Only some of the components of the electronic device 70 relevant to this application are shown in this illustration; components such as buses, input / output interfaces, etc., are omitted. In addition, the electronic device 70 may include any other suitable components depending on the specific application.

[0088] In addition to the methods and devices described above, embodiments of this application may also be computer program products, which include computer program instructions that, when executed by a processor, cause the processor to perform the steps in the container scheduling and deployment methods according to various embodiments of this application described above.

[0089] The computer program product can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments of this application. The programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0090] Furthermore, embodiments of this application may also be computer-readable storage media storing computer program instructions that, when executed by a processor, cause the processor to perform the steps in the container scheduling and deployment methods according to various embodiments of this application described above.

[0091] The computer-readable storage medium may be any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may, for example, include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0092] The basic principles of this application have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this application are merely examples and not limitations, and should not be considered as essential features of each embodiment of this application. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the application to the necessity of employing the aforementioned specific details for implementation.

[0093] The block diagrams of devices, apparatuses, devices, and systems involved in this application are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.

[0094] It should also be noted that in the apparatus, equipment, and methods of this application, the components or steps can be disassembled and / or recombined. These disassemblies and / or recombinations should be considered as equivalent solutions of this application.

[0095] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this application. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects without departing from the scope of this application. Therefore, this application is not intended to be limited to the aspects shown herein, but rather to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0096] The above description has been given for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of this application to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations thereof.

Claims

1. A container scheduling and deployment method, characterized in that, A domain controller system applied to a vehicle, the method comprising: If the current application environment of the domain controller system is a production environment, then based on the domain controller nodes of the domain controller system, the containers corresponding to the domain controller nodes are scheduled and deployed. The scheduling and deployment of containers corresponding to the domain controller nodes based on the domain controller nodes of the domain controller system includes: Based on the current operating status of the domain controller system, the container corresponding to the domain controller node is expanded or shrunk using the domain controller node; and / or If the container corresponding to the domain controller node is a failed container, then the failed container is deleted using the domain controller node, and a new container corresponding to the failed container is created. If the current application environment of the domain controller system is a development and testing environment, then the containers corresponding to the domain controller nodes are scheduled and deployed based on the remote server of the domain controller system. The scheduling and deployment of containers corresponding to the domain controller nodes based on the remote server of the domain controller system includes: Based on the usage scenario of the domain controller system, the remote server distributes container applications corresponding to the usage scenario to the domain controller nodes of the domain controller system, so that the domain controller nodes can complete the application deployment.

2. The container scheduling and deployment method according to claim 1, characterized in that, The container is a containerd container, which is used to decouple functional components within the domain controller node.

3. The container scheduling and deployment method according to claim 1, characterized in that, The container is deployed using K3s.

4. A container scheduling and deployment device, characterized in that, A domain controller system for use in vehicles, the device comprising: The first scheduling and deployment module is used to schedule and deploy containers corresponding to the domain controller nodes based on the domain controller nodes of the domain controller system if the current application environment of the domain controller system is a production environment. The first scheduling and deployment module is further used for: Based on the current operating status of the domain controller system, the container corresponding to the domain controller node is expanded or shrunk using the domain controller node; and / or If the container corresponding to the domain controller node is a failed container, then the failed container is deleted using the domain controller node, and a new container corresponding to the failed container is created. The second scheduling and deployment module is used to schedule and deploy the containers corresponding to the domain controller nodes based on the remote server of the domain controller system if the current application environment of the domain controller system is a development and testing environment. The second scheduling and deployment module is further used to distribute container applications corresponding to the usage scenario to the domain controller nodes of the domain controller system using the remote server, so that the domain controller nodes can complete the application deployment.

5. A domain controller system, characterized in that, include: Domain controller nodes are used to schedule and deploy containers corresponding to the domain controller nodes when the current application environment of the domain controller system is a production environment. The domain controller node is further used for: Based on the current operating status of the domain controller system, perform expansion or reduction operations on the containers corresponding to the domain controller nodes; and / or If the container corresponding to the domain controller node is a failed container, delete the failed container and create a new container corresponding to the failed container; The remote server is used to schedule and deploy containers corresponding to the domain controller nodes when the current application environment of the domain controller system is a development and testing environment. The remote server is further used to distribute container applications corresponding to the usage scenarios of the domain controller system to the domain controller nodes of the domain controller system, so that the domain controller nodes can complete the application deployment.

6. The domain controller system according to claim 5, characterized in that, It also includes a storage server for storing the container.

7. A computer-readable storage medium, characterized in that, The storage medium stores a computer program for executing the container scheduling and deployment method according to any one of claims 1 to 3.

8. An electronic device, characterized in that, include: processor; Memory used to store the processor's executable instructions; The processor is used to execute the container scheduling and deployment method according to any one of claims 1 to 3.

Images