WO2024179294A1 - Component deployment method and apparatus, electronic device, and storage medium - Google Patents

Abstract

The present application provides a component deployment method and apparatus, an electronic device, and a storage medium. The method comprises: obtaining a component deployment instruction, and determining a target component that the component deployment instruction indicates for deployment; executing, by means of the target component, a target deployment operation represented by the component deployment instruction, wherein the target deployment operation does not comprise creation and overwriting operations on an initial random access memory (RAM) disk; obtaining preset global information from a system where the target component is located, wherein the preset global information is used for indicating a creation body for the initial RAM disk; and when the creation body is not the target component, prohibiting the target component from creating and overwriting the initial RAM disk.

Description

Component deployment method, device, electronic device and storage medium

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to Patent Application No. 202310209280.6 filed with the China Patent Office on February 27, 2023, the entire contents of which are incorporated herein by reference.

Technical Field

The present application relates to but is not limited to the field of computer technology.

Background Art

In some operating systems, the initial RAM (random access memory) disk is an important component and an important part of the operating system boot process. In these operating systems, the initial RAM disk is a global shared file. The creation of this file is obviously time-consuming, and the creation of this file can be independently created and overwritten multiple times by individual components, programs, or people, so that only the last result is applied.

However, the number of component packages in current operating systems is in the thousands or tens of thousands. When deploying (installing, upgrading, uninstalling) multiple component packages, it will double the time consumption, which is not conducive to the rapid new installation of the operating system and large-scale component deployment. Component deployment in multiple component deployment scenarios takes a long time.

Summary of the invention

Embodiments of the present application provide a component deployment method, device, electronic device, and storage medium.

In a first aspect, an embodiment of the present application provides a component deployment method, the method comprising: obtaining a component deployment instruction, and determining a target component to be deployed indicated by the component deployment instruction; executing a target deployment operation indicated by the component deployment instruction through the target component, wherein the target deployment operation does not include the creation and overwriting operation of an initial random access memory RAM disk; obtaining preset global information from a system where the target component is located, The preset global information is used to indicate the creation subject of the initial RAM disk; when the creation subject is not the target component, the target component is prohibited from creating and overwriting the initial RAM disk.

In a second aspect, an embodiment of the present application provides a component deployment device, comprising: a first acquisition unit, configured to acquire a component deployment instruction, and determine a target component that the component deployment instruction indicates to be deployed; a first execution unit, configured to execute a target deployment operation represented by the component deployment instruction through the target component, wherein the target deployment operation does not include the creation and overwriting operations of an initial random access memory RAM disk; a second acquisition unit, configured to acquire preset global information from a system where the target component is located, wherein the preset global information is used to indicate a creation subject of the initial RAM disk; a control unit, configured to prohibit the target component from creating and overwriting the initial RAM disk when the creation subject is not the target component.

In a third aspect, an embodiment of the present application provides an electronic device, comprising: a memory configured to store a computer program; a processor configured to execute the computer program stored in the memory, and when the computer program is executed, implements any component deployment method described herein.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, it implements any component deployment method described herein.

In a fifth aspect, an embodiment of the present application provides a computer program, which includes a computer-readable code. When the computer-readable code is executed on a device, a processor in the device implements any component deployment method described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a flow chart of a component deployment method provided in an embodiment of the present application;

FIG2 is a flow chart of another component deployment method provided in an embodiment of the present application;

FIG3A is a schematic diagram of a flow chart of another component deployment method provided in an embodiment of the present application;

FIG3B is a schematic diagram of a flow chart of another component deployment method provided in an embodiment of the present application;

FIG3C is a flow chart of another component deployment method provided in an embodiment of the present application;

FIG4 is a schematic diagram of the structure of a component deployment device provided in an embodiment of the present application;

FIG5 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

DETAILED DESCRIPTION

Various exemplary embodiments of the present application will now be described in detail with reference to the accompanying drawings. It should be noted that unless otherwise specifically stated, the relative arrangements of components and steps, numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present application.

Those skilled in the art will understand that the terms "first" and "second" in the embodiments of the present application are only used to distinguish between different steps, devices, modules and other objects, and do not represent any specific technical meanings, nor do they indicate the logical order between them.

