Application deployment methods, devices, equipment, and media based on cloud control platform

Abstract

This invention discloses an application deployment method, apparatus, device, and medium based on a cloud control infrastructure platform. The method includes: decomposing the various levels of the original cloud control infrastructure platform into multiple independent functional units according to business requirements; wherein each functional unit includes components, modules, sub-modules, and functional points in descending order of functional level; combining the functional units of each cloud platform in descending order of functional level to form a cloud control infrastructure platform model; creating an integration base; loading front-end application resources based on the front-end service base; and deploying back-end applications to the various levels of the cloud control infrastructure platform model according to the functional level of their corresponding functional units based on the back-end service base. By adopting the above technical solution, the different functional units of the cloud control infrastructure platform are decoupled in terms of business operations, the process of front-end application integration is simplified, and the flexibility of the cloud control infrastructure platform is improved.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of intelligent transportation technology, and more specifically, to an application deployment method, apparatus, equipment, and medium based on a cloud control platform. Background Technology

[0002] The cloud control platform is an important component of the vehicle-road-cloud integrated system. It integrates the physical and information spaces of people, vehicles, roads, and the cloud through next-generation information and communication technologies, providing basic data, hierarchical sharing services, and collaborative computing environment for the intelligent connected vehicle industry. The cloud control platform consists of three levels of clouds: edge cloud, regional cloud, and central cloud, forming a logically collaborative and physically distributed cloud computing center.

[0003] Traditional cloud control infrastructure platforms are large-scale projects with numerous development teams. The various subsystems are interdependent and tightly coupled, requiring maintenance personnel to log into multiple systems to configure services. This process is time-consuming and labor-intensive, making overall platform maintenance and upgrades difficult. Furthermore, traditional cloud control technology platforms require the introduction of micro-frontend frameworks during front-end integration, a relatively complex and cumbersome process that hinders platform construction and management. Summary of the Invention

[0004] This invention provides an application deployment method, apparatus, device, and medium based on a cloud control platform, which decouples different functional units in terms of business, simplifies the process of front-end application integration, and improves the flexibility of the cloud control platform.

[0005] The specific technical solution is as follows:

[0006] In a first aspect, embodiments of the present invention provide an application deployment method based on a cloud control infrastructure platform, wherein the cloud control infrastructure platform consists of three levels: edge cloud, regional cloud, and central cloud. The method includes:

[0007] Based on business needs, the original cloud control platform is broken down into multiple independent functional units. Each functional unit includes components, modules, sub-modules, and functional points in descending order of functional level. The functional units establish interrelationships through interface functions.

[0008] The various functional units of each cloud platform are combined in descending order of functional level to form a cloud control basic platform model. The application of the cloud control basic platform model includes front-end applications and back-end applications. The front-end applications are implemented through front-end application resources, which include application interfaces, application menus, images, and runnable executable packages. The back-end applications include at least one application corresponding to a functional unit and its runtime environment.

[0009] Create an integration base, which includes a front-end service base and a back-end service base. The front-end service base is a container for integrating application pages corresponding to various levels of components and is used to manage front-end application resources. The back-end service base is the infrastructure that supports the operation of cloud control platform applications and is used to manage the various functional units of the cloud control platform model.

[0010] The front-end application resources are loaded based on the front-end service base, and the back-end application is deployed to the cloud platforms at various levels of the cloud control basic platform model according to the functional level of its corresponding functional unit based on the back-end service base.

[0011] Optionally, front-end application resources can be loaded based on the front-end service platform, including:

[0012] Create a new node to mount the component;

[0013] Determine the corresponding target front-end application resources based on user permissions;

[0014] For each level of cloud platform, the target front-end application resources are loaded based on the front-end service base, and a global routing variable of the base is registered. The global routing variable of the base is used to switch between different front-end pages.

[0015] Accordingly, after loading front-end application resources based on the front-end service platform, the method provided in this embodiment of the invention further includes:

[0016] The front-end application corresponding to the target front-end application resource is launched on the front-end service platform based on the node.

[0017] Optionally, based on the backend service foundation, backend applications are deployed to various levels of cloud platforms within the cloud control infrastructure platform model according to the functional level of their corresponding functional units, including:

[0018] Package the application and current runtime environment corresponding to each component into an image file as a backend application. For a component at a certain level, the application corresponding to the component includes the application of the component itself and the application of modules, sub-modules and function points that have a hierarchical relationship with the component at the functional level of the component.

[0019] Configure the configuration information for each image file, including the name, version number, and corresponding components at each level for each image file.

[0020] Upload the image file to the backend service platform according to the configuration information;

[0021] Allocate runtime resources to each level of the cloud platform in the established cloud control infrastructure platform model. The runtime resources include the target cloud platform to be deployed, the number of CPU cores, memory, and hard disks required when the target cloud platform is running.

[0022] Install the backend application corresponding to the image file onto the target cloud platform.

