CIDuty/Meetings:2013-09-03
From MozillaWiki
< CIDuty(Redirected from Buildduty/Meetings:2013-09-03)
« previous week |
index |
next week »
< most recent |
upcoming >
Contents
Release Engineering Buildduty Meeting
- Date: 2013-09-03
- Time: 1:30pm EDT
- Room: ReleaseEngineering Vidyo room
- Meeting notes: https://wiki.mozilla.org/ReleaseEngineering/Buildduty/Meetings:2013-09-03
Status of buildduty period
- These tegras need attention (rebooting hasn't helped):
Bugs filed
- https://bugzil.la/910818 - Please investigate cause of network disconnects 2013-08-29 10:22-10:24 Pacific
- should point in-house build slaves to in-house masters, and aws slaves to aws masters? (to eliminate need for high VPC uptime)
- availability zones of buildbot master types
Previous action items
- armenzg - to reach IT wrt to nagios URL links documentation
- carry forward
- jhopkins to look at bug with no reboot history - https://bugzil.la/908359
Agenda
- (Callek) put foopies in slave_health and slavealloc [as slaves]?
- Defer to when coop is here, is probably best.
- (coop) should go in slavealloc, but how? ideas:
1. new category (and associated db table) for foopies, where tegra/panda maps to foopy maps to master 2. foopies as masters 3. foopies as slaves
- for 2 and 3, still need a join table to do the one-to-many mapping
- foopy list in wiki, similar to project branch tracking
- (jhopkins) slaveapi failing to IPMI-reboot due to missing netflow
- need to deploy slaveapi to final location and open netflow, or open netflow from cruncher now as a temporary measure
- need list of slaves needing reboot to feed into slaveapi
- last_job_per_slave currently does this
List of current projects
Action items
- (jhopkins) talk to catlee about VPC link, availability zones
- armenzg - to reach IT wrt to nagios URL links documentation
- Callek: schema for new foopy table in slavealloc db (+ join table)
- bhearsum: file slaveapi bugs