CIDuty/Meetings:2013-12-17

From MozillaWiki
Jump to: navigation, search

« previous week | index | next week »
< most recent | upcoming >


Release Engineering Buildduty Meeting

Status of buildduty period

https://releng.etherpad.mozilla.org/buildduty

Bugs filed

Previous action items

  • (bhearsum) file nagios bug for loan requests monitoring

Agenda

  • (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?
  • (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

List of current projects

Action items

  • (coop) blog post about service expectations
  • (jhopkins) file tracking bug to move services off of cruncher