[0023] Optionally, after installing the target backend application corresponding to the target image file onto the cloud platform, the method provided in this embodiment of the invention further includes:

[0024] Map the port corresponding to the target backend application to the port of other backend applications so that other backend applications can access the port corresponding to the target backend application.

[0025] Secondly, embodiments of the present invention also provide an application deployment device based on a cloud control platform, comprising:

[0026] The decomposition module is configured to decompose the cloud platform at each level in the original cloud control basic platform into multiple independent functional units according to business needs. Each functional unit includes components, modules, sub-modules and function points in descending order of function level. The functional units establish interrelationships with each other through interface functions.

[0027] The combination module is configured to combine the various components of each level of the cloud platform in descending order of functional level to form a cloud control basic platform model. The application of the cloud control basic platform model includes front-end applications and back-end applications. The front-end applications are implemented through front-end application resources, which include application interfaces, application menus, images, and runnable executable packages. The back-end applications include at least one application corresponding to a functional unit and its runtime environment.

[0028] The base creation module is configured to create an integrated base, which includes a front-end service base and a back-end service base. The front-end service base is a container for integrating application pages corresponding to components at all levels and is used to manage front-end application resources. The back-end service base is the infrastructure that supports the operation of cloud control platform applications and is used to manage the various functional units of the cloud control platform model.

[0029] The application deployment module is configured to load front-end application resources based on the front-end service platform, and deploy back-end applications to the cloud platforms at various levels of the cloud control infrastructure platform model according to the functional level of their corresponding functional units based on the back-end service platform.

[0030] Optionally, the application deployment module includes: a front-end application deployment unit, which is configured as a node for creating a new mounted component;

[0031] Determine the corresponding target front-end application resources based on user permissions;

[0032] For each level of cloud platform, the target front-end application resources are loaded based on the front-end service base, and a base global routing variable is registered. The base global routing variable is used to switch between different front-end pages.

[0033] Accordingly, the apparatus provided in the embodiments of the present invention further includes:

[0034] The front-end application startup module is configured to start the front-end application corresponding to the target front-end application resource on the front-end service platform after loading the front-end application resource based on the front-end service platform.

[0035] Optionally, the application deployment module includes: a backend application deployment unit, which is configured as follows:

[0036] Package the application and current runtime environment corresponding to each component into an image file as a backend application. For a component at a certain level, the application corresponding to the component includes the application of the component itself and the application of modules, sub-modules and function points that have a hierarchical relationship with the component at the functional level of the component.

[0037] Configure the configuration information for each image file, including the name, version number, and corresponding components at each level for each image file.

[0038] Upload the image file to the backend service base according to the configuration information;

[0039] Allocate runtime resources to each level of the cloud platform in the established cloud control infrastructure platform model. The runtime resources include the target cloud platform to be deployed, the number of CPU cores, memory, and hard disks required when the target cloud platform is running.

[0040] Install the backend application corresponding to the image file onto the target cloud platform.

[0041] Optionally, the apparatus provided in this embodiment of the invention further includes:

[0042] The port mapping module is configured to map the port corresponding to the target backend application to the port of other backend applications after the target backend application corresponding to the target image file is installed on the cloud platform, so that other backend applications can access the port corresponding to the target backend application.

[0043] Thirdly, embodiments of the present invention provide a computer device, the computer device comprising:

[0044] At least one processor is provided, and the processor is coupled to a memory. The memory stores a program or instructions that run on the processor. When the program or instructions are executed by the processor, they implement the application deployment method based on the cloud control platform provided in any embodiment of the present invention.

[0045] Fourthly, embodiments of the present invention provide a readable storage medium storing a program or instructions thereon, which, when executed by a processor, implements the application deployment method based on a cloud control platform as provided in any embodiment of the present invention.

[0046] Fifthly, embodiments of the present invention provide a computer program, the computer program including program instructions, which, when executed by a computer, implement the application deployment method based on a cloud control platform as provided in any embodiment of the present invention.

[0047] By breaking down the original cloud control infrastructure platform into multiple independent functional units based on business needs, and combining these units in descending order of functional level, a cloud control infrastructure platform model is formed. This decoupling of different functional units in terms of business operations facilitates the maintenance and operation of the cloud control infrastructure platform. After establishing the cloud control infrastructure platform model, when integrating its components to deploy applications to various cloud platforms, the front-end employs a lightweight component integration approach, eliminating the need for a micro-front-end framework. Compared to front-end integration methods in related technologies, the integration process provided in this embodiment is simpler and easier to operate. The back-end uses container orchestration for component integration. By treating the applications of each component as services, there is no need to concern oneself with the development language and runtime environment of each component. The application and environment are simply packaged together into a container material, i.e., an image file, and uploaded to the back-end service base. When deploying the application to a specific cloud, the appropriate container material is selected. This process is simple and easy to operate, enabling dynamic addition and expansion of back-end applications on the cloud control infrastructure platform, thus improving its flexibility and scalability. Attached Figure Description

