On Wed, Feb 15, 2017 at 12:34:08AM +0200, Ben Daniel Pere wrote: > The suggestion sounds good but I'm not sure I understand step 1 - if it's > going to be assigned by project and not user - can I still have "powerful" > users in my normal default project that have more tickets there? > I should really read about projects. thanks for the lead.
If you mean you have a pre-existing project and want different users within that project to have different priorities then no that is incompatible with this scheme. With functional share (which it sounds like you are using) projects are compared to projects and users to users independently. Therefore if you already have projects with multiple members and want to prioritise different users within a project differently you would have to assign priority directly to users and that means jobs in the cheap queue would affect the regular queues. The scheme I suggested is based on the idea of each project (except the cheap project) having a single member and therefore being able to act as a proxy for that user when they are not requesting the cheap project/queue. This precludes using projects for grouping users in other ways. If you are already using projects for something there may be a way to adapt it but without details of how you currently use projects I can't really speculate how. You might, depending on what you are doing with projects, be able to replace them with departments. William
signature.asc
Description: Digital signature
_______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
