CN110445841B - A method, device and storage medium for mounting a cloud disk on a cloud physical machine - Google Patents

Abstract

The invention discloses a method for mounting a cloud disk on a cloud physical machine, comprising the steps of: acquiring a cloud disk to be mounted and a corresponding random number from a metadata service; and judging whether the acquired random number and a locally cached random number are not the same; in response to the obtained random number being different from the locally cached random number, the operation of scanning and mounting the cloud disk is performed. The invention also discloses a computer device and a readable storage medium. The present invention utilizes the security isolation feature of the metadata service for the tenant network and the management network, obtains the latest metadata from the metadata service, determines whether to mount or unmount volumes, and operates on which remote volumes, without adding an intelligent network card and a management network. , save hardware cost, and have strong network security reliability.

Description

A method, device and storage medium for mounting a cloud disk on a cloud physical machine

technical field

The invention relates to the field of servers, in particular to a method, device and storage medium for mounting a cloud disk on a cloud physical machine.

Background technique

Openstack cloud physical machine is realized by the integration of computing service Nova, network service Neutron, mirroring service Glance, and cloud physical machine deployment service Ironic. The process of creating a cloud physical machine is actually the process of scheduling a cloud physical machine and installing it. . When the cloud physical machine is created, Ironic remotely controls the cloud physical machine to start from PXE through IPMI, and downloads the deployment image with the agent installed. The Ironic installation service interacts with the agent, and installs the user image selected by the user to the local cloud physical machine through the iscsi protocol. disk for system installation.

Because the local disk of the cloud physical machine is easily damaged, data is easily lost, and economic losses are caused. Therefore, it is necessary to mount the cloud hard disk on the cloud physical machine. The virtual machine can mount the remote cloud hard disk through libvirt on the host. Mounting a cloud hard disk on a cloud physical machine involves problems such as how to get through the network, how to transmit cloud hard disk information, and how to automatically discover and mount cloud hard disks in the system. At present, some cloud products implement cloud physical machines to mount cloud hard disks by adding smart network cards + agents, but the price is too high and the cost is too high; the method of adding management network + agents to cloud physical machines faces major network security problems.

Therefore, a new method for mounting a cloud disk on a cloud physical machine is urgently needed.

SUMMARY OF THE INVENTION

In view of this, in order to overcome at least one aspect of the above problem, an embodiment of the present invention proposes a method for mounting a cloud disk on a cloud physical machine, including the steps:

Obtain the cloud disk to be mounted and the corresponding random number from the metadata service;

Determine whether the obtained random number is the same as the locally cached random number;

In response to the obtained random number being different from the locally cached random number, an operation of scanning and mounting the cloud disk is performed.

In some embodiments, obtaining the cloud disk to be mounted and the corresponding random number from the metadata service further includes:

Periodically obtain the cloud disk to be mounted and the corresponding random number from the metadata service.

In some embodiments, performing the operation of scanning and mounting the cloud disk further includes:

The locally cached random number is replaced with the obtained random number.

In some embodiments, performing the operation of scanning and mounting the cloud disk further includes:

According to the cloud disks to be mounted, it is determined that there are cloud disks that do not need to be mounted further in the mounted cloud disks, and a cleaning operation is performed on the cloud disks that do not need to be mounted further.

In some embodiments, performing the operation of scanning and mounting the cloud disk further includes:

According to the cloud disk to be mounted, it is determined that there is a cloud disk that needs to be mounted further in the mounted cloud disk, and no operation is performed on the cloud disk that needs to be mounted further.

In some embodiments, performing the operation of scanning and mounting the cloud disk further includes:

According to the cloud disk to be mounted and the mounted cloud disk, it is determined that there is a new cloud disk in the cloud disk to be mounted, and a scan and mount operation is performed on the new cloud disk.

In some embodiments, it also includes:

Determine the cloud disk to be mounted;

associating the cloud disk to be mounted with the cloud physical machine;

Send the associated information of the cloud disk to be mounted to the metadata service, and generate the corresponding random number.

In some embodiments, associating the cloud disk to be mounted and the cloud physical machine further includes: using a cinder interface to associate the cloud disk to be mounted and the cloud physical machine;

