WO2019047571A1 - 对请求处理的方法、片上系统和公有云管理组件 - Google Patents

对请求处理的方法、片上系统和公有云管理组件 Download PDF

Info

Publication number
WO2019047571A1
WO2019047571A1 PCT/CN2018/088829 CN2018088829W WO2019047571A1 WO 2019047571 A1 WO2019047571 A1 WO 2019047571A1 CN 2018088829 W CN2018088829 W CN 2018088829W WO 2019047571 A1 WO2019047571 A1 WO 2019047571A1
Authority
WO
WIPO (PCT)
Prior art keywords
volume
bare metal
metal server
chip
identifier
Prior art date
Application number
PCT/CN2018/088829
Other languages
English (en)
French (fr)
Inventor
王俊捷
董益兼
郭海涛
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP18854975.2A priority Critical patent/EP3713198B1/en
Priority to EP22176928.4A priority patent/EP4113291B1/en
Publication of WO2019047571A1 publication Critical patent/WO2019047571A1/zh
Priority to US16/743,131 priority patent/US11775316B2/en
Priority to US17/318,075 priority patent/US11847470B2/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4416—Network booting; Remote initial program loading [RIPL]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/76—Architectures of general purpose stored program computers
    • G06F15/78—Architectures of general purpose stored program computers comprising a single central processing unit
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/76—Architectures of general purpose stored program computers
    • G06F15/78—Architectures of general purpose stored program computers comprising a single central processing unit
    • G06F15/7807—System on chip, i.e. computer system on a single chip; System in package, i.e. computer system on one or more chips in a single package
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604—Improving or facilitating administration, e.g. storage management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629—Configuration or reconfiguration of storage systems
    • G06F3/0631—Configuration or reconfiguration of storage systems by allocating resources to storage systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629—Configuration or reconfiguration of storage systems
    • G06F3/0632—Configuration or reconfiguration of storage systems by initialisation or re-initialisation of storage systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4406—Loading of operating system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45541—Bare-metal, i.e. hypervisor runs directly on hardware
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Definitions

  • the present application relates to the field of storage and, more particularly, to a method of request processing, a system on a chip, and a public cloud management component.
  • the Preboot Execute Environment is a protocol designed by Intel to work in a client/server network mode. It can support bare metal servers to download operating systems from a remote server (another server) over the network. This allows the bare metal server to boot the operating system through the network to implement the bare metal server.
  • the basic input and output system (BIOS) of the bare metal server transfers the PXE client (a software in the BIOS) into the memory, and the PXE client sends the PXE client to the PXE client.
  • the server requests the operating system to be installed by the bare metal server, and the PXE server saves the operating system in the memory of the bare metal server, and the bare metal server activates the operating system in the memory, thereby realizing the issuance of the bare metal server.
  • the application provides a method for request processing, a system on chip, and a public cloud management component, which facilitates rapid allocation in a public cloud bare metal scenario, shortens the time allocated by the bare metal server, and improves efficiency and user experience.
  • a method of processing a request is provided, the method being performed by a system on a chip, the system on a chip being included in a bare metal server, the bare metal server further comprising a processor, the bare metal server being included in the distributed storage system
  • the distributed storage system further includes a public cloud management component, the method comprising: receiving, by the system on chip, a volume request sent by the public cloud management component, the volume request includes an identifier of a system volume; and the system on the chip is according to the volume Requesting to save the identifier of the system volume.
  • the identifier of the system volume is used by the bare metal server to determine the system volume, and the operating system of the bare metal server is started according to the system volume, and the system volume is saved.
  • the file used to boot the operating system of the bare metal server is saved.
  • the system volume is obtained by cloning a file of the operating system of the bare metal server by the public cloud management component.
  • the method for processing the request in the embodiment of the present application helps to shorten the time allocated by the bare metal server, and improves the efficiency and user experience.
  • the method further includes: receiving, by the system-on-chip, the public cloud management component A pending volume operation request, the volume operation request includes an identifier of the data volume; the system on chip sends an identifier of the data volume to the processor to instruct the processor to use the data volume as an available storage space of the bare metal server.
  • the public cloud management component In the method for processing a request in the embodiment of the present application, the public cloud management component generates an identifier of the volume that is carried by the hanging volume operation request, thereby realizing the automatic hanging of the bare-metal server, thereby preventing the tenant from manually loading the volume by logging in to the bare-metal server. Helps automate the management of volumes.
  • the system-on-a-chip sends an identifier of the data volume to the processor to instruct the processor to the data volume
  • the method further includes: receiving, by the system on chip, a unwinding operation request sent by the public cloud management component, the unwinding operation request including an identifier of the data volume; the system on the chip sends the data volume
  • the identifier is assigned to the processor to prevent the processor from using the data volume as available storage space for the bare metal server.
  • the method for processing the request in the embodiment of the present application generates the unloading operation request carrying the volume identifier by the public cloud management component, thereby realizing the automatic unloading of the bare metal server, thereby preventing the tenant from manually unloading the unloading operation by logging in to the bare metal server, which is helpful. To achieve automated management of the volume.
  • a method for processing a request is provided, the method being performed by a public cloud management component, the public cloud management component being included in a distributed storage system, the distributed storage system further comprising a bare metal server, the bare metal
  • the server includes a system on chip, the method includes: the public cloud management component generates a volume request, the volume request includes an identifier of a system volume, where the file of the operating system for starting the bare metal server is saved; the public cloud The management component sends the volume request to the system on chip to instruct the system on the chip to save the identity of the system volume according to the volume request.
  • the system volume is obtained by cloning a file of the operating system of the bare metal server by the public cloud management component.
  • the method for processing the request in the embodiment of the present application helps to shorten the time allocated by the bare metal server, and improves the efficiency and user experience.
  • the method further includes: the public cloud management component generates a hanging volume operation Requesting, the pending volume operation request includes an identifier of the data volume; the public cloud management component sends the volume operation request to the system on a chip to instruct the system on the chip to send an identifier of the data volume to the processor, the processor
  • the data volume serves as the available storage space for the bare metal server.
  • the public cloud management component In the method for processing a request in the embodiment of the present application, the public cloud management component generates an identifier of the volume that is carried by the hanging volume operation request, thereby realizing the automatic hanging of the bare-metal server, thereby preventing the tenant from manually loading the volume by logging in to the bare-metal server. Helps achieve fully automated management of volumes.
  • the system on a chip sends an identifier of the data volume to the processor, where the processor uses the data volume as the After the available storage space of the bare metal server, the method further includes: the public cloud management component generates a unwinding operation request, the unwinding operation request includes an identifier of the data volume; and the public cloud management component sends the unwinding operation to the system on a chip A request to instruct the on-chip system to send an identification of the data volume to the processor, the processor being prohibited from using the data volume as available storage space of the bare metal server.
  • the method for processing the request in the embodiment of the present application generates the unloading operation request carrying the volume identifier by the public cloud management component, thereby realizing the automatic unloading of the bare metal server, thereby preventing the tenant from manually unloading the unloading operation by logging in to the bare metal server, which is helpful. To achieve automated management of the volume.
  • the third aspect provides a system on chip
  • the system on chip includes: a transceiver module, configured to receive a volume request sent by a public cloud management component, where the volume request includes an identifier of a system volume, and a processing module is configured to The volume request saves the identifier of the system volume.
  • the identifier of the system volume is used by the bare metal server to determine the system volume, and the operating system of the bare metal server is started according to the system volume, and the system volume is saved. The file used to boot the operating system of the bare metal server.
  • the system volume is obtained by cloning a file of the operating system of the bare metal server by the public cloud management component.
  • the method for processing the request in the embodiment of the present application helps to shorten the time allocated by the bare metal server, and improves the efficiency and user experience.
  • the transceiver module is further configured to receive a volume operation request sent by the public cloud management component, where the volume operation request includes an identifier of the data volume;
  • the transceiver module is further configured to send the identifier of the data volume to the processor of the bare metal server to indicate that the processor of the bare metal server uses the data volume as available storage space of the bare metal server.
  • the system-on-a-chip of the embodiment of the present invention generates a volume-running request to carry a volume by using a public cloud management component, so that the bare-metal server automatically suspends the volume, thereby preventing the tenant from manually loading the volume by logging in to the bare-metal server, thereby facilitating the volume implementation.
  • Automated management
  • the transceiver module is further configured to receive an unwinding operation request sent by the public cloud management component, the unwinding operation The request includes an identifier of the data volume; the transceiver module is further configured to send the identifier of the data volume to the processor of the bare metal server to prohibit the processor of the bare metal server from using the data volume as an available storage space of the bare metal server.
  • the system-on-a-chip of the embodiment of the present application generates the unloading operation request carrying the volume identifier by using the public cloud management component, thereby realizing the automatic unloading of the bare metal server, thereby preventing the tenant from manually unloading the unloading operation by logging in to the bare metal server, thereby facilitating the volume realization. Automated management.
  • a fourth aspect provides a public cloud management component, where the public cloud management component includes: a processing module, configured to generate a volume request, where the volume request includes an identifier of a system volume, where the system volume is saved for starting the bare metal a file of the operating system of the server; the transceiver module is configured to send the volume request to the system on the chip to instruct the system on the chip to save the identifier of the system volume according to the request for the volume.
  • the system volume is obtained by cloning a file of the operating system of the bare metal server by the public cloud management component.
  • the method for processing the request in the embodiment of the present application helps to shorten the time allocated by the bare metal server, and improves the efficiency and user experience.
  • the processing module is further configured to generate a volume operation request, where the volume operation request includes an identifier of the data volume
  • the transceiver module is further configured to The system on chip sends the pending volume operation request to instruct the system on the chip to send the identifier of the data volume to the processor of the bare metal server, and the processor of the bare metal server uses the data volume as the available storage space of the bare metal server.
  • the public cloud management component of the embodiment of the present application implements the hanging volume operation request to carry the volume identifier, so that the bare metal server automatically suspends the volume, thereby preventing the tenant from manually loading the volume by logging in to the bare metal server, thereby facilitating the automation of the volume. management.
  • the processing module is further configured to generate a unwinding operation request, where the unwinding operation request includes an identifier of the data volume
  • the transceiver module is further configured to send the unwinding operation request to the system on a chip to instruct the system on the chip to send the identifier of the data volume to the processor of the bare metal server, and prohibit the processor of the bare metal server from using the data volume as the Available storage space for bare metal servers.
  • the public cloud management component of the embodiment of the present application implements the automatic unloading of the bare metal server by generating the unloading operation request carrying the volume identifier, thereby preventing the tenant from manually unloading the unloading operation by logging in to the bare metal server, thereby facilitating automatic management of the volume. .
  • a fifth aspect provides a system on chip, the system on chip comprising: a transceiver, configured to receive a volume request sent by a public cloud management component, where the volume request includes an identifier of a system volume, and the processor is configured to perform according to the hanging The volume request saves the identifier of the system volume.
  • the identifier of the system volume is used by the bare metal server to determine the system volume, and the operating system of the bare metal server is started according to the system volume, and the system volume is saved. The file used to boot the operating system of the bare metal server.
  • the transceiver is further configured to receive a volume operation request sent by the public cloud management component, where the volume operation request includes an identifier of the data volume;
  • the transceiver is further configured to send the identifier of the data volume to the processor of the bare metal server to indicate that the processor of the bare metal server uses the data volume as available storage space of the bare metal server.
  • the transceiver is further configured to receive a unwinding operation request sent by the public cloud management component, the unwinding operation The request includes an identification of the data volume; the transceiver is further configured to send an identifier of the data volume to a processor of the bare metal server to prohibit the processor of the bare metal server from using the data volume as available storage space of the bare metal server.
  • a sixth aspect provides a public cloud management component, where the public cloud management component includes: a processor, configured to generate a volume request, where the volume request includes an identifier of a system volume, where the system volume is saved for starting the bare metal a file of the operating system of the server; the transceiver is configured to send the volume request to the system on the chip to instruct the system on the chip to save the identifier of the system volume according to the request for the volume.
  • the processor is further configured to generate a volume operation request, where the volume operation request includes an identifier of the data volume; the transceiver is further configured to The system on chip sends the pending volume operation request to instruct the system on the chip to send the identifier of the data volume to the processor of the bare metal server, and the processor of the bare metal server uses the data volume as the available storage space of the bare metal server.
  • the processor is further configured to generate a unwinding operation request, where the unwinding operation request includes an identifier of the data volume;
  • the transceiver is further configured to send the unwinding operation request to the system on a chip to instruct the system on the chip to send the identifier of the data volume to the processor of the bare metal server, and prohibit the processor of the bare metal server from using the data volume as the bare metal The available storage space for the server.
  • a bare metal server includes a processor and a system on a chip, wherein the system on a chip is any one of the foregoing third and third aspects, and the fifth and fifth aspects A system on a chip in any of the possible implementations of the aspect.
  • a system comprising a bare metal server and a public cloud management component, the bare metal server comprising a system on chip and a processor, wherein the system on a chip is any one of the foregoing third aspect and the third aspect And a system-on-a-chip in any one of the foregoing possible implementations of the fifth aspect and the fifth aspect; and/or the public cloud management component is any one of the foregoing fourth and fourth aspects, and the foregoing The public cloud management component of any of the possible implementations of the sixth aspect and the sixth aspect.
  • FIG. 1 is a schematic block diagram of a distributed storage system in accordance with an embodiment of the present application.
  • FIG. 2 is a schematic block diagram of a bare metal server in the distributed storage system shown in FIG. 1.
  • FIG. 3 is a schematic flowchart of a method for processing a request according to an embodiment of the present application.
  • FIG. 4 is another schematic block diagram of a distributed storage system in accordance with an embodiment of the present application.
  • FIG. 5 is another schematic flowchart of a method for processing a request according to an embodiment of the present application.
  • FIG. 6 is still another schematic flowchart of a method for processing a request according to an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a system on a chip in accordance with an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of a public cloud management component in accordance with an embodiment of the present application.
  • FIG. 9 is another schematic block diagram of a system on a chip in accordance with an embodiment of the present application.
  • FIG. 10 is another schematic block diagram of a public cloud management component according to an embodiment of the present application.
  • the embodiments of the present application are applicable to any distributed storage architecture and non-OpenStack public cloud management architecture.
  • the distributed storage system 100 includes a bare metal server 110 and a public cloud management component 120, and the bare metal server 110 and The public cloud management component 120 communicates over a network.
  • FIG. 2 shows a schematic block diagram of a bare metal server 110 in the distributed storage system 100 shown in FIG. 1.
  • the bare metal server 110 includes a processor 111 and a system on chip (SOC) 112, which can be embedded in the bare metal server 110.
  • SOC system on chip
  • processor 111 can communicate with the system on chip 112 via a component Peripheral Component Interconnect Express (PCIe), which communicates with the public cloud management component 120 over a network.
  • PCIe Peripheral Component Interconnect Express
  • FIG. 3 shows a schematic flow chart of a method 200 for request processing according to an embodiment of the present application.
  • the method 200 includes S210 to S240.
  • the method illustrated in FIG. 3 can be performed by the distributed storage system 100 illustrated in FIG. S210 and S220 may be executed by the public cloud management component 120 in the distributed storage system 100 shown in FIG. 1.
  • S230 can be executed by the system on chip 112 in the distributed storage system 100 shown in FIG.
  • S240 can be executed by bare metal server 110 in distributed storage system 100 shown in FIG.
  • the public cloud management component 120 generates a volume request, where the volume request includes an identifier of a system volume in which a file for starting an operating system of the bare metal server 110 is saved.
  • the bare metal server 110 includes the processor 111 and the system on chip 112. Although the system on chip 112 is a component of the bare metal server 110, the operating system of the bare metal server 110 is not the operating system of the system on chip 112.
  • bare metal server 110 can include a central processing unit and a memory coupled to the central processing unit. The operating system of the bare metal server 110 can be saved in the memory. The central processing unit can run an operating system of the bare metal server 110 by accessing the memory.
  • the public cloud management component 120 sends the volume request to the system on chip 112.
  • the system on chip 112 saves the identifier of the system volume according to the volume request.
  • the system on chip 112 mounts the system volume to the operating system of the system on chip 112 according to the request for the volume, and a volume is added to the operating system of the system on chip 112.
  • a volume is added to the operating system of the system on chip 112.
  • GUI graphical user interface
  • the system volume can be the C drive of the system on chip 112.
  • the operating system of the system on chip 112 can access the system volume.
  • the bare metal server 110 starts the operating system of the bare metal server 110 according to the system volume, and specifically includes: the bare metal server 110 runs a file saved in the system volume for starting the operating system of the bare metal server, and starts the bare metal server 110. Operating system.
  • the operating system of system on chip 112 can be Windows 7, or Linux.
  • the bare metal server 110 when the bare metal server 110 starts the bare metal server 110 according to the system volume, the bare metal server 110 adds a system volume.
  • the system volume may be the C disk of the bare metal server 110.
  • FIG. 4 shows another schematic structural diagram of the distributed storage system 100 according to an embodiment of the present application.
  • the distributed storage system 100 shown in FIG. 1 can be expanded to obtain the distributed storage system 100 shown in FIG.
  • the distributed storage system further includes a storage pool 130.
  • the system volume is obtained by cloning the file of the operating system of the bare metal server 110 by the public cloud management component 120.
  • the public cloud management component 120 can obtain the operation from the storage pool 130 before cloning the file of the operating system. System files.
  • the processor 111 of the bare metal server 110 saves the front end driver 1111, which stores the back end driver 1121, the distributed storage software client 1122, and the management agent software 1123.
  • the public cloud management component 120 when the tenant who needs to apply for the bare metal server 110 applies for the bare metal server 110 through the local client interface where the tenant is located, the public cloud management component 120 generates a hanging volume request according to the request sent by the local client where the tenant is located, and the hanging volume request Includes the identification of the system volume.
  • the public cloud management component 120 sends the volume request to the system on chip 112.
  • the system on chip 112 determines by the management agent software 1123 that the volume request needs to be processed by the distributed storage software client 1122.
  • the distributed storage software client 1122 mounts the system volume to the operating system of the system on chip 112 according to the volume request. Specifically, the system on chip 112 saves the identifier of the system volume through the distributed storage software client 1122.
  • the correspondence of the information of the system volume is used for the startup of the bare metal server 110.
  • the correspondence is used by the processor 111 of the bare metal server 110 to obtain the information of the system volume according to the identifier of the system volume, and access the bare metal server saved in the system volume according to the information of the system volume.
  • the file of the operating system of 110 starts the operating system of the bare metal server 110 according to the system volume.
  • the mapping table may contain an entry that records information about the system volume and the identity of the system volume.
  • the system volume information includes the size of the system volume and the logical block address (LBA) of the system volume.
  • the system volume identifier includes the storage address of the system volume or the Universally Unique Identifier (UUID).
  • the processor 111 When the bare metal server 110 is started, the processor 111 first acquires the identifier of the system volume from the system on chip 112, and the processor 111 determines the information of the system volume according to the identifier of the system volume. The processor 111 searches for the entry matching the identifier of the system volume in the mapping table by using the identifier of the system volume as a search key. The processor 111 determines the information of the system volume according to the matched entry, and the processor 111 starts the file of the operating system of the bare metal server 110 according to the information of the system volume. Specifically, the bare metal server 110 runs the system volume as an operating system of the bare metal server 110.
  • the processor 111 loads a Basic Input Output System (BIOS) to find the system on chip 112, and the system on chip 112 runs the extended read only memory of the system on chip 112 (Expansion ROM) a saved driver of the system on chip 112, thereby obtaining an identification of the system volume, the system on chip 112 transmitting the identification of the system volume to the processor 111 of the bare metal server 110, the processor 111 of the bare metal server 110 according to the system volume And the volume query command sends a volume query command to the on-chip system 112.
  • BIOS Basic Input Output System
  • Exsion ROM extended read only memory of the system on chip 112
  • the volume query command carries the identifier of the system volume, and after receiving the volume query command, the system on chip 112 parses the volume query command to search for the on-chip system 112.
  • a mapping table holds a mapping relationship between the identifier of the system volume and the information of the system volume
  • the information of the system volume includes an LBA of the system volume
  • the system on the chip 112 sends the LBA of the information of the system volume to the processor 111.
  • the processor 111 can run a boot loader.
  • the processor can utilize the boot loader to access the system volume indicated by the LBA. Specifically, the processor may use a boot loader to obtain, from the system volume, a file that starts an operating system of the bare metal server.
  • the processor runs a file that launches an operating system of the bare metal server, thereby starting an operating system of the bare metal server.
  • the operating system of the bare metal server may be Windows 9x
  • the file of the operating system that starts the bare metal server may be IO.SYS.
  • the operating system of the bare metal server may be MS-DOS
  • the file of the operating system that starts the bare metal server may be MSDOS.SYS.
  • the information of the system volume is stored in the system on chip 112.
  • System on chip 112 is a component of bare metal server 110. Therefore, the bare metal server 110 can acquire the information of the operating system of the bare metal server 110 according to the corresponding relationship between the identifier of the system volume previously saved by the system on chip 112 and the information of the system volume, and run the operating system according to the system volume.
  • the file is downloaded from the remote server by starting the PXE client when the server is started, and the file of the operating system of the bare metal server 110 is obtained only by the information of the system volume, and then the operation of the bare metal server 110 is started according to the system volume.
  • the system shortens the bare-metal server 110 to start the PXE client first, then downloads the image from the remote server, and then starts the installation time of the operating system, which improves the efficiency and user experience.
  • the system volume only needs to be mounted to the public cloud management component 120.
  • the physical machine can be used by other tenants, and the public cloud management component 120 secures the system volume. except.
  • the method for request processing in the embodiment of the present application realizes rapid allocation and recovery of the bare metal server, which is shortened from 10 minutes to the second level, thereby improving efficiency and user experience.
  • FIG. 5 shows a schematic flow diagram of a method 300 of request processing in accordance with an embodiment of the present application.
  • the method 300 includes S310 through S340.
  • the method illustrated in FIG. 5 can be performed by the distributed storage system 100 illustrated in FIG.
  • the execution body of the method shown in FIG. 5 and the execution body of the method shown in FIG. 3 may be the same execution body.
  • the execution time of the method shown in FIG. 5 may be later than the execution time of the method shown in FIG.
  • the public cloud management component 120 generates a volume operation request, where the volume operation request includes an identifier of the data volume.
  • the public cloud management component 120 sends the hanging operation request to the system on chip 112;
  • the system on chip 112 sends an identifier of the data volume to the processor 111 of the bare metal server 110.
  • the processor 111 of the bare metal server 110 uses the data volume as the available storage space of the bare metal server 110.
  • the method 300 further includes:
  • the public cloud management component 120 finds the network address corresponding to the system on chip 112 through the correspondence table of the bare metal server 110 and the system on chip 112.
  • the public cloud management component 120 sends a pending volume operation request to the management agent software 1123 of the corresponding system on chip 112, the pending volume operation request including the identification of the data volume.
  • the system on chip 112 determines by the management agent software 1123 that the volume operation request needs to be processed by the distributed storage software client 1122, which mounts the data volume to the system on chip 112 according to the distributed storage software client 1122. In the operating system, the system on chip 112 then determines that the identity of the data volume needs to be sent to the processor 111, and the system on chip 112 sends the pending volume operation request to the backend driver saved by the system on chip 112 through the management agent software 1123. 1121.
  • the system on chip 112 sends the identifier of the data volume on the PCIe channel to the front end driver 1111 saved by the processor 111 according to the backend driver 1121.
  • the processor 111 drives the data volume according to the front end driver 1111. As the available storage space of the bare metal server 110.
  • the data volume may be a volume before expansion or a volume after expansion. This application does not limit this.
  • the processor 111 of the bare metal server 110 uses the data volume as the available storage space of the bare metal server 110, and the bare metal server 110 adds a data volume, for example, the data volume may be the D disk of the bare metal server or E disk.
  • the tenant needs to configure the volume information (volume size, type) through the management interface (provided by the OpenStack management software), and then the OpenStack management software creates the volume and identifies the volume information, for example, the World Wide Name (WWN). Or the small computer interface qualified name (IQN) is fed back to the tenant through the interface, and the tenant logs in to the bare metal server 110 to manually mount the volume.
  • WWN World Wide Name
  • IQN small computer interface qualified name
  • This process is more difficult to associate with the management interface provided by the OpenStack management software.
  • the automatic management of the volume can be realized, and the operation of the volume does not require manual intervention.
  • the public cloud management component In the method for processing a request in the embodiment of the present application, the public cloud management component generates an identifier of the volume that is carried by the hanging volume operation request, thereby realizing the automatic hanging of the bare-metal server, thereby preventing the tenant from manually loading the volume by logging in to the bare-metal server. Helps automate the management of volumes.
  • FIG. 6 shows a schematic flow diagram of a method 400 of request processing in accordance with an embodiment of the present application.
  • the method 400 includes S410 through S440.
  • the method illustrated in FIG. 6 can be performed by the distributed storage system 100 illustrated in FIG.
  • the execution body of the method shown in FIG. 6 and the execution body of the method shown in FIG. 5 may be the same execution body.
  • the execution time of the method shown in FIG. 6 may be later than the execution time of the method shown in FIG. 5.
  • the public cloud management component 120 After the system on the chip sends the identifier of the data volume to the processor to instruct the processor to use the data volume as the available storage space of the bare metal server, the public cloud management component 120 generates a unwinding operation request, and the unwinding The operation request includes an identification of the data volume;
  • the public cloud management component 120 receives the unloading operation request sent to the system on chip 112.
  • the system on chip 112 sends an identifier of the data volume to the processor 111.
  • the processor 111 avoids using the data volume as an available storage space of the bare metal server 110 according to the identifier of the data volume.
  • the unwinding operation request may be after the hanging operation request in the method 300, and the specific processing flow is similar to that in the method 300, except that the processor 111 obtains the identifier of the data volume and avoids The data volume serves as the available storage space for the bare metal server 110.
  • processor 111 can use the data volume as available storage space for the bare metal server 110.
  • the processor 111 of the bare metal server 110 can use the data volume as the available storage space of the bare metal server 110.
  • a volume is added to the operating system of the bare metal server 110.
  • a user of the bare metal server 110 can see that the data volume is added to the operating system of the bare metal server 110 through the GUI of the operating system of the bare metal server 110.
  • the data volume can be the D drive of the bare metal server 110, or an E drive.
  • the operating system of the bare metal server 110 can access the data volume.
  • a volume is deleted in the operating system of the bare metal server 110.
  • the user of the bare metal server 110 sees that the data volume is deleted from the operating system of the bare metal server 110 through the GUI of the operating system of the bare metal server 110. After the data volume is deleted, the user cannot access the data volume through the operating system of the bare metal server 110.
  • the method for processing the request in the embodiment of the present application generates the unloading operation request carrying the volume identifier by the public cloud management component, thereby realizing the automatic unloading of the bare metal server, thereby preventing the tenant from manually unloading the unloading operation by logging in to the bare metal server, which is helpful. To achieve automated management of the volume.
  • FIG. 7 to 10 The method for processing a request according to an embodiment of the present application is described in detail above with reference to FIG. 1 to FIG. 6.
  • the system on chip and the public cloud management component according to an embodiment of the present application will be described in detail with reference to FIGS. 7 to 10.
  • the system on chip and the public cloud management component shown in FIG. 7 to FIG. 10 can be used to specifically implement the system on chip 112 shown in FIG. 2 and the public cloud management component 120 shown in FIG.
  • the system on chip and the public cloud management component shown in Figures 7 through 10 can be used to perform the methods illustrated in Figures 3, 5, and 6.
  • FIG. 7 shows a schematic block diagram of a system on chip 500 according to an embodiment of the present application.
  • the system on chip 500 includes:
  • the transceiver module 510 is configured to receive a volume request sent by the public cloud management component, where the volume request includes an identifier of the system volume, where the file of the operating system for starting the bare metal server is saved;
  • the processing module 520 is configured to save an identifier of the system volume according to the hanging volume request.
  • the identifier of the system volume is used by the bare metal server to determine the system volume, and the bare metal server is started according to the system volume. Operating system.
  • the method for processing the request in the embodiment of the present application helps to shorten the time allocated by the bare metal server, and improves the efficiency and user experience.
  • the transceiver module 510 is further configured to receive a volume operation request sent by the public cloud management component, where the volume operation request includes an identifier of the data volume;
  • the transceiver module 510 is further configured to send the identifier of the data volume to the processor of the bare metal server to indicate that the processor of the bare metal server uses the data volume as available storage space of the bare metal server.
  • the system-on-a-chip of the embodiment of the present invention generates a volume-running request to carry a volume by using a public cloud management component, so that the bare-metal server automatically suspends the volume, thereby preventing the tenant from manually loading the volume by logging in to the bare-metal server, thereby facilitating the volume implementation.
  • Automated management
  • the transceiver module 510 is further configured to receive a unwinding operation request sent by the public cloud management component, where the unwinding operation request includes an identifier of the data volume;
  • the transceiver module 510 is further configured to send the identifier of the data volume to the processor of the bare metal server to prohibit the processor of the bare metal server from using the data volume as an available storage space of the bare metal server.
  • the system-on-a-chip of the embodiment of the present application generates the unloading operation request carrying the volume identifier by using the public cloud management component, thereby realizing the automatic unloading of the bare metal server, thereby preventing the tenant from manually unloading the unloading operation by logging in to the bare metal server, thereby facilitating the volume realization. Automated management.
  • FIG. 8 is a schematic block diagram of a public cloud management component 600 according to an embodiment of the present application. As shown in FIG. 8, the public cloud management component 600 includes:
  • the processing module 610 is configured to generate a volume request, where the volume request includes an identifier of a system volume, where the file of the operating system for starting the bare metal server is saved;
  • the transceiver module 620 is configured to send the volume request to the system on a chip to instruct the system on a chip to save the identifier of the system volume according to the volume request.
  • the system volume is obtained by cloning a file of the operating system of the bare metal server by the public cloud management component.
  • the method for processing the request in the embodiment of the present application helps to shorten the time allocated by the bare metal server, and improves the efficiency and user experience.
  • the processing module 610 is further configured to generate a volume operation request, where the volume operation request includes an identifier of the data volume;
  • the transceiver module 620 is further configured to send the hanging operation request to the system on a chip to instruct the system on the chip to send an identifier of the data volume to a processor of the bare metal server, where the processor of the bare metal server uses the data volume as the bare metal The available storage space for the server.
  • the public cloud management component of the embodiment of the present application implements the hanging volume operation request to carry the volume identifier, so that the bare metal server automatically suspends the volume, thereby preventing the tenant from manually loading the volume by logging in to the bare metal server, thereby facilitating the automation of the volume. management.
  • the processing module 610 is further configured to generate a unwinding operation request, where the unwinding operation request includes an identifier of the data volume;
  • the transceiver module 620 is further configured to send the unwinding operation request to the system on a chip to instruct the system on the chip to send the identifier of the data volume to the processor of the bare metal server, and prohibit the processor of the bare metal server from using the data volume as the Available storage space for bare metal servers.
  • the public cloud management component of the embodiment of the present application implements the automatic unloading of the bare metal server by generating the unloading operation request carrying the volume identifier, thereby preventing the tenant from manually unloading the unloading operation by logging in to the bare metal server, thereby facilitating automatic management of the volume. .
  • FIG. 9 shows a schematic block diagram of a system on chip 700 according to an embodiment of the present application.
  • the system on chip 700 includes:
  • the transceiver 710 is configured to receive a volume request sent by the public cloud management component, where the volume request includes an identifier of a system volume, where the file of the operating system for starting the bare metal server is saved;
  • the processor 720 is configured to save an identifier of the system volume according to the hanging volume request.
  • the identifier of the system volume is used by the bare metal server to determine the system volume, and the bare metal server is started according to the system volume. Operating system.
  • the transceiver 710 is further configured to receive a volume operation request sent by the public cloud management component, where the volume operation request includes an identifier of the data volume;
  • the transceiver 710 is further configured to send an identifier of the data volume to a processor of the bare metal server to indicate that the processor of the bare metal server uses the data volume as available storage space of the bare metal server.
  • the transceiver 710 is further configured to receive a unmounting operation request sent by the public cloud management component, where the unwinding operation request includes an identifier of the data volume;
  • the transceiver 710 is further configured to send the identifier of the data volume to the processor of the bare metal server to prohibit the processor of the bare metal server from using the data volume as available storage space of the bare metal server.
  • FIG. 10 is a schematic block diagram of a public cloud management component 800 according to an embodiment of the present application. As shown in FIG. 10, the public cloud management component 800 includes:
  • the processor 810 is configured to generate a volume request, where the volume request includes an identifier of a system volume, where the file of the operating system for starting the bare metal server is saved;
  • the transceiver 820 is configured to send the volume request to the system on a chip to instruct the system on a chip to save the identifier of the system volume according to the volume request.
  • the processor 810 is further configured to generate a volume operation request, where the volume operation request includes an identifier of the data volume;
  • the transceiver 820 is further configured to send the hanging operation request to the system on a chip to instruct the system on the chip to send an identifier of the data volume to a processor of the bare metal server, where the processor of the bare metal server uses the data volume as the bare metal The available storage space for the server.
  • the processor 810 is further configured to generate a unwinding operation request, where the unwinding operation request includes an identifier of the data volume;
  • the transceiver 820 is further configured to send the unwinding operation request to the system on a chip to instruct the system on the chip to send the identifier of the data volume to the processor of the bare metal server, and prohibit the processor of the bare metal server from using the data volume as the Available storage space for bare metal servers.
  • the embodiment of the present application further provides a bare metal server including a processor and a system on chip, and the system on chip is any one of the system on chip 500 or the system on chip 700.
  • the embodiment of the present application further provides a system including a bare metal server and a public cloud management component, the bare metal server including a processor and a system on chip, the system on a chip being any one of a system on chip 500 or a system on chip 700; and/or
  • the public cloud management component is any one of a public cloud management component 600 or a public cloud management component 800.
  • the processor may be an integrated circuit chip with signal processing capabilities.
  • each step of the foregoing method embodiments may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA), or the like. Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory.
  • the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
  • RAM Random Access Memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM).
  • SDRAM Double Data Rate SDRAM
  • DDR SDRAM Double Data Rate SDRAM
  • ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • SLDRAM Synchronous Connection Dynamic Random Access Memory
  • DR RAM direct memory bus random access memory
  • system and “network” are used interchangeably herein.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the character "/" in this article generally indicates that the contextual object is an "or" relationship.
  • B corresponding to A means that B is associated with A, and B can be determined according to A.
  • determining B from A does not mean that B is only determined based on A, and that B can also be determined based on A and/or other information.
  • the computer program product can include one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic disk), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read only memory, a random access memory, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Human Computer Interaction (AREA)
  • Computing Systems (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Stored Programmes (AREA)

Abstract

本申请提供了一种对请求进行处理的方法、片上系统和公有云管理组件。该方法由片上系统执行。该片上系统被包含在裸机服务器中。该裸机服务器还包括处理器。该裸机服务器被包含在分布式存储系统中。该分布式存储系统还包括公有云管理组件。该方法包括：该片上系统接收该公有云管理组件发送的挂卷请求，该挂卷请求包括系统卷的标识；该片上系统根据该挂卷请求，保存该系统卷的标识，该裸机服务器启动时，该系统卷的标识被该裸机服务器用于确定该系统卷，并根据该系统卷启动该裸机服务器的操作系统，该系统卷中保存了用于启动该裸机服务器的操作系统的文件。本申请实施例的对请求进行处理的方法，有助于裸机服务器的快速分配，提高效率和用户体验。

Description

对请求处理的方法、片上系统和公有云管理组件 技术领域
本申请涉及存储领域，并且更具体地，涉及对请求处理的方法、片上系统和公有云管理组件。
背景技术
预启动执行环境(Preboot Execute Environment，PXE)是由Intel设计的协议，工作于客户端/服务端的网络模式，它可以支持裸机服务器通过网络从远端服务器(另外一台服务器)下载操作系统，并由此支持裸机服务器通过网络启动操作系统，实现裸机服务器的发放。
例如，当租户需要通过界面申请裸机服务器时，裸机服务器的基本输入输出系统(Basic Input Output System，BIOS)将PXE客户端(BIOS中的一个软件)调入内存中执行，PXE客户端会向PXE服务端(远端服务器)请求该裸机服务器待安装的操作系统，PXE服务端将该操作系统保存在裸机服务器的内存中，裸机服务器通过启动内存中的操作系统，从而实现裸机服务器的发放。
但是，通过PXE客户端向PXE服务端请求操作系统这个过程需要10分钟左右，整个流程复杂且耗时较长。因此，如何实现裸机服务器的快速分配，提高效率和用户体验成为了一个亟待解决的问题。
发明内容
本申请提供对请求处理的方法、片上系统和公有云管理组件，有助于实现公有云裸机场景下快速分配，缩短了裸机服务器分配的时间，提高了效率和用户体验。
第一方面，提供了一种对请求进行处理的方法，该方法由片上系统执行，该片上系统被包含在裸机服务器中，该裸机服务器还包括处理器，该裸机服务器被包含在分布式存储系统中，该分布式存储系统还包括公有云管理组件，该方法包括：该片上系统接收该公有云管理组件发送的挂卷请求，该挂卷请求包括系统卷的标识；该片上系统根据该挂卷请求，保存该系统卷的标识，该裸机服务器启动时，该系统卷的标识被该裸机服务器用于确定该系统卷，并根据该系统卷启动该裸机服务器的操作系统，该系统卷中保存了用于启动该裸机服务器的操作系统的文件。
在一些可能的实现方式中，该系统卷由该公有云管理组件对该裸机服务器的操作系统的文件进行克隆获得。
本申请实施例的对请求进行处理的方法，有助于缩短裸机服务器分配的时间，提高了效率和用户体验。
结合第一方面，在第一方面的第一种可能的实现方式中，在该裸机服务器根据该 系统卷启动该裸机服务器的操作系统后，该方法还包括：该片上系统接收该公有云管理组件发送的挂卷操作请求，该挂卷操作请求包括数据卷的标识；该片上系统发送该数据卷的标识至该处理器，以指示该处理器将该数据卷作为该裸机服务器的可用存储空间。
本申请实施例的对请求进行处理的方法，通过公有云管理组件生成挂卷操作请求携带卷的标识，实现了裸机服务器自动挂卷，避免了租户通过登录裸机服务器手动进行挂载卷操作，有助于实现卷的自动化管理。
结合第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，该片上系统发送该数据卷的标识至该处理器，以指示该处理器将该数据卷作为该裸机服务器的可用存储空间之后，该方法还包括：该片上系统接收该公有云管理组件发送的卸卷操作请求，该卸卷操作请求包括该数据卷的标识；该片上系统发送该数据卷的标识至该处理器，以禁止该处理器将该数据卷作为该裸机服务器的可用存储空间。
本申请实施例的对请求进行处理的方法，通过公有云管理组件生成卸卷操作请求携带卷的标识，实现了裸机服务器自动卸卷，避免了租户通过登录裸机服务器手动进行卸卷操作，有助于实现卷的自动化管理。
第二方面，提供了一种对请求进行处理的方法，该方法由公有云管理组件执行，该公有云管理组件被包含在分布式存储系统中，该分布式存储系统还包括裸机服务器，该裸机服务器包括片上系统，该方法包括：该公有云管理组件生成挂卷请求，该挂卷请求包括系统卷的标识,该系统卷中保存了用于启动该裸机服务器的操作系统的文件；该公有云管理组件向该片上系统发送该挂卷请求，以指示该片上系统根据该挂卷请求，保存该系统卷的标识。
在一些可能的实现方式中，该系统卷由该公有云管理组件对该裸机服务器的操作系统的文件进行克隆获得。
本申请实施例的对请求进行处理的方法，有助于缩短裸机服务器分配的时间，提高了效率和用户体验。
结合第二方面，在第二方面的第一种可能的实现方式中，在该裸机服务器根据该系统卷启动该裸机服务器的操作系统后，该方法还包括：该公有云管理组件生成挂卷操作请求，该挂卷操作请求包括数据卷的标识；该公有云管理组件向该片上系统发送该挂卷操作请求，以指示该片上系统发送该数据卷的标识至该处理器，该处理器将该数据卷作为该裸机服务器的可用存储空间。
本申请实施例的对请求进行处理的方法，通过公有云管理组件生成挂卷操作请求携带卷的标识，实现了裸机服务器自动挂卷，避免了租户通过登录裸机服务器手动进行挂载卷操作，有助于实现卷的全自动化管理。
结合第二方面的第一种可能的实现方式，在第二方面的第二种可能的实现方式中，该片上系统发送该数据卷的标识至该处理器，该处理器将该数据卷作为该裸机服务器的可用存储空间之后，该方法还包括：该公有云管理组件生成卸卷操作请求，该卸卷操作请求包括该数据卷的标识；该公有云管理组件向该片上系统发送该卸卷操作请求，以指示该片上系统发送该数据卷的标识至该处理器，禁止该处理器将该数据卷作为该裸机服务器的可用存储空间。
本申请实施例的对请求进行处理的方法，通过公有云管理组件生成卸卷操作请求携带卷的标识，实现了裸机服务器自动卸卷，避免了租户通过登录裸机服务器手动进行卸卷操作，有助于实现卷的自动化管理。
第三方面，提供了一种片上系统，该片上系统包括：收发模块，用于接收公有云管理组件发送的挂卷请求，该挂卷请求包括系统卷的标识；处理模块，用于根据该挂卷请求，保存该系统卷的标识，裸机服务器启动时，该系统卷的标识被该裸机服务器用于确定该系统卷，并根据该系统卷启动该裸机服务器的操作系统，该系统卷中保存了用于启动该裸机服务器的操作系统的文件。
在一些可能的实现方式中，该系统卷由该公有云管理组件对该裸机服务器的操作系统的文件进行克隆获得。
本申请实施例的对请求进行处理的方法，有助于缩短裸机服务器分配的时间，提高了效率和用户体验。
结合第三方面，在第三方面的第一种可能的实现方式中，该收发模块还用于接收该公有云管理组件发送的挂卷操作请求，该挂卷操作请求包括数据卷的标识；该收发模块还用于发送该数据卷的标识至该裸机服务器的处理器，以指示该裸机服务器的处理器将该数据卷作为该裸机服务器的可用存储空间。
本申请实施例的片上系统，通过公有云管理组件生成挂卷操作请求携带卷的标识，实现了裸机服务器自动挂卷，避免了租户通过登录裸机服务器手动进行挂载卷操作，有助于实现卷的自动化管理。
结合第三方面的第一种可能的实现方式，在第三方面的第二种可能的实现方式中，该收发模块还用于接收该公有云管理组件发送的卸卷操作请求，该卸卷操作请求包括该数据卷的标识；该收发模块还用于发送该数据卷的标识至该裸机服务器的处理器，以禁止该裸机服务器的处理器将该数据卷作为该裸机服务器的可用存储空间。
本申请实施例的片上系统，通过公有云管理组件生成卸卷操作请求携带卷的标识，实现了裸机服务器自动卸卷，避免了租户通过登录裸机服务器手动进行卸卷操作，有助于实现卷的自动化管理。
第四方面，提供了一种公有云管理组件，该公有云管理组件包括：处理模块，用于生成挂卷请求，该挂卷请求包括系统卷的标识,该系统卷中保存了用于启动裸机服务器的操作系统的文件；收发模块，用于向该片上系统发送该挂卷请求，以指示片上系统根据该挂卷请求，保存该系统卷的标识。
在一些可能的实现方式中，该系统卷由该公有云管理组件对该裸机服务器的操作系统的文件进行克隆获得。
本申请实施例的对请求进行处理的方法，有助于缩短裸机服务器分配的时间，提高了效率和用户体验。
结合第四方面，在第四方面的第一种可能的实现方式中，该处理模块还用于生成挂卷操作请求，该挂卷操作请求包括数据卷的标识；该收发模块还用于向该片上系统发送该挂卷操作请求，以指示该片上系统发送该数据卷的标识至该裸机服务器的处理器，该裸机服务器的处理器将该数据卷作为该裸机服务器的可用存储空间。
本申请实施例的公有云管理组件，通过生成挂卷操作请求携带卷的标识，实现了 裸机服务器自动挂卷，避免了租户通过登录裸机服务器手动进行挂载卷操作，有助于实现卷的自动化管理。
结合第四方面的第一种可能的实现方式，在第四方面的第二种可能的实现方式中，该处理模块还用于生成卸卷操作请求，该卸卷操作请求包括该数据卷的标识；该收发模块还用于向该片上系统发送该卸卷操作请求，以指示该片上系统发送该数据卷的标识至该裸机服务器的处理器，禁止该裸机服务器的处理器将该数据卷作为该裸机服务器的可用存储空间。
本申请实施例的公有云管理组件，通过生成卸卷操作请求携带卷的标识，实现了裸机服务器自动卸卷，避免了租户通过登录裸机服务器手动进行卸卷操作，有助于实现卷的自动化管理。
第五方面，提供了一种片上系统，该片上系统包括：收发器，用于接收公有云管理组件发送的挂卷请求，该挂卷请求包括系统卷的标识；处理器，用于根据该挂卷请求，保存该系统卷的标识，裸机服务器启动时，该系统卷的标识被该裸机服务器用于确定该系统卷，并根据该系统卷启动该裸机服务器的操作系统，该系统卷中保存了用于启动该裸机服务器的操作系统的文件。
结合第五方面，在第五方面的第一种可能的实现方式中，该收发器还用于接收该公有云管理组件发送的挂卷操作请求，该挂卷操作请求包括数据卷的标识；该收发器还用于发送该数据卷的标识至该裸机服务器的处理器，以指示该裸机服务器的处理器将该数据卷作为该裸机服务器的可用存储空间。
结合第五方面的第一种可能的实现方式，在第五方面的第二种可能的实现方式中，该收发器还用于接收该公有云管理组件发送的卸卷操作请求，该卸卷操作请求包括该数据卷的标识；该收发器还用于发送该数据卷的标识至该裸机服务器的处理器，以禁止该裸机服务器的处理器将该数据卷作为该裸机服务器的可用存储空间。
第六方面，提供了一种公有云管理组件，该公有云管理组件包括：处理器，用于生成挂卷请求，该挂卷请求包括系统卷的标识,该系统卷中保存了用于启动裸机服务器的操作系统的文件；收发器，用于向该片上系统发送该挂卷请求，以指示片上系统根据该挂卷请求，保存该系统卷的标识。
结合第六方面，在第六方面的第一种可能的实现方式中，该处理器还用于生成挂卷操作请求，该挂卷操作请求包括数据卷的标识；该收发器还用于向该片上系统发送该挂卷操作请求，以指示该片上系统发送该数据卷的标识至该裸机服务器的处理器，该裸机服务器的处理器将该数据卷作为该裸机服务器的可用存储空间。
结合第六方面的第一种可能的实现方式，在第六方面的第二种可能的实现方式中该处理器还用于生成卸卷操作请求，该卸卷操作请求包括该数据卷的标识；该收发器还用于向该片上系统发送该卸卷操作请求，以指示该片上系统发送该数据卷的标识至该裸机服务器的处理器，禁止该裸机服务器的处理器将该数据卷作为该裸机服务器的可用存储空间。
第七方面，提供了一种裸机服务器，该裸机服务器包括处理器和片上系统，其中，该片上系统为上述第三方面及第三方面任一种可能的实现方式和上述第五方面及第五方面的任一种可能的实现方式中的片上系统。
第八方面，提供了一种系统，该系统包括裸机服务器和公有云管理组件，该裸机服务器包括片上系统和处理器，其中，该片上系统为上述第三方面及第三方面任一种可能的实现方式和上述第五方面及第五方面的任一种可能的实现方式中的片上系统；和/或该公有云管理组件为上述第四方面及第四方面任一种可能的实现方式和上述第六方面及第六方面的任一种可能的实现方式中的公有云管理组件。
附图说明
图1是根据本申请实施例的分布式存储系统的示意性框图。
图2是图1所示的分布式存储系统中的裸机服务器的示意性框图。
图3是根据本申请实施例的对请求进行处理的方法的示意性流程图。
图4是根据本申请实施例的分布式存储系统的另一示意性框图。
图5是根据本申请实施例的对请求进行处理的方法的另一示意性流程图。
图6是根据本申请实施例的对请求进行处理的方法的再一示意性流程图。
图7是根据本申请实施例的片上系统的示意性框图。
图8是根据本申请实施例的公有云管理组件的示意性框图。
图9是根据本申请实施例的片上系统的另一示意性框图。
图10是根据本申请实施例的公有云管理组件的另一示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例适用于任何分布式存储的架构以及非OpenStack公有云管理架构中。
图1示出了根据本申请实施例的分布式存储系统100的示意性结构图，如图1所示，该分布式存储系统100包括裸机服务器110和公有云管理组件120，该裸机服务器110和该公有云管理组件120通过网络进行通信。
图2示出了图1所示的分布式存储系统100中的裸机服务器110的示意性框图。如图2所示，该裸机服务器110包括处理器111和片上系统(System On Chip，SOC)112，该片上系统112可以嵌入该裸机服务器110中。
应理解，该处理器111可以通过部件快速互连局部总线(Peripheral Component Interconnect Express，PCIe)与该片上系统112进行通信，该片上系统112通过网络和该公有云管理组件120进行通信。
图3示出了根据本申请实施例的对请求处理的方法200的示意性流程图，如图3所示，该方法200包括S210至S240。图3所示的方法可以被图1所示的分布式存储系统100执行。其中，S210和S220可以被图1所示的分布式存储系统100中的公有云管理组件120执行。S230可以被图1所示的分布式存储系统100中的片上系统112执行。S240可以被图1所示的分布式存储系统100中的裸机服务器110执行。
S210，公有云管理组件120生成挂卷请求，该挂卷请求包括系统卷的标识，该系统卷中保存了用于启动该裸机服务器110的操作系统的文件。
应理解，裸机服务器110包括处理器111和片上系统112，虽然片上系统112是该裸机服务器110的部件，但是该裸机服务器110的操作系统并不是片上系统112的 操作系统。举例来说，裸机服务器110可以包括中央处理单元以及与所述中央处理单元耦合的存储器。裸机服务器110的操作系统可以保存在所述存储器中。所述中央处理单元可以通过访问所述存储器，运行所述裸机服务器110的操作系统。
S220，该公有云管理组件120向该片上系统112发送该挂卷请求；
S230，该片上系统112根据该挂卷请求，保存该系统卷的标识。
应理解，该片上系统112根据该挂卷请求，挂载该系统卷至该片上系统112的操作系统中，该片上系统112的操作系统中会增加一个卷。例如，用户可以通过该片上系统112的操作系统的图像用户界面(Graphical User Interface，GUI)，看到该片上系统112的操作系统中增加了该系统卷。例如，该系统卷可以是该片上系统112的C盘。该片上系统112的操作系统可以访问该系统卷。
S240，该裸机服务器110启动时，根据该系统卷的标识确定该系统卷，并根据该系统卷启动该裸机服务器110的操作系统。
例如，该裸机服务器110根据该系统卷启动该裸机服务器110的操作系统具体包括：该裸机服务器110运行该系统卷中保存的用于启动所述裸机服务器的操作系统的文件，启动该裸机服务器110的操作系统。
举例来说，片上系统112的操作系统可以是Windows 7，或者Linux。
应理解，S240该裸机服务器110根据系统卷启动裸机服务器110时，该裸机服务器110会增加一个系统卷，例如，该系统卷可以为该裸机服务器110的C盘。
可选地，图4示出了根据本申请实施例的分布式存储系统100的另一示意性结构图。可以对图1所示的分布式存储系统100进行扩展，从而得到图4所示的分布式存储系统100。如图4所示，该分布式存储系统还包括存储池130。该系统卷由该公有云管理组件120对该裸机服务器110的操作系统的文件进行克隆获得，该公有云管理组件120在对该操作系统的文件进行克隆前，可以从存储池130中获取该操作系统的文件。
可选地，该裸机服务器110的处理器111保存前端驱动1111，该片上系统112保存后端驱动1121、分布式存储软件客户端1122和管理代理软件1123。具体而言，需要申请裸机服务器110的租户通过租户所在的本地客户端界面申请裸机服务器110时，公有云管理组件120根据租户所在的本地客户端发送的请求，生成挂卷请求，该挂卷请求包括系统卷的标识。该公有云管理组件120向该片上系统112发送该挂卷请求。片上系统112通过管理代理软件1123确定该挂卷请求需要由分布式存储软件客户端1122处理。该分布式存储软件客户端1122根据该挂卷请求将该系统卷挂载到该片上系统112的操作系统中，具体的，片上系统112通过分布式存储软件客户端1122保存该系统卷的标识和系统卷的信息的对应关系。该系统卷的信息用于该裸机服务器110的启动。当裸机服务器110启动时，该对应关系被该裸机服务器110的处理器111用于根据该系统卷的标识获取该系统卷的信息，并根据该系统卷的信息访问系统卷中保存的该裸机服务器110的操作系统的文件，根据该系统卷启动该裸机服务器110的操作系统。
应理解，该对应关系具体被保存在映射表中。例如，所述映射表可以包含一个记录有系统卷的信息和系统卷的标识的表项。系统卷的信息包括系统卷的大小、系统卷 的逻辑区块地址(Logical Block Address，LBA)，系统卷的标识包括系统卷的存储地址或通用唯一标识码(Universally Unique Identifier，UUID)。
还应理解，公有云管理组件创建的所有卷的标识是不同的，系统卷的标识是唯一标识。
裸机服务器110启动时，处理器111首先从该片上系统112获取系统卷的标识，该处理器111根据该系统卷的标识确定该系统卷的信息。处理器111以系统卷的标识为查找关键字，在映射表中查找与该系统卷的标识匹配的表项。处理器111根据匹配的表项，确定系统卷的信息，处理器111根据系统卷的信息，启动该裸机服务器110的操作系统的文件。具体地，该裸机服务器110将所述系统卷作为该裸机服务器110的操作系统运行所述系统卷。
例如，裸机服务器110启动时，处理器111加载基本输入输出系统(Basic Input Output System，BIOS)，从而查找到该片上系统112，该片上系统112运行该片上系统112的扩展只读内存(Expansion ROM)保存的片上系统112的驱动程序，从而获得系统卷的标识，该片上系统112将该系统卷的标识发送给该裸机服务器110的处理器111，该裸机服务器110的处理器111根据该系统卷的标识，向该片上系统112发送卷查询命令，该卷查询命令携带该系统卷的标识，片上系统112收到该卷查询命令后，对该卷查询命令进行解析，从而查找该片上系统112保存的映射表，该映射表保存有系统卷的标识和系统卷的信息的映射关系，该系统卷的信息包括系统卷的LBA，该片上系统112将该系统卷的信息中LBA发给该处理器111，该处理器111可以运行引导加载器(boot loader)。处理器可以利用boot loader访问LBA指示的所述系统卷。具体地，处理器可以利用boot loader从所述系统卷中获取启动所述裸机服务器的操作系统的文件。所述处理器运行启动所述裸机服务器的操作系统的文件，从而启动所述裸机服务器的操作系统。例如，所述裸机服务器的操作系统可以是Windows 9x，启动所述裸机服务器的操作系统的文件可以是IO.SYS。例如，所述裸机服务器的操作系统可以是MS-DOS，启动所述裸机服务器的操作系统的文件可以是MSDOS.SYS。
应理解，该处理器111获取该LBA后，该系统卷对该裸机服务器110是可见的。
根据上述技术方案可以看出，系统卷的信息保存在片上系统112中。片上系统112是裸机服务器110的部件。因此，裸机服务器110可以根据片上系统112预先保存的系统卷的标识和系统卷的信息的所述对应关系，获取裸机服务器110的操作系统的信息，并根据系统卷运行操作系统。上述技术方案中，避免了服务器启动时通过启动PXE客户端从远端服务器下载映像，仅通过系统卷的信息获取启动该裸机服务器110的操作系统的文件，进而根据系统卷启动裸机服务器110的操作系统，缩短了裸机服务器110先启动PXE客户端，再从远端服务器下载映像，然后再启动安装操作系统的分配时间，提高了效率和用户体验。
还应理解，当租户需要释放裸机服务器110时，只需要将该系统卷挂载到公有云管理组件120上，此台物理机器可以被其他租户使用，公有云管理组件120将该系统卷安全擦除。
本申请实施例的对请求处理的方法，实现了裸机服务器的快速分配和回收，从10分钟缩短到秒级，提高了效率和用户体验。
图5示出了根据本申请实施例的对请求处理的方法300的示意性流程图。如图5所示，该方法300包括S310至S340。图5所示的方法可以被图1所示的分布式存储系统100执行。举例来说，图5所示的方法的执行主体与图3所示的方法的执行主体可以是同一个执行主体。图5所示的方法的执行时间可以晚于图3所示的方法的执行时间。
S310，该公有云管理组件120生成挂卷操作请求，该挂卷操作请求包括数据卷的标识；
S320，在该裸机服务器110根据该系统卷启动该裸机服务器的操作系统后，该公有云管理组件120向该片上系统112发送该挂卷操作请求；
S330，该片上系统112向该裸机服务器110的处理器111发送该数据卷的标识；
S340，该裸机服务器110的处理器111将该数据卷作为该裸机服务器110的可用存储空间。
可选地，在该公有云管理组件120向该片上系统112发送该挂卷操作请求之前，该方法300还包括：
该公有云管理组件120通过裸机服务器110和片上系统112的对应关系表查找到该片上系统112对应的网络地址。
具体而言，该公有云管理组件120将挂卷操作请求发送到对应的片上系统112的管理代理软件1123，该挂卷操作请求包括数据卷的标识。片上系统112通过管理代理软件1123确定该挂卷操作请求需要由分布式存储软件客户端1122处理，该片上系统112根据该分布式存储软件客户端1122，将该数据卷挂载至该片上系统112的操作系统中，然后该片上系统112确定该数据卷的标识需要发送至处理器111，该片上系统112通过该管理代理软件1123将该挂卷操作请求发送到该片上系统112保存的后端驱动1121，该片上系统112根据该后端驱动1121，在PCIe通道上将该数据卷的标识发送到该的处理器111保存的前端驱动1111中，该处理器111根据该前端驱动1111将该数据卷作为该裸机服务器110的可用存储空间。
应理解，若该处理器111的前端驱动1111不存在，该挂卷操作命令保存在后端驱动1121中，当前端驱动1111加载时会将所有之前挂载的卷都添加到该裸机服务器110的操作系统中。
还应理解，该数据卷可以为扩容前的卷，也可以为扩容后的卷，本申请对此不作任何限定。
还应理解，该裸机服务器110的处理器111将该数据卷作为该裸机服务器110的可用存储空间，该裸机服务器110会增加一个数据卷，例如，该数据卷可以为该裸机服务器的D盘或者E盘。
现有技术中，租户需要通过管理界面(OpenStack管理软件提供)配置卷信息(卷大小、类型)，然后OpenStack管理软件创建卷，并将卷标识信息，例如，全球唯一名字(World Wide Name，WWN)或小型计算机接口限定名称(iSCSI Qualified Name，IQN)通过界面反馈给租户，租户再登录裸机服务器110手动挂载卷，该过程较难和OpenStack管理软件提供的管理界面关联，本申请实施例的对请求处理的方法，可以实现卷的自动化管理，对卷的操作无需手动介入。
本申请实施例的对请求进行处理的方法，通过公有云管理组件生成挂卷操作请求携带卷的标识，实现了裸机服务器自动挂卷，避免了租户通过登录裸机服务器手动进行挂载卷操作，有助于实现卷的自动化管理。
图6示出了根据本申请实施例的对请求处理的方法400的示意性流程图。如图6所示，该方法400包括S410至S440。图6所示的方法可以被图1所示的分布式存储系统100执行。举例来说，图6所示的方法的执行主体与图5所示的方法的执行主体可以是同一个执行主体。图6所示的方法的执行时间可以晚于图5所示的方法的执行时间。
S410，该片上系统发送该数据卷的标识至该处理器，以指示该处理器将该数据卷作为该裸机服务器的可用存储空间之后，该公有云管理组件120生成卸卷操作请求，该卸卷操作请求包括该数据卷的标识；
S420，该公有云管理组件120向该片上系统112接收发送的卸卷操作请求；
S430，该片上系统112向该处理器111发送该数据卷的标识；
S440，该处理器111根据该数据卷的标识，避免将该数据卷作为该裸机服务器110的可用存储空间。
应理解，该卸卷操作请求可以在方法300中的挂卷操作请求之后，具体的处理流程与方法300中的类似，不同之处在于该处理器111获得该数据卷的标识后，避免将该数据卷作为该裸机服务器110的可用存储空间。
应理解，S440之前，处理器111能够将该数据卷作为该裸机服务器110的可用存储空间。例如，根据S340，裸机服务器110的处理器111能够将该数据卷作为该裸机服务器110的可用存储空间。
举例来说，基于S340，裸机服务器110的操作系统中会增加一个卷。例如，裸机服务器110的用户可以通过裸机服务器110的操作系统的GUI，看到裸机服务器110的操作系统中增加了该数据卷。例如，该数据卷可以是该裸机服务器110的D盘，或者E盘。该裸机服务器110的操作系统可以访问该数据卷。
举例来说，基于S440，裸机服务器110的操作系统中会删除一个卷。例如，裸机服务器110的用户通过裸机服务器110的操作系统的GUI，看到该数据卷从裸机服务器110的操作系统中删除。数据卷被删除后，用户不能够通过裸机服务器110的操作系统访问该数据卷。
本申请实施例的对请求进行处理的方法，通过公有云管理组件生成卸卷操作请求携带卷的标识，实现了裸机服务器自动卸卷，避免了租户通过登录裸机服务器手动进行卸卷操作，有助于实现卷的自动化管理。
上文结合图1至图6，详细得描述了根据本申请实施例的对请求处理的方法，下文将结合图7至10，详细描述根据本申请实施例的片上系统和公有云管理组件。需要说明的是，图7至10所示的片上系统和公有云管理组件，可以分别用于具体实现图2所示的片上系统112和图1所示的公有云管理组件120。图7至10所示的片上系统和公有云管理组件，可以用于执行图3、图5以及图6所示的方法。
图7示出了根据本申请实施例的片上系统500的示意性框图，如图7所示，该片上系统500包括：
收发模块510，用于接收公有云管理组件发送的挂卷请求，该挂卷请求包括系统卷的标识，该系统卷中保存了用于启动裸机服务器的操作系统的文件；
处理模块520，用于根据该挂卷请求，保存该系统卷的标识，该裸机服务器启动时，该系统卷的标识被该裸机服务器用于确定该系统卷，并根据该系统卷启动该裸机服务器的操作系统。
本申请实施例的对请求进行处理的方法，有助于缩短裸机服务器分配的时间，提高了效率和用户体验。
可选地，该收发模块510还用于接收该公有云管理组件发送的挂卷操作请求，该挂卷操作请求包括数据卷的标识；
该收发模块510还用于发送该数据卷的标识至该裸机服务器的处理器，以指示该裸机服务器的处理器将该数据卷作为该裸机服务器的可用存储空间。
本申请实施例的片上系统，通过公有云管理组件生成挂卷操作请求携带卷的标识，实现了裸机服务器自动挂卷，避免了租户通过登录裸机服务器手动进行挂载卷操作，有助于实现卷的自动化管理。
可选地，该收发模块510还用于接收该公有云管理组件发送的卸卷操作请求，该卸卷操作请求包括该数据卷的标识；
该收发模块510还用于发送该数据卷的标识至该裸机服务器的处理器，以禁止该裸机服务器的处理器将该数据卷作为该裸机服务器的可用存储空间。
本申请实施例的片上系统，通过公有云管理组件生成卸卷操作请求携带卷的标识，实现了裸机服务器自动卸卷，避免了租户通过登录裸机服务器手动进行卸卷操作，有助于实现卷的自动化管理。
图8示出了根据本申请实施例的公有云管理组件600的示意性框图，如图8所示，该公有云管理组件600包括：
处理模块610，用于生成挂卷请求，该挂卷请求包括系统卷的标识,该系统卷中保存了用于启动裸机服务器的操作系统的文件；
收发模块620，用于向该片上系统发送该挂卷请求，以指示片上系统根据该挂卷请求，保存该系统卷的标识。
在一些可能的实现方式中，该系统卷由该公有云管理组件对该裸机服务器的操作系统的文件进行克隆获得。
本申请实施例的对请求进行处理的方法，有助于缩短裸机服务器分配的时间，提高了效率和用户体验。
可选地，该处理模块610还用于生成挂卷操作请求，该挂卷操作请求包括数据卷的标识；
该收发模块620还用于向该片上系统发送该挂卷操作请求，以指示该片上系统发送该数据卷的标识至该裸机服务器的处理器，该裸机服务器的处理器将该数据卷作为该裸机服务器的可用存储空间。
本申请实施例的公有云管理组件，通过生成挂卷操作请求携带卷的标识，实现了裸机服务器自动挂卷，避免了租户通过登录裸机服务器手动进行挂载卷操作，有助于实现卷的自动化管理。
可选地，该处理模块610还用于生成卸卷操作请求，该卸卷操作请求包括该数据卷的标识；
该收发模块620还用于向该片上系统发送该卸卷操作请求，以指示该片上系统发送该数据卷的标识至该裸机服务器的处理器，禁止该裸机服务器的处理器将该数据卷作为该裸机服务器的可用存储空间。
本申请实施例的公有云管理组件，通过生成卸卷操作请求携带卷的标识，实现了裸机服务器自动卸卷，避免了租户通过登录裸机服务器手动进行卸卷操作，有助于实现卷的自动化管理。
图9示出了根据本申请实施例的片上系统700的示意性框图，如图9所示，该片上系统700包括：
收发器710，用于接收公有云管理组件发送的挂卷请求，该挂卷请求包括系统卷的标识，该系统卷中保存了用于启动裸机服务器的操作系统的文件；
处理器720，用于根据该挂卷请求，保存该系统卷的标识，该裸机服务器启动时，该系统卷的标识被该裸机服务器用于确定该系统卷，并根据该系统卷启动该裸机服务器的操作系统。
可选地，该收发器710还用于接收该公有云管理组件发送的挂卷操作请求，该挂卷操作请求包括数据卷的标识；
该收发器710还用于发送该数据卷的标识至该裸机服务器的处理器，以指示该裸机服务器的处理器将该数据卷作为该裸机服务器的可用存储空间。
可选地，该收发器710还用于接收该公有云管理组件发送的卸卷操作请求，该卸卷操作请求包括该数据卷的标识；
该收发器710还用于发送该数据卷的标识至该裸机服务器的处理器，以禁止该裸机服务器的处理器将该数据卷作为该裸机服务器的可用存储空间。
图10示出了根据本申请实施例的公有云管理组件800的示意性框图，如图10所示，该公有云管理组件800包括：
处理器810，用于生成挂卷请求，该挂卷请求包括系统卷的标识,该系统卷中保存了用于启动裸机服务器的操作系统的文件；
收发器820，用于向该片上系统发送该挂卷请求，以指示片上系统根据该挂卷请求，保存该系统卷的标识。
可选地，该处理器810还用于生成挂卷操作请求，该挂卷操作请求包括数据卷的标识；
该收发器820还用于向该片上系统发送该挂卷操作请求，以指示该片上系统发送该数据卷的标识至该裸机服务器的处理器，该裸机服务器的处理器将该数据卷作为该裸机服务器的可用存储空间。
可选地，该处理器810还用于生成卸卷操作请求，该卸卷操作请求包括该数据卷的标识；
该收发器820还用于向该片上系统发送该卸卷操作请求，以指示该片上系统发送该数据卷的标识至该裸机服务器的处理器，禁止该裸机服务器的处理器将该数据卷作为该裸机服务器的可用存储空间。
本申请实施例还提供了一种裸机服务器，该裸机服务器包括处理器和片上系统，该片上系统为片上系统500或片上系统700中的任意一种。
本申请实施例还提供了一种系统，包括裸机服务器和公有云管理组件，该裸机服务器包括处理器和片上系统，该片上系统为片上系统500或片上系统700中的任意一种；和/或，该公有云管理组件为公有云管理组件600或公有云管理组件800中的任意一种。
在本申请实施例中，应注意，本申请实施例上述的方法实施例可以应用于处理器中，或者由处理器实现。处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
另外，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品可以包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁盘)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以 存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式。熟悉本技术领域的技术人员可以在本申请揭露的技术方案，想到变化或替换的技术方案。

