my guess would be there are two cables because the sata cables are not
overly flexible at the joint
having the connector tail in either the up direction or down direction
could save a loop of cable in the chassis
On Mon, Mar 8, 2010 at 3:28 PM, David Mathog wrote:
> SATA cables may be purchased
SATA cables may be purchased with an L shaped connector. I just looked
at 10 of them and they were all like this when looking into the open end
of the angled connector (ASCII art):
+---+
| |
| --+ |
|| |
+--++-
Micha Feigin wrote:
>The problem:
>
>I want to allow gpu related jobs to run only on the gpu
>equiped nodes (i.e more jobs then GPUs will be queued),
>I want to run other jobs on all nodes with either:
>
> 1. a priority to use the gpu equiped nodes last
> 2. or better, use only two out of
We do it the opposite way quite frequently: Linux master node with Windows
slaves. You could at the very least install the Linux servers from Windows
over the network. Setup a Windows DHCP/HTTP server. Then you could at the
very least 'kickstart' or 'autoyast' the nodes. Not sure about the soft
On 3/8/10 10:14 AM, "Micha Feigin" wrote:
I have a small local cluster in our lab that I'm trying to setup with minimum
hustle to support both cpu and gpu processing where only some of the nodes have
a gpu and those have only two gpu for four cores.
It is currently setup using torque from ubu
I have a small local cluster in our lab that I'm trying to setup with minimum
hustle to support both cpu and gpu processing where only some of the nodes have
a gpu and those have only two gpu for four cores.
It is currently setup using torque from ubuntu (2.3.6) with the torque supplied
scheduler
