Skip to content Skip to navigation

"Fall 2017 Use Cases and Capability Delivery Plans" Priorities by User Requirements Evaluation and Prioritization (UREP) Team

We asked the UREP to rate the usefulness of each of the following use cases and their proposed Capability Delivery Plans (CDPs) at the end of 2017 to assess their importance. These were features requested by XSEDE stakeholders during 2017. The results will guide our work during 2018.

The UREP used the following rating scale.

5 star - XSEDE should do this. (high priority)
4 star - XSEDE should do this. (normal priority)
3 star - XSEDE should do this. (low priority)
2 star - XSEDE should not do this. (maybe)
1 star - XSEDE should not do this. (definitely)

Prioritized ItemAverage RatingIndividual Ratings
SPI-05: Active account information
(Capability Delivery Plan)

This use case, from the XSEDE security incident response team, describes how team members need to be able to quickly obtain a list of all resources and services on which a specific XSEDE user identity has an active account. This is needed both for providing user support (e.g., help desk) and for handling account compromises. The delivery plan calls for updates to the existing XSEDE user portal User Query interface to enable searching by local SP usernames (not just XSEDE usernames) and to show current account status (active/inactive) in results.

4.7 of 5 stars
(20 votes)
5 star (16)
80%
80%
4 star (1)
5%
5%
3 star (3)
15%
15%
2 star (0)
0%
0%
1 star (0)
0%
0%
no vote (0)
0%
0%
SPI-06: Emergency account suspension
(Capability Delivery Plan)

This use case, from the XSEDE security incident response team, describes how a staff member responding to an account compromise needs to temporarily prevent a specific user account from being used on XSEDE resources and services. The delivery plan proposes creating a secure directory of SP security administrator contacts, enhancing the XSEDE central database to track the status of account suspensions, and creating a secure web interface for use by the XSEDE security operations team that would automate the labor of requesting, tracking, and releasing account suspensions across the independent XSEDE service providers. Total effort proposed is 25 person weeks (just over 6 person months).

4.3 of 5 stars
(20 votes)
5 star (12)
60%
60%
4 star (4)
20%
20%
3 star (2)
10%
10%
2 star (1)
5%
5%
1 star (1)
5%
5%
no vote (0)
0%
0%
SPI-02: Guided resource discovery
(Capability Delivery Plan)

This use case describes how the XSEDE system should support researchers and educators in identifying the appropriate resources for their project allocation proposals. The delivery plan proposes to increase the visibility of information from the current Resource Description Repository (RDR) for both allocated and non-allocated resources and to add supplementary links to data from other sources, such as the community software repository (CSR) and the XSEDE User Portal system monitor.

4.3 of 5 stars
(20 votes)
5 star (10)
50%
50%
4 star (6)
30%
30%
3 star (3)
15%
15%
2 star (1)
5%
5%
1 star (0)
0%
0%
no vote (0)
0%
0%
RC-02: Manage usage within an allocation
(Capability Delivery Plan)

This use case describes how researchers, campus champions, and educators need help managing the use of their XSEDE allocations by individual members of their projects. The proposed delivery plan involves enhancing the XSEDE User Portal's project management interfaces and the XSEDE central database to allow project managers to define limits on individual users, resulting in automatic suspend requests to the relevant service providers when the users exceed their limits. Total effort proposed is 8 person weeks.

3.9 of 5 stars
(20 votes)
5 star (4)
20%
20%
4 star (10)
50%
50%
3 star (5)
25%
25%
2 star (1)
5%
5%
1 star (0)
0%
0%
no vote (0)
0%
0%
IDM-14: SSH access using XSEDE identities for education
(Capability Delivery Plan)

