System using vital product data and map for selecting a BIOS and an OS for a server prior to an application of power

• US 7,743,124 B2
• Filed: 04/30/2008
• Issued: 06/22/2010
• Est. Priority Date: 04/30/2008
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Holdaway, Kevan D., Olguin, Ivan Ronald II
• Primary Examiner(s): LUU, LE HIEN
• Application Number:
  US12/112,195
• Publication Number:
  US 20090276512A1
• Time in Patent Office: 783 Days
• Field of Search: 709/222, 709/220, 709/223, 707/100, 715/223
• US Class Current: 709/222
• CPC Class Codes: G06F 9/4405 Initialisation of multiprocessor systems

Abstract

A method for selecting a basic input output system (BIOS) and an operating system (OS) for a server managed by a controller in communication with a plurality of servers is provided. The server is detected. A map describing a relationship between the server and the plurality of servers is consulted. The map at least partially defines a policy for the server. Vital product data (VPD) of the server is used in conjunction with the map and the policy to select at least one of the BIOS and the OS for the server prior to an application of power to the server.

Claims

1. A method for selecting a basic input output system (BIOS) and an operating system (OS) for a server managed by a controller in communication with a plurality of servers, comprising:

detecting the server;

consulting a map describing a relationship between the server and the plurality of servers, the map at least partially defining a policy for the server; and

using vital product data (VPD) of the server in conjunction with the map and the policy to select at least one of the BIOS and the OS for the server prior to an application of power to the server.

2. The method of claim 1, further including configuring and storing the map on the controller.

3. The method of claim 1, wherein detecting the selected server includes detecting an insertion of the server into a slot.

4. The method of claim 1, wherein consulting a map describing a relationship between the server and the plurality of servers includes consulting a slot-to-volume map describing a relationship between a slot and a volume assigned to the slot.

5. The method of claim 4, further including configuring a compatibility matrix describing a compatibility relationship between an application and the server.

6. The method of claim 4, further including:

determining if the volume exists,

if the volume exists, modifying the BIOS of the server to point to the volume, and

if the volume does not exist, providing a request that the volume be created.

7. The method of claim 1, wherein consulting a map describing a relationship between the server and the plurality of servers includes consulting a blade-to-volume map describing a relationship between the server and a volume assigned to the server.

8. The method of claim 1, wherein using vital product data (VPD) of the server in conjunction with the policy to select at least one of the BIOS and the OS for the server prior to an application of power to the server includes requesting a zoning change on a switch or updating the BIOS of the server with a boot location.

9. A system for selecting a basic input output system (BIOS) and an operating system (OS) for a server managed by a management module, the management module in communication with the plurality of servers, comprising:

a configuration module operational on the management module, the configuration module adapted for;

detecting the server,

consulting a map describing a relationship between the server and plurality of servers, the map at least partially defining a policy for the server, and

using vital product data (VPD) of the server in conjunction with the map and the policy to select at least one of the BIOS and the OS for the server prior to an application of power to the server.

10. The system of claim 9, further including an information manager module in communication with the configuration module, the information manager module adapted for consulting a slot-to-volume map describing a relationship between a slot of the server and a volume assigned to the slot.

11. The system of claim 10, further including a compatibility matrix module in communication with the information manager module, the compatibility matrix module adapted for configuring a compatibility matrix describing a compatibility relationship between an application and the server.

12. The system of claim 9, further including an information manager module in communication with the configuration module, the information manager module adapted for consulting a blade-to-volume map describing a relationship between the selected server and a volume assigned to the server.

13. The system of claim 12, further including a BIOS module in communication with the information manager module, the BIOS module adapted for:

if the volume exists, modifying the BIOS of the selected server to point to the volume, and

if the volume does not exist, providing a request that the volume be created.

14. The system of claim 9, wherein the configuration module is further adapted for requesting a zoning change on a switch or updating the BIOS of the server with a boot location prior to an application of power to the server.

15. A computer program product selecting a basic input output system (BIOS) and an operating system (OS) for a server managed by a controller in communication with a plurality of servers, the computer program product comprising a computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising:

a first executable portion for detecting the server;

a second executable portion for consulting a map describing a relationship between the server and the plurality of servers, the map at least partially defining a policy for the server; and

a third executable portion for using vital product data (VPD) of the server in conjunction with the map and the policy to select at least one of the BIOS and the OS for the server prior to an application of power to the server.

16. The computer program product of claim 15, further including a fourth executable portion for configuring and storing the map on the controller.

17. The computer program product of claim 15, wherein the second executable portion for consulting a map describing a relationship between the server and the plurality of servers includes a fourth executable portion for consulting a slot-to-volume map describing a relationship between a slot and a volume assigned to the slot.

18. The computer program product of claim 15, wherein the second executable portion for consulting a map describing a relationship between the server and the plurality of servers includes a fourth executable portion for consulting a blade-to-volume map describing a relationship between the server and a volume assigned to the server.

19. The computer program product of claim 18, further including a fifth executable portion for:

determining if the volume exists,

if the volume exists, modifying the BIOS of the server to point to the volume, and

if the volume does not exist, providing a request that the volume be created.

20. The computer program product of claim 15, wherein the third executable portion for using vital product data (VPD) of the server in conjunction with the policy to select at least one of the BIOS and the OS for the server prior to an application of power to the server includes a fourth executable portion for requesting a zoning change on a switch or updating the BIOS of the server with a boot location.