Storage volume mounting method and device, electronic equipment and storage medium

Abstract

The invention discloses a storage volume mounting method and device, electronic equipment and a storage medium, and the storage volume mounting method comprises the steps: responding to a storage volume mounting instruction corresponding to a target service, calling a management plane interface of a storage server through a current service node corresponding to the target service, and obtaining a first calling result; if the first calling result represents that calling is abnormal, calling a service interface of the storage server through a target service node corresponding to the target service; and mounting a target storage volume corresponding to the target service in the storage server to the target service node through the service interface. According to the method, the target storage volume is mounted to the target service node corresponding to the target service by multiplexing the service interface when the management plane link has the calling abnormity, so that strong dependence of the management plane interface is avoided, and stable operation of the target service is ensured.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and more specifically, to a method, device, electronic device and storage medium for mounting a storage volume. Background Art

[0002] In the block storage scenario, the storage volume corresponding to the user business is set with access rules through the management interface of the storage server, so that the storage volume is only accessible to the user business, and then the storage volume is mounted to the business node corresponding to the business through the business interface of the storage server to enable the user business to access the storage volume. However, when an abnormality occurs in the management link, it is impossible to set access rules for the target business through the management interface, resulting in the inability to mount the storage volume, affecting the normal operation of the user business. Summary of the invention

[0003] In view of the above problems, the present application proposes a method, device, electronic device and storage medium for mounting a storage volume.

[0004] In a first aspect, an embodiment of the present application provides a method for mounting a storage volume, the method comprising: in response to a storage volume mounting instruction corresponding to a target business, calling a management plane interface of a storage server through a current business node corresponding to the target business to obtain a first calling result; if the first calling result indicates a call exception, calling a business interface of the storage server through a target business node corresponding to the target business; and mounting a target storage volume corresponding to the target business in the storage server to the target business node through the business interface.

[0005] In the second aspect, an embodiment of the present application provides a storage volume mounting device, the device comprising: a first call result acquisition module, used to respond to the storage volume mounting instruction corresponding to the target business, call the management plane interface of the storage server through the current business node corresponding to the target business, and obtain a call result as the first call result; a business interface calling module, used to call the business interface of the storage server through the target business node corresponding to the target business if the first call result represents a call exception; a mounting module, used to mount the target storage volume corresponding to the target business in the storage server to the target business node through the business interface.

[0006] In a third aspect, an embodiment of the present application provides an electronic device, comprising: one or more processors; a memory; and one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are configured to execute the storage volume mounting method provided in the first aspect above.

[0007] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a program code is stored. The program code can be called by a processor to execute the method for mounting a storage volume provided in the first aspect.

[0008] The solution provided in the present application, when responding to the mount instruction of the storage volume of the target business, will first determine whether there is a call exception in the management plane link. If there is a call exception, the business interface in the storage server will be reused, and the target storage volume will be mounted to the target business node corresponding to the target business by calling the business interface, thereby avoiding strong dependence on the management plane interface and ensuring the stable operation of the target business. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0010] Figure 1 A schematic diagram of a network topology for mounting storage volumes in related technologies is shown.

[0011] Figure 2 A schematic diagram of a process for mounting a storage volume provided in an embodiment of the present application is shown.

[0012] Figure 3 A schematic flow chart of a method for mounting a storage volume provided in another embodiment of the present application is shown.

[0013] Figure 4 A schematic diagram of a process for mounting a storage volume provided in yet another embodiment of the present application is shown.

[0014] Figure 5 A schematic flow chart of a method for mounting a storage volume provided in yet another embodiment of the present application is shown.

[0015] Figure 6 A mounting flow chart of a storage volume mounting method provided in an embodiment of the present application is shown.

[0016] Figure 7 A schematic diagram of mounting a target storage volume when the first call result in an embodiment of the present application indicates that the management plane interface is in a normal state and the current service node is in a normal state is shown.

[0017] Figure 8 A schematic diagram of mounting a target storage volume when the first call result indicates that the management plane interface is in an abnormal state and the current service node is in an abnormal state in an embodiment of the present application is shown.

