Method for mounting cloud hard disk on bare metal server, distributed management system and device

Abstract

The invention relates to a bare metal server cloud hard disk mounting method, a distributed management system and a device. The method is applied to an iSCSI server, and comprises the following steps: receiving a cloud hard disk mounting request carrying a bare metal server identifier and a cloud hard disk identifier sent by a management and control platform, and searching a bare metal server address corresponding to the bare metal server identifier, and forwarding the cloud hard disk mounting request to a cloud hard disk mounting proxy component deployed on a bare metal server corresponding to the bare metal server address, so that the cloud hard disk mounting proxy component mounts a cloud hard disk corresponding to the cloud hard disk identifier to the bare metal server, and receiving a mounting result fed back by the cloud hard disk mounting proxy component, and feeding back the mounting result to the management and control platform. By adopting the scheme, the network security of the virtual private cloud of the tenant can be improved, and the cloud hard disk mounting efficiency can also be improved.

Description

Technical Field

[0001] The present application relates to the field of cloud computing and distributed technology, and in particular to a method, device, distributed management system, computer equipment, computer-readable storage medium, and computer program product for mounting a cloud hard disk on a bare metal server. Background Art

[0002] In the field of cloud computing, performance, cost and security are key issues. Compared with cloud hosts that share CPU (Central Processing Unit) and memory resources, bare metal servers provide complete CPU and memory resources, with the advantages of high performance and low latency.

[0003] Currently, the existing bare metal mounting iSCSI (Internet Small Computer System Interface) cloud hard disk solutions mainly include mounting the cloud hard disk by adding a management network card.

[0004] However, although the cost of adding a management network card is low, the networks of all tenants' bare metal servers are connected, which poses a network security risk. In addition, the mounting operation is complicated and time-consuming, affecting the mounting efficiency.

[0005] It can be seen from this that a more secure and efficient solution for mounting cloud hard disks on bare metal servers is needed. Summary of the invention

[0006] Based on this, it is necessary to provide a safe and efficient bare metal server cloud hard disk mounting method and device, as well as a distributed management system, computer equipment, computer-readable storage medium and computer program product to address the above technical problems.

[0007] In a first aspect, the present application provides a method for mounting a cloud hard disk on a bare metal server, which is applied to an iSCSI server, wherein the iSCSI server communicates with a bare metal server in a tenant's virtual private cloud through a virtual private cloud terminal node created on the tenant's virtual private cloud. The method includes:

[0008] Receive a cloud hard disk mount request sent by the management and control platform, where the cloud hard disk mount request carries a bare metal server identifier and a cloud hard disk identifier;

[0009] Find the bare metal server address corresponding to the bare metal server identifier, and forward the cloud hard disk mount request to the cloud hard disk mount proxy component deployed on the bare metal server corresponding to the bare metal server address, so that the cloud hard disk mount proxy component mounts the cloud hard disk corresponding to the cloud hard disk identifier to the bare metal server;

[0010] Receive the mounting result fed back by the cloud hard disk mounting agent component, and feed back the mounting result to the management and control platform.

[0011] In one of the embodiments, a virtual private cloud terminal node service is created on the iSCSI virtual private cloud where the iSCSI server is located, and the virtual private cloud terminal node service is connected to the virtual private cloud terminal node created on the tenant virtual private cloud, so that the tenant virtual private cloud and the iSCSI server can communicate over the network.

[0012] In one embodiment, the method further comprises:

[0013] Receiving identification information and address information of the bare metal server reported by the cloud hard disk mounting agent component;

[0014] The identification information and address information of the bare metal server are stored.

[0015] In one embodiment, the method further comprises:

[0016] In response to the cloud hard disk creation message sent by the management and control platform, create a cloud hard disk in the storage cluster;

[0017] An iSCSI target is created on the iSCSI gateway, and the iSCSI target is associated with the hard disk information of the created cloud hard disk.

[0018] In a second aspect, the present application further provides a distributed management system, including: a management and control platform, an iSCSI server and a bare metal server, wherein a virtual private cloud terminal node service is created on the iSCSI virtual private cloud where the iSCSI server is located, and the virtual private cloud terminal node service is connected to the virtual private cloud terminal node created on the tenant virtual private cloud, so that the tenant virtual private cloud and the iSCSI server perform network communication, and multiple bare metal servers are deployed on the tenant virtual private cloud;

[0019] The bare metal server is used to report the identification information and address information of the bare metal server to the management and control platform and the iSCSI server;

