1 / 13

NREL HPC FY20 Allocation Webinar

NREL HPC FY20 Allocation Webinar. Steve Hammond, Joyce Yang, Chris Chang, Kevin Regimbal Webinar April 30, 2019. Topics. Overview of FY20 HPC Allocation Features. Eagle. NREL Hours. Request Process. Web Form Preview. Overview of FY20 HPC Allocation Features. Aug-Sep. Oct. Jun-Jul.

rlyons
Download Presentation

NREL HPC FY20 Allocation Webinar

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NREL HPC FY20 Allocation Webinar Steve Hammond, Joyce Yang, Chris Chang,Kevin Regimbal Webinar April 30, 2019

  2. Topics Overview of FY20 HPC Allocation Features Eagle NREL Hours Request Process Web Form Preview

  3. Overview of FY20 HPC Allocation Features Aug-Sep Oct Jun-Jul Apr-May

  4. Process Request Review Allocation Implementation

  5. Online Web Form Preview

  6. Online Web Form Front Page • Should see existing allocations. • The “Copy to FY20” button should save a lot of data entry for continuing projects. • New projects: blue button

  7. Online Web Form Screen 1 • Infoboxes next to each field explain expectations • Triggered by hovering or clicking

  8. Online Web Form Screen 2 • Detailed funding info required for EERE allocation decisions • PI vs. Project Lead (previous screen) • Reference milestones and tasks back to SOW!

  9. Online Web Form Screen 3 • Current request and projections • /projects vs. Mass Store • Minimum and maximum NREL-hours • Allocation pools

  10. Online Web Form Screen 4 • Software requirements: what, %age, and how important • Approach: Describe the overall project workflow • I/O: How much data in and out of NREL’s network? • Justification: How do you intend to use the resources?

  11. Questions? Q: Are separate allocation requests required if different software will be used? A: A separate allocation request is required for each source of funding. Project activities including use of different software can be described in a single request under the “Computational Readiness” section of the request. Q: The process described is for the EERE allocation pool. How is the process different for the NREL allocation pool to cover things like LDRD? A: The process to determine within the NREL allocation pool is similar. NREL ALDs and LPMs participate in similar activities to EERE Office Directors. Q: If the same team of people is working on multiple, inter-related projects with multiple funding streams, can jobs access an aggregated allocation to simplify management of resources used by the team? A: We account for and report NREL-hour use per allocation decision. So, a unique handle is needed for each job submission. However, storage can be shared by multiple allocations. HPC Operations will contact project leads in August to establish teams (list of members) and associate those teams with use of handles for job submission and access to shared storage.

  12. Questions? Q: For a Multi-lab project, should one request per project or per lab be submitted? A: If an AOP WBS spans multiple labs, a single allocation request will serve. Otherwise one is required for each AOP project ID. Q: For large programs with future awards, how should those be handled? A: A single allocation request to cover the program needs can be submitted. Q: Will access to the large memory and accelerated nodes be handled with a “special” request? A: We plan to offer the large memory and GPGPU-accelerated nodes in normal queues like they are on Peregrine initially. This may change during the system’s life as project needs evolve. Q: How can I give critical jobs higher run priority? A: Using the Slurm option “--qos=high” allows urgent jobs to jump to the top of the queue in exchange for a higher allocation burn rate. Note that routine use of this mechanism is not allowed.Reservations are possible if situations require, see https://www.nrel.gov/hpc/eagle-job-priorities.html Q: If my allocation burn rate is not expected to be linear over the year, how can I convey that in the request? A: Please specify your expected usage by quarter in the “Approach” field.

  13. Thank you Publication Number

More Related