[0018] Fig. 9 A structural block diagram of a storage volume mounting device provided in an embodiment of the present application is shown.

[0019] Fig.10 A structural block diagram of an electronic device provided by an embodiment of the present application for executing a method for mounting a storage volume according to an embodiment of the present application is shown.

[0020] Fig.11 A storage medium provided by an embodiment of the present application and used to store or carry program code for implementing a method for mounting a storage volume according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0021] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

[0022] See also Figure 1 , Figure 1 A schematic diagram of the network topology for mounting storage volumes in the related art is shown. When the storage volume corresponding to the target business needs to be mounted, the switch of the business node corresponding to the current business will send a call instruction to the switch corresponding to the management plane interface of the storage server, and the data exchange router will forward the call instruction to the router corresponding to the management plane interface. The management plane interface then sets access rules for the business node, and the router corresponding to the management plane interface feeds the access rules back to the business node. The switch of the business node then forwards the access rules to the router corresponding to the business interface of the storage server through the data exchange router, so that the business interface mounts the storage volume to the business node according to the access rules, thereby realizing the target business's access to the storage volume.

[0023] In the related art, before mounting the storage volume, the access rules are set by calling the management interface to lock the service node connection, so that only the service node that has successfully locked the call can access the storage volume. However, this will cause the mounting of the storage volume to rely on the availability of the management interface. When the management interface is upgraded and restarted or abnormally powered off, if the service node used at this time is scheduled to migrate, the storage volume cannot be used because the call to lock the management interface before mounting the new service node fails, and the storage volume cannot be mounted.

[0024] In response to the problems in the background technology, the inventors have proposed a method, device, electronic device and storage medium for mounting a storage volume provided in the embodiments of the present application. When responding to the mount instruction of the storage volume of the target business, it will first determine whether there is a call exception in the management plane link. If there is a call exception, the business interface in the storage server is reused, and the target storage volume is mounted to the target business node corresponding to the target business by calling the business interface, thereby avoiding a strong dependence on the management plane interface and ensuring the stable operation of the target business.

[0025] The following will describe in detail the method, device, electronic device and storage medium for mounting a storage volume provided in the embodiments of the present application in conjunction with the accompanying drawings.

[0026] See also Figure 2 , Figure 2 The flowchart of the method for mounting a storage volume provided in the embodiment of the present application is shown. The method for mounting a storage volume can be applied to Fig. 9 The storage volume mounting device 300 and the electronic device 100 ( Fig.10 ).

[0027] The storage volume mounting method may specifically include the following steps:

[0028] Step S110: In response to a storage volume mounting instruction corresponding to the target service, the management plane interface of the storage server is called through the current service node corresponding to the target service to obtain a first calling result.

[0029] Among them, in the block storage system, the storage volume is treated as an independent hard disk. "Volume" is a logical concept, which represents a continuous storage space that can be recognized by the business node and used as data storage. The storage volume is usually composed of one or more storage blocks, which are formatted and mounted on the business node so that the storage volume can store files and / or directories in the business node mounted with it. The storage volume provides users with an interface that can directly read and write data in the storage server. The process of mounting a storage volume is actually the process of establishing a connection between the directory and / or file in the storage volume and the directory and / or file in the business node, so that the storage volume can store the directory and / or file of the business node. The mount instruction can be a direct mount instruction or an indirect mount instruction. The specific form of the mount instruction is not limited here.

[0030] In some embodiments, the storage volume may be an Internet Small Computer System Interface (iSCSI) storage volume. iSCSI is a network protocol standard that allows SCSI commands to be encapsulated in network data packets and transmitted over the Internet Protocol. This allows computers to remotely access storage devices through a local area network (LAN), a wide area network (WAN), or the Internet, just as if these devices were directly connected to a local computer. In most cases, an iSCSI volume can only be mounted in read-write mode by one service node at a time to ensure data security.

