A vehicle-mounted cloud platform application high-availability system and deployment method

Abstract

The application provides a kind of vehicle-mounted cloud platform application high availability system and deployment method.The system includes cloud application unit, control unit, execution unit, storage unit and data unit, through each unit state monitoring and feedback and load condition timely adjustment cloud platform system overall high availability, cover vehicle-mounted cloud platform system and vehicle-mounted application.Through the high availability design of the above-mentioned application unit, control unit, execution unit, storage unit and data unit, the automatic maintenance of the vehicle-mounted application in the application online stage of the cloud platform is realized, and the high availability and high reliability of the vehicle-mounted application are guaranteed.

Description

Technical Field

[0001] This invention relates to the field of vehicle cloud platform application technology, specifically to a high-availability system for vehicle cloud platform applications and its deployment method. Background Technology

[0002] In industries such as national intelligent transportation and rail transit, cloud-based vehicle applications can effectively solve the problem of resource-intensive management in embedded environments, enabling collaborative resource scheduling, high-quality continuous and stable operation, and unified lifecycle management of applications.

[0003] In actual production projects, the migration of embedded automotive applications to the cloud is divided into two stages: the debugging and adaptation stage of the cloud platform automotive application and the online operation stage of the automotive application.

[0004] During the debugging and adaptation phase of in-vehicle applications, the main tasks are the installation and deployment of the cloud platform and the linkage debugging between the in-vehicle application and the in-vehicle equipment. This requires manual operation. This phase of work is mainly carried out in the integration testing workshop, where the power and network environment is stable and the cloud platform environment is usually relatively stable, which can meet the adaptation requirements of the in-vehicle application.

[0005] During the deployment and operation phase of in-vehicle applications, the in-vehicle cloud platform and applications run on trains, often without human intervention. The in-vehicle applications need to operate stably without supervision. In the mobile operating environment of a vehicle, critical components of the cloud platform, such as the cloud controller, node controller, cloud storage, and cloud database, require primary and secondary deployments for redundancy and reliability, distributed across multiple carriages. When abnormal environmental conditions such as unstable power supply or network connectivity occur, these critical components may fail. More seriously, after the recovery from power outages or network interruptions, these components may experience split-brain failures, rendering the in-vehicle cloud application unable to continue providing services.

[0006] To ensure the high availability of in-vehicle cloud platform applications, the industry currently focuses on design guarantees from two main aspects: the cloud platform itself and the in-vehicle applications.

[0007] For the vehicle cloud platform, a primary / standby mode is adopted to design a high-availability container cloud architecture. Its core design relies on the synchronization of metadata between the primary and standby nodes. The primary node provides the container cloud platform control plane services, while the standby node synchronizes and backs up the container cloud platform metadata in real time. When the primary node becomes unavailable, the container cloud platform's primary / standby failover model is used to quickly switch the cloud platform control plane components to the standby node, such as... Figure 1 As shown.

[0008] In terms of in-vehicle applications, these applications primarily rely on container instances as their foundation. The application is first deployed within a container image and stored in an image repository. By leveraging a node controller to monitor the operational environment of the in-vehicle application and reporting its status to the cloud controller, a new container instance is created when a container instance fails, thus ensuring the application's continued operation and service sustainability.

[0009] In automotive embedded environments, whether for automotive cloud platforms or automotive applications, the risk of split-brain scenarios due to network outages is unavoidable. The backup controller uses an independent heartbeat connection to determine the status of the primary controller. When the heartbeat connection between the primary and backup controllers is interrupted due to network failure, and the status of the other cannot be determined, a split-brain phenomenon occurs. This includes split-brain scenarios involving cloud controllers, cloud databases, and cloud storage. Consequently, both the primary and backup controllers will schedule node controllers to create new instances, resulting in a catastrophic application failure where both applications cannot provide normal service. Summary of the Invention

[0010] In view of the above, this invention addresses the shortcomings of the prior art by providing a high-availability system and deployment method for in-vehicle cloud platform applications, aiming to enable timely adjustment of the overall high availability of the cloud platform system, covering both the in-vehicle cloud platform system and in-vehicle applications.

[0011] This invention is achieved through the following technical solution:

[0012] The present invention first provides a high availability system for in-vehicle cloud platform applications, which includes: an application unit, a control unit, an execution unit, a storage unit, and a data unit.

[0013] The control unit includes a cloud controller, which is distributed in two adjacent carriages in a primary / backup deployment mode. The cloud controller is used to send resource requests and to receive application creation requests and schedule node controllers to process the creation of the application.

