CN117938641A - A network address configuration method and computing device - Google Patents

Abstract

The embodiment of the application provides a network address configuration method and computing equipment. The target block device mounted on the BMS comprises the target IP address, so that the BMS can automatically acquire the target IP address from the target block device. In this manner, when the BMS needs to configure a network address, the network address of the BMS can be automatically configured using the target IP address in the target block device. Therefore, the embodiment of the application can automatically acquire the target IP address and automatically configure the target IP address, and has high configuration efficiency compared with manual configuration of the network address. In addition, the embodiment of the application can reduce manual configuration errors by pre-storing the network address, is beneficial to improving the configuration accuracy, reduces the probability of occurrence of network faults of the BMS and improves the user experience.

Description

A network address configuration method and computing device

Technical Field

The present invention relates to the technical field of servers, and in particular to a configuration method and computing device for a network address.

Background technique

A bare metal server (BMS) is a physical server that has the characteristics of flexibility, high-performance computing capabilities comparable to traditional physical machines, and secure physical isolation. Therefore, BMS is increasingly widely used.

During the BMS operation phase, the network address needs to be configured, specifically the Internet Protocol (IP) address, so that the BMS can access the Internet normally through the network address. However, in related solutions, users need to manually configure the network address, which is inefficient and prone to configuration errors, causing BMS network failures and affecting user experience.

Summary of the invention

The embodiments of the present application provide a method and a computing device for configuring a network address, which are used to improve the efficiency of configuring a network address, reduce the configuration error rate, reduce the probability of network failures, and improve user experience.

In a first aspect, an embodiment of the present application provides a method for configuring a network address. The method is applied to a bare metal server BMS, and is characterized in that the method includes:

Get the target block device mounted on the BMS; the target block device carries the target Internet Protocol IP address; configure the network address in the BMS based on the target IP address.

The embodiment of the present application uses a target block device mounted on the BMS, and the target block device includes a target IP address, so that the BMS can automatically obtain the target network address from the target block device. In this way, when the BMS needs to configure the network address, the target network address in the target block device can be used to automatically configure the network address of the BMS. The embodiment of the present application can automatically obtain the target network address and perform automatic configuration, which has high configuration efficiency compared to manual configuration of the network address. In addition, by pre-storing the network address, the embodiment of the present application can reduce manual configuration errors, help improve the configuration accuracy, reduce the probability of network failures of the BMS, and improve the user experience.

In a possible implementation, the target block device includes a preset tag, and the embodiment of the present application can obtain the target block device from at least one block device mounted on the BMS based on the preset tag. In this way, the target block device can be quickly and accurately obtained from the mounted block devices by carrying the preset tag in the target block device.

In another possible implementation, before obtaining the target block device mounted on the BMS, the virtual hard disk mounted on the BMS is obtained, and the target virtual hard disk is obtained from the virtual hard disk. Each virtual hard disk is established based on a block device, and the target virtual hard disk is established based on the target block device. In this way, the target block device is mounted on the BMS through the target virtual hard disk.

In another possible implementation, before obtaining the target virtual hard disk mounted on the BMS, obtain a network configuration file; wherein the network configuration file includes a target IP address; generate an image file corresponding to the network configuration file; wherein the image file includes a preset tag; create a target block device based on the image file, the target block device includes a preset tag; and create a target virtual hard disk based on the target block device. In this way, the target IP address is configured to the network configuration file, and the network configuration file is used to construct an image file and a target block device with a preset tag.

In another possible implementation, a first file and a second file are obtained; wherein the first file is used to store the login password of the BMS management system, and the second file is used to store the identification information of the BMS instance; an image file is generated based on the network configuration file, the first file, and the second file; wherein the image file is an ISO image file including a preset tag. In this way, the network configuration file, the file storing the login password of the BMS management system, and the file storing the identification information of the BMS instance are packaged and configured at the same time, thereby improving the configuration speed.

In another possible implementation, a system cloud disk is created and configured based on the cloud disk configuration parameters in the bare metal instance configuration parameters issued by the cloud management platform; wherein the system cloud disk is used to store the operating system OS to be installed of the BMS; and the operating system OS is installed based on the system cloud disk. Optionally, a virtual network card is created and configured based on the network card configuration parameters in the bare metal instance configuration parameters issued by the cloud management platform. In this way, by customizing the virtual network card or cloud disk configuration through the cloud management platform, a network configuration block device is created in advance and mounted on the BMS Host, so as to realize automatic IP configuration while improving the efficiency of BMS instance issuance and user experience.

Optionally, the network address in the BMS is the network address of the virtual network card, and the network address of the virtual network card is configured based on the target IP address, thereby realizing configuration of the network address in the BMS based on the target IP address.

In another possible implementation, before acquiring the target block device mounted on the BMS, the BMS is restarted in response to a restart instruction of the cloud management platform, so that the target block device mounted on the BMS can be acquired after the restart.

In a second aspect, an embodiment of the present application provides a computing device, the computing device including a first processor, the first processor being configured to:

Obtain a target block device mounted on the BMS; wherein the target block device includes a target IP address; and configure a network address in the BMS based on the target IP address.

In a possible implementation, the target block device includes a preset tag; and the first processor is configured to obtain the target block device from at least one block device mounted on the BMS based on the preset tag.

In another possible implementation, before the first processor is used to obtain the target block device mounted on the BMS, the first processor is also used to: obtain the virtual hard disk mounted on the BMS; wherein each virtual hard disk is established based on the block device; obtain the target virtual hard disk from the virtual hard disk; wherein the target virtual hard disk is established based on the target block device.

In another possible implementation, the computing device further includes a second processor, and before the first processor is used to obtain the target virtual hard disk mounted on the bare metal server BMS, the second processor is used to:

Obtain a network configuration file; wherein the network configuration file includes a target IP address; generate an image file corresponding to the network configuration file; wherein the image file includes a preset tag; create a target block device based on the image file, wherein the target block device includes a preset tag; and create a target virtual hard disk based on the target block device.