[0031] Furthermore, a storage server refers to a server used to store and manage large-scale data and supports various applications and services in a data center. A storage server can be a data center or a cloud server, and the storage server is not specifically limited here. A storage server may include multiple interfaces for implementing data storage and management, wherein the storage server includes but is not limited to a management interface and a business interface. The management interface is used to set access rules for business nodes so that only business nodes corresponding to the access rules are allowed to access the storage volumes corresponding to the access rules at the current moment to ensure data security. The business interface is used to establish a communication channel with a business node to implement business access to and storage of data.

[0032] The calling method may be a direct calling method or an indirect calling method, and the calling method is not specifically limited here. Further, the calling result includes a successful calling method and a calling abnormality.

[0033] In an embodiment of the present application, in response to a mount instruction of a storage volume corresponding to a target business, the current business node corresponding to the target business will call a management plane interface to facilitate completion of the storage volume mount task.

[0034] Step S120: If the first call result indicates a call exception, a service interface of the storage server is called through a target service node corresponding to the target service.

[0035] Among them, call exceptions include management plane interface exceptions, current business node exceptions, and both current business node and management plane interface exceptions.

[0036] Furthermore, the target service node may be the current service node of the target service, or may be another service node. When the target service node is another service node, the other service node may be a service node used only for storage volume mounting, or may be another service node that is not working and is determined as the target service node when the current service node fails, so as to complete the storage volume mounting task. The target service node is not limited here.

[0037] The calling method of the business interface can be the same as or different from the calling method of the management interface, and is not specifically limited here.

[0038] In an embodiment of the present application, when the first call result indicates a call exception, the business interface of the storage device is reused so that the business interface can complete the work that the management plane interface needs to complete, thereby completing the mounting of the storage volume to the target business node.

[0039] Step S130: Mounting the target storage volume corresponding to the target service in the storage server to the target service node through the service interface.

[0040] The mounting method may be a data volume mount, where the data volume of the target service node is mounted under the data volume of the target storage volume in the storage server. The mounting method may also be a file mount, where the file of the target service node is mounted in a specified file of the target storage volume. The mounting method may also be a directory mount, where the directory of the target service node is mounted in the directory of the target storage volume of the storage server. The mounting method is not specifically limited here.

[0041] In an embodiment of the present application, an association is established between a storage volume in a storage server and a target service node through a service interface, so that the storage volume can be mounted on the target service node, thereby enabling the target service to access the storage volume and store data.

[0042] The solution provided in this embodiment, when responding to the mount instruction of the storage volume of the target business, will first determine whether there is a call exception in the management plane link. If there is a call exception, the business interface in the storage server is reused, and the target storage volume is mounted to the target business node corresponding to the target business by calling the business interface, thereby avoiding strong dependence on the management plane interface and ensuring the stable operation of the target business.

[0043] See also Figure 3 , Figure 3 A schematic flow chart of a method for mounting a storage volume provided in another embodiment of the present application is shown.

[0044] Step S210: In response to a storage volume mounting instruction corresponding to a target service, a management plane interface of a storage server is called through a current service node corresponding to the target service to obtain a first calling result.

[0045] For the detailed description of step S210, please refer to step S110 in the aforementioned embodiment, which will not be repeated here.

[0046] Step S220: If the first calling result indicates that the management plane interface is in an abnormal state and the current service node is in a normal state, the current service node is determined to be the target service node, and the service interface is called through the target service node.

[0047] Step S230: Acquire target node information of the target service node through the service interface.

[0048] Step S240: Mounting the target storage volume corresponding to the target service in the storage server to the target service node through the service interface and according to the target node information.

[0049] The node information includes, but is not limited to, target service information, storage volume information corresponding to the target service, transmission protocol of target node information, transmission password corresponding to the target node, etc. The node information is not specifically limited here.

[0050] In the embodiment of the present application, when the first call result indicates that the management plane interface is in an abnormal state and the current service node is in a normal state, the current service node is determined as the target service node. The node information corresponding to the current service node is obtained through the service interface, and the association between the current service node and the target storage volume is established through the service interface according to the node information, so as to mount the target storage volume to the current service node, so as to realize the target service accessing the target storage volume.