[0014] The application unit includes an application self-maintenance component, which is used to accept the application template creation request issued by the cloud controller;

[0015] The storage unit includes cloud storage and a cloud storage monitoring module. The cloud storage is distributed in a primary and backup manner according to the cloud controllers, and is used to provide storage volume mounting for application units. The cloud storage monitoring module is used to synchronize the primary and backup cloud storage and monitor the status of the cloud storage.

[0016] The data unit includes a cloud database, a cloud database backup module, and a cloud database monitoring module. The primary and backup cloud databases are distributed one-to-one with the cloud controllers in a primary-backup manner, and are mainly used to store vehicle cloud platform resource data. The cloud database backup module is used to back up the database resources of the vehicle cloud platform after the application adaptation phase is completed, and saves them as backup_init.tar.gz. The cloud database monitoring module is used to synchronize the primary and backup database data in real time and monitor the database status.

[0017] The execution unit includes multiple node controllers distributed in each carriage. The node controllers are mainly responsible for processing the creation requests sent by the cloud controller and saving them to the cloud database and the cloud storage.

[0018] According to the high availability system for the vehicle cloud platform application, the application template saves the application information required by the vehicle cloud to the database during the application adaptation phase, including the image, storage volume, and IP resources required by the application; during the application launch phase, the application template automatically creates and monitors the application; and after an application failure, the application template actively sends an application creation request to the cloud controller.

[0019] According to the high availability system for the in-vehicle cloud platform, the cloud controller implements primary and backup capabilities through the distributed mechanism of Erlang; when the primary controller is running, the backup controller stops; when the controlled controller cannot connect to the primary controller through network heartbeat, the backup controller runs, thereby ensuring the high availability of the primary and backup cloud controller.

[0020] According to the high availability system for the in-vehicle cloud platform, the cloud storage monitoring module is used to monitor the status of the cloud storage in real time, and automatically synchronize the data of the primary and backup cloud storage when the primary and backup cloud storage is abnormal, so as to ensure the availability of the cloud storage.

[0021] According to the high availability system for the in-vehicle cloud platform, the cloud database monitoring module is used to monitor the status of the cloud database in real time, and when the main and backup cloud controllers experience a split-brain anomaly, the data is restored through the backup file backup_init.tar.gz of the cloud database backup module to ensure the availability of the cloud database.

[0022] The present invention also provides a deployment method for the aforementioned in-vehicle cloud platform application high availability system, the specific steps of which are as follows:

[0023] After completing the cloud platform deployment on the embedded board and the linkage between the vehicle application and the vehicle equipment during the commissioning phase, physical resources are created on the node controller, and data is saved to the cloud storage and cloud database.

[0024] The cloud controller sends a request to the application self-maintenance component to create the application template.

[0025] The application self-maintenance component binds and creates the application template based on logical resource information and saves it to the cloud database;

[0026] After the application template is successfully created, the cloud database backup operation is performed, and the backup file backup_init.tar.gz is created. The vehicle cloud platform is then ready to enter the online operation phase.

[0027] The application template notifies the cloud controller to create the application. The cloud controller then schedules the application creation to the node controller and saves the application resource information in the cloud database, thus entering the online operation phase.

[0028] According to the deployment method of the vehicle cloud platform application high availability system, when the application crashes due to an anomaly, the application template notifies the cloud controller to reschedule to a new node controller to create the application.

[0029] When the cloud controller malfunctions, after the network is restored, the vehicle cloud platform restores the main and backup operation of the cloud controller according to the pre-configured node priorities, with the node with the higher priority being the main cloud controller.

[0030] When the cloud storage fails, after the failure is recovered, the cloud storage monitoring module elects a primary storage through the virtual IP management component, and then synchronizes the data of the primary storage to the backup storage to restore the cloud storage status.

[0031] When the cloud data is abnormal, after the abnormality is recovered, the cloud database monitoring module restores the cloud database state from the backup file backup_init.tar.gz.

[0032] According to the deployment method of the high availability system for the vehicle cloud platform application, the physical resources created by the node controller include images, storage volumes, and network data; the application self-maintenance component binds to and creates the application template according to the logical resource information, which includes images, storage volumes, and network IP addresses.

[0033] According to the deployment method of the high availability system for the vehicle cloud platform application, the abnormal application downtime includes downtime caused by abnormalities in the storage module, network, or node controller; the abnormality of the cloud controller includes network partitioning abnormalities leading to a split-brain anomaly in the cloud controller; the abnormality of the cloud storage includes frequent network drops and network outages leading to a split-brain anomaly in the cloud storage.