[0048] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0049] Figure 1a This is a flowchart of an application deployment method based on a cloud control platform provided in Embodiment 1 of the present invention;

[0050] Figure 1bThis is a schematic diagram of the hierarchical structure of the cloud control infrastructure platform model provided in Embodiment 1 of the present invention;

[0051] Figure 1c This is a schematic diagram illustrating the deployment process of the backend application provided in Embodiment 1 of the present invention;

[0052] Figure 2 This is a structural block diagram of an application deployment device based on a cloud control platform provided in Embodiment 2 of the present invention;

[0053] Figure 3 This is a structural block diagram of a computer device provided in Embodiment 3 of the present invention. Detailed Implementation

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

[0055] It should be noted that the terms "comprising" and "having," and any variations thereof, in the embodiments and drawings of this invention are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the steps or units listed, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0056] This invention discloses an application deployment method, apparatus, device, and medium based on a cloud control platform. These are described in detail below.

[0057] Example 1

[0058] Figure 1a This is a flowchart illustrating an application deployment method based on a cloud-controlled infrastructure platform, as provided in Embodiment 1 of the present invention. This method can be applied to the server side of the cloud-controlled infrastructure platform. The method provided in this embodiment can be executed by an application deployment device based on a cloud-controlled infrastructure platform model, which can be implemented through software and / or hardware. Figure 1a As shown, the method provided in this embodiment specifically includes:

[0059] S110. Based on business needs, the cloud platforms at all levels in the original cloud control infrastructure platform are broken down into multiple independent functional units.

[0060] The cloud control platform comprises three levels: edge cloud, regional cloud, and central cloud. The edge cloud, located close to vehicles and roads, provides highly reliable, low-latency services for fusion perception, collaborative decision-making, and collaborative control. It primarily processes real-time vehicle data and edge computing tasks, ensuring data timeliness and accuracy. The regional cloud, positioned above the edge cloud, collects data from multiple edge clouds and performs more complex data processing and analysis. It supports regional-level traffic fusion perception, collaborative decision-making, collaborative control, and traffic management services. The central cloud is the core and highest-level cloud computing resource hub of the entire intelligent connected vehicle cloud control platform. It collects data from various regional and edge clouds and performs global data analysis, modeling, and decision-making. It aggregates traffic-related data from various regional clouds, storing and managing the data to achieve efficient interaction of business data and hierarchical sharing of common basic capabilities.

[0061] In related technologies, the functional modules of various levels of cloud platforms in a cloud control infrastructure platform are interdependent and coupled in business roles. This leads to maintenance personnel needing to log into multiple subsystems with multiple accounts when configuring services, resulting in time-consuming, labor-intensive, and extremely inefficient maintenance and upgrades of the entire cloud control infrastructure platform. In this embodiment, the various levels of cloud platforms in the original cloud control infrastructure platform can be decomposed into multiple independent functional units according to business needs. Each functional unit includes components, modules, sub-modules, and functional points in descending order of functional level. The business requirements of the cloud control infrastructure platform model can be proposed by the maintenance party of the cloud control infrastructure platform. The maintenance party can propose its business requirements based on the functions that the cloud control infrastructure platform needs to achieve in its application scenario.

[0062] Specifically, Figure 1b This is a schematic diagram of the hierarchical structure of the cloud control infrastructure platform model provided in Embodiment 1 of the present invention. Figure 1bAs shown, the cloud control infrastructure platform comprises three levels: edge cloud, regional cloud, and central cloud. Each level's independent functional units, ranked from highest to lowest functional level, include: components, modules, sub-modules, and functional points. These functional units establish interrelationships through interface functions. For any given level, there may be multiple actual functional units belonging to that level based on business needs. For example, components belonging to the edge cloud platform include: collaborative decision-making components, fusion perception components, collaborative control components, standardized hierarchical sharing interface components, and operation and maintenance components; components belonging to the regional cloud platform include: fusion perception components, collaborative decision-making components, collaborative control components, traffic management components, standardized hierarchical sharing interface components, operation and maintenance components, and operational components; components belonging to the central cloud platform include: domain big data analysis components and standardized hierarchical sharing interface components. Furthermore, the next level of modules under the collaborative control component includes: vehicle control modules and dynamic lane control modules; the next level of sub-modules under the vehicle control module includes: vehicle lateral control sub-modules and vehicle longitudinal control sub-modules; and the next level of functional points under the vehicle lateral control sub-modules and vehicle longitudinal control sub-modules includes the specific control methods for vehicle lateral and longitudinal movement.

