Sun Grid Engine Information Center
Administering Sun Grid Engine
Index

Defining Projects

About Projects

Projects provide a means to organize joint computational tasks from multiple users. A project also defines resource usage policies for all jobs that belong to such a project.

Projects must be declared before they can be used in any of the three scheduling policy policies. Projects are used in three policy areas:

• Share-based, when shares are assigned to projects – see Configuring the Share-Based Policy
• Functional, when projects receive a percentage of the functional tickets – see Configuring the Functional Policy
• Override, when an administrator grants override tickets to a project – see Configuring the Override Policy

Grid Engine system managers define projects by giving them a name and some attributes. Grid Engine users can attach a job to a project when they submit the job. Attachment of a job to a project influences the job's dispatching, depending on the project's share of share-based, functional, or override tickets.

How to Define Projects With QMON

Grid Engine system managers can define and update definitions of projects by using the Project Configuration dialog box.

1. To define a project, on the QMON Main Control window, click the Project Configuration button.
   
   The Project Configuration dialog box appears, as shown below. The currently defined projects are displayed in the Projects list. The project definition of a selected project is displayed under Configuration.
   
   
   
2. To add a new project, click Add.
   
   
3. To modify a project, select it, and then click Modify.
   
   Clicking Add or Modify opens the Add/Modify Project dialog box.
   
   
   
   The name of the selected project is displayed in the Name field. The project defines the access lists of users who are permitted access or who are denied access to the project. See Configuring Users for more information.
   
   
   The Add/Modify Project dialog box shows the following access lists:
   • The User Lists column shows access lists that contain users who have permission to access the project.
   • The Xuser Lists column shows access lists that contain users who do not have permission to access the project.
   • If both lists are empty, all users can access the project. If a user belongs to an access list that is in the User Lists and to an access list that is in the Xuser Lists, the user is denied access to the project.
     
4. To delete a project immediately, select it, and then click Delete.
   
   
5. To add or remove users from the User Lists or Xuser Lists, click the button at the right of the User Lists or the Xuser Lists.
   
   The Select Access Lists dialog box, shown in the figure below, appears. Currently defined access lists are displayed under Available Access Lists. Currently selected access lists are displayed under chosen access lists. You can select access lists in either list. You can move access lists from one list to the other by using the red arrows.
   
   
   
6. Click OK to save your changes and close the dialog box.
   
   Click Cancel to close the dialog box without saving your changes.

Defining Projects From the Command Line

To define projects from the command line, type the following command with appropriate options:

# qconf <options>

The following options are available:

• qconf -aprj – The -aprj option (add project) opens a template project configuration in an editor. See the project(5) man page. The editor is either the default vi editor or the editor specified by the EDITOR environment variable. After you save your changes and exit the editor, the changes are registered with sge_qmaster.
• qconf -Aprj filename – The -Aprj option (add project from file) parses the specified file and adds the new project configuration. The file must have the format of the project configuration template.
• qconf -dprj project-name – The -dprj option (delete project) deletes one or more projects.
• qconf -mprj project-name – The -mprj option (modify project) enables you to modify an existing user entry. The option loads the project configuration in an editor. The editor is either the default vi editor or the editor specified by the EDITOR environment variable. After you save your changes and exit the editor, the changes are registered with sge_qmaster.
• qconf -Mprj filename – The -Mprj option (modify project from file) parses the specified file and modifies the existing project configuration. The file must have the format of the project configuration template.
• qconf -sprj project-name – The -sprj option (show project) displays the configuration of a particular project.
• qconf -sprjl – The -sprjl option (show project list) displays a list of all currently defined projects.