[0020] The management and control platform is used to store the identification information and address information of the bare metal server, and send a cloud hard disk mount request carrying the bare metal server identification and the cloud hard disk identification to the iSCSI server;

[0021] The iSCSI server is used to find the bare metal server address corresponding to the bare metal server identifier, forward the cloud hard disk mount request to the cloud hard disk mount proxy component deployed on the bare metal server corresponding to the bare metal server address, so that the cloud hard disk mount proxy component mounts the cloud hard disk corresponding to the cloud hard disk identifier to the bare metal server, receives the mount result fed back by the cloud hard disk mount proxy component, and feeds back the mount result to the management and control platform.

[0022] In a third aspect, the present application further provides a device for mounting a cloud hard disk on a bare metal server, which is applied to an iSCSI server, wherein the iSCSI server communicates with a bare metal server in a tenant's virtual private cloud through a virtual private cloud terminal node created on the tenant's virtual private cloud; the device comprises:

[0023] A request receiving module, used to receive a cloud hard disk mount request sent by the management and control platform, wherein the cloud hard disk mount request carries a bare metal server identifier and a cloud hard disk identifier;

[0024] A request forwarding module is used to find the bare metal server address corresponding to the bare metal server identifier, and forward the cloud hard disk mount request to the cloud hard disk mount proxy component deployed on the bare metal server corresponding to the bare metal server address, so that the cloud hard disk mount proxy component mounts the cloud hard disk corresponding to the cloud hard disk identifier to the bare metal server;

[0025] The message processing module is used to receive the mounting result fed back by the cloud hard disk mounting agent component, and feed back the mounting result to the management and control platform.

[0026] In a fourth aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps in any one of the above-mentioned methods for mounting a cloud hard disk on a bare metal server are implemented.

[0027] In a fifth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps in an embodiment of a method for mounting a cloud hard disk on a bare metal server.

[0028] In a sixth aspect, the present application further provides a computer program product, including a computer program, which, when executed by a processor, implements the steps in an embodiment of a method for mounting a cloud hard disk on a bare metal server.

[0029] The above-mentioned method, device, distributed management system, computer equipment, computer-readable storage medium and computer program product for mounting a cloud hard disk on a bare metal server, by creating a virtual private cloud terminal node in the tenant's virtual private cloud, connects the network of the tenant's virtual private cloud and the iSCSI service node virtual private cloud, so that the iSCSI server and the bare metal server in the tenant's virtual private cloud can communicate through the virtual private cloud terminal node created on the tenant's virtual private cloud, and the virtual private clouds of different tenants are still network isolated, which improves the security of the tenant network. In addition, by deploying a cloud hard disk mounting proxy component on the bare metal server, when the iSCSI server receives a cloud hard disk mounting request issued by the management and control platform, the iSCSI server forwards the cloud hard disk mounting request to the cloud hard disk mounting proxy component, and the cloud hard disk mounting proxy component can automatically mount the cloud hard disk on the bare metal server, reducing the cumbersome steps of manual mounting operations and improving the cloud hard disk mounting efficiency. In summary, the above-mentioned scheme can not only improve the security of the tenant network, but also improve the cloud hard disk mounting efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0031] Figure 1 This is an application environment diagram of a method for mounting a cloud hard disk on a bare metal server in one embodiment;

[0032] Figure 2 A schematic diagram of a process of mounting a cloud hard disk on a bare metal server in one embodiment;

[0033] Figure 3 A schematic diagram of a process of mounting a cloud hard disk on a bare metal server in another embodiment;

[0034] Figure 4 is an architectural diagram of a distributed management system in one embodiment;

[0035] Figure 5 It is an architecture diagram of a distributed management system in another embodiment;

[0036] Figure 6 This is a structural block diagram of a device for mounting a cloud hard disk on a bare metal server in one embodiment;

[0037] Figure 7 It is a structural block diagram of an apparatus for mounting a cloud hard disk on a bare metal server in another embodiment;

[0038] Figure 8 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0039] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0040] The method for mounting a cloud hard disk on a bare metal server provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown in the figure, the management and control platform 102 communicates with the iSCSI server 104 and the bare metal server 106 respectively, and the iSCSI server 104 communicates with the bare metal server 106 in the tenant virtual private cloud through the virtual private cloud terminal node 108 created on the tenant virtual private cloud. The bare metal server 106 is deployed with an iSCSI agent (hereinafter referred to as the cloud hard disk mounting agent component). The data storage system can be integrated on the iSCSI server 104, or it can be placed on the cloud or other network servers.

