Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/44—Arrangements for executing specific programs
  • G06F9/4401—Bootstrapping
  • G06F9/4416—Network booting; Remote initial program loading [RIPL]
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/44—Arrangements for executing specific programs
  • G06F9/4401—Bootstrapping
  • G06F9/4406—Loading of operating system

Definitions

• the present disclosure generally relates to the field of computing devices, and more particularly to a system and method for efficiently root booting computing devices.
• Root booting is the practice of booting a computing device using a volume on an attached storage device such as an attached storage array.
• This volume may contain everything that a local drive would contain if the computing device booted from the local drive (such as an operating system, drivers, temporary files, application programs, and/or virtual memory swap space).
• FIG. 1 illustrates a typical system 100 for root booting.
• the system 100 typically includes a plurality of computing devices 101 communicably connected to an attached storage device 102.
• Each computing device 101 typically boots from a dedicated volume 104 of the attached storage device 102 which is presented. to each computing device 101 as a virtual volume 105. Then each computing device 101 typically continues to utilize its respective dedicated volume 104 (via the respective virtual volume 105) for operation.
• FIG. 2 illustrates how each computing device 101 views the system 100.
• Each computing device 101 is only able to access the respective volume 104 and the respective area of the cache 103 of the attached storage device 102 for the computing device 101 , though the computing device 101 is actually only aware of its respective virtual volume 105 of the attached storage device 102.
• a system and method for root booting may include a plurality of computing devices communicably connected to an attached storage device. Each computing device may boot from a read-only base volume of the attached storage device.
• the read-only base volume may include data common to the plurality of computing devices including, but not limited to one or more operating systems, drivers, temporary files, application programs, and/or virtual memory swap space. Frequently accessed data of the read-only base volume may be stored in a portion of the cache of the attached storage device.
• the attached storage device may also include a plurality of volumes, each dedicated to one of the plurality of computing devices, which are redirect on write snapshots of the read-only base volume.
• the respective volume for each computing device may include unique items for a computing device such as unique registration keys, virtual memory swap space, and/or temporary files. If any of the computing devices makes a change to the data of the read-only base volume, the change may be directed and stored in the respective volume for that computing device. Frequently accessed data of each of the volumes may be stored in a portion of the cache of the attached storage device for that respective volume.
• the read-only base volume, the portions of cache, and the respective volume may be presented to each of the plurality of computing devices as a virtual volume.
• the storage system may map data to the respective virtual volume for each of the plurality of computing devices from the read-only base volume when the data from the read-only base volume has not changed for the respective computing device and from the respective volume when the data from the read-only base volume has changed for the respective computing device.
• the read-only base volume may be stored in one or more solid state drives (a data storage device that utilizes solid-state memory to store persistent data) which may be configured as a RAID (redundant array of independent disks) and/or mirrored with one or more other storage drives for redundancy purposes.
• the plurality of volumes may each be stored in one or more solid state drives and/or hard disk drives which may be configured as a RAID.
• the attached storage device may be operable to add data common to the plurality of computing devices to the read-only base volume. In this way, the read-only base volume utilized to root boot the plurality of computing devices may be updated by committing the new common data to the read-only base volume.
• the present disclosure may reduce the storage space, I/O, and caching inefficiencies associated with root booting a plurality of computing devices from volumes of an attached storage device.
• the present disclosure may harness the read performance offered by solid state drives by storing the read-only base volume in one or more solid state drives. As only one read-only base volume may be required for the plurality of computing devices, the read performance offered by solid state drives is balanced against the typically higher cost of solid state drives as compared to hard disk drives. Further, the present disclosure does not require deduplication code in the I/O path which may result in a simpler implementation of system.
• FIG. 1 is a diagram illustrating a typical system for root booting
• FIG. 2 is a diagram illustrating the view of the system illustrated in FIG. 1 from the perspective of one of the plurality of computing devices;
• FIG. 3 is a diagram illustrating a system for root booting, in accordance with an embodiment of the present disclosure
• FIG. 4 is a diagram illustrating the view of the system illustrated in FIG. 3 from the perspective of one of the plurality of computing devices, in accordance with an embodiment of the present disclosure
• FIG. 5 is flow diagram illustrating a method for root booting, in accordance with an embodiment of the present disclosure
• FIG. 6 is flow diagram illustrating a method for root booting, in accordance with an alternative embodiment of the present disclosure.
• FIG. 7 is a flow diagram illustrating a method for root booting, in accordance with an alternative embodiment of the present disclosure.
• Root booting a plurality of computing devices from an attached storage device utilizing a separate volume for each computing device is inefficient.
• the data contained in the separate volumes including, but not limited to, operating systems, drivers, temporary files, application programs, and/or virtual memory swap space
• the data contained in the separate volumes may be nearly identical.
• storage space may be wasted.
• each of the plurality of servers has a separate copy of one or more operating systems, drivers, temporary files, application programs, and/or virtual memory swap space
• the same data may be read from the separate volumes separately for each one of the plurality of servers.
• unnecessary I/O input/output
• the separate volumes may compete for limited cache space inside the attached storage device (and/or a controller communicably connecting one of the plurality of computing devices to the attached storage device).
• each of the plurality of computing devices may experience more cache misses, resulting in more I/Os that have to interact with the separate volumes, stored in one or more storage drives, and slowing performance.
• FIG. 3 illustrates a system 300 for root booting, in accordance with an embodiment of the present disclosure.
• the system 300 includes a plurality of computing devices 301 communicably connected to an attached storage device 302.
• the plurality of computing devices 301 may comprise any kind of digital computing devices including, but not limited to, personal desktop computers, personal laptop computers, server computers, and/or dummy terminals.
• Each computing device 301 may boot from a read-only base volume 305 of the attached storage device 302 which is presented to each computing device 301 as a virtual volume 307 for that computing device 301.
• the read-only base volume 305 may include data common to the plurality of computing devices 301 including, but not limited to one or more operating systems, drivers, temporary files, application programs, and/or virtual memory swap space.
• Frequently accessed data of the read-only base volume may be stored in a portion of the cache 303 of the attached storage device 302.
• the portion of the cache 303 may store data of the read-only base volume frequently accessed by any of the plurality of computing devices 101 (via the respective virtual volume 307)
• the portion of the cache 303 may be proportionally more of the total cache than if separate volumes were utilized (which would require separate portions of cache) and more of the data for each of the plurality of computing devices 303 may be in cache at a given time, resulting in fewer cache misses.
• the attached storage device 302 may also include a plurality of volumes 306, each dedicated to one of the plurality of computing devices 301 , which are redirect on write snapshots of the read-only base volume 305.
• the respective volume 306 for each computing device 301 may include unique items for that computing device 301 such as unique registration keys, virtual memory swap space, and/or temporary files. If any of the computing devices 301 makes a change to the data of the read-only base volume 305 (via the respective virtual volume 307), the change may be directed and stored in the respective volume 306 for that computing device 301. Frequently accessed data of each of the volumes 306 may be stored in a portion of the cache 304 of the attached storage device for that respective volume 306.
• the storage system 302 may map data to the respective virtual volume 307 for each of the plurality of computing devices 301 from the read-only base volume 305 when the data from the read-only base volume 305 has not changed for the respective computing device 301 and from the respective volume 306 when the data from the read-only base volume 305 has changed for the respective computing device 301.
• the plurality of computing devices 301 may comprise diskless servers.
• the read-only base volume 305 may be stored in one or more solid state drives (a data storage device that utilizes solid-state memory to store persistent data).
• the read-only base volume 305 may be stored in one or more storage drives configured as a RAID (redundant array of independent disks).
• the one or more storage drives may be configured as a RAID that does not implement redundancy, such as where data is striped across a plurality of storage drives.
• the read-only base volume 305 may be stored in one or more storage drives that are mirrored with one or more other storage drives for redundancy purposes.
• the plurality of computing devices 301 may access the read-only base volume 305 (via the respective virtual volume 307) via the one or more storage drives and not the one or more other storage drives.
• the read-only base volume 305 may be stored in one or more solid state drives that are mirrored with one or more hard disk drives (a non-volatile storage device which stores digitally encoded data on rotating platters with magnetic surfaces) and the plurality of computing devices 301 may access the read-only base volume 305 (via the respective virtual volume 307) via the one or more solid state drives and not the one or more hard disk drives.
• the plurality of volumes 306 may each be stored in one or more solid state drives and/or hard disk drives.
• the plurality of volumes 306 may be each stored in one or more storage drives configured as a RAID.
• the one or more storage drives may be configured as a RAID that does not implement redundancy, such as where data is striped across a plurality of storage drives.
• the attached storage device 302 may comprise one or more network attached storage (NAS) devices and/or one or more storage area network (SAN) devices.
• the attached storage device 302 may comprise one or more RAID storage devices.
• FIG. 4 illustrates how each computing device 301 may view the system 300.
• Each computing device 301 is only able to access the readonly base volume 305, the portion of the cache 303 utilized to store frequently accessed data from the read-only base volume, its respective volume 306, and the portion of the cache 303 utilized to store frequently accessed data from its respective volume 306, though the computing device 301 is actually only aware of its respective virtual volume 307 of the attached storage device 302.
• the attached storage device 302 may be operable to add data common to the plurality of computing devices 301 to the read-only base volume 305. In this way, the read-only base volume 305 utilized to root boot the plurality of computing devices may be updated by committing the new common data to the read-only base volume 305.
• the present disclosure has been illustrated and described as a plurality of computing devices that boot from a common read-only base volume of an attached storage device and each store data particular for the respective computing device to a redirect on write snapshot of the common read-only base volume dedicated to the respective computing device (both presented to each of the plurality of computing devices as a virtual volume for the respective computing device), it should be understood that more than one plurality of computing devices, each plurality booting from a separate read-only base volume that is common to the respective plurality of computing devices, without departing from the scope of the present disclosure.
• ten Linux servers and ten Microsoft Windows servers may both be communicatively coupled to the same attached storage device.
• the ten Linux servers may boot from a Linux read-only base volume of the attached storage device common to the ten Linux servers and the ten Microsoft Windows servers may boot from a Windows read-only base volume of the attached storage device common to the ten Microsoft Windows servers.
• the present disclosure may reduce the storage space, I/O, and caching inefficiencies associated with root booting a plurality of computing devices from volumes of an attached storage device.
• the present disclosure may harness the read performance offered by solid state drives by storing the read-only base volume 305 in one or more solid state drives. As only one read-only base volume 305 may be required for the plurality of computing devices 301 , the read performance offered by solid state drives is balanced against the typically higher cost of solid state drives as compared to hard disk drives. Further, the present disclosure does not require deduplication code in the I/O path which may result in a simpler implementation of system 300.
• FIG. 5 illustrates a method of root booting a plurality of computing devices, in accordance with an embodiment of the present disclosure.
• root boot a plurality of computing devices from a read-only base volume of an attached storage device stored in at least one storage drive, the read-only base volume containing at least one of at least one operating system or at least one application program common to the plurality of computing devices.
• the at least one storage drive may comprise at least one solid state drive.
• the at least one storage drive may comprise a plurality of storage drives configured in a RAID.
• the plurality of computing devices may comprise a plurality of diskless computing devices.
• the attached storage device may comprise an attached RAID device.
• step 503 redirect the writes for each of the plurality of computing devices to one of a plurality of volumes of the attached storage device which are redirect on write snapshots of the read-only base volume, each of the plurality of volumes of the attached storage device being dedicated to one of the plurality of computing devices and storing data particular to the one of the plurality of computing devices.
• Each of the plurality of volumes may be stored in at least one hard disk drive.
• Each of the plurality of volumes may be stored in a plurality of hard disk drives configured in a RAID.
• the data particular to the one of the plurality of computing devices may comprise at least one of at least one registration key, at least one virtual memory swap space, and/or at least one temporary file.
• FIG. 6 illustrates a method of root booting a plurality of computing devices, in accordance with an alternative embodiment of the present disclosure.
• root boot a plurality of computing devices from a read-only base volume of an attached storage device stored in at least one storage drive, the read-only base volume containing at least one of at least one operating system or at least one application program common to the plurality of computing devices.
• the at least one storage drive may comprise at least one solid state drive.
• the at least one storage drive may comprise a plurality of storage drives configured in a RAID.
• the plurality of computing devices may comprise a plurality of diskless computing devices.
• the attached storage device may comprise an attached RAID device.
• step 603 receive writes for the read-only base volume from the plurality of computing devices.
• step 604 redirect the writes for each of the plurality of computing devices to one of a plurality of volumes of the attached storage device which are redirect on write snapshots of the read-only base volume, each of the plurality of volumes of the attached storage device being dedicated to one of the plurality of computing devices and storing data particular to the one of the plurality of computing devices.
• Each of the plurality of volumes may be stored in at least one hard disk drive.
• Each of the plurality of volumes may be stored in a plurality of hard disk drives configured in a RAID.
• the data particular to the one of the plurality of computing devices may comprise at least one of at least one registration key, at least one virtual memory swap space, and/or at least one temporary file.
• FIG. 7 illustrates a method of root booting a plurality of computing devices, in accordance with an alternative embodiment of the present disclosure.
• root boot a plurality of computing devices from a read-only base volume of an attached storage device stored in at least one storage drive, the read-only base volume containing at least one of at least one operating system or at least one application program common to the plurality of computing devices.
• the at least one storage drive may comprise at least one solid state drive.
• the at least one storage drive may comprise a plurality of storage drives configured in a RAID.
• the plurality of computing devices may comprise a plurality of diskless computing devices.
• the attached storage device may comprise an attached RAID device.
• step 703 redirect the writes for each of the plurality of computing devices to one of a plurality of volumes of the attached storage device which are redirect on write snapshots of the readonly base volume, each of the plurality of volumes of the attached storage device being dedicated to one of the plurality of computing devices and storing data particular to the one of the plurality of computing devices.
• Each of the plurality of volumes may be stored in at least one hard disk drive.
• Each of the plurality of volumes may be stored in a plurality of hard disk drives configured in a RAID.
• the data particular to the one of the plurality of computing devices may comprise at least one of at least one registration key, at least one virtual memory swap space, and/or at least one temporary file.
• step 704 add common data to the read-only base volume.
• the methods disclosed may be implemented as sets of instructions or software readable by a device. Further, it is understood that the specific order or hierarchy of steps in the methods disclosed are examples of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the method can be rearranged while remaining within the disclosed subject matter.
• the accompanying method claims present elements of the various steps in a sample order, and are not necessarily meant to be limited to the specific order or hierarchy presented.

Landscapes

• Engineering & Computer Science (AREA)
• Software Systems (AREA)
• Theoretical Computer Science (AREA)
• Computer Security & Cryptography (AREA)
• Physics & Mathematics (AREA)
• General Engineering & Computer Science (AREA)
• General Physics & Mathematics (AREA)
• Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
• Debugging And Monitoring (AREA)

Applications Claiming Priority (1)

Publications (2)

Family

ID=41444796

Family Applications (1)

Country Status (5)

Families Citing this family (1)

Family Cites Families (11)

• 2008
  • 2008-06-26 CN CN200880129824.1A patent/CN102067114B/zh active Active
  • 2008-06-26 KR KR1020107029037A patent/KR101288721B1/ko not_active Expired - Fee Related
  • 2008-06-26 EP EP08779790A patent/EP2291771A4/de not_active Withdrawn
  • 2008-06-26 WO PCT/US2008/007954 patent/WO2009157899A1/en not_active Ceased
  • 2008-06-26 JP JP2011516234A patent/JP5357964B2/ja not_active Expired - Fee Related

Also Published As

Similar Documents

Legal Events