Video gateway heterogeneous deployment method and device, equipment and storage medium

Abstract

The invention discloses a video gateway heterogeneous deployment method and device, equipment and a storage medium, and relates to the technical field of security monitoring, and the method comprises the steps: obtaining a target installation package, sent by a front end, of a video gateway, judging whether the target installation package is heterogeneous deployment or not based on the architecture information of the target installation package and the host architecture information of a target deployment host appointed by the front end; if the target installation package is heterogeneous deployment, pulling an architecture mirror image corresponding to a current cluster of the target deployment host; if the architecture mirror image corresponding to the current cluster is not pulled, obtaining an installation strategy corresponding to the target installation package; and determining to generate a target architecture corresponding to a current cluster based on the installation strategy, and deploying the target architecture to the current cluster so as to install the target installation package to the current cluster to complete deployment of the video gateway. Therefore, the problems of time consumption and high cost of heterogeneous service adaptation can be solved.

Description

Technical Field

[0001] The present invention relates to the field of security monitoring technology, and in particular to a method, device, equipment and storage medium for heterogeneous deployment of a video gateway. Background Art

[0002] With the changes in the international situation in recent years, the information and communication technology industry has become part of my country's national strategy to achieve independent control in the field of information technology, ensure national information security, and gradually complete the construction of domestic information technology software and hardware underlying architecture system and full-cycle ecological system.

[0003] Video surveillance platforms adapting to the trusted computing platform must support different processor architectures. Existing video platforms are mostly based on the X86 architecture (the computer language instruction set executed by microprocessors). Re-adapting all services to the new architecture requires developing corresponding architecture versions, especially for private video gateways. SDKs (Software Development Kits) from different manufacturers typically include multiple interfaces for registration, heartbeats, adding devices, removing devices, updating devices, streaming, PTZ (a core technology in the security monitoring field) operation, recording, adjusting focus, obtaining device information, setting the time, and calibrating the time. Adapting to multiple architectures requires developing separate SDK versions for each architecture. Adapting every SDK interface is costly, and some older SDK versions may not be supported by the manufacturer, resulting in inoperability.

[0004] Therefore, how to save heterogeneous service adaptation costs when performing heterogeneous deployment of video gateways needs to be solved. Summary of the Invention

[0005] In view of this, the purpose of the present invention is to provide a method, apparatus, device, and storage medium for heterogeneous deployment of video gateways, which can solve the problem of time-consuming and high cost of heterogeneous service adaptation. The specific solution is as follows:

[0006] In a first aspect, the present application discloses a method for heterogeneous deployment of a video gateway, comprising:

[0007] Obtaining a target installation package of the video gateway sent by the front end, and determining whether the target installation package is a heterogeneous deployment based on the architecture information of the target installation package and the host architecture information of the target deployment host specified by the front end;

[0008] If the target installation package is a heterogeneous deployment, then pull the architecture image corresponding to the current cluster of the target deployment host;

[0009] If the architecture image corresponding to the current cluster is not pulled, then obtain the installation policy corresponding to the target installation package;

[0010] A target architecture corresponding to the current cluster is generated based on the installation strategy, and the target architecture is deployed to the current cluster, so that the target installation package is installed to the current cluster to complete the deployment of the video gateway.

[0011] Optionally, before obtaining the target installation package of the video gateway sent by the front end, the method further includes:

[0012] Obtaining the host parameters of the target deployment host sent by the front end, and connecting to the target deployment host using a preset secure shell protocol and the host parameters to add the target deployment host to the local;

[0013] Create a K8S cluster on the target deployment host and generate the kubeconf cluster access configuration file.

[0014] Optionally, the determining whether the target installation package is heterogeneously deployed based on the architecture information of the target installation package and the host architecture information of the target deployment host specified by the front end includes:

[0015] Parsing each installation package uploaded by the front end through a preset interface to obtain each parsed installation package, and uploading each parsed installation package to the object storage;

[0016] Obtaining the video gateway deployment instruction sent by the front end, and obtaining the target installation package and determining the target deployment host from the object storage based on the video gateway deployment instruction;

