CN115700465A

CN115700465A - Movable electronic equipment and application thereof

Info

Publication number: CN115700465A
Application number: CN202211396977.0A
Authority: CN
Inventors: 请求不公布姓名
Original assignee: Anchao Cloud Software Co Ltd
Current assignee: Anchao Cloud Software Co Ltd
Priority date: 2022-11-09
Filing date: 2022-11-09
Publication date: 2023-02-07
Anticipated expiration: 2042-11-09
Also published as: CN115700465B

Abstract

The invention belongs to the technical field of software deployment, and provides a movable electronic device, which comprises: the system bus is coupled to the CI/CD unit, the processor and the memory of the system bus; the CI/CD unit consists of a local disk, a CI/CD agent and an application code warehouse; the CI/CD agent determines at least one mirror image template to be synchronized to the equipment to be deployed, and synchronizes the mirror image template to a specified disk partition in the equipment to be deployed; the equipment to be deployed is restarted after a physical machine operating system is installed according to a system disk image file loaded by a CI/CD unit and at least one image template to be synchronized to a specified disk partition in the equipment to be deployed; and setting the starting path of the equipment to be deployed to be started from the disk containing the specified disk partition. The installation efficiency of executing and installing the operating system of the physical machine on the equipment to be deployed is remarkably improved.

Description

Movable electronic equipment and application thereof

Technical Field

The invention relates to the technical field of software deployment, in particular to a movable electronic device and application thereof.

Background

CI/CD is a method of delivering applications to customers frequently by introducing automation during the application development phase. Continuous Integration (CI) means that multiple developers can frequently merge lines of code together and do not affect each other in the process of developing different function codes. Continuous Deployment (CD) refers to delivering a product to an online environment on the basis of Continuous deployment to deploy a continuously integrated code to a class production environment (for example, a device to be deployed in which an operating system of a physical machine has been installed in the present application) closer to a real operating environment, so that software is completed in a short time, development, test, and release of the software are ensured to be more convenient, development cycle and development cost based on the software in the device to be deployed are reduced, and risk of software development failure is reduced.

Firstly, the physical machine deploying the virtual machine needs to be frequently rebuilt in the CI/CD process, and the physical machine as the device to be deployed needs to pull up the virtual machine by repeatedly loading a system disk image file (e.g., an ISO file) in the rebuilding process. For example, when a physical machine installs a physical machine operating system image file (e.g., centOS7.9) via an image file, centOS-7-x86_64-DVD-2009.Iso (i.e., a system disk image file) needs to be used. However, to start the virtual machine of the CentOS7.9 operating system, the image file (i.e., virtual machine image template) of CentOS7.9-X86_64.RAW also needs to be used. It can be seen that the formats and contents of the image files used by the physical machine and the virtual machine are different. Therefore, when a large number of virtual machines are frequently started, the management difficulty of the image files is very complicated, and the virtual machines and the services and applications based on the virtual machines cannot be effectively started due to the error of the image files of the system disk loaded by the virtual machine during the starting. Secondly, the physical machine in the prior art needs to install the operating system of the physical machine through the system disk image file based on the ISO format, and in the process of installing the operating system of the physical machine, because decompression, calculation, numerous small files contained in the system disk image file and other objective reasons need to be executed, the system disk image file is written into the device to be deployed and the resources such as the CPU, the memory, the storage, the network bandwidth and the like of the physical machine are greatly consumed in the installation process, and therefore, the operation process of installing the system disk image file to construct the operating system of the physical machine and subsequently pulling up and starting the virtual machine in the physical machine is very long. In addition, when the device to be deployed is located in a different place and needs to be continuously deployed through a network, delay exists and certain consumption is caused on the computing performance of a local computer plugged with the mobile electronic device for continuous integration and continuous deployment, so that difficulties are caused on continuous deployment, upgrading and version maintenance of a system disk image file and a virtual machine image template, and further difficulties are caused on the efficiency of software development and service operation executed in a physical machine which is continuously deployed.

In view of the above, there is a need for an improved apparatus for performing persistent integration and persistent deployment via network connection in the prior art to solve the above problems.

Disclosure of Invention

The invention aims to disclose a mobile electronic device and application thereof, which are used for solving the technical problem of difficult maintenance caused by non-uniform image file formats of operating systems of physical machines which need to be repeatedly installed in continuous deployment in the prior art, improving software development efficiency, ensuring the sustainable operation of deployed services in the device to be deployed, improving the flexibility of executing continuous deployment of the device to be deployed, reducing the consumption and dependence on network bandwidth in the continuous deployment process, releasing the computing performance of a computer plugged with the mobile electronic device, and improving the efficiency of executing continuous integration and continuous deployment of the device to be deployed.

To achieve one of the above objects, the present invention provides a removable electronic device logically independent of a device to be deployed for which continuous deployment is performed,

the method comprises the following steps: the system bus is coupled to the CI/CD unit, the processor and the memory of the system bus; the CI/CD unit consists of a local disk, a CI/CD agent and an application code warehouse;

the CI/CD agent determines at least one mirror image template to be synchronized to the equipment to be deployed, and synchronizes the mirror image template to a specified disk partition in the equipment to be deployed; the equipment to be deployed is restarted after a physical machine operating system is installed according to a system disk image file loaded by a CI/CD unit and at least one image template to be synchronized to a specified disk partition in the equipment to be deployed; and setting the starting path of the equipment to be deployed as the starting path from the disk comprising the specified disk partition.

As a further improvement of the invention, the equipment to be deployed is controlled by a CI/CD agent, and the system disk image file in the local disk is guided to be switched to a rescue mode by a rescue system deployed by the equipment to be deployed in a system disk partition of the equipment to be deployed based on an IPMI protocol, so as to load the system disk image file for installing the physical machine operating system based on the rescue mode.

As a further improvement of the present invention, at least one mirror image template to be synchronized to a specified disk partition in a device to be deployed is determined by being pre-saved in the local disk, or is determined by being imported under the control of a CI/CD agent by an application code repository that establishes a session with the local disk;

the system disk image file is independent of the image template, independent of the latest code and adaptive to commodity attributes of the equipment to be deployed, and the commodity data is defined by the manufacturer, the model and the version of the equipment to be deployed individually or together.

As a further improvement of the present invention, the application code repository is hosted by a CI/CD agent, and the mirror template is constructed by a preconfigured script deployed in the application code repository, and after the mirror template is synchronized to a disk partition specified by the device to be deployed, the specified disk partition is used as a system disk of the device to be deployed; the file format of the mirror image template comprises raw, qcow2, vmdk or ova.

As a further improvement of the present invention, a system disk image file on which the device to be deployed depends is pre-stored in the local disk, the CI/CD agent pulls at least one image template from an application code repository, and loads the system disk image file to a virtual optical drive deployed by the device to be deployed;

and guiding the rescue system to read the system disk image file always stored in the CI/CD unit based on the IPMI protocol, setting the equipment to be deployed to be started from the system disk image file located in the CI/CD unit, and installing a physical machine operating system in the equipment to be deployed according to the system disk image file.

As a further improvement of the present invention, the CI/CD agent pulls at least one image template from the application code repository, loads a system disk image file that the device to be deployed depends on through the CI/CD agent, and loads the system disk image file to a virtual optical drive deployed by the device to be deployed;

As a further improvement of the present invention, the mirror image template is synchronized to at least one disk partition associated with the device to be deployed, the mirror image template is synchronized to the disk partition, a virtual machine is started by the disk partition serving as a system disk, and the disk partition is mounted to the created virtual machine in the device to be deployed; wherein the disk partition is logically located on the device to be deployed and visible to the CI/CD unit.

As a further improvement of the present invention, the CI/CD agent loads a mirror template to at least one piece of device deployed in a local disk, creates a disk partition in the device to be deployed, where the number of the piece of device and the disk space are the same, and the piece of device is controlled by the CI/CD agent based on a data synchronization protocol to map the piece of device to the disk partition in the device to be deployed, and starts a start path setting of the device to be deployed from the disk partition on which the piece of device is mounted and on which the mirror template synchronization job has been completed.

As a further improvement of the present invention, the local disk creates at least one disk partition of a block device formed by mapping a device to be deployed to the local disk, the block device and a disk partition specified in the device to be deployed establish a mapping relationship based on a data synchronization protocol, so as to establish a data synchronization path between the block device and the disk partition, and after data synchronization is completed, disconnect the mapping relationship and unload the block device located in the local disk;

the data synchronization protocol comprises an rsync protocol or an iSCSI protocol, and the block device comprises a network block device or a loop device.

As a further improvement of the present invention, the CI/CD agent generates a copy instruction to synchronize the mirror image template and the file directory corresponding to the mirror image template to the specified disk partition in the device to be deployed based on the mapping relationship based on the copy command; synchronizing a mirror image template and a file directory in a local disk to a specified disk partition in equipment to be deployed through the data synchronization protocol based on the disk partition determined by the mapping relation;

