EngineeringProductivity/Projects/Everything
Motivation
This page is to help diagram all the various things the A*Team has built and continue to support.
The plan is to draw high level components/systems, and links between them, so it is easier to see how all the parts work together. Hopefully this diagram will be clickable so the reader can get more detail on each of the components.
Something like what RelEng has, but without all the internals.
History (blah blah blah..)
My name is Kyle Lahnakoski, and I joined the A*Team in April 2013.
When I started, the plan was to improve the alerting mechanism in Datazilla. Jmaher and jeads were kind enough to give me an overview of the various systems surrounding Datazilla. I drew my notes and diagrams on paper, and for months I carried my "secret decoder" so I could talk reasonably intelligently about the various A*Team systems and how they connected.
It is late June 2014 now, and my notes are long lost. I recently had a request from another team's member (:avih) about how dzAlerts fits into the greater ecosystem. In a recent meeting jgriffin mentioned it would be nice to have a summary of all the great things the A*Team works on and supports.
I would like to draw another not-so-secret decoder, but this time with everything!
Please help by adding the A*Team systems to The List below
The List
Use the EMPTY TEMPLATE to add more entries. Include ones you know about, even if you can not fill them.
EXAMPLE
- Docs - some wiki, or read the docs to learn more
- Code - link to code, if it makes sense
- Contact - for ekyle to contact if he has questions
- Inputs -
- automated resources
- services consumed
- Outputs/Services
- automated services provided
- dashboards (and teams that consume them)
EMPTY TEMPLATE
- Docs -
- Code -
- Contact -
- Inputs
- Outputs/Services
Autophone
- Docs - https://wiki.mozilla.org/Auto-tools/Projects/AutoPhone
- Code - https://github.com/mozilla/autophone/
- Contact -
- Inputs
- Outputs/Services
- http://phonedash.mozilla.org/ (used by who?)
B2gPerf
- Docs -
- Code -
- Contact -
- Inputs
- Outputs/Services
Bugzilla
- Docs - http://bugzilla.readthedocs.org
- Code - http://git.mozilla.org/?p=webtools/bmo/bugzilla.git
- Contact - Mark Cote, Byron Jones, David Lawrence, Dylan Hardison
- Inputs
- Web UI
- WebServices API (REST, XMLRPC, JSONRPC)
- Outputs/Services
- https://bugzilla.mozilla.org (bug reporters, developers, etc)
- WebServices API (For REST https://bugzilla.mozilla.org/rest)
BugzFeed
- Docs -
- Code -
- Contact -
- Inputs
- Outputs/Services
Buildbot
- Docs -
- Code -
- Contact -
- Inputs
- hg.mozilla.org?
- Outputs/Services
- builder slaves
- tester slaves
- https://wiki.mozilla.org/ReleaseEngineering/BuildAPI ??
- where do buildbot results go, a file? picked up by TBPL
Buildbot/Talos
- Docs - https://wiki.mozilla.org/Buildbot/Talos
- Code - http://hg.mozilla.org/build/talos
- Contact - jmaher@mozilla.com
- Inputs
- build for desktop or android
- commandline (done via mozharness now) to specify which test(s) to run
- Outputs/Services
- log file with raw data
- uploaded summarization of data to graph server
- uploaded raw data to datazilla
Can be referred to as what is run by buildbot or by tbpl since this is the only performance test run on our per revision CI system. Other tools are run at a different cadence.
Treeherder
- Docs - https://wiki.mozilla.org/Auto-tools/Projects/TreeHerder_2013Q2
- Code
- Contact - [:jeads][:camd][:mdoglio]
- Inputs
- Pushlog from hg.mozilla.org via json-pushes
- Build/tests from Buildbot via buildapi
- Direct pushes via ``treeherder-client``
- Build/tests from Taskcluster (under development)
- Outputs/Services
Datazilla
- Docs -
- Code -
- Contact -
- Inputs
- Outputs/Services
Graph Server
- Docs -
- Code -
- Contact -
- Inputs
- Outputs/Services
Orange Factor
- Docs - https://wiki.mozilla.org/Auto-tools/Projects/WarOnOrange
- Code - http://github.com/jmaher/Orange-Factor
- Contact -
- Inputs
- buildbot messages (using pulse)
- build logs
- comments from TBPL
- bugzilla bug data
- Outputs/Services
- https://brasstacks.mozilla.com/orangefactor/
- email status [War on Orange]
Ouija
- Docs - https://wiki.mozilla.org/Auto-tools/Projects/Ouija
- Code - https://github.com/dminor/ouija.git
- Contact - jmaher
- Inputs
- https://hg.mozilla.org/
- tbpl.mozilla.org
- Outputs/Services
Pulse
- Docs - https://wiki.mozilla.org/Auto-tools/Projects/Pulse
- Code -
- Contact -
- Inputs (exchanges? http://christian.legnitto.com/blog/2010/07/17/mozilla-pulse-and-rabbitmq/)
- Outputs/Services
Review Board
- Docs -
- Code -
- Contact -
- Inputs
- Outputs/Services
TBPL (for the sake of history)
- Docs -
- Code -
- Contact -
- Inputs
- Outputs/Services
Eideticker
- Docs -
- Code -
- Inputs -
- Nightly/inbound b2g and android builds.
- Outputs/Services
- Eideticker dashboard (http://eideticker.mozilla.org)
BMO/ES Cluster
- Docs - https://wiki.mozilla.org/BMO/ElasticSearch
- Code - https://github.com/klahnakoski/Bugzilla-ETL
- Contact' - klahnakoski@mozilla.com
- Inputs -
- Bugzilla (direct database access)
- Outputs/Services
dzAlerts
- Docs - https://wiki.mozilla.org/Auto-tools/Projects/Alerts
- Code - https://github.com/klahnakoski/datazilla-alerts
- Contact' - klahnakoski@mozilla.com
- Inputs
- Datazilla web service (https://datazilla.mozilla.org/talos/refdata/objectstore/json_blob)
- Eideticket web service (http://eideticker.mozilla.org)
- Outputs/Services
- fxos-perf-alerts@mozilla.org (b2g sheriffs?)
AlertManager
- Docs -https://github.com/jmaher/alert_manager/
- Code - https://github.com/jmaher/alert_manager/
- Contact' - jmaher@mozilla.com
- Inputs
- mozilla.dev.tree-management alerts from graph server
- Outputs/Services
- webUI for organizing and taking action on these alerts.
charts.mozilla.org
- Docs -
- Code - https://github.com/mozilla/charts
- Contact' - klahnakoski@mozilla.com
- Inputs -
- BMO/ES Cluster
- Outputs/Services
- charts.mozilla.org (project managers)