It should also be understood that in this embodiment, “plurality” may refer to two or more than two, and “at least one” may refer to one, two or more than two.

It should also be understood that any component, data or structure mentioned in the embodiments of the present application can generally be understood as one or more, unless explicitly limited or otherwise indicated in the context.

In addition, the term "and/or" in this application is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character "/" in this application generally indicates that the associated objects before and after are in an "or" relationship.

It should also be understood that the description of each embodiment in this application focuses on the differences between the embodiments, and the same or similar aspects can be referenced to each other. For the sake of brevity, they will not be described one by one.

The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the present application, its application, or uses.

Technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the above-mentioned technologies, methods, and equipment should be considered as part of the specification.

It should be noted that like reference numerals and letters refer to similar items in the following drawings. Therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

It should be noted that, in the absence of conflict, the embodiments in this application and the features in the embodiments can be combined with each other. To facilitate the understanding of the embodiments of the present application, the present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

FIG1 is a flow chart of a component deployment method provided by an embodiment of the present application. The method can be applied to one or more electronic devices such as smart phones, laptops, desktop computers, portable computers, servers, etc. In addition, the execution subject of the method can be hardware or software. When the above-mentioned execution subject is hardware, the execution subject can be one or more of the above-mentioned electronic devices. For example, a single electronic device can execute the method, or multiple electronic devices can cooperate with each other to execute the method. When the above-mentioned execution subject is software, the method can be implemented as multiple software or software modules, or as a single software or software module. No special limitation is made here.

As shown in FIG. 1 , the method may include steps 101 to 104 .

Step 101: Obtain a component deployment instruction, and determine a target component to be deployed as instructed by the component deployment instruction.

In this embodiment, the above component deployment instruction can be used to indicate the deployment target component.

The target component can be the main packaging form of the kernel, driver, and user-mode program before deployment. For example, the target component can be a component package in a management format such as rpm or deb. For example, the target component can be ixgbe, megaraid_sas, i40e, smartpqi, mpt3sas, ixgbevf, and igb.

In addition, the target component may be a component in various systems. As an example, the target component may be a component in any of the following systems: Windows operating system, Linux operating system, Android operating system, etc.

Step 102: executing the target component represented by the component deployment instruction through the target component A deployment operation, wherein the target deployment operation does not include a creation and overwriting operation of an initial random access memory RAM disk.

In this embodiment, the target deployment operation may be other deployment operations other than the creation and overwriting operations of the RAM disk among the target deployment operations represented by the component deployment instruction. Alternatively, the component deployment instruction may also be used to instruct: to perform other deployment operations other than the creation and overwriting operations of the RAM disk.

In the Linux operating system, the initial RAM disk is a complete root file system, which contains the necessary components of a Linux operating system (such as drivers, process user-mode programs, dynamic libraries, etc.) in addition to the kernel.

The initial RAM disk creation is based on the files and configurations in the local root file system. The configuration of the creation tool (such as dracut, mkinitrd) is used as the basis for file screening and supplementation. The relevant files are collected, packaged according to the initial RAM disk format, and placed in the specified location for global use.

From the perspective of the composition of the Linux operating system, it mainly consists of grub, kernel, driver, initial RAM disk, local root file system, and user-mode programs. Among them, the kernel, driver, and user-mode programs are mainly packaged in component packages (such as target components) before deployment, such as rpm and deb package management formats. From a functional perspective, during the startup phase of the Linux operating system, grub first boots the kernel, then the kernel loads the initial RAM disk as the root file system, loads the driver in it, executes related programs, and then the kernel cuts the root to the local root file system and starts related programs, finally completing the startup of the operating system.

It should be noted that the initial RAM disk is strongly related to the kernel. If multiple different kernels are deployed on a Linux system at the same time, each kernel will have a corresponding initial RAM disk to adapt to the kernel and serve as the initial RAM disk shared by the system when the kernel is running.

In some optional implementations of this embodiment, the target deployment operation includes at least one of the following: signature verification of the target component, checking dependent components of the target component, file deployment and configuration, and updating record information indicating that the target component has been deployed.