[0051] In some implementations, mounting the target storage volume corresponding to the target service in the storage server to the target service node through the service interface and according to the target node information includes: setting access rules for the target service node through the service interface and according to the target node information. Mounting the target storage volume corresponding to the target service in the storage server to the target service node through the service interface and according to the access rules.

[0052] Among them, the access rule can be an access control list rule (Access Control List, ACL). ACL can filter the data packets on the interface according to the set conditions, allowing them to pass or discard them. ACL can set access rules for storage volumes by generating a unique identifier at the business node and sending it to the storage server. At this time, the storage server only allows the business node with the identifier to read and write the mounted storage volume. The access rule can also be a custom rule to achieve that when accessing the target storage volume at the current moment, only the target business node is allowed to access it. The access rule is not specifically defined here.

[0053] In an implementation manner of the present application, access rules are set for the target business node according to the node information of the target business node through the business interface to ensure that only the target business node is allowed to mount the target storage volume at the current moment, thereby ensuring data security.

[0054] In an optional implementation, the target node information includes a node verification password, and setting access rules for the target service node through the service interface according to the target node information includes: generating a verification password corresponding to the target service node through the service interface according to the node verification password. Verifying the target service node through the service interface according to the verification password to obtain a verification result. If the verification result indicates that the verification is passed, setting the access rules for the target service node through the service interface.

[0055] Among them, the node verification password can be a Challenge Handshake Authentication Protocol (CHAP) password. The Challenge Handshake Authentication Protocol periodically verifies the identity of the other party through a three-way handshake, which is completed when the initial link is established and can be repeated at any time after the link is established to ensure data security during data interaction. The node verification password can also be a custom-set secret key. The corresponding decryption key is set in the business interface to verify the target business node, thereby ensuring data security. The secret key can be a symmetric secret key or a custom secret key. The secret key and the decryption key are not specifically limited here. At the same time, the specific form of the node verification password is not limited, and it can be set according to actual needs.

[0056] In this embodiment, the target service node is authenticated first by the node verification password, and the access rule is set for the target service node only after the authentication is passed. If the authentication fails, the access to the target service node is denied, thereby protecting data security.

[0057] The solution provided in this embodiment reuses the business interface when the first call result indicates that the management plane interface is in an abnormal state and the current business node is in a normal state, and calls the business interface through the current business node, so that the business interface mounts the target storage volume to the current business node according to the node information of the current business node, so as to ensure that the target storage volume is only accessed by the current business node at the current moment, so as to ensure the data security in the target storage volume.

[0058] See also Figure 4 , Figure 4 A schematic diagram of a process flow of a method for mounting a storage volume provided by another embodiment of the present application is shown. The method for mounting a storage volume may specifically include the following steps:

[0059] Step S310: In response to a storage volume mounting instruction corresponding to a target service, a management plane interface of a storage server is called through a current service node corresponding to the target service to obtain a first calling result.

[0060] For the detailed description of step S310, please refer to step S110 in the aforementioned embodiment, which will not be repeated here.

[0061] Step S320: If the first call result indicates that the management plane interface is in a normal state and the current service node is in an abnormal state, determine a candidate service node corresponding to the target service from a service node cluster, and determine the candidate service node as the target service node, wherein the service node cluster includes multiple service nodes.

[0062] The candidate service nodes may be determined randomly, and non-working service nodes in the service node cluster may be randomly determined as candidate service nodes. The determination method may also be to first determine two or more service nodes for the target service from the service node cluster, and then determine one service node as the current service node of the target service, and the other service nodes as candidate service nodes. The method for determining the candidate service nodes may be selected according to actual needs, and is not specifically limited here.

[0063] In the embodiment of the present application, if the current service node is in an abnormal state, the current service node cannot complete the related operations of the mount instruction. At this time, according to the determination method of the candidate service node, the candidate service node corresponding to the target service is determined from the service node cluster, and the candidate service node is used as the target service node to complete the related operations of the mount instruction.