[0041] Specifically, an operator may send a cloud hard disk mount request carrying a bare metal server identifier and a cloud hard disk identifier to an iSCSI server 104 through the management and control platform 102. The iSCSI server 104 receives the cloud hard disk mount request, and then searches for a bare metal server address corresponding to the bare metal server identifier based on the bare metal server identifier, and then forwards the cloud hard disk mount request to a cloud hard disk mount proxy component deployed on a bare metal server corresponding to the bare metal server address, so that the cloud hard disk mount proxy component mounts the cloud hard disk corresponding to the cloud hard disk identifier to the bare metal server. The cloud hard disk mount proxy component mounts the cloud hard disk on the bare metal server, and feeds back the mount result to the iSCSI server 104. The iSCSI server 104 feeds back the mount result to the management and control platform 102.

[0042] The control platform 102 may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, IoT devices, and portable wearable devices. IoT devices may be smart speakers, smart TVs, smart air conditioners, smart car devices, projection devices, etc. Portable wearable devices may be smart watches, smart bracelets, head-mounted devices, etc. Head-mounted devices may be virtual reality (VR) devices, augmented reality (AR) devices, smart glasses, etc. The iSCSI server 104 may be an independent physical server, a server cluster or distributed system consisting of multiple physical servers, or a cloud server that provides cloud computing services.

[0043] In an exemplary embodiment, Figure 2 As shown, a method for mounting a cloud hard disk on a bare metal server is provided. Figure 1 The iSCSI server 104 in FIG. 1 is used as an example to illustrate the method, which includes the following steps S200 to S600. Among them:

[0044] S200, receiving a cloud hard disk mount request sent by the management and control platform, where the cloud hard disk mount request carries a bare metal server identifier and a cloud hard disk identifier.

[0045] The management and control platform is the central platform for managing cloud computing resources and services. It is responsible for processing various requests such as creation, deletion, configuration changes, etc. For cloud hard disks, it can issue "create", "delete", "expand", "mount", and "unmount" requests to the iSCSI server.

[0046] A bare metal server is a physical server that runs an operating system directly without a virtualization layer. Tenants have full control over the machine, including the underlying hardware resources. A bare metal server identifier is an identifier used to uniquely identify a bare metal server, including but not limited to an ID (identity) and a device number.

[0047] Tenant Virtual Private Cloud (VPC) provides users with an isolated network environment in which users can define IP address ranges, subnets, routing tables, etc., and VPC is referred to as VPC in the following text. VPC endpoints are nodes created in VPC and used to access services in VPC and implement network communication between bare metal servers and iSCSI servers in VPC.

[0048] The iSCSI server is one end that implements the iSCSI protocol. It is a server deployed in the iSCSI VPC and is used to provide storage resources to other nodes in the network. iSCSI is a standard protocol that allows SCSI commands to be sent over a TCP / IP network, making remote storage devices look like locally connected hard drives. In this embodiment, the iSCSI server includes an iSCSI control end and an iSCSI gateway. Among them, the iSCSI control end is used to receive requests from the control platform, create or delete cloud hard disks in the storage cluster, and create or delete iSCSI Targets on the iSCSI gateway component. The iSCSI gateway is a multi-process service that connects the bare metal server and the storage cluster through the iSCSI Target, receives the iSCSI protocol IO requests issued by the bare metal server, and converts the requests into IO requests of the storage protocol that matches the storage cluster.

[0049] The bare metal server is deployed with an iSCSI agent and a management and control platform agent. The iSCSI agent is used to automatically mount the cloud hard disk, and the management and control platform agent is used to report information to the management and control platform.

[0050] Specifically, the management and control platform agent on the bare metal server reports the bare metal ID and IP information to the management and control platform. At the same time, the iSCSI agent deployed on the bare metal server reports the bare metal ID and IP information to the iSCSI management and control end in the iSCSI server, so that the iSCSI management and control end can identify and locate the specific bare metal instance.

[0051] When a cloud hard disk mount operation is required, the operator will send a cloud hard disk mount request to the iSCSI control end in the iSCSI server through the control platform. The request includes the bare metal server ID to be mounted and the cloud hard disk ID, where the cloud hard disk can be an iSCSI cloud hard disk. After receiving the cloud hard disk mount request, the iSCSI server will verify the validity of the request. After the verification is passed, the request information will be recorded and prepared for the next step of processing.

[0052] S400, search for the bare metal server address corresponding to the bare metal server identifier, and forward the cloud hard disk mount request to the cloud hard disk mount proxy component deployed on the bare metal server corresponding to the bare metal server address, so that the cloud hard disk mount proxy component mounts the cloud hard disk corresponding to the cloud hard disk identifier to the bare metal server.

