Using a diskless client network topology for disk duplication and configuration

• US 20030088650A1
• Filed: 04/02/2002
• Published: 05/08/2003
• Est. Priority Date: 07/30/2001
• Status: Abandoned Application

• Current Assignee: Lockheed Martin Corporation (Martin Marietta Corporation)
• Original Assignee: Lockheed Martin Corporation (Martin Marietta Corporation)
• Inventors: Mele, Michael A., Patchett, Martin B., Fassold, Richard C.
• Application Number:
  US10/114,501
• Publication Number:
  US 20030088650A1
• Time in Patent Office: Days
• US Class Current: 709/220
• CPC Class Codes: G06F 8/63 Image based installation; Cloning; Build to order
• CPC Class Codes: G06F 9/4416 Network booting; Remote initial program loading [RIPL]
• 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]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A system and method for cloning files to a plurality of client systems simultaneously over a network. Client PCs are booted to a server as “diskless clients”. Each client then executes configuration scripts that prepare mass storage devices to which the clients are connected for downloading a file or files from the server. Any type of file, including an operating system file or applications code, can be downloaded to the mass storage device. The mass storage device can be rendered bootable, should that be an appropriate action for the files that are downloaded. Configuration and log files are stored on the server for each cloned client.

Claims

1. A cloning system for cloning at least one file, said cloning system comprising:

a server executing a first operating system, said server having electronic communication with at least one client through a communications network;

a diskless client system for configuring the at least one client to operate as a diskless client;

a mass storage device being in electronic communication with said diskless client;

a cloning server configuration system executed by said server, said server configuration system enabling said diskless client to access said at least one file, said at least one file created in the context of a second operating system; and

a cloning client configuration system executed by said diskless client, said cloning configuration system preparing said mass storage device for downloading said at least one file, said cloning configuration system downloading said at least one file to said mass storage device.

2. The cloning system as in claim 1 wherein said first operating system is the same as said second operating system.

3. The cloning system as in claim 1 wherein said first operating system is different from said second operating system.

4. The cloning system as in claim 1 wherein said mass storage device is initially unconfigured and inactive, said mass storage device being of unknown type and size.

5. The cloning system as in claim 1 further comprising:

a master boot record system executed by said diskless client, said master boot record system writing said master boot record onto said mass storage device and enabling said mass storage device to be bootable.

6. The cloning system as in claim 1 wherein said server further comprises:

a server network interface to said communications network, said server network interface executing in said server, said server network interface being capable of sending and receiving communications messages;

a DHCP server executing in said server for receiving a network boot request communications message from said diskless client through said server network interface, said DHCP server sending a network boot reply communications message through said server network interface to said diskless client, said DHCP server dynamically assigning a network address to said diskless client;

a TFTP server executing in said server for sending a kernel image communications message through said server network interface to said diskless client after said network boot reply communications message is received by said diskless client;

a NFS server executing in said server for granting access to said diskless client for said at least one file; and

a floppy disk bootROM image system for creating a bootROM image on a floppy disk, said bootROM image enabling said diskless client to begin a bootstrap procedure from the floppy disk and continue the bootstrap procedure over said communications network.

7. The cloning system as in claim 6 wherein the diskless client further comprises:

a client network interface executing in said diskless client for sending and receiving communications messages;

a means for booting said diskless client through said client network interface;

a BOOTP client executing in said diskless client for sending a network boot request communications message from said diskless client through said client network interface to said DHCP server, said DHCP server sending a network boot reply communications message through said client network interface to said diskless client;

a TFTP client executing in said diskless client for receiving a kernel image communications message through said client network interface after said diskless client receives said network boot reply communications message; and

a NFS client executing on said diskless client for accessing said at least one file through said NFS server.

8. The cloning system as in claim 6 wherein said cloning server configuration system comprises:

a network address system for establishing a block of network addresses that are to be dynamically assigned to said diskless client;

a network address lease system for establishing a length of time during which said each network address from said block of network addresses can be used by the cloning system;

a kernel image protocol enabling system for enabling said TFTP server to execute on said server;

a diskless client file storage preparation system for creating a space for storing said at least one file; and

a logging preparation system for enabling said server to receive status messages from said diskless client, said logging system storing said status messages.

9. The cloning system as in claim 1 wherein said cloning client configuration system further comprises:

a file creation system for creating and storing said at least one file.

10. The cloning system as in claim 1 wherein said cloning client configuration system comprises:

a file creation system for creating and storing said at least one file; and

an operating system creation system for creating and storing said second operating system, said second operating system being downloaded from said server to said diskless client, said master boot record transferring control to said second operating system after said master boot record completes its part of a boot procedure of said mass storage device.