In another possible implementation, the second processor is further used to: obtain a first file and a second file; wherein the first file is used to store a login password of the BMS management system, and the second file is used to store identification information of the BMS instance; generate an image file based on the network configuration file, the first file and the second file; wherein the image file is an ISO image file including a preset tag.

Optionally, the second processor is also used to: create and configure a system cloud disk based on the cloud disk configuration parameters in the bare metal instance configuration parameters issued by the cloud management platform; wherein the system cloud disk is used to store the operating system OS to be installed of the BMS; and install the operating system OS based on the system cloud disk.

Optionally, the second processor is further used to: create and configure a virtual network card based on the network card configuration parameters in the bare metal instance configuration parameters issued by the cloud management platform.

In yet another possible implementation, the network address in the BMS is a network address of a virtual network card; and the first processor is configured to configure the network address of the virtual network card based on the target IP address.

In yet another possible implementation, before the first processor is used to obtain the target block device mounted on the BMS, the second device is further used to: restart the BMS in response to a restart instruction of the cloud management platform.

Optionally, the first processor is a central processing unit CPU; the second processor is a data processing unit DPU

In a third aspect, an embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is run on a computer, the computer executes the operating steps of any possible network address configuration method of the first aspect described above.

In a fifth aspect, an embodiment of the present application further provides a computer program product which, when executed on a computer, implements the operating steps of any possible method for configuring a network address in the first aspect.

Any of the network address configuration method computing devices or computer-readable storage media or computer program products provided above are used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods and will not be repeated here.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of an implementation method of manually configuring an IP address;

FIG2 is a flow chart of a method for configuring a network address provided in an embodiment of the present application;

FIG3 is a method for implementing target block device mounting provided in an embodiment of the present application;

FIG4 is a schematic diagram of the structure of a network address configuration system provided in an embodiment of the present application;

FIG5A is a schematic diagram of creating a target block device and a system cloud disk based on a DPU;

FIG5B is a schematic diagram of creating a target block device, a system cloud disk, and a virtual network card based on a DPU;

FIG6 is an interactive diagram of another method for configuring a network address provided in an embodiment of the present application;

FIG7 is a schematic diagram of an interface display of a cloud management platform provided in an embodiment of the present application;

FIG8 is a schematic diagram of a network address configuration device according to an embodiment of the present application;

FIG9 is a schematic diagram of the structure of a computing device provided in an embodiment of the present application.

Detailed ways

The computing device provided in the embodiment of the present application does not specifically limit the application scenario. For example, the computing device is introduced by taking a server as an example, and the type of the server is not specifically limited. For example, the computing device can be a rack server or an edge server. The server can be located in a data center or in other areas, and the embodiment of the present application does not make specific limitations.

Servers are a type of computing device that runs faster and has a higher load than ordinary computers. Servers provide computing or application services to other clients (such as PCs, smartphones, and other devices) in the network. Servers have high-speed CPU computing power, long-term reliable operation, strong external data throughput, and better scalability. Servers are divided into rack-mounted, blade-mounted, tower-mounted, and cabinet-mounted types.

Bare metal server (BMS) is a type of physical server, also known as a bare metal node or a physical machine with a "bare" operating system. It generally refers to a server without an operating system or virtualization software installed. A physical machine with a "bare" operating system can also refer to a physical machine with an operating system installed but no virtualization software installed. BMS is flexible and elastic, has high-performance computing capabilities comparable to traditional physical machines, and features secure physical isolation, so its application is becoming more and more widespread.

In order to achieve normal Internet access, BMS needs to configure the network address after the BMS instance is decentralized. In related solutions, users use the out-of-band management software corresponding to the BMS, such as the server intelligent management software (intelligent baseboard management controller, IBMC) to observe in real time whether the BMS is successfully started. If the startup is successful, the user manually configures the network address for the BMS, specifically the IP address. See Figure 1 for IBMC, which is a schematic diagram of a manual configuration of the IP address.

Figure 1 (a) shows the IBMC login interface. After the user enters the login password in the IBMC login interface, he logs in to the IBMC interface. Figure 1 (b) shows the IBMC interface, which shows whether the BMS instance is successfully started. Figure 1 (b) uses a startup progress bar to show the startup status of the BMS instance. Among them, the BMS instance is started 50%.

(c) in Figure 1 shows the IBMC interface corresponding to the successful startup of the BMS instance. The IBMC interface corresponding to the successful startup of the BMS instance displays a startup success mark, and the user can confirm that the BMS instance has been successfully started through the startup success mark. In addition, the IBMC interface corresponding to (c) in Figure 1 also shows the trigger item corresponding to entering the manual configuration IP address interface. For example, the trigger item can be a "Next" button. When the user clicks the "Next" button, the manual configuration IP address interface is entered. In addition, the IBMC interface is also provided with a "Cancel" button. The user clicks the "Cancel" button to no longer configure the IP address.

(d) in FIG1 shows a schematic diagram of the manual configuration IP address interface. The user can enter the IP address in the manual configuration position and use the input IP address to configure the IP address of the BMS. (d) in FIG1 also shows the configuration completion trigger item, for example, the trigger item is a "Confirm" button, and the user clicks the "Confirm" button to complete the configuration. And the "Cancel" button is shown, and the user clicks the "Cancel" button to reconfigure the IP address.

However, manual configuration of network addresses has low configuration efficiency and is prone to configuration errors, causing network failures of the BMS and affecting user experience.

In view of the above problems, the embodiment of the present application uses a target block device mounted on the BMS, wherein the target block device includes a target network address, so that the BMS can automatically obtain the target IP address from the target block device. In this way, when the BMS needs to configure the network address, the target IP address in the target block device can be used to automatically configure the network address of the BMS. It can be seen that the embodiment of the present application can automatically obtain the target IP address and perform automatic configuration, which has high configuration efficiency compared to manual configuration of the network address. In addition, the embodiment of the present application can reduce manual configuration errors by pre-storing the network address, thereby helping to improve the configuration accuracy, reduce the probability of network failures of the BMS, and improve the user experience.

