WO2023184875A1 - 一种裸金属磁盘备份方法、装置及计算机可读存储介质 - Google Patents

一种裸金属磁盘备份方法、装置及计算机可读存储介质 Download PDF

Info

Publication number
WO2023184875A1
WO2023184875A1 PCT/CN2022/118102 CN2022118102W WO2023184875A1 WO 2023184875 A1 WO2023184875 A1 WO 2023184875A1 CN 2022118102 W CN2022118102 W CN 2022118102W WO 2023184875 A1 WO2023184875 A1 WO 2023184875A1
Authority
WO
WIPO (PCT)
Prior art keywords
ironic
bare metal
command
backup
disk
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2022/118102
Other languages
English (en)
French (fr)
Inventor
雷亚帅
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Suzhou Wave Intelligent Technology Co Ltd
Original Assignee
Suzhou Wave Intelligent Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Suzhou Wave Intelligent Technology Co Ltd filed Critical Suzhou Wave Intelligent Technology Co Ltd
Publication of WO2023184875A1 publication Critical patent/WO2023184875A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operations
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1448—Management of the data involved in backup or backup restore
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G06F8/63—Image based installation; Cloning; Build to order
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/547—Remote procedure calls [RPC]; Web services
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/54—Indexing scheme relating to G06F9/54
    • G06F2209/544—Remote