[0017] It is determined whether the target installation package is heterogeneously deployed based on the architecture information of the target installation package and the host architecture information of the target deployment host.

[0018] Optionally, after determining whether the target installation package is heterogeneously deployed based on the architecture information of the target installation package and the host architecture information of the target deployment host specified by the front end, the method further includes:

[0019] If the target installation package is a homogeneous deployment, the target installation package is installed to the current cluster, and the nodeSelector attribute is bound to the target deployment host using the k8s resource file to complete the deployment of the video gateway.

[0020] Optionally, if the target installation package is a heterogeneous deployment, after pulling the architecture image corresponding to the current cluster of the target deployment host, the method further includes:

[0021] If the architecture image corresponding to the current cluster is pulled, the target installation package is installed to the current cluster using the architecture image, and the nodeSelector attribute is bound to the target deployment host using the k8s resource file to complete the deployment of the video gateway.

[0022] Optionally, if the installation strategy is a heterogeneous container simulation deployment strategy, then determining and generating a target architecture corresponding to the current cluster based on the installation strategy, and deploying the target architecture to the current cluster, so as to install the target installation package to the current cluster to complete the deployment of the video gateway, includes:

[0023] Install the qemu-user-static component and binfmt-support component on the node of the target deployment host, and activate the target architecture support;

[0024] The image in the service chart template is set as the target architecture, and the target architecture is deployed to the current cluster so that the target installation package is installed to the current cluster to complete the deployment of the video gateway.

[0025] Optionally, if the installation strategy is a heterogeneous virtual machine deployment strategy, then determining and generating a target architecture corresponding to the current cluster based on the installation strategy, and deploying the target architecture to the current cluster, so as to install the target installation package to the current cluster to complete the deployment of the video gateway, includes:

[0026] Deploy a target virtual machine with the same architecture as the target installation package on a node of the target deployment host using the Kubevirt component;

[0027] The target virtual machine is added to the current cluster, and the target installation package is installed to the target virtual machine to complete the deployment of the video gateway.

[0028] In a second aspect, the present application discloses a video gateway heterogeneous deployment device, comprising:

[0029] An installation package acquisition module is used to obtain the target installation package of the video gateway sent by the front end, and determine whether the target installation package is a heterogeneous deployment based on the architecture information of the target installation package and the host architecture information of the target deployment host specified by the front end;

[0030] An image architecture pulling module is used to pull the architecture image corresponding to the current cluster of the target deployment host if the target installation package is a heterogeneous deployment;

[0031] An installation strategy determination module, configured to obtain an installation strategy corresponding to the target installation package if the architecture image corresponding to the current cluster is not pulled;

[0032] The installation package deployment module is used to determine and generate a target architecture corresponding to the current cluster based on the installation strategy, and deploy the target architecture to the current cluster so as to install the target installation package to the current cluster to complete the deployment of the video gateway.

[0033] In a third aspect, the present application discloses an electronic device, comprising:

[0034] Memory, used to store computer programs;

[0035] A processor is used to execute the computer program to implement the aforementioned video gateway heterogeneous deployment method.

[0036] In a fourth aspect, the present application discloses a computer-readable storage medium for storing a computer program, which, when executed by a processor, implements the aforementioned video gateway heterogeneous deployment method.

[0037] It can be seen that in this application, the target installation package of the video gateway sent by the front end is obtained, and based on the architecture information of the target installation package and the host architecture information of the target deployment host specified by the front end, it is determined whether the target installation package is a heterogeneous deployment; if the target installation package is a heterogeneous deployment, the architecture image corresponding to the current cluster of the target deployment host is pulled; if the architecture image corresponding to the current cluster is not pulled, the installation policy corresponding to the target installation package is obtained; based on the installation policy, the target architecture corresponding to the current cluster is generated, and the target architecture is deployed to the current cluster, so that the target installation package is installed to the current cluster to complete the deployment of the video gateway. That is, by judging whether the service is enabled for heterogeneous deployment based on the architecture information, and determining the corresponding installation policy based on the architecture image corresponding to the target installation package, and finally using the corresponding installation policy for heterogeneous deployment. In this way, the corresponding installation strategy is determined for different deployment methods, which realizes automatic adaptation of the host architecture, simple and efficient real-time installation and deployment, and operation and maintenance, and solves the problem of high time-consuming and costly adaptation of heterogeneous deployment services. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are merely embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0039] Figure 1 This is a flow chart of a method for heterogeneous deployment of video gateways disclosed in this application;

