none
Managing user access on a GPGPU HPC Cluster. RRS feed

  • Question

  • Hi All,

    I have configured a cluster where each node has a decent graphics card and use it for performing parallel rendering. The caveats of using MS HPC in a GPGPU setting is that you must:

    1. Login a console session on all nodes with one user login, lets call him gpu-user.
    2. gpu-user must also be the user that that submits jobs otherwise the scheduler will fail because it must match the job submitter to the user that created the console session on each node.

    This is troublesome as often the data that we want to render on the cluster is sensitive and only certain users have access to it. Thus using a shared user (gpu-user) for job submission/node console login is non-ideal.

    What would be more preferable is that part of the job submission would be to login the job submitters user as the console session on each node, and then also lock the console until the job has completed.

    Does anyone know if it is possible to achieve this work flow through the job manager and/or with some scripting?
    Wednesday, November 11, 2009 2:36 PM

Answers

  • Just to give an update. After talking with a Microsoft developer at Super Computing 09 conference, apparently the Server 2008 R2 HPC Pack currently in Beta will have a way to spawn a console session on all the nodes. Can't Wait!
    Monday, November 23, 2009 5:31 PM

All replies

  • Just curious, where do these constraints come from?  Are you using CUDA or something else for the GPGPU programming?

    Cheers,

    Brian
    Thursday, November 12, 2009 7:57 AM
  • Hi.

    You probably know the guide here: http://download.microsoft.com/download/1/2/9/129ad397-4054-493e-8734-c0b3d88cbac2/GPU%20Computing%20in%20Windows%20HPC%20Server%202008_Final.docx

    because it exactly leads to the problem you state.
    However it also says:

    To create the console session automatically you can modify the machine registry so that when your compute nodes start they automatically log on a user and create an active console session. 

    So one solution would be  to reboot the nodes prior to job execution with a changed registry. Starting a console session for the owner who submitted the job.
    This could be done by a submission filter e.g..

    A more elaborate, though more elegant way would be to have another  service running there with admin rights which executes the GPGPU jobs.


    Regards,

    Johannes


    JH
    Thursday, November 12, 2009 10:45 AM
  • It is a Windows driver model issue afaik. Only the console session (and there is just one) gets access to the video driver.
    Should be the same for ATI and NVIDIA

    JH
    Thursday, November 12, 2009 10:46 AM
  • Just to give an update. After talking with a Microsoft developer at Super Computing 09 conference, apparently the Server 2008 R2 HPC Pack currently in Beta will have a way to spawn a console session on all the nodes. Can't Wait!
    Monday, November 23, 2009 5:31 PM