after the mirror image template is synchronized to the specified disk partition in the equipment to be deployed, a plurality of virtual machines running in the equipment to be deployed are created according to the mirror image template, and the equipment to be deployed and the virtual machines deployed in the equipment to be deployed are created and started at least based on one same mirror image template.

As a further improvement of the present invention, a disk including the specified disk partition or a specified disk partition is mapped to a block device of a local disk based on a mapping relationship corresponding to the data synchronization protocol, a copy command selection policy is determined by the CI/CD agent acquiring a data specification of a mirror image template, so as to synchronize the mirror image template and a file directory corresponding to the mirror image template to the specified disk partition in a device to be deployed based on a dd copy command or an rsync copy command alternatively; the data specification is defined by the size of the file contained in the mirror image template and the proportion of the small file.

As a further improvement of the present invention, the copy command selection policy includes:

if the proportion of the small files is larger than or equal to 50%, the files are smaller than or equal to 64KB and smaller than or equal to 64KB, and the mirror image template and the file directory corresponding to the mirror image template are synchronized to the disk partition appointed in the equipment to be deployed through the mapping relation based on the dd copying command;

and if the small file occupation ratio of the file is larger than 64KB or smaller than or equal to 64KB and is less than 50%, synchronizing the mirror image template and the file directory corresponding to the mirror image template to the specified disk partition in the equipment to be deployed through the mapping relation based on the rsync copying command.

As a further improvement of the present invention, the CI/CD agent identifies a disk partition and determines a mapping relationship between the block device and the disk partition according to a preset mount path, where the mapping relationship includes a corresponding relationship defined between the block device and a local disk mapped by a disk, which includes the specified disk partition, in the device to be deployed.

As a further improvement of the present invention, the mirror image template in the disk partition and the file directory corresponding to the mirror image template are stored in the same disk partition of the device to be deployed, or the mirror image template in the disk partition and the file directory corresponding to the mirror image template are stored in two disk partitions of the device to be deployed, and the data contained in the two disk partitions respectively storing the mirror image template and the file directory corresponding to the mirror image template are consistent.

As a further improvement of the present invention, the CI/CD agent determines whether a disk partition specified in the device to be deployed is identified by the local disk; if so, mounting the block equipment to a designated disk partition in the equipment to be deployed through an nbd protocol or a loop protocol; if not, scanning the logical volume of the disk partition through the physical volume of the device to be deployed, and after identifying the corresponding disk partition, mounting the block device to the specified disk partition in the device to be deployed through the nbd protocol or the loop protocol.

As a further improvement of the invention, the method also comprises the following steps: the system comprises at least one physical network card and a PCIE interface which are coupled to a system bus, wherein the physical network card is used for establishing communication connection between equipment to be deployed and the mobile electronic equipment;

the system bus comprises a PCIE protocol-based system bus, and the processor comprises a CPU, a DPU, an FPGA, an ASIC or a GPU.

Based on the same inventive concept, the present application further discloses an application of the removable electronic device as any one of the inventions of the above mentioned invention, wherein the removable electronic device is used for executing installation of a physical machine operating system on a device to be deployed.

Compared with the prior art, the invention has the beneficial effects that:

firstly, as the installation operation of the physical machine operating system is executed without writing an ISO (International organization for standardization) image file into the equipment to be deployed needing to create the physical machine operating system, the physical machine operating system is installed on the equipment to be deployed from a system disk image file loaded on the movable electronic equipment and at least one image template to be synchronized to a specified disk partition in the equipment to be deployed, and the basic installation environment is constructed by only guiding the system disk image file through an IPMI (Intelligent platform management interface) protocol in the installation process of the physical machine operating system, the installation of the physical machine operating system can be executed by synchronizing the movable electronic equipment to the specified disk partition in the equipment to be deployed and taking the disk partition as the image template of the system disk, such as a RAW (RAW architecture) format, wherein the mirror template is compiled and determined through a CI/CD (compact disc) unit, so that the technical problem of difficulty in maintenance caused by non-uniform mirror file formats existing in the installation of the physical machine operating system which need to be repeatedly installed in the continuous deployment scene of the equipment to be deployed in the prior art is solved, and the technical effect of good adaptability and the fast installation speed of the physical machine operating system, and the operation efficiency of the sustainable deployment of the equipment to be deployed in the development and the operation of the equipment to be deployed is improved;

secondly, in the process of executing the installation of the physical machine operating system on the equipment to be deployed, the physical separation between the movable electronic equipment and the equipment to be deployed can be realized, the installation operation of the physical machine operating system can be executed on the equipment to be deployed in batches in a remote mode through a main board plugged in a local computer, or the installation operation of the physical machine operating system can be executed by directly plugging in the main board of the equipment to be deployed and independently setting the equipment to be deployed in a local mode, so that the continuous deployment of the virtual machine and the application in the equipment to be deployed and the equipment to be deployed can be realized; meanwhile, the system disk image file does not need to be actually written into the equipment to be deployed, so that the technical effect of low network bandwidth resource consumption in the application scene of remotely installing numerous equipment to be deployed in batches is achieved, and when the movable electronic equipment is plugged with the main board of the equipment to be deployed, the equipment to be deployed can be directly and continuously integrated and continuously deployed in a local mode;

finally, because the movable electronic device comprises an independent processor and an independent memory, the computing performance of a computer plugged with the movable electronic device can be released in the process of executing continuous integration and continuous deployment on the device to be deployed, so that the efficiency of executing continuous integration and continuous deployment on the device to be deployed is improved.

Drawings

Fig. 1 is an overall topology diagram of a mobile electronic device according to the present invention.

Fig. 2 is a schematic diagram of the mobile electronic device shown in fig. 1, in an embodiment, executing installation of a physical machine operating system by using an image template for a device to be deployed, where the image template and a file directory corresponding to the image template are synchronized to the device to be deployed based on an nbd protocol.

Fig. 3 is a topological diagram of an example scenario in which an ISO file is saved in an application code repository and is imported into a local disk by a CI/CD unit.

Fig. 4 is a flowchart of mapping the mirror image template to a disk partition specified in the device to be deployed by the network block device nbd, where the file directory corresponds to the mirror image template and the mirror image template is synchronized in the local disk.

FIG. 5 is a specific flow chart of installing a physical machine operating system.

FIG. 6 is a detailed flowchart of disk partition scanning.

FIG. 7 is a diagram illustrating a mobile electronic device synchronizing a mirror template and a file directory corresponding to the mirror template with a dd copy command to a device to be deployed.

FIG. 8 is a diagram illustrating synchronization of a mirror template and a file directory corresponding to the mirror template by a rsync copy command from a removable electronic device to a device to be deployed.

Fig. 9 is a topological diagram of an example scenario in which an ISO file is pre-saved in a CI/CD unit and the CI/CD unit imports the ISO file into a local disk.

Fig. 10 is a schematic diagram of synchronizing the mirror image template and the file directory corresponding to the mirror image template to a disk partition specified in the device to be deployed, taking the disk partition as a system disk, and then pulling up the virtual machine, where Linux3 is a physical machine operating system formed by embedding the device to be deployed after the installation operation of the physical machine operating system has been completed.

Fig. 11 is a schematic diagram of the mobile electronic device shown in fig. 1, in another embodiment, the device to be deployed executes installation of an operating system of a physical machine by using an image template, where the image template and a file directory corresponding to the image template are synchronized to the device to be deployed based on a loop protocol.

Detailed Description

The present invention is described in detail with reference to the embodiments shown in the drawings, but it should be understood that these embodiments are not intended to limit the present invention, and that functional, methodological, or structural equivalents thereof, which are equivalent or substituted by those of ordinary skill in the art, are within the scope of the present invention.

Before each embodiment included in the present application is described in detail, the meanings of the terms and the acronyms referred to in the present application are necessarily explained and defined, and the application scenarios of the technical solutions included in the present application are exemplarily described, and do not constitute a specific limitation for the invention included in the present application.

The term "host": a physical computer (or "physical machine") or server, and the host is a generic concept of the removable electronic device 100 or the to-be-deployed device 20, which is a computer or server to which the removable electronic device 100 is plugged.

The term "local disk": logically independent of the device 20 to be deployed and the computer to which the removable electronic device 100 is plugged, and may be understood as a storage device (e.g., a solid state disk) soldered to the removable electronic device 100, and may pre-load or pull one or more system disk image files, e.g., centOS-7-x86_64-DVD-2009. To perform an installation operation of the physical machine operating system by the removable electronic device 100 on the deployed device.

The term "device to be deployed": a computer device or a server or a physical machine logically independent of the removable electronic device 100 can be understood as a computer carrier implemented with persistent integration (CI) and persistent deployment (CD) and deploying virtual machines and various services or applications or computer logic carried by virtual machines in the device to be deployed 20.