[0040] Figure 2 A flowchart of a specific host management method disclosed in this application;

[0041] Figure 3 A flow chart of a specific cluster management method disclosed in this application;

[0042] Figure 4 A flow chart of a specific cluster deployment management method disclosed in this application;

[0043] Figure 5 A flowchart of a specific configuration management method disclosed in this application;

[0044] Figure 6 This is a flowchart of a specific video gateway heterogeneous deployment method disclosed in this application;

[0045] Figure 7 This is a schematic diagram of the structure of a heterogeneous deployment device for a video gateway disclosed in this application;

[0046] Figure 8 This is a structural diagram of an electronic device disclosed in this application. DETAILED DESCRIPTION

[0047] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0048] In the existing technology, the adaptation and debugging of heterogeneous deployment of video gateways takes too long. In order to save the adaptation cost of heterogeneous deployment of video gateways and achieve a balance between cost and function, this application will specifically introduce a heterogeneous deployment method of video gateways, which can make deployment and operation simple and efficient, and save adaptation costs.

[0049] See also Figure 1 As shown, the embodiment of the present application discloses a method for heterogeneous deployment of a video gateway, including:

[0050] Step S11: Obtain the target installation package of the video gateway sent by the front end, and determine whether the target installation package is a heterogeneous deployment based on the architecture information of the target installation package and the host architecture information of the target deployment host specified by the front end.

[0051] In this embodiment, before obtaining the target video gateway installation package sent by the front-end, the process also includes: obtaining the host parameters of the target deployment host sent by the front-end, connecting to the target deployment host using a preset secure shell protocol and the host parameters to add the target deployment host to the local computer; creating a K8S cluster on the target deployment host, and generating a kubeconf cluster access configuration file. This involves both host management and centralized management.

[0052] The first is host management, such as Figure 2 As shown, host management enables management of server hosts of different architectures, providing available host resources for creating Kubernetes clusters. First, you can add a host through the deployment frontend. Adding parameters includes the host's Internet Protocol (IP), port, user, password, and description. The deployment backend connects to the host via SSH (Secure Shell) and updates information such as the host's online status, CPU (Central Processing Unit) resources, memory resources, and CPU architecture. Adding hosts also supports virtual machines, meaning you can add virtual machine hosts. When deleting, modifying, or querying hosts, you can specifically delete host resources through the deployment frontend. Deletion checks whether the host is in use; if so, deletion is prohibited and an error is displayed. The host's IP, port, user, and password can be modified, and the host status is updated after the modification is complete. For active hosts, changes to their IP and port information will not be synchronized to the Kubernetes (Kubernetes, an open-source platform for managing containerized applications across multiple hosts in a cloud platform) cluster nodes. Updates to the cluster require adding or removing nodes. When querying hosts, query parameters include IP, user, tags, and description information. Additionally, host management allows you to add and remove tags to distinguish nodes.