Definitions

  • the present application relates to the technical field of cloud computing, and in particular to a bare metal disk backup method, device and computer-readable storage medium.
  • Bare Metal refers to a physical server without an operating system installed.
  • the bare metal service of the cloud computing platform provides an exclusive computing resource with the advantages of automatic provisioning system, automatic network switching, and no performance loss. It is widely used in high-performance computing, key databases and other scenarios. Public clouds and private clouds of major manufacturers have successively provided this service, and most of them have adopted the bare metal service (Ironic) project in the OpenStack cloud computing management platform to provide bare metal life cycle management.
  • Bare metal service Ironic manages the entire life cycle of bare metal on the cloud platform, including registration, hardware configuration, power management, status management, system deployment, etc. It is responsible for providing bare metal resources to nova, the computing service component of the cloud platform, and combines mirroring, network , storage component services, providing customers with bare metal system deployment services.
  • the current bare metal system installation method is to write the system image to the local physical disk of the bare metal.
  • This method of writing the local physical disk usually uses the configuration of disk arrays (Redundant Arrays of Independent Disks, RAID) for parity checking.
  • Disk redundancy protection is implemented to prevent data loss caused by hardware damage to a single physical disk.
  • RAID Redundant Arrays of Independent Disks
  • embodiments of the present application provide a bare metal disk backup method, including:
  • Extend Ironic-api as a backup interface to receive information about target physical disks in bare metal through the backup interface;
  • Control Ironic-conductor to generate a command to back up the target physical disk according to the information
  • Ironic-Python-Agent Send the command to Ironic-Python-Agent, so that the Ironic-Python-Agent converts the information of the target physical disk into a target image file according to the command and uploads it to Glance.
  • a bare metal disk backup device including:
  • An extension module for extending Ironic-api as a backup interface to receive information about the target physical disk in bare metal through the backup interface;
  • a control module configured to control Ironic-conductor to generate a command to back up the target physical disk based on the information
  • a sending module configured to send the command to Ironic-Python-Agent, so that the Ironic-Python-Agent converts the information of the target physical disk into a target image file according to the command and uploads it to Glance.
  • a bare metal disk backup device including:
  • a processor configured to implement the steps of the bare metal disk backup method in any embodiment when executing the computer readable instructions.
  • embodiments of the present application provide one or more non-volatile computer-readable storage media storing computer-readable instructions, which, when executed by one or more processors, cause the The one or more processors perform the steps of the bare metal disk backup method in any embodiment.
  • Figure 1 is a flow chart of a bare metal disk backup method according to one or more embodiments
  • Figure 2 is a schematic diagram of a bare metal disk backup principle according to one or more embodiments
  • Figure 3 is a schematic structural diagram of a bare metal disk backup device according to one or more embodiments
  • Figure 4 is a schematic structural diagram of another bare metal disk backup device according to one or more embodiments.
  • Bare metal is a physical server without an operating system installed. It has the characteristics of a traditional physical server and the virtualization service function of cloud computing technology. It is a product of the combination of the advantages of hardware and software. Its essence is a server that combines cloud computing service functions and provides physical device performance.
  • the bare metal service of the cloud computing platform provides an exclusive computing resource with the advantages of automatic provisioning system, automatic network switching, and no performance loss. It is widely used in high-performance computing, key databases and other scenarios. Public clouds and private clouds of major manufacturers have successively provided this service, and most of them have adopted the Ironic project in the OpenStack cloud computing management platform to provide bare metal life cycle management.
  • Bare metal service Ironic manages the entire life cycle of bare metal on the cloud platform, including registration, hardware configuration, power management, status management, system deployment, etc. It is responsible for providing bare metal resources to nova, the computing service component of the cloud platform, and combines mirroring, network , storage component services, providing customers with bare metal system deployment services.
  • Existing bare metal system installation includes writing the system image to the bare metal local physical disk. This way of writing to a local disk usually uses RAID for parity check for disk redundancy protection to prevent data loss caused by hardware damage to a single physical disk, but the reliability is still limited.
  • Figure 1 is a flow chart of a bare metal disk backup method provided by an embodiment of the present application. As shown in Figure 1, bare metal disk backup methods include:
  • Step S10 Extend Ironic-api as a backup interface to receive information about the target physical disk in bare metal through the backup interface.
  • Step S11 Control the Ironic-conductor to generate a command for backing up the target physical disk based on the information.
  • Step S12 Send the command to Ironic-Python-Agent, so that Ironic-Python-Agent converts the information of the target physical disk into the target image file according to the command and uploads it to Glance.
  • FIG 2 is a schematic diagram of a bare metal disk backup principle provided by an embodiment of the present application.
  • Ironic's bare metal service interface (Ironic-api) is extended as a backup interface to receive information about the bare metal target physical disk, including but not limited to the name of the disk to be backed up. , as well as the project and project name of the image to be created.
  • Ironic-api is a RESTful (a design style and development method of network applications) application programming interface (Application Programming Interface, API) service. Administrators and other services interact with Ironic through the API.
  • the bare metal management configuration service (Ironic-conductor) is controlled to generate a command to back up the target physical disk.
  • Ironic-conductor is one of the processes of Ironic. It is used to complete most of the work of Ironic services. It opens its functions to the outside world through APIs, interacts with Ironic-api through remote procedure calls (Remote Procedure Call, RPC), and is responsible for interacting with other components. to interact.
  • RPC Remote Procedure Call
  • Ironic-Python-Agent is an agent running on the bare metal memory file system and is responsible for hardware discovery, Deployment, disk cleanup and other tasks.
  • the Mirror Service provides OpenStack with services for discovering, registering, and obtaining virtual machine images, and provides a RESTful API for querying virtual machine image metadata.
  • Ironic-Python-Agent converts the target physical disk information into the target image file according to the command and uploads it to Glance, realizing the backup of the target physical disk.
  • the bare metal needs the backup of the disk, it can be obtained from Glance, preventing Loss of disk contents.
  • Ironic-api By extending Ironic-api as a backup interface, it is used to receive information about the target physical disk in bare metal through the backup interface; control Ironic-conductor to generate a command to backup the target physical disk based on the information, and send the command to Ironic-Python-Agent to use Use the Ironic-Python-Agent to convert the target physical disk information into the target image file according to the command and upload it to Glance.
  • the above technical solution uses an in-band method to back up the bare metal local disk as a mirror in Glance. When the backup file of the disk is needed, it can be obtained from Glance in the back-end docking storage to achieve data recovery and use, which greatly Improve the experience of cloud platform bare metal services and make them very reliable.
  • the command to control Ironic-conductor to generate a backup target physical disk based on the information includes:
  • first control Ironic-api to call the RPC interface of Ironic-conductor, thereby triggering Ironic-conductor to back up the target physical disk of bare metal.
  • the calling method of Ironic-api calling the RPC interface of Ironic-conductor can be rpc cast, which is an asynchronous call.
  • Call Glance to download the bare metal deployment image to the Trivial File Transfer Protocol (tftp) directory.
  • the deployment image is the kernel image and memory disk image associated when registering bare metal.
  • the configuration file of the Preboot eXecution Environment (PXE) is generated.
  • PXE here is also called the pre-execution environment. It provides a mechanism to start the computer using the Network Interface. This mechanism allows the computer to start without relying on local data storage devices (such as hard drives) or locally installed operating systems.
  • IPMI Intelligent Platform Management Interface
  • IPMI Intelligent Platform Management Interface
  • IPMI can span different operating systems, firmware and hardware platforms, and can intelligently monitor, control and automatically report a large number of The operating status of the server to reduce server system costs.
  • IPMI Intelligent Platform Management Interface
  • IPA runs and calls back, finally causing Ironic-conductor to establish a heartbeat connection with Ironic-Python-Agent to generate commands for use. In the future, the backup command will be issued through the IPA extended interface.
  • Ironic-api By controlling the Ironic-api to call the RPC interface of Ironic-conductor, calling Glance to download the bare metal deployment image to the tftp directory, generating the PXE configuration file, and controlling the Ironic-conductor to issue IPMI commands to trigger the deployment of bare metal based on the image.
  • Restart the configuration file from PXE control Ironic-conductor to establish a heartbeat connection with Ironic-Python-Agent, and generate a command to back up the target physical disk.
  • Control Ironic-api to determine whether the target physical disk and its backup items in the information exist
  • controlling Ironic-api before controlling Ironic-api to call the RPC interface of Ironic-conductor, controlling Ironic-api determines whether the target physical disk and its backup items in the information exist, and in response to the judgment result being that they exist, enter the control Steps for Ironic-api to call the RPC interface of Ironic-conductor;
  • controlling Ironic-api before controlling Ironic-api to call the RPC interface of Ironic-conductor, controlling Ironic-api determines whether the target physical disk and its backup item in the information exist, and generates a backup in response to the judgment result being that it does not exist. wrong information.
  • the input backup disk information may be wrong.
  • the Ironic-api before controlling the Ironic-api to call the RPC interface of the Ironic-conductor, it is necessary to control the Ironic-
  • the API determines whether the target physical disk and its backup items in the information exist. Specifically, Ironic-api performs parameter verification. If the selected physical disk and backup item do not exist, an error will be reported directly and a backup error message will be generated; if the selected backup physical disk and backup item exist, Ironic-api will be called. Conductor's RPC interface is backed up.
  • control Ironic-api In order to prevent incorrect backup disk information from being entered, before controlling Ironic-api to call the RPC interface of Ironic-conductor, control Ironic-api to determine whether the target physical disk and its backup items in the information exist, and then perform operations on whether to back up based on the results. Improved backup efficiency.
  • Ironic-conductor adopts an event-driven code architecture
  • a backup event is added, that is, a backup event, and the current bare metal status is set to backup (backingup).
  • Ironic receives the RPC call, it triggers the backup event to prepare PXE for bare metal and triggers Ironic to restart from PXE.
  • the network service (Neutron) interface is called to switch the bare metal network from the business network to the deployment network, that is, changing the network status of the bare metal during the disk backup process to facilitate disk backup.
  • the specific steps for Ironic-Python-Agent to convert the target physical disk information into a target image file according to the command and upload it to Glance include:
  • first Ironic-Python-Agent i.e. IPA
  • dd is a command on Unix and Unix-like systems, its main function is to convert and copy files
  • IPA calls the authentication service (keystone) interface.
  • Keystone is the function in the OpenStack framework responsible for authentication, service rules and service tokens. Therefore, by calling the Keystone interface, you can obtain a token so that the backup can be authenticated. Then call Glance based on the token to create the temporary image file as the target image file under Glance.
  • IPA converts the information of the target physical disk into a temporary image file according to the command, calls the Keystone interface to obtain the token, and calls Glance based on the token, thereby creating the temporary image file as the target image file under Glance, realizing the target physical disk in the Backup under Glance.
  • IPA converts the target physical disk information into a temporary image file through the dd command, and the file format is img format.
  • the qemu-img tool uses the qemu-img tool to change the format of the temporary image file and convert it from img format to qcow2 format.
  • the qcow2 image format can use a file to represent a fixed-size block device, has a smaller file size, and supports copy-on-write (COW, Copy-on-write), snapshot and zlib-based data compression, and supports Advanced Encryption Standard (AES) encryption.
  • COW copy-on-write
  • AES Advanced Encryption Standard
  • the Ironic-conductor is controlled to set the status of the bare metal to the original status and call the Neutron interface to switch the bare metal network from the deployment network to the business network.
  • the command execution status of the Ironic-Python-Agent is obtained at a preset period, and in response to determining that the command execution is completed based on the command execution status, the Ironic-conductor is controlled. Set the status of the bare metal to the original status, and call the Neutron interface to switch the bare metal network from the deployment network to the business network.
  • Ironic-Python-Agent After receiving the backup command, Ironic-Python-Agent creates an image file under Glance based on the information of the target physical disk according to the command. At this time, it is also necessary to obtain the command execution status of Ironic-Python-Agent according to the preset period to determine whether the backup command has been executed; there is no limit on the preset period and can be determined according to the specific implementation situation. If it is determined that the command execution is completed based on the command execution status, that is, the image file under Glance has been created. At this time, you need to control Ironic-conductor to set the status of the bare metal to the original status, that is, change the backup event status to the original status. state.
  • the original state is running, that is, the state where the bare metal is running normally, thereby releasing the backup state and clearing the cache files; and calling the Neutron interface to switch the bare metal network from the deployment network to the business network, and then switching the network back to the business network so that Normal operation with subsequent bare metal.
  • the command execution status of Ironic-Python-Agent can be obtained according to the preset period; if the command execution is determined to be completed based on the command execution status, the Ironic-conductor is controlled to set the status of the bare metal to the original state. It is stateful and calls the Neutron interface to switch the bare metal network from the deployment network to the business network so that the bare metal can run normally later.
  • the above embodiment describes the bare metal disk backup method.
  • the embodiments of this application also provide corresponding implementation methods of bare metal disk backup devices. It should be noted that the embodiments of the present application describe practical examples of the device part from two perspectives, one is based on the functional module perspective, and the other is based on the hardware structure perspective.
  • FIG 3 is a schematic structural diagram of a bare metal disk backup device provided by an embodiment of the present application. As shown in Figure 3, the bare metal disk backup device includes:
  • Extension module 10 is used to extend Ironic-api as a backup interface to receive information about the target physical disk in bare metal through the backup interface.
  • the control module 11 is used to control the Ironic-conductor to generate a command for backing up the target physical disk based on the information.
  • the sending module 12 is used to send commands to Ironic-Python-Agent, so that Ironic-Python-Agent converts the information of the target physical disk into a target image file according to the command and uploads it to Glance.
  • the expansion module 10 extends Ironic's Ironic-api as a backup interface to receive information about the target physical disk of bare metal, including but not limited to the name of the disk to be backed up, as well as the project and project of the mirror to be created. name.
  • Ironic-api is a RESTful API service. Administrators and other services interact with Ironic through the API.
  • Ironic-conductor is one of Ironic's processes, used to complete most of the work of Ironic services, open its functions to the outside world through API, interact with Ironic-api through remote procedure call RPC interface, and is responsible for interacting with other components.
  • Ironic-conductor there is no restriction on the specific process of controlling the Ironic-conductor to generate the command for backing up the target physical disk, and it depends on the specific implementation situation.
  • the sending module 12 sends the command to Ironic-Python-Agent.
  • Ironic-Python-Agent IPA
  • Glance provides services for OpenStack to discover, register and obtain virtual machine images, and provides a RESTful API to query virtual machine image metadata.
  • Ironic-Python-Agent converts the target physical disk information into the target image file according to the command and uploads it to Glance, realizing the backup of the target physical disk.
  • the bare metal needs the backup of the disk, it can be obtained from Glance, preventing Loss of disk contents.
  • there is no restriction on the generation process of the target image file and it depends on the specific implementation situation.
  • the bare metal disk backup device provided in the embodiment of Figure 3 extends the Ironic-api as a backup interface through an expansion module to receive information about the target physical disk in the bare metal through the backup interface; and controls the Ironic-conductor according to the information through the control module Generate a command to back up the target physical disk; send the command to Ironic-Python-Agent through the sending module, so that Ironic-Python-Agent can convert the target physical disk information into a target image file according to the command and upload it to Glance. It can be seen that the device backs up the bare metal local disk as an image in Glance in-band. When the backup file of the disk is needed, it can be obtained from Glance in the back-end docking storage to achieve data recovery and use, which greatly improves the cloud The platform’s bare metal service experience is very reliable.
  • FIG 4 is a schematic structural diagram of another bare metal disk backup device provided by an embodiment of the present application. As shown in Figure 4, the bare metal disk backup device includes:
  • Memory 20 for storing computer readable instructions.
  • the processor 21 is configured to implement the steps of the bare metal disk backup method in any of the previous embodiments when executing computer readable instructions.
  • the bare metal disk backup device provided by the embodiment of FIG. 4 may include, but is not limited to, a smartphone, a tablet computer, a notebook computer or a desktop computer.
  • the processor 21 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc.
  • the processor 21 can adopt at least one hardware form among a digital signal processor (Digital Signal Processor, DSP), a field-programmable gate array (Field-Programmable Gate Array, FPGA), and a programmable logic array (Programmable Logic Array, PLA). to fulfill.
  • DSP Digital Signal Processor
  • FPGA field-programmable gate array
  • PROgrammable Logic Array PLA
  • the processor 21 may also include a main processor and a co-processor.
  • the main processor is a processor used to process data in the wake-up state, also called a central processing unit (Central Processing Unit, CPU); the co-processor is A low-power processor used to process data in standby mode.
  • CPU Central Processing Unit
  • the processor 21 may be integrated with a graphics processor (Graphics Processing Unit, GPU), and the GPU is responsible for rendering and drawing content that needs to be displayed on the display screen.
  • the processor 21 may also include an artificial intelligence (Artificial Intelligence, AI) processor, which is used to process computing operations related to machine learning.
  • AI Artificial Intelligence
  • Memory 20 may include one or more computer-readable storage media, which may be non-transitory.
  • the memory 20 may also include high-speed random access memory, and non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices.
  • the memory 20 is at least used to store the following computer readable instructions 201. After the computer readable instructions are loaded and executed by the processor 21, the relevant aspects of the bare metal disk backup method disclosed in any of the previous embodiments can be implemented. step.
  • the resources stored in the memory 20 may also include the operating system 202, data 203, etc., and the storage method may be short-term storage or permanent storage.
  • the operating system 202 may include Windows, Unix, Linux, etc.
  • Data 203 may include but is not limited to data involved in the bare metal disk backup method.
  • the bare metal disk backup device may also include a display screen 22 , an input and output interface 23 , a communication interface 24 , a power supply 25 and a communication bus 26 .
  • Figure 4 does not constitute a limitation on the bare metal disk backup device, and may include more or fewer components than shown in the figure.
  • This application also provides a corresponding embodiment of a computer-readable storage medium.
  • Computer-readable instructions are stored on the computer-readable storage medium.
  • the steps of the bare metal disk backup method in any of the previous embodiments are implemented.
  • Embodiments of the present application propose one or more non-volatile computer-readable storage media storing computer-readable instructions.
  • the computer-readable instructions When executed by one or more processors, the one or more processes cause the The server performs the steps of the bare metal disk backup method in any of the previous embodiments.
  • the methods in the above embodiments are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , execute all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

