Page Comparison

Attendees:

• RAMPS:Stephen Deems (v), Dave Hart

• MATCH: Shelley Knuth (v), Alana Romanella

• CONECT: Tim Boerner (v), Leslie Froeschl

• MMS: Tom Furlani (v), Joe White

• OpenCI: John Towns (v), Shawn Strande, Lavanya Podila, Lisa Kaczmarczyk

• NSF: Tom Gulbransen, Sharon Geva

• Guest Speaker: Dave Hudak

...

1. OnDemand Working Group Updates @Dave Hudak (15 mins)

   1. UB and OSC are currently piloting new XDMoD code that will facilitate the the integration of data between ACCESS XDMoD and ACCESS OnDemand instances (much like already exists between OpenXDMoD and Open OnDemand instances. This primarily involves data from each ACCESS XDMoD instance regularly being sent to a database hosted by UB

   2. Jetstream2 team is working on including OnDemand in their Virtual Cluster ansible scripts. This will allow clients the option to have OnDemand automatically installed / configured when they create a virtual cluster on Jetstream2

   3. OnDemand now has an official, documented versioning / support policy (per the request from several RPs in the working group)

   4. The RP roadmap task now includes information on how to provide group based access to the ACCESS menu (per the request from several RPs in the working group)

   5. There has been ongoing discussions around provided RPs guidance to reference privacy / acceptable use / code of conduct policies in the footer of their OnDemand installations.

   6. Year 2 specific ACCESS OnDemand plans:

      1. OnDemand deployed on more RPs

      2. Majority of the deployments have the ACCESS menu available

      3. Deployments are tied into other ACCESS services (e.g. XDMoD)

         1. ACCESS Portal common look-and-feel

         2. Globus file service integration

         3. Registration of OOD deployments / services with operations edge service database

         4. Publishing OOD integrated applications into the ACCESS wide software catalog

   7. Questions for Ondemand working group

      1. what are you thinking about the structure and the organization of the working group moving forward?

         We plan to have continuing conversations, reduced the meeting frequency. However, we do not feel at we are at a point, where we can move this to meeting on an as-needed basis.

      2. Given the personas ideas to help the community, do you think the open on demand users are personas themselves or maybe a part of gateways?

         Maybe along the lines of gateways, on demand is a useful platform for a subset of the folks, so as a community.

      3. Is there any mechanism that currently exists for differentiating RPs on ACCESS allocations versus locally, for instance, if an RP is allocated locally on Delta versus ACCESS, can you treat them as 2 separate allocations or one.

         We currently do not have a mechanism for differentiation. This suggestion will be taken back to the team for discussions.

      4. on demand instance in the public cloud, is this something that you are thinking?

         Yes they have deployable instances already available on cloud.

          
         

2. Approval of summaries from prior EC meetings John Towns (5 mins)

   1. 20 June 2023 EC Summary (approved)
      

3. ACCESS Colocated Event at PEARC John Towns (10 mins)

   1. https://access-ci.atlassian.net/wiki/spaces/ACP/pages/271908868/2023-07-27+ACCESS+Colocated+Event+PEARC+23

   2. Any additional agenda topics

   3. Discussion regarding agenda items

   4. “How we can engage better with the RPs” Tom Maiden not going to be at the event. Tom planning a separate forum with users and technical operators.

      1. EC requests Tom to facilitate a discussion with the technical operators, present his findings to the EC.

   5. ACO to finalize the agenda by the end of the week, 14th July 2023.

       
      

4. EAB Recommendations Shawn Strande (2 mins)

   1. Need folks to update the EAB recommendation document. We will share this as part of our update with the EAB during the PEARC EAB meeting: https://docs.google.com/spreadsheets/d/1CtAMssCnj8RNfWk7M7K4RvZG-rBdNJsuFseFVQWuP5s/edit?pli=1#gid=0

   2. How does item 13 relate to the personas? Support is working on a recommender system, which is basically like a decisions tree which points them in the right direction, which might be useful.

   3. We do want several recommender systems.

   4. Discussion regarding creating a working group around personas, a representative from Support to be the chair of the group (still undecided)
      

5. Next ACCESS Program Wide Meeting John Towns (5 mins)

   1. Next quarterly meeting , virtual, dates?will be virtual

   2. Conflicts/unavailable,

      1. September 1st week Support unavailable, 2nd week NSF unavailable, last week several community events

   3. Tentative dates - September 18th and 19th

   4. Next in-person meeting, dates and host? Would be worth considering holding the EAB in-person meeting as part of this to minimize the cost of ACCESS staff travel (EAB member travel will be covered by the ACO).
      

6. ACCESS engagement tracker Shawn Strande (2 mins)

   1. To better support reporting and outcomes. Please update with outreach, events, et al activities. https://docs.google.com/spreadsheets/d/1_EXKUOXmY-TVkDWaHR1-SuiKt404uGEnGSr6uQCkwzw/edit#gid=0

      1. Stephen Deems start using this instead of our internal tracking sheet.
         

7. Program Milestone CheckJohn Towns (10 mins)

   1. Action item for the awardees to update their program milestones

   2. Reminder:Do not edit "Dashboard" tab, please edit "ACCESS program milestones" tab as needed
      

8. Informational Items (10 mins)

   1. RAMPS Stephen Deems

      1. ACCESS Reviewer Manual v1.0 (Draft)

         1. Will circulate to reviewers and RPs for feedback; will then refactor feedback into revisions.

      2. AARC June After Meeting Report

         1. Is available for any interested personnel. A link is NOT provided here since these agendas are open to the public and portions of the content are confidential.

            1. Please contact Stephen or an Allocations representative if you’re interested in the data.

         2. In future quarters we will look to provide a summary report that can be open to the public

            1. and a more streamlined report for internal ACCESS (and RP) use/reference

      3. All Allocations-related risks have been updated in the Risk Register

         1. Contingencies and Triggers still need to be fully populated.

   2. MATCH Shelley Knuth

      1. We would like to get an up to date list of the software that each of the RPs are running. Can Operations assist with getting this list? Otherwise we would need to do a workaround.

   3. CONECT Tim Boerner

   4. MMS Tom Furlani

      1. XMDoD 10.5 currently in final ‘staging’ testing. Due to update production on Tuesday July 18

   5. OpenCI John Towns

      1. Working with EC on finalizing Program-Wide Goals

         1. will lead into development of associated metrics

      2. ACO actively working on updated PEP; some elements of metrics will require discussions with service teams to explore shared metrics

      3. Continued planing for PEARC23 activities

   6. General Tom Gulbransen

      1. John has neat story of UIUC undergrads publishing based on analytics from an Explore allocation. To evidence democratization, shall we invite Explore and Discover awardees to broadcast their successes via ACCESS somewhere?

...