Claims (20)

  1. 一种对请求进行处理的方法，其特征在于，所述方法由片上系统执行，所述片上系统被包含在裸机服务器中，所述裸机服务器还包括处理器，所述裸机服务器被包含在分布式存储系统中，所述分布式存储系统还包括公有云管理组件，所述方法包括：
    所述片上系统接收所述公有云管理组件发送的挂卷请求，所述挂卷请求包括系统卷的标识，所述系统卷中保存了用于启动所述裸机服务器的操作系统的文件；
    所述片上系统根据所述挂卷请求，保存所述系统卷的标识，所述裸机服务器启动时，所述系统卷的标识被所述裸机服务器用于确定所述系统卷，并根据所述系统卷启动所述裸机服务器的操作系统。
  2. 根据权利要求1所述的方法，其特征在于，在所述裸机服务器根据所述系统卷启动所述裸机服务器的操作系统后，所述方法还包括：
    所述片上系统接收所述公有云管理组件发送的挂卷操作请求，所述挂卷操作请求包括数据卷的标识；
    所述片上系统发送所述数据卷的标识至所述处理器，以指示所述处理器将所述数据卷作为所述裸机服务器的可用存储空间。
  3. 根据权利要求2所述的方法，其特征在于，所述片上系统发送所述数据卷的标识至所述处理器，以指示所述处理器将所述数据卷作为所述裸机服务器的可用存储空间之后，所述方法还包括：
    所述片上系统接收所述公有云管理组件发送的卸卷操作请求，所述卸卷操作请求包括所述数据卷的标识；
    所述片上系统发送所述数据卷的标识至所述处理器，以禁止所述处理器将所述数据卷作为所述裸机服务器的可用存储空间。
  4. 一种对请求进行处理的方法，其特征在于，所述方法由公有云管理组件执行，所述公有云管理组件被包含在分布式存储系统中，所述分布式存储系统还包括裸机服务器，所述裸机服务器包括片上系统，所述方法包括：
    所述公有云管理组件生成挂卷请求，所述挂卷请求包括系统卷的标识,所述系统卷中保存了用于启动所述裸机服务器的操作系统的文件；
    所述公有云管理组件向所述片上系统发送所述挂卷请求，以指示所述片上系统根据所述挂卷请求，保存所述系统卷的标识。
  5. 根据权利要求4所述的方法，其特征在于，在所述裸机服务器根据所述系统卷启动所述裸机服务器的操作系统后，所述方法还包括：
    所述公有云管理组件生成挂卷操作请求，所述挂卷操作请求包括数据卷的标识；
    所述公有云管理组件向所述片上系统发送所述挂卷操作请求，以指示所述片上系统发送所述数据卷的标识至所述处理器，所述处理器将所述数据卷作为所述裸机服务器的可用存储空间。
  6. 根据权利要求5所述的方法，其特征在于，所述片上系统发送所述数据卷的标识至所述处理器，所述处理器将所述数据卷作为所述裸机服务器的可用存储空间之后，所述方法还包括：
    所述公有云管理组件生成卸卷操作请求，所述卸卷操作请求包括所述数据卷的标识；
    所述公有云管理组件向所述片上系统发送所述卸卷操作请求，以指示所述片上系统发送所述数据卷的标识至所述处理器，禁止所述处理器将所述数据卷作为所述裸机服务器的可用存储空间。
  7. 一种片上系统，其特征在于，包括：
    收发模块，用于接收公有云管理组件发送的挂卷请求，所述挂卷请求包括系统卷的标识，所述系统卷中保存了用于启动裸机服务器的操作系统的文件；
    处理模块，用于根据所述挂卷请求，保存所述系统卷的标识，所述裸机服务器启动时，所述系统卷的标识被所述裸机服务器用于确定所述系统卷，并根据所述系统卷启动所述裸机服务器的操作系统。
  8. 根据权利要求7所述的片上系统，其特征在于，所述收发模块还用于接收所述公有云管理组件发送的挂卷操作请求，所述挂卷操作请求包括数据卷的标识；
    所述收发模块还用于发送所述数据卷的标识至所述裸机服务器的处理器，以指示所述裸机服务器的处理器将所述数据卷作为所述裸机服务器的可用存储空间。
  9. 根据权利要求8所述的片上系统，其特征在于，所述收发模块还用于接收所述公有云管理组件发送的卸卷操作请求，所述卸卷操作请求包括所述数据卷的标识；
    所述收发模块还用于发送所述数据卷的标识至所述裸机服务器的处理器，以禁止所述裸机服务器的处理器将所述数据卷作为所述裸机服务器的可用存储空间。
  10. 一种公有云管理组件，其特征在于，包括：
    处理模块，用于生成挂卷请求，所述挂卷请求包括系统卷的标识，所述系统卷中保存了用于启动裸机服务器的操作系统的文件；
    收发模块，用于向所述片上系统发送所述挂卷请求，以指示片上系统根据所述挂卷请求，保存所述系统卷的标识。
  11. 根据权利要求10所述的公有云管理组件，其特征在于，所述处理模块还用于生成挂卷操作请求，所述挂卷操作请求包括数据卷的标识；
    所述收发模块还用于向所述片上系统发送所述挂卷操作请求，以指示所述片上系统发送所述数据卷的标识至所述裸机服务器的处理器，所述裸机服务器的处理器将所述数据卷作为所述裸机服务器的可用存储空间。
  12. 根据权利要求11所述的公有云管理组件，其特征在于，所述处理模块还用于生成卸卷操作请求，所述卸卷操作请求包括所述数据卷的标识；
    所述收发模块还用于向所述片上系统发送所述卸卷操作请求，以指示所述片上系统发送所述数据卷的标识至所述裸机服务器的处理器，禁止所述裸机服务器的处理器将所述数据卷作为所述裸机服务器的可用存储空间。
  13. 一种片上系统，其特征在于，包括：
    收发器，用于接收公有云管理组件发送的挂卷请求，所述挂卷请求包括系统卷的标识，所述系统卷中保存了用于启动裸机服务器的操作系统的文件；
    处理器，用于根据所述挂卷请求，保存所述系统卷的标识，所述裸机服务器启动时，所述系统卷的标识被所述裸机服务器用于确定所述系统卷，并根据所述系统卷启 动所述裸机服务器的操作系统。
  14. 根据权利要求13所述的片上系统，其特征在于，所述收发器还用于接收所述公有云管理组件发送的挂卷操作请求，所述挂卷操作请求包括数据卷的标识；
    所述收发器还用于发送所述数据卷的标识至所述裸机服务器的处理器，以指示所述裸机服务器的处理器将所述数据卷作为所述裸机服务器的可用存储空间。
  15. 根据权利要求14所述的片上系统，其特征在于，所述收发器还用于接收所述公有云管理组件发送的卸卷操作请求，所述卸卷操作请求包括所述数据卷的标识；
    所述收发器还用于发送所述数据卷的标识至所述裸机服务器的处理器，以禁止所述裸机服务器的处理器将所述数据卷作为所述裸机服务器的可用存储空间。
  16. 一种公有云管理组件，其特征在于，包括：
    处理器，用于生成挂卷请求，所述挂卷请求包括系统卷的标识,所述系统卷中保存了用于启动裸机服务器的操作系统的文件；
    收发器，用于向所述片上系统发送所述挂卷请求，以指示片上系统根据所述挂卷请求，保存所述系统卷的标识。
  17. 根据权利要求16所述的公有云管理组件，其特征在于，所述处理器还用于生成挂卷操作请求，所述挂卷操作请求包括数据卷的标识；
    所述收发器还用于向所述片上系统发送所述挂卷操作请求，以指示所述片上系统发送所述数据卷的标识至所述裸机服务器的处理器，所述裸机服务器的处理器将所述数据卷作为所述裸机服务器的可用存储空间。
  18. 根据权利要求17所述的公有云管理组件，其特征在于，所述处理器还用于生成卸卷操作请求，所述卸卷操作请求包括所述数据卷的标识；
    所述收发器还用于向所述片上系统发送所述卸卷操作请求，以指示所述片上系统发送所述数据卷的标识至所述裸机服务器的处理器，禁止所述裸机服务器的处理器将所述数据卷作为所述裸机服务器的可用存储空间。
  19. 一种裸机服务器，其特征在于，所述裸机服务器包括处理器和片上系统，其中，所述片上系统为权利要求7-9以及13-15中任一项所述的片上系统。
  20. 一种系统，其特征在于，包括裸机服务器和公有云管理组件，所述裸机服务器包括片上系统和处理器，其中，所述片上系统为权利要求7-9以及13-15中任一项所述的片上系统；和/或
    所述公有云管理组件为权利要求10-12以及16-18中任一项所述的公有云管理组件。