It can be understood that in the above optional implementation, the target component can perform signature verification on the target component, check the dependent components of the target component, file deployment and configuration. The method further comprises: configuring and updating at least one deployment operation in the record information indicating that the target component has been deployed.

Step 103: Acquire preset global information from the system where the target component is located, wherein the preset global information is used to indicate a creation subject of the initial RAM disk.

In this embodiment, the system where the target component is located can be any one of the following: Windows operating system, Linux operating system, Android operating system, etc.

The preset global information may be stored in a storage space other than the target component in the above system. In addition, in some cases, the preset global information may include a subject identifier for indicating a subject that creates the initial RAM disk, or the preset global information may also include a keyword and a value to indicate whether the component (e.g., the target component) decides to create the initial RAM disk (e.g., create_initrd=yes, create_initrd=no).

Step 104: When the creation subject is not the target component, prohibit the target component from creating and overwriting the initial RAM disk.

In this embodiment, if the creation entity of the initial RAM disk indicated by the preset global information is not the above-mentioned target component, then after executing the target deployment operation indicated by the component deployment instruction, the target component can skip the operation of creating and overwriting the initial RAM disk, thereby prohibiting the target component from creating and overwriting the initial RAM disk.

In some optional implementations of this embodiment, after executing the above step 103, the following step may also be executed: when the creation subject is the target component, the initial RAM disk is created and overwritten by the target component.

It can be understood that in the above optional implementation method, the initial RAM disk is created and overwritten by the target component only when the creation subject is the target component. In this way, by presetting global information to control whether the initial RAM disk is created and overwritten by the target component, more effective control of the total component deployment duration in multiple component deployment scenarios is achieved.

The component deployment method provided in the embodiment of the present application can obtain a component deployment instruction and determine the target component to be deployed indicated by the component deployment instruction. Then, the target deployment operation indicated by the component deployment instruction is executed through the target component, wherein the target deployment operation does not include the creation and overwriting operation of the initial random access memory RAM disk. Then, preset global information is obtained from the system where the target component is located, wherein the preset global information is used to indicate the creation subject of the initial RAM disk. Finally, when the creation subject is not the target component, the creation and overwriting of the target component are prohibited. Overwrite the initial RAM disk. Thus, the preset global information indicating the creation subject of the initial RAM disk can be obtained from the system where the target component is located, and when the creation subject is not the target component, the target component is prohibited from creating and overwriting the initial RAM disk. In this way, some components do not need to create and overwrite the initial RAM disk, which reduces the number of times the initial RAM disk is created and overwritten, thereby reducing the loss of the initial RAM disk and saving the total component deployment time in multiple component deployment scenarios.

Fig. 2 is a flow chart of another component deployment method provided by an embodiment of the present application. As shown in Fig. 2, the method may include steps 201 to 206.

Step 201: Obtain a component deployment instruction, and determine a target component to be deployed as instructed by the component deployment instruction.

In this embodiment, step 201 is substantially the same as step 101 in the corresponding embodiment of FIG. 1 , and will not be described in detail here.

Step 202: Execute the target deployment operation represented by the component deployment instruction through the target component, wherein the target deployment operation does not include the creation and overwriting operation of the initial random access memory RAM disk.

In this embodiment, step 202 is substantially the same as step 102 in the corresponding embodiment of FIG. 1 , and will not be described in detail here.

Step 203: Obtain preset global information from the system where the target component is located, wherein the preset global information is used to indicate a creation subject of the initial RAM disk.

In this embodiment, step 203 is substantially the same as step 103 in the corresponding embodiment of FIG. 1 , and will not be described in detail here.

Step 204: when the creation subject is not the target component, prohibit the target component from creating and overwriting the initial RAM disk.

In this embodiment, step 204 is substantially the same as step 104 in the corresponding embodiment of FIG. 1 , and will not be described in detail here.

Step 205: When the operating environment of the target component does not match the system environment of the system, a component external object is determined as the creation subject.

In this embodiment, the operating environment of the target component and the system can be determined by determining whether the target component can be successfully deployed or run normally in the system environment. Whether the system environment matches.

The component external object may be any object (such as a program or toolkit) included in the above system except the target component, or may be a user.

Step 206, creating and overwriting the initial RAM disk through the component external object.