[0064] Step S330: calling the management plane interface through the target service node to obtain a second calling result.

[0065] In the embodiment of the present application, since the first call result only indicates that the current service node is in an abnormal state when the current service node calls the management plane interface, the access rule of the target service node needs to call the management plane interface to set it, and obtain the second call result of the target service node calling the management plane interface.

[0066] Step S340: If the second calling result indicates that the management plane interface is in a normal state, the management plane interface is called through the target service node.

[0067] Step S350: Setting access rules for the target service node through the management plane interface.

[0068] Step S360: Through the service interface and according to the access rule, the target storage volume corresponding to the target service in the storage server is mounted to the target service node.

[0069] In an embodiment of the present application, when the second call result indicates that the management plane interface is in a normal state, the management plane interface sets access rules for the target business node, and mounts the storage volume corresponding to the target business to the target business node through the business interface and access rules to enable the target business to access the storage volume.

[0070] Step S370: If the second calling result indicates that the management plane interface is in an abnormal state, calling the service interface through the target service node.

[0071] Step S380: Mounting the target storage volume corresponding to the target service in the storage server to the target service node through the service interface.

[0072] In an embodiment of the present application, when the second call result indicates that the management plane interface is in an abnormal state, access rules are set for the target business node by calling the business interface, and the storage volume is mounted to the target business node through the business interface and the access rules to enable the target business to access the storage volume.

[0073] In the embodiment of the present application, when the first call result only indicates that the current business interface is in an abnormal state, a candidate business node will be determined from the business node cluster first, and the candidate business node will be used as the target business node of the target business. At this time, the candidate business node calls the management plane interface to obtain the second call result to determine the state of the management plane interface at the current moment. If the second call result indicates that the management plane interface is in a normal state, the access rules are set for the candidate business node directly through the management plane interface. If the second call result indicates that the management plane interface is in an abnormal state, the reused business interface sets the access rules for the candidate business node. Then, according to the access rules, the target storage volume is mounted to the candidate business node through the business interface. When the current business node is in an abnormal state, the candidate business node will be determined in time, and the mounting work of the target storage volume will continue through the candidate business node. In addition, during the mounting process, the management plane interface will be called again to determine the state of the management plane interface. When the management plane interface is in an abnormal state, the normal mounting of the storage volume is guaranteed by reusing the business interface.

[0074] See also Figure 5 , Figure 5 A schematic flow chart of a method for mounting a storage volume provided in yet another embodiment of the present application is shown.

[0075] Step S410: In response to a storage volume mounting instruction corresponding to a target service, a management plane interface of a storage server is called through a current service node corresponding to the target service to obtain a first calling result.

[0076] For the detailed description of step S410, please refer to step S110 in the aforementioned embodiment, which will not be repeated here.

[0077] Step S420: If the first call result indicates that the management plane interface is in an abnormal state and the current service node is in an abnormal state, a candidate service node is determined from a service node cluster, and the candidate service node is determined as the target service node.

[0078] Step S430: calling the service interface of the storage server through the target service node.

[0079] In an embodiment of the present application, when the first call result indicates that the management interface is in an abnormal state, and the current business node is in an abnormal state, if the storage volume corresponding to the target business needs to be mounted to the relevant business node, it is necessary to re-determine the candidate business node for the target business from the business node cluster, and determine the candidate business node as the target business node of the target business node. The candidate business node calls the business interface of the storage server so that the business interface sets access rules for the candidate business node, so that the storage volume is only allowed to be used by the candidate business node at the same time through the access rule, thereby ensuring data security. The method for determining the candidate business node can refer to the method for determining step S320 in the aforementioned embodiment, which will not be repeated here.

[0080] Step S440: Mounting the target storage volume corresponding to the target service in the storage server to the target service node through the service interface.

[0081] For the detailed description of step S440, please refer to step S130 in the aforementioned embodiment, which will not be repeated here.