[0063] In this embodiment, various functional units of the cloud platform at all levels can be managed through a platform model front-end configuration interface. This front-end configuration interface allows for adding or deleting components, and super administrators can edit or delete components according to actual business needs to create a cloud control basic platform model. Different levels of functional units can be represented by different identifiers. Functional units at the same level can be represented by sequentially increasing Arabic numerals to indicate the actual number of functional units they contain. For example, edge cloud functional units are represented by a combination of the letter A and Arabic numerals; for instance, component 1 of the edge cloud is identified as A01, component 2 as A02, component 3 as A03, and so on. The identification methods for modules, sub-modules, and functional points are similar to those for components and will not be elaborated further here. The identification methods for functional units in other cloud platforms can also refer to the above methods.

[0064] S120. Combine the functional units of each cloud platform in descending order of functional level to form a cloud control basic platform model.

[0065] In this embodiment, for each level of the cloud platform, its functional units are combined in descending order of functional level to obtain a hierarchical cloud control infrastructure platform model. In this model, each functional unit is independent of the others in terms of both business and functionality; modifying one functional unit will not affect other components coupled with it. Furthermore, a failure in one functional unit will not affect other coupled functional units. Each functional unit can be developed by different teams and then integrated on the platform. Compared to related technologies where the functional units of a cloud control infrastructure platform are coupled in terms of business, the cloud control infrastructure platform model provided in this embodiment decouples different functional units in terms of business, which is more conducive to the maintenance and operation of the cloud control infrastructure platform.

[0066] In this embodiment, the cloud control infrastructure platform model includes front-end applications and back-end applications. The front-end applications are implemented through front-end application resources, which include application interfaces, application menus, images, and executable packages. The back-end applications include applications corresponding to at least one functional unit and their runtime environment. For example, developers can set corresponding user permissions for each component and set corresponding front-end application interfaces for each. The login account for the front-end application interfaces of different components can be set to a unified account for the cloud control infrastructure platform. Users can log in to the front-end application interface corresponding to their permissions using this account, and view or modify the configuration information of components with specific permissions. Compared to the traditional cloud control infrastructure platform where different subsystems require different usernames and passwords for login, this embodiment integrates the common parts of each component of the cloud control infrastructure platform and defines the entire platform's account and permission system. Furthermore, each sub-component can implement interface functions according to a unified UI (User Interface) style, improving the user experience.

[0067] S130, Create an integrated base.

[0068] In this embodiment, the business operations of the cloud control infrastructure platform need to be completed through the combination of front-end and back-end applications. These applications can be integrated into a platform. The platform refers to the software platform, which is the container that hosts the various applications of the cloud control infrastructure platform, providing basic support and services. The platform includes a front-end service platform and a back-end service platform. The front-end service platform is a container that integrates the application pages corresponding to each functional unit, used to manage front-end application resources. The back-end service platform is the infrastructure that hosts the applications of the cloud control infrastructure platform, mainly including the container orchestration system and the underlying environment, network, and storage upon which the container orchestration system depends.

[0069] Specifically, in this embodiment, the integrated base's functions include front-end application relationships, back-end application relationships, and system management. Front-end application relationships include front-end menu management and resource management. Back-end application management includes application material management and application monitoring, where application materials refer to the image files packaged from the application program corresponding to the component and its current runtime environment.

[0070] S140. Load front-end application resources based on the front-end service platform, and deploy back-end applications to the cloud platforms at all levels of the cloud control basic platform model according to the functional level of their corresponding functional units based on the back-end service platform.

[0071] Those skilled in the art will understand that the deployment process of front-end and back-end applications is a process of integrating the various functional units (e.g., components) of the cloud control infrastructure platform within the platform model. For example, front-end integration can employ a lightweight integration approach, which may include acquiring the front-end application, loading front-end application resources, loading the user-permitted application menu, and rendering the page. The back-end can utilize container orchestration, which may include uploading application image files, deploying the cloud platform, and installing application services. Once both front-end and back-end applications are deployed, they can be integrated into a single cloud control infrastructure platform.

[0072] In this embodiment, loading front-end application resources based on the front-end service platform can be achieved through the following steps a1 to a3:

[0073] a1. Create a new node to mount the component.

[0074] Operations and maintenance personnel, i.e., users of the cloud control platform, must log in to the cloud control platform before creating a new node for mounting components. After logging in, they can host the current front-end application by creating a new node for mounting components, which can be achieved through the following code:

[0075] <div id＝"subapp-container">

[0076]

[0077] a2. Determine the corresponding target front-end application resources based on user permissions.

[0078] The target front-end application resources include the application interface, application menu, images, and executable packages.

[0079] a3. For each level of cloud platform, load the target front-end application resources based on the front-end service base and register the base's global routing variables.

[0080] Specifically, the loading of the target front-end application resources can be achieved using the following code:

[0081] / / Create a new div element

[0082] var div=document.createElement('div');

[0083] / / Set the ID of this newly created div element to 'subapp-container'

[0084] div.id = 'subapp-container'

[0085] / / Add the newly created div element to the first element on the page with the class name 'body'.