[0034] By employing the above technical solution, the beneficial effects of the present invention compared to the prior art are as follows:

[0035] 1) Through the high availability design of the above application unit, control unit, execution unit, storage unit and data unit, the cloud platform realizes automatic maintenance of vehicle applications during the application launch phase, ensuring the high availability and high reliability of vehicle applications.

[0036] The debugging and online operation phases of cloud platform vehicle applications are designed to be separated, thereby ensuring the purity of the cloud platform environment and the certainty of resources during the online operation phase.

[0037] 2) By leveraging Erlang's distributed, high-concurrency, and lightweight features at the language level, lightweight and easy deployment of the cloud controller and node controller can be achieved, while ensuring high availability of the cloud controller and node controller.

[0038] 3) During the cloud platform's online operation phase, the application templates managed by the application template component enable one-to-one creation and monitoring of applications, ensuring high availability of in-vehicle applications under normal cloud platform conditions.

[0039] 4) When abnormalities such as power outages or network outages cause critical components of the cloud platform to experience split-brain events, the self-recovery capabilities of each component ensure the high reliability of the cloud platform, thereby guaranteeing the high availability of in-vehicle applications. Attached Figure Description

[0040] Figure 1 This diagram shows a high availability design of the existing vehicle cloud platform in primary / standby mode.

[0041] Figure 2 The diagram shown is a structural block diagram of the high-availability system for the vehicle-mounted cloud platform application of this invention.

[0042] Figure 3 The diagram shown is a schematic diagram of the deployment method of the high-availability system for the vehicle cloud platform application of the present invention.

[0043] Figure 4 The diagram shown illustrates the high availability recovery of each module in the high availability system of the vehicle cloud platform application of this invention. Detailed Implementation

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

[0045] The technical concept of this invention is as follows: During the application adaptation and debugging phase, unpredictable operations such as frequent creation, image packaging, and application configuration are performed on the application, which may have a certain impact on the stability of the vehicle cloud platform; however, in the production environment, it is only necessary to ensure the stable operation of the application without human intervention, and all resources of the cloud platform remain constant.

[0046] Therefore, the present invention separates the application debugging phase and the online operation phase of the vehicle cloud platform system, and proposes a maintenance mode and a production mode for the vehicle cloud platform, thereby effectively solving the problem of mismatch between the debugging phase and the production phase in terms of cloud platform capability requirements.

[0047] In maintenance mode, it is mainly responsible for debugging, image packaging, and testing of the application, and preparing the necessary resources such as images, storage, network, and application templates for the production stage. In production mode, through the high availability design of application units, control units, execution units, storage units, and data units, it ensures the stable operation of the application without manual intervention.

[0048] By operating these two modes separately, the vehicle cloud platform enables automatic maintenance of vehicle applications during the application launch phase, ensuring high availability and high reliability of vehicle applications.

[0049] Reference Figure 1 As shown in the diagram, this invention provides a structural block diagram of a high-availability system for an in-vehicle cloud platform application. The high-availability system for an in-vehicle cloud platform includes:

[0050] The vehicle-mounted cloud platform 300 includes an application unit 301, a control unit 302, an execution unit 303, a data unit 304, and a storage unit 305; among them, the cloud controller, the primary / backup mode cloud database, the primary / backup mode cloud storage, and the distributed mode node controller, each component supports independent single-machine operation, primary / backup switching, and automatic recovery.

[0051] The control unit includes a cloud controller 307 with a primary / standby mode, distributed across two adjacent carriages in a primary / standby deployment. The cloud controller sends resource requests and receives requests from application units to create applications, and schedules node controllers to process these requests and create container applications. The primary and standby cloud controllers are deployed in two adjacent carriages, and their primary / standby capabilities are implemented using Erlang's distributed mechanism. When the primary controller is running, the standby controller stops; when the controlled component cannot connect to the primary controller via network heartbeat, the standby controller runs, thus ensuring high availability of the cloud controller.

[0052] The application unit includes an application self-maintenance component 306, which is used to accept application template creation requests from the cloud controller. During the application adaptation phase, the application template is created and stored in the database based on the application information required by the vehicle cloud, including the application's required image, storage volume, IP resources, etc. During the application deployment phase, the application template automatically creates and monitors the application. When the application experiences an abnormal failure due to network, storage, or other faults, the application template component proactively sends an application creation request to the cloud controller and creates a new application based on the configured information.

