Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
hpc [2016/03/31 18:31] zashi |
hpc [2016/04/05 18:00] zashi [Details] |
||
|---|---|---|---|
| Line 24: | Line 24: | ||
| * <del>Will utilize MOSIX for automated process load balancng: http://www.mosix.cs.huji.ac.il/</del> Can't get MOSIX to work after a dozen too many hoops | * <del>Will utilize MOSIX for automated process load balancng: http://www.mosix.cs.huji.ac.il/</del> Can't get MOSIX to work after a dozen too many hoops | ||
| * SSH keys will let each cluster run arbitrary commands to other bits of the cluster | * SSH keys will let each cluster run arbitrary commands to other bits of the cluster | ||
| - | * rsync will be used to keep system configs (/etc/passwd,shadow,hosts et al) in sync | + | * rsync (or NFS + bind mounts) will be used to keep system configs (/etc/passwd,shadow,hosts et al) in sync |
| - | * NFS will provide shared, common storage (may be problematic as the NAS is pretty low-performance) | + | * NFS, via autofs, will provide shared, common storage (may be problematic as the NAS is pretty low-performance) |
| * Infiniband will provide PtP Ethernet connections between nodes | * Infiniband will provide PtP Ethernet connections between nodes | ||
| Line 32: | Line 32: | ||
| mpi can be used as a job dispatcher. Knottcl can act as an orchestration layer so things like aircrack-ng and john the ripper can be ran in a distributed fashion (via split dictionaries). | mpi can be used as a job dispatcher. Knottcl can act as an orchestration layer so things like aircrack-ng and john the ripper can be ran in a distributed fashion (via split dictionaries). | ||
| + | OpenCL will be leveraged so additional processing power can be harnessed from GPUs. PCI and PCIe graphics cards can fill the extra slots for low-cost additions. | ||
| + | There's even a compatibility layer for OpenCL that lets OpenCL programs run directly on an x86_64 cpu--so code only has to be written fro one arch! | ||