In this embodiment, when the creation subject is the target component and the operating environment of the target component does not match the system environment of the system, the initial RAM disk can be created and overwritten via the component external object. When the operating environment of the target component matches the system environment of the system (that is, the target component can be successfully deployed or run normally in the system environment), the initial RAM disk may not be created and overwritten.

In some optional implementations of this embodiment, the following method can be adopted to obtain the preset global information from the system where the target component is located: obtain the preset global information from the system where the target component is located through the target component.

On this basis, the initial RAM disk can be created and overwritten through the component external object in the following manner: the first step is to obtain the preset global information from the system where the target component is located through the component external object; the second step is to create and overwrite the initial RAM disk through the component external object when the creation subject is not the target component.

It can be understood that in the above optional implementation, preset global information is obtained through both the target component and the component external object, and then the judgment of the creation subject can be performed twice, which reduces the probability of erroneous creation of the creation subject of the initial RAM disk.

In some application scenarios of the above optional implementation manner, before executing the above first step, it is also possible to determine whether the target component has a deployment exception through the component external object.

Furthermore, if a deployment anomaly exists in a target component, the target component may be controlled to be redeployed or repaired.

It can be understood that in the above application scenario, whether there is a deployment anomaly in the target component can be determined through a component external object to ensure that the target component is deployed normally.

In some optional implementations of this embodiment, the following methods can be used to Creating and overwriting the initial RAM disk through the component external object: performing the creation and overwriting operation of the initial RAM disk once through the component external object, so as to create and overwrite the initial RAM disk for at least two of the target components.

Here, the operating environment information of the component can be recorded after each deployment of the target component. When creating and deploying the initial RAM disk, the intersection of the default operating environment information and the recorded operating environment information can be used as the content of creating and deploying the initial RAM disk.

It can be understood that in the above optional implementation method, an initial RAM disk can be created and deployed for at least two target components by performing an initial RAM disk creation and overwriting operation. This reduces the number of times the initial RAM disk is created and overwritten, thereby reducing the loss of the initial RAM disk and saving the total component deployment time in multiple component deployment scenarios.

It should be noted that, in addition to the contents recorded above, this embodiment may also include the corresponding technical features described in the embodiment corresponding to Figure 1, so as to achieve the technical effect of the component deployment method shown in Figure 1. Please refer to the relevant description of Figure 1 for details. For the sake of brevity, it will not be repeated here.

The component deployment method provided in the embodiment of the present application creates and overwrites the initial RAM disk through the external object of the component only when the creation subject is the above-mentioned target component and the operating environment of the target component does not match the system environment of the system. Therefore, when the operating environment of the target component matches the system environment of the system, there is no need to create and overwrite the initial RAM disk, which further reduces the number of times the initial RAM disk is created and overwritten, thereby reducing the loss of the initial RAM disk and saving the total component deployment time in multiple component deployment scenarios.

FIG3A is a flow chart of another component deployment method provided in an embodiment of the present application.

As shown in FIG. 3A , the method may include steps 301 to 305 .

Step 301, obtaining a component deployment instruction, and determining a target component to be deployed according to the component deployment instruction, wherein the system where the target component is located is a Linux operating system.

In this embodiment, the above component deployment instruction can be used to indicate the deployment target group Piece.

The target component can be the main packaging form of the kernel, driver, and user-mode program before deployment. For example, the target component can be a component package in a management format such as rpm or deb. For example, the target component can be ixgbe, megaraid_sas, i40e, smartpqi, mpt3sas, ixgbevf, and igb.

Furthermore, the target component may be a component in a Linux operating system.

In this embodiment, step 301 is substantially the same as step 101 in the corresponding embodiment of FIG. 1 , and will not be described in detail here.

Step 302: Execute the target deployment operation represented by the component deployment instruction through the target component, wherein the target deployment operation does not include the creation and overwriting operation of the initial random access memory RAM disk.

In this embodiment, step 302 is substantially the same as step 102 in the corresponding embodiment of FIG. 1 , and will not be described in detail here.

Step 303: Determine a pre-set global configuration file from the Linux operating system where the target component is located.

