ReleaseEngineering/TegraDashboard

Tegra Dashboard

Tegras have been decommissioned

The current status of each Tegra, and other informational links, can be seen on the Tegra Dashboard. Dashboard is only updated every 8 minutes; use ./check.sh on the foopy for live status.

The page is broken up into three sections: Summary, Production and Staging where Production/Staging have the same information but focus on the named set of Tegras.

The Summary section has the current start/end date range of the displayed Tegras and a grid of counts.

                                      Production  Staging
Tegra and buildslave online           57          8
Tegra online but buildslave is not    0           0
Both Tegra and buildslave are offline 19          2

The Production/Staging section is a detailed list of all Tegras that fall into the given category.

ID 	Tegra 	CP 	BS 	Msg 	Online 	Active 	Foopy 	PDU 	active bar

• ID Tegra-### identifier. Links to the buildslave detail page on the master
• Tegra Shows if the Tegra is powered and responding: online|OFFLINE
• CP Shows if the ClientProxy daemon is running: active|INACTIVE
• BS Shows if the buildslave for the Tegra is running: active|OFFLINE
• Msg The info message from the last check.py run for that Tegra
• Foopy Which foopy server the Tegra is run on. Links to the hostname:tegra-dir
• PDU Which PDU page can be used to power-cycle the Tegra. PDU0 is used for those not connected as of yet
• Log Links to the text file that contains the cumulative check.py log entries
• active bar A single character summary of the last 10 status checks where '_' is offline and 'A' is active

How to make changes to the dashboard

The dashboard is currently hosted on relengweb1.dmz.scl3.mozilla.com. It is accessible via the build VPN via LDAP, i.e. key-based auth should happen automatically as your LDAP user.

There is a crontab entry on relengweb that pulls the generated dashboard from mobile-dashboard1.build.mtv1.mozilla.com every 5 minutes. Again, this host is accessible via the build VPN. The dashboard is generated by the user briarpatch via the script /home/briarpatch/run_dashboard.sh that runs via cron every 5 minutes.