Sending the associated information of the cloud disk to be mounted to the metadata service further includes: sending the associated information of the cloud disk to be mounted to the metadata service by using a metada interface.

Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a computer device, including:

at least one processor; and

A memory, where the memory stores a computer program that can be run on the processor, and is characterized in that, when the processor executes the program, any one of the above-mentioned methods for mounting a cloud disk on a cloud physical machine is performed. step.

Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor Perform the steps of any of the methods for mounting a cloud disk on a cloud physical machine as described above.

The present invention has one of the following beneficial technical effects: the present invention utilizes the security isolation feature of the metadata service for the tenant network and the management network, obtains the latest metadata from the metadata service, determines whether to mount or unmount volumes, and which remote volumes to perform Operation, no need to add intelligent network card and management network, save hardware costs, and has strong network security reliability.

Description of drawings

In order to explain the embodiments of the present invention or the technical solutions in the prior art more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. For those of ordinary skill in the art, other embodiments can also be obtained according to these drawings without creative efforts.

1 is a schematic flowchart of a method for mounting a cloud disk on a cloud physical machine according to an embodiment of the present invention;

2 is a flowchart of a method for mounting a cloud disk on a cloud physical machine according to an embodiment of the present invention;

3 is a structural block diagram of a method for mounting a cloud disk on a cloud physical machine according to an embodiment of the present invention;

4 is a schematic structural diagram of a computer device provided by an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a computer-readable storage medium provided by an embodiment of the present invention.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present invention more clearly understood, the embodiments of the present invention will be further described in detail below with reference to the specific embodiments and the accompanying drawings.

It should be noted that all expressions using "first" and "second" in the embodiments of the present invention are for the purpose of distinguishing two entities with the same name but not the same or non-identical parameters. It can be seen that "first" and "second" It is only for the convenience of expression and should not be construed as a limitation to the embodiments of the present invention, and subsequent embodiments will not describe them one by one.

It should be noted that, in the embodiment of the present invention, the metadata service is a sub-module of the OpenStack computing service, which provides a Restful interface for adding, deleting, modifying and checking cloud host metadata. For example, public clouds such as Alibaba Cloud and Huawei Cloud have this service. .

According to an aspect of the present invention, an embodiment of the present invention proposes a method for mounting a cloud disk on a cloud physical machine. As shown in FIG. 1 , the method may include steps: S1, obtaining a cloud disk to be mounted from a metadata service and corresponding random number; S2, determine whether the obtained random number is the same as the random number in the local cache; S3, in response to the obtained random number being different from the random number in the local cache, perform a scan to mount the Operation of the cloud disk.

The method disclosed in the present invention obtains the latest metadata from the metadata service by utilizing the security isolation feature of the metadata service for the tenant network and the management network, determines whether to mount or unmount volumes, and which remote volumes to operate on, without adding intelligence. Network card and management network, save hardware costs, and have strong network security reliability.

The following is a detailed description in conjunction with the flowchart of the method for mounting a cloud disk on a cloud physical machine shown in FIG. 2 .

First, you need to obtain the cloud disk to be mounted and the corresponding random number from the metadata service.

In some embodiments, the cloud disk to be mounted may be determined first; then the cloud disk to be mounted and the cloud physical machine are associated at the control level; and finally the cloud disk to be mounted is sent to the metadata service, and generate the corresponding random number.

Specifically, the user can determine which cloud disks need to be mounted to the cloud physical machine through the cloud platform operation interface, and then use the relevant interface to realize the association between the cloud physical machine and the cloud disk at the control level.

The interface specifically implements the binding logic between the cloud physical machine and the cloud hard disk at the control plane as follows:

The interface URL is /baremeatl/{baremetal_id}/os-volume_attachments, and the POST method is used; the API obtains the cloud disk UUID in the body, and calls the API layer bm_attach_volume interface, which obtains the DB object of the cloud physical machine, and calls the compute manager's Method bm_attach_volume. bm_attach_volume calls the ironic interface through ironic_client to obtain the cloud physical machine information, calls the cinder interface through cinder_client to obtain the iqn information (UUID serial number information) of each cloud hard disk, registers the cloud physical machine into the back-end storage, and binds the cloud hard disk to the cloud physical machine machine. Call the update_volume_metada interface to update the metadata of the cloud physical machine. The update_volume_metada interface updates the cloud hard disk iqn information list to the metadata volume_list of the cloud physical machine; and generates a random number flag for the agent to determine whether to perform a mount operation, and also update the metadata to the metadata.