PCT/CN2018/088829 2017-09-05 2018-05-29 对请求处理的方法、片上系统和公有云管理组件 WO2019047571A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP18854975.2A EP3713198B1 (en) 2017-09-05 2018-05-29 Request processing method, system on chip, and public cloud management component
EP22176928.4A EP4113291B1 (en) 2017-09-05 2018-05-29 Request processing method, system on chip, and public cloud management component
US16/743,131 US11775316B2 (en) 2017-09-05 2020-01-15 Request processing method, system on chip, and public cloud management component
US17/318,075 US11847470B2 (en) 2017-09-05 2021-05-12 Request processing method, system on chip, and public cloud management component

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710791704.9A CN109428943B (zh) 2017-09-05 2017-09-05 对请求处理的方法、片上系统和公有云管理组件
CN201710791704.9 2017-09-05

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/743,131 Continuation US11775316B2 (en) 2017-09-05 2020-01-15 Request processing method, system on chip, and public cloud management component

Publications (1)

Publication Number Publication Date
WO2019047571A1 true WO2019047571A1 (zh) 2019-03-14

Family

ID=65514093

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/088829 WO2019047571A1 (zh) 2017-09-05 2018-05-29 对请求处理的方法、片上系统和公有云管理组件

Country Status (4)

Country Link
US (2) US11775316B2 (zh)
EP (2) EP4113291B1 (zh)
CN (3) CN112087494B (zh)
WO (1) WO2019047571A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113127013A (zh) * 2021-03-18 2021-07-16 杭州涂鸦信息技术有限公司 一种芯片烧录的管理方法、系统及计算机可读存储介质
CN113965530A (zh) * 2020-07-01 2022-01-21 中移(苏州)软件技术有限公司 一种服务启动方法、装置和存储介质

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11947489B2 (en) 2017-09-05 2024-04-02 Robin Systems, Inc. Creating snapshots of a storage volume in a distributed storage system
US11748203B2 (en) 2018-01-11 2023-09-05 Robin Systems, Inc. Multi-role application orchestration in a distributed storage system
US11392363B2 (en) 2018-01-11 2022-07-19 Robin Systems, Inc. Implementing application entrypoints with containers of a bundled application
US11582168B2 (en) 2018-01-11 2023-02-14 Robin Systems, Inc. Fenced clone applications
US11086725B2 (en) 2019-03-25 2021-08-10 Robin Systems, Inc. Orchestration of heterogeneous multi-role applications
US11256434B2 (en) 2019-04-17 2022-02-22 Robin Systems, Inc. Data de-duplication
US11226847B2 (en) 2019-08-29 2022-01-18 Robin Systems, Inc. Implementing an application manifest in a node-specific manner using an intent-based orchestrator
US11520650B2 (en) 2019-09-05 2022-12-06 Robin Systems, Inc. Performing root cause analysis in a multi-role application
US11249851B2 (en) 2019-09-05 2022-02-15 Robin Systems, Inc. Creating snapshots of a storage volume in a distributed storage system
US11113158B2 (en) 2019-10-04 2021-09-07 Robin Systems, Inc. Rolling back kubernetes applications
US11347684B2 (en) 2019-10-04 2022-05-31 Robin Systems, Inc. Rolling back KUBERNETES applications including custom resources
US11403188B2 (en) 2019-12-04 2022-08-02 Robin Systems, Inc. Operation-level consistency points and rollback
CN113127008B (zh) * 2019-12-30 2024-04-26 华为云计算技术有限公司 裸金属服务器发放方法及相关装置
US11108638B1 (en) 2020-06-08 2021-08-31 Robin Systems, Inc. Health monitoring of automatically deployed and managed network pipelines
US11528186B2 (en) * 2020-06-16 2022-12-13 Robin Systems, Inc. Automated initialization of bare metal servers
US11740980B2 (en) 2020-09-22 2023-08-29 Robin Systems, Inc. Managing snapshot metadata following backup
US11743188B2 (en) 2020-10-01 2023-08-29 Robin Systems, Inc. Check-in monitoring for workflows
US11456914B2 (en) 2020-10-07 2022-09-27 Robin Systems, Inc. Implementing affinity and anti-affinity with KUBERNETES
US11271895B1 (en) 2020-10-07 2022-03-08 Robin Systems, Inc. Implementing advanced networking capabilities using helm charts
US11750451B2 (en) 2020-11-04 2023-09-05 Robin Systems, Inc. Batch manager for complex workflows
US11556361B2 (en) 2020-12-09 2023-01-17 Robin Systems, Inc. Monitoring and managing of complex multi-role applications
CN113342270A (zh) * 2021-06-01 2021-09-03 中国工商银行股份有限公司 卷卸载方法、装置和电子设备
US20230031741A1 (en) * 2021-07-30 2023-02-02 Netapp, Inc. Quality of service for cloud based storage system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101344852A (zh) * 2008-09-02 2009-01-14 华为技术有限公司 一种部署windows企业版操作系统的方法、装置和系统
CN103297504A (zh) * 2013-05-09 2013-09-11 浙江大学 一种云数据中心中物理裸机快速部署操作系统的方法
US20170083351A1 (en) * 2015-09-22 2017-03-23 International Business Machines Corporation Deployment of virtual machines
CN107122267A (zh) * 2017-05-31 2017-09-01 广州鼎甲计算机科技有限公司 一种Windows操作系统挂载恢复方法

