[IT认证]Windows HPC ServerJob Templates White Paper.doc

Windows HPC Server 2008 Job TemplatesMicrosoft CorporationPublished: June 2008, Revised September 2008AbstractJob templates, which are simply custom submission policies, help streamline the job submission process in Windows® HPC Server 2008. The IT administrator defines the job template, then the user specifies the desired job template at the command line or in the Administration Console, and the job is off to the compute cluster. For the IT administrator, job templates provide a way to control the job submission processthey provide a means of partitioning the cluster, prioritizing the jobs, and limiting the resources used by jobs. They let the IT administrator specify different handling for different types of jobs. For the user, job templates provide a way to easily submit a job without having to obtain an in-depth understanding of how the Job Scheduler works. Job templates serve as a pattern for the creation of jobs that meet the users processing needs, while also conforming to the organizations resource allocation policies. Job templates are powerful, easy to use, and can save time and effort for both users and IT administrators. Windows HPC Server 2008 Job TemplatesThis document was developed prior to the products release to manufacturing, and as such, we cannot guarantee that all details included herein will be exactly as what is found in the shipping product. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.© 2008 Microsoft Corporation. All rights reserved.Microsoft, Active Directory, SQL Server, Windows, the Windows logo, Windows PowerShell, and Windows Server are trademarks of the Microsoft group of companies.All other trademarks are property of their respective owners.ContentsJob Templates in Windows HPC Server 20081What Is a Job Template?2How Is a Job Template Created?3Creating a Basic Job Template3Setting Permissions on the Job Template9How Does an IT Administrator Use Job Templates to Address Common Scenarios?11Using a Job Template to Constrain Resource Allocation11Using a Job Template to Prioritize Access to Shared Resources15Using a Job Template to Constrain a Group of Users to a Particular Node Group17Using the Default Template22How Is the Job Template Enforced?24How Does the User Submit Jobs with a Job Template?25Conclusion: Powerful and Easy to Use32Appendix33Glossary35Job Templates in Windows HPC Server 2008High performance computing (HPC) applications use a cluster of computers working together to solve a single computational problem or single set of closely related computational problems. Windows® HPC Server 2008 enables such cluster-based supercomputing based on x64 versions of the Windows Server® 2008 operating system. Windows HPC Server 2008 can efficiently scale to thousands of processing cores and provides a comprehensive set of deployment, administration, and monitoring tools that are easy to deploy, manage, and integrate with an existing infrastructure. A wide range of software vendors in various vertical markets have designed their applications to work seamlessly with Windows HPC Server 2008, so users can submit and monitor jobs from within familiar applications without having to learn new or complex user interfaces.Windows HPC Server 2008 provides a host of features, including a more advanced Job Scheduler, a faster Microsoft® Message Passing Interface (MS-MPI), rapid deployment options using Windows® Deployment Services (WDS), and a new management interface built on the Microsoft® System Center user interface (UI) that supports Windows PowerShell as a preferred scripting language. Windows HPC Server 2008 takes advantage of Windows Server 2008 failover services, in addition to the failover clustering capabilities of Microsoft® SQL Server®, to provide for high availability and redundancy.One of the most powerful new features in Windows HPC Server 2008 is the ability to create job templates. A job template is a custom submission policy created by an IT administrator to define the job parameters for an application, freeing the user from having to learn the Job Scheduler nomenclature before submitting a job from the HPC Job Manager or command line. The IT administrator can use job templates to easily manage job submission and optimize cluster usage. Jobs submitted with job templates all enter a single queue, making the job queue easier to monitor and manage. For the user, job templates simplify the process of submitting the jobthe user just specifies the desired template to use, so no in-depth job scheduling knowledge is required.In this white paper, we describe how job templates can help the IT administrator partition, prioritize, and limit cluster resources. We show how easy it is to create, edit, and use job templates for some common scenarios. We also describe some more advanced options that an IT administrator may want to employ. This white paper provides IT administrators and users with important information needed to put job templates to work in their own cluster environments.What Is a Job Template?Job templates are one of the most helpful features in Windows HPC Server 2008. Simply put, job templates are custom submission policies configured by the IT administrator and employed by the cluster users to submit jobs. Administrators can create a number of different job templates, and then let users pick the one that is right for their job. Most job admission policies can be created using job templates with just a few mouse clicks. Submission filters (which parse and validate a jobs XML file) are also supported in Windows HPC Server 2008 to enable more complex scenarios.Job templates enable IT administrators to provide sets of defaults and constraints for the different jobs submitted to the system. Job templates let the IT administrator:· Enforce run time and size limits on jobs.· Limit job priority.· Send different types of jobs to different sets of nodes.· Partition the cluster for different users groups.· Simplify job submission for the user.· Customize the job submission process in many ways to support a variety of scenarios.To accomplish these goals, the IT administrator can:· Create one or more job templates.· Select a set of job properties for the job template. For each job property, the administrator can provide: o A default value that will be used on all job properties not set by the user.o A list or range of acceptable values that the user can provide.· Set permissions for which users or groups can submit jobs using each template.The job queues used in many third-party scheduling products also provide some of these abilities; however, the jobs submitted with job templates in Windows HPC Server 2008 all enter a single queue. This keeps all of the jobs that are waiting to execute in one place, so job queue is easier to monitor and manage.Because job templates can define default values for any job properties, they free the user from having to learn the Job Scheduler nomenclature before submitting a job. Users can select the desired template and easily submit the job from the command-line interface or the HPC Job Manager.How Is a Job Template Created?The IT administrator creates the job templates using an easy wizard-driven process that provides many useful options. We start by describing how to create a simple job template and how to set permissions to control access to it. We then explain how to use job templates for some common scenarios: partitioning the cluster, prioritizing access to shared resources, and constraining resources such as the run time and size of jobs. Finally, we discuss the default job template and explore the more advanced options that an administrator may want to use.Creating a Basic Job Template We begin by creating a simple, basic job template that limits the priorities that users can assign to their jobs. The process starts in the Administration Console (from the Start menu, click on HPC Cluster Manager).1. Click Configuration in the lower-left pane of the HPC Cluster Manager, and then click Job Templates in the Navigation pane.2. In the Job Templates results pane, a new installation displays a default job template. You can clone that template and edit it, or you can create a new job template. In this example, we create a new job template. 3. Select New in the Actions pane on the right. Figure 1 Job templates pane4. The Generate Job Template wizard launches. On the Welcome page, you can provide a name for the new job template. You can also provide a description for the new job templatethis is optional, but descriptions may be helpful if you create many job templates. In this example, we use the default, New Job Template 1, as a name for our template. Click Next.Figure 2 Enter Template Name page5. On the Job Run Times page, you can enter a maximum run time. This is optional, but in general it is recommended that all cluster administrators enforce a maximum run time on jobs. Figure 3 Limit Run Time page6. On the Job Priorities page, you can set a default priority and a maximum priority from the drop-down menus. There are five options: Lowest, BelowNormal, Normal, AboveNormal, and Highest.For this example template, set the Default priority to Lowest and the Maximum priority to BelowNormal, and then click Next. A user submitting a job with this template now has only those choicesif the user does not specify the priority as BelowNormal, the job will be submitted as Lowest priority; no jobs submitted with this template can submit a job with a higher priority.Figure 4 Set Priorities page7. On the Project Names page, you can ensure that jobs submitted to this template must name a project from a specified list. This lets you more easily catalog and track the jobs submitted to your cluster.In this example, select Dont constrain the Project Name for jobs submitted to this template. Click Next.Figure 5 Set Project Names page8. On the Node Groups page, you can constrain the node groups on which jobs submitted to this template may run. You may choose to specify that jobs submitted to this template may run only on nodes that are in all of the selected node groupseffectively partitioning the clusteror choose to route jobs to nodes that meet certain characteristics. Note: For more details on how to use job templates to partition clusters, see the section Using a Job Template to Constrain a Group of Users to a Particular Node Group later in this document.For this example, select Dont constrain the Project Name for jobs submitted to this template.Figure 6 Limit Node Groups page9. On the Finish page, click Finish.Figure 7 Finish page10. In the Administration Console, you can see that the new template has been added to the list. You now have a job template that is ready for use, but you may want to set permissions so that users only have access to the appropriate templates.Figure 8 Administration ConsoleSetting Permissions on the Job TemplateAccess control is the process of authorizing users, groups, and computers to access objects on the network or computer. The access control list (ACL) is a list of permissionswhich define the type of access granted to a user or group for an object or object propertyattached to the job templates. Permissions let the IT administrator control who can use each particular template to submit jobs.1. In the Job Templates view, highlight New Job Template 1 and click Set Permission in the Actions pane on the right.Figure 9 Jobs Template view2. The Permissions for New Job Template 1 dialog box appears. Here you can choose the permissions to grant or deny for the different groups of users. Click OK, and then click Apply.Figure 10 Set permissionsNote: For each user or group, the IT administrator can specify privileges: Submit Job, Modify, Full Control, or Special Permissions. For normal users, Submit Jobs is sufficient. The Modify privilege lets the IT administrator delegate the management of the template to the selected user or group. The Full Control option should be reserved for the cluster administrator, because this privilege allows the user to remove the job template altogether.For more information about defining permissions with ACLs, see: or click on the Learn about access control and permissions link at the bottom of the dialog box.In this example, we have created and set permissions on a basic template. Now we explain how an IT administrator can use templates to streamline the management of the job submission process.How Does an IT Administrator Use Job Templates to Address Common Scenarios?Using a Job Template to Constrain Resource AllocationJob templates bind the users processing needs and the organizations resource allocation policies together. With job templates, the IT administrator can enforce and mandate the delivery of resources to user groups in ways that support the organizations productivity goals. For example, administrators can use job templates to require that:· All jobs share nodes (run non-exclusively).· Run-time limits are enforced on all the jobs. · Nodes are partitioned and divided among projects in particular ways that reflect the processing deadline constraints or organizational structure.Suppose an organization has two groups of users: one group that owns the cluster and has mission-critical applications to run, and the rest of the users, who may occasionally have jobs they want