English abbreviation "rsync" (remote sync): the rsync is a remote data synchronization tool in a Linux operating system environment, and can rapidly perform a synchronization operation of a file and a file directory included in the file between a plurality of hosts (for example, the removable electronic device 100 and the device to be deployed 20) through a LAN/WAN based on the rsync, and appropriately use an rsync algorithm (differential encoding) to reduce the transmission amount of data.

English abbreviation "dd": commands in the Linux operating system environment that provide full disk replication and can be used for block copies of a specified size.

English abbreviation "IPMI" (Intelligent Platform Management Interface): a managed, open source protocol for a server that specifies a specification for message formats that may vary from transport interface to transport interface. Meanwhile, besides standard commands specified by a protocol, a plurality of OEM commands are reserved, a user can realize the OEM commands according to actual requirements, and the operations of remote control of the server, such as startup and shutdown, restart and the like, can be supported, BIOS settings can be remotely checked and modified, the system starting process can be checked, the server can be remotely connected, the system can be logged in, and the SSH access problem can be solved.

Briefly, as shown in fig. 1 and fig. 2, the core of the present invention is to provide a removable electronic device 100 to perform a physical machine operating system installation operation on one or more devices to be deployed 20 logically independent of the removable electronic device 100, to perform persistent integration and persistent deployment in the devices to be deployed 20, and to execute computer events such as development, testing, release, etc. of software or applications in a physical machine operating system environment built by the devices to be deployed 20. From the physical appearance, the removable electronic device 100 is a card device plugged into a motherboard of a computer. Fig. 2 illustrates an exemplary device 20 to be deployed, but it is reasonably anticipated by those skilled in the art that the removable electronic device disclosed herein can also perform the installation operation of the physical machine operating system on a plurality of devices 20 to be deployed in a batch manner. In particular, the physical machine operating system in the present application refers to a basic operating system running in the device to be deployed 20 to control and manage hardware resources and software resources and applications of the device to be deployed 20. An application may be understood in the present application as a computer executable program run by the device to be deployed 20 for responding to a user request or satisfying a software test, cloud service environment. The removable electronic device 100 disclosed in this embodiment may be plugged into a motherboard logically independent from the deployed device 20, and perform persistent integration and persistent deployment on the deployed device 20 in a local mode (for example, installing a physical machine operating system on the deployed device 20, etc.), or the removable electronic device 100 may be plugged into a motherboard of another computer in a scenario where the persistent integration and persistent deployment are performed remotely over a network and logically independent from the deployed device 20, and the removable electronic device 100 may be plugged into the motherboard of another computer.

Meanwhile, the method and the device for installing the software version of the equipment to be deployed also avoid the problems that the software version management difficulty is high and the installation process time is long when different equipment 20 to be deployed need to depend on the system disk image file (for example, the file type is an ISO file) and the image template (for example, the image template-1 to the image template-n) such as the file type is a RAW file at the same time in the process of installing the physical machine operating system. Since the network block device nbd0 is a very lightweight and very simple-configured remote storage, and the QEMU (virtualization simulator) in the Linux system itself supports the nbd protocol, a specified disk partition (e.g., disk partition disk1s 1) in the device 20 to be deployed can be used as a storage space of a mirror template, so that the nbd protocol or the loop protocol of the QEMU can be directly used to establish a connection, and the installation of the physical machine operating system can be performed on the mirror template that has been synchronized to the specified disk partition. In addition, the ISO file has the same technical meaning as ISO. Meanwhile, the block device in the present application includes a network block device nbd0 as shown in fig. 2 or a loop device loop0 as shown in fig. 11.

Generally, the time for executing a complete installation operation of the physical machine operating system to one device to be deployed 20 in a remote manner is 2 to 3 minutes, and the operation time for directly plugging the movable electronic device 100 on the motherboard of the device to be deployed and directly installing the physical machine operating system to the device to be deployed 20 in a local mode can be further shortened. The operating system environments in which the removable electronic device 100 and the device to be deployed 20 operate are, for example, linux systems. The mobile electronic device 100 runs the Linux system 1, the physical machine operating system to which the device to be deployed 20 is finally installed is the Linux system 3, and one or more virtual machines, that is, VM1 to VMm in fig. 10, can be pulled up in the Linux system 3, and the parameter m is a positive integer greater than or equal to one. Furthermore, it should be understood that the virtual machine in fig. 10 can also be regarded as an application or program synchronized by the removable electronic device 100 in a persistent deployment, the application or program being determined by the mirroring template.

It should be particularly noted that, in the present application, although the system disk image file is also needed during the installation of the physical machine operating system by the device to be deployed 20, the system disk image file (i.e., ISO file) in the removable electronic device 100 is only loaded by the device to be deployed 20 to enter the temporary system based on the rescue mode in the rescue system. Therefore, network resources and computing resources consumed in the process of synchronizing the ISO file 12 with a huge data specification to the device to be deployed 20 are avoided, and the installation operation of the physical machine operating system is executed on the device to be deployed 20 in the rescue mode according to the same mirror image template (note: the number of the mirror image templates can be one or more), so that the ISO file deployed in the movable electronic device 100 is prevented from being transmitted into the device to be deployed 20. The ISO file 12 in the removable electronic device 100 is mapped to the virtual optical drive 22 based on IPMI protocol, and disk1 containing the specified disk partition can be identified by the virtual optical drive 22. Therefore, the present application can reduce the consumption of huge resources caused by executing the installation of the physical machine operating system to the device to be deployed 20 after decompressing the ISO file (e.g., the ISO file 12 in the removable electronic device 100) in the process of the physical machine operating system, and implement the continuous integration and continuous deployment of the device to be deployed 20, and avoid the installation of the physical machine operating system based on both the ISO file (i.e., the lower concept of the system disk image file) and the RAW file (i.e., the lower concept of the virtual machine image template). The resource consumption includes one or a combination of any of the storage resource, the CPU resource, the memory resource of the host, and the network bandwidth resource consumed by the mobile electronic device 100 and the device to be deployed 20 to execute the synchronization data. Meanwhile, the removable electronic device 100 disclosed in the present application comprises a processor 50 alone, so that it is not necessary to occupy the computing resources of the physical machine (note: the computer is logically independent of the device to be deployed 20) to which the removable electronic device 100 is plugged, and it is not necessary to occupy the computing resources of the device to be deployed 20.

The following embodiments are provided as examples of the mobile electronic device and the computer device disclosed in the present application.

Referring to fig. 1 and fig. 2, the present application discloses a removable electronic device 100 for performing continuous deployment on a device to be deployed 20, where the continuous deployment includes, but is not limited to, performing installation of a physical machine operating system and continuous deployment of an application on the device to be deployed 20.

Specifically, the removable electronic device 100 is logically independent of the device to be deployed 20 being subject to continued deployment. The removable electronic device 100 comprises: a system bus 40, a CI/CD unit 30 coupled to the system bus 40, a processor 50, and a memory 60. The CI/CD unit 30 is composed of a local disk 10, a CI/CD agent 16, and an application code repository 17. The CI/CD unit 30 is coupled to the system bus 40 through the communication interface 14.

The CI/CD agent 16 determines at least one mirroring template to be synchronized to the device 20 to be deployed, synchronizing the mirroring template to the specified disk partition in the device 20 to be deployed. The to-be-deployed device 20 restarts the to-be-deployed device 20 after installing the physical machine operating system according to the system disk image file loaded by the CI/CD unit 16 and at least one image template to be synchronized to the disk partition specified in the to-be-deployed device 20. Finally, the boot path of the device to be deployed 20 is set to boot from the disk containing the specified disk partition. The system Bus 40 is preferably a PCIE Bus. The system bus 40 may establish a remote communication connection with the communication interface 24 in the device to be deployed 20 through a physical network card coupled to the system bus 40, or may be directly inserted into a motherboard of the device to be deployed 20 through a PCIE interface 70 coupled to the system bus 40 to perform persistent integration and persistent deployment.

The device 20 to be deployed of the removable electronic device 100 is controlled by the CI/CD agent 16, and may direct, based on the IPMI protocol, the system disk image file of the current disk 10 included in the removable electronic device 100 to be deployed in the system disk partition of the device 20 to be deployed, and the rescue system deployed by the device 20 to be deployed switches the device 20 to the rescue mode, so as to load the system disk image file for installing the physical machine operating system based on the rescue mode. The system disk image file of the current disk 10 may be stored in the local disk 10 in the CI/CD unit 30 in advance, or may be imported and determined from the application code repository 17 under the guidance of the CI/CD agent 16. A rescue system (similar to the PE system in the Windows operating system) is started in the device to be deployed 20. Entering a command line interface of the equipment 20 to be deployed, inputting linux resume after the prompt of boot, and entering a Rescue mode (resume mode) by returning. Selecting 'CD-ROM' in a starting path of the rescue mode, wherein the CD-ROM is a virtual optical drive 22, the virtual optical drive 22 comprises an ISO file 13 loaded from an ISO file 12 in the movable electronic equipment 100 to the virtual optical drive 22, the ISO file 12 and the ISO file 13 are the same system disk image file, the ISO file 12 is objectively not actually written into the equipment 20 to be deployed and is always stored in the movable electronic equipment 100, and the ISO file 12 is only read by the virtual optical drive 22 of the equipment 20 to be deployed. The ISO file 12 may be deployed in advance and only one mapping need be performed after directing the device 20 to be deployed to switch to rescue mode through the CI/CD agent 16 for one or all of the devices 20 to be deployed. The command lines involved in the above operation are as follows:

# /opt/SMCIPIMTool/SMCIPMITool IPADDR USER PASSWORD shell

# vmwa dev2iso/root/CentOS-7-x86_64.iso

thus, the IPMI of the device 20 to be deployed is remotely set up to be started from the ISO file 12 actually saved in the removable electronic device 100 via the virtual optical drive 22 in a system disk image file of CentOS-7-x86_64. ISO.

Meanwhile, in this embodiment, the CI/CD agent 16 is encapsulated with control logic such as block device mount, data synchronization, disk partition, and controlling the mirror image template to be imported into the local disk. At least one image template to be synchronized to a specified disk partition in the device to be deployed 20 is compiled by the CI/CD agent 16 establishing a session with the removable electronic device 100. The removable electronic device 100 configures the API15 to establish a session with the CI/CD agent 16 to transfer the pre-configured script deployed in the application code repository 17 into the local disk 10 of the removable electronic device 100 via one or n mirror templates, i.e., mirror template-1 through mirror template-n, formed by the compilation operation of the CI/CD agent 16. The parameter n is a positive integer greater than or equal to two. The pre-configuration script integrates script files, function files and plug-ins including application test logic, software pressure test, safety test and the like into the mirror image templates-1-n, so that the pre-configuration script is deployed into the equipment to be deployed 20 while the physical machine operating system is installed.

Illustratively, referring to fig. 2 and 3, the CI/CD proxy 16 acts as a pipelined system that establishes a session with a user over the Web network 6, and the user can control the CI/CD proxy 16 through a user graphical interface formed by the embeddings of the Web network 6. At this time, the CI/CD agent 16 pulls at least one image template from the application code repository 17, loads the ISO file 11 that is also originally stored in the application code repository 17 through the CI/CD agent 16, and transfers the ISO file into the local disk 10 to become the ISO file 12, and finally loads the system disk image file to the virtual optical drive 22 deployed by the device to be deployed 20. As a variation of the foregoing embodiment, for example, referring to fig. 9, as a variation of the technical solution disclosed in fig. 3, the ISO file 12 imported into the removable electronic device 100 may also be saved in advance in the local disk 10, and the preconfigured script, the Java applet, the Python program, one or more image templates, and the like, are saved in the application code repository 17 at the same time, and the preconfigured script, the Java applet, the Python program, one or more image templates, and the like, as shown in fig. 9, are continuously loaded to the CI/CD proxy 16 by the logic shown by arrow 171, so as to implement persistent integration (CI). The mirror template is imported into the removable electronic device 100 under the control of the CI/CD agent 16. In this process, the system disk image file (i.e., the ISO file 12) on which the device to be deployed 20 depends is pre-saved on the local disk 10, and the CI/CD proxy 16 pulls at least one image template from the application code repository 17, so as to load the system disk image file to the virtual optical drive 22 deployed by the device to be deployed 20.

The virtual machine created in the device to be deployed 20 is created by at least one image template synchronized by the removable electronic device 100 to the disk partition specified in the device to be deployed 20, and the device to be deployed 20 and the virtual machine deployed in the device to be deployed 20 are created and started based on at least one same image template. The aforementioned start command is issued by the CI/CD agent 16, and the command behavior to which the start command relates:

# ipmitool –I lan -H 10.1.199.212 -U ADMIN -P 123456 chassis bootdevdisk。

referring to fig. 2, exemplarily, the image template is determined by the CI/CD agent 16 through importing, and specifically, image templates-1 to-n are constructed through a pre-configured script deployed in the application code repository 17 hosted by the CI/CD agent 16, and after the image templates are synchronized to a disk partition specified by the device to be deployed 20, the disk partition is used as a system disk of the device to be deployed 20; the applicant uses the image template in raw format as an example in the present application to exemplarily describe, and the image templates in other file formats are executed in the same manner with reference to the technical solution disclosed in this embodiment. The application code repository 17 continuously loads preconfigured scripts, java programs, python programs, etc. as shown in fig. 9 to the CI/CD agent 16 with logic shown by arrow 171 to achieve persistent integration (CI). The pre-configured scripts, java programs, python programs and ISO files 12 are continuously deployed in the to-be-deployed device 20 in the form of one or more image templates with logic shown by an arrow 181, so as to create a physical machine operating system and applications required by the to-be-deployed device 20, so as to implement Continuous Deployment (CD). Illustratively, the pre-configured script may be packaged as a mirror template alone, or as a mirror template with the Java program in its entirety, or as a mirror template with all objects that are not ISO files, with the ISO file (i.e., ISO 11) being packaged separately as a mirror template, and then continuously loaded along the logic shown by arrow 171 to CI/CD proxy 16 to achieve Continuous Integration (CI). Furthermore, the mirror template encapsulating the non-ISO file does not have to be transferred into the removable electronic device 100 to be finally deployed to the device to be deployed 20.

The CI/CD agent 16 determines at least one mirror template to be synchronized to the device to be deployed 20, synchronizing the mirror template to the specified disk partition in the device to be deployed 20. During the system disk data synchronization operation disclosed in the present embodiment, the CI/CD agent 16 remotely logs in the rescue system of the device to be deployed 20 through the SSH service to guide the mobile electronic device 100 and the device to be deployed 20 to perform the following steps 101 to 108.

Step 101, judging whether the network block device nbd is loaded. It should be noted that the scenario of loading the mirror template into the loop device is executed with reference to fig. 11. If yes, skipping to execute the step 102; if not, the step 103 is executed by jumping.

Step 102, mapping the mirror templates, i.e. establishing a mapping relationship between one or more mirror templates and the network block device nbd0 as the local device of the removable electronic device 100, so as to map the mirror templates (e.g. with file names cenos7.9-X86_64. Raw) into the network block device nbd0 logically located in the local disk 10 under the control of the CI/CD agent 16, thereby automatically identifying cenos7.9-X86_64.Raw internal partitions by the network block device nbd0, and correspondingly allocating the internal partitions to the network block device nbd0p1 and the network block device nbd0p2. Since the mirror image template is a prior art, the description thereof is omitted in this embodiment.

And 103, loading the network block device nbd0, and jumping to execute the step 103 after the loading is finished.

And 104, identifying the disk partitions and copying the mirror image template, namely copying the mirror image template to the identified disk partitions. Here, the disk partitions are network block devices nbd0p1 and nbd0p2.

Step 105, mount partition and copy system disk data. The system disk data is a synchronization object pointed by synchronization data established between the network block device nbd0p1 and the disk partition disk1s1 and between the network block device nbd0p2 and the disk partition disk1s2, so that mirror templates such as cenos7.9-X86_64.Raw are actually and respectively written into the disk partition disk1s1 and the disk partition disk1s2. The system disk data is a file containing raw format.

And 106, setting a physical machine to be installed and waiting for the completion of the data synchronization of the system disk. The physical machine to be installed is the device to be deployed 20. In the process of synchronizing data, such as shown in fig. 2 and fig. 7, the disk partition disk1s1 and the disk partition disk1s2 of the device 20 to be deployed are mounted in the removable electronic device 100.

Step 107, the mirror image template is unmapped to recycle the storage resource corresponding to the network block device nbd0 of the mobile electronic device 100 as the local device, so that the mobile electronic device 100 synchronously executes the installation operation of the physical machine operating system on the multiple devices to be deployed 20.

Step 108, uninstalling the network block device nbd0, that is, uninstalling the network block device nbd0 currently hung in the Linux directory included in the mobile electronic device 100 through the umount command, so as to recover the storage resource corresponding to the mobile electronic device 100 in the local disk 10 due to the fact that the network block device nbd0 is hung.

Therefore, in this embodiment, in the process of executing the installation of the physical machine operating system on the device to be deployed 20, the physical separation between the movable electronic device 100 and the device to be deployed 20 can be achieved, and the method is particularly suitable for executing the installation operation of the physical machine operating system on the device to be deployed 20 in batch in a remote manner, so as to achieve continuous deployment of the virtual machine and the application in the device to be deployed 20 and the device to be deployed 20 thereof; meanwhile, because the system disk image file does not need to be actually written into the device to be deployed 20, network bandwidth resources which need to be consumed in an application scenario in which a large number of devices to be deployed are remotely installed in batches are small, and a technical effect that the device to be deployed 20 does not need to decompress the ISO file 12 is achieved, so that the technical problem that computing resources are wasted when a physical machine operating system is installed on the device to be deployed 20 in the prior art is solved.

