Systems and methods for software distribution and management

• US 7,080,134 B2
• Filed: 06/29/2001
• Issued: 07/18/2006
• Est. Priority Date: 06/29/2001
• Status: Expired due to Fees

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Savage, Paul R., Doherty, Matthew T., Sillonis, Kathleen L., Erickson, Ryan B., Ruse, Andrew L., Johnson, Peter E.
• Primary Examiner(s): Follansbee, John
• Assistant Examiner(s): SIDDIQI, MOHAMMAD A
• Application Number:
  US09/893,740
• Publication Number:
  US 20030018763A1
• Time in Patent Office: 1,845 Days
• Field of Search: 709/223, 709/222, 709/221, 713/12, 713/2, 713/201, 713/100, 713/1
• US Class Current: 709/221
• CPC Class Codes: G06F 9/4416 Network booting; Remote initial program loading [RIPL]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A method and system for obtaining service from a management server is presented. A client sends a request for service to a management agent. The management agent forwards the request for service to a management server via Hypertext Transfer Protocol (HTTP). The management server sends service information via HTTP to the management agent. The management agent then forwards the service information to the client. As such, the client may obtain service even where network nodes, such as switches and routers, intervene between the client and the management server.

Claims

1. A system, comprising:

a client device, the client transmitting a request for an operating system utilizing the BOOTP protocol and setting an indicator identifying that this boot sequence is being made to a management server, a first virtual local area network (VLAN) including the client device;

a pre-boot execution environment (PXE) agent device, the PXE agent device located on a first local area network with the client device, to receive the BOOTP request for the operating system, to open a hypertext transport protocol (HTTP) session, to convert the BOOTP request for the operating system to a HTTP request for the operating system; and

to transmit the HTTP request for the operating system; and

a pre-boot execution environment (PXE) server, the PXE server being located on a second local area network separated by at least one router from the first local area network and a second VLAN, distinct from the first VLAN, including the PXE server, to receive the converted HTTP request for the operating system, to retrieve the operating system requested in the converted HTTP request, and to transmit the retrieved operating system via HTTP, wherein the PXE agent device receives the retrieved operating system via HTTP, converts the HTTP protocol to the BOOTP protocol, and transmits the retrieved operating system to the client device utilizing the BOOTP protocol, wherein the client sets an indicator identifying that this boot sequence is being made to a PXE server.

2. The system of claim 1, wherein the PXE client and the PXE agent device communicate in a virtual local area network (VLAN).

3. The system of claim 1, wherein at least a switch physically separates the PXE client and the PXE server.

4. A method for operating a management server, comprising:

receiving a pre-boot request from a PXE client, the PXE client requesting booting information utilizing the hipertext transport protocol (HTTP);

querying a management database for booting information for the PXE client;

receiving the booting information from the management database if the management database has the booting information for the PXE client, the booting information including instructions to install a specific operating system if the management database has booting information for the PXE client;

transmitting, utilizing HTTP, both the instructions to install a specific operating system and the operating system to the PXE client if the management database has booting information for the PXE client; and

transmitting, utilizing HTTP, a command for the PXE client to boot locally if the management database does not have booting information for the PXE client and default information in the management server for the PXE client indicates the PXE client should boot locally, wherein a first virtual local area network (VLAN) includes the PXE client and a second VLAN includes the management server, the first VLAN being distinct from the second VLAN.

5. The method of claim 4, further including transmitting a command to the PXE client to boot to an operating system on a network if the management information does not have booting information for the PXE client and the management server does not have default information for the PXE client.

6. The method of claim 4, wherein one of a switch or a router physically separates the client and the management server.

7. A method of utilizing a pre-boot execution environment (PXE) agent device, comprising:

receiving a request for an operating system, the client transmitting the request utilizing the BOOTP protocol;

opening a hypertext transport protocol (HTTP) session;

converting the request for the operating system from the BOOTP protocol to a HTTP request which utilizes an HTTP protocol;

transmitting the HTTP request for the operating system utilizing the HTTP protocol to a PXE server, the PXE server being located on a second local area network separated by at least one router from the first local area network;

receiving a retrieved operating system from PXE server utilizing the HTTP protocol;

converting the HTTP protocol to the BOOTP protocol; and

transmitting the retrieved operating system to the PXE client device utilizing the BOOTP protocol, wherein a first virtual local area network (VLAN) includes the PXE client and a second VLAN includes the PXE server, the first VLAN being distinct from the second VLAN.

8. The method of claim 7 wherein the PXE client and the PXE agent device communicate in a virtual local area network.

9. A program code storage device, comprising:

a computer-readable storage medium; and

computer-readable data, stored on the computer-readable storage medium, the computer-readable data including instructions, which when executed, cause a processor to;

receive a pre-boot request from a PXE client, the PXE client requesting booting information utilizing the hypertext transport protocol (HTTP);

query a management database for booting information for the PXE client;

receive the booting information from the management database if the management database has booting information for the PXE client, the booting information including instructions to install a specific operating system if the management database has booting information for the PXE client;

transmit, utilizing HTTP, both the instructions to install a specific operating system and the operating system to the PXE client if the management database has booting information for the PXE client; and

transmit, utilizing HTTP, a command for the PXE client to boot locally if the management database does not have booting information for the PXE client and default information in the management server for the PXE client indicates the PXE client should boot locally, wherein a first virtual local area network (VLAN) includes the PXE client and a second VLAN includes the management server, the first VLAN being distinct from the second VLAN.

10. The program code storage device of claim 9, including instructions which when executed cause the processor to transmit a command to the PXE client to boot to an operating system on a network if the management information does not have booting information for the PXE client and the management server does not have default information for the PXE client.

11. The program code storage device of claim 9, wherein one of a,switch or a router physically separates the client and the management server.