Roles¶
Service Team Roles¶
Each Rubin service will have the following roles defined in the table below to manage and operate the service. A person can hold more than one role.
The roles are documented in Confluence here. Views are available on the tabs to filter by the Service Grouping.
Role |
Responsibilities |
|---|---|
Service Sponsor |
Responsible for allocating staff to work on the service. This person is an Ops Team Leader or designate. |
Service Owner |
Responsible for the overall service functionality, data, and user experience. Similar to a product owner. |
Database Administrator |
Responsible the database’s design, performance, security, and maintenance. Absent if no database. |
Service Infrastructure |
Responsible for the infrastructure configuration, deployment, and routine maintenance |
Operations Support |
Responsible for the support of the service. Handles alerts, monitoring, incident response |
Documentation Lead |
Ensures all documentation is created and up to date. |
SLAC and Rubin Team Infrastructure Roles¶
Below are the roles and responsibilities for the SLAC and Rubin Infrastructure teams.
Role |
Responsibilities |
|---|---|
Infrastructure Services Support (Physical) |
Responsible for physical datacenter, servers, storage, and networking. This includes Weka and Ceph. |
Applications and Users (Virtual) |
Responsible for the virtual infrastructure, Kubernetes cluster, vClusters and Kubernetes Weka Storage. The DBA is on this team and is responsible for Butler and providing subject matter expertise to help the App DBAs. |
Astro Domain / Rubin Specific |
Understanding Science Operations, Teams, and Roles. They may also be service owners. |