Embodiment 1

The following provides a detailed and complete description of the embodiments of the present application in conjunction with the accompanying drawings.

See Figure 2, which is a flow chart of a method for configuring a network address provided in an embodiment of the present application. The method is performed by a BMS, specifically a first processor of the BMS. Exemplarily, the first processor may be a central processing unit (CPU) of the BMS. The method includes:

S21: BMS obtains the target block device from the pre-mounted block devices.

The target block device refers to a device that pre-stores the target Internet Protocol IP address. In the embodiment of the present application, the target block device is mounted on the BMS, so that the BMS can directly obtain the target block device from the mounted block device.

Since there may be multiple block devices mounted on the BMS, in order to quickly and accurately obtain the target block device from the mounted block devices, a preset label is added to the target block device mounted on the BMS, and the preset label is used to uniquely identify the target block device.

For example, among the N block devices mounted on the BMS, a preset label cidata is added to the target block device, and no label is added to other block devices. The BMS can quickly obtain the target block device from the N block devices based on the preset label cidata.

For another example, N block devices are mounted on the BMS, and a label is added to each block device. The label added to the block device storing the target IP address is cidata, and the labels added to other block devices are different from cidata. In this way, the BMS can quickly obtain the target block device from the N block devices based on cidata.

The above-mentioned preset tag cidata is only for illustrative purposes. The present application embodiment does not specifically limit the form of the preset tag. For example, the preset tag can be a key content topic of a block device, such as a block device storing network configuration parameters, which can add a network-config tag. The tag can also be the content format of the block device, or a preset identifier can be used as a tag.

It should be noted that the correspondence between the label and the block device needs to be saved in advance on the BMS. In this way, when the BMS obtains the label information, it can quickly obtain the target block device from multiple mounted block devices based on the correspondence between the label and the block device.

The target IP address refers to the IP address that the BMS needs to configure. In the embodiment of the present application, in order for the BMS to access the Internet normally, the target IP address configured by the BMS cannot conflict with the IP addresses of other servers. Other servers are located in the same local area network as the BMS, or other servers share the same network with the BMS.

The embodiment of the present application does not specifically limit the form in which the target IP address exists in the target block device. For example, the target IP address can be written into a network configuration file, and the target block device is formed based on the network configuration file. Or the target IP address is written into a network configuration file, the network configuration file is first packaged into a mirror file, and then the target block device is formed based on the mirror file.

In addition, the embodiment of the present application does not specifically limit the time for acquiring the target block device. For example, the BMS can be automatically triggered to acquire the target block device after the BMS instance is successfully launched. The BMS can also be automatically triggered to acquire the target block device during the restart of the BMS host operating system (Host OS).

S22: Configure the network address of the BMS based on the target network protocol address IP in the target block device.

After the BMS obtains the target block device, it automatically obtains the target IP address from the target block device.

The embodiment of the present application does not specifically limit the method of obtaining the target IP address. Compared with manually inputting the target IP address, the embodiment of the present application is less prone to manual input errors and is faster to obtain. In addition, by pre-ensuring that the target IP address does not conflict with the IP addresses of other servers during storage, the configuration accuracy is further improved.

In one example, the BMS may traverse all information stored in the target block device and obtain the target IP address therefrom.

In another example, consider that there are multiple files in the target block device, such as user data files, network configuration files, etc., and each file has a corresponding network identifier, for example, the identifier of the user data file is user-data, and the identifier of the network configuration file is network-config. In addition, the target IP address is stored in the network configuration file. The BMS can obtain the network configuration file based on the network identifier network-config, and then obtain the target IP address from the network configuration file. Compared with traversing the information in all target block devices, the acquisition efficiency is higher.

In another example, the BMS may call a reading tool to read the target IP address from the target block device. For example, the reading tool may be Cloud-Init. Cloud-Init is a tool developed specifically for initializing virtual machines in a cloud environment, and is used to read relevant data from various data sources when creating a virtual machine startup and customize the virtual machine accordingly.

The BMS configures the IP address using the target IP address.

In some examples, the IP address configured by the BMS is the same as the target IP address. For example, if the target IP address is 70:182:40:116, the IP address configured by the BMS may be 70:182:40:116.

In other examples, the BMS stores a correspondence between a target IP address and an IP address configured by the BMS, and the BMS automatically configures the IP address using the target IP address and the correspondence between the IP addresses.

The embodiment of the present application uses a target block device mounted on the BMS, wherein the target block device includes a target network address, so that the BMS can automatically obtain the target network address from the target block device. In this way, when the BMS needs to configure the network address, the target network address in the target block device can be used to automatically configure the network address of the BMS. It can be seen from this that the embodiment of the present application can automatically obtain the target network address and perform automatic configuration, which has high configuration efficiency compared to manually configuring the network address. In addition, the embodiment of the present application can reduce manual configuration errors by pre-storing the network address, thereby helping to improve the configuration accuracy, reduce the probability of network failures of the BMS, and improve the user experience.

See FIG. 3 , which is a method for implementing target block device mounting provided in an embodiment of the present application. The execution subject of the method is the second processor of the BMS. Exemplarily, the second processor may be a data processor (DPU) of the BMS. The method specifically includes:

S31: Create network configuration related files in the DPU file system.

The network configuration related file refers to at least one file required to configure the IP address of the BMS.

Among them, the network configuration related files include network configuration files, which are used to enable the BMS to configure network address information, such as IP address, gateway address, mask, etc. The BMS obtains the network address configuration information through the network configuration file, and uses the network address configuration information to automatically configure the network address.

This application does not specifically limit the format of the network configuration file. For example, the format of the network configuration file is:

root@localhost:/home? ubuntu/cloud-init#cat network-config

version: 1

config:

type:physical

name:ens9

mac_address: '86:a1:80:de:1e:f7'

subnets:

type:static

address:70:182:40:116

netmask:255.255.255.0

gateway:70.182.40.1

Among them, the network configuration file is identified as network-config, and the version number is 1. In the configuration information, the type is a physical network card, and the name of the network card to be configured is ens9. The media access control (MAC) address of the network card to be configured is 86:a1:80:de:1e:f7. In the subnet information, the subnet type is static, the target IP address, that is, the subnet IP address is 70:182:40:116, the subnet mask is 255.255.255.0, and the subnet gateway is 70.182.40.1.

After the BMS obtains the network configuration file, it can create a network card to be configured according to the corresponding information and configure the subnet network address to enable normal Internet communication of the BMS.

The embodiment of the present application can create network configuration related files in the file system of the DPU and write the target IP address into the network configuration file.

The embodiment of the present application does not specifically limit the writing method. For example, the BMS can overwrite the original IP address with the target IP address based on the writing location corresponding to the target IP address, that is, the address in the above file format. Assume that the target IP address is 70.182.40.11. At this time, the address in the network configuration file is 70:182:40:11.

In addition, network configuration parameter information such as subnet gateway and mask can also be written into the network configuration file.

In an example, the network configuration related files also include but are not limited to the first file and the second file.

The first file is also called the user-data file, which is used to store the login password required to log in to IBMC. BMS can obtain the login password through the first file and automatically connect to IBMC.

The embodiment of the present application does not specifically limit the format of the first file. For example, the format of the first file may be:

root@localhost:/home? ubuntu/cloud-init#cat user-data

#cloud-connect

password:pass

expire:False

password is the default login password. In the example, the default login password is pass. expire indicates whether the user needs to reset the password the next time he logs in. If the content corresponding to expire is the first preset flag, such as the preset flag is False, it means that the password does not need to be reset and the default login will be used next time. If it is the second preset flag, such as empty or True, it means that the password needs to be reset. user-data is the first file identifier. Through user-data, BMS can confirm that the acquired file is the first file. user-data is only an illustrative description, and technicians in this field can adjust it as needed.

The second file user stores the first identity of the instance to be configured, wherein the instance to be configured is the instance required by the BMS.

The cache area caches the instance information being sent and the second identity corresponding to the instance information. To ensure that the instance sent is the instance to be configured, the BMS checks whether the second identity of the cache area is the same as the first identity. If they are the same, the instance cached in the cache area is the instance to be configured. If they are not the same, it means that the instance cached in the cache area is not the instance to be configured, and the cache area needs to reload the configured instance information.

The embodiment of the present application does not specifically limit the format of the second file. For example, the format of the second file is:

root@localhost:/home? ubuntu/cloud-init#cat meta-data

instance-id: id-10.

Wherein, meta-data is the second file identifier, instance-id is the first identity identifier, and the first identity identifier is specifically id-10. meta-data is the second file identifier. Through meta-data, the BMS can confirm that the acquired file is the second file. meta-data is only for illustrative purposes, and those skilled in the art can adjust it as needed.

S32: Generate an image file corresponding to the network configuration related files.

A mirror file is similar to a compressed file, which is used to compress network configuration-related files into a file with a smaller storage space to save storage space.

The embodiment of the present application does not specifically limit the type of the image file, for example, the image file may be an ISO image file, wherein the network configuration-related files in the ISO image file cannot be modified at will, and the security is higher during the transmission and storage process.

In order to facilitate the subsequent identification of the image file, the image file carries a preset tag, for example, the preset tag is a cidata tag. That is, the network configuration related file is converted into an image file, and the image file is added with a preset tag. Through the preset tag, the image file corresponding to the network configuration related file can be quickly obtained.

The embodiment of the present application does not specifically limit the method of generating the image file.

In one example, in the local disk, click on the network configuration-related file to be added. After adding the network configuration-related file to the disc, click on the disc name under the disc directory to rename the newly added network configuration-related file to a preset label. Convert the network configuration-related file to an image file by saving the image file type as. For example, rename the network configuration-related file to cidata, and save it as ISO to successfully output the network configuration-related file to an ISO image file with the cidata label.

In another example, the DPU may use a production tool to produce network configuration related files into an image file with a preset tag, such as using a genisoimage tool to package the network configuration related files into an ISO image file with a cidata tag.

S33: The DPU generates a target block device based on the image file.

A block device is a storage device that supports reading and writing data in fixed-size blocks. A target block device is a block device to which the image file is written as blocks.

The embodiment of the present application generates a target block device based on an image file. Optionally, the target block device has the same label as the image file. For example, the image file is an ISO image file with a cidata label, and the generated target block device has a cidata label, for example, the target block device is a bdev device with a cidata label.

The purpose of creating a target block device in the embodiment of the present application is to use the target block device to create a virtual hard disk and mount network configuration information such as the target IP address on the BMS.

S34: Create a virtual hard disk based on the target block device.

In an embodiment of the present application, a virtual hard disk is created based on the target block device. After the BMS is restarted, the basic input output system (BIOS) mounts the virtual hard disk on the BMS. The BMS can obtain the target block device based on the mounted virtual hard disk, and obtain other network configuration information such as the target IP address from the target block device.

The embodiment of the present application does not specifically limit the BMS restart method. For example, the cloud management platform issues a restart instruction to restart the BMS operating system.

The embodiment of the present application does not specifically limit the type of virtual hard disk, for example, the virtual hard disk is implemented through virtio-blk. Virtio-blk is an implementation method of virtual hard disk under the virtualized KVM platform, which is essentially a semi-simulation technology. The virtio-blk device uses io_event_fd for front-end to back-end notification, uses interrupt injection to implement back-end to front-end notification, and shares data through the IO ring (vring).