[0053] In this embodiment, the bare metal server address refers to the bare metal server IP address.

[0054] After the iSCSI control end in the iSCSI server receives the cloud hard disk mount request, it finds the corresponding bare metal server IP address based on the correspondence between the bare metal server ID reported by the iSCSI agent and the bare metal server IP (established through the previous information report), and then sends the cloud hard disk mount request to the bare metal server pointed to by the bare metal server IP address, specifically to the iSCSI agent on the bare metal server. After receiving the cloud hard disk mount instruction, the iSCSI agent uses the iSCSI protocol to try to connect to the target (Target) assigned to the cloud hard disk on the corresponding iSCSI gateway. After successfully establishing the connection, the iSCSI agent will mount the iSCSI cloud hard disk on the bare metal server.

[0055] S600, receiving the mounting result fed back by the cloud hard disk mounting agent component, and feeding back the mounting result to the management and control platform.

[0056] In actual applications, once the iSCSI agent completes the mount operation (whether successful or not), the iSCSI agent will report the mount status to the iSCSI control end. Specifically, the mount result can be sent to the iSCSI control end in the form of a message notification. The mount result includes two results: mount success or mount failure. After receiving the mount result, the iSCSI control end parses the mount result and feeds the mount result back to the control platform to complete the entire cloud hard disk mount process.

[0057] The above-mentioned bare metal server cloud hard disk mounting method connects the network of the tenant virtual private cloud and the iSCSI service node virtual private cloud by creating a virtual private cloud terminal node in the tenant virtual private cloud, so that the iSCSI server and the bare metal server in the tenant virtual private cloud can communicate through the virtual private cloud terminal node created on the tenant virtual private cloud. In addition, the virtual private clouds of different tenants are still network isolated, which improves the security of the tenant network. In addition, by deploying a cloud hard disk mounting proxy component on the bare metal server, when the iSCSI server receives a cloud hard disk mounting request issued by the management and control platform, the iSCSI server forwards the cloud hard disk mounting request to the cloud hard disk mounting proxy component. The cloud hard disk mounting proxy component can automatically mount the cloud hard disk to the bare metal server, reducing the tedious steps of manual mounting operations and improving the cloud hard disk mounting efficiency. In summary, the above-mentioned scheme can not only improve the security of the tenant network, but also improve the cloud hard disk mounting efficiency.

[0058] In some embodiments, a virtual private cloud terminal node service is created on the iSCSI virtual private cloud where the iSCSI server is located, and the virtual private cloud terminal node service is connected to the virtual private cloud terminal node created on the tenant virtual private cloud, so that the tenant virtual private cloud and the iSCSI server can communicate over the network.

[0059] In actual applications, developers can pre-define a VPC endpoint service in the iSCSI service VPC where the iSCSI server is located. This service will allow other VPCs to connect to this iSCSI service through the VPC endpoint. In addition, one or more network interfaces are specified for the service, which will be used to process data traffic from the VPC endpoint.

[0060] Create a VPC endpoint in the tenant VPC and configure the VPC endpoint to connect to the VPC endpoint service in the iSCSI management VPC. In addition, configure appropriate security group rules for the VPC endpoint to allow iSCSI services from specific channels and ensure that the network settings are correct to allow cross-VPC communication. In addition, you can also update the relevant routing table in the tenant VPC and add routing entries pointing to the VPC endpoint so that data packets can be correctly forwarded to the iSCSI service.

[0061] In actual applications, when a bare metal instance in a tenant's VPC needs to access an iSCSI service, it sends a network request, and the tenant's VPC uses the routing table to decide how to forward the request. If the correct routing entry is configured, the request is sent to the VPC endpoint. The VPC endpoint forwards the request directly to the VPC endpoint service in the iSCSI service VPC through a pre-established private connection. After receiving the request, the VPC endpoint service in the iSCSI service VPC forwards the request to the actual iSCSI server according to the configuration. After the iSCSI server processes the request, the response is returned to the bare metal instance in the tenant's VPC through the same path.

[0062] In this embodiment, the above architecture provides secure cross-VPC communication, while also reducing the risk of transmitting data through the public Internet, thereby ensuring data security and privacy.

[0063] In an exemplary embodiment, Figure 3 As shown, the method also includes: S100, receiving identification information and address information of the bare metal server reported by the cloud hard disk mounting agent component on the bare metal server, and storing the identification information and address information of the bare metal server.