This use case originated from Jetstream users with education allocations. They'd like their students to be able to login to VMs they administer using their XSEDE identities rather than the instructor having to issue new IDs/passwords. (Note that a solution to this problem would not be limited to XSEDE VMs, but could be used on any system administered by non-XSEDE personnel, including science gateways that offer command-line services or campus login systems.) XSEDE's public authentication service provides an implementation path, but a specific solution that complies with XSEDE's security requirements isn't immediately obvious. The immediate plan is to conduct a technology readiness assessment to identify a specific technical solution satisfying all relevant requirements. Total effort proposed is 4-5 person weeks.

3.7 of 5 stars
(19 votes)
5 star (2)
10%
10%
4 star (10)
50%
50%
3 star (6)
30%
30%
2 star (1)
5%
5%
1 star (0)
0%
0%
no vote (1)
5%
5%
GRP-03: Manually view or manage the configuration or membership of a group
(Capability Delivery Plan)

This use case was identified in XSEDE's Spring 2017 needs analysis for group management functions and describes a need expressed by many areas of the XSEDE enterprise. The need is for anyone--researchers, educators, XSEDE staff, service providers, science gateway developers, campus administrators--to be able to manually manage (in a Web browser) groups they've defined in the XSEDE system. The current system allows XSEDE staff and allocation project managers to do this for allocation groups, but no other types of groups are currently supported. At this time, the delivery plan is to search for, identify, and evaluate available technologies that XSEDE could use for this and related group features. The effort proposed for this assessment (which covers all of GRP-02 through GRP-16) is 4.5 to 5.5 person months.

3.6 of 5 stars
(20 votes)
5 star (4)
20%
20%
4 star (6)
30%
30%
3 star (8)
40%
40%
2 star (2)
10%
10%
1 star (0)
0%
0%
no vote (0)
0%
0%
GRP-02: Manually create a group
(Capability Delivery Plan)

This use case was identified in XSEDE's Spring 2017 needs analysis for group management functions and describes a need expressed by many areas of the XSEDE enterprise. The need is for anyone--researchers, educators, staff members, service providers, campus administrators, science gateway developers--to be able to define a group in XSEDE that can be used later for things like access control, data sharing, email distribution, or team/task assignments. At this time, the delivery plan is to search for, identify, and evaluate available technologies that XSEDE could use for this and related group features. The effort proposed for this assessment (which covers all of GRP-02 through GRP-16) is 4.5 to 5.5 person months.

3.6 of 5 stars
(20 votes)
5 star (4)
20%
20%
4 star (6)
30%
30%
3 star (8)
40%
40%
2 star (2)
10%
10%
1 star (0)
0%
0%
no vote (0)
0%
0%
GRP-15: Use a group for task assignments within a staff tool
(Capability Delivery Plan)

This use case was identified in XSEDE's Spring 2017 needs analysis for group management functions. This use case is specific to XSEDE staff, particularly managers. XSEDE managers currently spend significant time managing and manually synchronizing groups in a surprising number of tools used by XSEDE personnel. A shared group system used by multiple staff tools would save time and effort throughout the project and reduce errors in staff communication and task tracking activities. At this time, the delivery plan is to search for, identify, and evaluate available technologies that XSEDE could use for this and related group features. The effort proposed for this assessment (which covers all of GRP-02 through GRP-16) is 4.5 to 5.5 person months.

3.5 of 5 stars
(19 votes)
5 star (4)
20%
20%
4 star (6)
30%
30%
3 star (5)
25%
25%
2 star (3)
15%
15%
1 star (1)
5%
5%
no vote (1)
5%
5%
GRP-05: Invite members to a group
(Capability Delivery Plan)

This use case was identified in XSEDE's Spring 2017 needs analysis for group management functions and describes a need expressed by many areas of the XSEDE enterprise. The need is the ability to invite someone to join a group. (The group would likely be one used for managing staff teams/tools/assignments, for email distribution, for coordinating research activities, or for a science gateway or campus service.) The invitee may not yet be registered with XSEDE--they could be invited via email--and the invitee will not belong to the group until he/she accepts the invitation, including, if necessary, registering with XSEDE. At this time, the delivery plan is to search for, identify, and evaluate available technologies that XSEDE could use for this and related group features. The effort proposed for this assessment (which covers all of GRP-02 through GRP-16) is 4.5 to 5.5 person months.

