AuroraMiddleware/skia2
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
05572fa6e7
skia2/site/dev/sheriffing/trooper.md
Ben Wagner 05572fa6e7 Update docs on Skia bots. 
No-Try: true
Docs-Preview: https://skia.org/?cl=52163
Change-Id: I2bcd73bc7597219e4748c28e9120b5138a0eb3d1
Reviewed-on: https://skia-review.googlesource.com/52163
Reviewed-by: Eric Boren <borenet@google.com>
Reviewed-by: Ravi Mistry <rmistry@google.com>
Commit-Queue: Ben Wagner <benjaminwagner@google.com>
2017-09-28 13:45:37 +00:00

4.2 KiB
Raw Blame History

Infra Trooper Documentation

Contents

What does an Infra trooper do?

The trooper has two main jobs:

  1. Keep an eye on Infra alerts available here.

  2. Resolve the above alerts as they come in.

View current and upcoming troopers

The list of troopers is specified in the skia-tree-status web app. The current trooper is highlighted in green. The banner on the top of the status page also displays the current trooper.

How to swap trooper shifts

If you need to swap shifts with someone (because you are out sick or on vacation), please get approval from the person you want to swap with. Then make the change in the cloud console. Add a filter to find the dates you are looking for and then click on the entries you want to edit.

Note: The above link can be used to update the sheriff/wrangler/robocop schedules as well.

Tips for troopers

  • Go over the trooper handoff doc to be aware of ongoing problems and any issues the previous trooper ran into. Document any notes there from your trooper week that might help the next trooper.

  • Make sure you are a member of MDB group chrome-skia-ninja. Valentine passwords and Chrome Golo access are based on membership in this group.

  • Install the Skia trooper Chrome extension (available here) to be able to see alerts quickly in the browser.

  • Where machines are located:

    • Machine name like "skia-gce-NNN", "skia-i-gce-NNN", "ct-gce-NNN", "skia-ct-gce-NNN", "ct-xxx-builder-NNN" -> GCE
    • Machine name ends with "a9", "m3" -> Chrome Golo/Labs
    • Machine name ends with "m5" -> CT bare-metal bots in Chrome Golo
    • Machine name starts with "skia-e-", "skia-i-" (other than "skia-i-gce-NNN"), "skia-rpi-" -> Chapel Hill lab

  • The chrome-infra hangout is useful for questions regarding bots managed by the Chrome Infra team and to get visibility into upstream failures that cause problems for us.

  • To log in to a Linux bot in GCE, use gcloud compute ssh default@<machine name>. Choose the zone listed for the GCE VM (or specify it using the --zone command-line flag).

  • To log in to a Windows bot in GCE, use Chrome RDP Extension with the IP address of the GCE VM shown on the host info page for that bot. The username is chrome-bot and the password can be found on Valentine as "chrome-bot (Win GCE)".

  • To log in to other bots, see the Skolo maintenance doc remote access section.

  • If there is a problem with a bot in the Chrome Golo or Chrome infra GCE, the best course of action is to file a bug with the Chrome infra team.

  • Read over the Skolo maintenance doc for more detail on dealing with device alerts.