[0064] In actual applications, developers deploy an iSCSI agent (cloud disk mount agent component) on the bare metal server. The iSCSI agent processes cloud disk mount requests and communicates with the management and control platform. When a bare metal server is started or configured for the first time, the iSCSI agent is activated. The iSCSI agent first collects relevant information about the bare metal server, including a unique identifier (such as the bare metal server ID) and a network address (such as an IP address). The iSCSI agent reports a message containing server identification information and address information to the iSCSI management and control end in the iSCSI server through a secure channel.

[0065] After receiving the information reported by the iSCSI agent, the iSCSI control end first verifies the validity and integrity of the data, checks whether the data conforms to the expected format, and confirms the legitimacy of the bare metal server identification and address information. If the data verification is successful, the iSCSI control end will store the data.

[0066] In this embodiment, the cloud hard disk mounting agent component reports the identification information and address information of the bare metal server to the iSCSI control end, which enables the iSCSI control end to obtain and store the key information of the bare metal server in a timely manner, thereby providing support for the automatic mounting of the cloud hard disk.

[0067] In some embodiments, the method further includes: in response to a cloud hard disk creation message sent by the management and control platform, creating a cloud hard disk in the storage cluster, creating an iSCSI target on the iSCSI gateway, and associating the iSCSI target with the hard disk information of the created cloud hard disk.

[0068] In this embodiment, the storage cluster communicates with the iSCSI server, and the iSCSI gateway is responsible for exposing storage resources to the client through the iSCSI protocol.

[0069] In specific implementation, the operator can use the automated script to send a request to create a cloud hard disk to the control platform through the interface. The cloud hard disk creation request contains necessary parameters, such as hard disk size, performance requirements, etc. After receiving the cloud hard disk creation request, the control platform verifies the validity of the request. After the validity verification is passed, it sends a cloud hard disk creation instruction to the iSCSI control end. After receiving the cloud hard disk creation instruction, the iSCSI control end sends a cloud hard disk creation instruction to the storage cluster. The storage cluster responds to the instruction and performs the actual hard disk creation operation, which specifically includes allocating the necessary storage space according to the parameters in the request and creating a new logical volume or partition. Once the hard disk is created, the storage cluster will generate a unique identifier and other related information (such as capacity, location, etc.) for the hard disk. The storage cluster returns the successfully created hard disk information to the iSCSI control end, including the hard disk's unique identifier and related attributes. After receiving the hard disk information returned by the storage cluster, the iSCSI control end continues the next step and sends a request to create an iSCSI target to the iSCSI gateway. The request contains the hard disk information obtained from the storage cluster. After receiving the request, the iSCSI gateway creates a new iSCSI target in its configuration. This target will be associated with the hard disk in the storage cluster. The iSCSI gateway configures the necessary parameters such as LUN mapping for the newly created target, and returns the information of the newly created iSCSI target to the iSCSI control end. The iSCSI control end associates the iSCSI target information with the previously created cloud hard disk information, and stores this information in its database or persistent storage. Then, it updates the status of the cloud hard disk and marks it as created. If users need to mount the cloud hard disk in the future, they can send a cloud hard disk mount request to the iSCSI control end through the control platform.

[0070] In this embodiment, the iSCSI control end can efficiently complete the creation of the cloud hard disk by coordinating the storage cluster and the iSCSI gateway. This process is conducive to the rapid deployment and efficient management of the cloud hard disk.

[0071] Based on the same inventive concept, Figure 4 As shown, the present application also provides a distributed management system, which includes: a management and control platform 402, an iSCSI server 404 and a bare metal server 406.

[0072] Among them, a virtual private cloud terminal node service is created on the iSCSI virtual private cloud where the iSCSI server 404 is located. The virtual private cloud terminal node service is connected to the virtual private cloud terminal node created on the tenant virtual private cloud, so that the tenant virtual private cloud can communicate with the iSCSI server over the network. Multiple bare metal servers are deployed on the tenant virtual private cloud.

[0073] The bare metal server 406 is used to report the identification information and address information of the bare metal server to the management and control platform and the iSCSI server.

[0074] The management and control platform 402 is used to store the identification information and address information of the bare metal server, and send a cloud hard disk mount request carrying the bare metal server identification and the cloud hard disk identification to the iSCSI server.

