Also in GlusterHPC, we configure few of the cluster monitoring/scheduling packages. It can also be used to only configure HPC applications on all the cluster nodes. -Amar Tumballi On Wed, Jun 28, 2006 at 03:13:48PM -0700, Susumu Urata (Technocross) wrote: > I would like to confirm the following. > > 1. GlusterHPC objective is to distribute the master image to all > the clients so that the each computing node has the same image to > perform the HPC jobs. > This is why the Gluster collects the client network information and > then distributes the image to everyone at the same time. Once the > image is distributed, the master and the clients can be booted up > normally. > > 2. GlusterEP objective is to capture the individual client node > image and store it to the master node so that the each client node > can be rebooted with Gluster client to provision the system whenever > the local boot image is lost or add a new node. Provisioning allows > the stored image to be loaded to the local disk based on the > username. This way, the client node images can be managed centrally > and no more loading of OS with a CD is required. > > Susumu Urata > Technical Consultant > > 408-873-2760 (Voice) > 408-873-2761 (Fax) > > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxx > http://lists.nongnu.org/mailman/listinfo/gluster-devel >