In this embodiment, the global configuration file can be used to record the configuration values in the Linux operating system. It can include information indicating the creation subject of the initial RAM disk. For example, the path of the global configuration file in the Linux operating system can be /etc/yum/extra.conf. Keywords and values can be set in it to indicate whether "the creation of the initial RAM disk is determined by the component external object" (for example, create_initrd=yes).

Step 304: query preset global information from the global configuration file, wherein the preset global information is used to indicate a creation subject of the initial RAM disk.

In this embodiment, when deploying (installing, upgrading, uninstalling) the target component, in the internal stage of the target component, the value in the above-mentioned global configuration file is queried and judged. If it is determined by an external object of the component (for example, create_initrd=yes), the judgment and operation related to the creation of the initial RAM disk by this target component are skipped; if it is not determined by an external object of the component (for example, create_initrd=no, or there is no global configuration file, or the global configuration file does not record the creation subject of the initial RAM disk), no existing operations will be skipped.

Step 305: When the creation subject is not the target component, prohibit the target component from creating and overwriting the initial RAM disk.

In this embodiment, the system where the target component is located may be a Linux operating system.

The preset global information may be stored in a storage space other than the target component in the above system. In addition, in some cases, the preset global information may include a subject identifier for indicating a subject that creates the initial RAM disk, or the preset global information may also include a keyword and a value to indicate whether the component (e.g., the target component) decides to create the initial RAM disk (e.g., create_initrd=yes, create_initrd=no).

The following is an illustrative description of the embodiments of the present application, but it should be noted that the embodiments of the present application may have the features described below, but the following description does not constitute a limitation on the scope of protection of the embodiments of the present application.

As shown in Figure 3B, Figure 3B is a flow chart of another component deployment method provided in an embodiment of the present application. The method includes the following steps 1 to 9.

Step 1, a person or program (ie, the above-mentioned component external object) sets "whether to make the initial RAM disk is determined by the outside of the component package" information (ie, the above-mentioned preset global information) outside the component package (ie, the above-mentioned target component).

Step 2: When a person or program starts to deploy (install, upgrade, uninstall) a component package, several actions are first performed inside the component package (i.e., the target deployment operations described above, such as component package signature verification and dependent component checking).

Step 3: Deploy and configure files within the component package, that is, perform the above-mentioned target deployment operation.

Step 4, the component package queries the external decision information of the component package (that is, the above-mentioned preset global information). If it is determined by the outside (that is, the above-mentioned component external object) to make the initial RAM disk, jump to step 6; if not, continue to execute step 5.

Step 5: If the component package determines that an initial RAM disk needs to be created, the initial RAM disk is created and overwritten with the initial RAM disk shared by the entire system; if it does not need to be created, the initial RAM disk is not created.

Step 6: Finishing actions within the component package (i.e., the target deployment operations mentioned above, such as updating the record information of the installed component packages of the entire system).

When all component packages (1 or N, N>1) of this deployment have executed the above steps in sequence, proceed to step 8 below.

Step 8: Post-deployment inspection, for example, a person or program checks whether the component package deployment is abnormal. often.

Step 9. A person or program queries external decision information. If the initial RAM disk is not made by external decision, it will not be made; if it is, it will be made and will cover the initial RAM disk shared by the entire system. It should be pointed out that: in special scenarios (for example, the current environment is a virtual machine environment, even if a driver component is deployed, but the environment does not have a device corresponding to the driver), a person or program may decide not to make an initial RAM disk; a person or program may also create multiple initial RAM disks according to their own special needs.

The following takes the target component as the rpm component package management format as an example to illustrate the above steps:

First, set up a global configuration file in the system, such as /etc/yum/extra.conf, in which keywords and values are set to indicate whether "making the initial RAM disk is determined by the outside of the component package (that is, the above-mentioned component external object)" (such as create_initrd = yes).

Secondly, a person or program (that is, the external object of the above-mentioned component) deploys (installs, upgrades, uninstalls) the rpm component package. At this time, in the "%post" and "%postun" stages inside rpm, the value in the above-mentioned global configuration file is queried and judged. If it is determined externally (for example, create_initrd=yes), the judgment and operation related to the creation of the initial RAM disk by this rpm package are skipped; if it is not determined externally (for example, create_initrd=no, or there is no global configuration file), no existing actions will be skipped.

Then, when all rpm component packages are deployed (installed, upgraded, uninstalled), a person or program checks the deployment results (eg, no errors are reported).

Finally, a person or a program queries the value in the above global configuration file and judges. If it is determined by an external party (for example, create_initrd=yes), the person or program executes the initial RAM disk creation tool to create an initial RAM disk and overwrite it (for example, dracut -f/boot/initramfs-3.10.0-693.el7.x86_64.img); if it is not determined by an external party (for example, create_initrd=no, or there is no global configuration file), the person or program does not perform any operation on the initial RAM disk.

Next, please continue to refer to Figure 3C. As shown in Figure 3C, Figure 3C is a flow chart of another component deployment method provided in an embodiment of the present application.

The differences between the component deployment method shown in FIG. 3C and the component deployment method shown in FIG. 3B are in the following two points.

First, instead of directly querying external decision information in the component package, when the initial RAM disk creation tool is called in the component package, the creation tool queries and determines internally. For example, the creation tool may be dracut or mkinitrd.

Second, add judgments in the creation tool. If it is used by the component package, it is controlled by external decisions. If it is not used by the component package, the existing actions remain unchanged.

Therefore, in the operating system, global information "whether the production of the initial RAM disk is determined by the outside of the component package" is set. Inside the component package, after completing the "file deployment and configuration" action, the above global information can be queried. Inside the component package, after completing the "file deployment and configuration" action, the above global information can be judged to determine whether the component package itself can produce the initial RAM disk. Outside the component package, in the tool for producing the initial RAM disk, the above global information can be queried. Outside the component package, in the tool for producing the initial RAM disk, the above global information can be judged to determine whether the production tool itself can produce the initial RAM disk. Outside the component package, a person can query the above global information. Outside the component package, a person can judge the above global information to determine whether the person himself can produce the initial RAM disk. Therefore, the operating system interface is not deleted, and a global query interface is added for querying whether the production of the initial RAM disk is determined by the outside of the component package, which can be queried by the component package, program, and person.

This solution can greatly reduce the time spent on new installation of Linux systems and batch deployment of component packages.

It should be noted that, in addition to the contents recorded above, this embodiment may also include the technical features described in the above embodiments, so as to achieve the technical effects of the component deployment method shown above. Please refer to the above description for details. For the sake of brevity, it will not be repeated here.

The component deployment method provided in the embodiment of the present application can configure a global configuration file from the Linux operating system where the target component is located, and set global information therein, so that some components in the Linux operating system do not need to create and overwrite the initial RAM disk, thereby reducing the number of times the initial RAM disk is created and overwritten, thereby reducing the loss of the initial RAM disk, and saving the total time for component deployment that depends on the Linux operating system in multiple component deployment scenarios.

FIG4 is a schematic diagram of the structure of a component deployment device provided in an embodiment of the present application. As shown in Figure 4, the device may include: a first acquisition unit 401, configured to acquire a component deployment instruction, and determine a target component that the component deployment instruction indicates to be deployed; a first execution unit 402, configured to execute a target deployment operation represented by the component deployment instruction through the target component, wherein the target deployment operation does not include the creation and overwriting operation of an initial random access memory RAM disk; a second acquisition unit 403, configured to acquire preset global information from the system where the target component is located, wherein the preset global information is used to indicate a creation subject of the initial RAM disk; a control unit 404, configured to prohibit the target component from creating and overwriting the initial RAM disk when the creation subject is not the target component.

In one possible implementation, after the target deployment operation represented by the component deployment instruction is executed by the target component, the device further includes: a first determination unit, configured to determine a component external object as the creation subject when the operating environment of the target component does not match the system environment of the system; and a first creation unit, configured to create and overwrite the initial RAM disk through the component external object.

In one possible implementation, obtaining preset global information from the system where the target component is located includes: obtaining preset global information from the system where the target component is located through the target component; and creating and overwriting the initial RAM disk through the component external object includes: obtaining the preset global information from the system where the target component is located through the component external object; and creating and overwriting the initial RAM disk through the component external object when the creation subject is not the target component.

