- NSF documents & others that we try to keep up with as these inform our work
- XSEDE vision & mission
- Strategic Goals each broken down into subgoals; KPIs built around these goals:
- Deepen and Extend Use (49% of budget)
- Advance the ecosystem (39% of budget)
- Sustain the ecosystem (11% of budget)
- 5 year budget invested by strategic goals.
- Partnership of 19 institutions
- Collaborations with other NSF funded projects (as an unfunded project)
- Support the community through allocated resources, user portal, ECSS service, training & workforce development
- XSEDE has supported nearly $2 Billion to date in federal research (includes NSF, DOD, DOE, NIH, NASA, DOC, etc.)
- User Survey shows high responses for overall satisfaction, awareness of XSEDE services. Suggested improvements continually request more and faster. About 25% of XSEDE users are new every year so onboarding is always important.
- ECSS saves about 13 mos per project, equates to about a $7.8M value in RY2.
- Associated with several Gateways
- Enhancing user productivity is an ongoing focus of the project
- XSEDE allocated resources are provided through NSF grants to the SP institutions (not part of XSEDE budget). NSF requires them to work with XSEDE.
- Science impact: stories that make use of multiple sites, use ECSS, etc.
- Possible to report on amount of data/disk residency for projects in various categories (won't call out PIs).
- In addition to XAB, we have a User advisory committee who provides input.
- Service Provider Forum
- Mission is to actively engage a broad/diverse cross-section of the open science community. Public, potential users, current users. Front line of people using resources or may potentially have a need
- Workforce Development
- provide learning resources, training, education, student preparation
- User engagement
- user guides, working with SPs, ticketing
- Broadening Participation
- engage underrepresented minority researchers
- User Interfaces & Online Information (UII)
- enables discovery & understanding of XSEDE's capabilities & services via website & user portal
- Campus engagement
- promotes & facilitates participation of diverse community of campuses
- Gaps/needs not being met?
- Don't see any. Whether XSEDE should play in innovation & development. Tool development/augmentation allows us to more flexibly respond to user needs.
- Advance & sustain e-infrastructure, connector of resources, software, services
- Connecting SPs to XSEDE & eachother
- Making it simple as possible for CI ecosystem outside XSEDE to operate software in ways that leverage XSEDE
- Provide capabilities: security, login, data, information services. Formal process based on use case analysis, priority, adaptation & use of preexisting tools.
- Current efforts
- research software portal
- Kepler Workflow service
- Globus toolkit replacement
- Resource description repository improvements
- Federated access across CI
- Usage trackgin in support of ROI analysis
- XCRI (campus resource integration) software toolkits
- XCBC - XSEDE compatible basic cluster kit–build an XSEDE-like basic cluster based on OpenHPC
- XNIT - XSEDE National Integration Toolkit - open-source scientific software that you can install on a cluster already running
- Globus Connect server config mgmt
- Jetstream virtual clusters
- Cluster monitoring toolkit
- How to be sure efforts aren't duplicated?
- Leverage Open HPC. Not developing anything new in XCRI, but packaging & distributing. RACD focusing on integration of SPs with XSEDE. Leverage as much as possible. Almost never build from scratch. However, many specialized requirements exist.
- How is XCI hurting due to smaller budget?
- Ability to adapt to new & emerging needs. Ability to deliver tools that help integration of resources, management software. One of our biggest growth areas.
- Have approx 4.5 FTE
- Which are most critical offerings?
- Software for SPs. Software repo is scattered-widely liked. Globus is downloaded a lot. A lot of demand for XDMoD and cloud tools.
- Goal to improve productivity through collaborations with researchers
- Extended support for research teams
- Extended support for community codes
- Extended support for science gateways
- Novel & innovative projects
- Extended Support for Training, Education and Outreach – pairs ECSS staff with campus champions
- Answer 5 questions to request ECSS service to get PIs thinking
- Over 700 cumulative requests since 2010
- 64 staff across 10 sites.
- Close to 400 attendees at ECSS symposia
- 539 adaptive reviews
- 129 NIP projects mentored
- 47 ECSS projects
- Overall high satisfaction ratings from PIs
- ECSS Symposium Series open to everyone.
- How is ECSS managing requests
- Hard to scale ECSS since it requires staff time. Have found the demand is still matching what we can make available. Having PIs answer the 5 questions filters out those who aren't ready for ECSS assistance. If demand increases we would have to turn away PIs.
- Collaborative nature of ECSS. Distribute a lot of knowledge so people can move on independently.
- Install, connect, maintain, secure, evolve integrated CI
- Work toward high availability of up time for critical services
- Data transfer services
- XOC: user support and monitor central services
- SysOps: maintain & monitor enterprise services & execute XES Cloud virtualization plan
- Allocations process–map users, resources, support to generate science results
- 900+ requests/year, 776 startup requests, 177 educational requests
- ORCID integration to help identify contributions from user facilities such as those allocated via XSEDE. Hope to roll out this quarter
- XRAS administrative workflow evaluation
- Redesigning accounting service
- Demand matched recommended in March 2018 & has stayed close to that level since. Number of large requests rejected. Working to reduce rejection rates. Goal is not to force red tape on users but find best matches between users & resources
- To be presented at the beginning of the February XAB call.
| ||Close Meeting|| || |