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":true,"roadmap":68},{"id":388,"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":68},{"id":403,"badge":{"badge_id":5,"prerequisite_list":"ACCESS Resource Description","tasks":[{"badge_id":5,"sequence_no":0,"task":{"task_id":11,"name":"Cybersecurity Requirements for RPs","technical_summary":"The cybersecurity requirements for RPs ensures that the ACCESS community’s cybersecurity needs are satisfied when a new service is added to the system. For instance: membership and participation in incident response, vulnerability patching and mitigation, retention of system logs, etc. Requirements are driven by ACCESS community policies.\r\n\r\nThe purpose of this document is to define the expectations and responsibilities of the ACCESS Resource Providers with respect to security and incident response. These requirements ensure the ability to (i) protect ACCESS assets, (ii) respond to threats to those assets, and (iii) maintain the lines of communication necessary for the former two goals.","implementor_roles":"Cybersecurity and incident response","task_experts":"Derek Simmel, Shane Filus","detailed_instructions_url":"https://readthedocs.access-ci.org/projects/integration-roadmaps/en/latest/tasks/Cybersecurity_Requirements_for_RPs_v1.html"},"required":true},{"badge_id":5,"sequence_no":1,"task":{"task_id":14,"name":"Incident Response and Coordination","technical_summary":"Resource Providers and ACCESS Tracks must follow incident response and coordination procedures as defined in ACCESS’s Incident Response Policy. Representatives from each RP and Track must be identified to participate in the ACCESS Incident Response Trust Group (AIRTG). This representative’s contact information must be provided and will be used in the case of an incident as defined in the Incident Response Policy.","implementor_roles":"Cybersecurity and incident response","task_experts":"Derek Simmel, Shane Filus","detailed_instructions_url":"https://readthedocs.access-ci.org/projects/integration-roadmaps/en/latest/tasks/Incident_Response_and_Coordination_v1.html"},"required":true},{"badge_id":5,"sequence_no":2,"task":{"task_id":17,"name":"Integrate Local Services with ACCESS IAM","technical_summary":"This task provides guidance for Resource Providers that want to integrate their services with ACCESS identity management.","implementor_roles":"Cybersecurity and incident response, System administrator","task_experts":"Derek Simmel, Shane Filus","detailed_instructions_url":"https://readthedocs.access-ci.org/projects/integration-roadmaps/en/latest/tasks/Local_Services_ACCESS_IAM_Integration_v1.html"},"required":false}],"name":"ACCESS CyberSecurity Coordination","graphic":"https://operations-api.access-ci.org/wh2/integration_badges/v1/files/1289d861-3f0b-4819-ac2f-1b6f65a35ead","researcher_summary":"Coordinates CyberSecurity incidents and best practices with ACCESS","resource_provider_summary":"The Resource Provider must provide complete contact information and establish secure communication means to enable rapid cybersecurity incident response with ACCESS and other RPs. RPs are also expected to participate regularly in ACCESS Incident Response Trust Group (AIRTG) meetings and communications. RPs need to acknowledge and adhere to ACCESS Cybersecurity Policies and Procedures.","verification_summary":"The ACCESS CyberSecurity coordinator verifies that CyberSecurity communications channels have been established with the RP, that the RP is participating in AIRTG, and that the RP has acknowledged and adheres to ACCESS CyberSecurity polices and Procedures","verification_method":"Manual","default_badge_access_url":"https://operations.access-ci.org/pub/cybersecurity/awareness","default_badge_access_url_label":"Cybersecurity Awareness","prerequisites":[]},"sequence_no":3,"required":true,"roadmap":68},{"id":438,"badge":{"badge_id":12,"prerequisite_list":"","tasks":[{"badge_id":12,"sequence_no":1,"task":{"task_id":34,"name":"ACCESS Training Publishing Instructions","technical_summary":"Resource providers post ACCESS Events & Training related to their resource.
","implementor_roles":"Training, Documentation","task_experts":"Lissie Fein","detailed_instructions_url":"https://access-ci.atlassian.net/wiki/x/QQBQSw"},"required":true}],"name":"ACCESS Advertised Training","graphic":"https://operations-api.access-ci.org/wh2/integration_badges/v1/files/a68fcb79-1df0-4f48-840c-51be4b862d9c","researcher_summary":"Resource related workshops, tutorials and training are advertised through ACCESS.","resource_provider_summary":"Resource provider creates and/or hosts (live and/or online) training (workshops, tutorials and technical lectures) related to the use of your resources and promotes them through events on the ACCESS website.","verification_summary":"Has resource provider prepared training been posted to the ACCESS website","verification_method":"Manual","default_badge_access_url":"https://support.access-ci.org/knowledge-base/resources","default_badge_access_url_label":"Learning Resources","prerequisites":[]},"sequence_no":11,"required":false,"roadmap":68},{"id":443,"badge":{"badge_id":13,"prerequisite_list":"ACCESS Resource Description","tasks":[{"badge_id":13,"sequence_no":0,"task":{"task_id":68,"name":"Affinity Group Request Form","technical_summary":"Form for requesting an Affinity Group
","implementor_roles":"Documentation","task_experts":"Lissie Fein","detailed_instructions_url":"https://support.access-ci.org/form/affinity-group-request"},"required":true},{"badge_id":13,"sequence_no":1,"task":{"task_id":67,"name":"Affinity Group Coordinator Notes","technical_summary":"Information for coordinators about establishing and maintaining affinity groups.
","implementor_roles":"Documentation","task_experts":"Lissie Fein","detailed_instructions_url":"https://access-ci.atlassian.net/wiki/x/GQBQSw"},"required":true}],"name":"ACCESS Affinity Group","graphic":"https://operations-api.access-ci.org/wh2/integration_badges/v1/files/43ba93a0-0e75-4cde-8495-f67b33cca6af","researcher_summary":"An Affinity Group is available for community engagement about this resource.","resource_provider_summary":"Provide a hub for information, news, links and discussion related to your resource (system(s)) or focus topic, for example information regarding documentation and training. Build, maintain and support your user community.","verification_summary":"ACCESS confirms that an Affinity Group exists for this resource.","verification_method":"Manual","default_badge_access_url":"https://support.access-ci.org/affinity-groups","default_badge_access_url_label":"View Affinity Groups","prerequisites":[]},"sequence_no":12,"required":false,"roadmap":68},{"id":453,"badge":{"badge_id":15,"prerequisite_list":"ACCESS Allocations, ACCESS Usage Metrics","tasks":[{"badge_id":15,"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},{"badge_id":15,"sequence_no":1,"task":{"task_id":22,"name":"Performance Data Reporting","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 the efficiency reporting is low-level performance data collected from each CI resource. CI resource providers must periodically transfer a copy of the low-level performance data to ACCESS Metrics so that it can be processed and displayed in XDMoD. This task involves setting up the data transfer of performance data.
","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/Performance_Data_Reporting_v1.html"},"required":true}],"name":"ACCESS Performance Metrics","graphic":"https://operations-api.access-ci.org/wh2/integration_badges/v1/files/223acfea-16e0-4e01-823d-de7bc49aba00","researcher_summary":"Researchers can view metrics of system-level and job-level performance of this resource through ACCESS XDMoD","resource_provider_summary":"Resource Providers work with the ACCESS Metrics team to set up daily transfers of resource manager (e.g., Slurm) logs. If the Resource Provider runs performance monitoring software (e.g., Performance Co-Pilot, Prometheus, HPCPerfStats, etc.), they work with the ACCESS Metrics team to set up daily transfers of these data as well.","verification_summary":"ACCESS confirms that performance metrics for the resource are available in XDMoD","verification_method":"Manual","default_badge_access_url":"https://xdmod.access-ci.org/","default_badge_access_url_label":"Visit XDMod","prerequisites":[]},"sequence_no":14,"required":false,"roadmap":68},{"id":433,"badge":{"badge_id":11,"prerequisite_list":"","tasks":[{"badge_id":11,"sequence_no":0,"task":{"task_id":16,"name":"Knowledge Base Documentation","technical_summary":"The purpose of this task is to ensure that RPs have provided all of the knowledge base elements that are needed to fully represent their resources to the ACCESS team and the general user community. Components of the information provided will be represented on the ACCESS MATCH Portal (AMP).
","implementor_roles":"Documentation","task_experts":"Vikram Gazula","detailed_instructions_url":"https://readthedocs.access-ci.org/projects/integration-roadmaps/en/latest/tasks/Knowledge_Base_v2.html"},"required":true}],"name":"ACCESS Documentation","graphic":"https://operations-api.access-ci.org/wh2/integration_badges/v1/files/22c32be5-dcf1-4a28-a9a6-a84b4af9273d","researcher_summary":"Resource documentation is published through ACCESS.","resource_provider_summary":"RP publishes and maintains documentation in the ACCESS Confluence knowledge base about their resource, including instructions and information on the system usage and usage examples.","verification_summary":"ACCESS confirms that the knowledge base has a page documenting the resource.","verification_method":"Manual","default_badge_access_url":"https://access-ci.atlassian.net/wiki/spaces/ACCESSdocumentation/overview","default_badge_access_url_label":"Knowledge Base","prerequisites":[]},"sequence_no":4,"required":true,"roadmap":68},{"id":383,"badge":{"badge_id":1,"prerequisite_list":"","tasks":[{"badge_id":1,"sequence_no":0,"task":{"task_id":2,"name":"ACCESS Allocated Resource Integration Coordination","technical_summary":"A resource provider wishing to integrate an ACCESS allocated compute, storage, or cloud resource contacts ACCESS to start the integration process, provides basic resource information, and identifies resource provider staff contacts that will be involved in coordination, technical integration, and ongoing support activities.","implementor_roles":"Integration coordinator","task_experts":"JP Navarro, Winona Snapp-Childs","detailed_instructions_url":"https://readthedocs.access-ci.org/projects/integration-roadmaps/en/latest/tasks/ACCESS_Allocated_Resource_Integration_Coordination_v1.html"},"required":true},{"badge_id":1,"sequence_no":1,"task":{"task_id":15,"name":"Infrastructure Description","technical_summary":"ACCESS infrastructure that is visible to researchers/users, resource providers, developers, between ACCESS projects, or the broader community must be described. ACCESS resource providers, ACCESS projects, and other ACCESS affiliated online service providers (i.e. science gateways, etc.) enter basic information about their organization and then describe the infrastructure that they operate in the Cyberinfrastructure Description Repository (CiDeR). Audience relevant summaries of these descriptions are displayed in different ACCESS websites.\r\n\r\nInitial setup involves the integration coordinator obtaining administrator access to CiDeR so they can authorize others in their organization to enter and maintain infrastructure descriptions. This task should take ~½ hour. Organization staff enter initial descriptions and maintain accurate infrastructure descriptions in CiDeR. This task should take ~1 hour/year per infrastructure element.","implementor_roles":"Integration coordinator, Documentation, System administrator","task_experts":"JP Navarro, Rob Light, Nathan Tolbert","detailed_instructions_url":"https://readthedocs.access-ci.org/projects/integration-roadmaps/en/latest/tasks/Infrastructure_Description_v2.html"},"required":true}],"name":"ACCESS Resource Description","graphic":"https://operations-api.access-ci.org/wh2/integration_badges/v1/files/86413d7f-dba9-4a67-a6f4-02b45299ca4c","researcher_summary":"The resource is described and discoverable in an ACCESS resource catalog","resource_provider_summary":"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":68},{"id":398,"badge":{"badge_id":4,"prerequisite_list":"","tasks":[{"badge_id":4,"sequence_no":3,"task":{"task_id":4,"name":"ACCESS DNS Records","technical_summary":"ACCESS Operations manages the access-ci.org DNS domain and sub-domains. ACCESS projects, integrated resources, and central service may request DNS entries and DNS subdomains for their ACCESS integrated infrastructure.","implementor_roles":"Data and networking","task_experts":"Matthew Kollross","detailed_instructions_url":"https://readthedocs.access-ci.org/projects/integration-roadmaps/en/latest/tasks/ACCESS_DNS_Records_v1.html"},"required":false},{"badge_id":4,"sequence_no":0,"task":{"task_id":12,"name":"Data and Network Integration","technical_summary":"Meeting data transfer requirements requires an understanding of storage system, application requirements, and site network connectivity. While available data transfer options are determined by site preferences, ACCESS Networking and Data Transfer Services (NDTS) network engineers and data transfer specialists will continue to facilitate those options by: 1) offering a Globus subscription through at least Project Year 1 (ending 31-Aug-2023); 2) identifying, evaluating, and encouraging the use of promising data transfer applications; 3) providing the CONECTnet Internet2 overlay network to improve connectivity between RPs, and 4) consulting with sites upon request to help them tackle data transfer application and infrastructure challenges.
","implementor_roles":"Data and networking","task_experts":"David Wheeler","detailed_instructions_url":"https://readthedocs.access-ci.org/projects/integration-roadmaps/en/latest/tasks/Data_and_Network_Integration.html"},"required":true},{"badge_id":4,"sequence_no":1,"task":{"task_id":9,"name":"CONECTnet Integration","technical_summary":"CONECTnet is the wide area network infrastructure and services that connect ACCESS RPs and participant sites. In most cases, the Internet2 Research and Education (R&E) network will be the WAN provider. However, due to financial or other constraints, some sites’ only connectivity option may be via a commodity Internet service provider. In either case, ACCESS CONECT network engineers are available to work with the connecting sites to help with integration questions and optimize their network performance. CONECTnet participants are encouraged to take advantage of network measurement and test infrastructure that is available through Internet2 and also through participation in an ACCESS perfSONAR mesh.
","implementor_roles":"Data and networking","task_experts":"David Wheeler","detailed_instructions_url":"https://readthedocs.access-ci.org/projects/integration-roadmaps/en/latest/tasks/CONECTnet_Integration_v1.html"},"required":true}],"name":"ACCESS Enhanced Networking","graphic":"https://operations-api.access-ci.org/wh2/integration_badges/v1/files/8e13659e-2738-4251-bf43-bd7c563885a0","researcher_summary":"Peers with ACCESS CONECTnet to enhance networking through connectivity review and performance metrics visibility","resource_provider_summary":"The RP establishes a collaboration with the NDTS team, which includes setting up CONECTnet peering, sharing resource flow data with the ACCESS NetSage instance, and participating in ACCESS perfSONAR testing. RP provides network infrastructure information from resource to WAN and staff contacts. Initial 2 hours to gather site connectivity infrastructure information, review with NDTS, and plan next steps. Provisioning peering 2 hours hands-on (possibly more depending on site network complexity). Set up to provide NetSage flow data 1 week. perfSONAR data share 2 hours to 1+ week depending on existence of RP perfSONAR infrastructure.","verification_summary":"ACCESS CONECTnet coordinator confirms that peering has been established","verification_method":"Manual","default_badge_access_url":"https://operations.access-ci.org/pub/data_n_networking","default_badge_access_url_label":"About CONECTnet","prerequisites":[]},"sequence_no":5,"required":false,"roadmap":68},{"id":531,"badge":{"badge_id":67,"prerequisite_list":"","tasks":[{"badge_id":67,"sequence_no":0,"task":{"task_id":100,"name":"NetSage Integration","technical_summary":"First, an information conversation takes place between the NetSage team and the resource provider integration coordinator and security staff. Please contact jms@tacc.utexas.edu to start that conversation. Then, the resource provider deployed and runs a container on a VM local to their router, which shares de-identified data with an archive located at TACC. This data is displayed in a series of public dashboards. Instructions to deploy the Ingest Pipeline docker container that collects flow data is available online following the link.
","implementor_roles":"Integration coordinator, Data and networking","task_experts":"Jennifer Schopf","detailed_instructions_url":"https://github.com/netsage-project/netsage-pipeline/blob/master/README.md"},"required":true}],"name":"ACCESS NetSage","graphic":"https://operations-api.access-ci.org/wh2/integration_badges/v1/files/b7db24fc-2011-48c9-8053-ca95a0cbf266","researcher_summary":"NetSage network measurement, analysis, and visualization tool shows patterns of data movement between resource providers and visualizes performance information. With this tool you can evaluate how long a data transfer to another site might take.","resource_provider_summary":"NetSage is a managed service that displays network measurement data for large data transfers to understand patterns of behavior. This performance data is essential in understanding how to support science data movement and decrease time to science. In order to gather networking data relevant to an ACCESS-allocated resource, RPs run a VM on local hardware that supports an Ingest Pipeline container that gathers flow data, tags the flow records for transfers over 10M, and then de-identifies the information before forwarding it to an archive at TACC. This data is displayed in public dashboards available at https://access.netsage.io
","verification_summary":"The NetSage team confirms they are receiving network data for each resource, and the data is visible on the ACCESS NetSage Dashboard at https://access.netsage.io/grafana/.
","verification_method":"Manual","default_badge_access_url":"https://access.netsage.io","default_badge_access_url_label":"ACCESS NetSage Portal","prerequisites":[]},"sequence_no":6,"required":true,"roadmap":68},{"id":408,"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":10,"required":false,"roadmap":68},{"id":413,"badge":{"badge_id":7,"prerequisite_list":"","tasks":[{"badge_id":7,"sequence_no":1,"task":{"task_id":13,"name":"Deploy Globus Endpoint","technical_summary":"A Globus endpoint connects a system to Globus and enables authorized researchers (members of an allocated project team) to transfer data to and from it using Globus. During the last two years of XSEDE, hundreds of researchers used Globus to transfer data to and from XSEDE resources as a part of their projects. A single transfer request may involve a single file or a million files. Individual requests were commonly 100 GB or more and frequently 1 TB or more. Requests of 10 TB or more happened daily. The other end of the data transfer may be a personal system, a campus system (hundreds of campuses have multi-user Globus endpoints and encourage their researchers to use them), or another HPC system (hundreds of national-scale service providers, e.g., DOE or non-US systems, have Globus endpoints). Globus enables researchers to perform transfers at these scales and is broadly available on the systems where research data is used.","implementor_roles":"Data and networking, System administrator","task_experts":"Lee Liming, Eric Blau","detailed_instructions_url":"https://readthedocs.access-ci.org/projects/integration-roadmaps/en/latest/tasks/Deploy_Globus_Endpoint_v1.html"},"required":true}],"name":"Globus Data Transfer","graphic":"https://operations-api.access-ci.org/wh2/integration_badges/v1/files/9a5032b7-d9b4-42a6-adc6-088be8ed4c1e","researcher_summary":"Researchers can use Globus to transfer data to and from this resource.","resource_provider_summary":"The RP has deployed a Globus endpoint that enables ACCESS-allocated researchers to transfer data to and from this resource using their ACCESS-CI ID.","verification_summary":"ACCESS staff can discover the Globus endpoint for the resource in Globus.","verification_method":"Manual","default_badge_access_url":"https://app.globus.org/file-manager/collections","default_badge_access_url_label":"Go to Globus","prerequisites":[]},"sequence_no":15,"required":false,"roadmap":68}],"name":"ACCESS Allocated Storage","graphic":"https://operations-api.access-ci.org/wh2/integration_badges/v1/files/b3d371cc-3195-4ab6-9ded-14f90543a6fb","executive_summary":"The ACCESS program (https://access-ci.org) enables researchers and educators to gain access to advanced computing, visualization, and data resources to accomplish their research or classroom objectives using an allocations process described at https://allocations.access-ci.org/.\r\n\r\nThis roadmap includes a set of badges required to integrate a specific storage resource as ACCESS allocated in production. It also offers some optional badges.","infrastructure_types":"Storage","integration_coordinators":"Lee Liming","status":"Production"}},"status_code":200}