Locking down features of HPC for end-users? RRS feed

  • Question

  • If this is the wrong forum, please redirect me to the appropriate one.

    I have built the capability to use Microsoft HPC into our company's software and the question I got from the sales team were: "Can we as the vendor bill for the usage of Azure usage?" and "Could we lock down azure and/or workstation machines?"

    If we offer customers the ability to use Microsoft HPC for an in-premise cluster, the fear is that when we support also adding cloud instances the customer will get that for free because it only involves provisioning new machines. But we have to do a lot of work to be able to support this, so obviously we would like a way (1) for us to bill the customer for their cloud usage, instead of Microsoft, and (2) have some way to restrict the use of workstation and azure machines.

    With the second point, I thought I could submit a job and restrict it to the ComputeNodes group. But even then, if the job is queued, a user could still modify the job before it starts running. I would appreciate any feedback you have.

    Thursday, October 27, 2011 9:55 AM