CIDuty/Meetings:2014-01-28

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

Release Engineering Buildduty Meeting

• Date: Tuesdays
• Time: 1:00pm EST
• Room: ReleaseEngineering Vidyo room
• Meeting notes: https://wiki.mozilla.org/ReleaseEngineering/Buildduty/Meetings:2014-01-28

Status of buildduty period

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

Bugs filed

• https://bugzilla.mozilla.org/show_bug.cgi?id=964855
  • Prevent runslave.py from starting buildbot with a basedir that starts with uppercase

Agenda

(POSTPONED IT FROM LAST WEEK)

• (armenzg) Windows machines do not receive keys upon imaging
  • https://bugzilla.mozilla.org/show_bug.cgi?id=930595
  • deploying the keys manually is not too difficult and it is documented

Q and Dustin and [jhopkins] talked about this before and (as [jhopkins] recall[s]) Dustin figured that since effort was being invested into Puppet key management, investing effort into GPO key management was not the best use of our time. The existing GPO key copying mechanism did not do proper staging/try/production key management so [jhopkins] asked for it to be disabled and we've been handling it manually since then.

• (jhopkins) tegra problem tracking escalation - wiki section created
  • https://wiki.mozilla.org/ReleaseEngineering/How_To/Android_Tegras#Tegra_Problem_Tracking
• (jhopkins) do we want problem tracking bugs for AWS loaner instances?
  • our reporting workflow seems to rely on them
• (coop) minimum viable product for self-serve slave loan tool

web interface:

• • for devs to request machines and we would approve it
  • start/stop aws machines

puppet:

• • do the secret clean up and disable puppet itself
  • plus setup the password

slaveapi:

• inventory changes for AWS
  • can IT export a way to 'kick' DNS instead of us waiting for it to update?
• bug filling
• nagging emails
• LDAP changes for machine and user
• automatically do re-imaging
  • we can do this for Mac (you can't switch OS versions)
  • also iX and HP, but maybe not headless

what are we solving?

• look better to the rest of the company
• reduce human time by reducing steps
• reduce costs (by shutting things faster)
• VPN issues

• (coop) importance of staying on top of buildduty tasks
  • Bug 962698 - Expose aws sanity report data via web interface in json format
  • expose long-running instances via nagios (for ack-ing, etc)
  • Possibly https://bugzilla.mozilla.org/show_bug.cgi?id=922320
  • add loan requests to buildduty report

List of current projects

• https://github.com/bhearsum/slaveapi/blob/master/TODO
• https://bugzilla.mozilla.org/show_bug.cgi?id=914764
• in-house capacity: https://bugzilla.mozilla.org/show_bug.cgi?id=867593

Action items

• (Callek) file tracking bug for self-serve slave loan tool
• (coop) file a bug to add loan requests to buildduty report