Then, the device to be deployed 20 restarts the device to be deployed 20 after installing the physical machine operating system according to the system disk image file loaded by the CI/CD unit 30 and the at least one image template to be synchronized to the specified disk partition in the device to be deployed 20. Specifically, the Disk partition in this embodiment is a Disk partition Disk1s1 or a Disk partition Disk1s2 formed in the Disk1, the Disk partition Disk1s1 and the Disk partition Disk1s2 are deployed in the Disk1 and are formed by partitioning the Disk1, and the Disk1 can be regarded as a Physical Disk (Physical Disk) in the device to be deployed 20. In an actual production environment, the device to be deployed 20 is a physical machine, which is also configured with a communication interface 24 establishing communication with the system bus 40, so as to perform a loading operation of loading the system disk image file and a synchronization operation performed on the image template between the removable electronic device 100 and the device to be deployed 20. Meanwhile, disk1 is a physical storage device, and can be selected from mechanical disks (HDD), RAID 0-RAID 10, solid State Disk (SSD), NVMe and other storage devices capable of storing Master Boot Record (MBR).

Illustratively, the communication interface 24 disclosed in the present embodiment includes, but is not limited to, an m.2 interface, a PCI-E interface, a USB interface, an ethernet interface, a fiber interface, an iSCSI interface, or a wireless network interface. Meanwhile, the data synchronization executed between the network block device nbd0 and the disk1 and the loading of the ISO file 12 in the rescue mode can be specifically realized through a data packet forwarding operation in a wired manner or a wireless manner established between the communication interface 24 and the mobile electronic device 100.

Specifically, in the present embodiment, the CI/CD proxy 16 loads the system disk image file relied on by the device to be deployed 20 in the removable electronic device 100, and loads the system disk image file (i.e., ISO file) to the virtual optical drive 22 deployed by the removable electronic device 100. At this time, the ISO file (i.e., ISO 12) in the removable electronic device 100 is not actually written in the virtual optical drive 22 of the device to be deployed 20 and is visible to the removable electronic device 100. Therefore, bandwidth and computing resources consumed by actually writing the ISO file 12 with huge data volume into the equipment 20 to be deployed are avoided, the equipment 20 to be deployed can quickly enter a basic installation environment in a rescue mode, and installation operation of a physical machine operating system is executed through the mirror templates-1-n synchronized to the equipment 20 to be deployed.

Meanwhile, the rescue system is guided to read the system disk image file which is always stored in the movable electronic equipment 100 based on the IPMI protocol, the equipment 20 to be deployed is set to be started from the system disk image file which is located in the movable electronic equipment 100, and a physical machine operating system is installed in the equipment 20 to be deployed according to the system disk image file; the system disk image file is independent of the image template, does not depend on the latest code and is adapted to the commodity attributes of the equipment 20 to be deployed, and the commodity data is defined by the manufacturer, model and version of the equipment 20 to be deployed individually or together.

Therefore, in the present application, the system disk image files required for building the basic installation environment based on the rescue mode may use various versions, such as CentOS-7-x86_64-LiveGNOME-2003.Iso or CentOS-7-x86_64-DVD-2009.Iso, and the image templates may be adaptively compiled by the CI/CD agent 16 according to the to-be-deployed devices 20 with different commodity data, thereby improving the adaptability and flexibility of performing the installation operation of the physical machine operating system on the to-be-deployed devices 20 with different models (e.g., DELL R730 and DELL R740) and different hardware versions (e.g., INTEL Xeon 4201-containing server and INTEL Xeon 3204-containing server) provided by different manufacturers (e.g., DELL and Langchao).

Referring to fig. 5, this embodiment further illustrates a specific flow of installing the operating system of the physical machine to the device to be deployed 20, specifically referring to steps 201 to 210.

And step 201, mounting the system disk image file. Specifically, the ISO file 12 of the removable electronic device 100 is mapped to the device to be deployed 20 by the virtual optical drive 22 to form the ISO file 13 to actually mount the ISO file 12, so that the device to be deployed 20 is remotely started from the ISO file 12 of the removable electronic device 100 based on the IPMI protocol. The ISO file 12 in the removable electronic device 100 is set to read-only mode.

Step 202, the device to be deployed 20 is set to start from the virtual optical drive 22.

The IPMI is implemented by remotely accessing the device to be deployed 20, inputting a command line form by a Web controller deployed in the IPMI system or directly in the removable electronic device 100, and performing a modification computer (i.e., the device to be deployed 20) in a visual interface, and setting the device to be deployed 20 to be booted from a system disk. The CI/CD agent 16 controls the visual operation interface displayed by the IPMI of the device to be deployed 20, and sets the device to be deployed 20 to perform remote boot from the ISO file 12 actually saved in the removable electronic device 100, wherein the command lines are as follows:

# ipmitool -I lan -H 10.1.199.212 -U ADMIN -P 123456 chassis bootdevcdrom；

10.1.199.212 is the IPMI address of the device to be deployed 20 where the operating system of the physical machine is to be installed, ADMIN is the IPMI user name, 123456 is the password of IPMI, and cdrom means starting from the virtual optical drive 22. Thus, at least one mirror template to be synchronized to the device to be deployed, namely mirror template-1-mirror template-n in FIG. 2, is determined by the removable electronic device 100, which is logically independent of the device to be deployed 20. The IPMI system disclosed in this embodiment refers to a set of computer interface specifications for out-of-band management. Out-of-band refers to accessing a computer system without being in the same logical space as the physical devices of the system. The IPMI system supports remote monitoring without the permission of the computer operating system. The IPMI system runs on separate hardware connected to the motherboard or server of the host. This separate hardware is the Baseboard Management Controller (BMC). The BMC manages the interface between the platform hardware and the system management software.

Step 203, powering on the device to be deployed 20. This step 203 is controlled by the CI/CD agent 16 and involves the following command lines:

# ipmitool -I lan -H 10.1.199.212 -U ADMIN -P 123456 chassis power on。

step 204, configuring the network of the device to be deployed, and also controlled by the CI/CD agent 16, and specifically entering the rescue system through the remote Console management entry of IPMI, and setting the network address of the device to be deployed 20, for example, setting the IP address of the device to be deployed 20 to 192.168.8.10/24, and setting the gateway of the device to be deployed 20 to gw192.168.8.1/24.

Step 205, identifying one or more disk partitions formed by the division of the removable electronic device 100 to identify a/dev/nbd device or a/dev/loop 0 device. Preferably, step 204 may be followed by identifying a file size of the image template to be mounted to select a logical disk partition in the removable electronic device 100.

And step 206, partitioning the disk partitions, and specifically, performing disk partitioning on disk1 in the device to be deployed 20. Referring to fig. 2, disk1 may be divided into two disk partitions, and the size of each disk partition is ensured to be consistent with the size of a disk partition formed by mapping centos7.9-X86_64 raw through a network block device nbd0, so that nbd0p1 is consistent with disk0s1, and nbd0p2 is consistent with disk0s 2. The disk partitions formed by disk1 partitioning can be determined according to the number of mirror image templates which need to be continuously deployed, but no strict one-to-one correspondence exists.

Step 207, mounting the network block device nbd to the specified disk partition, thereby mounting nbd0p1 and nbd0p2 to the removable electronic device 100 and mounting disk0s1 and disk0s2 in the device to be deployed 20 to the device to be deployed 20 under the control of the CI/CD agent 16. The loop device loop0p1 and loop device loop0p2 in fig. 11 are implemented in reference.

And step 208, synchronizing the disk partition specified by the system disk data, namely synchronously copying the data of the mirror image template with the nbd0p1 mounted to the disk0s1 through the rsync protocol, and synchronously copying the data of the mirror image template with the nbd0p2 mounted to the disk0s2 through the rsync protocol, so that the disk1 of the device 20 to be deployed is contained in the basic installation environment configured in the rescue mode, and the physical machine operating system can be installed on the device 20 to be deployed.

Step 209, the boot path of the device to be deployed 20 is set to be booted from the disk of the device to be deployed 20, and specifically, booted from the disk1 of the device to be deployed 20 as the disk of the system disk.

Step 210, restarting the device to be deployed 20, and the restart operation instruction may be initiated by a user or an administrator from a command line interface of the movable electronic device 100 to restart the device to be deployed 20, or the user directly restarts the device to be deployed 20 in a physical manner, or directly clicks a "restart" control with a cursor in an operating system interface formed by embedding the device to be deployed 20 in which the physical machine operating system installation has been completed, so as to complete the restart operation of the device to be deployed 20. At this point, the installation and continuous deployment of the operating system of the physical machine to be executed by the device 20 to be deployed are completed.