The embodiment of the present application does not specifically limit the method of creating a virtual hard disk. For example, a storage performance development kit (SPDK) may be used to create a virtual hard disk.

The embodiment of the present application creates a network configuration-related file in the DPU file system, generates an ISO image file of the network configuration-related file, generates a target block device based on the ISO image file, and creates a virtual hard disk based on the target block device, thereby mounting the target block device including the target IP address on the BMS. The BMS can obtain the target IP address based on the mounted target block device and configure the IP address.

Embodiment 2

Furthermore, the current BMS instance issuance process is as follows: the cloud management platform schedules the bare metal, and then controls the bare metal to execute the preboot execute environment (PXE) to start. Next, the bare metal loads the downloaded Mini OS into the bare metal's memory by accessing the trivial file transfer protocol (TFTP) service, and downloads the OS image to be installed to the local hard disk by accessing the image service; finally, the cloud management platform or IBMC controls the bare metal to start from the local hard disk. Since the entire bare metal server issuance process requires starting the bare metal twice and downloading the image, the bare metal server issuance process takes a long time, resulting in low efficiency in BMS instance issuance.

In view of the above problems, the embodiment of the present application also provides another method for configuring the network address. This method customizes the virtual network card and cloud disk configuration based on the cloud management platform, uses the DPU to pre-create the network configuration block device and mount it on the BMS host, so as to realize automatic IP configuration, improve the efficiency of BMS instance distribution, and enhance the user experience.

See Figure 4, which is a schematic diagram of the BMS structure corresponding to a method for configuring a network address provided in an embodiment of the present application. The BMS includes a first processor and a second processor. Specifically, the first processor is a CPU, and the second processor is a DPU. The CPU communicates data with the DPU.

It should be noted that the DPU is a special processor with a data-centric structure. In the embodiment of the present application, the DPU creates a block device in advance and mounts the created block device on the BMS, so that the BMS can access the block device.

The CPU can obtain the block device and configure the corresponding IP address of the BMS according to the IP address included in the block device, so that the BMS can communicate with the Internet normally.

The embodiment of the present application does not specifically limit the data communication method between the CPU and the DPU. For example, the CPU communicates with the DPU via the peripheral component interconnect express (PCIE) PCIE, etc.

The embodiment of the present application does not specifically limit the type of DPU. For example, the DPU may be a PCIE smart network card.

As shown in FIG. 5A , this figure is a schematic diagram of creating a target block device and a system cloud disk based on a DPU.

S1: Create a system cloud disk.

The DPU obtains the cloud disk configuration parameters and uses them to create a system cloud disk.

Cloud disk configuration parameters refer to the parameters for configuring the system cloud disk, including but not limited to the maximum capacity, maximum throughput, and maximum input/output per second (IOPS) of the cloud disk.

The DPU can obtain cloud disk configuration parameters in a variety of ways.

For example, the DPU is connected to a cloud management platform, and the user can directly input cloud disk configuration parameters through the cloud management platform. Or the cloud management platform stores cloud disk configuration parameters and preset trigger rules, and the DPU can directly read cloud disk configuration parameters from the cloud management platform based on the preset trigger rules.

The system cloud disk is a network storage tool dedicated to storage, and the system cloud disk can specifically be a virtual hard disk. The system cloud disk created in the embodiment of the present application can be the same as the cloud disk configuration parameters, or can have a corresponding relationship with the cloud disk configuration parameters.

For example, the maximum capacity of the cloud disk configuration parameter is 32TB, and the maximum capacity of the system cloud disk is configured as 32TB.

For another example, the mapping relationship between DPU storage and cloud disk configuration parameters and system cloud disk parameters, assuming that half of the mapping relationship is the system cloud disk parameters. If the maximum capacity of the cloud disk configuration parameters is 32TB, based on the above mapping relationship, the maximum capacity of the system cloud disk is configured to be 16TB.

The operating system program to be installed is stored in the system cloud disk. The operating system program to be installed includes a BMS image startup program for implementing the BMS image startup.

S2: Create a virtual hard disk.

The specific creation method is shown in Figure 3 and will not be discussed here.

The embodiment of the present application does not specifically limit the execution order of S1 and S2. S1 may be executed first and then S2, or S2 may be executed first and then S1, or they may be performed simultaneously.

Optionally, the DPU can also create a virtual network card, and the CPU of the BMS configures the target IP address to the virtual network card.

See Figure 5B, which is a schematic diagram of creating a target block device, a system cloud disk, and a virtual network card based on the DPU.

Compared with FIG. 5A , a process of creating a virtual network card is added.

S3: Create a virtual network card. The DPU obtains the network card configuration parameters and uses them to create a virtual network card. When the BMS goes online, it can communicate online based on the pre-created virtual network card.

The network card configuration parameters are used to configure the network card. The network card configuration parameters include but are not limited to the network card type, the MAC address corresponding to the network card, the subnet type, the subnet mask, the IP address, and the gateway. For example, the network card configuration parameters are as follows:

type:physical

name:ens9

mac_address: '86:a1:80:de:1e:f7'

subnets:

type:static

address:70:182:40:116

netmask:255.255.255.0

gateway:70.182.40.1

The configuration of the virtual network card created at this time is: type is static, target IP address is 70:182:40:116, subnet mask is 255.255.255.0, and gateway is 70.182.40.1.

The embodiment of the present application does not specifically limit the implementation of the virtual network card, for example, it can be virtio-Net. Virtio-Net is an implementation of the virtual network card under the virtualized KVM platform, and is also a network card device in the virtio standard and is widely used.

The DPU can obtain network card configuration parameters in multiple ways.

For example, the DPU is connected to a cloud management platform, and the user can directly input the network card configuration parameters through the cloud management platform. Or the cloud management platform stores the network card configuration parameters and preset trigger rules, and the DPU can directly read the network card configuration parameters from the cloud management platform based on the preset trigger rules.