本申请实施例公开了一种裸金属磁盘备份方法、装置及计算机可读存储介质，涉及云计算领域。裸金属磁盘备份方法的步骤包括：通过扩展Ironic-api作为备份接口，根据信息控制Ironic-conductor生成备份目标物理磁盘的命令，发送命令至Ironic-Python-Agent，以用于Ironic-Python-Agent根据命令将目标物理磁盘的信息转换为目标镜像文件并上传至Glance。

Description

一种裸金属磁盘备份方法、装置及计算机可读存储介质
相关申请的交叉引用
本申请要求于2022年3月30日提交中国专利局，申请号为CN202210321233.6，申请名称为“一种裸金属磁盘备份方法、装置及计算机可读存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及云计算的技术领域，特别是涉及一种裸金属磁盘备份方法、装置及计算机可读存储介质。
背景技术
裸金属(Bare Metal)是指没有安装操作系统的物理服务器。而云计算平台的裸金属服务提供的是一种独占式的计算资源，具有自动发放系统、自动切换网络、无性能损耗等优点，广泛应用于高性能计算、关键数据库等场景。各大厂商的公有云、私有云均陆续提供了此项服务，其中大多数是采用了OpenStack云计算管理平台中的裸金属服务(Ironic)项目提供裸金属的生命周期管理。裸金属服务Ironic管理裸金属在云平台的整个生命周期，包括注册、硬件配置、电源管理、状态管理以及系统部署等，负责向云平台的计算服务组件nova提供裸金属资源，并结合镜像、网络、存储组件服务，向客户提供裸金属系统的部署服务。
目前裸金属的系统安装是采取将系统镜像写入裸金属本地物理磁盘的方式，这种写本地物理磁盘的方式，通常使用配置磁盘阵列(Redundant Arrays of Independent Disks，RAID)进行奇偶校验的方式进行磁盘冗余保护，以防止单个物理磁盘的硬件损坏导致的数据丢失，但是这种方式存在硬件故障的可能性，可靠性还是有限。
发明内容
在第一方面，本申请实施例提供了一种裸金属磁盘备份方法，包括：
扩展Ironic-api作为备份接口，以用于通过所述备份接口接收裸金属中目标物理磁盘的信息；
根据所述信息控制Ironic-conductor生成备份所述目标物理磁盘的命令；以及
发送所述命令至Ironic-Python-Agent，以用于所述Ironic-Python-Agent根据所述命令将所述目标物理磁盘的所述信息转换为目标镜像文件并上传至Glance。
在第二方面，本申请实施例提供了一种裸金属磁盘备份装置，包括：
扩展模块，用于扩展Ironic-api作为备份接口，以用于通过所述备份接口接收裸金属中目标物理磁盘的信息；
控制模块，用于根据所述信息控制Ironic-conductor生成备份所述目标物理磁盘的命令；以及
发送模块，用于发送所述命令至Ironic-Python-Agent，以用于所述Ironic-Python-Agent根据所述命令将所述目标物理磁盘的所述信息转换为目标镜像文件并上传至Glance。
在第三方面，本申请实施例提供了一种裸金属磁盘备份装置，包括：
存储器，用于存储计算机可读指令；以及
处理器，用于执行所述计算机可读指令时实现任一实施例中的裸金属磁盘备份方法的步骤。
在第四方面，本申请实施例提供了一个或多个存储有计算机可读指令的非易失性计算机可读存储介质，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行任一实施例中的裸金属磁盘备份方法的步骤。
附图说明
为了更清楚地说明本申请实施例，下面将对实施例中所需要使用的附图做简单的介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为根据一个或多个实施例中的一种裸金属磁盘备份方法的流程图；
图2为根据一个或多个实施例中的一种裸金属磁盘备份原理的示意图；
图3为根据一个或多个实施例中的一种裸金属磁盘备份装置的结构示意图；
图4为根据一个或多个实施例中的又一种裸金属磁盘备份装置的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下，所获得的所有其他实施例，都属于本申请保护范围。
为了使本技术领域的人员更好地理解本申请实施例的方案，下面结合附图和具体实施方式对本申请作进一步的详细说明。
裸金属，是没有安装操作系统的物理服务器，既具有传统物理服务器特点，又具备云计算技术的虚拟化服务功能，是硬件和软件优势结合的产物。其本质是兼具云计算服务功能和提供物理设备性能的服务器。而云计算平台的裸金属服务提供的是一种独占式的计算资源，具有自动发放系统、自动切换网络、无性能损耗等优点，广泛应用于高性能计算、关键数据库等场景。各大厂商的公有云、私有云均陆续提供了此项服务，其中大多数是采用了OpenStack云计算管理平台中的Ironic项目提供裸金属的生命周期管理。裸金属服务Ironic管理裸金属在云平台的整个生命周期，包括注册、硬件配置、电源管理、状态管理以及系统部署等，负责向云平台的计算服务组件nova提供裸金属资源，并结合镜像、网络、存储组件服务，向客户提供裸金属系统的部署服务。已有的裸金属的系统安装包括采取将系统镜像写入裸金属本地物理磁盘的方式。这种写本地磁盘的方式，通常使用RAID进行奇偶校验的方式进行磁盘冗余保护，以防止单个物理磁盘的硬件损坏导致的数据丢失，但是可靠性还是有限。
本申请实施例提供了一种裸金属磁盘备份方法。图1为本申请实施例提供的一种裸金属磁盘备份方法的流程图。如图1所示，裸金属磁盘备份方法包括：
步骤S10：扩展Ironic-api作为备份接口，以用于通过备份接口接收裸金属中目标物理磁盘的信息。
步骤S11：根据信息控制Ironic-conductor生成备份目标物理磁盘的命令。
步骤S12：发送命令至Ironic-Python-Agent，以用于Ironic-Python-Agent根据命令将目标物理磁盘的信息转换为目标镜像文件并上传至Glance。
图2为本申请实施例提供的一种裸金属磁盘备份原理的示意图。如图2所示，在本实施例中，通过扩展Ironic的裸金属服务接口(Ironic-api)作为备份接口，接收裸金属的目标物理磁盘的信息，其中包括但不限于要备份的磁盘的名称，以及将要创建的镜像的项目和项目名称。其中Ironic-api是一个RESTful(一种网络应用程序的设计风格和开发方式)的应用程序编程接口(Application Programming Interface，API)服务，管理员和 其他服务通过API与Ironic进行交互。
随后根据上述信息控制裸金属管理配置服务(Ironic-conductor)生成备份目标物理磁盘的命令。Ironic-conductor是Ironic的进程之一，用于完成Ironic服务的绝大部分工作，通过API对外开放其功能，与Ironic-api通过远程过程调用(Remote Procedure Call，RPC)进行交互，负责与其他组件进行交互。在本实施例对于控制Ironic-conductor生成备份目标物理磁盘的命令的具体过程不做限制，根据具体的实施情况而定。
在生成了备份命令之后，发送命令至裸金属服务代理(Ironic-Python-Agent，IPA)，可以理解的是，Ironic-Python-Agent是运行于裸金属内存文件系统的一个代理，负责硬件发现、部署、磁盘清理等任务。镜像服务(Glance)为OpenStack提供了用来发现、注册和获取虚拟机映像的服务，提供RESTful API用来查询虚拟机映像元数据。Ironic-Python-Agent根据命令将目标物理磁盘的信息转换为目标镜像文件并上传至Glance，实现了对目标物理磁盘的备份，当裸金属需要该磁盘的备份时，可以从Glance中获取，防止了磁盘内容的丢失。对于目标镜像文件的生成过程不做限制，可根据具体的实施情况而定。
通过扩展Ironic-api作为备份接口，以用于通过备份接口接收裸金属中目标物理磁盘的信息；根据信息控制Ironic-conductor生成备份目标物理磁盘的命令，发送命令至Ironic-Python-Agent，以用于Ironic-Python-Agent根据命令将目标物理磁盘的信息转换为目标镜像文件并上传至Glance。由此可见，上述技术方案通过带内的方式将裸金属本地磁盘备份为Glance中的镜像，当需要磁盘的备份文件时能够从后端对接存储的Glance中获取，以实现数据恢复使用，极大地提升云平台裸金属服务的体验，十分地可靠。
作为一种可选的实施方式，根据信息控制Ironic-conductor生成备份目标物理磁盘的命令包括：
控制Ironic-api调用Ironic-conductor的RPC接口；
调用Glance下载裸金属的部署镜像至tftp目录下，生成PXE的配置文件；
控制Ironic-conductor下发IPMI命令，以用于触发裸金属根据部署镜像和配置文件从PXE中重启；
控制Ironic-conductor与Ironic-Python-Agent建立心跳连接，以生成命令。
对于控制Ironic-conductor生成备份目标物理磁盘的命令的具体过程不做限制，可根据具体的实施情况而定。
作为一种可选的实施方式，首先控制Ironic-api调用Ironic-conductor的RPC接口，从而去触发Ironic-conductor去备份裸金属的目标物理磁盘。需要注意的是，Ironic-api调 用Ironic-conductor的RPC接口的调用方式可以是rpc cast，即异步调用。调用Glance下载裸金属的部署镜像至简单文件传输协议(Trivial File Transfer Protocol，tftp)目录下，其中，部署镜像是注册裸金属时关联的内核镜像和内存盘镜像。随后生成预启动执行环境(Preboot eXecution Environment，PXE)的配置文件，这里的PXE也被称为预执行环境，它提供了一种使用网络接口(Network Interface)启动计算机的机制。这种机制让计算机的启动可以不依赖本地数据存储设备(如硬盘)或本地已安装的操作系统。
在建立好PXE后，控制Ironic-conductor下发智能平台管理接口(Intelligent Platform Management Interface，IPMI)命令，IPMI能够横跨不同的操作系统、固件和硬件平台，可以智能地监视、控制和自动回报大量服务器的运作状况，以降低服务器系统成本。控制Ironic-conductor下发IPMI命令后，从而触发裸金属根据部署镜像和配置文件从PXE中重启，IPA运行并回调，最终使得Ironic-conductor与Ironic-Python-Agent建立心跳连接，以生成命令以用于在后续通过IPA扩展的接口将备份命令下发。
通过控制Ironic-api调用Ironic-conductor的RPC接口，调用Glance下载裸金属的部署镜像至tftp目录下，生成PXE的配置文件，控制Ironic-conductor下发IPMI命令，以用于触发裸金属根据部署镜像和配置文件从PXE中重启，控制Ironic-conductor与Ironic-Python-Agent建立心跳连接，生成了备份目标物理磁盘的命令。
作为一种可选的实施方式，在控制Ironic-api调用Ironic-conductor的RPC接口之前，可以执行以下步骤：
控制Ironic-api判断信息中目标物理磁盘及其备份项目是否存在；
若是，则进入到控制Ironic-api调用Ironic-conductor的RPC接口的步骤；
若否，生成备份错误的信息。
在一些可选的实施方式中，在控制Ironic-api调用Ironic-conductor的RPC接口之前，控制Ironic-api判断信息中目标物理磁盘及其备份项目是否存在，响应于判断结果为存在，进入到控制Ironic-api调用Ironic-conductor的RPC接口的步骤；
在一些可选的实施方式中，在控制Ironic-api调用Ironic-conductor的RPC接口之前，控制Ironic-api判断信息中目标物理磁盘及其备份项目是否存在，响应于判断结果为不存在，生成备份错误的信息。
可以理解的是，在具体实施中可能会出现输入的备份的磁盘信息是错误的情况，作为一种可选的实施方式，在控制Ironic-api调用Ironic-conductor的RPC接口之前，需要控制Ironic-api判断信息中目标物理磁盘及其备份项目是否存在。具体地，Ironic-api进行参数校验，若选择的备份的物理磁盘、备份项目不存在，则直接报错，生成备份错误的 信息；若选择的备份的物理磁盘、备份项目存在，则调用Ironic-conductor的RPC接口进行备份。
为了防止输入错误的备份磁盘信息，在控制Ironic-api调用Ironic-conductor的RPC接口之前，先控制Ironic-api判断信息中目标物理磁盘及其备份项目是否存在，再根据结果对是否备份进行操作，提高了备份效率。
作为一种可选的实施方式，在调用Glance下载裸金属的部署镜像至tftp目录下之前，还可以执行以下步骤：
控制Ironic-conductor将裸金属的状态设置为备份中；
调用Neutron接口将裸金属的网络从业务网络切换为部署网络。
如图2所示，由于Ironic-conductor采用事件驱动的代码架构，因此增加一个backup事件，即备份事件，设置当前裸金属状态为备份中(backingup)。Ironic接收到RPC调用后，触发backup事件，从而为裸金属准备PXE，触发Ironic从PXE重启。同时调用网络服务(Neutron)接口将裸金属的网络从业务网络切换为部署网络，也就是在裸金属的磁盘备份过程中改变其网络状态，以便于磁盘备份。
作为一种可选的实施方式，Ironic-Python-Agent根据命令将目标物理磁盘的信息转换为目标镜像文件并上传至Glance的具体步骤包括：
根据命令将目标物理磁盘的信息转换为临时镜像文件；
调用Keystone接口以获取令牌；
根据令牌调用Glance，以用于将临时镜像文件创建为Glance下的目标镜像文件。
对于目标镜像文件的生成过程不做限制，可根据具体的实施情况而定。
作为一种可选的实施方式，首先Ironic-Python-Agent(即IPA)根据命令将目标物理磁盘的信息通过dd命令(dd是一个Unix和类Unix系统上的命令，主要功能为转换和复制文件)转换为一个临时镜像文件；随后如图2所示，IPA调用认证服务(keystone)接口。需要注意的是，Keystone是OpenStack框架中负责身份验证、服务规则和服务令牌的功能，因此通过调用Keystone接口能够获得一个令牌token，从而使备份得到身份验证。再根据该令牌token调用Glance，从而将临时镜像文件创建为Glance下的目标镜像文件。
IPA根据命令将目标物理磁盘的信息转换为临时镜像文件，调用Keystone接口以获取令牌，并根据令牌调用Glance，从而将临时镜像文件创建为Glance下的目标镜像文件，实现了目标物理磁盘在Glance下的备份。
作为一种可选的实施方式，在调用Keystone接口以获取令牌之前，还可以执行以下 步骤：通过qemu-img工具将临时镜像文件的格式由img格式转换为qcow2格式。
IPA根据命令将目标物理磁盘的信息通过dd命令转换为一个临时镜像文件，文件格式为img格式。通过qemu-img工具更改临时镜像文件的格式，将其从img格式转换为qcow2格式，qcow2镜像格式可以使用一个文件来表示一个固定大小的块设备，具有更小的文件大小，并支持写时拷贝(COW,Copy-on-write)，快照和基于zlib的数据压缩，并支持高级加密标准(Advanced Encryption Standard，AES)加密。在得到qcow2格式的临时镜像文件后，调用Keystone接口以获取令牌，根据令牌调用Glance，将qcow2格式的临时镜像文件创建为Glance下的目标镜像文件，处理时间更短。
作为一种可选的实施方式，在发送命令至Ironic-Python-Agent之后，还可以执行以下步骤：
按预设周期获取Ironic-Python-Agent的命令执行情况；
若根据命令执行情况确定命令执行完成，则控制Ironic-conductor将裸金属的状态设置为原有状态，并调用Neutron接口将裸金属的网络从部署网络切换为业务网络。
在一些可选的实施方式中，在发送命令至Ironic-Python-Agent之后，按预设周期获取Ironic-Python-Agent的命令执行情况，响应于根据命令执行情况确定命令执行完成，控制Ironic-conductor将裸金属的状态设置为原有状态，并调用Neutron接口将裸金属的网络从部署网络切换为业务网络。
Ironic-Python-Agent在接收到备份命令之后，根据命令对目标物理磁盘的信息进行Glance下镜像文件的创建。此时还需要按预设周期获取Ironic-Python-Agent的命令执行情况，从而确定备份命令是否被执行完成；对于预设周期不做限制，可根据具体实施情况而定。若根据命令执行情况确定命令执行完成，即已经创建完成Glance下的镜像文件，这时需要控制Ironic-conductor将裸金属的状态设置为原有状态，即更改backup事件状态，将其改为原有状态。原有状态为运行中，即裸金属正常运行的状态，从而解除备份状态，清理缓存文件；并调用Neutron接口将裸金属的网络从部署网络切换为业务网络，将网络重新切换回业务网络，以便与裸金属后续的正常运行。
在发送命令至Ironic-Python-Agent之后，可以按预设周期获取Ironic-Python-Agent的命令执行情况；若根据命令执行情况确定命令执行完成，则控制Ironic-conductor将裸金属的状态设置为原有状态，并调用Neutron接口将裸金属的网络从部署网络切换为业务网络，以便与裸金属后续的正常运行。
上述实施例对于裸金属磁盘备份方法进行了描述。本申请实施例还提供了裸金属磁盘备份装置对应的实施方式。需要说明的是，本申请实施例从两个角度对装置部分的实 方式例进行描述，一种是基于功能模块的角度，另一种是基于硬件结构的角度。
图3为本申请实施例提供的一种裸金属磁盘备份装置的结构示意图，如图3所示，裸金属磁盘备份装置包括：
扩展模块10，用于扩展Ironic-api作为备份接口，以用于通过备份接口接收裸金属中目标物理磁盘的信息。
控制模块11，用于根据信息控制Ironic-conductor生成备份目标物理磁盘的命令。
发送模块12，用于发送命令至Ironic-Python-Agent，以用于Ironic-Python-Agent根据命令将目标物理磁盘的信息转换为目标镜像文件并上传至Glance。
可以理解的是，拓展模块10通过扩展Ironic的Ironic-api作为备份接口，接收裸金属的目标物理磁盘的信息，其中包括但不限于要备份的磁盘的名称，以及将要创建的镜像的项目和项目名称。其中Ironic-api是一个RESTful的API服务，管理员和其他服务通过API与Ironic进行交互。
随后控制模块11根据上述信息控制Ironic-conductor生成备份目标物理磁盘的命令。Ironic-conductor是Ironic的进程之一，用于完成Ironic服务的绝大部分工作，通过API对外开放其功能，与Ironic-api通过远程过程调用RPC接口进行交互，负责与其他组件进行交互。在本实施例对于控制Ironic-conductor生成备份目标物理磁盘的命令的具体过程不做限制，根据具体的实施情况而定。
在生成了备份命令之后，发送模块12发送命令至Ironic-Python-Agent，可以理解的是，Ironic-Python-Agent(IPA)是运行于裸金属内存文件系统的一个代理，负责硬件发现、部署、磁盘清理等任务。Glance为OpenStack提供了用来发现、注册和获取虚拟机映像的服务，提供RESTful API用来查询虚拟机映像元数据。Ironic-Python-Agent根据命令将目标物理磁盘的信息转换为目标镜像文件并上传至Glance，实现了对目标物理磁盘的备份，当裸金属需要该磁盘的备份时，可以从Glance中获取，防止了磁盘内容的丢失。在本实施例中，对于目标镜像文件的生成过程不做限制，根据具体的实施情况而定。
图3的实施例所提供的裸金属磁盘备份装置，通过扩展模块扩展Ironic-api作为备份接口，以用于通过备份接口接收裸金属中目标物理磁盘的信息；通过控制模块根据信息控制Ironic-conductor生成备份目标物理磁盘的命令；通过发送模块发送命令至Ironic-Python-Agent，以用于Ironic-Python-Agent根据命令将目标物理磁盘的信息转换为目标镜像文件并上传至Glance。由此可见，装置通过带内的方式将裸金属本地磁盘备份为Glance中的镜像，当需要磁盘的备份文件时能够从后端对接存储的Glance中获取，以实现数据恢复使用，极大地提升云平台裸金属服务的体验，十分地可靠。
图4为本申请实施例提供的又一种裸金属磁盘备份装置的结构示意图，如图4所示，裸金属磁盘备份装置包括：
存储器20，用于存储计算机可读指令。
处理器21，用于执行计算机可读指令时实现前文任一实施例中的裸金属磁盘备份的方法的步骤。
图4的实施例提供的裸金属磁盘备份装置可以包括但不限于智能手机、平板电脑、笔记本电脑或台式电脑等。
其中，处理器21可以包括一个或多个处理核心，比如4核心处理器、8核心处理器等。处理器21可以采用数字信号处理器(Digital Signal Processor，DSP)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、可编程逻辑阵列(Programmable Logic Array，PLA)中的至少一种硬件形式来实现。处理器21也可以包括主处理器和协处理器，主处理器是用于对在唤醒状态下的数据进行处理的处理器，也称中央处理器(Central Processing Unit，CPU)；协处理器是用于对在待机状态下的数据进行处理的低功耗处理器。在一些实施例中，处理器21可以在集成有图形处理器(Graphics Processing Unit，GPU)，GPU用于负责显示屏所需要显示的内容的渲染和绘制。一些实施例中，处理器21还可以包括人工智能(Artificial Intelligence，AI)处理器，该AI处理器用于处理有关机器学习的计算操作。
存储器20可以包括一个或多个计算机可读存储介质，该计算机可读存储介质可以是非暂态的。存储器20还可包括高速随机存取存储器，以及非易失性存储器，比如一个或多个磁盘存储设备、闪存存储设备。本实施例中，存储器20至少用于存储以下计算机可读指令201，其中，该计算机可读指令被处理器21加载并执行之后，能够实现前文任一实施例公开的裸金属磁盘备份方法的相关步骤。另外，存储器20所存储的资源还可以包括操作系统202和数据203等，存储方式可以是短暂存储或者永久存储。其中，操作系统202可以包括Windows、Unix、Linux等。数据203可以包括但不限于裸金属磁盘备份方法涉及到的数据。
在一些实施例中，裸金属磁盘备份装置还可包括有显示屏22、输入输出接口23、通信接口24、电源25以及通信总线26。
本领域技术人员可以理解，图4中示出的结构并不构成对裸金属磁盘备份装置的限定，可以包括比图示更多或更少的组件。
本申请还提供一种计算机可读存储介质对应的实施例。计算机可读存储介质上存储有计算机可读指令，计算机可读指令被处理器执行时实现前文任一实施例中的裸金属磁 盘备份方法的步骤。
本申请实施例提出一个或多个存储有计算机可读指令的非易失性计算机可读存储介质，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行前文任一实施例中的裸金属磁盘备份方法的步骤。
可以理解的是，如果上述实施例中的方法以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上对本申请实施例提供的裸金属磁盘备份方法、装置及计算机可读存储介质进行了介绍。说明书中，一些实施例重点说明的可能是与另一些实施例的不同之处，各个实施例之间相同相似部分互相参见即可。对于实施例公开的装置而言，由于其与实施例公开的方法相对应，所以描述的比较简单，相关之处参见方法部分说明即可。应当指出，对于本技术领域的普通技术人员来说，在不脱离本申请原理的前提下，还可以对本申请进行若干改进和修饰，这些改进和修饰也落入本申请权利要求的保护范围内。
还需要说明的是，在本说明书中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。