Referring to fig. 3, in this implementation, the mobile electronic device 100 synchronizes one or more mirror templates of the mirror templates-1 to-mirror templates-n to at least one disk partition associated with the device to be deployed 20, synchronizes the mirror templates to the disk partition, starts a virtual machine from the disk partition serving as a system disk, and mounts the disk partition to the virtual machines VM1 to VMm created in the device to be deployed 20; wherein the disk partition is logically located on the device to be deployed 20 and visible to the removable electronic device 100. The disk partition as the system disk refers to the disk partition disk1s1 or the disk partition disk1s2, and if the disk partition disk1s1 is taken as the system disk, the disk partition disk1s2 is taken as one or more disk partitions for deploying applications of software stress test and security test, and the applications are determined by one or more mirror image templates synchronized from the removable electronic device 100 to the device 20 to be deployed. The virtual machines VM1 and VM2 \8230 \8230andVMm are deployed in disk1. A plurality of virtual machines are created and started in the device to be deployed 20, namely VM1, VM2, 8230, VMm and parameter m in FIG. 3 are positive integers. The virtual machine can be pulled up after the operating system of the device 20 to be deployed is created, and the service logic to be deployed is borne through the virtual machines VM 1-VMm so as to respond to the user. Meanwhile, since the image template synchronized to the device to be deployed 20 may further include the preconfigured script, one or more virtual machines including the preconfigured script, the Java program, or the Python program may be directly deployed and pulled up while the operating system of the physical machine is installed, so as to directly start to execute the software stress test and the security test, thereby meeting the application requirements of persistent integration (CI) and persistent deployment (CD) executed by the device to be deployed 20.

The removable electronic device 100 loads the mirror template to at least one piece of device deployed in the removable electronic device 100, where the piece of device includes a network block device nbd or a loop device (e.g., the network block device nbd0 in the removable electronic device 100 shown in fig. 2 or the loop device loop0 in the removable electronic device 100 shown in fig. 11), creates disk partitions (e.g., disk partitions disk1s1 and disk partitions disk1s2 in the device 20 to be deployed) that are the same as the number and disk space of the network block devices in the device 20 to be deployed, and the network block devices are controlled by the CI/CD agent 16 based on a data synchronization protocol to map the network block devices to the disk partitions in the device 20 to be deployed, and start up the boot path settings of the device 20 to be deployed from the disk partitions on which the network block devices are mounted and the mirror template synchronization job has been completed. After creating the disk partitions with the same number of network block devices and the same disk space in the device to be deployed 20, the method further includes: identifying the disk partitions and determining mapping relationships between the network block devices and the disk partitions according to the preset mounting path, where the mapping relationships include correspondence defined between the network block devices and the local disks 10 in the removable electronic device 100, which are mapped by the disks of the to-be-deployed device 20 that include the specified disk partitions. Such a correspondence relationship requires that, after synchronizing the mirror template to the designated partition in the device to be deployed 20, the mapping relationship between the network block device nbd0 and the disk partition is cancelled, and the network block device nbd0 is unloaded. To this end, the process shown in fig. 2 of mapping the mirror template to the removable electronic device 100 through the network block device nbd0 to synchronize the mirror template and the file directory corresponding to the mirror template to the specified disk partition in the device to be deployed 20 is ended.

For example, after the mirror template and the file directory corresponding to the mirror template mount the network block device to the network block device nbd0 of the local disk 10 through the nbd protocol (see fig. 2) or the loop protocol (see fig. 11), a device of "/dev/nbd0" or a device of "/dev/loop0" may be displayed in the background of the removable electronic device 100.

Referring to fig. 2, in a scenario where the nbd protocol is used to perform system disk data synchronization, a storage medium in the removable electronic device 100 that stores an image file is a network block device nbd0, and the network block device nbd0 may include a network block device nbd0p1 and a network block device nbd0p2. Referring to fig. 11, in a scenario of performing data synchronization by using a loop protocol, a storage medium of the movable electronic device 100 for storing an image file is a loop device loop0, and the loop0 may include a loop device loop0p1 and a loop device loop0p2. Both the loop device loop0 and the network block device nbd0 can be regarded as a block device for storing the mirror template.

Specifically, the network block device nbd may use the disk space of one remote host (e.g., the device 20 to be deployed) as one network block device nbd. The network block device nbd is similar to a physical disk to facilitate adding hard disk space of another server (e.g., the device 20 to be deployed) to the local device (i.e., the removable electronic device 100). The client may format this network block device nbd0 into various types of partitions (i.e., nbd0p1 and nbd0p 2) to facilitate the usage requirements of the device 20 to be deployed for the user of the device 20 to be deployed. In the scenario of data synchronization performed in the nbd protocol, a block device driver of the network block device nbd0 needs to be scanned. Referring to fig. 2 or fig. 11, the mirror template is mounted to a disk of the device 20 to be deployed through the nbd protocol or the loop protocol. In the synchronous data scene based on the nbd protocol, nbd0p1 and nbd0p2 in the mobile electronic device 100 are network block devices nbd0; meanwhile, in a scenario of synchronizing data based on a loop protocol, loop0p1 and loop0p2 in the mobile electronic device 100 are loop devices and may also be regarded as a block device. A loop device is a pseudo device that uses files to emulate a block device, which, when emulated, acts like a magnetic or optical disk. Before use, a loop device must be connected to a file. This combination provides the user with an interface to replace the block specific file. Thus, if the file contains a complete file system, the file can be mounted as if it were a disk. The mount-up mirror file in the loop device (loop) itself also contains a file system, and the loop device mounts up the mount-up mirror file just like a file system which is wound by one turn on the file system. Thus, in the present application, the data synchronization operation performed between the removable electronic device 100 and the device to be deployed 20 refers to a synchronization operation performed on the image template, while the system disk image file (i.e., ISO file) is not actually written to the device to be deployed 20.

After the network block device nbd0 or the loop device loop0 is mounted to the device to be deployed 20, one or more/dev/nbd devices or/dev/loop 0 devices are displayed in an installation interface of the device to be deployed 20. The aforementioned/dev/nbd devices or/dev/loop 0 devices may be recognized by the removable electronic device 100. Meanwhile, in the present application, the disk partition needs to be identified to meet the requirement of mounting the mirror image template in the subsequent device 20 to be deployed. Referring to fig. 6, the specific flow of the disk partition scanning is specifically as shown in the following steps 301 to 307.

And 301, loading the mirror image template on the nbd device or the loop device. Loading a mirror template can only be an option for the removable electronic device 100 to select either an nbd device or a loop device.

Step 302, identify a disk partition. Nbd0p1 and nbd0p2 included in the network block device nbd0 in fig. 2 may be regarded as two disk partitions in the nbd0 device, and loop0p1 and loop0p2 included in the loop device loop0 in fig. 11 may be regarded as two disk partitions (i.e., block devices) in the loop0 device. Identifying a disk partition may determine whether a file format of an image template being mounted can be identified. Step 303, judging whether the disk partition can be identified, if so, skipping to execute step 304, and ending after step 304 is executed; if not, the step 305 is executed.

Step 305, scan the logical volume (lvm) of the disk partition, which refers to the command behavior # pvsan.

Step 306, judging whether the mounted disk partition is successful, if so, skipping to execute step 307; if not, ending.

And 307, mounting the mirror image template to the logical volume of the disk partition, and ending.

For example, the disk Partition disk1s1 and the disk Partition disk1s2 may be deployed in one disk of the device 20 to be deployed, may also be deployed in two independent disks, and even may be separately deployed in two physical partitions (partitions) of one disk of the device 20 to be deployed. Meanwhile, in the process of mapping the network block device nbd0 to the disk partition in the device 20 to be deployed, the network block device nbd0 automatically identifies the internal partitions (i.e., nbd0p1 and nbd0p 2) of the mirror template (e.g., centros 7.9-X86_64. Raw) for installing the physical machine operating system, and presents device information listing all available network block devices in the removable electronic device 100, i.e., the network block device nbd0p1 and the network block device nbd0p2, to the user by entering an lsblk command in the command line interface of the removable electronic device 100 in the removable electronic device 100. Then, a mirror template is mounted to the network block devices nbd0p1 and nbd0p2 together, and the related command behaviors are as follows:

# qemu-nbd --connect=/dev/nbd0 CentOS7.9-X86_64.RAW。