[0086] document.getElementsByClassName('body')[0].appendChild(div)

[0087] / / Use querySelector to find the first page whose src attribute matches the variable url. <script>元素

[0088] var oldScript＝document.querySelector('script[src＝"'+url+'"]')；

[0089] / / 如果找到了匹配的<script>元素,那么就移除这个元素

[0090] if(oldScript){

[0091] oldScript.parentNode.removeChild(oldScript)；

[0092] }

[0093] / / 创建一个新的<script>元素

[0094] var script＝document.createElement('script')；

[0095] / / 设置这个<script>元素的类型为'module'

[0096] script.type＝'module'

[0097] / / 设置这个<script>元素的src属性为变量url的值，即要加载的模块的URL

[0098] cript.src＝url；

[0099] / / 将这个新的<script>元素添加到<body>标签的末尾

[0100] document.body.appendChild(script)；

[0101] / / 为这个<script>元素设置一个onload事件监听器

[0102] / / 当脚本加载完成时，这个监听器会被触发，并在控制台打印出'加载完成'和事件对象e

[0103] script.onload＝(e)＝>{

[0104] console.log('加载完成',e)

[0105] }

[0106] 此外，还可通过注册底座全局路由变量来实现前端不同页面之间的切换。

[0107] 进一步的，在加载完成前端应用资源后，基于预先新建的节点在前端服务底座启动目标前端应用资源对应的前端应用，该过程可包括渲染前端应用界面。

[0108] 本实施例中，基于后端服务底座将后端应用按照其对应功能单元的功能级别部署到云控基础平台模型的各级云平台中，可通过如下步骤b1～b4来实现：

[0109] b1、将各个组件对应的应用程序和当前运行环境打包为镜像文件，作为后端应用。

[0110] 本实施例中，后端将各个组件的应用当成服务，无需关心各级组件的开发语言和运行环境，只需要将应用程序和环境一起打包成容器物料，即镜像文件，上传到后端服务底座中。在将应用部署到具体云的时候，选择相应的容器物料即可。其中，对于某个级别的组件，该组件对应的应用程序包括该组件本身的应用程序及在该组件的功能级别下与该组件具有层级关系的模块、子模块和功能点的应用程序。

[0111] b2、配置各镜像文件的配置信息，并将镜像文件按照配置信息上传到后端服务底座。

[0112] 其中，配置信息包括各镜像文件的名称、版本号以及镜像文件分别对应的各级组件。在上次镜像文件时，需选择该镜像文件属于云控基础平台模型例的哪个组件、哪个模块、哪个子模块和哪个功能点。本实施例中，在将镜像文件按照配置信息上传到后端服务底座后，可根据实际业务需求将后端应用部署到目标云平台，或者在目标云平台现有应用的基础上添加新的应用。

[0113] b3、为已创建的云控基础平台模型的各级云平台分配运行资源。

[0114] 其中，运行资源包括待部署的目标云平台、在该目标云平台运行时的中央处理器(Central Processing Unit，CPU)核的数量、内存和硬盘。该目标云平台可以为边缘云、区域云或者中心云中的任意一级云平台。

[0115] 具体的，对于需要部署的云，可在创建具体云的命名空间时配置镜像文件的运行资源，例如，在新建云的操作过程中选择云所属层级(边缘云，区域云，中心云中的一种)，并分配资源(CPU，内存，硬盘等)。

[0116] b4、将镜像文件对应的后端应用安装到目标云平台。

[0117] 本实施例中，用户在上传镜像文件、分配运行资源后，可在通过点击确定按键进入下一步流程。在下一步流程中，后端会对应用进行冲突校验，校验的判断条件是在同一个云平台下，同一个组件、同一个模块是否对应一个应用。如果对应一个应用，则校验成功，此时，可创建Deployment(一种资源类型)用于管理底层节点pod的部署、更新和扩展，具体可通过如下代码实现：

[0118] apiVersion:apps / v1

[0119] kind:Deployment

[0120] metadata:

[0121] name:deployment-appname

[0122] namespace:namespace-cloud-basis-platform

[0123] spec:

[0124] replicas:3

[0125] selector: / / 定义选择Pod的标签选择器

[0126] matchLabels: / / 选择具有特定标签的Pod

[0127] app:appname / / 标签选择器，选择所有标签为app:appname的Podtemplate: / / 定义Pod的模板

[0128] metadata: / / Pod模板的元数据

[0129] labels: / / Pod模板的标签

[0130] app:appname / / 给Pod模板添加一个标签app:appname

[0131] spec: / / Pod模板的规格说明

[0132] containers: / / 定义Pod模板中的容器列表

[0133] name:container-appname / / 容器的名称为container-appname

[0134] image:image-appname / / 容器使用的镜像mage-appname

[0135] ports: / / 定义容器需要暴露的端口列表

[0136] containerPort:3000

