Changes between Version 18 and Version 19 of Internal/VirtualPL/ParallelImaging

Timestamp:

Nov 9, 2006, 5:13:18 PM (18 years ago)

Author:

anonymous

Comment:

—

Internal/VirtualPL/ParallelImaging

@@ -1 @@
-== Steps in Imaging a Node ==
+= Investigating parallel imaging using gexec = 
+
+== Current approach for imaging a node ==
 
 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:
@@ -11 +13 @@
  7. From now on the nodes boot up from the image stored in the hard disk.
 
+== Changes needed for parallel imaging processes ==
 The imaging of nodes in parallel involves launching multiple instances of nodehandler which in turn implies launching more than one frisbee servers with different multicast addresses throwing away different images. At present the frisbee server settings are such that one multicast address per domain is allowed. For e.g. if a user is using a sb only one multicast address for a particular sb is allowed. So in case a user runs a second imageNodes in parallel, the frisbee server fetches the same nulticast address that results in an error. Thus the basic steps involved in parallelization would be :
 
+
+=== Basic steps === 
  1. Tweaking the way frisbee server is launched, so that even if two frisbee servers are launched in the same domain, they throw images on different multicast addresses.
  2. Making appropriate changes in nodeHandler.rb since right now the script only allows one instance of nodeHandler to run at a time. 
@@ -131 +136 @@
 Date 10/26/2006
 
-Ping Experiments on Grid:
+== Ping Experiments on Grid = :
 
 Ping experiments have been performed to determine the performance of grid when large number of nodes are being imaged in parallel, with different images. The results have been tabulated below: