The resource provider supplies information describing their type of resource, including: public facing information like descriptive text, user guide URL, and resource status dates; and non-public information like the names and email addresses of RP staff contacts. ACCESS allocated resource providers will generally enter this information into the ACCESS CyberInfrastructure Description Repository (CiDeR) database themselves, with an estimated effort of 2-3/hours to gain CiDeR access and to enter the information, and ~30 minutes semi-annually to maintain the information. Most other resource providers will provide needed information to ACCESS staff, with an estimated effort of <1 hour, and ACCESS staff will maintain the information into CiDeR for them.
","verification_summary":"ACCESS will verify that CiDeR information is complete automatically on a daily basis, and communicate discrepancies to to the RP.
","verification_method":"Automated","default_badge_access_url":"https://allocations.access-ci.org/resources","default_badge_access_url_label":"Visit Resource Catalog","prerequisites":[]},"sequence_no":0,"required":true,"roadmap":101},{"id":641,"badge":{"badge_id":3,"prerequisite_list":"ACCESS Resource Description","tasks":[{"badge_id":3,"sequence_no":1,"task":{"task_id":32,"name":"Setup Ticket Handling","technical_summary":"ACCESS resource and online service operators will be assigned tickets for issues or questions about their resources and online services. In response they will monitor the ticket system for tickets assigned to them, triage them as necessary, reassign them to other staff or organizations if necessary, resolve issues, and close tickets once the request is addressed.
","implementor_roles":"Researcher support and ticket handling","task_experts":"Winona Snapp-Childs","detailed_instructions_url":"https://readthedocs.access-ci.org/projects/integration-roadmaps/en/latest/tasks/Ticket_Handling_v2.html"},"required":true}],"name":"ACCESS Ticketing Support","graphic":"https://operations-api.access-ci.org/wh2/integration_badges/v1/files/608a9fb8-5abd-4295-ad90-53de2fa79f84","researcher_summary":"Support requests can be submitted using the ACCESS ticketing system","resource_provider_summary":"Initial tasks: \r\n- Confirm name of ticket queue (system name is current convention in ACCESS)\r\n- Identify essential team members and email addresses for ticket watcher group\r\nOngoing tasks:\r\n- Review tickets upon entry\r\n- Assign tickets to relevant team member\r\n- Update tickets when appropriate (respond to researchers, close tickets)","verification_summary":"ACCESS confirms that resource support queues have been established, the resource provider staff have obtained agent access to the ticketing system, and that ACCESS instructions about ticket routing include the resource.","verification_method":"Manual","default_badge_access_url":"https://support.access-ci.org/help-ticket","default_badge_access_url_label":"Open Help Ticket","prerequisites":[]},"sequence_no":1,"required":false,"roadmap":101},{"id":642,"badge":{"badge_id":2,"prerequisite_list":"ACCESS Resource Description, ACCESS CyberSecurity Coordination","tasks":[{"badge_id":2,"sequence_no":0,"task":{"task_id":3,"name":"ACCESS Allocation Policies","technical_summary":"Resource Providers will need to have proper representation for Allocation questions, reviewing RP requests and provide guidance to both ACCESS Allocations staff and review panels.","implementor_roles":"Allocations process","task_experts":"Ken Hackworth","detailed_instructions_url":"https://readthedocs.access-ci.org/projects/integration-roadmaps/en/latest/tasks/ACCESS_Allocation_Policies_v1.html"},"required":true},{"badge_id":2,"sequence_no":1,"task":{"task_id":8,"name":"AMIE and Usage Reporting","technical_summary":"Resource Providers will implement a client for the Account Management Information Exchange (AMIE) protocol, to receive allocations information from ACCESS Allocations and report necessary information back to ACCESS.","implementor_roles":"AMIE technical","task_experts":"Nathan Tolber, Rob Light","detailed_instructions_url":"https://readthedocs.access-ci.org/projects/integration-roadmaps/en/latest/tasks/AMIE_and_Usage_Reporting_v1.html"},"required":true},{"badge_id":2,"sequence_no":2,"task":{"task_id":139,"name":"ACCESS Usage Command Line Tool","technical_summary":"The ACCESS Usage (accessusage) tool enables researchers to display project and user usage information for their ACCESS allocations from the command line. Resource providers may install accessusage on their ACCESS allocated compute resources for researchers to use.
","implementor_roles":"System administrator","task_experts":"Eric Blau","detailed_instructions_url":"https://github.com/access-ci-org/accessusage/blob/master/README.md"},"required":false}],"name":"ACCESS Allocations","graphic":"https://operations-api.access-ci.org/wh2/integration_badges/v1/files/fd9eb691-26d2-4516-a0b6-eae77c7bdd50","researcher_summary":"Researches can submit allocation requests to ACCESS and be awarded allocations on this resource.
","resource_provider_summary":"The resource provider must first fulfill the requirements for the ACCESS Resource Description badge. Additionally, must align with ACCESS Allocation Policies and must integrate their local allocations system with ACCESS AMIE API infrastructure, which is a development effort that can take a significant amount of time (potentially multiple weeks of a developer’s time).
","verification_summary":"The RP receives and processes AMIE packets which results in local ACCESS allocated user accounts, allocation usage tracking, and usage reporting to ACCESS.
","verification_method":"Manual","default_badge_access_url":"https://allocations.access-ci.org","default_badge_access_url_label":"Allocations Information","prerequisites":[]},"sequence_no":2,"required":true,"roadmap":101},{"id":643,"badge":{"badge_id":14,"prerequisite_list":"ACCESS Allocations","tasks":[{"badge_id":14,"sequence_no":2,"task":{"task_id":19,"name":"Utilization Reporting for non-ACCESS allocated resources","technical_summary":"ACCESS Metrics provides ACCESS XDMoD and various data reporting and analysis services for ACCESS-allocated resources and for other NSF-funded projects such as the Campus Cyberinfrastructure program.\r\n\r\nThis task involves setting up the data transfer of utilization data for a compute resource that is not allocated by ACCESS. This includes compute resources that are funded by NSF’s CC* program that are expected to work cooperatively with ACCESS award activities and services.\r\n\r\nThe data reporting will be via a Federated XDMoD portal that is managed by ACCESS Metrics. This federated XDMoD portal is based on the Open XDMoD software and is configured to be able to report across multiple NSF funded projects and resources. The data will be made available to NSF staff.","implementor_roles":"System administrator","task_experts":"Joseph White","detailed_instructions_url":"https://readthedocs.access-ci.org/projects/integration-roadmaps/en/latest/tasks/NonACCESSUtilizationReporting_v1.html"},"required":false},{"badge_id":14,"sequence_no":3,"task":{"task_id":5,"name":"ACCESS OnDemand Portal Integration","technical_summary":"This task provides Resource Providers instructions on how to deploy an ACCESS integrated OnDemand portal. This task will generally be performed by RP system administrators.
","implementor_roles":"System administrator","task_experts":"Alan Chalker","detailed_instructions_url":"https://readthedocs.access-ci.org/projects/integration-roadmaps/en/latest/tasks/ACCESS_OnDemand_Portal_Integration_v1.html"},"required":false},{"badge_id":14,"sequence_no":0,"task":{"task_id":28,"name":"Resource Metrics Data Availability Assessment","technical_summary":"ACCESS Metrics provides ACCESS XDMoD and various data reporting and analysis services. XDMoD provides reporting on a wide range of CI metrics. This includes CI efficiency reporting that is available to end users, PIs and RP staff. The main data source for this is low-level performance data collected from each CI resource. Resource Providers do not need to install or maintain XDMoD. ACCESS Metrics provides the service that processes the low-level performance data, correlates it with other CI metrics, analyzes it and stores in ACCESS XDMoD. For traditional HPC resources, performance data collection is typically achieved by running monitoring software on the compute nodes. Examples of such software include tacc_stats, Performance Co-Pilot Prometheus or Ganglia to name a few. Performance data can also be obtained from some resource managers (such as slurm) with the appropriate configuration. The choice of performance data collection system depends on the resource architecture and operational constraints. ACCESS Metrics can provide guidance and recommendations based on our experience.
","implementor_roles":"Metrics and performance data","task_experts":"Joseph White, Conner Saeli","detailed_instructions_url":"https://readthedocs.access-ci.org/projects/integration-roadmaps/en/latest/tasks/Resource_Metrics_Data_Availability_Assessment_v1.html"},"required":true}],"name":"ACCESS Usage Metrics","graphic":"https://operations-api.access-ci.org/wh2/integration_badges/v1/files/477a98e6-34ea-41f9-8274-22aaa7ab506f","researcher_summary":"Researchers can view metrics of usage of this resource through ACCESS XDMoD","resource_provider_summary":"Usage information that Resource Providers report via the AMIE and Usage APIs is automatically ingested into ACCESS XDMoD without requiring additional effort from Resource Providers.","verification_summary":"ACCESS staff confirm that usage metrics reported through AMIE are viewable in XDMoD.","verification_method":"Manual","default_badge_access_url":"https://xdmod.access-ci.org/","default_badge_access_url_label":"Visit XDMod","prerequisites":[]},"sequence_no":3,"required":false,"roadmap":101},{"id":644,"badge":{"badge_id":6,"prerequisite_list":"ACCESS Resource Description","tasks":[{"badge_id":6,"sequence_no":1,"task":{"task_id":21,"name":"Operational Status Communications","technical_summary":"ACCESS resource providers RPs, ACCESS projects (tracks), and online service operators communicate planned and unplanned outages, and configuration changes, using the ACCESS Operations Infrastructure News system.","implementor_roles":"Public documentation, System administrator, Research support and ticket handling","task_experts":"JP Navarro","detailed_instructions_url":"https://readthedocs.access-ci.org/projects/integration-roadmaps/en/latest/tasks/Operational_Status_Communications_v1.html"},"required":true}],"name":"ACCESS Resource Status","graphic":"https://operations-api.access-ci.org/wh2/integration_badges/v1/files/97c05044-ce3f-46d8-a461-3c3aa2b784e4","researcher_summary":"Publishes resources status news through ACCESS channels","resource_provider_summary":"The resource provider publishes resource announcement, full and partial outages, degraded status, reconfigurations, and retirements using the ACCESS Operations System Status News service. Initial effort of 1/hour to obtain access, and ~10/minutes to post each resource status news items","verification_summary":"ACCESS confirms that RP staff have requested and been granted access to the ACCESS System Status news publishing service.","verification_method":"Manual","default_badge_access_url":"https://operations.access-ci.org/infrastructure_news_view","default_badge_access_url_label":"System Status News","prerequisites":[]},"sequence_no":4,"required":false,"roadmap":101}],"name":"ACCESS Enabled Data Collection","graphic":"https://operations-api.access-ci.org/wh2/integration_badges/v1/files/89eb2193-1da0-40ac-b130-6314ab41c944","executive_summary":"(executive summary for the resource provider)
","infrastructure_types":"Storage","integration_coordinators":"Lee Liming","status":"Draft"}},"status_code":200}