[0137] 通过执行上述代码，可将后端应用安装完成，并将后端应用程序启动。对于目标云平台之外其他云平台中后端应用的部署方案，与上述目标云平台中后端应用的部署方式相同，具体可参照上述步骤的说明，此处不再赘述。本实施例中，在完成各级云平台的前端应用和后端应用的部署之后，即可得到各组件融合后的云控基础平台。

[0138] 本实施例中，前端应用和后端应用的部署可以顺序执行，也可以同步执行，本实施例对此不作具体限定。

[0139] 进一步的，在将目标镜像文件对应的目标后端应用安装到目标云平台之后，本发明实施例提供的方法还包括：

[0140] 将目标后端应用对应的端口映射到其他后端应用的端口上，这样可暴露目标后端应用的端口给外部其他应用，以使其他后端应用能够访问目标后端应用对应的端口，即将内部应用和外部应用桥接起来。

[0141] 下面通过图1c对添加后端应用的过程进行详细介绍：

[0142] 在运维人员新增后端应用的过程中，需要运维人员输入云基础信息。云管理服务模块和物料服务管理模块可对该基础信息进行校验，其中，校验可通过模块的管理人员人工进行校验，或者也可采用自动校验的方式。信息合法性校验主要是校验用户输入的信息是否符合信息的输入规则，比如用户输入CPU核数应当为数字，但用户却输入字符，则说明不合法。在用户输入的云基础信息校验不合法的情况下，需要用户重新输入云基础信息；在校验合法的情况下，创建云命名空间，即在后端服务底座新建待部署后端应用的云，并反馈创建结果给运维人员，运维人员可查看云信息，并在该云平台上创建后端应用。在创建后端应用时，需要查询该后端应用对应的应用物料，即镜像文件(由组件的应用程序和对应的运行环境打包后得到的文件包)，运维人员可输入应用信息，即可为已创建的云控基础平台模型的各级云平台分配运行资源，其中，运行资源包括待部署的目标云平台、在目标云平台运行时所要用到的中央处理器CPU核的数量、内存和硬盘。应用管理模块校验该应用信息的合法性，该合法性表示的是数据是否有效，如果有效则合法，如果无效则不合法，例如，信息有效性校验是对用户输入的信息是否能够被使用和处理这两个方面进行校验，比如如果当前待部署的目标云平台只有20个CPU核可以使用，而用户分配了25个，超出了范围，则说明应用信息不合法。在应用信息合法的情况下，可创建服务，即将已上传的镜像文件对应的后端应用安装到目标云平台。在后端应用安装成功后，应用管理模块可反馈创建结果，运营人员根据该创建结果即可查看已安装的应用。

[0143] 本实施例中，通过根据业务需求将原始云控基础平台中的各级云平台拆解为多个独立的功能单元，并按照功能级别从高到低的顺序将每级云平台的各个功能单元进行组合，形成云控基础平台模型，实现了不同功能单元在业务上的解耦，从而更加有利于云控基础平台的维护和运营。在建立云控基础平台模型后，在融合该模型的各组件以将应用部署到各级云平台时，前端采用轻量级的组件融合方式，无需引入微前端框架，相对于相关技术中的前端集成方式，本实施例提供的融合过程简单易操作。后端采用容器编排的方式进行组件融合，通过将各个组件的应用当成服务，而无需关心各级组件的开发语言和运行环境，只需要将应用程序和环境一起打包成容器物料，即镜像文件，上传到后端服务底座中。在将应用部署到具体云的时候，选择相应的容器物料即可，其过程简单、易操作，实现了云控基础平台后端应用的动态增加和扩展，提高了云控基础平台的灵活性和可拓展性。

[0144] 实施例二

[0145] 图2为本发明实施例二提供的一种基于云控基础平台的应用部署装置的结构框图，如图2所示，该装置包括：拆解模块210、组合模块220、底座创建模块230和应用部署模块240，其中，

[0146] 拆解模块210，被配置为根据业务需求将原始云控基础平台中的各级云平台拆解为多个独立的功能单元，其中，各个功能单元按照功能级别从高到低的顺序依次包括组件、模块、子模块和功能点，其中，各个功能单元通过接口函数建立相互之间的关联关系；

[0147] 组合模块220，被配置为按照功能级别从高到低的顺序将每级云平台的各个组件进行组合，形成云控基础平台模型，其中，云控基础平台模型的应用包括前端应用和后端应用，前端应用通过前端应用资源实现，前端应用资源包括应用界面、应用菜单、图片和可运行的执行包，后端应用包括至少一个功能单元对应的应用程序及其运行环境；

[0148] 底座创建模块230，被配置为创建集成底座，其中，集成底座包括前端服务底座和后端服务底座，前端服务底座是集成各级组件对应的应用页面的容器，用于管理前端应用资源；后端服务底座是承载云控基础平台应用运行的基础设施，用于管理云控基础平台模型的各个功能单元；