creating at least one disk partition of a network block device formed by mapping the device to be deployed 20 to the removable electronic device 100 in the removable electronic device 100, wherein the network block device and a disk partition designated in the device to be deployed 20 establish a mapping relationship based on a data synchronization protocol, so as to establish a data synchronization path between the network block device and the disk partition, and disconnecting the mapping relationship and uninstalling the network block device located in the removable electronic device 100 after the data synchronization is completed; the data synchronization protocol comprises an rsync protocol or an iSCSI protocol. The mapping relationship refers to, for example, correspondence relationships formed between the network block device nbd0p1 and the disk partition disk1s1, and between the network block device nbd0p2 and the disk partition disk1s2, and a data synchronization path formed for the mirror template between the removable electronic device 100 and the device to be deployed 20 may be determined based on the correspondence relationships, so that a data synchronization path is established between the network block device nbd0p1 on which the mirror template-1 has been mounted and the disk partition disk1s1, or between the network block device nbd0p2 on which the mirror template-n is mounted and the disk partition disk1s2, so as to synchronize one or more mirror templates into one or more specified disk partitions in the device to be deployed 20. In the rescue mode, when the device 20 to be deployed recognizes that the mirror template has been copied to the designated disk partition by the mirror template synchronized to the network block device.

With reference to fig. 2 and 7, applicants proceed to illustrate an installation process for executing a physical machine operating system on a mirrored template that has been synchronized to the device 20 to be deployed. Generating a copy instruction by the CI/CD agent 16 to synchronize the mirror image template and the file directory corresponding to the mirror image template to the specified disk partition in the device to be deployed 20 based on the mapping relationship based on the copy instruction; and synchronizing the mirror image template and the file directory in the removable electronic device 100 to the disk partition designated in the device to be deployed 20 through the data synchronization protocol based on the disk partition determined by the mapping relation. Then, mapping the disk containing the specified disk partition or the specified disk partition to the CI/CD agent 16 based on the mapping relation corresponding to the data synchronization protocol, determining a copy command selection policy by the CI/CD agent 16 according to the data specification of the mirror image template, so as to synchronize the mirror image template and the file directory corresponding to the mirror image template to the specified disk partition in the device to be deployed 20 based on the dd copy command or the rsync copy command alternatively; the data specification is defined by the size of the file contained in the mirror image template and the proportion of the small file. The replication command selection policy is determined by the CI/CD agent 16 and stored in the CI/CD agent 16, and the replication command selection policy can be configured by the user at the CI/CD agent 16, thereby improving the flexibility and rationality of data synchronization to avoid occupying excessive network bandwidth resources during continuous deployment.

After the mirror image template is synchronized to the disk partition specified in the device to be deployed 20, a plurality of virtual machines running in the device to be deployed 20 are created according to the mirror image template (refer to one or more virtual machines VM1 to VMm pulled up in the Linux system 3 in the device to be deployed 20 in fig. 10), and the device to be deployed 20 and the virtual machines deployed in the device to be deployed 20 are created and started based on at least one same mirror image template.

Specifically, in the present embodiment, the disk partition disk1s1 is mapped to disk _ a of the removable electronic device 100 or the disk partition disk1s2 is simultaneously mapped to disk _ b of the removable electronic device 100 based on the iSCSI protocol, and then the mirroring template that has been mounted to disk _ a or disk _ b is synchronously copied to the disk partition by the copy command selection policy. It should be noted that, a mapping relationship is established between the disk1 and the removable electronic device 100 based on the iSCSI protocol, where the removable electronic device 100 includes an iSCSI server (not shown), and the device to be deployed 20 includes an iSCSI client (not shown). Disk _ a and disk _ b in fig. 7 are not disks or storage spaces that actually exist, but disk maps formed by mapping relationships among information such as port numbers, iSCSI client IP addresses, and the like of disk partitions (i.e., disk partition 1s1 and disk partition 1s 2) specified in the device 20 to be deployed based on the iSCSI protocol in the removable electronic device 100. The efficiency and speed of synchronizing data between the mobile electronic device 100 and the device 20 to be deployed are very fast, and the data synchronization at the GB level can be achieved typically in the order of seconds. Meanwhile, the removable electronic device 100 can also be remotely mounted to the CI/CD agent 16 through the iSCSI protocol, so that data corresponding to a mirror template included in the network block device nbd0 or the loop device loop0 can be directly copied to the disk1 without considering a disk partition condition formed in the disk1, but as long as the storage space of the disk1 is greater than that of the network block device nbd0 or the loop device loop0, the removable electronic device disclosed in this embodiment is more convenient. Exemplarily, when the removable electronic device 100 includes an nbd0 device and synchronizes the mirror template and the file directory corresponding to the mirror template to the command line related to the disk partition specified in the device 20 to be deployed through the mapping relationship by using a dd copy command, the command line is as follows:

# dd if=/dev/nbd0 of=/dev/disk1。

the data synchronization formed based on the dd copy command is suitable for a scene with more small files and supports single-thread copy.

When the movable electronic device 100 includes a loop device loop0 and a dd copy command is used to synchronize the mirror image template and the file directory corresponding to the mirror image template to the command line related to the disk partition specified in the device to be deployed 20 through the mapping relationship, as follows:

# dd if=/dev/loop0 of=/dev/disk1。

meanwhile, in the embodiment, in order to solve the technical problems of low efficiency and long time consumption in the synchronous mirror template copying process due to excessive small files in the continuous deployment process, the embodiment preferably needs to judge the size of the file formed in the mirror template and the data specification defined by the small files so as to select a proper copying command. The copy command selection policy includes:

if the percentage of the small files is greater than or equal to 50%, the files are smaller than or equal to 64KB and smaller than or equal to 64KB, and the file directories corresponding to the mirror image template and the mirror image template are synchronized to the disk partition specified in the device to be deployed 20 through the mapping relationship based on the dd copy command. The mapping is preferably an iSCSI mapping. Fig. 7 shows a detailed process of synchronizing the mirror image template and the file directory corresponding to the mirror image template to the designated disk partition in the device 20 to be deployed based on the dd copy command, and the dd copy command is suitable for a synchronization scenario in which a small file included in an object to be synchronized is less, and is particularly suitable for large-block files and whole disk copy. The disk partitions disk1s1 and disk partitions disk1s2 are mounted in the removable electronic device 100 under the guidance of the CI/CD proxy 16 to form disk _ a and disk _ b, then the network block devices nbd0p1 and nbd0p2 are respectively saved and mirror templates (e.g., mirror template-1 and mirror template-n) that have been mounted to the corresponding network block devices are synchronously copied to disk _ a and disk _ b, respectively, by dd copy commands, and then a synchronization data operation is performed based on the iSCSI protocol based on the mapping relationship formed between disk _ a and disk partitions disk1s1 and the mapping relationship formed between disk _ b and disk1s2 to synchronize one or more mirror templates to the disk partition specified in the device to be deployed 20.

If the small file occupation ratio of the file is less than 50% and is greater than 64KB or less than or equal to 64KB, the mirror image template and the file directory corresponding to the mirror image template are synchronized to the disk partition specified in the device to be deployed 20 through the mapping relationship based on the rsync copy command. A detailed process of synchronizing the mirror image template and the file directory corresponding to the mirror image template to the designated disk partition in the device to be deployed 20 based on the rsync copy command is shown in fig. 8, and the rsync copy command is applicable to a synchronization scene with more large files included in an object to be synchronized (i.e., the mirror image template and the file directory corresponding to the mirror image template). Meanwhile, as shown in fig. 8, a sync data operation is performed between the removable electronic device 100 and the device to be deployed 20 based on the rsync protocol when the rsync copy command is employed. The data-1 to data-4 are temporary directories and are created by the CI/CD agent 16. The nbd0 comprises nbd0p1 and nbd0p1, the disk1 comprises disk partitions disk1s1 and disk partitions disk1s2, and directory paths from nbd0p1 mount (mount) to/data-1. The directory path from nbd0p2 mount (mount) to/data-2, the directory path from disk partition disk1s1 mount (mount) to/data-3, and the directory path from disk partition disk1s2 mount (mount) to/data-4. Two independent synchronization data paths are thus established between the directory path of/data-1 and the directory path of/data-3, and between the directory path of/data-2 and the directory path of/data-4, respectively, to synchronize data based on the rsync copy command. The data synchronization formed based on the rsync copy command is suitable for a scene with more large files, and multi-thread high-concurrency copy is supported. The rsync copy command can realize simultaneous multi-thread copy and arbitrary configuration of thread number through the shell script.

Since the disk partition disk1s1 and the disk partition disk1s2 can be set to have different storage spaces or the same storage space, and preferably the same storage space; and the storage space of the disk partition disk1s1 is greater than or equal to the storage space of nbd0p1 or loop0p1, and the storage space of the disk partition disk1s2 is greater than or equal to the storage space of nbd0p2 or loop0p2. Meanwhile, the number of the disk partitions that receive the mirror image template and are located in the device to be deployed 20 and the capacity of each disk partition may also be flexibly determined according to the size of the data formed by the mirror image template.

Preferably, in this embodiment, the mirror image template in the disk partition and the file directory corresponding to the mirror image template are stored in the same disk partition of the device 20 to be deployed, or the mirror image template in the disk partition and the file directory corresponding to the mirror image template are stored in two disk partitions of the device 20 to be deployed, and the data in the two disk partitions that respectively store the mirror image template and the file directory corresponding to the mirror image template are the same.