[0075] iSCSI server 404 is used to find the bare metal server address corresponding to the bare metal server identifier, forward the cloud hard disk mount request to the cloud hard disk mount proxy component deployed on the bare metal server corresponding to the bare metal server address, so that the cloud hard disk mount proxy component mounts the cloud hard disk corresponding to the cloud hard disk identifier to the bare metal server, receives the mount result feedback from the cloud hard disk mount proxy component, and feeds back the mount result to the management and control platform.

[0076] In this embodiment, a VPC terminal node service is created in the iSCSI service VPC where the iSCSI server is located. This service will allow other VPCs to connect to this iSCSI service through the VPC terminal node. A VPC terminal node is created in the tenant VPC, and the VPC terminal node is configured to connect to the VPC terminal node service in the iSCSI control VPC to achieve cross-VPC communication. The specific process of achieving network intercommunication is referred to the above embodiment, which will not be repeated here.

[0077] The bare metal server is deployed with an iSCSI agent and a control platform agent. The iSCSI agent is used to automatically mount the cloud hard disk, and the control platform agent is used to report information to the control platform. When a bare metal server is started or configured for the first time, the iSCSI agent will be activated. The iSCSI agent first collects relevant information about the bare metal server, including a unique identifier (such as the bare metal server ID) and a network address (such as an IP address). The iSCSI agent reports a message containing server identification information and address information to the iSCSI control end in the iSCSI server through a secure channel. The iSCSI control end stores the bare metal server ID and IP address information.

[0078] When a cloud hard disk mount operation is required, the operator will send a cloud hard disk mount request to the iSCSI control end in the iSCSI server through the control platform. The request includes the bare metal server ID to be mounted and the cloud hard disk ID. After receiving the cloud hard disk mount request, the iSCSI control end will find the corresponding bare metal server IP address based on the bare metal server ID reported by the iSCSI agent and the bare metal server IP correspondence (established through the previous information report), and then send the cloud hard disk mount request to the iSCSIagent on the bare metal server pointed to by the bare metal server IP address. After the iSCSI agent receives the cloud hard disk mount instruction, it will mount the iSCSI cloud hard disk on the bare metal server.

[0079] Once the iSCSI agent completes the mount operation (whether successful or not), the iSCSI agent will report the mount status to the iSCSI control end. Specifically, the mount result can be sent to the iSCSI control end in the form of a message notification. The mount result includes two results: mount success or mount failure. After receiving the mount result, the iSCSI control end parses the mount result and feeds the mount result back to the control platform to complete the entire cloud hard disk mount process.

[0080] In the above-mentioned distributed management system, a virtual private cloud terminal node is created in the tenant virtual private cloud, which connects the network of the tenant virtual private cloud and the iSCSI service node virtual private cloud, so that the iSCSI server and the bare metal server in the tenant virtual private cloud can communicate through the virtual private cloud terminal node created on the tenant virtual private cloud. In addition, the virtual private clouds of different tenants are still network isolated, which improves the security of the tenant network. In addition, by deploying a cloud hard disk mount proxy component on the bare metal server, when the iSCSI server receives a cloud hard disk mount request issued by the management and control platform, the iSCSI server forwards the cloud hard disk mount request to the cloud hard disk mount proxy component, and the cloud hard disk mount proxy component can automatically mount the cloud hard disk to the bare metal server, reducing the tedious steps of manual mounting operations and improving the cloud hard disk mount efficiency. In summary, the above-mentioned solution can not only improve the security of the tenant network, but also improve the cloud hard disk mount efficiency.

[0081] In an exemplary embodiment, Figure 5 As shown, the system also includes a storage cluster 408 , and the iSCSI server 404 includes an iSCSI gateway 424 and an iSCSI management and control component 444 . The storage cluster 408 communicates with the iSCSI server 404 through the iSCSI gateway 424 .

[0082] A storage cluster consists of multiple storage nodes that work together to provide high availability, scalability, and performance, capable of handling large amounts of data storage requirements and providing reliable data access services.

[0083] The iSCSI gateway is a multi-process service that connects the bare metal service and storage cluster through the iSCSI Target, receives the iSCSI protocol IO requests sent by the bare metal server, and converts the requests into IO requests of the storage protocol that matches the storage cluster.

[0084] In some embodiments, the iSCSI server is also used to respond to the cloud hard disk creation message sent by the management and control platform, create a cloud hard disk in the storage cluster, create an iSCSI target on the iSCSI gateway, and associate the iSCSI target with the hard disk information of the created cloud hard disk.