[0053] The execution unit includes multiple node controllers 308, distributed across each carriage. Each node controller is primarily responsible for processing creation requests sent by the cloud controller, saving them to the cloud database and cloud storage, and running applications. When a node controller in one carriage fails, causing an application failure on its node, the application template will detect the anomaly and notify the cloud controller to recreate the application on another working node controller, thus resolving the node controller failure issue in the vehicle-mounted cloud platform.

[0054] The data unit includes a cloud database 309, a cloud database backup module 310, and a cloud database monitoring module 311. The cloud database is deployed on the primary and secondary cloud controller nodes in a primary-secondary manner, distributed one-to-one with the cloud controllers. It is mainly used to store vehicle cloud platform resource data, including application templates, application instances, application images, storage volumes, and network IPs. The backup module is mainly used to back up the database after the application adaptation phase of the cloud platform is completed. The monitoring module is used to monitor the working status of the primary and secondary databases in real time and synchronize the data between the primary and secondary databases. When the database status is abnormal, such as split-brain, the monitoring module will automatically restore the database using the database information backed up by the backup module, so that the primary and secondary database information are consistent, thereby ensuring the high availability of the cloud database.

[0055] The cloud database backup module is used to back up the database resources of the vehicle cloud platform after the application adaptation phase, saving them as backup_init.tar.gz. The cloud database monitoring module is used to synchronize the primary and backup database data in real time and monitor the database status. Specifically, the cloud storage monitoring module is used to monitor the status of the cloud storage in real time, and automatically synchronize the primary and backup cloud storage data when the primary and backup cloud storage experiences an anomaly, ensuring the availability of the cloud storage. The cloud database monitoring module is used to monitor the status of the cloud database in real time, and restore the data through the backup file backup_init.tar.gz of the cloud database backup module when the primary and backup cloud controllers experience a split-brain anomaly, ensuring the availability of the cloud database.

[0056] The storage unit includes cloud storage 312 and a cloud storage monitoring module 313. The cloud storage is deployed on the primary and backup cloud controllers in a master-slave configuration, distributed one-to-one with each cloud controller, and is used to provide storage volume mounting for application units. The cloud storage monitoring module is used to synchronize the primary and backup cloud storage and monitor the status of the cloud storage. When an anomaly such as split-brain occurs in the cloud storage, the monitoring module elects a primary storage through a virtual IP management component, and then simultaneously transfers the data from the primary storage to the slave storage to ensure data consistency between the primary and slave storage. This ensures high availability of the cloud storage while tolerating the loss of storage data by applications.

[0057] Furthermore, in the event of critical cloud platform components malfunctioning due to harsh environments such as weak power or network conditions, the system can automatically assess component status and provide self-recovery mechanisms. Critical component malfunctions include: cloud database split-brain, cloud storage split-brain, cloud controller split-brain, and node controller power failure. The self-recovery mechanisms include: backing up system configuration and application data during cloud platform operation; rebuilding the environment in case of component malfunction using backup data; self-recovery of component services after network partitioning; and self-recovery of application services. Rebuilding the abnormal component environment includes self-recovery of the primary and backup databases from backup data in case of cloud database split-brain, and self-recovery through data synchronization in case of cloud storage split-brain. Self-recovery of component services after network partitioning includes the independent operation of components in primary / backup mode to provide services during network malfunctions and automatic restoration of primary / backup mode to continue providing services after network recovery. Self-recovery of application services includes automatic creation when applications are not running, re-creation of applications in case of malfunction, and deletion of redundant applications when the same application is running simultaneously on multiple nodes.

[0058] Figure 3 This diagram illustrates the deployment method of the high-availability system for the vehicle-mounted cloud platform application of the present invention. (For example...) Figure 3 As shown, the specific steps of this deployment method are as follows:

[0059] Step 1: Deploy the cloud platform on the embedded board. The system enters maintenance mode. The vehicle cloud platform is used for vehicle application adaptation, image packaging, storage data creation, testing, and debugging. Application instances are created through the cloud controller to configure and adapt the applications, ensuring the modules within the platform function correctly.

[0060] Step 2: Based on the application's requirements and resource configuration (such as images, storage volumes, network configurations, etc.), notify the application self-maintenance component through the cloud controller to create an application template. The application template contains the necessary configurations required by the application, such as resource requirements and deployment strategies.

[0061] Step 3: The application self-maintaining component processes the creation of the application template, which will be stored in the cloud database to ensure that the template can be called and used in subsequent production modes.