Referring to fig. 6, in the removable electronic device, it is determined whether the disk partition specified in the device to be deployed 20 is identified by the removable electronic device 100; if yes, mounting the network block device to a designated disk partition in the device to be deployed 20 through an nbd protocol or a loop protocol; if not, scanning a logical volume (lvm) of the disk partition through a Physical Volume (PV) of the device to be deployed 20, and after identifying the corresponding disk partition, respectively mounting the network block devices nbd0p1 and nbd0p2 to disk partitions disk1s1 and disk1s2 specified in the device to be deployed 20 through an nbd protocol or a loop protocol.

Then, the boot path of the device to be deployed 20 is set to boot from the disk containing the specified disk partition. Meanwhile, the start path of the device 20 to be deployed is set by the CI/CD agent 16 based on the IPMI protocol, so that the device 20 to be deployed is partitioned from a disk of the synchronized mirror template, the physical machine operating system required by the device 20 to be deployed is installed, and the physical machine operating system is used as a system disk after the installation of the physical machine operating system is completed, and the device 20 to be deployed is guided to enter the operating system. The device to be deployed 20 is set to initiate the command behavior involved from the system disk:

# ipmitool -I lan -H 10.1.199.212 -U ADMIN -P 123456 chassis bootdevdisk。

finally, the CI/CD agent 16 inputs a restart instruction through the Web controller or directly in the command line interface of the device to be deployed 20 based on the IPMI protocol to restart the device to be deployed 20, thereby finally completing the installation operation of the operating system of the physical machine executed by the device to be deployed 20. Compared with the prior art in which the ISO file is directly written into the device to be deployed 20 and the operating system of the physical machine is installed, the technical solution disclosed in the present application is based on one or more image templates, such as raw format, controlled by the CI/CD agent 16 and synchronized to the device to be deployed 20 to perform the installation operation of the operating system of the physical machine, and has the technical advantage that the installation speed of the operating system of the physical machine is very fast.

Further, the present application discloses an application of the removable electronic device 100, wherein the removable electronic device 100 is used for executing installation of a physical machine operating system on the device to be deployed 20. A user, upon an access request or operation initiated in a client (e.g., a computer logically separate from the removable electronic device 100 and the device to be deployed 20), performs a quick installation and deployment of the physical machine operating system and its various applications to the device to be deployed 20, which is logically in a separate structure from the removable electronic device 100.

The above-listed detailed description is only a specific description of a possible embodiment of the present invention, and they are not intended to limit the scope of the present invention, and equivalent embodiments or modifications made without departing from the technical spirit of the present invention should be included in the scope of the present invention.

Furthermore, it should be understood that although the present description refers to embodiments, not every embodiment may contain only a single embodiment, and such description is for clarity only, and those skilled in the art should integrate the description, and the embodiments may be combined as appropriate to form other embodiments understood by those skilled in the art.

Claims

1. A removable electronic device logically independent of a device to be deployed for which continuous deployment is performed,

it is characterized by comprising: the system bus is coupled to the CI/CD unit, the processor and the memory of the system bus; the CI/CD unit consists of a local disk, a CI/CD agent and an application code warehouse;

the CI/CD agent determines at least one mirror image template to be synchronized to the equipment to be deployed, and synchronizes the mirror image template to a specified disk partition in the equipment to be deployed; the equipment to be deployed is restarted after a physical machine operating system is installed according to the system disk image file loaded by the CI/CD unit and at least one image template which is to be synchronized to the specified disk partition in the equipment to be deployed; and setting the starting path of the equipment to be deployed to be started from the disk comprising the specified disk partition.

2. The removable electronic device according to claim 1, wherein the device to be deployed is controlled by a CI/CD agent, and the system disk image file in the local disk is guided based on the IPMI protocol to switch the device to be deployed to the rescue mode by the rescue system deployed by the device to be deployed in the system disk partition of the device to be deployed, so as to load the system disk image file for installing the physical machine operating system based on the rescue mode.

3. The removable electronic device of claim 2, wherein at least one mirror template to be synchronized to a specified disk partition in the device to be deployed is determined by being pre-saved to the local disk or by being imported under control of a CI/CD agent by an application code repository that establishes a session with the local disk;

4. The removable electronic device according to claim 3, wherein the application code repository is hosted by a CI/CD agent, and the mirror template is constructed by a pre-configured script deployed in the application code repository, and after the mirror template is synchronized to a disk partition specified by the device to be deployed, the specified disk partition is taken as a system disk of the device to be deployed; the file format of the mirror image template comprises raw, qcow2, vmdk or ova.

5. The removable electronic device according to claim 3, wherein a system disk image file on which the device to be deployed depends is pre-saved in the local disk, and the CI/CD agent pulls at least one image template from an application code repository to load the system disk image file to the virtual optical drive deployed by the device to be deployed;

6. The removable electronic device of claim 3, wherein the CI/CD agent pulls at least one image template from an application code repository, loads a system disk image file relied on by the device to be deployed through the CI/CD agent, and loads the system disk image file to the virtual drive deployed by the device to be deployed;

7. The removable electronic device according to claim 5 or 6, wherein the mirror template is synchronized to at least one disk partition associated with the device to be deployed, the mirror template is synchronized to the disk partition, a virtual machine is started by the disk partition serving as a system disk, and the disk partition is mounted to the created virtual machine in the device to be deployed; wherein the disk partition is logically located on the device to be deployed and visible to the CI/CD unit.

8. The removable electronic device according to claim 5 or 6, wherein the CI/CD agent loads a mirror template to at least one device deployed in a local disk, creates a disk partition in the device to be deployed, the number and disk space of which are the same as those of the device to be deployed, the device to be deployed is based on a data synchronization protocol and controlled by the CI/CD agent to map the device to the disk partition in the device to be deployed, and starts the boot path setting of the device to be deployed from the disk partition on which the device to be deployed is mounted and has completed a mirror template synchronization job.

9. The removable electronic device according to claim 8, wherein the local disk creates at least one disk partition of a block device formed by mapping a device to be deployed to the local disk, the block device and a specified disk partition of the device to be deployed establish a mapping relationship based on a data synchronization protocol, so as to establish a data synchronization path between the block device and the disk partition, and disconnect the mapping relationship and uninstall the block device located in the local disk after data synchronization is completed;

10. The removable electronic device according to claim 9, wherein the CI/CD agent generates a copy instruction to synchronize the mirror template and the file directory corresponding to the mirror template to the disk partition specified in the device to be deployed based on the mapping relationship based on a copy command; synchronizing a mirror image template and a file directory in a local disk to a specified disk partition in equipment to be deployed through the data synchronization protocol based on the disk partition determined by the mapping relation;

11. The removable electronic device according to claim 10, wherein the disk containing the specified disk partition or the specified disk partition is mapped to a block device of a local disk based on a mapping relationship corresponding to the data synchronization protocol, and a copy command selection policy is determined by the CI/CD agent acquiring a data specification of a mirror image template to synchronize the mirror image template and a file directory corresponding to the mirror image template to a specified disk partition in a device to be deployed based on a dd copy command or an rsync copy command alternatively; the data specification is defined by the size of the file contained in the mirror image template and the proportion of the small file.

12. The removable electronic device of claim 11, wherein the copy command selection policy comprises:

13. The removable electronic device of claim 9, wherein the CI/CD agent identifies disk partitions and determines mapping relationships between block devices and disk partitions according to preset mount paths, the mapping relationships including correspondence relationships defined between block devices and local disks mapped to the local disks by disks of the devices to be deployed that include the specified disk partitions.

14. The removable electronic device according to claim 11, wherein the mirror image template in the disk partition and the file directory corresponding to the mirror image template are stored in a same disk partition of the device to be deployed, or the mirror image template in the disk partition and the file directory corresponding to the mirror image template are stored in two disk partitions of the device to be deployed, and data in the two disk partitions that store the mirror image template and the file directory corresponding to the mirror image template respectively are consistent.

15. The removable electronic device of claim 8, wherein the CI/CD agent determines whether a disk partition specified in the device to be deployed is identified by the local disk; if so, mounting the block equipment to a designated disk partition in the equipment to be deployed through an nbd protocol or a loop protocol; if not, scanning the logical volume of the disk partition through the physical volume of the device to be deployed, and after identifying the corresponding disk partition, mounting the block device to the specified disk partition in the device to be deployed through the nbd protocol or the loop protocol.

16. The removable electronic device of any of claims 1-6, further comprising: the system comprises at least one physical network card and a PCIE interface which are coupled to a system bus, wherein the physical network card is used for establishing communication connection between equipment to be deployed and the mobile electronic equipment;

the system bus comprises a system bus based on a PCIE protocol, and the processor comprises a CPU, a DPU, an FPGA, an ASIC or a GPU.

17. Use of a removable electronic device according to any of claims 1 to 16, for performing a physical machine operating system installation on a device to be deployed according to any of claims 1 to 16.