[0082] The solution provided in this embodiment will determine a candidate business node when the current business node is in an abnormal state and the management plane interface is in an abnormal state, and the candidate business node will reuse the business interface to complete the mounting of the target storage volume, thereby avoiding a strong dependence on the management plane interface and ensuring the normal operation of the target business without affecting the business fault scheduling.

[0083] In conjunction with the above embodiments, please refer to Figure 6 , Figure 6A mounting flow chart of a storage volume mounting method provided by an embodiment of the present application is shown. When the current business node node1 where the target business is located receives a mounting instruction for the target storage volume corresponding to the target business, the current business node node1 will first be used to send a call instruction to the management plane interface of the storage server to the management plane interface of the storage server, so that the management plane interface sets access rules for the target business node corresponding to the target business. The target business node then establishes an association between the current business node and the target storage volume through the business interface of the storage server and the access rules, so that the target storage volume is mounted on the current business node. When the current business node node1 calls the management plane interface, it will determine whether the management plane interface and / or the current business node node1 can work normally based on the first call result fed back. When the first call result indicates that the management plane interface is in an abnormal state, and the current business node node1 is in a normal state, the current business node node1 is determined as the target business node corresponding to the target business, and the current business node node1 calls the business interface of the storage server to set access rules for the current business node node1, so that the business interface establishes an association between the current business node and the target storage volume according to the access rules, and then mounts the target storage volume to the current business node node1. When the first call result indicates that the management plane interface is in a normal state and the current business node is in an abnormal state, the candidate business node node2 is determined from the business node cluster, and the candidate business node node2 is determined as the target business node corresponding to the target business. The target business node node2 calls the management plane interface to obtain a second call result. When the second call result indicates that the management plane interface is in a normal state, the management plane interface sets access rules for the candidate business node node2, and mounts the target storage volume to the candidate business node node2 according to the access rules through the business interface. When the second call result indicates that the management plane interface is in an abnormal state, the target business node calls the business interface, so that the business interface sets access rules for the candidate business node node2, and then mounts the target storage volume to the candidate business node node2 through the business interface according to the access rules. When the first call result indicates that the management plane interface is in an abnormal state, and the current business node is in an abnormal state, the candidate business node node2 is first determined from the business node cluster as the target business node of the target business, and the business interface is called by the candidate business node node2 to set access rules for the target business node, and then the target storage volume is mounted to the candidate business node node2 through the business interface according to the access rules. The solution provided in the embodiment of the present application reuses the business interface without affecting the business fault call when an abnormality occurs in the management plane interface link, and mounts the target storage volume to the target business node through the business interface by calling the business interface to ensure the normal mounting of the storage volume.

[0084] For example, see Figure 7 , Figure 7 The diagram shows the mounting diagram of the target storage volume when the first call result in the embodiment of the present application indicates that the management interface is in a normal state and the current service node is in a normal state. Access rules are set for node1 through the management interface, and the target storage volume is mounted to node1 through the service interface. Figure 8 , Figure 8 A schematic diagram of mounting a target storage volume when the first call result indicates that the management plane interface is in an abnormal state and the current service node is in an abnormal state in an embodiment of the present application is shown. Figure 8 In the example, when node1 is in an abnormal state and the management plane interface is in an abnormal state, node2 in the business node cluster is determined to be a candidate business node for the target business, and access rules are set for node2 through the business interface. Finally, the target storage volume is mounted to node2 through the business interface according to the access rules.

[0085] See also Fig. 9 , which shows a structural block diagram of a storage volume mounting device 300 provided in an embodiment of the present application. The storage volume mounting device 300 is applied to an electronic device 100, and the storage volume mounting device 300 includes: a first call result acquisition module 310, which is used to respond to the storage volume mounting instruction corresponding to the target business, call the management plane interface of the storage server through the current business node corresponding to the target business, and obtain a call result as the first call result; a business interface calling module 320, which is used to call the business interface of the storage server through the target business node corresponding to the target business if the first call result indicates a call exception; a mounting module 330, which is used to mount the target storage volume corresponding to the target business in the storage server to the target business node through the business interface.