[0062] Step 4: The vehicle-mounted cloud platform backs up all critical data in the cloud database. The backup file will contain important resource data such as application templates, image information, and storage volume configurations. The backup file is named backup_init.tar.gz and stored on the primary and backup cloud database nodes. This backup data can be used for subsequent disaster recovery, environment rollback, and other operations. After the cloud database backup is complete, the vehicle-mounted cloud platform is switched from maintenance mode to production mode via the management console. During the switchover process, the platform ensures that all resources are ready and checks the health status of all services and components. After switching to production mode, the cloud platform will start all components and functions required for production mode, ensuring that all applications can run stably under strict production environment conditions.

[0063] Step 5: The system starts in production mode. The application self-maintenance component will notify the cloud controller to automatically create new application instances based on the application template saved in step 2.

[0064] Step 6: The cloud controller will schedule the corresponding node controllers to create application instances based on the specified resource requirements (such as images, CPU, memory, storage volumes, etc.). The cloud platform will automatically allocate resources according to application needs and ensure that the resource allocation of each application instance meets production environment standards, thus launching the in-vehicle cloud platform.

[0065] Step 7: During the online operation phase, the vehicle cloud platform continuously monitors the status of relevant modules through application templates, primary and backup cloud controllers, cloud storage monitoring modules, and cloud database monitoring modules. This ensures high availability of the vehicle cloud platform during the online operation phase. Figure 4 As shown:

[0066] a. When an application crashes due to storage, network, or node controller anomalies, the application template notifies the cloud controller to reschedule the application creation to a new node controller, ensuring high availability of the in-vehicle application provided that the cloud platform components are functioning normally.

[0067] b. When the cloud controller malfunctions due to network partitioning or other anomalies in the carriage, after the network is restored, the cloud platform restores the primary and backup operation status of the cloud controller according to the pre-configured node priorities. The node with the higher priority becomes the primary cloud controller, thereby ensuring the high availability of the cloud controller.

[0068] c. When the cloud storage malfunctions due to frequent point drops, network outages, or other anomalies in the carriage, after the anomaly is recovered, the cloud storage monitoring module elects a master storage unit through the virtual IP management component, and then synchronizes the data of the master storage unit to the slave unit to restore the cloud storage status, thereby ensuring the availability of cloud storage.

[0069] d. When anomalies such as data loss or network outage occur, the cloud database may experience abnormalities, leading to data inconsistency or database service unavailability. The database monitoring module will continuously monitor the database status, promptly detect abnormal phenomena and record faults, and automatically restore the database status from the backup module (such as backup_init.tar.gz). During the restoration process, the system will perform data consistency checks to ensure that the data restored from the backup is complete and correct.

[0070] The aforementioned in-vehicle cloud platform application high-availability system and deployment method have the following technical effects:

[0071] 1) Through the high availability design of the above application unit, control unit, execution unit, storage unit and data unit, the cloud platform realizes automatic maintenance of vehicle applications during the application launch phase, ensuring the high availability and high reliability of vehicle applications.

[0072] The debugging and online operation phases of cloud platform vehicle applications are designed to be separated, thereby ensuring the purity of the cloud platform environment and the certainty of resources during the online operation phase.

[0073] 2) By leveraging Erlang's distributed, high-concurrency, and lightweight features at the language level, lightweight and easy deployment of the cloud controller and node controller can be achieved, while ensuring high availability of the cloud controller and node controller.

[0074] 3) During the cloud platform's online operation phase, the application templates managed by the application template component enable one-to-one creation and monitoring of applications, ensuring high availability of in-vehicle applications under normal cloud platform conditions.

[0075] 4) When abnormalities such as power outages or network outages cause critical components of the cloud platform to experience split-brain events, the self-recovery capabilities of each component ensure the high reliability of the cloud platform, thereby guaranteeing the high availability of in-vehicle applications.

[0076] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention in any way. Therefore, any simple modifications, equivalent changes, and alterations made to the above embodiments based on the technical essence of the present invention without departing from the scope of the present invention shall still fall within the scope of the present invention.

Claims