[0149] 应用部署模块240，被配置为基于前端服务底座加载前端应用资源，并且，基于后端服务底座将后端应用按照其对应功能单元的功能级别部署到云控基础平台模型的各级云平台中。

[0150] 可选的，应用部署模块240，包括：前端应用部署单元，该前端应用部署单元被配置为新建挂载组件的节点；

[0151] 根据用户权限确定对应的目标前端应用资源；

[0152] 对于每一级云平台，基于所述前端服务底座加载目标前端应用资源，并注册底座全局路由变量，其中，底座全局路由变量用于将前端不同页面进行切换；

[0153] 相应的，本发明实施例提供的装置还包括：

[0154] 前端应用启动模块，被配置为在基于前端服务底座加载前端应用资源之后，基于节点在前端服务底座启动目标前端应用资源对应的前端应用。

[0155] 可选的，应用部署模块240，包括：后端应用部署单元，该后端应用部署单元被配置为：

[0156] 将各个组件对应的应用程序和当前运行环境打包为镜像文件，作为后端应用，其中，对于某个级别的组件，该组件对应的应用程序包括该组件本身的应用程序及在该组件的功能级别下与该组件具有层级关系的模块、子模块和功能点的应用程序；

[0157] 配置各镜像文件的配置信息，其中，配置信息包括各镜像文件的名称、版本号以及镜像文件分别对应的各级组件；

[0158] 将镜像文件按照所述配置信息上传到所述后端服务底座；

[0159] 为已创建的云控基础平台模型的各级云平台分配运行资源，其中，运行资源包括待部署的目标云平台、在目标云平台运行时所要用到的中央处理器CPU核的数量、内存和硬盘；

[0160] 将镜像文件对应的后端应用安装到所述目标云平台。

[0161] 可选的，本发明实施例提供的装置还包括：

[0162] 端口映射模块，被配置为在将所述目标镜像文件对应的目标后端应用安装到该云平台之后，将目标后端应用对应的端口映射到其他后端应用的端口上，以使其他后端应用能够访问所述目标后端应用对应的端口。

[0163] 本发明实施例所提供的基于云控基础平台的应用部署装置可执行本发明任意实施例所提供的基于云控基础平台的应用部署方法，具备执行方法相应的功能模块和有益效果。未在上述实施例中详尽描述的技术细节，可参见本发明任意实施例所提供的基于云控基础平台的应用部署方法。

[0164] 实施例三

[0165] 图3为本发明实施例三提供的一种计算机设备的结构框图，如图3所示，该计算机设备包括：

[0166] 至少一个处理器(图3中示出了一个处理器520)，

[0167] 处理器520和存储器510耦合，存储器510存储有在处理器520上运行的程序或指令，该程序或指令被处理器520执行时实现本发明任意实施例所提供的基于云控基础平台的应用部署方法。

[0168] 基于上述方法实施例，本发明的另一实施例提供了一种可读存储介质，其上存储有程序或指令，该程序或指令被处理器执行时使处理器实现如上任一实施方式所述的基于云控基础平台的应用部署方法。

[0169] 本领域普通技术人员可以理解：附图只是一个实施例的示意图，附图中的模块或流程并不一定是实施本发明所必须的。

[0170] 本领域普通技术人员可以理解：实施例中的装置中的模块可以按照实施例描述分布于实施例的装置中，也可以进行相应变化位于不同于本实施例的一个或多个装置中。上述实施例的模块可以合并为一个模块，也可以进一步拆分成多个子模块。

[0171] 最后应说明的是：以上实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明实施例技术方案的精神和范围。< / script>

Claims

1. An application deployment method based on a cloud control platform, wherein, The cloud control infrastructure platform consists of three levels: edge cloud, regional cloud, and central cloud. The method includes: Based on business needs, the original cloud control platform is broken down into multiple independent functional units. Each functional unit includes components, modules, sub-modules, and functional points in descending order of functional level. The functional units establish interrelationships through interface functions. The various functional units of each cloud platform are combined in descending order of functional level to form a cloud control basic platform model. The application of the cloud control basic platform model includes front-end applications and back-end applications. The front-end applications are implemented through front-end application resources, which include application interfaces, application menus, images, and runnable executable packages. The back-end applications include at least one application corresponding to a functional unit and its runtime environment. An integrated platform is created, comprising a front-end service platform and a back-end service platform. The front-end service platform is a container that integrates application pages corresponding to functional units at all levels and is used to manage the front-end application resources. The back-end service platform is the infrastructure that supports the operation of cloud control platform applications and is used to manage the various functional units of the cloud control platform model. The front-end application resources are loaded based on the front-end service base, and the back-end application is deployed to the cloud platforms at each level of the cloud control basic platform model according to the functional level of its corresponding functional unit based on the back-end service base.