3.4 of 5 stars
(20 votes)
5 star (3)
15%
15%
4 star (4)
20%
20%
3 star (11)
55%
55%
2 star (2)
10%
10%
1 star (0)
0%
0%
no vote (0)
0%
0%
GRP-16: Use a group for email distribution
(Capability Delivery Plan)

This use case was identified in XSEDE's Spring 2017 needs analysis for group management functions. This use case is especially relevant to XSEDE staff who use email to coordinate their work, but it could also be useful to any group of people who use XSEDE. Email is heavily used among the XSEDE staff and throughout the XSEDE user community, but there is currently no way to automatically populate email distribution lists based on staff plans or directories, team membership, or the groups defined in tools and services. A shared group service that could be used for email distribution would reduce errors in staff communication and the time/effort spent by managers and team members to maintain lists. At this time, the delivery plan is to search for, identify, and evaluate available technologies that XSEDE could use for this and related group features. The effort proposed for this assessment (which covers all of GRP-02 through GRP-16) is 4.5 to 5.5 person months.

3.4 of 5 stars
(20 votes)
5 star (1)
5%
5%
4 star (9)
45%
45%
3 star (7)
35%
35%
2 star (2)
10%
10%
1 star (1)
5%
5%
no vote (0)
0%
0%
GRP-10: Automate a group's configuration
(Capability Delivery Plan)

This use case was identified in XSEDE's Spring 2017 needs analysis for group management functions. This use case is specific to science gateway developers, external service providers, and staff tool providers. The need is to be able to manage a group's configuration under program control (via an API) rather than manually through a Web browser. At this time, the delivery plan is to search for, identify, and evaluate available technologies that XSEDE could use for this and related group features. The effort proposed for this assessment (which covers all of GRP-02 through GRP-16) is 4.5 to 5.5 person months.

3.4 of 5 stars
(20 votes)
5 star (4)
20%
20%
4 star (3)
15%
15%
3 star (9)
45%
45%
2 star (4)
20%
20%
1 star (0)
0%
0%
no vote (0)
0%
0%
GRP-13: Use a group to control access within an XSEDE service
(Capability Delivery Plan)

This use case was identified in XSEDE's Spring 2017 needs analysis for group management functions. This use case is specific to people who provide XSEDE system components (examples: the XSEDE user portal, XSEDE staff tools, training websites). The need is to be able to use XSEDE-defined groups within XSEDE's user interfaces, staff tools, and other community services. It does not refer to allocated XSEDE services, which already have access to XSEDE-defined groups. At this time, the delivery plan is to search for, identify, and evaluate available technologies that XSEDE could use for this and related group features. The effort proposed for this assessment (which covers all of GRP-02 through GRP-16) is 4.5 to 5.5 person months.

3.4 of 5 stars
(19 votes)
5 star (2)
10%
10%
4 star (6)
30%
30%
3 star (9)
45%
45%
2 star (2)
10%
10%
1 star (0)
0%
0%
no vote (1)
5%
5%
IDM-13: Authenticate to XSEDE OpenStack APIs
(Capability Delivery Plan)

This use case originates from the IU/TACC Jetstream service provider team and their users, who would like to be able to use XSEDE identities to authenticate to Jetstream's OpenStack APIs. Jetstream's Web interface (Atmosphere) currently uses XSEDE's public authentication service, but OpenStack API access currently requires issuing "local" IDs/passwords. (Note that a solution to this problem would not be limited to Jetstream, but would be available to any service provider offering OpenStack cloud services.) The delivery plan calls for the Jetstream team to test OpenStack's OIDC authentication module with XSEDE's OIDC-based public authentication service. XSEDE personnel may be needed to assist with this testing and PSC/Bridges personnel may also contribute. Total effort proposed (by all contributing parties) is 4 person weeks.