See Figure 6, which is an interactive diagram of a network address configuration method provided in an embodiment of the present application. The method uses a cloud management platform to create a customized bare metal instance, sends virtual network card and cloud disk configuration parameters to DPU_agent, and implements bare metal instance distribution creation and IP configuration through DPU and CPU. The method specifically includes:

S61: Configure bare metal instance configuration parameters on the cloud management platform.

Bare metal instance configuration parameters are the parameters required to configure a bare metal instance.

In the embodiment of the present application, the bare metal instance configuration parameters may include hard disk size, hard disk type and other parameters. In addition, the bare metal instance configuration parameters also include network card configuration parameters and cloud disk configuration parameters. The DPU may create a virtual network card according to the network card configuration parameters, and create a system cloud disk according to the cloud disk configuration parameters.

The embodiments of the present application do not specifically limit the implementation method in which the user sends the bare metal instance configuration parameters through the cloud management platform.

See Figure 7, which is a schematic diagram of the interface display of a cloud management platform provided in an embodiment of the present application.

(a) in FIG7 shows a bare metal instance configuration parameter interface, where the user can manually input bare metal instance configuration parameters at a specified position 701 of the bare metal instance configuration parameter interface. In addition, the user can also trigger the cloud management platform to obtain bare metal instance configuration parameters from a pre-stored bare metal instance configuration parameter area in other ways.

S62: The cloud management platform service sends the network card configuration parameters to the DPU.

In the embodiment of the present application, after the cloud management platform obtains the network card configuration parameters, it sends the network card configuration parameters to the DPU. Specifically, it sends them to the DPU Agent. The DPU Agent is an intermediate service deployed on the DPU OS, which is used to receive requests from the cloud management platform, create virtual network cards and virtual hard disk devices, and provide them to the BMS for use.

S63: The DPU creates a virtual network card according to the network card configuration parameters.

S64: The DPU returns the virtual network card creation result to the cloud management platform.

The DPU returns the network card creation result to the cloud management platform. The cloud management platform determines whether the virtual network card is successfully created based on the network card creation result.

In one example, the network card creation result includes a creation success identifier. The cloud management platform can determine that the virtual network card is successfully created according to the creation success identifier.

In another example, the network card creation result includes network card configuration parameters, such as IP address, subnet gateway, and subnet mask. The cloud management platform compares the network card configuration parameters returned by the DPU with the network card configuration parameters sent to the DPU. If the two are consistent, the cloud management platform displays a virtual network card creation success mark. Otherwise, the cloud management platform displays a virtual network card creation failure mark.

S65: DPU configures user-data, meta-data, and network-config files.

In the embodiment of the present application, the DPU does not initially contain user-data, meta-data, and network-config files. The DPU first creates user-data, meta-data, and network-config files. Specifically, they can be created on the DPU file system.

For example, the created user-data file is:

root@localhost:/home? ubuntu/cloud-init#cat user-data

#cloud-connect

password:pass

expire:False

The created meta-data file is:

root@localhost:/home? ubuntu/cloud-init#cat meta-data

instance-id: id-10.

The network-config file created is:

root@localhost:/home? ubuntu/cloud-init#cat network-config

version: 1

config:

type:physical

name:ens9

mac_address: '86:a1:80:de:1e:f7'

subnets:

type:static

address:

netmask:

gateway:

The DPU configures the network file based on the network card configuration parameters. For example, the subnet IP address is 70:182:40:116, the subnet mask is 255.255.255.0, and the subnet gateway is 70.182.40.1.

The configured network-config file is:

root@localhost:/home? ubuntu/cloud-init#cat network-config

version: 1

config:

type:physical

name:ens9

mac_address: '86:a1:80:de:1e:f7'

subnets:

type:static

address:70:182:40:116

netmask:255.255.255.0

gateway:70.182.40.1

S66: The DPU creates an ISO image file, creates a target block device based on the ISO image file, and creates a target virtual hard disk based on the target block device.

The DPU uses the genisoimage tool to package the user-data, meta-data, and network-config files into an ISO image file identified as cidata. It also creates a target block device based on the ISO image file identified as cidata, namely, a bdev device identified as cidata.

Finally, a virtual hard disk is created based on the bdev device identified as cidata. In this way, when the BMS is restarted, the target block device can be mounted to the BMS instance to display the target block device on the BMS.

S67: The cloud management platform sends cloud disk configuration parameters to the DPU.

The cloud management platform obtains the cloud disk configuration parameters from the bare metal instance configuration parameters and sends them to the DPU.

S68: DPU creates a system cloud disk.

After receiving the cloud disk configuration parameters, the DPU creates a system cloud disk based on the cloud disk configuration parameters and a third correspondence between the cloud disk configuration parameters and the system cloud disk pre-stored by the DPU.

S69: The DPU returns the cloud disk configuration result to the cloud management platform.

After the creation is complete, the DPU returns the cloud disk configuration result to the cloud management platform. The cloud management platform determines whether the system cloud disk is configured successfully based on the cloud disk configuration result.

In one example, the cloud disk configuration result includes a creation success identifier. The cloud management platform can determine that the creation is successful based on the creation success identifier.

In another example, the cloud disk configuration result includes cloud disk configuration parameters. The cloud management platform compares the cloud disk configuration parameters returned by the DPU with the cloud disk configuration parameters sent to the DPU. If the two are consistent, the cloud management platform displays a configuration success mark. Otherwise, the cloud management platform displays a configuration failure mark.

S610: The cloud management platform triggers the restart of the BMS operating system.

After the cloud management platform completes the creation of the virtual network card and system cloud disk, it calls the IBMC interface to send a command to restart the BMSHost OS.

S611: The CPU determines a target block device.

The BMS restarts, triggering the BMC to search for the target block device. In the embodiment of the present application, the BMC uses Cloud Init to search for block devices with the cidata tag by traversal.

S612: The CPU reads the network configuration file and completes the IP address configuration.

