Abstract:
A method, apparatus and program product for automatically detecting the configuration of a hardware platform, generating the communications necessary to request the correct OS for the platform, authenticating the request at a remote server, detecting the image class based on a class node policy, and downloading the correct OS to the requesting platform while avoiding any necessity of inventorying or entering node-specific information such as a MAC (Media Access Control) address or UUID (Universally Unique Identifier).

Description:
FIELD AND BACKGROUND OF INVENTION 
       [0001]    This invention relates to the loading of operating system software into computer system hardware from a server accessible over a network. 
         [0002]    Today, there are a number of systems that support loading of different operating system software from a remote server. Specifically, a single hardware platform can support a virtualized environment in which a number of virtualized operating systems support a number of users requiring identical operating systems and applications or that same platform can support a single high performance connection to a single operating system (hereinafter the phrases “operating system” or “operating system software” will be represented by the abbreviation OS) and a single high performance application. The last mentioned operation is particularly true in a rack environment in which a plurality of hardware platforms function as nodes in a network. 
       SUMMARY OF THE INVENTION 
       [0003]    With the foregoing in mind, what is required is a system class image detection mechanism which will auto-classify various OS requests from multiple nodes and assign an OS request to a class node policy in an image boot server. This classification is characterized by the different configurations of the same base architecture. What follows describes a method, apparatus and program product for automatically detecting the configuration of a hardware platform, generating the communications necessary to request the correct OS for the platform, authenticating the request at a remote server, detecting the image class based on a class node policy, and downloading the correct OS to the requesting platform while avoiding any necessity of inventorying or entering node-specific information such as a MAC (Media Access Control) address, UUID (Universally Unique Identifier) or VPD (Vital Product Data). 
     
    
     
       BRIEF DESCRIPTION OF DRAWINGS 
         [0004]    Some of the purposes of the invention having been stated, others will appear as the description proceeds, when taken in connection with the accompanying drawings, in which: 
           [0005]      FIG. 1  is a representation of the flow of processes in a preboot execution environment; 
           [0006]      FIG. 2  is a representation of the format used by a preboot execution environment message; 
           [0007]      FIG. 3  is a representation of an initial program load process; 
           [0008]      FIG. 4  is a representation of layers of code in a computer system hardware platform; 
           [0009]      FIG. 5  is an illustration of the interactions and interconnections of computer system hardware platform elements and network resources in implementing this invention; and 
           [0010]      FIG. 6  is a representation of a computer readable medium on which may be stored program code efective, when executing, to implement this invention. 
       
    
    
     DETAILED DESCRIPTION OF INVENTION 
       [0011]    While the present invention will be described more fully hereinafter with reference to the accompanying drawings, in which a preferred embodiment of the present invention is shown, it is to be understood at the outset of the description which follows that persons of skill in the appropriate arts may modify the invention here described while still achieving the favorable results of the invention. Accordingly, the description which follows is to be understood as being a broad, teaching disclosure directed to persons of skill in the appropriate arts, and not as limiting upon the present invention. 
         [0012]    Today an Information Technology (IT) administrator is required to obtain the Media Access Control (MAC) address of a newly installed computer system and then manually enter both the MAC address and Internet Protocol (IP) address of that node in a remote Pre-boot Execution Environment (PXE) boot server. This information is manually obtained from an external tag, sometimes called a “toe tag”, attached to the computer. Once this information is entered at the remote PXE boot server, the local computer is powered on. The Ethernet Network Interface Card (NIC) uses the PXE boot protocol to access a remote boot image and down load that image. This operation is tedious in an environment consisting of rack on rack of computer systems. 
         [0013]    This invention provides a method of obtaining the hardware configuration of the newly installed computer, including the MAC and IP addresses. The inventive method allows initial detection and determination of the class of operating system to be loaded based on the hardware configuration contained in the VPD. Use of the current PXE boot interface and architecture allows different classes of operating systems to be loaded based on VPD. Also, automatic modification of the class of operating system is provided if the customer changes the hardware configuration. Hardware configurations are BIOS independent. The environment may be easily scaled. 
         [0014]    Implementations contemplated by this invention provide for base board management (BMC) to communicate information to the BIOS and request the remote boot of a specific class of operating system. Further, for transmission of the Internet Protocol Suite, commonly known as Transmission Control Protocol/Internet Protocol (TCP/IP) packets through an Ethernet NIC to a PXE boot server to request the loading of a specific class of operation system. Further, for the PXE boot server to authenticate the request to ensure the correct operating system is loaded. And further for the PXE server to auto-classify the requesting node and automatically detect the image class required by the requester. 
         [0015]    As will be understood, this disclosure deals with the remote network loading of an operating system from a centralized server. Specifically, this disclosure deals with the identification of a class of servers. Once this class is identified by a base board management controller (BMC) query of the system configuration, this information is communicated to the BIOS in the Pre-boot Execution Environment (PXE Boot). The PXE boot process then allows the BIOS to communicate class parameters to a boot server so it can remotely download one of “n” operating systems. This disclosure discusses two classes of operating systems, but can easily be expanded to “n”. The diagram of  FIG. 1  shows the basic flow of the PXE boot protocols. 
         [0016]    This disclosure relates to a PXE Client to Boot Service aspect in which the hardware node specifies the class type of download required. Specifically what is disclosed here is an automated way to communicate with a network bootstrap program (NBP) to tell the NBP whether it is desired to boot a bare metal OS subsequently booted or whether a hypervisor is to be subsequently booted. This allows administrators that manage central provisioning servers that house NBPs to communicate with and to deploy operating systems, perform diagnostics, or manage disk deployment. Today, the bulk (or potentially all) of the NBP based solutions do all their decision making on the servers with which NBPs communicate. What is taught here is moving a key decision making policy to the device (provisioning server) on which the NBP runs. More specifically, this disclosure teaches an addition to Step  9  in  FIG. 1  in which a client device communicates hardware parameters to the NBP&#39;s provisioning server and the NBP remotely deploys the correct bare metal OS or hypervisor plus virtual machine OS&#39;s based on a provisioning policy. 
         [0017]    Prior to Step  1  in  FIG. 1 , the BMC identifies the class of operational software required. Steps  5  through  9  depict the process that this disclosure enhances. Network boot steps following step  9  in  FIG. 1  automate the selection of the operating system to be loaded across a network from a provisioning server. In this architecture, there is a tag for the operation class configuration identifier. What is described herein is a method of automatically modifying the configuration class tag identifier to load a specific operating system. The Universal Unique Identification (UUID) is not required for this operation. 
         [0018]    There are a number of prior patents that deal with PXE boot services to which the interested reader may be referred. Among them are U.S. Pat. Nos. 7,313,690 and 7,194,619 that deal with authentication, U.S. Pat. No. 7,297,354 that deals with a secure network boot, U.S. Pat. No. 7,290,258 that deals with booting the same image to multiple devices, U.S. Pat. No. 7,284,120 that deals with loading an image during the manufacturing process and U.S. Pat. No. 7,159,018 that deals with loading an image based on a manufacturing script. U.S. Pat. No. 7,293,168 invokes the use of a UUID to provide a boot image. 
         [0019]    Linux provides a type of boot service called PXELinux that searches for its configuration file on the boot server and loads the appropriate application files. However, this is a two-step process actually requiring manual intervention as described in the following link: http://syslinux.zytor.com/pxe.php. The initial step of this process is for the user to load a diskette image of the application required. To use PXELinux, the user completes a checklist of the required applications. These options are then loaded on a diskette. This diskette image is user-defined based on the system configuration and the applications required. This manual input is done during the BIOS boot-up process. Once completed and configured by the user, PXELinux then requests the application images from a Boot Server. 
         [0020]    In this invention, the message exchange follows the protocol described above, but is user independent. The format shown in  FIG. 2  is used by the PXE Boot to request certain type of applications. Note that this is an abbreviated form of the formatted message. 
         [0021]    In accordance with this invention, the OS boot architecture is modified to include two additional requested architectured parameters. Unlike what is fixed in PXE Base-Code option ROMs or input by a user, the base board management controller (BMC) determines the hardware configuration and passes that configuration to the BIOS during the initial program load (IPL) process. This operation defines the class of operation service. This flexibility allows a user to boot with one operating system and then modify that operating system when a hardware update is needed. 
         [0022]    The client system architecture field is used to denote the system architecture, such that the appropriate PXE loader can be loaded, not what operating system to be loaded (Microsoft Windows cannot be PXEbooted). This disclosure shows that this structure can be used as a possible implementation to pass the system classification. Adding a new type field or parameter to an existing field to the client system architecture would require minor modifications to the boot loader, such that it knows what to request when it requests the operating system to load from the higher level provisioning server. One possible implementation is to define a tag name in the PXEClient data structure such as “NBP vendor specific parameter”. This may have certain compatibility issues. However, an extension of the architecture does permit this function to be implemented. 
         [0023]    In the case of the iDataPlex Hosted Client, two possibilities exist. The first possibility is the class requirement for a virtual operating system such as Citrix and Xen Hypervisor to be loaded in a virtual environment. The second possibility is for the high resolution Microsoft-compliant operating system to be loaded. The hardware differentiation is provided by the presence or absence of a video compression card. Note that this archstecture is not limited to a specific card or operating system, but can be extended depending on requirements 
         [0024]    The BMC detects this differentiation requiring no device drivers in the BIOS. The BMC then passes this class operating system configuration parameter to BIOS. During the PXE Boot process, the client system architecture specifies the class type of operating system to load. For example, a code of 6 can specify a Microsoft Vista load whereas a code of 7 specifies a virtual environment in which a virtual operating system environment is loaded. The advantage of this methodology is that the user can either add or remove the hardware requirement after the manufacturing process is complete. This method differentiates the present invention from U.S. Pat. No. 7,293,168 since the UUID is always fixed in that teaching.  FIG. 3  shows the IPL process from the power-on of the system. 
         [0025]    BIOS base code is stored in EEPROM in the system prior to the actual operating system image load. See  FIG. 4  for a representation of stored program layers. BIOS communicates with the BMC to determine the hardware configuration and therefore, the class operating system type. This allows a remote boot without any intervention. Once the class is determined, this parameter is passed to the PXE Boot server. The PXE Boot server then loads the class operating system correlating it to the MAC address and the UUID specified as part of the PXE Boot protocol. These parameters are then passed to the Application Program Interface (API) and the transfer occurs. The operation of this invention is independent of the transfer mechanism. 
         [0026]    Referring now to  FIG. 5 , When standby power is applied to the system, shown in steps  1  &amp;  2  of  FIG. 1  above, the BMC  50  reads the VPD  51  and the hardware configuration as indicated by a line  60 . This information is passed to BIOS  52  as indicated by a line  61  to determine the class of operating system required. BIOS  54  then sends a Dynamic Host Controller Protocol (DHCP) request to the DHCP server  55  as indicated by a line  62 . This request returns the IP address of the PXE boot server. BIOS then passes the request for the class of operating system to the PXE Boot server  56 , as indicated by a line  64 , which is passed to the API, indicated by a line  65 , as is done according to prior art. The correct class of operating system is then sent to the iDataPlex Hosted Client product. Shown in this example is the loading of a hard disk  58 , indicated by a line  66 . However, this operation can be performed in a diskless environment. 
         [0027]      FIG. 6  shows a computer readable medium (here, an optical disk)  60  storing executable programming code in accordance with this invention which, when executed by a computer system hardware platform which has a plurality of elements including a memory element which stores executable program code and a base board management controller component, is effective to practice the methods described here. 
         [0028]    In the drawings and specifications there has been set forth a preferred embodiment of the invention and, although specific terms are used, the description thus given uses terminology in a generic and descriptive sense only and not for purposes of limitation.