[0086] In some embodiments of the present application, the business interface calling module 320 includes: a first calling submodule, which is used to determine that the current business node is the target business node if the first calling result indicates that the management plane interface is in an abnormal state and the current business node is in a normal state, and call the business interface through the target business node.

[0087] In some embodiments of the present application, the business interface calling module 320 includes: a second calling submodule, which is used to determine the candidate business node corresponding to the target business from the business node cluster if the first calling result indicates that the management plane interface is in a normal state and the current business node is in an abnormal state, and determine the candidate business node as the target business node, wherein the business node cluster includes multiple business nodes; a second calling result obtaining submodule, which is used to call the management plane interface through the target business node to obtain a second calling result; a management plane interface calling submodule, which is used to call the management plane interface through the target business node if the second calling result indicates that the management plane interface is in a normal state; an access rule first setting submodule, which is used to set access rules for the target business node through the management plane interface; a first mounting submodule, which is used to mount the target storage volume corresponding to the target business in the storage server to the target business node through the business interface and according to the access rules; and a third calling submodule, which is used to call the business interface through the target business node if the second calling result indicates that the management plane interface is in an abnormal state.

[0088] In some embodiments of the present application, the business interface calling module 320 includes: a candidate business node determination submodule, which is used to determine a candidate business node from a business node cluster and determine the candidate business node as the target business node if the first calling result indicates that the management plane interface is in an abnormal state and the current business node is in an abnormal state; and a fourth calling submodule, which is used to call the business interface of the storage server through the target business node.

[0089] In some embodiments of the present application, the mounting module 330 includes: a target node information acquisition submodule, used to obtain the target node information of the target business node through the business interface; and a second mounting submodule, used to mount the target storage volume corresponding to the target business in the storage server to the target business node through the business interface and based on the target node information.

[0090] In some embodiments of the present application, the second mounting sub-module includes: an access rule setting unit, used to set access rules for the target business node through the business interface and according to the target node information; a mounting unit, used to mount the target storage volume corresponding to the target business in the storage server to the target business node through the business interface and according to the access rules.

[0091] In some embodiments of the present application, the access rule setting unit includes: a verification password generation subunit, which is used to generate a verification password corresponding to the target business node according to the node verification password through the business interface; a verification result acquisition subunit, which is used to verify the target business node according to the verification password through the business interface to obtain a verification result; and an access rule setting subunit, which is used to set the access rule for the target business node through the business interface if the verification result indicates that the verification is passed.

[0092] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices and modules can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here.

[0093] In several embodiments provided in the present application, the coupling between modules may be electrical, mechanical or other forms of coupling.

[0094] In addition, each functional module in each embodiment of the present application can be integrated into a processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The above integrated modules can be implemented in the form of hardware or software functional modules.

[0095] A structural block diagram of an electronic device provided in an embodiment of the present application. Please refer to Fig.10 , which shows a structural block diagram of an electronic device provided in an embodiment of the present application. The electronic device 100 can be an electronic device such as a computer, a server, etc. that can run an application. The electronic device 100 in the present application may include one or more of the following components: a processor 101, a memory 102, and one or more applications, wherein the one or more applications may be stored in the memory 102 and configured to be executed by one or more processors 101, and the one or more programs are configured to execute the method described in the aforementioned method embodiment.

[0096] The processor 101 may include one or more processing cores. The processor 101 uses various interfaces and lines to connect various parts of the entire electronic device 100, and executes various functions and processes data of the electronic device 100 by running or executing instructions, programs, code sets or instruction sets stored in the memory 102, and calling data stored in the memory 102. Optionally, the processor 101 can be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), and programmable logic array (PLA). The processor 101 can integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing display content; and the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 101, but may be implemented separately through a communication chip.

[0097] The memory 102 may include a random access memory (RAM) or a read-only memory (ROM). The memory 102 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 102 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the following various method embodiments, etc. The data storage area may also store data (such as a phone book, audio and video data, chat record data) created by the electronic device 100 during use.

[0098] Please refer to Fig.11 , which shows a structural block diagram of a computer-readable storage medium provided in an embodiment of the present application. The computer-readable storage medium 200 stores program codes, which can be called by a processor to execute the method described in the above method embodiment.

