Page Comparison

...

1. The goals of the pilot are to:

   1. Provide a centralized location for OnDemand activity in ACCESS to serve as a demonstration of what is possible and provide a starting point to expand over time.

   2. Link three local OnDemand deployments back to common ACCESS services to smooth the user experience.

2. User story

   1. User authenticates to ACCESS MATCH Portal (AMP) as appropriate (e.g., CILogon).

   2. One of the top-level tabs in the AMP is labeled “ACCESS OnDemand” (or “ACCESS MATCH Tools” if the Pegasus team would also like to leverage this). Clicking on this tab brings up links to the following deployments:

      1. Bridges OnDemand

      2. Expanse OnDemand

      3. Anvil OnDemand

   3. Say the user has an allocation on Bridges and clicks the “Bridges OnDemand” link. The user is taken to Bridges OnDemand and must authenticate as appropriate.

   4. The local OnDemand deployments have links back to the AMP and display statistics from MMS.

3. See UI mock-up and system diagram below.

4. Other ideas to consider:

   TBD…

   Notes:

   1. This is a concept target to shoot for, not a commitment. It clearly shows the first iteration of the vision of having OnDemand at various resources leverage common ACCESS services.

   2. The underlying technology for single sign-on (OAUTH) is not in this proposal. I intentionally said, “forget that, let’s just assume the user can remember their usernames and passwords.” Any smoothing of the authentication experience through either common credentials (e.g., using the same CILogon credentials for both AMP and OnDemand) or federated authentication through OAUTH would be welcome but I consider to be independent of this pilot.

   3. The top-level AMP Tools page could also point (someday) to a central OnDemand instance that provides connections to ACCESS resources via SSH. (Terminal and hopefully SSHFS for files.). Again, let’s assume two sets of credentials at the start.

5. First steps:

   1. Complete a “listenting tour”. Talk individually with the Expanse, Bridges and Anvil teams about their OnDemand successes and struggles. See if there are common features that they’d like that we could add that would help their users.

   2. I think of “ACCESS OnDemand” to mean any OnDemand instance that is connected to (and supported by central ACCESS services). For branding, it could be “Bridges OnDemand powered by ACCESS” or something like that.

UI mock-up:

...

System diagram:

...