| 1 | | = Notes on parallelization of imaging = |
| | 1 | The task of parallelization of imaging basically involves running multiple instances of nodeHandler which would launch different images on different nodes. The basic sequence of imaging of nodes as of now is as follows: |
| | 2 | |
| | 3 | 1. The user runs the script imageNodes with the nodes and the image to be loaded as inputs. |
| | 4 | |
| | 5 | 2. The parameters are passed on to the nodeHandler which then resets the specific nodes using cmc. |
| | 6 | |
| | 7 | 3. It also launches the frisbee server from the tftpboot which sends out the particular image on a multicast address and creates tftp links to the node to provide nodes with the memory based image. |
| | 8 | |
| | 9 | 4. On the node side, the nodes when started boot into the memory image and then launch the frisbee client. |
| | 10 | |
| | 11 | 5. The frisbee client fetches disk chunks from the frisbee client and writes it to the hard disk. |
| | 12 | |
| | 13 | 6. The tftp links for the nodes are then removed. |
| | 14 | |
| | 15 | 7. From now on the nodes boot up from the image stored in the hard disk. |
| | 16 | |