[0085] The operator can use the automated script to send a request to create a cloud hard disk to the control platform through the interface. The cloud hard disk creation request contains necessary parameters, such as hard disk size, performance requirements, etc. After receiving the cloud hard disk creation request, the control platform verifies the validity of the request. After the validity verification is passed, it sends a cloud hard disk creation instruction to the iSCSI control end. After receiving the cloud hard disk creation instruction, the iSCSI control end sends a cloud hard disk creation instruction to the storage cluster. The storage cluster responds to the instruction and performs the actual hard disk creation operation, including allocating the necessary storage space according to the parameters in the request and creating a new logical volume or partition. Once the hard disk is created, the storage cluster will generate a unique identifier and other related information (such as capacity, location, etc.) for the hard disk. The storage cluster returns the successfully created hard disk information to the iSCSI control end, including the hard disk's unique identifier and related attributes. After receiving the hard disk information returned by the storage cluster, the iSCSI control end continues the next step and sends a request to create an iSCSI target to the iSCSI gateway. The request contains the hard disk information obtained from the storage cluster. After receiving the request, the iSCSI gateway creates a new iSCSI target in its configuration. This target will be associated with the hard disk in the storage cluster. The iSCSI gateway configures necessary parameters for the newly created target, such as LUN (Logical Unit Number) mapping, and returns the information of the newly created iSCSI target to the iSCSI control end. The iSCSI control end associates the iSCSI target information with the previously created cloud hard disk information and stores this information in its database or persistent storage.

[0086] In this embodiment, the iSCSI control end can efficiently complete the creation of the cloud hard disk by coordinating the storage cluster and the iSCSI gateway. This process is conducive to the rapid deployment and efficient management of the cloud hard disk.

[0087] It is understandable that in other embodiments, if the user needs to delete, expand or uninstall the cloud hard disk, the user can send a corresponding request to the iSCSI control end through the control platform. Similarly, the iSCSI control end can implement operations such as deleting, expanding or uninstalling the cloud hard disk in the same way as mounting the cloud hard disk. For the specific process, please refer to the process of mounting the cloud hard disk in the above embodiment.

[0088] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0089] Based on the same inventive concept, the embodiment of the present application also provides a device for mounting a cloud hard disk on a bare metal server for implementing the method for mounting a cloud hard disk on a bare metal server involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations of the embodiments of the device for mounting a cloud hard disk on one or more bare metal servers provided below can refer to the limitations of the method for mounting a cloud hard disk on a bare metal server above, and will not be repeated here.

[0090] In an exemplary embodiment, Figure 6 As shown, a device 600 for mounting a cloud hard disk on a bare metal server is provided, which is applied to an iSCSI server. The iSCSI server communicates with the bare metal server in the tenant's virtual private cloud through a virtual private cloud terminal node created on the tenant's virtual private cloud. The device includes:

[0091] The request receiving module 610 is used to receive a cloud hard disk mount request sent by the management and control platform. The cloud hard disk mount request carries a bare metal server identifier and a cloud hard disk identifier.

[0092] The request forwarding module 620 is used to find the bare metal server address corresponding to the bare metal server identifier, and forward the cloud hard disk mount request to the cloud hard disk mount proxy component deployed on the bare metal server corresponding to the bare metal server address, so that the cloud hard disk mount proxy component mounts the cloud hard disk corresponding to the cloud hard disk identifier to the bare metal server.

[0093] The message processing module 630 is used to receive the mounting result fed back by the cloud hard disk mounting agent component and feed back the mounting result to the management and control platform.

[0094] like Figure 7 As shown, in some embodiments, the device also includes a data receiving module 602, which is used to receive the identification information and address information of the bare metal server reported by the cloud hard disk mounting agent component, and store the identification information and address information of the bare metal server.

[0095] In some embodiments, the device also includes a cloud hard disk creation module 604, which is used to respond to the cloud hard disk creation message sent by the management and control platform, create a cloud hard disk in the storage cluster, create an iSCSI target on the iSCSI gateway, and associate the iSCSI target with the hard disk information of the created cloud hard disk.

[0096] Each module in the above-mentioned bare metal server mounting cloud hard disk device can be implemented in whole or in part by software, hardware and their combination. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory in the computer device in the form of software, so that the processor can call and execute the corresponding operations of each of the above modules.

[0097] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 8 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data such as bare metal server identification data and cloud hard disk information. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for mounting a cloud hard disk on a bare metal server is implemented.

[0098] Those skilled in the art will understand that Figure 8The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0099] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the steps in any of the above-mentioned methods for mounting a cloud hard disk on a bare metal server are implemented.

[0100] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in any of the above-mentioned methods for mounting a cloud hard disk on a bare metal server are implemented.

