Release Engineering Buildduty Meeting

Date: 2013-12-17
Time: 1:00pm EST
Room: ReleaseEngineering Vidyo room
Meeting notes: https://wiki.mozilla.org/ReleaseEngineering/Buildduty/Meetings:2013-12-17

Status of buildduty period

(armenzg) make in-house test masters permit all other host classes to connect to them
- we would need monitoring for them
- in the long term, we would reduce complexity when setting new things up
- it would also reduce slavealloc complexity
- this is not high priority but it might be nice for setting future masters
- this increases unique builders per master, and is part of why we split it up to begin with, I'm (callek) not in favor due to that
(jhopkins) http://bugzil.la/950702 - AWS builds are falling way behind. In response, I filed:
- http://bugzil.la/950746 - Log aws_watch_pending.py operations to a machine-parseable log or database
  - in the meantime, emails go to a specific list of people defined in crontab on buildduty@cruncher
- http://bugzil.la/950780 - Start AWS instances in parallel
(jhopkins) do we have a plan for moving services off of cruncher?
- was talk of moving AWS tools off of cruncher
  - AWS manager http://bugzil.la/946292 http://bugzil.la/943134
(coop) http://bugzil.la/905587 - make sure to check redis once a week as buildduty
(coop) shutting down loaner instances over the break <- where are we on this?
- I didn't send the e-mail due to joduinn's response contradicting catlee's and no confirmed decision -- I'm happy to send the e-mail and do so.
(Callek) status of reduction of nagios alerts (http://bugzil.la/927941 )
(Callek) new mobile masters