Claims (20)

  1. 一种裸金属磁盘备份方法，其特征在于，包括：
    扩展Ironic-api作为备份接口，以用于通过所述备份接口接收裸金属中目标物理磁盘的信息；
    根据所述信息控制Ironic-conductor生成备份所述目标物理磁盘的命令；以及
    发送所述命令至Ironic-Python-Agent，以用于所述Ironic-Python-Agent根据所述命令将所述目标物理磁盘的所述信息转换为目标镜像文件并上传至Glance。
  2. 根据权利要求1所述的裸金属磁盘备份方法，其特征在于，所述根据所述信息控制Ironic-conductor生成备份所述目标物理磁盘的命令，包括：
    控制所述Ironic-api调用所述Ironic-conductor的RPC接口；
    调用所述Glance下载所述裸金属的部署镜像至tftp目录下，生成PXE的配置文件；
    控制所述Ironic-conductor下发IPMI命令，以用于触发所述裸金属根据所述部署镜像和所述配置文件从所述PXE中重启；以及
    控制所述Ironic-conductor与所述Ironic-Python-Agent建立心跳连接，以生成所述命令。
  3. 根据权利要求2所述的裸金属磁盘备份方法，其特征在于，在所述控制所述Ironic-api调用所述Ironic-conductor的RPC接口之前，还包括：
    控制所述Ironic-api判断所述信息中所述目标物理磁盘及其备份项目是否存在；以及
    响应于判断结果为存在，进入到所述控制所述Ironic-api调用所述Ironic-conductor的RPC接口的步骤；
  4. 根据权利要求2所述的裸金属磁盘备份方法，其特征在于，在所述控制所述Ironic-api调用所述Ironic-conductor的RPC接口之前，还包括：
    控制所述Ironic-api判断所述信息中所述目标物理磁盘及其备份项目是否存在；以及
    响应于判断结果为不存在，生成备份错误的信息。
  5. 根据权利要求2所述的裸金属磁盘备份方法，其特征在于，所述控制所述Ironic-api调用所述Ironic-conductor的RPC接口，包括：
    控制所述Ironic-api通过异步调用的方式调用所述Ironic-conductor的RPC接口。
  6. 根据权利要求2所述的裸金属磁盘备份方法，其特征在于，在所述调用所述Glance下载所述裸金属的部署镜像至tftp目录下之前，还包括：
    控制所述Ironic-conductor将所述裸金属的状态设置为备份中；以及
    调用Neutron接口将所述裸金属的网络从业务网络切换为部署网络。
  7. 根据权利要求1至6任一项所述的裸金属磁盘备份方法，其特征在于，所述Ironic-Python-Agent根据所述命令将所述目标物理磁盘的所述信息转换为目标镜像文件并上传至Glance的具体步骤包括：
    根据所述命令将所述目标物理磁盘的所述信息转换为临时镜像文件；
    调用Keystone接口以获取令牌；以及
    根据所述令牌调用所述Glance，以用于将所述临时镜像文件创建为所述Glance下的所述目标镜像文件。
  8. 根据权利要求7所述的裸金属磁盘备份方法，其特征在于，所述根据所述令牌调用所述Glance，包括：
    根据所述令牌对备份操作进行身份验证；以及
    响应于身份验证通过，调用所述Glance。
  9. 根据权利要求1至8所述的裸金属磁盘备份方法，其特征在于，所述命令为Unix或类Unix系统中的dd命令。
  10. 根据权利要求9所述的裸金属磁盘备份方法，其特征在于，所述根据所述命令将所述目标物理磁盘的所述信息转换为临时镜像文件，包括：
    根据所述dd命令将所述目标物理磁盘的所述信息转换为格式为img格式的临时镜像文件。
  11. 根据权利要求10所述的裸金属磁盘备份方法，其特征在于，在所述调用Keystone接口以获取令牌之前，还包括：
    通过qemu-img工具将所述临时镜像文件的格式由img格式转换为qcow2格式。
  12. 根据权利要求11所述的裸金属磁盘备份方法，其特征在于，还包括：
    对具有qcow2格式的临时镜像文件采用高级加密标准进行加密。
  13. 根据权利要求1至12任一项所述的裸金属磁盘备份方法，其特征在于，在所述发送所述命令至Ironic-Python-Agent之后，还包括：
    按预设周期获取所述Ironic-Python-Agent的命令执行情况；以及
    响应于根据所述命令执行情况确定命令执行完成，控制所述Ironic-conductor将所述裸金属的状态设置为原有状态，并调用所述Neutron接口将所述裸金属的网络从所述部署网络切换为所述业务网络。
  14. 根据权利要求13所述的裸金属磁盘备份方法，其特征在于，所述控制所述Ironic-conductor将所述裸金属的状态设置为原有状态，包括：控制所述Ironic-conductor 将所述裸金属的备份事件状态设置为原有状态。
  15. 根据权利要求13或14所述的裸金属磁盘备份方法，其特征在于，还包括：
    在所述调用所述Neutron接口将所述裸金属的网络从所述部署网络切换为所述业务网络之前，接触备份状态，清理缓存文件。
  16. 根据权利要求1至15任一项所述的裸金属磁盘备份方法，其特征在于，所述目标物理磁盘的信息包括要备份的磁盘的名称，以及将要创建的镜像的项目和项目名称。
  17. 根据权利要求1至16任一项所述的裸金属磁盘备份方法，其特征在于，还包括：响应于所述裸金属需要该磁盘的备份的指令，从Glance中获取所述目标镜像文件。
  18. 一种裸金属磁盘备份装置，其特征在于，包括：
    扩展模块，用于扩展Ironic-api作为备份接口，以用于通过所述备份接口接收裸金属中目标物理磁盘的信息；
    控制模块，用于根据所述信息控制Ironic-conductor生成备份所述目标物理磁盘的命令；以及
    发送模块，用于发送所述命令至Ironic-Python-Agent，以用于所述Ironic-Python-Agent根据所述命令将所述目标物理磁盘的所述信息转换为目标镜像文件并上传至Glance。
  19. 一种裸金属磁盘备份装置，其特征在于，包括：
    存储器，用于存储计算机可读指令；
    处理器，用于执行所述计算机可读指令时实现如权利要求1至17任一项所述的裸金属磁盘备份方法的步骤。
  20. 一个或多个存储有计算机可读指令的非易失性计算机可读存储介质，其特征在于，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行如权利要求1至17任一项所述的裸金属磁盘备份方法的步骤。
