1 / 3

Typical Shift Plan

Typical Shift Plan. Browse recent shift history Check performance of all sites File tickets for new issues Continue interactions about old issues Check status of current tasks Check all central processing tasks Monitor analysis flow (not individual tasks) Overall data movement

lefty
Download Presentation

Typical Shift Plan

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Typical Shift Plan • Browse recent shift history • Check performance of all sites • File tickets for new issues • Continue interactions about old issues • Check status of current tasks • Check all central processing tasks • Monitor analysis flow (not individual tasks) • Overall data movement • File software (validation) bug reports • Check Panda, DDM health • Maintain elog of shift activities

  2. Some Communications Issues • Monitoring: primary goal of ADCoS team • When problems are found • Elog entry must be opened first • If software error, file validation Savannah bug report • If task error, file operations savannah bug report • If site error, file GGUS (or RT) bug report • If serious error, inform/consult ADCoS mailing list • If DDM error, inform DDM on call expert (through mailing list) • If central services problem, inform central services expert on call • Interventions • If a site is in downtime or failing badly for many hours, shifters can set site to offline (please leave elog ticket open till site is set online)

  3. Monitor-Escalate-Follow up • We expect production to be maximally automated • Shifters primary function – monitor • Any problems discovered – escalate • Continue to follow up all open issues • Types of escalation: • Site problems • Service problems (Panda, DB, DDM…) • Software bugs • Work flow (tasks, exercises…)

More Related