At this point, the cloud physical machine at the control plane is attached to the cloud hard disk, and the cloud hard disk created by cinder has been associated with the cloud physical machine at the back end of the cloud physical machine.

It should be noted that flag is a metadata key, and its value is a random number, which is persisted to the metadata service. Only when the user performs the mount/unmount operation through the cloud platform operation interface, the control layer service will update it.

After the cloud disk to be mounted is associated with the cloud physical machine at the control level, the agent service bm_volume_agent for mounting the cloud hard disk can be used in the cloud physical machine. This agent service is installed in the cloud physical machine image. In the image, and registered as a service unit managed by systemd, the boot service starts automatically.

In some embodiments of the present invention, acquiring the cloud disk to be mounted and the corresponding random number from the metadata service includes: periodically acquiring the cloud disk to be mounted and the corresponding random number from the metadata service. In several further embodiments of the present invention, performing the operation of scanning and mounting the cloud disk further includes: replacing the locally cached random number with the acquired random number.

According to an embodiment of the present invention, the agent core is a timed task, which periodically obtains the metadata of the cloud physical machine from the metadata service every 20 seconds, and parses the list of cloud hard disks to be mounted and the mount flag fields, Thereby, the cloud disk to be mounted and the corresponding random number are obtained.

It should be noted that the acquisition period can be set according to actual needs, and is not limited to 20 seconds.

Then, it is determined whether the random number is the same as the locally cached random number.

The scheduled task in the cloud physical machine periodically obtains the metadata of the host: volume_list and flag. Each time it is obtained, it will be compared with the flag stored locally and the new flag will be stored locally. By comparing the mount flag field local_flag of the local cache with the flag flag in the metadata, it is judged whether to perform the scan and mount operation.

If flag≠local_flag, it means that the cloud physical machine is called to mount the cloud disk interface, that is, the control layer performs the mount operation. At this time, the mount task needs to be performed on the data layer, and the scan mount operation needs to be performed to list the cloud disk. The remote volume in is mounted locally, and the local flag field is updated.

If flag=local_flag, it means that the user does not call the interface and does not operate.

In some embodiments, performing the scan and mount operation may include: judging, according to the cloud disks to be mounted, that there are cloud disks that do not need to be mounted in the mounted cloud disks; Perform a cleanup operation on the cloud disk. According to a further embodiment, according to the cloud disk to be mounted, it is determined that there is a cloud disk that needs to be mounted further in the mounted cloud disk, and no operation is performed on the cloud disk that needs to be mounted continuously. According to a further embodiment, according to the cloud disk to be mounted and the cloud disk that has been mounted, it is determined that there is a new cloud disk in the cloud disk to be mounted, and scan and mount is performed on the new cloud disk operate.

Specifically, for example, the cloud disks that were mounted last time are A, B, and C, and the cloud disks that need to be mounted this time are A, B, and D. Then, when the mount task is performed, the actions that each volume needs to perform are obtained from the metadata, that is, A, B, and D need to be mounted, and C needs to be unloaded.

When a periodic task operates on each cloud disk to be mounted, it first determines whether the current state is equal to the target state, and then takes corresponding actions. For example, if A and B are already mounted, and the target is to mount, no action will be taken; if D is not mounted, scan the disk to mount. When the periodic task operates on each cloud disk to be uninstalled, it directly performs the cleanup operation.

In some embodiments of the present invention, the method further includes: determining the cloud disk to be mounted; associating the cloud disk to be mounted with the cloud physical machine; sending the associated information of the cloud disk to be mounted to the metadata service , and generate the corresponding random number. According to a further embodiment, associating the cloud disk to be mounted and the cloud physical machine further includes: using a cinder interface to associate the cloud disk to be mounted and the cloud physical machine. Sending the associated information of the cloud disk to be mounted to the metadata service further includes: sending the associated information of the cloud disk to be mounted to the metadata service by using a metada interface.