PCT/CN2022/118102 2022-03-30 2022-09-09 一种裸金属磁盘备份方法、装置及计算机可读存储介质 Ceased WO2023184875A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210321233.6A CN114416434B (zh) 2022-03-30 2022-03-30 一种裸金属磁盘备份方法、装置及计算机可读存储介质
CN202210321233.6 2022-03-30

Publications (1)

Publication Number Publication Date
WO2023184875A1 true WO2023184875A1 (zh) 2023-10-05

Family

ID=81263868

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/118102 Ceased WO2023184875A1 (zh) 2022-03-30 2022-09-09 一种裸金属磁盘备份方法、装置及计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN114416434B (zh)
WO (1) WO2023184875A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024217061A1 (zh) * 2023-12-12 2024-10-24 天翼云科技有限公司 基于三层化网络的裸金属部署方法、装置、设备及介质
CN119127578A (zh) * 2024-10-30 2024-12-13 浪潮云信息技术股份公司 一种裸金属节点的镜像并发下载方法、装置、设备及介质
CN119356764A (zh) * 2024-12-25 2025-01-24 珠海星云智联科技有限公司 一种裸金属服务器部署方法及系统
CN120915798A (zh) * 2025-09-25 2025-11-07 中移(苏州)软件技术有限公司 服务器信息采集、更新方法与装置、系统、介质、产品及设备

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114416434B (zh) * 2022-03-30 2022-07-08 苏州浪潮智能科技有限公司 一种裸金属磁盘备份方法、装置及计算机可读存储介质
CN117891472B (zh) * 2024-03-11 2024-06-04 杭州吉利汽车数字科技有限公司 一种裸金属镜像部署的方法、装置及介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120072398A1 (en) * 2008-07-10 2012-03-22 Cms Products, Inc. Method and Apparatus for Creating a Self Booting Operating System Image Backup on an External USB Hard Disk Drive That is Capable of Performing a Complete Restore to an Internal System Disk
CN107765990A (zh) * 2016-08-17 2018-03-06 中兴通讯股份有限公司 一种系统磁盘管理方法和装置
CN111090439A (zh) * 2019-12-13 2020-05-01 苏州浪潮智能科技有限公司 裸金属服务器linux系统镜像生成方法、装置及设备
CN113918174A (zh) * 2021-10-27 2022-01-11 华云数据控股集团有限公司 裸金属服务器的部署方法、部署控制器及服务器集群
CN114416434A (zh) * 2022-03-30 2022-04-29 苏州浪潮智能科技有限公司 一种裸金属磁盘备份方法、装置及计算机可读存储介质

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150278032A1 (en) * 2014-04-01 2015-10-01 Ca, Inc. Providing services on system being recovered
CN108984272A (zh) * 2018-07-23 2018-12-11 郑州云海信息技术有限公司 OpenStack云计算管理平台的控制方法和装置
CN109144821A (zh) * 2018-09-05 2019-01-04 山东浪潮云投信息科技有限公司 一种云计算数据中心内物理服务器自动管理方法
CN111756629B (zh) * 2019-03-26 2022-06-03 中移(苏州)软件技术有限公司 设备接入overlay网络及通信的方法、装置、设备、网络及介质
CN112367186B (zh) * 2020-10-13 2023-01-10 苏州浪潮智能科技有限公司 一种基于0penStack裸机的故障保护方法及装置
CN112866017B (zh) * 2021-01-08 2022-07-08 苏州浪潮智能科技有限公司 配置裸金属服务器bmc ip地址的方法、系统、介质及设备
CN112948008B (zh) * 2021-03-02 2023-06-23 浪潮云信息技术股份公司 一种基于Ironic管理物理裸机的方法
CN113419813B (zh) * 2021-05-21 2023-02-24 济南浪潮数据技术有限公司 一种基于容器平台部署裸机管理服务的方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120072398A1 (en) * 2008-07-10 2012-03-22 Cms Products, Inc. Method and Apparatus for Creating a Self Booting Operating System Image Backup on an External USB Hard Disk Drive That is Capable of Performing a Complete Restore to an Internal System Disk
CN107765990A (zh) * 2016-08-17 2018-03-06 中兴通讯股份有限公司 一种系统磁盘管理方法和装置
CN111090439A (zh) * 2019-12-13 2020-05-01 苏州浪潮智能科技有限公司 裸金属服务器linux系统镜像生成方法、装置及设备
CN113918174A (zh) * 2021-10-27 2022-01-11 华云数据控股集团有限公司 裸金属服务器的部署方法、部署控制器及服务器集群
CN114416434A (zh) * 2022-03-30 2022-04-29 苏州浪潮智能科技有限公司 一种裸金属磁盘备份方法、装置及计算机可读存储介质

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024217061A1 (zh) * 2023-12-12 2024-10-24 天翼云科技有限公司 基于三层化网络的裸金属部署方法、装置、设备及介质
CN119127578A (zh) * 2024-10-30 2024-12-13 浪潮云信息技术股份公司 一种裸金属节点的镜像并发下载方法、装置、设备及介质
CN119356764A (zh) * 2024-12-25 2025-01-24 珠海星云智联科技有限公司 一种裸金属服务器部署方法及系统
CN120915798A (zh) * 2025-09-25 2025-11-07 中移(苏州)软件技术有限公司 服务器信息采集、更新方法与装置、系统、介质、产品及设备