[0099] The computer-readable storage medium 200 may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read-only memory), an EPROM, a hard disk, or a ROM. Optionally, the computer-readable storage medium 200 includes a non-transitory computer-readable storage medium. The computer-readable storage medium 200 has storage space for program code 210 that performs any method steps of the above method. These program codes can be read from or written to one or more computer program products. The program code 210 can be compressed, for example, in an appropriate form.

[0100] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for mounting a storage volume, characterized in that: The method comprises: In response to a storage volume mounting instruction corresponding to a target service, calling a management plane interface of a storage server through a current service node corresponding to the target service to obtain a first calling result; If the first call result indicates a call exception, calling a service interface of the storage server through a target service node corresponding to the target service; The target storage volume corresponding to the target service in the storage server is mounted to the target service node through the service interface.

2. The method according to claim 1, characterized in that If the first call result indicates a call exception, calling the service interface of the storage server through the target service node corresponding to the target service includes: If the first calling result indicates that the management plane interface is in an abnormal state and the current service node is in a normal state, the current service node is determined to be the target service node, and the service interface is called through the target service node.

3. The method according to claim 1, characterized in that If the first call result indicates a call exception, calling the service interface of the storage server through the target service node corresponding to the target service includes: If the first call result indicates that the management plane interface is in a normal state and the current service node is in an abnormal state, determining a candidate service node corresponding to the target service from a service node cluster, and determining the candidate service node as the target service node, wherein the service node cluster includes multiple service nodes; Calling the management plane interface through the target service node to obtain a second calling result; If the second calling result indicates that the management plane interface is in a normal state, calling the management plane interface through the target service node; Setting access rules for the target service node through the management plane interface; Mounting the target storage volume corresponding to the target service in the storage server to the target service node through the service interface and according to the access rule; If the second calling result indicates that the management plane interface is in an abnormal state, the service interface is called through the target service node.

4. The method according to claim 1, characterized in that If the first call result indicates a call exception, calling the service interface of the storage server through the target service node corresponding to the target service includes: If the first call result indicates that the management plane interface is in an abnormal state and the current service node is in an abnormal state, determining a candidate service node from a service node cluster, and determining the candidate service node as the target service node; The service interface of the storage server is called through the target service node.

5. The method according to any one of claims 1 to 4, characterized in that: The step of mounting the target storage volume corresponding to the target service in the storage server to the target service node through the service interface includes: Obtaining target node information of the target service node through the service interface; Through the service interface and according to the target node information, the target storage volume corresponding to the target service in the storage server is mounted to the target service node.

6. The method according to claim 5, characterized in that The step of mounting the target storage volume corresponding to the target service in the storage server to the target service node through the service interface according to the target node information includes: Setting access rules for the target service node according to the target node information through the service interface; Through the service interface and according to the access rule, the target storage volume corresponding to the target service in the storage server is mounted to the target service node.

7. The method according to claim 6, characterized in that The target node information includes a node verification password, and setting an access rule for the target service node according to the target node information through the service interface includes: Generate a verification password corresponding to the target service node according to the node verification password through the service interface; Verifying the target service node through the service interface according to the verification password to obtain a verification result; If the verification result indicates that the verification is passed, the access rule is set for the target service node through the service interface.

8. A storage volume mounting device, characterized in that: The device comprises: A first call result acquisition module is used to respond to the storage volume mounting instruction corresponding to the target business, call the management plane interface of the storage server through the current business node corresponding to the target business, and obtain the call result as the first call result; A service interface calling module, configured to call the service interface of the storage server through a target service node corresponding to the target service if the first calling result indicates a call exception; The mounting module is used to mount the target storage volume corresponding to the target service in the storage server to the target service node through the service interface.

9. An electronic device, characterized in that: The electronic device comprises: one or more processors; Memory; One or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are configured to execute the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores program codes, which can be called by a processor to execute the method according to any one of claims 1 to 7.

Images