Bootstrapping from a remote disk image via a network

US9280360B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9280360-B2
Application numberUS-201414304158-A
CountryUS
Kind codeB2
Filing dateJun 13, 2014
Priority dateJun 14, 2013
Publication dateMar 8, 2016
Grant dateMar 8, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A method of bootstrapping from a remote image file comprising loading, by a processor, an initial bootloader, employing the initial bootloader to download a final bootloader from the remote image file via a network, employing the final bootloader to mount the remote image file as a block device, downloading a kernel and root file system mounting data from the remote image, and executing the kernel to bootstrap the processor based on the root file system mounting data.

First claim

Opening claim text (preview).

What is claimed is: 1. A method of bootstrapping from a remote image file comprising: loading, by a processor, an initial bootloader; employing the initial bootloader to download a final bootloader from the remote image file via a network; employing the final bootloader to download a kernel; executing the kernel to download root file system mounting data from the remote image file; and executing the kernel to bootstrap the processor based on the root file system mounting data. 2. The method of claim 1 , wherein downloading the kernel and the root file system mounting data does not comprise downloading the entire remote image file. 3. The method of claim 1 , wherein executing the kernel to bootstrap the processor comprises: mounting, by the kernel, the remote image file via the network as a block device based on the root file system mounting data; and downloading a final root file system from the mounted remote image file. 4. The method of claim 3 , wherein employing the initial bootloader to download the final bootloader comprises querying a boot server to obtain an internet protocol (IP) address associated with a target server that comprises the remote image file, a file name of the remote image file, and a configuration indicating a location of the final bootloader in the remote image file. 5. The method of claim 4 , wherein the boot server is queried via a Dynamic Host Configuration Protocol (DHCP). 6. The method of claim 4 , wherein the root file system mounting data is downloaded from an initial ramdisk (initrd) file. 7. The method of claim 1 , wherein all downloaded files are stored to a random access memory (RAM) and no downloaded files are stored to a hard disk. 8. A network element (NE) comprising: a transmitter; a receiver; a memory; and a processor coupled to the transmitter, receiver, and memory, configured to cause the NE to: load an initial bootloader to memory; execute the initial bootloader to download a final bootloader from a remote image file via a network; execute the final bootloader to download a kernel; execute the kernel to download root file system mounting data from the remote image; and employ the kernel to complete a bootstrapping process based on the root file system mounting data. 9. The NE of claim 8 , wherein the NE does not comprise a hard drive or a Compact Disk Read Only Memory (CD-ROM) input. 10. The NE of claim 8 , wherein the root file system mounting data comprises only data needed to allow the kernel to mount the remote image file as a block device. 11. The NE of claim 10 , wherein executing the kernel comprises: mounting the remote image file as a block device based on the root file system mounting data; and downloading a root file system from the remote image file. 12. The NE of claim 8 , wherein the processor is further configured to cause the NE to query a boot server to obtain an internet protocol (IP) address associated with a target server that comprises the remote image file, a file name of the remote image file, and a configuration indicating a location of the final bootloader in the remote image file. 13. The NE of claim 12 , wherein the boot server is queried via a Dynamic Host Configuration Protocol (DHCP). 14. The NE of claim 8 , wherein the entire remote image file is not downloaded. 15. A network element (NE) comprising: a memory configured to store a bootable image file comprising a bootloader, a kernel, and root file system mounting data, wherein the bootloader is configured to mount the image file and download the kernel when executed by a client, and wherein the kernel is configured to download the root file system mounting data and mount the image file based on the root file system mounting data when executed by the client; a receiver configured to receive download requests from the client; a processor coupled to the memory and the receiver and configured to process download requests from the client; and a transmitter coupled to the processor and configured to transmit at least some of the bootable image file to the client via a network in response to download requests from the client. 16. The NE of claim 15 , wherein the bootable image file further comprises an initial root file system, and wherein the kernel is further configured to download the initial root file system when executed by the client and perform a bootstrapping process based on the initial root file system. 17. The NE of claim 16 , wherein the initial root file system is an initial ramdisk (initrd) file. 18. The NE of claim 15 , wherein the transmitter is not configured to transmit the entire bootable image file in response to a single request from the client. 19. The NE of claim 15 , wherein the bootable image file is an International Standards Organization 9660 (.iso) file. 20. The NE of claim 15 , wherein the bootable image file is configured to be transmitted to, and executed by, a plurality of clients without read only memory (ROM).

Assignees

Inventors

Classifications

  • G06F9/4416Primary

    Network booting; Remote initial program loading [RIPL] · CPC title

  • Electricity · mapped topic

  • using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP] · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9280360B2 cover?
A method of bootstrapping from a remote image file comprising loading, by a processor, an initial bootloader, employing the initial bootloader to download a final bootloader from the remote image file via a network, employing the final bootloader to mount the remote image file as a block device, downloading a kernel and root file system mounting data from the remote image, and executing the ker…
Who is the assignee on this patent?
Futurewei Technologies Inc
What technology area does this patent fall under?
Primary CPC classification G06F9/4416. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Mar 08 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).