[0053] The second is cluster management, such as Figure 3As shown, cluster management enables Kubernetes cluster management, providing a basic deployment environment for service deployment. When creating a cluster, you can manage third-party clusters using kubeconf for service deployment and uninstallation, but you cannot delete or add or remove nodes from the cluster. You can also create a cluster using host resources added in host management. You can select an available online host to create a cluster, perform password-free login on the selected host, install the qemu-user-static emulation component, configure the image repository, send the cluster deployment package, and send the GPU (Graphics Processing Unit) driver package. During deployment, you can configure whether the node is schedulable. After cluster creation, the deployment backend periodically checks the cluster, providing real-time updates on cluster status, node online status, node CPU resource information, node GPU resource information, and node memory resource information. Cluster management allows you to add and remove nodes to the local cluster; third-party clusters are not allowed to add or remove nodes. When adding a node, perform password-free login on the selected host, install the qemu-user-static emulation component, configure the image repository, send the cluster deployment package, send the GPU driver package, and then add the node to the cluster. When deleting a node, determine whether the node has a deployed service or whether it is the last control node (Master node) of the K8S cluster. If so, the deletion is rejected and an error message is returned. After the node is deleted, the host management updates the node management status to No, and the host becomes available. When deleting a cluster, determine whether the cluster node can be deleted. For non-third-party clusters, the judgment logic is the same as node deletion. If the node can be deleted, it will be deleted. For managed third-party clusters, the management information is deleted, and the actual cluster still exists on the third party. When updating a cluster, you can update the cluster description information, cluster name, and other information. To query the cluster, you can perform cluster query operations based on the cluster name and description information.

[0054] In this embodiment, determining whether the target installation package is a heterogeneous deployment based on the architecture information of the target installation package and the host architecture information of the target deployment host specified by the front-end includes: parsing each installation package uploaded by the front-end through a preset interface to obtain each parsed installation package, and uploading each parsed installation package to an object storage; obtaining a video gateway deployment instruction sent by the front-end, and obtaining the target installation package and determining the target deployment host from the object storage based on the video gateway deployment instruction; and determining whether the target installation package is a heterogeneous deployment based on the architecture information of the target installation package and the host architecture information of the target deployment host. Specifically, the deployment front-end uploads a service deployment package in a specific format, and the deployment back-end parses and stores the package and displays the package information. The host management interface supports adding hosts, supporting both physical and virtual machines. After adding a host, the deployment service connects to the host through SSH to check the host status and update it to an online and normal state. It also obtains the host's CPU, memory, and other resource information. To create a cluster, select an online and normal host in the host management to create a Kubernetes cluster. Third-party clusters can also be managed through the kubeconf information API (Application Programming Interface). After the cluster is successfully created, use the API to obtain CPU and memory usage information for the cluster nodes. Select the service to deploy and click Install. During installation, you will need to select the deployment cluster and cluster nodes. You can modify the service configuration and click OK to begin deployment. The backend then determines whether the deployment service package architecture is identical to the deployment host architecture.

[0055] In this embodiment, after determining whether the target installation package is a heterogeneous deployment based on the architecture information of the target installation package and the host architecture information of the target deployment host specified by the front-end, it also includes: if the target installation package is a homogeneous deployment, the target installation package is installed to the current cluster, and the nodeSelector attribute is bound to the target deployment host using the k8s resource file to complete the deployment of the video gateway. Specifically, the same architecture (homogeneous deployment) is directly deployed to the host selected in the cluster, and is bound to the selected host through the nodeSelector attribute of the k8s resource file.

[0056] Step S12: If the target installation package is a heterogeneous deployment, then pull the architecture image corresponding to the current cluster of the target deployment host.

[0057] In this embodiment, if the target installation package is a heterogeneous deployment, after pulling the architecture image corresponding to the current cluster of the target deployment host, it also includes: if the architecture image corresponding to the current cluster is pulled, the target installation package is installed to the current cluster using the architecture image, and the nodeSelector attribute is bound to the target deployment host using the k8s resource file to complete the deployment of the video gateway. In this embodiment, if it is heterogeneous, an attempt is made to pull a service image with the same architecture as the host, and if it exists, it is directly deployed to the selected K8S cluster node.

[0058] Step S13: If the architecture image corresponding to the current cluster is not pulled, the installation policy corresponding to the target installation package is obtained.

[0059] Step S14: Determine and generate a target architecture corresponding to the current cluster based on the installation strategy, and deploy the target architecture to the current cluster, so as to install the target installation package to the current cluster to complete the deployment of the video gateway.