In a possible implementation, before acquiring the preset global information from the system where the target component is located through the component external object, the device further includes: a second determination unit configured to determine whether there is a deployment anomaly in the target component through the component external object.

In one possible implementation, the creation and overwriting of the initial RAM disk through the component external object includes: a second execution unit, configured to perform a creation and overwriting operation of the initial RAM disk once through the component external object, so as to create and overwrite the initial RAM disk for at least two of the target components.

In a possible implementation, the system where the target component is located is a Linux operating system. and obtaining preset global information from the system where the target component is located, comprising: determining a preset global configuration file from the Linux operating system where the target component is located; and querying preset global information from the global configuration file.

In a possible implementation, after obtaining the preset global information from the system where the target component is located, the device further includes: a second creation unit configured to create and overwrite the initial RAM disk through the target component when the creation subject is the target component.

In a possible implementation, the target deployment operation includes at least one of the following: signature verification of the target component, checking dependent components of the target component, file deployment and configuration, and updating record information indicating that the target component has been deployed.

The component deployment device provided in this embodiment can be a component deployment device as shown in Figure 4, which can execute all steps of the component deployment methods described above, and then achieve the technical effects of the component deployment methods described above. Please refer to the above related description for details. For the sake of brevity, it will not be repeated here.

FIG5 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. The electronic device 500 shown in FIG5 includes: at least one processor 501, a memory 502, at least one network interface 504 and other user interfaces 503. The various components in the electronic device 500 are coupled together through a bus system 505. It can be understood that the bus system 505 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 505 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, various buses are marked as bus systems 505 in FIG5.

The user interface 503 may include a display, a keyboard, or a pointing device (eg, a mouse, a trackball, a touch pad, or a touch screen).

It can be understood that the memory 502 in the embodiment of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory. Random Access Memory (RAM) is used as an external high-speed cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 502 described herein is intended to include, but is not limited to, these and any other suitable types of memory.

In some implementations, the memory 502 stores the following elements, executable units or data structures, or a subset thereof, or an extended set thereof: an operating system 5021 and an application program 5022 .

The operating system 5021 includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., which are used to implement various basic services and process hardware-based tasks. The application 5022 includes various application programs, such as a media player (Media Player), a browser (Browser), etc., which are used to implement various application services. The program for implementing the method of the embodiment of the present application can be included in the application 5022.

In this embodiment, by calling the program or instruction stored in the memory 502, exemplarily, it can be the program or instruction stored in the application 5022, the processor 501 is used to execute the method steps provided by each method embodiment, for example, including: obtaining a component deployment instruction, and determining the target component indicated by the component deployment instruction for deployment; executing the target deployment operation represented by the component deployment instruction through the target component, wherein the target deployment operation does not include the creation and overwriting operation of the initial random access memory RAM disk; obtaining preset global information from the system where the target component is located, wherein the preset global information is used to indicate the creation subject of the initial RAM disk; when the creation subject is not the target component, prohibiting the target component from creating and overwriting the initial RAM disk.

The method disclosed in the above embodiment of the present application can be applied to the processor 501, or implemented by the processor 501. The processor 501 may be an integrated circuit chip having a signal Processing capability. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit or software instruction in the processor 501. The above processor 501 can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to be executed, or the hardware and software units in the decoding processor are combined and executed. The software unit can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 502, and the processor 501 reads the information in the memory 502 and completes the steps of the above method in combination with its hardware.

It is understood that the embodiments described herein can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPDevice, DSPD), programmable logic devices (PLD), field programmable gate arrays (FPGA), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the above-mentioned functions of the present application, or a combination thereof.

For software implementation, the technology described above in this article can be implemented by a unit that performs the functions described above in this article. The software code can be stored in a memory and executed by a processor. The memory can be implemented in the processor or outside the processor.

The electronic device provided in this embodiment may be an electronic device as shown in FIG5 , which may execute all steps of the component deployment methods described above, thereby achieving the technical effects of the component deployment methods described above. For details, please refer to the above related descriptions. For the sake of brevity, they will not be elaborated here.

