This task involves installing and running the Information Publishing Framework (IPF) tool on ACCESS allocated compute resources in order to publish batch resource, queue, and job information, software module information, and (optionally) job events to the ACCESS information sharing platform. The ACCESS information sharing platform provides information to ACCESS portals, SGCI resource schema compatible science gateways, and other service developers.
","implementor_roles":"System administrator","task_experts":"Andy Loftus, Eric Blau","detailed_instructions_url":"https://github.com/access-ci-org/ipf/blob/master/README.md"},"required":true}],"name":"ACCESS Software Publishing","graphic":"https://operations-api.access-ci.org/wh2/integration_badges/v1/files/a39d25dc-f8c6-4f0e-9784-6c27fcece227","researcher_summary":"Software information is available through the ACCESS Software Documentation Service","resource_provider_summary":"Deploy and operate the IPF component, or request the ACCESS Operations run it for you, to publish software module information from the resource.","verification_summary":"Resource software module information is available in the ACCESS Software Documentation Service (SDS) at https://sds.access-ci.org.","verification_method":"Manual","default_badge_access_url":"https://sds.access-ci.org","default_badge_access_url_label":"Software Documentation Service","prerequisites":[]},"sequence_no":7,"required":false,"roadmap":69},{"id":435,"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":10,"required":false,"roadmap":69},{"id":440,"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":69},{"id":445,"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":69},{"id":385,"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":69},{"id":405,"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":4,"required":true,"roadmap":69},{"id":395,"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":2,"required":true,"roadmap":69},{"id":410,"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":5,"required":true,"roadmap":69}],"name":"ACCESS Online Service","graphic":"https://operations-api.access-ci.org/wh2/integration_badges/v1/files/a2d434e2-4e40-4e50-9a90-5d777f5827e7","executive_summary":"This roadmap integrates online services provided by ACCESS projects and their vendors / partners into the ACCESS operational environment. The roadmap is intended for online services that are visible outside a single ACCESS project and used by other ACCESS projects, resource providers, developers, or ACCESS researchers. Online services are accessed using a variety of network protocols suited for their function and target audience. Examples include ACCESS websites; Atlassian, GitHub, Google, and Globus services; DNS services; IAM services, and various APIs.","infrastructure_types":"Online Service","integration_coordinators":"JP Navarro","status":"Draft"}},"status_code":200}