1. A high-availability system for in-vehicle cloud platform applications, characterized in that, The system includes: an application unit, a control unit, an execution unit, a storage unit, and a data unit; The control unit includes a cloud controller, which is distributed in two adjacent carriages in a primary / backup deployment mode. The cloud controller is used to send resource requests and to receive application creation requests and schedule node controllers to process the creation of the application. The application unit includes an application self-maintenance component, which is used to accept the application template creation request issued by the cloud controller; The storage unit includes cloud storage and a cloud storage monitoring module. The cloud storage is distributed in a primary and backup manner according to the cloud controllers, and is used to provide storage volume mounting for application units. The cloud storage monitoring module is used to synchronize the primary and backup cloud storage and monitor the status of the cloud storage. The data unit includes a cloud database, a cloud database backup module, and a cloud database monitoring module. The primary and backup cloud databases are distributed one-to-one with the cloud controllers in a primary-backup manner and are used to store vehicle cloud platform resource data. The cloud database backup module is used to back up the database resources of the vehicle cloud platform after the application adaptation phase is completed and saves them as backup_init.tar.gz. The cloud database monitoring module is used to synchronize the primary and backup database data in real time and monitor the database status. The execution unit includes multiple node controllers distributed in each carriage. Each node controller is responsible for processing the creation requests sent by the cloud controller and saving them to the cloud database and the cloud storage. During the application adaptation phase, the application template saves the application information required by the vehicle cloud to the database, including the image, storage volume, and IP resources required by the application. During the application launch phase, the application template automatically creates and monitors the application. After an application failure, the application template actively sends an application creation request to the cloud controller.

2. The high-availability system for vehicle-mounted cloud platform applications as described in claim 1, characterized in that: The cloud controller implements primary and backup capabilities through Erlang's distributed mechanism; when the primary controller is running, the backup controller stops; when the controlled controller cannot connect to the primary controller via network heartbeat, the backup controller runs, thereby ensuring high availability of the cloud controller's primary and backup capabilities.

3. The high-availability system for vehicle-mounted cloud platform applications as described in claim 1, characterized in that: The cloud storage monitoring module is used to monitor the status of the cloud storage in real time, and automatically synchronize the data of the primary and backup cloud storage when the primary and backup cloud storage is abnormal, so as to ensure the availability of the cloud storage.

4. The high-availability system for vehicle-mounted cloud platform applications as described in claim 1, characterized in that: The cloud database monitoring module is used to monitor the status of the cloud database in real time, and when the primary and backup cloud controllers experience a split-brain anomaly, it restores the data through the backup file backup_init.tar.gz of the cloud database backup module to ensure the availability of the cloud database.

5. A deployment method for a vehicle-mounted cloud platform application high-availability system applied to any one of claims 1-4, characterized in that: The specific steps of the deployment method are as follows: After completing the cloud platform deployment on the embedded board and the linkage between the vehicle application and the vehicle equipment during the commissioning phase, physical resources are created on the node controller, and data is saved to the cloud storage and cloud database. The cloud controller sends a request to the application self-maintenance component to create the application template. The application self-maintenance component binds and creates the application template based on logical resource information and saves it to the cloud database; After the application template is successfully created, the cloud database backup operation is performed, and the backup file backup_init.tar.gz is created. The vehicle cloud platform is then ready to enter the online operation phase. The application template notifies the cloud controller to create the application. The cloud controller then schedules the application creation to the node controller and saves the application resource information in the cloud database, thus entering the online operation phase.

6. The deployment method of the high-availability system for vehicle-mounted cloud platform applications as described in claim 5, characterized in that: When an application crashes due to an anomaly, the application template notifies the cloud controller to reschedule the application creation to a new node controller. When the cloud controller malfunctions, after the network is restored, the vehicle cloud platform restores the main and backup operation of the cloud controller according to the pre-configured node priorities, with the node with the higher priority being the main cloud controller. When the cloud storage fails, after the failure is recovered, the cloud storage monitoring module elects a primary storage through the virtual IP management component, and then synchronizes the data of the primary storage to the backup storage to restore the cloud storage status. When the cloud data is abnormal, after the abnormality is recovered, the cloud database monitoring module restores the cloud database state from the backup file backup_init.tar.gz.

7. The deployment method of the high-availability system for vehicle-mounted cloud platform applications as described in claim 6, characterized in that: The physical resources created by the node controller include images, storage volumes, and network data; the application self-maintenance component binds to and creates the application template based on the logical resource information, which includes images, storage volumes, and network IP addresses.

8. The deployment method of the high-availability system for vehicle-mounted cloud platform applications as described in claim 7, characterized in that: The application anomalies include downtime caused by storage module, network, or node controller anomalies; the cloud controller anomalies include network partition anomalies causing a split-brain anomaly in the cloud controller; the cloud storage anomalies include frequent network drops and network outages causing a split-brain anomaly in the cloud storage.

Images