A detailed description will be given below with reference to the structural block diagram shown in FIG. 3 .

As shown in Figure 3, the mount cloud disk interface receives the pre-mounted cloud disk uuid, adds it to the metadata of the cloud physical machine, and generates a flag field to update the metadata. Call the cinder interface to bind the cloud physical machine to the remote volume. In the cloud physical machine system, the agent bm_volume_agent, which is injected into the image in advance and starts automatically, completes the mounting: the scheduled task periodically obtains the metadata of the cloud physical machine, and judges whether the upper layer operates according to whether the flag is equal to the local_flag saved locally. If they are not equal, mount on the data layer.

Based on the same inventive concept, according to another aspect of the present invention, as shown in FIG. 4 , an embodiment of the present invention further provides a computer device 501, including:

at least one processor 520; and

The memory 510 stores a computer program 511 that can run on the processor. When the processor 520 executes the program, the processor 520 executes the steps of any of the above methods for mounting a cloud disk on a cloud physical machine.

Based on the same inventive concept, according to another aspect of the present invention, as shown in FIG. 5 , an embodiment of the present invention further provides a computer-readable storage medium 601, where the computer-readable storage medium 601 stores computer program instructions 610, and the computer When the program instructions 610 are executed by the processor, the steps of any of the above methods for mounting a cloud disk on a cloud physical machine are performed.

Finally, it should be noted that those of ordinary skill in the art can understand that all or part of the process in the method of the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium, When the program is executed, it may include the flow of the embodiments of the above-mentioned methods. Wherein, the storage medium can be a magnetic disk, an optical disk, a read only memory (ROM) or a random access memory (RAM) and the like. The above computer program embodiments can achieve the same or similar effects as any of the foregoing method embodiments corresponding thereto.

In addition, typically, the apparatuses, devices, etc. disclosed in the embodiments of the present invention may be various electronic terminal devices, such as mobile phones, personal digital assistants (PDAs), tablet computers (PADs), smart TVs, etc., and may also be large-scale terminal devices. For example, a server, etc., therefore, the protection scope disclosed by the embodiments of the present invention should not be limited to a certain type of apparatus or equipment. The client disclosed in the embodiment of the present invention may be applied to any of the foregoing electronic terminal devices in the form of electronic hardware, computer software, or a combination of the two.

In addition, the methods disclosed according to the embodiments of the present invention may also be implemented as a computer program executed by the CPU, and the computer program may be stored in a computer-readable storage medium. When the computer program is executed by the CPU, the above-mentioned functions defined in the methods disclosed in the embodiments of the present invention are executed.

In addition, the above-mentioned method steps and system units can also be implemented by using a controller and a computer-readable storage medium for storing a computer program that enables the controller to implement the functions of the above-mentioned steps or units.

