Operations PY 10 Planning Greg Peterson Operations Director

Operations PY 10 Planning Greg Peterson Operations Director gdp@utk. edu

Ops PY 10 Project and L 2 KPIs Metric Level Metric Name Mean composite availability of core services Project (geometric mean of critical services and XRAS, %) Project L 2 KPI 2 Goal Subgoal Sustain the Ecosystem Provide reliable, efficient, and secure infrastructure Sustain the Ecosystem Provide excellent user support Hours of downtime with direct user impacts from an XSEDE security incident Sustain the Ecosystem Provide reliable, efficient, and secure infrastructure Mean rating of user satisfaction with tickets closed by the XOC Sustain the Ecosystem Provide excellent user support Mean time to ticket resolution (hours) L 3 Owner PY 9 Target PY 10 Target Sys. Ops 99. 9% XOC <16/qtr Cybersecurity 0/qtr XOC 4. 5 of 5/qtr

PY 10 Priorities • Office (2. 4. 1) • Continue coordination of Operations activities, reporting, reviews • Cybersecurity (2. 4. 2) • • 3 Vulnerability scanning & mitigation (w/ Sys. Ops) Update and maintain policies, standards, & guidelines (w/ Project Office) Maintain operational security Operate and/or maintain XSEDE CA, CA Trust repository, CILogon service, and Kerberos realm

PY 10 Priorities (cont. ) • Data Transfer Services (2. 4. 3) • Maintain DTS (hardware/software tools that monitor/measure services DNS, Grid. FTP logging, perf. SONAR, maddash, Globus Online, I 2 connectivity) • Provide direct network, DTN, and file system expertise • Communicate and promote best practices to the community • Document best practices • XSEDE Operations Center (2. 4. 4) • • 4 Provide (Level 1) user support Monitoring XSEDE’s Enterprise servers and services (w/ Sys. Ops) Develop and maintain XOC procedures Develop and maintain operational documentation

PY 10 Priorities (cont. ) • Sys. Ops (2. 4. 5) • Maintain and monitor XSEDE’s Enterprise servers and services (w/ 2. 4. 4) • Continue deploying according to Hybrid Cloud plan for XES and software (w/ 2. 3) • Operate and continue developing INCA monitoring framework 5

What’s New or Changing in PY 10 • Ops Dir. office is coordinating all transition efforts for Ops • Each Ops WBS will have transition items and effort • Cybersecurity will be allocating time and effort to thoroughly review XSEDE’s resources on AWS • For DTS, more broadly expand engagement in the hands-on data transfer consulting service. Nothing new or discontinued • Nothing new, changing, or discontinued in XOC • Evaluating Sys. Ops migration of Identity Management (Id. M) to AWS. Nothing changing or discontinued 6

PY 10 ± 5% Exercise 5% Increase impacts: • Cybersecurity will increase vigilance on vulnerability scanning and operations security oversight, including AWS. This is greater scrutiny on potential security holes which might prove to be quite impactful • DTS will provide additional expertise to direct network, DTN and file system efforts to greater improve the project’s data user experience. Impact would be a better user experience for some users 7

PY 10 ± 5% Exercise (cont. ) 5% Increase impacts: • XOC will increase/improve user support, it’s primary activity, by adding more effort toward (Level 1) support, training, documentation, and procedure improvement • Sys. Ops will increase effort for transition documentation. Impact level is hard to determine w/o more information about follow-on award or awardees. 8

PY 10 ± 5% Exercise (cont. ) 5% Decrease impacts: • Cybersecurity would eliminate effort on publications and place less emphasis on performing incident response drills, federated intelligence sharing, and table top exercises. Impact would be minimal since these are the lower priority activities for the group in PY 10 • DTS would reduce collaboration with I 2 on improving metrics collection and would engage with the project’s SPs and user community less on promoting a shared understanding of needs. 9

PY 10 ± 5% Exercise (cont. ) 5% Decrease impacts: • XOC would reduce effort for Enterprise server/services monitoring and creating additional operational documentation, putting the focus more squarely on its primary purpose of user support. Impact could be mild since XOC is 24/7 but Sys. Ops effort is not. • Sys. Ops would reduce travel to relevant conferences, meetings, etc. Impact to the project would be minimal because we’ll be in the final year. 10

PY 10 Publications Being Considered Cybersecurity is considering submitting to the following: - Internet 2 Technology Exchange - PEARC 21 / Trusted CI Workshop at PEARC 21 - NSF Cybersecurity Summit 2020 - Still mulling over possible topics for these No other pubs planned in Ops at present 11

Recommendations Being Addressed in PY 10 • At present, all recommendations from JIRA have been addressed • No new recommendations 12

PY 10 Transition Planning Efforts • Ops has put a Transition task in the plan for PY 10 ~0. 9 FTE • Transition items include, but are not limited to: • Director’s office transition coordination • XSEDE Enterprise Services (2. 4. 2 & 2. 4. 5) • Trust group and security processes handoff (2. 4. 2) • Level 1 ticket support processes (2. 4. 4) hand off by going over XOC playbook • XSEDEnet, Perf. SONAR, and DNS hand off (2. 4. 3) 13