[0060] In this embodiment, if the installation strategy is a heterogeneous container simulation deployment strategy, then the target architecture corresponding to the current cluster is generated based on the installation strategy, and the target architecture is deployed to the current cluster, so that the target installation package is installed to the current cluster to complete the deployment of the video gateway, including: installing the qemu-user-static component and the binfmt-support component on the node of the target deployment host, and activating the target architecture support; setting the image in the service chart template to the target architecture, and deploying the target architecture to the current cluster, so that the target installation package is installed to the current cluster to complete the deployment of the video gateway. Specifically, if the service package installation strategy is container simulation, then determine whether the selected K8S cluster node has qemu-user-static and binfmt-support installed. If not, install them, and then deploy the selected heterogeneous service package image to the specified cluster node.

[0061] In this embodiment, if the installation strategy is a heterogeneous virtual machine deployment strategy, then the target architecture corresponding to the current cluster is generated based on the installation strategy, and the target architecture is deployed to the current cluster, so that the target installation package is installed to the current cluster to complete the deployment of the video gateway, including: using the Kubevirt component to deploy a target virtual machine with the same architecture as the target installation package on the node of the target deployment host; adding the target virtual machine to the current cluster, and installing the target installation package to the target virtual machine to complete the deployment of the video gateway. Specifically, if the service package installation strategy is a virtual machine method, a virtual machine with the same architecture as the installation package is deployed on the selected cluster node through kubevirt, and after network configuration, the created virtual machine is added to the K8S cluster, and then the installation package is deployed to the virtual machine.

[0062] Finally, after the service is successfully installed, the deployment service periodically obtains and displays the service status through the API interface provided by K8S. The service is running normally.

[0063] like Figure 4As shown, the specific process of service deployment is as follows: click Deploy on the deployment front-end, select the installation package to be deployed on the interface, select the host to be deployed, and click Deploy. The deployment back-end receives the deployment instruction and determines whether it is heterogeneous based on the package architecture information and the host architecture information. If the architecture is the same, it is directly deployed to the host selected in the cluster and bound to the selected host through the nodeSelector attribute of the k8s resource file. For heterogeneous hosts, for example, if the service image architecture for deployment on an X86 server host is ARRCH64, the container image of the same architecture amd64 architecture is first pulled according to the host architecture X86. If the same architecture image is pulled, this image is used to deploy directly to the selected host. If the same architecture image is not pulled, deployment is performed according to the service package deployment strategy. The service can be run by creating a kvm virtual machine or container simulation. The virtual machine method, for example, deploys ARM64 architecture services on an X86 host. Qemu and KVM components are installed on the X86 host to support heterogeneous startup of container virtual machines. Then, the Kubevirt component installed on the K8S cluster is used to create an ARM64 architecture KVM virtual machine. After the virtual machine is created, nodes are added to the cluster through the cluster management function. The newly created ARM64 virtual machine is added to the cluster as a node running the ARM64 architecture service. Modify the image name in the service chart template, set the image to the ARM64 architecture, and use Helm to render the deployment template into a YAML (a highly readable format for expressing data serialization) resource type file directly supported by the K8S cluster. The deployment backend is applied to the K8S cluster using the K8s API. During the K8s container runtime of the ARM64 virtual machine node, containerd pulls the configured service image and starts the container, completing the deployment and operation of the ARRCH64 architecture service on the X86 node. For third-party clusters that do not support node operations, an error is directly reported and the installation is rejected. If using the container method, for example, select an X86 node host to deploy the ARRCH64 architecture service, install qemu-user-static and binfmt-support on the X86 node, and activate ARRCH64 architecture support. Modify the image name in the service chart template, set the image to the ARRCH64 architecture, use Helm to render the deployment template into a YAML resource type file directly supported by the K8S cluster, and deploy the backend using the k8s API to apply it to the K8S cluster. During the k8s container runtime, containerd pulls the set image and starts the container in a heterogeneous manner, thus completing the deployment and operation of the ARRCH64 architecture service on the X86 node. It should be noted that for heterogeneous deployment, whether using a virtual machine or container simulation method, there will be some performance loss. This is more suitable for services such as video gateways that support multi-service deployment and do not support specific architectures.For example, the Hikvision Private Gateway, Dahua Private Gateway, and Uniview Private Gateway all offer C++ SDKs, enabling simulated deployment to reduce modification and adaptation workload. Performance losses are mitigated by deploying multiple services. GB28181 and ONVIF protocol video gateways are relatively universal, making adaptation and modification relatively simple, allowing for direct deployment of services with the same architecture.