In addition, it should be understood that computer-readable storage media (eg, memory) herein can be volatile memory or non-volatile memory, or can include both volatile and non-volatile memory. By way of example and not limitation, nonvolatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory memory. Volatile memory may include random access memory (RAM), which may act as external cache memory. By way of example and not limitation, RAM is available in various forms such as synchronous RAM (DRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The storage devices of the disclosed aspects are intended to include, but not be limited to, these and other suitable types of memory.

Those skilled in the art will also appreciate that the various exemplary logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described generally in terms of their functionality. Whether such functionality is implemented as software or hardware depends on the specific application and design constraints imposed on the overall system. Those skilled in the art may implement the functions in various ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed embodiments of the present invention.

The various exemplary logical blocks, modules, and circuits described in connection with the disclosure herein can be implemented or executed using the following components designed to perform the functions herein: general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of these components. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, eg, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP, and/or any other such configuration.

The steps of a method or algorithm described in connection with the disclosures herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, such that the processor can read information from, and write information to, the storage medium. In an alternative, the storage medium may be integrated with the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in the user terminal. In an alternative, the processor and storage medium may reside in the user terminal as discrete components.

In one or more exemplary designs, functions may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium can be any available medium that can be accessed by a general purpose or special purpose computer. By way of example and not limitation, the computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or may be used to carry or store instructions in the form of or data structures and any other medium that can be accessed by a general purpose or special purpose computer or a general purpose or special purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave are used to send software from a website, server, or other remote source, the above coaxial cable Cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are all included in the definition of medium. As used herein, magnetic disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, blu-ray disks, where disks usually reproduce data magnetically, while optical disks reproduce data optically with lasers . Combinations of the above should also be included within the scope of computer-readable media.

The above are exemplary embodiments of the present disclosure, but it should be noted that various changes and modifications may be made without departing from the scope of the disclosure of the embodiments of the present invention as defined in the claims. The functions, steps and/or actions of the method claims in accordance with the disclosed embodiments described herein need not be performed in any particular order. Furthermore, although elements disclosed in the embodiments of the present invention may be described or claimed in the singular, unless explicitly limited to the singular, the plural may also be construed.

It should be understood that, as used herein, the singular form "a" is intended to include the plural form as well, unless the context clearly supports an exception. It will also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items.

The above-mentioned embodiments of the present invention disclose the serial numbers of the embodiments only for description, and do not represent the advantages and disadvantages of the embodiments.

Those of ordinary skill in the art can understand that all or part of the steps of implementing the above embodiments can be completed by hardware, or can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium. The storage medium can be read-only memory, magnetic disk or optical disk, etc.

Those of ordinary skill in the art should understand that the discussion of any of the above embodiments is only exemplary, and is not intended to imply that the scope (including the claims) disclosed by the embodiments of the present invention is limited to these examples; under the idea of the embodiments of the present invention , the technical features in the above embodiments or different embodiments can also be combined, and there are many other changes in different aspects of the above embodiments of the present invention, which are not provided in detail for the sake of brevity. Therefore, any omission, modification, equivalent replacement, improvement, etc. made within the spirit and principle of the embodiments of the present invention should be included within the protection scope of the embodiments of the present invention.

Claims (9)

1. A method for mounting a cloud disk on a cloud physical machine, comprising the steps of: Determine the cloud disk to be mounted; associating the cloud disk to be mounted with the cloud physical machine; Send the associated information of the cloud disk to be mounted to the metadata service, and generate a corresponding random number; Obtain the cloud disk to be mounted and the corresponding random number from the metadata service; Determine whether the obtained random number is the same as the locally cached random number; In response to the obtained random number being different from the locally cached random number, an operation of scanning and mounting the cloud disk is performed. 2. The method according to claim 1, wherein obtaining the cloud disk that needs to be mounted and the corresponding random number from the metadata service further comprises: Periodically obtain the cloud disk to be mounted and the corresponding random number from the metadata service. 3. The method according to claim 2, wherein performing the operation of scanning and mounting the cloud disk further comprises: The locally cached random number is replaced with the obtained random number. 4. The method of claim 1, wherein performing the operation of scanning and mounting the cloud disk further comprises: According to the cloud disks to be mounted, it is determined that there are cloud disks that do not need to be mounted further in the mounted cloud disks, and a cleaning operation is performed on the cloud disks that do not need to be mounted further. 5. The method of claim 1, wherein performing the operation of scanning and mounting the cloud disk further comprises: According to the cloud disk to be mounted, it is determined that there is a cloud disk that needs to be mounted further in the mounted cloud disk, and no operation is performed on the cloud disk that needs to be mounted further. 6. The method of claim 1, wherein performing the operation of scanning and mounting the cloud disk further comprises: According to the cloud disk to be mounted and the mounted cloud disk, it is determined that there is a new cloud disk in the cloud disk to be mounted, and a scan and mount operation is performed on the new cloud disk. 7. The method of claim 1, wherein associating the cloud disk to be mounted with the cloud physical machine further comprises: using a cinder interface to associate the cloud disk to be mounted with the cloud physical machine machine; Sending the associated information of the cloud disk to be mounted to the metadata service further includes: sending the associated information of the cloud disk to be mounted to the metadata service by using a metada interface. 8. A computer device comprising: at least one processor; and A memory, wherein the memory stores a computer program that can be executed on the processor, wherein the processor executes the method according to any one of claims 1-7 when the processor executes the program. 9 . A computer-readable storage medium storing a computer program, wherein the computer program executes the method according to any one of claims 1 to 7 when the computer program is executed by a processor. 10 .

Images