11/شعبان/1429 05:43 مHi
What are the access Rights Required for Submitting the Job to the HPC Server.
Thanks in Advance
26/شعبان/1429 05:30 مHi Murthy,
Users can submit jobs to the HPC cluster if they have been added as users to the cluster. You can find a link to user management on the To-Do page of the HPC Server management console.
Ryan Waite - Product Unit Manager - Windows HPC
26/شعبان/1429 05:31 مالمشرفYou can configure your Users and Admins in the HPC CLuster Manager console (just go to Conifguration -> Users). Only Domain Users can run jobs on the cluster. If you add a Domain Account as a user, that user will be automatically added to the Local Users group on all cluster nodes.
Does that answer your question?
17/رمضان/1429 08:10 م
I'm using CCS 2003 and the CCP SDK in order to submit commands asynchronously. Unfortunately GetNewCommandId() and ExecuteCommand() require Cluster Administration priveleges in order to execute the command properly without any exceptions. Is there any way to make it so that the command can be executed by a Cluster User (for security purposes)?
We have a custom application that solves a mathematical problem, and we need the results as soon as one of the processors in the cluster has solved it. We want to stop the command/job as soon as a solution has been calculated, and go on to the next calculation. This made using GetNewCommandId, ExecuteCommand, and EndCommand ideal for our purposes (by setting IsAsynchronous to true on ICluster). Having the program that submits the command/job run as a cluster administrator (and having to hard-code username/passwords into the application) goes against every security-oriented bone in my body. On that topic as well, why doesn't the scheduler running on the machine submitting the command/job just use windows authentication?
Apologies for the multi-faceted question, but since this thread is already asking questions about access rights it seemed like the best place to ask it.
17/رمضان/1429 10:35 مالمشرفBen,
Unfortunately those APIs are not available to non-Admins, since they are a) designed to back "Clusrun" b) Allow execution of arbitrary commands on the machine at any time, thereby bypassing the scheduler/job queue.
I think you should be able to accomplish what you are trying to do using standard jobs (rather than remote commands). You can have your job write out to a file or named pipe which you can listen to from a client. Also, if you consider moving to HPC Server 2008, we have a new SOA programming model which might be good for this type of model.
As for your Windows Auth question . . . because jobs can sit in the queue for quite a long time before they run, it's necessary that we cache credentials with which to log the user into the compute node (since the user may be long gone when the job actually gets started). We are continually looking into ways to improve this story and hope to have something new in v3.
- تم الاقتراح كإجابة بواسطة Josh BarnardModerator 17/رمضان/1429 10:35 م