Family Cites Families (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6694317B1 (en) 1997-12-31 2004-02-17 International Business Machines Corporation Method and apparatus for high-speed access to and sharing of storage devices on a networked digital data processing system
US6751658B1 (en) * 1999-10-18 2004-06-15 Apple Computer, Inc. Providing a reliable operating system for clients of a net-booted environment
US20050093572A1 (en) 2003-11-03 2005-05-05 Macronix International Co., Ltd. In-circuit configuration architecture with configuration on initialization function for embedded configurable logic array
US7293168B2 (en) 2004-12-15 2007-11-06 Hewlett-Packard Development Company, L.P. System and method for initially configuring and booting a device using a device identifier
US9069599B2 (en) 2008-06-19 2015-06-30 Servicemesh, Inc. System and method for a cloud computing abstraction layer with security zone facilities
US8055893B2 (en) * 2008-08-28 2011-11-08 Lenovo (Singapore) Pte. Ltd. Techniques for booting a stateless client
US8397046B2 (en) 2009-03-26 2013-03-12 Hitachi, Ltd. Method and apparatus for deploying virtual hard disk to storage system
US8195929B2 (en) 2009-08-27 2012-06-05 Hewlett-Packard Development Company, L.P. Controlling file systems sharing among two or more operating system
US20120054734A1 (en) 2010-08-31 2012-03-01 Apple Inc. Device software upgrade using a dynamically sized partition
US8793379B2 (en) * 2011-11-01 2014-07-29 Lsi Corporation System or method to automatically provision a storage volume by having an app-aware based appliance in a storage cloud environment
US9110600B1 (en) 2012-03-19 2015-08-18 Amazon Technologies, Inc. Triggered data shelving to a different storage system and storage deallocation
WO2014032233A1 (zh) * 2012-08-29 2014-03-06 华为技术有限公司 虚拟机热迁移的系统和方法
GB2506181A (en) * 2012-09-25 2014-03-26 Ibm Generating customised program logic for hardware devices
US9262448B2 (en) * 2013-08-12 2016-02-16 International Business Machines Corporation Data backup across physical and virtualized storage volumes
CN104572147A (zh) * 2013-10-18 2015-04-29 宇宙互联有限公司 云启动系统、具有云启动系统的虚拟机及其启动方法
US9652331B2 (en) 2013-10-24 2017-05-16 Sas Institute Inc. Techniques for creating a bootable image in a cloud-based computing environment
CN104660528A (zh) * 2013-11-25 2015-05-27 上海益尚信息科技有限公司 新型基于pn序列的ofdm系统导频信道估计方法及装置
US9838371B2 (en) * 2014-03-14 2017-12-05 Citrix Systems, Inc. Method and system for securely transmitting volumes into cloud
CN105335168B (zh) * 2014-05-27 2018-07-10 阿里巴巴集团控股有限公司 实现操作系统远程配置的系统、方法及装置
US10425480B2 (en) 2014-06-26 2019-09-24 Hitachi Vantara Corporation Service plan tiering, protection, and rehydration strategies
US9836419B2 (en) * 2014-09-15 2017-12-05 Microsoft Technology Licensing, Llc Efficient data movement within file system volumes
US9940377B1 (en) 2014-09-16 2018-04-10 Amazon Technologies, Inc. Instant copies of storage volumes
US20160092088A1 (en) * 2014-09-30 2016-03-31 Microsoft Corporation Computing system facilitating inter-user communication
US9483187B2 (en) * 2014-09-30 2016-11-01 Nimble Storage, Inc. Quality of service implementation in a networked storage system with hierarchical schedulers
CN105791370B (zh) * 2014-12-26 2019-02-01 华为技术有限公司 一种数据处理方法及相关服务器
CN105141684A (zh) * 2015-08-18 2015-12-09 北京汉柏科技有限公司 一种云计算操作系统及其部署架构
WO2017046830A1 (en) * 2015-09-17 2017-03-23 Hitachi, Ltd. Method and system for managing instances in computer system including virtualized computing environment
CN106713250B (zh) * 2015-11-18 2019-08-20 杭州华为数字技术有限公司 基于分布式系统的数据访问方法和装置
CN105635276B (zh) * 2015-12-28 2019-05-21 国云科技股份有限公司 云平台分布式物理卷对象迁移到非分布式存储的方法
US11132187B2 (en) 2016-08-26 2021-09-28 American Megatrends International, Llc Bare metal provisioning of software defined infrastructure
US10691803B2 (en) 2016-12-13 2020-06-23 Amazon Technologies, Inc. Secure execution environment on a server
US10911405B1 (en) 2017-07-31 2021-02-02 Amazon Technologies, Inc. Secure environment on a server
US10949125B2 (en) * 2019-06-28 2021-03-16 Amazon Technologies, Inc. Virtualized block storage servers in cloud provider substrate extension

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101344852A (zh) * 2008-09-02 2009-01-14 华为技术有限公司 一种部署windows企业版操作系统的方法、装置和系统
CN103297504A (zh) * 2013-05-09 2013-09-11 浙江大学 一种云数据中心中物理裸机快速部署操作系统的方法
US20170083351A1 (en) * 2015-09-22 2017-03-23 International Business Machines Corporation Deployment of virtual machines
CN107122267A (zh) * 2017-05-31 2017-09-01 广州鼎甲计算机科技有限公司 一种Windows操作系统挂载恢复方法

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113965530A (zh) * 2020-07-01 2022-01-21 中移(苏州)软件技术有限公司 一种服务启动方法、装置和存储介质
CN113965530B (zh) * 2020-07-01 2023-10-13 中移(苏州)软件技术有限公司 一种服务启动方法、装置和存储介质
CN113127013A (zh) * 2021-03-18 2021-07-16 杭州涂鸦信息技术有限公司 一种芯片烧录的管理方法、系统及计算机可读存储介质

Also Published As

Publication number Publication date
EP4113291B1 (en) 2024-04-03
CN112087493B (zh) 2022-02-22
EP3713198A4 (en) 2021-01-13
CN112087494A (zh) 2020-12-15
US11775316B2 (en) 2023-10-03
CN109428943A (zh) 2019-03-05
EP3713198A1 (en) 2020-09-23
EP3713198B1 (en) 2022-06-08
CN112087494B (zh) 2024-04-09
CN109428943B (zh) 2020-08-25
US20210263748A1 (en) 2021-08-26
CN112087493A (zh) 2020-12-15
US11847470B2 (en) 2023-12-19
US20200150977A1 (en) 2020-05-14
EP4113291A1 (en) 2023-01-04

Similar Documents

Publication Publication Date Title
US11847470B2 (en) Request processing method, system on chip, and public cloud management component
US10503490B2 (en) Mobile application processing
US8504815B2 (en) Method of using an information handling system having a boot file, and an information handling system and machine-executable code for carrying out the method
US10146556B2 (en) System and method to perform an OS boot using service location protocol and launching OS using a dynamic update of network boot order without a reboot
JP6799668B2 (ja) Ｒａｉｄ設定
US10860307B2 (en) Fragmented firmware storage system and method therefor
US9767118B2 (en) Optimized UEFI file system with network file system compound statements
WO2023060893A1 (zh) 存储空间管理方法、装置、设备及存储介质
US20060129788A1 (en) System and method for initially configuring and booting a device using a device identifier
CN108021372A (zh) 一种应用程序的管理方法和装置
US11630591B1 (en) System and method to manage storage system for startup
US10956173B2 (en) Capturing pre-fetch blocks of an operating system to improve boot performance in a cloud environment
US20090183149A1 (en) Data imaging system and methods
WO2019201248A1 (zh) 轻量级机器到机器系统中重新引导的方法和装置
WO2019100704A1 (zh) 用于多模IoT设备的启动方法、多模IoT设备及存储介质
US20090172135A1 (en) Pre-boot retrieval of an external boot file
US8412769B2 (en) Scalably imaging clients over a network
US20210357295A1 (en) Recovery image downloads via data chunks
WO2024222545A1 (zh) 一种容器启动方法、装置、电子设备及存储介质
CN117435212A (zh) 裸金属服务器管理方法及相关装置
CN116088998A (zh) 通用串行总线usb设备重定向的方法和装置
US20130139184A1 (en) Method for embedding a host driver within a device
CN117785296A (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: 18854975

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018854975

Country of ref document: EP

Effective date: 20200406