1 / 13

Common User Environments - Update

Common User Environments - Update. Shawn T. Brown, PSC (stbrown@psc.edu) ‏ CUE Working Group Lead TG Quartely. Team Members. S hawn Brown (PSC, Lead) Kevin Colby (Purdue) Dan Lapine (NCSA) David McWilliams (NICS) Derek Simmel (PSC) Rich Raymond (PSC, Managing Lead)

ganya
Download Presentation

Common User Environments - Update

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. Common User Environments - Update Shawn T. Brown, PSC (stbrown@psc.edu)‏ CUE Working Group Lead TG Quartely

  2. Team Members • Shawn Brown (PSC, Lead) • Kevin Colby (Purdue) • Dan Lapine (NCSA) • David McWilliams (NICS) • Derek Simmel (PSC) • Rich Raymond (PSC, Managing Lead) • Jerry Greenberg (SDSC) • Roberto Gomez (PSC) • John Lockman (TACC) • Jim Lupo(LONI) • Diana Diehl (SDSC, TG Documentation, volunteer)

  3. Philosophy • Create commonality without destroying diversity. • Focus on user requirements and experience. • We are not developing a gateway. • We are not catering to the hero users.

  4. CUED CUE - DocumentationA centrally located, clearly itemized area for documentation of resources with both web and CLI based access. CUBE Common User Build EnvironmentAttempting to make common the tools needed for building usable scientific code across resources Common User Environment TeraGridResources CUEMS CUE Management SystemA single common command line system for managing one’s environment, with a single entry to load the CUE. CUEVCCUE Variable CollectionA set of environment variables that will be common across the TeraGrid, making job submission and resource discovery easier. CUETP CUE – Testing Platform Simple program or set of programs that can be compiled and executed through the CUE and will help to illustrate its use.

  5. CUED CUE - DocumentationA centrally located, clearly itemized area for documentation of resources with both web and CLI based access. CUBE Common User Build EnvironmentAttempting to make common the tools needed for building usable scientific code across resources Common User Environment TeraGridResources CUEMS CUE Management SystemA single common command line system for managing one’s environment, with a single entry to load the CUE. CUEVCCUE Variable CollectionA set of environment variables that will be common across the TeraGrid, making job submission and resource discovery easier. CUETP CUE – Testing Platform Simple program or set of programs that can be compiled and executed through the CUE and will help to illustrate its use.

  6. How did we proceed? • Targeted RP “liaisons” to work on implementation. • Developed implementation documents outlining the “rules” of the implementation. • Done in consultation with: • RP liaisons • SW Int working group • Campus Champions • Worked to implement the CUEMS and CUEVC portions on current TG machines.

  7. The Machines We are Working With

  8. CUEMS – Environment Management • Implementation of the Modules software environment manager on all systems • Five basic modules: • cue-login-env Contains  the  CUEVC  definitions  for  environment  variables   • cue-math     A  wrapper  for  the  modules  cue-mkl  cue-fftw cue-lapack  cue-scalapack • cue-build   A  wrapper  for  the  module  cue-compile   • cue-comm   A  wrapper  for  the  default  mpi  stack     • cue-tg     Contains  already  defined  TG  variables  for  the site • Application Modules • cue-namd, cue-gamess, cue-hdf5, etc..

  9. CUEVC – Variable Collection

  10. CUEMS – Environment Management • Current Policy – Opt In approach • Provide users a clear and simple procedure for implementing CUE as default. .nosoft – tells the system that you want modules as your default environment management .modules – Contains commented out cue modules that can be implemented at login.

  11. CUED – Documentation • Working with the documentation group to add modules documentation to TG Docs • A getting started guide on how to activate modules • https://www.teragrid.org/web/bof/cue

  12. Rolling out • Announce to the TG User Services group at next meeting. • Ask for feedback and testing. • Ask Campus Champions to test out the implementation. • Incorporate into the QA testing procedures • Already underway • Current implementation…. The Jerry Test • Announcement and opening to public.

  13. Not stopping… • Discussion of common queue names. • Continue work on CUED incorporation. • Finish fitting this into the TG SW Integration Kits • Derek Simmel (PSC)

More Related