How to Create User-Based, Project-Based, and Department-Based
Functional Scheduling
Use this setup to create a certain share assignment of all the resources in
the cluster to different users, projects, or departments. First-come, first-served
scheduling is used among jobs of the same user, project, or department.
StepsIn the Scheduler Configuration dialog box, select the Share Functional
Tickets check box. See Sharing Functional Ticket Shares, and the sched_conf(5) man page.
Specify the number of functional tickets (for example, 1000000) in the
scheduler configuration. See Configuring Policy-Based Resource Management With QMON, and the sched_conf(5) man
page.
Add scheduling-relevant items:
Assign functional shares to each user, project, or department. See Configuring User Access Lists With QMON,
and the access_list(5) man page.
Assign the shares
as a percentage of the whole. Examples follow:
For users: UserA (10)
UserB (20)
UserC (20)
UserD (20)
For projects: ProjectA (55)
ProjectB (45)
For departments: DepartmentA (90)
DepartmentB (5)
DepartmentC (5)
Configuring the Override Policy
Override scheduling enables a grid engine system manager or operator to dynamically
adjust the relative importance of one job or of all jobs that are associated with
a user, a department, a project, or a job class. This adjustment adds tickets to the
specified job, user, department, project, or job class. By adding override tickets,
override scheduling increases the total number of tickets that a user, department,
project, or job has. As a result, the overall share of resources is increased.
The addition of override tickets also increases the total number of tickets
in the system. These additional tickets deflate the value of every job's tickets.
You can use override tickets for the following two purposes: To temporarily override the share-based policy or the functional policy
without having to change the configuration of these policies.
To establish resource entitlement levels with an associated fixed
amount of tickets. The establishment of entitlement levels is appropriate for scenarios
like high, medium, or low job classes, or high, medium, or low priority classes.
Override tickets that are assigned directly to a job go away when the job finishes.
All other tickets are inflated back to their original value. Override tickets that
are assigned to users, departments, projects, and job classes remain in effect until
the administrator explicitly removes the tickets.
The Policy Configuration dialog box displays the current number of override
tickets that are active in the system.
Note - Override entries remain in the Override dialog box. These entries can
influence subsequent work if they are not explicitly deleted by the administrator
when they are no longer needed.
Configuring the Override Policy With QMON
At the bottom of the QMON Policy Configuration dialog box,
click Override Policy. The Override Policy dialog box appears.
 Override Category List
Select the category for which you are defining override tickets: user, project,
department, or job.
Override Table
The override table is scrollable. It displays the following information: A list of the members of the category for which you are defining tickets.
The categories are user, project, department, job, and job class.
The number of override tickets for each member of the category. This
field is editable.
QMON periodically updates the information that is displayed
in the Override Policy dialog box. Click Refresh to force the display to refresh immediately.
To save all override changes that you make, click Apply. To close the dialog
box without saving changes, click Done.
Changing Override Configurations
Click the jagged arrow above the override table to open a configuration dialog
box. For User override tickets, the User Configuration dialog box appears.
Use the User tab to switch to the appropriate mode for changing the configuration
of grid engine users. See Configuring User Objects With QMON.
For Department override tickets, the User Configuration dialog box
appears. Use the Userset tab to switch to the appropriate mode for changing the configuration
of departments that are represented as usersets. See Defining Usersets As Projects and Departments.
For Project override tickets, the Project Configuration dialog box
appears. See Defining Projects With QMON.
For Job override tickets, the Job Control dialog box appears. See "Monitoring and
Controlling Jobs With QMON" in N1 Grid Engine 6
User's Guide.
|