After the CPU obtains the block device with the cidata tag, it reads the internal network configuration file and uses Cloud Init to search for the network configuration file by traversal.

The CPU can complete the IP address configuration based on the read network address configuration file.

In one example, the BMC directly configures the IP address using the target IP address of the network address configuration file.

For example, if the target IP address in the network address configuration file is 70:182:40:116, the configured IP address is 70:182:40:116.

The embodiments of the present application do not specifically limit the implementation method of IP address configuration.

S613: The cloud management platform periodically uses the connection instruction to connect to the BMS instance.

In the embodiment of the present application, the cloud management platform can connect to the BMS instance through a connection instruction at preset time intervals.

The preset time interval may be 1ms, 2ms, etc., which is not specifically limited in this application.

The connection instruction may specifically be a ping instruction. For example, you may use ping+configured IP address to connect to the BMS instance.

S614: In response to the successful connection, the cloud management platform feeds back a successful creation indicator to the user.

If the connection command is successful, the cloud management platform will feedback to the user the successful creation of the BMS instance.

As shown in FIG. 7 , (b) in FIG. 7 shows a sign indicating that the BMS instance is successfully created.

In this way, the embodiment of the present application implements BMS instance creation and IP configuration through the interaction between the DPU and the CPU.

The embodiment of the present application provides a method for automatic IP configuration, which solves the problem that the traditional bare metal virtual network card needs to manually configure the IP. In addition, the embodiment of the present application allows users to perceive in real time whether the bare metal instance is successfully deployed through the bare metal management platform, allowing users to quickly perceive the status of the bare metal instance in real time, greatly improving the user experience. In addition, the embodiment of the present application uses the cloud management platform to create a customized bare metal instance, sends the virtual network card and cloud disk configuration parameters to the DPU_agent, and realizes the rapid distribution of bare metal instances and the rapid configuration of IP through the DPU.

In addition, an embodiment of the present application also provides a device for configuring a network address.

See Figure 8, which is a schematic diagram of a network address configuration device according to an embodiment of the present application. The configuration device specifically includes:

The acquisition unit 801 is used to acquire the target block device mounted on the BMS; wherein the target block device includes a target Internet Protocol IP address; the configuration unit 802 is used to configure the network address in the BMS based on the target IP address.

In a possible implementation, the target block device includes a preset tag. The acquisition unit 801 is specifically configured to: acquire the target block device from at least one block device mounted on the BMS based on the preset tag.

In another possible implementation, the configuration device also includes: a mounting unit 803, and the mounting unit 803 is specifically used to: obtain a virtual hard disk mounted on the BMS; wherein each virtual hard disk is established based on a block device; obtain a target virtual hard disk from the virtual hard disk; wherein the target virtual hard disk is established based on the target block device.

Optionally, the mounting unit 803 is further used for:

Obtain a network configuration file; wherein the network configuration file includes the target IP address; generate an image file corresponding to the network configuration file; wherein the image file includes a preset tag; create the target block device based on the image file, the target block device includes the preset tag; and create the target virtual hard disk based on the target block device.

In another possible implementation, the configuration device further includes an image file generating unit 804, and the image file generating unit 804 is specifically used to:

Obtain a first file and a second file; wherein the first file is used to store a login password of the management system of the BMS, and the second file is used to store identification information of the BMS instance; generate the image file based on the network configuration file, the first file and the second file; wherein the image file is an ISO image file including the preset tag.

Optionally, the configuration device further includes a creation unit 805. The creation unit 805 is further used to: create and configure a system cloud disk based on the cloud disk configuration parameters in the bare metal instance configuration parameters issued by the cloud management platform; wherein the system cloud disk is used to store the operating system OS to be installed of the BMS; and install the operating system OS based on the system cloud disk.

Optionally, the creation unit 805 is further used to create and configure a virtual network card based on the network card configuration parameters in the bare metal instance configuration parameters sent by the cloud management platform.

Optionally, the network address in the BMS is the network address of the virtual network card;

The configuration unit 802 is used to configure the network address of the virtual network card based on the target IP address.

Optionally, the configuration device further includes a restart unit 806, which is specifically configured to restart the BMS in response to a restart instruction of the cloud management platform.

The configuration device provided in the embodiment of the present application, through the target block device mounted on the BMS, wherein the target block device includes a target IP address, can enable the BMS to automatically obtain the target IP address from the target block device. In this way, when the BMS needs to configure the network address, the target IP address in the target block device can be used to automatically configure the network address of the BMS. It can be seen that the embodiment of the present application can automatically obtain the target IP address and perform automatic configuration, and the configuration efficiency is high compared to manual configuration of the network address. In addition, the embodiment of the present application can reduce manual configuration errors by pre-storing the network address, thereby helping to improve the configuration accuracy, reduce the probability of network failures of the BMS, and improve the user experience.

As shown in Figure 9, an embodiment of the present application also provides a computing device 900, including a first processor 901, a second processor 902 and a memory 903, the memory 903 is electrically connected to the first processor 901 and the second processor 902 respectively; the memory 903 is used to store program instructions, and the program instructions are used for the network address configuration method involved in the above-mentioned embodiments; the first processor 901 and the second processor 902 are used to call the corresponding parts of the above-mentioned program instructions so that the computing device can execute the network address configuration method involved in the above-mentioned embodiments.

An embodiment of the present application also provides a computer-readable storage medium on which computer instructions are stored. When the computer instructions are executed on a computing device, the computing device executes the network address configuration method involved in the above embodiments.

For the explanation of the relevant contents and description of the beneficial effects in any of the above-mentioned computer-readable storage media, reference may be made to the above-mentioned corresponding embodiments, which will not be repeated here.

An embodiment of the present application provides a computer program product, which, when executed on a computer, enables the computer to execute the network address configuration method involved in the above embodiments.

In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using a software program, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions in the embodiments of the present application are generated.