[0064] In addition, Figure 5 As shown, you can modify the configuration files of services deployed in the cluster. You can restore the default configuration or modify the configuration directly, such as changing the value of a configuration item or adding or removing a configuration item. Each time you modify the configuration, the current configuration is saved in advance for restoring the previous configuration. The previous configuration is only saved for the configuration before the last modification, and can only be restored once; it is not possible to restore the previous configuration continuously. Configuration management uses the Consul component to manage service configurations. Services monitor configuration keys and reset configuration information when they detect a configuration change, which takes effect immediately.

[0065] It can be seen that in this application, Figure 6 As shown, the target installation package of the video gateway sent by the front end is obtained, and based on the architecture information of the target installation package and the host architecture information of the target deployment host specified by the front end, it is determined whether the target installation package is a heterogeneous deployment; if the target installation package is a heterogeneous deployment, the architecture image corresponding to the current cluster of the target deployment host is pulled; if the architecture image corresponding to the current cluster is not pulled, the installation policy corresponding to the target installation package is obtained; based on the installation policy, the target architecture corresponding to the current cluster is generated, and the target architecture is deployed to the current cluster, so that the target installation package is installed to the current cluster to complete the deployment of the video gateway. That is, by judging whether the service is enabled for heterogeneous deployment based on the architecture information, and determining the corresponding installation policy based on the architecture image corresponding to the target installation package, and finally using the corresponding installation policy for heterogeneous deployment. In this way, the corresponding installation strategy is determined for different deployment methods, which realizes automatic adaptation of the host architecture, simple and efficient real-time installation and deployment, and operation and maintenance, and solves the problem of high time-consuming and costly adaptation of heterogeneous deployment services.

[0066] refer to Figure 7 The embodiment of the present application further discloses a video gateway heterogeneous deployment device, including:

[0067] An installation package acquisition module 11 is configured to acquire a target installation package of the video gateway sent by the front end, and determine whether the target installation package is a heterogeneous deployment based on the architecture information of the target installation package and the host architecture information of the target deployment host specified by the front end;

[0068] The image architecture pulling module 12 is used to pull the architecture image corresponding to the current cluster of the target deployment host if the target installation package is a heterogeneous deployment;

[0069] An installation strategy determination module 13 is configured to obtain an installation strategy corresponding to the target installation package if the architecture image corresponding to the current cluster is not pulled;

[0070] The installation package deployment module 14 is used to determine and generate a target architecture corresponding to the current cluster based on the installation strategy, and deploy the target architecture to the current cluster, so as to install the target installation package to the current cluster to complete the deployment of the video gateway.

[0071] It can be seen that in this embodiment, corresponding installation strategies are determined for different deployment methods, which realizes automatic adaptation of the host architecture, makes real-time installation and deployment simple and efficient in operation and maintenance, and solves the problem of time-consuming and high cost of heterogeneous deployment service adaptation.

[0072] In some specific embodiments, the video gateway heterogeneous deployment device may further include:

[0073] A host adding module is used to obtain the host parameters of the target deployment host sent by the front end, and connect to the target deployment host using a preset secure shell protocol and the host parameters to add the target deployment host to the local;

[0074] The cluster deployment module is used to create a K8S cluster on the target deployment host and generate a kubeconf cluster access configuration file.

[0075] In some specific embodiments, the installation package acquisition module 11 may specifically include:

[0076] The installation package parsing unit is used to parse each installation package uploaded by the front end through a preset interface to obtain each parsed installation package, and upload each parsed installation package to the object storage;

[0077] An instruction acquisition unit, configured to acquire the video gateway deployment instruction sent by the front end, and acquire a target installation package from the object storage and determine a target deployment host based on the video gateway deployment instruction;

