cluster:153
Warning: Undefined array key 24 in /usr/share/dokuwiki/inc/html.php on line 1453
Warning: Undefined array key -1 in /usr/share/dokuwiki/inc/html.php on line 1458
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
cluster:153 [2017/03/01 13:03] hmeij07 created |
cluster:153 [2017/12/06 10:34] hmeij07 |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | Proposal Focus | + | \\ |
| + | **[[cluster: | ||
| - | [C* multi-campus extract of key lines] | + | https:// |
| + | Due Jan 30, 2018, totally refocused on network, killing the ideas on this page | ||
| + | --- // | ||
| + | ==== NSF CC* ==== | ||
| + | * Create a $1 Million+ CC* proposal to meet the research, staff and cyberinfrastructure | ||
| + | * Needs/Wants of small, primarily undergraduate, | ||
| + | * 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' | ||
| + | * Provide for multiple off-site, geographically dispersed, backup storage targets | ||
| + | * Establish a global Data Management Plan for all institutions participation | ||
| - | Proposal Guideline | ||
| + | === 2017 === | ||
| + | * Data Driven Multi-Campus/ | ||
| + | * < | ||
| + | * RFI CC* (due April 5th, 2017) at https:// | ||
| + | * Pull Wesleyan brain storm meeting together, scheduled for 3/21/2017 | ||
| - | * leveraging a common environment and skill set amongst small, northeast, liberal arts colleges | + | === 2016 === |
| - | - we do science too | + | * RFP CC* at https:// |
| + | * Henk to find an example of somewhat larger colleges' | ||
| + | * these are all very large, | ||
| + | * https:// | ||
| + | * https:// | ||
| + | * https:// | ||
| + | * Probably more aligned with our goals, click on PDF | ||
| + | * http:// | ||
| + | * Regional Access a report to NSF, good read | ||
| + | * https:// | ||
| + | * key part: the local aspect is important (flexibility and personalized attention) to ensure researcher success and productivity...collaborating at the campus and regional levels is an important aspect in building the services | ||
| + | * XSEDE https:// | ||
| + | * for research this involves writing XSEDE proposals to get time allocations, | ||
| + | * Jeststream (allocates XSEDE resources) https:// | ||
| + | * this also requires writing proposals for time allocations, | ||
| - | - 2-4 sysadmin FTEs covering 4-8 colleges for 3 years | + | === Thoughts === |
| - | - redundancy in sysadmin coverage, round robin | + | **Until we have a 2017 CC* RFP announcements** this is a list of random thoughts to keep track of. |
| - | - each member to assess how to provide funding past year 3 | + | * 2016 Parsing of proposal language (Science-driven requirements are the primary motivation for any proposed activity.) |
| + | * Data Driven Multi-Campus/ | ||
| + | * NSF strongly urges the community to think broadly and not simply rely on traditional models when considering multi-campus and/or multi-institutional cyberinfrastructure | ||
| + | * Proposals are expected to be science-driven | ||
| + | * Proposals...significant impact on the multi-campus, | ||
| + | * methods for assured federated access | ||
| + | * Multi-institution/ | ||
| + | * across a range of disciplines, | ||
| + | * Cyber Team,2-4 awards, | ||
| + | * This program area seeks to build centers of expertise and knowledge in cyberinfrastructure | ||
| + | * Proposals in this area should describe the multi-institutional science-driven needs | ||
| + | * Proposals ... engagement, interactions, | ||
| + | * Proposals ...areas of expertise, such as networking, distributed data management, and scientific computing. | ||
| + | * Proposals may request up to four full-time equivalents (FTE) for up to three years (inside of $1.5M???) | ||
| + | * Proposals should describe plans for broadening participation, | ||
| + | * Leverage a common HPC environment among small, northeast, colleges | ||
| + | * we do science too (compare to larger colleges) | ||
| + | * need to drive proposal with unique science efforts by each college <--- important! | ||
| + | * think about how to build the data driven multi campus effort | ||
| + | * 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 (underlined=informally contacted, bolded=interested party): | ||
| + | * Hamilton, | ||
| + | * **Lafayette**, | ||
| + | * **Middlebury**, | ||
| + | * **Swarthmore**, | ||
| + | * Trinity, image analysis | ||
| + | * __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, | ||
| + | * infiniband enabled /home storage with ipoib, head node (both on UPS), sandbox | ||
| + | * ethernet storage for backup with snapshots (LVM or rsnapshot.org) (on UPS, switches) | ||
| + | * possible off site backup of data, round robin, among members | ||
| + | * Hardware desires/ | ||
| + | * Each site should offer something unique | ||
| + | * Shared with whole community of members | ||
| + | * Custom hardware requests highlight each member' | ||
| + | * Leverage a common HPC deployment software stack | ||
| + | * OpenHPC (openhpc.community) with shared deployment modules (CentOS 7.x/ | ||
| + | * Application software modules to deploy per members' | ||
| + | * Commercial software? (License type would need to be discussed with vendors) | ||
| + | * Shared skill set with experts in certain specific areas and tools | ||
| + | * Facilitate classroom usage (local temp accounts recycled by semester? | ||
| + | * User account creation | ||
| + | * Participants can request accounts on each members' | ||
| + | * Local accounts with request workflow, SSH keys federation < | ||
| + | * Collaborative non-member account requests? | ||
| + | * Meetings, ofcourse | ||
| + | * of sysadmin group | ||
| + | * of advisory group | ||
| + | * Data Management Plan (DMP) | ||
| + | * To satisfy NSF public data access policy and distribution | ||
| + | * One site for all (Islandora, Dataverse, or ???). One members' | ||
| + | * ... | ||
| - | - possible: Hampton, Middlebury, Trinity, Wellesley, Wesleyan, Williams | ||
| - | * each member will do an internal survey of local computing and storage desires | + | \\ |
| + | **[[cluster: | ||
| - | - gpu, cpu, hybrid of such, visualization, | ||
| - | - infiniband enabled /home storage with ipoib, ethernet backups with snapshots, head node...one rack (switches, UPS) | ||
| - | - possible off site backup of /home, round robin | ||
| - | * hardware desires vetted for too much redundancy | ||
| - | |||
| - | - custom hardware requests highlight each member' | ||
| - | |||
| - | * leveraging a common HPC deployment software stack | ||
| - | |||
| - | - OpenHPC with shared deployment modules | ||
| - | |||
| - | - user account creation | ||
| - | |||
| - | - each members' | ||
| - | |||
| - | * annual and bi-annual meetings | ||
| - | |||
| - | - of sysadmins | ||
| - | |||
| - | - of researchers | ||
| - | |||
| - | * develop platform for data preservation and public access | ||
| - | |||
| - | - data distribution plan | ||
cluster/153.txt · Last modified: 2017/12/06 10:34 by hmeij07
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