2. The method according to claim 1, characterized in that, The loading of front-end application resources based on the front-end service platform includes: Create a new node to mount the component; Determine the corresponding target front-end application resources based on user permissions; For each level of cloud platform, the target front-end application resources are loaded based on the front-end service base, and a base global routing variable is registered, wherein the base global routing variable is used to switch between different front-end pages; Accordingly, after loading the front-end application resources based on the front-end service platform, the method further includes: Based on the node, the front-end application corresponding to the target front-end application resource is launched on the front-end service platform.

3. The method according to claim 1, characterized in that, The process of deploying backend applications to various levels of the cloud platform model based on the backend service foundation, according to the functional level of their corresponding functional units, includes: Package the application and current runtime environment corresponding to each component into an image file as a backend application. For a component at a certain level, the application corresponding to the component includes the application of the component itself and the application of modules, sub-modules and function points that have a hierarchical relationship with the component at the functional level of the component. Configure the configuration information for each image file, wherein the configuration information includes the name, version number, and corresponding components at each level of each image file; Upload the image file to the backend service base according to the configuration information; Allocate runtime resources to each level of the cloud platform in the established cloud control infrastructure platform model, wherein the runtime resources include the target cloud platform to be deployed, the number of CPU cores, memory and hard disk to be used when the target cloud platform is running; Install the backend application corresponding to the image file onto the target cloud platform.

4. The method according to claim 3, characterized in that, After installing the target backend application corresponding to the image file onto the cloud platform, the method further includes: The port corresponding to the target backend application is mapped to the port of other backend applications, so that other backend applications can access the port corresponding to the target backend application.

5. An application deployment device based on a cloud control platform, characterized in that, include: The decomposition module is configured to decompose the cloud platform at each level in the original cloud control basic platform into multiple independent functional units according to business needs. Each functional unit includes components, modules, sub-modules and function points in descending order of function level. The functional units establish interrelationships with each other through interface functions. The combination module is configured to combine the various functional units of each level of the cloud platform in descending order of the functional level to form a cloud control basic platform model. The application of the cloud control basic platform model includes front-end applications and back-end applications. The front-end applications are implemented through front-end application resources, which include application interfaces, application menus, images, and runnable executable packages. The back-end applications include at least one application corresponding to a functional unit and its runtime environment. The base creation module is configured to create an integrated base, wherein the integrated base includes a front-end service base and a back-end service base. The front-end service base is a container that integrates application pages corresponding to components at all levels and is used to manage the front-end application resources. The back-end service base is the infrastructure that supports the operation of cloud control platform applications and is used to manage the various functional units of the cloud control platform model. The application deployment module is configured to load the front-end application resources based on the front-end service base, and to deploy the back-end application to the cloud platforms at each level of the cloud control basic platform model according to the functional level of its corresponding functional unit based on the back-end service base.

6. The apparatus according to claim 5, characterized in that, The application deployment module includes: a front-end application deployment unit, which is configured as follows: Create a new node to mount the component; Determine the corresponding target front-end application resources based on user permissions; For each level of cloud platform, the target front-end application resources are loaded based on the front-end service base, and a base global routing variable is registered, wherein the base global routing variable is used to switch between different front-end pages; Accordingly, the device also includes: The front-end application startup module is configured to, after loading the front-end application resources based on the front-end service base, launch the front-end application corresponding to the target front-end application resources on the front-end service base based on the node.

7. The apparatus according to claim 5, characterized in that, The application deployment module includes: a backend application deployment unit, wherein the backend application deployment unit is configured as follows: Package the application and current runtime environment corresponding to each component into an image file as a backend application. For a component at a certain level, the application corresponding to the component includes the application of the component itself and the application of modules, sub-modules and function points that have a hierarchical relationship with the component at the functional level of the component. Configure the configuration information for each image file, wherein the configuration information includes the name, version number, and corresponding components at each level of each image file; Upload the image file to the backend service base according to the configuration information; Allocate runtime resources to each level of the cloud platform in the established cloud control infrastructure platform model, wherein the runtime resources include the target cloud platform to be deployed, the number of CPU cores, memory and hard disk to be used when the target cloud platform is running; Install the backend application corresponding to the image file onto the target cloud platform.

8. The apparatus according to claim 7, characterized in that, The device further includes: The port mapping module is configured to, after the target backend application corresponding to the image file is installed on the cloud platform, map the port corresponding to the target backend application to the port of other backend applications, so that other backend applications can access the port corresponding to the target backend application.

9. A computer device, characterized in that, It includes at least one processor, the processor being coupled to a memory, the memory storing a program or instructions that run on the processor, the program or instructions being executed by the processor to implement the steps of the application deployment method based on the cloud control platform as described in any one of claims 1 to 4.

10. A readable storage medium having a program or instructions stored thereon, characterized in that, When the program or instructions are executed by the processor, they implement the steps of the application deployment method based on the cloud control platform as described in any one of claims 1 to 4.

Images