[0078] The deployment status judgment unit is configured to judge whether the target installation package is heterogeneously deployed based on the architecture information of the target installation package and the host architecture information of the target deployment host.

[0079] In some specific embodiments, the video gateway heterogeneous deployment device may further include:

[0080] The isomorphic deployment module is used to install the target installation package to the current cluster if the target installation package is an isomorphic deployment, and use the k8s resource file to bind the nodeSelector attribute to the target deployment host to complete the deployment of the video gateway.

[0081] In some specific embodiments, the video gateway heterogeneous deployment device may further include:

[0082] The image pulling module is used to use the architecture image to install the target installation package to the current cluster if the architecture image corresponding to the current cluster is pulled, and use the k8s resource file to bind the nodeSelector attribute to the target deployment host to complete the deployment of the video gateway.

[0083] In some specific embodiments, the installation package deployment module 14 may specifically include:

[0084] A component installation unit, configured to install the qemu-user-static component and the binfmt-support component on the node of the target deployment host, and activate target architecture support;

[0085] The first video gateway deployment unit is used to set the mirror in the service chart template as the target architecture and deploy the target architecture to the current cluster so as to install the target installation package to the current cluster to complete the deployment of the video gateway.

[0086] In some specific embodiments, the installation package deployment module 14 may specifically include:

[0087] A virtual machine deployment unit, configured to deploy a target virtual machine having the same architecture as the target installation package on a node of the target deployment host using a Kubevirt component;

[0088] The second video gateway deployment unit is used to add the target virtual machine to the current cluster and install the target installation package to the target virtual machine to complete the deployment of the video gateway.

[0089] Furthermore, the embodiment of the present application also discloses an electronic device, Figure 8 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content in the diagram should not be considered as any limitation to the scope of application of the present application.

[0090] Figure 8This is a schematic diagram of the structure of an electronic device 20 provided in an embodiment of the present application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 is used to store a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the heterogeneous deployment method of the video gateway disclosed in any of the aforementioned embodiments. In addition, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0091] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and the external device. The communication protocol it follows is any communication protocol that can be applied to the technical solution of this application and is not specifically limited here; the input and output interface 25 is used to obtain external input data or output data to the outside world. Its specific interface type can be selected according to specific application needs and is not specifically limited here.

[0092] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or CD, etc. The resources stored thereon can include an operating system 221, a computer program 222, etc., and the storage method can be temporary storage or permanent storage.

[0093] The operating system 221 is used to manage and control the hardware devices and computer program 222 on the electronic device 20. The operating system 221 can be Windows Server, NetWare, Unix, Linux, etc. In addition to including computer programs capable of implementing the video gateway heterogeneous deployment method performed by the electronic device 20 as disclosed in any of the aforementioned embodiments, the computer program 222 can further include computer programs capable of performing other specific tasks.

[0094] Furthermore, this application also discloses a computer-readable storage medium for storing a computer program; wherein, when executed by a processor, the computer program implements the aforementioned method for heterogeneous deployment of video gateways. The specific steps of this method can be referred to the corresponding content disclosed in the aforementioned embodiments and will not be repeated here.

[0095] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from the other embodiments. Reference can be made to the descriptions of the identical or similar parts between the various embodiments. For the devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple, and the relevant parts can be referred to the descriptions of the methods.

[0096] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0097] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0098] Finally, it should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or device comprising the element.

[0099] The above is a detailed introduction to the technical solution provided by the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for those skilled in the art, according to the ideas of the present application, there may be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A video gateway heterogeneous deployment method, characterized in that: include: Obtaining a target installation package of the video gateway sent by the front end, and determining whether the target installation package is a heterogeneous deployment based on the architecture information of the target installation package and the host architecture information of the target deployment host specified by the front end; If the target installation package is a heterogeneous deployment, then pull the architecture image corresponding to the current cluster of the target deployment host; If the architecture image corresponding to the current cluster is not pulled, then obtain the installation policy corresponding to the target installation package; A target architecture corresponding to the current cluster is generated based on the installation strategy, and the target architecture is deployed to the current cluster, so that the target installation package is installed to the current cluster to complete the deployment of the video gateway.