3.4 of 5 stars
(19 votes)
5 star (2)
10%
10%
4 star (4)
20%
20%
3 star (12)
60%
60%
2 star (1)
5%
5%
1 star (0)
0%
0%
no vote (1)
5%
5%
GRP-06: Request membership in a group
(Capability Delivery Plan)

This use case was identified in XSEDE's Spring 2017 needs analysis for group management functions and describes a need expressed by many areas of the XSEDE enterprise. The need is for registered XSEDE users to be able to request membership in a specific XSEDE group. (The group would likely be one used for managing staff teams/tools/assignments, for email distribution, for coordinating research activities, or for a science gateway or campus service.) The requester will not become a member of the group until/unless the group's administrator approves the request. At this time, the delivery plan is to search for, identify, and evaluate available technologies that XSEDE could use for this and related group features. The effort proposed for this assessment (which covers all of GRP-02 through GRP-16) is 4.5 to 5.5 person months.

3.3 of 5 stars
(20 votes)
5 star (2)
10%
10%
4 star (4)
20%
20%
3 star (12)
60%
60%
2 star (2)
10%
10%
1 star (0)
0%
0%
no vote (0)
0%
0%
GRP-17: Drive project membership with an email message
(Capability Delivery Plan)

This feature has been requested by educators using XSEDE education allocations to support classes and training activities. The request is to allow educators to add (or invite) members to an allocation project team by sending XSEDE an email message containing a list of email addresses, rather than manually entering each proposed member in the user portal's Web interface. The delivery plan at this time is simply to request a security risk assessment to​ identify "safe" implementation​ options from a security risk perspective. Proposed effort for the assessment is one person week.

3.3 of 5 stars
(19 votes)
5 star (3)
15%
15%
4 star (4)
20%
20%
3 star (7)
35%
35%
2 star (5)
25%
25%
1 star (0)
0%
0%
no vote (1)
5%
5%
GRP-09: Synchronize an external group
(Capability Delivery Plan)

This use case was identified in XSEDE's Spring 2017 needs analysis for group management functions and describes a need expressed by many areas of the XSEDE enterprise. What's needed is the ability to reference a group defined in another system from within XSEDE. For example, a research collaboration that already has several groups defined in another system (e.g., Open Science Grid or Internet2) would like to be able to use those group definitions in XSEDE for access control, email distribution, allocation proposals. At this time, the delivery plan is to search for, identify, and evaluate available technologies that XSEDE could use for this and related group features. The effort proposed for this assessment (which covers all of GRP-02 through GRP-16) is 4.5 to 5.5 person months.

3.1 of 5 stars
(20 votes)
5 star (2)
10%
10%
4 star (3)
15%
15%
3 star (10)
50%
50%
2 star (4)
20%
20%
1 star (1)
5%
5%
no vote (0)
0%
0%
GRP-14: Use a group to control access within an external resource
(Capability Delivery Plan)

This use case was identified in XSEDE's Spring 2017 needs analysis for group management functions. This use case is specific to science gateway developers and campus system administrators who want to use XSEDE groups in their services. The need is for developers not affiliated with XSEDE (e.g., science gateway, campus, or XSEDE L3 service developers) to be able to use XSEDE-defined groups in their applications and services, with appropriate authorizaiton. At this time, the delivery plan is to search for, identify, and evaluate available technologies that XSEDE could use for this and related group features. The effort proposed for this assessment (which covers all of GRP-02 through GRP-16) is 4.5 to 5.5 person months.

3.1 of 5 stars
(19 votes)
5 star (2)
10%
10%
4 star (3)
15%
15%
3 star (8)
40%
40%
2 star (6)
30%
30%
1 star (0)
0%
0%
no vote (1)
5%
5%