The computer may be a bare metal server. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (e.g., a floppy disk, a magnetic disk, a magnetic tape), an optical medium (e.g., a digital video disc (DVD)), or a semiconductor medium (e.g., a solid state drive (SSD)), etc.

The above is only a preferred embodiment of the present application and does not constitute any formal limitation to the present application. Although the present application has been disclosed as above with a preferred embodiment, it is not intended to limit the present application. Any technician familiar with the art can make many possible changes and modifications to the technical solution of the present application using the methods and technical contents disclosed above without departing from the scope of the technical solution of the present application, or modify it into an equivalent embodiment of equivalent changes. Therefore, any simple modification, equivalent change and modification made to the above embodiments based on the technical essence of the present application without departing from the content of the technical solution of the present application still falls within the scope of protection of the technical solution of the present application.

Claims (19)

1. A method for configuring a network address, the method being applied to a bare metal server BMS, the method comprising:

Acquiring target block equipment mounted on the BMS; wherein the target block device carries a target internet protocol IP address;

And configuring a network address in the BMS based on the target IP address.

2. The method of claim 1, wherein the target block device comprises a preset tag;

The obtaining the target block device mounted on the BMS includes:

and acquiring the target block device from at least one block device mounted on the BMS based on the preset tag.

3. The method according to claim 1 or 2, wherein before acquiring the target block device mounted on the BMS, the method further comprises:

acquiring a virtual hard disk mounted on the BMS; wherein each virtual hard disk is built based on block equipment;

obtaining a target virtual hard disk from the virtual hard disk; the target virtual hard disk is established based on the target block device.

4. A method according to claim 3, characterized in that before obtaining the target virtual hard disk mounted on the BMS, the method comprises:

Acquiring a network configuration file; wherein the network configuration file comprises the target IP address;

Generating an image file corresponding to the network configuration file; wherein the image file comprises a preset label;

Creating the target block device based on the image file, wherein the target block device comprises the preset tag;

And creating the target virtual hard disk based on the target block device.

5. The method of claim 4, wherein the method further comprises:

acquiring a first file and a second file; the first file is used for storing a login password of a management system of the BMS, and the second file is used for storing identification information of a BMS instance;

the generating the image file corresponding to the network configuration file includes:

Generating the mirror image file based on the network configuration file, the first file and the second file; the image file is an ISO image file comprising the preset label.

6. The method according to any one of claims 1-5, further comprising:

Creating and configuring a system cloud disk based on cloud disk configuration parameters in bare metal instance configuration parameters issued by a cloud management platform; the system cloud disk is used for storing an OS (operating system) to be installed of the BMS;

And installing the operating system OS based on the system cloud disk.

7. The method according to any one of claims 1-6, further comprising:

and creating and configuring a virtual network card based on the network card configuration parameters in the bare metal instance configuration parameters issued by the cloud management platform.

8. The method of claim 7, wherein the network address in the BMS is a network address of a virtual network card;

The configuring the network address in the BMS based on the target IP address includes:

And configuring the network address of the virtual network card based on the target IP address.

9. The method according to any one of claims 6-8, wherein prior to obtaining the target block device mounted on the BMS, the method further comprises:

And restarting the BMS in response to a restarting instruction of the cloud pipe platform.

10. A computing device, the computing device comprising a first processor to:

acquiring target block equipment mounted on the BMS; wherein the target block device includes a target IP address;

And configuring a network address in the BMS based on the target IP address.

11. The computing device of claim 10, wherein the target block device comprises a preset tag;

The first processor is configured to obtain a target block device mounted on the BMS, and includes:

The first processor is configured to obtain the target block device from at least one block device mounted on the BMS based on the preset tag.

12. The computing device of claim 10 or 11, wherein before the first processor is configured to obtain a target block device mounted on the BMS, the first processor is further configured to:

acquiring a virtual hard disk mounted on the BMS; wherein each virtual hard disk is built based on block equipment;

obtaining a target virtual hard disk from the virtual hard disk; the target virtual hard disk is established based on the target block device.

13. The computing device of claim 12, further comprising a second processor, before the first processor is configured to obtain the target virtual hard disk mounted on the BMS, the second processor is configured to:

Acquiring a network configuration file; wherein the network configuration file comprises the target IP address;

Generating an image file corresponding to the network configuration file; wherein the image file comprises a preset label;

creating the target block device based on the image file, wherein the target block device comprises the preset tag;

And creating the target virtual hard disk based on the target block device.

14. The computing device of claim 13, wherein the second processor is further to:

acquiring a first file and a second file; the first file is used for storing a login password of a management system of the BMS, and the second file is used for storing identification information of a BMS instance;

the generating the image file corresponding to the network configuration file includes:

Generating the mirror image file based on the network configuration file, the first file and the second file; the image file is an ISO image file comprising the preset label.

15. The computing device of any of claims 10-14, wherein the second processor is further to:

Creating and configuring a system cloud disk based on cloud disk configuration parameters in bare metal instance configuration parameters issued by a cloud management platform; the system cloud disk is used for storing an OS (operating system) to be installed of the BMS;

And installing the operating system OS based on the system cloud disk.

16. The computing device of any of claims 10-15, wherein the second processor is further to:

and creating and configuring a virtual network card based on the network card configuration parameters in the bare metal instance configuration parameters issued by the cloud management platform.

17. The computing device of claim 16, wherein the network address in the BMS is a network address of a virtual network card;

The first processor is configured to configure a network address in the BMS based on the target IP address, including: the first processor is configured to configure a network address of the virtual network card based on the target IP address.

18. The computing device of any of claims 15-17, wherein, before the first processor is configured to obtain a target block device mounted on the BMS, the second device is further configured to:

And restarting the BMS in response to a restarting instruction of the cloud pipe platform.

19. The computing device of any of claims 10-18, wherein the first processor is a central processing unit, CPU; the second processor is a data processor DPU.