ACCESS Allocated Resource Integration Coordination v2

Infrastructure Integration Roadmap Task

Task Type(s): Coordination
Start by phase: Planning
Complete by phase: ongoing
RP role(s): PI and co-PI(s), Resource integration coordinator(s)

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.

Support Information

For assistance with this task see the Support Information section in the Integration Roadmap Description.

Prerequisite tasks

None

Operator Instructions

Integration Launch

The integration engagement and process begin when a resource PI, co-PI, or designated Resource Integration Coordinator open an ACCESS ticket using Integration and Operations Requests and identifies their institution name, the name and type of the resource they plan to integrate, and which ACCESS integration roadmap they plan to follow (if known). Those who are exploring the possibility of integrating may open a ticket and request to be contacted for futher discussion.

In response, ACCESS will identify an Integration Concierge, and if needed schedule a call between the Resource Integration Coordinator, anyone else the RP wishes to invite, the ACCESS Integration Concierge, and the ACCESS Resource Provider Coordinator. The purpose of the meeting is to introduce RP and ACCESS staff to each other, to discuss the integration process and timeline, and to introduce integration roadmap documentation. A call may not be necessary if the RP is already familiar with the ACCESS integration process.

The Integration Concierge acts as the resource or service operator’s primary point of contact for all questions and issues in selecting and completing the integration roadmap.

The Resource Integration Coordinator is responsible for coordinating all RP activities, for identifying and maintaining the list of RP contacts involved in different aspects of coordination, integration, and resource support (see the next section), for communicating relevant ACCESS integration information and Roadmap based resource integration document to RP staff, and for managing RP staff access to ACCESS services.

Identity Resource Provider Contacts

Soon after the Integration Launch the Resource Integration Coordinator must enter the following RP contacts in CiDeR:

  1. Allocations process contact(s)

  2. AMIE technical contact(s)

  3. Cybersecurity and incident response contact(s)

  4. Data and networking contact(s)

  5. Integration coordinator(s)

  6. Metrics and performance data contact(s)

  7. Public documentation contact(s)

  8. Public relations and media contact(s)

  9. Researcher support and ticket handling contact(s)

  10. Resource news and outages publisher(s)

  11. System administrator(s)

If the RP doesn’t know who some of these contacts will be, or wishes not to identify them until relevant integration effort ramps up, please name the Integration Coordinator as the placeholder for those roles. In other words, ACCESS needs each someone to be the contact in each of the above areas, even if it’s the coordinator who will eventually hand off effort to someone else. As integration activities ramps up the Integration Coordinator can add other RP staff replacing themselves as necessary.

The Integration Coordinator should enter and update their RP contacts in CiDeR as detailed in the task:

  • [Infrastructure Description v2] (Infrastructure_Description_v2.md)

The Integration Coordinator is responsible for maintaining accurate contact information CiDeR as RP staff change. We recommend that the Integration Coordinator review and correct their contacts every 6 months. This sub-task should take ~1 hour to complete initially, and ~½ hour annually to keep up-to-date.

Each ACCESS Integration Roadmaps task will list which RP staff contacts normally perform that task.