[0101] In one embodiment, a computer program product is provided, including a computer program, which, when executed by a processor, implements the steps in any of the above-mentioned methods for mounting a cloud hard disk on a bare metal server.

[0102] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0103] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0104] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0105] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A method for mounting a cloud hard disk on a bare metal server, characterized in that: Applied to an iSCSI server, the iSCSI server communicates with a bare metal server in a tenant virtual private cloud through a virtual private cloud terminal node created on the tenant virtual private cloud, the method comprising: Receive a cloud hard disk mount request sent by the management and control platform, where the cloud hard disk mount request carries a bare metal server identifier and a cloud hard disk identifier; Find the bare metal server address corresponding to the bare metal server identifier, and forward the cloud hard disk mount request to the cloud hard disk mount proxy component deployed on the bare metal server corresponding to the bare metal server address, so that the cloud hard disk mount proxy component mounts the cloud hard disk corresponding to the cloud hard disk identifier to the bare metal server; Receive the mounting result fed back by the cloud hard disk mounting agent component, and feed back the mounting result to the management and control platform.

2. The method according to claim 1, characterized in that: A virtual private cloud terminal node service is created on the iSCSI virtual private cloud where the iSCSI server is located. The virtual private cloud terminal node service is connected to the virtual private cloud terminal node created on the tenant virtual private cloud, so that the tenant virtual private cloud and the iSCSI server can perform network communication.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: Receiving identification information and address information of the bare metal server reported by the cloud hard disk mounting agent component; The identification information and address information of the bare metal server are stored.

4. The method according to claim 3, characterized in that: The iSCSI server includes an iSCSI gateway; the method further includes: In response to the cloud hard disk creation message sent by the management and control platform, create a cloud hard disk in the storage cluster; An iSCSI target is created on the iSCSI gateway, and the iSCSI target is associated with the hard disk information of the created cloud hard disk.

5. A distributed management system, characterized in that: The system includes: a management and control platform, an iSCSI server and a bare metal server, a virtual private cloud terminal node service is created on the iSCSI virtual private cloud where the iSCSI server is located, the virtual private cloud terminal node service is connected to the virtual private cloud terminal node created on the tenant virtual private cloud, so that the tenant virtual private cloud and the iSCSI server perform network communication, and multiple bare metal servers are deployed on the tenant virtual private cloud; The bare metal server is used to report the identification information and address information of the bare metal server to the management and control platform and the iSCSI server; The management and control platform is used to store the identification information and address information of the bare metal server, and send a cloud hard disk mount request carrying the bare metal server identification and the cloud hard disk identification to the iSCSI server; The iSCSI server is used to find the bare metal server address corresponding to the bare metal server identifier, forward the cloud hard disk mount request to the cloud hard disk mount proxy component deployed on the bare metal server corresponding to the bare metal server address, so that the cloud hard disk mount proxy component mounts the cloud hard disk corresponding to the cloud hard disk identifier to the bare metal server, receives the mount result fed back by the cloud hard disk mount proxy component, and feeds back the mount result to the management and control platform.

6. The system according to claim 5, characterized in that The system also includes a storage cluster, the iSCSI server includes an iSCSI gateway and an iSCSI management and control component, and the storage cluster communicates with the iSCSI server through the iSCSI gateway.

7. The system according to claim 6, characterized in that The iSCSI server is also used to respond to the cloud hard disk creation message sent by the management and control platform, create a cloud hard disk in the storage cluster, create an iSCSI target on the iSCSI gateway, and associate the iSCSI target with the hard disk information of the created cloud hard disk.

8. A device for mounting a cloud hard disk on a bare metal server, characterized in that: Applied to an iSCSI server, the iSCSI server communicates with a bare metal server in a tenant's virtual private cloud through a virtual private cloud terminal node created on the tenant's virtual private cloud; the device comprises: A request receiving module, used to receive a cloud hard disk mount request sent by the management and control platform, wherein the cloud hard disk mount request carries a bare metal server identifier and a cloud hard disk identifier; A request forwarding module is used to find the bare metal server address corresponding to the bare metal server identifier, and forward the cloud hard disk mount request to the cloud hard disk mount proxy component deployed on the bare metal server corresponding to the bare metal server address, so that the cloud hard disk mount proxy component mounts the cloud hard disk corresponding to the cloud hard disk identifier to the bare metal server; The message processing module is used to receive the mounting result fed back by the cloud hard disk mounting agent component, and feed back the mounting result to the management and control platform.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 4 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

Images