DokuWiki

• Create a $1 Million+ CC* proposal to meet the research, staff and cyberinfrastructure
• Needs/Wants of small, primarily undergraduate, northeast Higher Ed institutions
• To share faculty expertise (current research projects and new collaborations)
• To share staff expertise (deploy and support, sustain after grant period)
• To share unique computational capabilities in a variety of disciplines
• Establish a single, participants' wide, user directory with global access
• Provide for multiple off-site, geographically dispersed, backup storage targets
• Establish a global Data Management Plan for all institutions' participants

• Data Driven Multi-Campus/Multi-Institution Model, or/and Cyber Team
• RFP mid March?

• RFI CC* (due April 5th, 2017) at https://www.nsf.gov/pubs/2017/nsf17031/nsf17031.jsp
• Pull Wesleyan brain storm meeting together, scheduled for 3/21/2017

• RFP CC* at https://www.nsf.gov/pubs/2016/nsf16567/nsf16567.htm
• Need to find an example of somewhat larger colleges' successful proposal in 2016

Until we have a 2017 CC* RFP this is a list of random thoughts to keep track of.

• Leverage a common HPC environment among small, northeast, colleges
  • we do science too (compare to larger colleges)
• 1-3 sysadmin FTEs covering 3-6 colleges for 3 years
  • redundancy in sysadmin coverage, round robin
  • each member to assess how to provide funding past year 3
• Possible Members (* indicates interested member):
  • Hamilton, Lafayette (*), Middlebury, Trinity, Wellesley, Wesleyan (*), Williams
• Each member will do an internal survey of local computing and storage desires, put together 1-2 racks
  • gpu, cpu, hybrid of such, visualization, deep learning, etc…(no UPS, compute nodes)
  • infiniband enabled /home storage with ipoib, head node (on UPS), sandbox,
  • ethernet backups storage with snapshots (LVM or rsnapshot.org) (on UPS, switches)
  • possible off site backup of data, round robin, among members
• Hardware desires/configs to be vetted for too much redundancy
  • Each site should offer something unique
  • Shared with whole community of members
  • Custom hardware requests highlight each member's area of expertise
• Leverage a common HPC deployment software stack
  • OpenHPC (openhpc.community) with shared deployment modules
  • Software modules to deploy per members' requirements
  • Shared skill set
• User account creation
  • Participants can request accounts on each members' installation
  • Local accounts with request workflow or InCommon?
• Meetings, ofcourse
  • of sysadmins
  • of researchers
• Data Management Plan
  • To satisfy NSF public data access policy
  • One site for all (Islandora, Dspace, etc)
  • One members' expertise?
• …

Back