The embodiment of the present application also provides a storage medium (computer-readable storage medium). The storage medium here stores one or more programs. The storage medium may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a read-only memory, a flash memory, a hard disk or a solid-state drive; the memory may also include a combination of the above types of memory.

When one or more programs in the storage medium can be executed by one or more processors, the component deployment method executed on the electronic device side can be implemented.

The above-mentioned processor is used to execute the component deployment program stored in the memory to implement the following steps of the component deployment method performed on the electronic device side: obtain a component deployment instruction, and determine the target component indicated by the component deployment instruction for deployment; execute the target deployment operation represented by the component deployment instruction through the target component, wherein the target deployment operation does not include the creation and overwriting operation of the initial random access memory RAM disk; obtain preset global information from the system where the target component is located, wherein the preset global information is used to indicate the creation subject of the initial RAM disk; when the creation subject is not the target component, prohibiting the target component from creating and overwriting the initial RAM disk.

The professionals should also be further aware that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

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

The exemplary embodiments described above further explain the purpose, technical solutions and beneficial effects of the present application in detail. It should be understood that the above description is only an exemplary embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles shall be included in the scope of protection of this application. In addition, for the aforementioned embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the described order of actions, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by this application.

Claims (11)

A component deployment method, comprising: Obtaining a component deployment instruction, and determining a target component that the component deployment instruction indicates to deploy; Executing, by the target component, a target deployment operation represented by the component deployment instruction, wherein the target deployment operation does not include a creation and overwriting operation of an initial random access memory RAM disk; Acquire preset global information from the system where the target component is located, wherein the preset global information is used to indicate a creation subject of the initial RAM disk; In the case where the creation subject is not the target component, the target component is prohibited from creating and overwriting the initial RAM disk. The method according to claim 1, wherein, after the target component executes the target deployment operation represented by the component deployment instruction, the method further comprises: In the case that the operating environment of the target component does not match the system environment of the system, determining a component external object as the creation subject; The initial RAM disk is created and overwritten by the component external object. The method according to claim 2, wherein the obtaining preset global information from the system where the target component is located comprises: Obtaining preset global information from the system where the target component is located through the target component; and The creating and overwriting the initial RAM disk by the component external object comprises: Acquiring the preset global information from the system where the target component is located through the component external object; In the case where the creation subject is not the target component, the initial RAM disk is created and overwritten by the component external object. The method according to claim 3, wherein, before acquiring the preset global information from the system where the target component is located through the component external object, the method further comprises: It is determined whether the target component has a deployment anomaly through the component external object. The method according to claim 2, wherein the creating and overwriting the initial RAM disk by the component external object comprises: The creation and overwriting operation of the initial RAM disk is performed once through the component external object so as to create and overwrite the initial RAM disk for at least two of the target components. The method according to claim 1, wherein the system where the target component is located is a Linux operating system; and The obtaining of preset global information from the system where the target component is located includes: Determine a pre-set global configuration file from the Linux operating system where the target component is located; The preset global information is queried from the global configuration file. The method according to claim 1, wherein, after acquiring the preset global information from the system where the target component is located, the method further comprises: In the case where the creation subject is the target component, the initial RAM disk is created and overwritten by the target component. The method according to any one of claims 1 to 7, wherein the target deployment operation comprises at least one of the following: Perform signature verification on the target component, check dependent components, file deployment and configuration of the target component, and update record information indicating that the target component has been deployed. A component deployment device, comprising: The first acquisition unit is configured to acquire a component deployment instruction and determine the component deployment instruction. The deployment instruction indicates the target component to be deployed; A first execution unit is configured to execute, through the target component, a target deployment operation represented by the component deployment instruction, wherein the target deployment operation does not include a creation and overwriting operation of an initial random access memory RAM disk; A second acquisition unit is configured to acquire preset global information from a system where the target component is located, wherein the preset global information is used to indicate a creation subject of the initial RAM disk; The control unit is configured to prohibit the target component from creating and overwriting the initial RAM disk when the creation subject is not the target component. An electronic device, comprising: a memory configured to store a computer program; The processor is configured to execute the computer program stored in the memory, and when the computer program is executed, the method described in any one of claims 1 to 8 is implemented. A computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the method described in any one of claims 1 to 8 is implemented.