cluster:153
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
cluster:153 [2017/03/01 14:55] hmeij07 |
cluster:153 [2017/12/06 10:34] (current) hmeij07 |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| \\ | \\ | ||
| **[[cluster: | **[[cluster: | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | https:// | ||
| + | |||
| + | Due Jan 30, 2018, totally refocused on network, killing the ideas on this page | ||
| + | --- // | ||
| ==== NSF CC* ==== | ==== NSF CC* ==== | ||
| - | * Create a $1M+ CC* proposal to meet the research, staff and cyberinfrastructure | + | * Create a $1 Million+ CC* proposal to meet the research, staff and cyberinfrastructure |
| * Needs/Wants of small, primarily undergraduate, | * Needs/Wants of small, primarily undergraduate, | ||
| * To share faculty expertise (current research projects and new collaborations) | * To share faculty expertise (current research projects and new collaborations) | ||
| Line 11: | Line 19: | ||
| * Establish a single, participants' | * Establish a single, participants' | ||
| * Provide for multiple off-site, geographically dispersed, backup storage targets | * Provide for multiple off-site, geographically dispersed, backup storage targets | ||
| - | * Establish a global Data Management Plan for all institutions' participants | + | * Establish a global Data Management Plan for all institutions |
| Line 17: | Line 25: | ||
| * Data Driven Multi-Campus/ | * Data Driven Multi-Campus/ | ||
| - | * RFP mid March? | + | * <del>RFP mid March?</ |
| * RFI CC* (due April 5th, 2017) at https:// | * RFI CC* (due April 5th, 2017) at https:// | ||
| Line 25: | Line 33: | ||
| * RFP CC* at https:// | * RFP CC* at https:// | ||
| - | * Need to find an example of somewhat larger colleges' | + | * Henk to find an example of somewhat larger colleges' |
| + | * these are all very large, we should also investigate XSEDE and NSF/ | ||
| + | * 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, | ||
| === Thoughts === | === Thoughts === | ||
| - | Until we **have** a 2017 CC* RFP this is a list of random thoughts to keep track of. | + | **Until we have a 2017 CC* RFP announcements** |
| + | * 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 | * Leverage a common HPC environment among small, northeast, colleges | ||
| * we do science too (compare to larger 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 | * 1-3 sysadmin FTEs covering 3-6 colleges for 3 years | ||
| * redundancy in sysadmin coverage, round robin | * redundancy in sysadmin coverage, round robin | ||
| * each member to assess how to provide funding past year 3 | * each member to assess how to provide funding past year 3 | ||
| - | * Possible Members (* indicates | + | * Possible Members (underlined=informally contacted, bolded=interested |
| - | * Hamilton, Lafayette | + | * Hamilton, |
| + | * **Lafayette**, engineering college HPC | ||
| + | * **Middlebury**, ? | ||
| + | * **Swarthmore**, | ||
| + | * Trinity, | ||
| + | * __Wellesley__, ? | ||
| + | * **Wesleyan**, Gaussian HPC, text mining HPC | ||
| + | * **Williams**, Islandora DMP | ||
| * Each member will do an internal survey of local computing and storage desires, put together 1-2 racks | * Each member will do an internal survey of local computing and storage desires, put together 1-2 racks | ||
| - | * gpu, cpu, hybrid of such, visualization, | + | * gpu, cpu, hybrid of such, visualization, |
| - | * infiniband enabled /home storage with ipoib, head node (on UPS), sandbox, | + | * infiniband enabled /home storage with ipoib, head node (both on UPS), sandbox |
| - | * ethernet | + | * ethernet storage |
| * possible off site backup of data, round robin, among members | * possible off site backup of data, round robin, among members | ||
| * Hardware desires/ | * Hardware desires/ | ||
| Line 48: | Line 93: | ||
| * Custom hardware requests highlight each member' | * Custom hardware requests highlight each member' | ||
| * Leverage a common HPC deployment software stack | * Leverage a common HPC deployment software stack | ||
| - | * OpenHPC (openhpc.community) with shared deployment modules | + | * OpenHPC (openhpc.community) with shared deployment modules |
| - | * Software | + | * Application software |
| - | * Shared skill set | + | * 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 | * User account creation | ||
| * Participants can request accounts on each members' | * Participants can request accounts on each members' | ||
| - | * Local accounts with request workflow | + | * Local accounts with request workflow, SSH keys federation <del>InCommon</ |
| + | * Collaborative non-member account requests? | ||
| * Meetings, ofcourse | * Meetings, ofcourse | ||
| - | * of sysadmins | + | * of sysadmin group |
| - | * of researchers | + | * of advisory group |
| - | * Data Management Plan | + | * Data Management Plan (DMP) |
| - | * To satisfy NSF public data access policy | + | * To satisfy NSF public data access policy |
| - | * One site for all (Islandora, | + | * One site for all (Islandora, |
| - | * One members' | + | |
| * ... | * ... | ||
cluster/153.1488398151.txt.gz · Last modified: 2017/03/01 14:55 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