2. The video gateway heterogeneous deployment method according to claim 1, characterized in that: Before obtaining the target installation package of the video gateway sent by the front end, the method further includes: Obtaining the host parameters of the target deployment host sent by the front end, and connecting to the target deployment host using a preset secure shell protocol and the host parameters to add the target deployment host to the local; Create a K8S cluster on the target deployment host and generate the kubeconf cluster access configuration file.

3. The video gateway heterogeneous deployment method according to claim 1, characterized in that: The determining whether the target installation package is heterogeneously deployed based on the architecture information of the target installation package and the host architecture information of the target deployment host specified by the front end includes: Parsing each installation package uploaded by the front end through a preset interface to obtain each parsed installation package, and uploading each parsed installation package to the object storage; Obtaining the video gateway deployment instruction sent by the front end, and obtaining the target installation package and determining the target deployment host from the object storage based on the video gateway deployment instruction; Whether the target installation package is heterogeneously deployed is determined based on the architecture information of the target installation package and the host architecture information of the target deployment host.

4. The method for heterogeneous deployment of video gateways according to claim 1, wherein: After determining whether the target installation package is heterogeneous deployment based on the architecture information of the target installation package and the host architecture information of the target deployment host specified by the front end, the method further includes: If the target installation package is a homogeneous deployment, the target installation package is installed to the current cluster, and the nodeSelector attribute is bound to the target deployment host using the k8s resource file to complete the deployment of the video gateway.

5. The method for heterogeneous deployment of video gateways according to claim 1, wherein: If the target installation package is a heterogeneous deployment, after pulling the architecture image corresponding to the current cluster of the target deployment host, the method further includes: If the architecture image corresponding to the current cluster is pulled, the target installation package is installed to the current cluster using the architecture image, and the nodeSelector attribute is bound to the target deployment host using the k8s resource file to complete the deployment of the video gateway.

6. The method for heterogeneous deployment of video gateways according to claim 1, wherein: If the installation strategy is a heterogeneous container simulation deployment strategy, then determining and generating a target architecture corresponding to the current cluster based on the installation strategy, and deploying the target architecture to the current cluster, so as to install the target installation package to the current cluster to complete the deployment of the video gateway, includes: Install the qemu-user-static component and binfmt-support component on the node of the target deployment host, and activate the target architecture support; The image in the service chart template is set as the target architecture, and the target architecture is deployed to the current cluster so that the target installation package is installed to the current cluster to complete the deployment of the video gateway.

7. The method for heterogeneous deployment of video gateways according to claim 1, wherein: If the installation strategy is a heterogeneous virtual machine deployment strategy, then determining and generating a target architecture corresponding to the current cluster based on the installation strategy, and deploying the target architecture to the current cluster, so as to install the target installation package to the current cluster to complete the deployment of the video gateway, includes: Deploy a target virtual machine with the same architecture as the target installation package on a node of the target deployment host using the Kubevirt component; The target virtual machine is added to the current cluster, and the target installation package is installed to the target virtual machine to complete the deployment of the video gateway.

8. A video gateway heterogeneous deployment device, characterized in that: include: An installation package acquisition module is used to obtain the target installation package of the video gateway sent by the front end, and determine whether the target installation package is a heterogeneous deployment based on the architecture information of the target installation package and the host architecture information of the target deployment host specified by the front end; An image architecture pulling module is used to pull the architecture image corresponding to the current cluster of the target deployment host if the target installation package is a heterogeneous deployment; An installation strategy determination module, configured to obtain an installation strategy corresponding to the target installation package if the architecture image corresponding to the current cluster is not pulled; The installation package deployment module is used to determine and generate a target architecture corresponding to the current cluster based on the installation strategy, and deploy the target architecture to the current cluster so as to install the target installation package to the current cluster to complete the deployment of the video gateway.

9. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor, configured to execute the computer program to implement the video gateway heterogeneous deployment method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that Used to store a computer program, which, when executed by a processor, implements the video gateway heterogeneous deployment method as described in any one of claims 1 to 7.

Images