Also Published As

Publication number Publication date
CN114416434A (zh) 2022-04-29
CN114416434B (zh) 2022-07-08

Similar Documents

Publication Publication Date Title
WO2023184875A1 (zh) 一种裸金属磁盘备份方法、装置及计算机可读存储介质
US10073747B2 (en) Reducing recovery time in disaster recovery/replication setup with multitier backend storage
US9747179B2 (en) Data management agent for selective storage re-caching
US10754955B2 (en) Authenticating a boot path update
US20240378119A1 (en) System and method for cloning as sql server ag databases in a hyperconverged system
EP3750066B1 (en) Protection of infrastructure-as-a-service workloads in public cloud
WO2021129733A1 (zh) 云操作系统的管理方法、装置、服务器、管理系统及介质
CN111488241A (zh) 在容器编排平台实现无代理备份与恢复操作的方法和系统
US10452502B2 (en) Handling node failure in multi-node data storage systems
CN107111530B (zh) 一种容灾方法、系统和装置
US10592373B2 (en) Integrating external services with a clustered file system
CN106777394B (zh) 一种集群文件系统
CN112256393A (zh) 一种裸金属服务器的资源管理方法及设备
CN117311627A (zh) 容器卷热扩容系统、方法及介质
CN115576705B (zh) 一种冗余固件的数据同步方法、装置及介质
CN110221868B (zh) 主机系统的部署方法、装置、电子设备及存储介质
CN110688128A (zh) 一种提高超融合存储可靠性的部署方法和装置
CN115174596A (zh) 一种设备远程复制方法、装置以及介质
WO2022088812A1 (zh) 一种基于Openstack的硬盘快照方法和装置
CN120429169B (zh) 一种基于多云平台的数据恢复方法及系统
CN119311371B (zh) 虚拟机迁移方法、装置、计算机设备、可读存储介质和程序产品
US12613784B2 (en) Lossless failover for data recovery
US12430183B2 (en) Snapshot based pool of virtual resources for efficient development and test of hyper-converged infrastructure environments
US20240231868A9 (en) Management of duplicative virtual machine entries for a data management system
CN110955489B (zh) 用于可靠地恢复虚拟机的方法和系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22934694

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22934694

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 01/04/2025)

122 Ep: pct application non-entry in european phase

Ref document number: 22934694

Country of ref document: EP

Kind code of ref document: A1