11. A cloning system having a network upon which a server and at least one diskless client cooperatively operate, said cloning system enabling the diskless client to clone at least one file initially located on the server, said cloning system comprising:

a subnet creation system for creating a subnet including said server and said at least one diskless client;

an IP address assignment system executing in said server, said assignment system dynamically assigning limited lease Internet Protocol (IP) addresses to said at least one diskless client on said subnet;

a file access path connecting said at least one diskless client to said server through said subnet, said path using said IP address assigned to said at least one diskless client, said path enabling said at least one diskless client to access said at least one file;

a file transfer protocol, said file transfer protocol being understood by said at least one diskless client and said server, said file transfer protocol enabling transfer of said at least one file from said server to said at least one diskless client over said file access path;

at least one mass storage device, said at least one storage device having electronic connection to said at least one diskless client;

a file transfer system for transferring said at least one file from said server to said at least one diskless client over said file access path using said file transfer protocol, said at least one diskless client transferring said at least one file to said at least one mass storage device;

a monitoring system for maintaining a cloning system execution progress log, said monitoring system storing said log on said server.

12. A method for cloning at least one file comprising:

enabling network communications between a diskless client and a server;

accessing the at least one file by said server;

booting the diskless client to said server through said network communications;

creating by the server a network pointer to said at least one file;

accessing said network pointer by said diskless client through said network communications;

creating at least one client-specific area on said server;

configuring said server to allow said diskless client to access said at least one file through said network pointer;

copying said at least one file from said server through said network communications to said diskless client;

copying by said diskless client said at least one file to a mass storage device, said mass storage device having electronic communication with said diskless client; and

creating and populating by said diskless client a copying progress log; and

writing by said diskless client said progress log to said server.

13. The method as in claim 12 further comprising:

copying said at least one file containing a currently non-executing operating system file having separate identity from any operating system currently executing on said server,

copying at least one applications code file;

copying a kernel image file, said kernel image file having code that executes in said diskless client; and

copying at least one cloning command file.

14. The method as in claim 13 further comprising

partitioning said mass storage device;

downloading said currently non-executing operating system file from said server to said diskless client, said diskless client storing said currently non-executing operating system on said mass storage device;

creating a swap file on said mass storage device;

downloading said at least one applications code file from said server to said diskless client, said diskless client storing said at least one applications code file on said mass storage;

verifying that said mass storage device is error-free; and

writing a master boot record onto said mass storage device.

19. A communication network comprising at least two nodes according to claim 12.

20. Electromagnetic signals traveling over a computer network comprising:

said electromagnetic signals carrying information for the practice of the method according to claim 12.

21. A computer readable medium containing instructions for the practice of the method according to claim 12.

15. A method for cloning at least one file over a communications network,

locating said at least one file on a server, the server having electronic communication with a client, said client having electronic communication with a mass storage device;

configuring the server for cloning said at least one file to said mass storage device through the communications network, the communications network connecting the server and the client;

creating command files, said command files stored on the server, said command files created for execution on the client, said command files enabling cloning of said at least one file;

booting the client from a network boot device,

requesting from the server an IP address,

responding by the server to said requesting step with said IP address and a pointer to a directory on the server, said directory having a kernel image;

configuring by the client a network interface device with said IP address;

requesting by the client a download of said kernel image from the server;

responding by the server with said download of said kernel image to the client;

executing on the client said kernel image;

requesting by the kernel image executing on the client network parameters from the server;

configuring, by the client, network access for the client using said network parameters;

bringing the client into the network;

establishing a connection between the client and at least one file on the server, the client having read and write access to the at least one file;

downloading said at least one file and said command file from the server to the client, the client executing said command file, said command file storing said at least one file on said mass storage device.

16. The method as in claim 15 further comprising:

copying an operating system file having a currently non-executing computer operating system from the server to said mass storage device through the client; and

copying at least one applications code file from the server to said mass storage device through the client.

17. The method as in claim 16 further comprising:

determining, by the client, characteristics of said mass storage device;

partitioning, by the client, said mass storage device according to said characteristics;

downloading said currently non-executing operating system file from the server to the client, the client storing said currently non-executing operating system on said mass storage device;

creating a swap file on said mass storage device;

downloading said at least one applications code file from the server to the client, the client storing said at least one applications code file on said mass storage;

verifying that said mass storage device is error-free; and

writing a master boot record onto said mass storage device.

18. The method as in claim 15 further comprising:

retaining symbolic links associated with said at least one file;

preserving relationships between said at least one file and a copy of said at least one file stored on said mass storage device;

preserving access permission and timestamp information associated with said at least one file, after said at least one file is copied to said mass storage device; and

copying at least one directory recursively to retain a hierarchical directory structure, said at least one directory stored on the server, said at least one directory containing said at least one file.