ReferencePlatforms/How To/Setup a New Reference Platform

From MozillaWiki
Jump to navigation Jump to search

Congratulations. You have been chosen to setup a new reference platform. Armen summarized this journey as "It will be difficult". In addition to testing the new image on the test or build machines, there are several other steps that must be taken to ensure that our build infrastructure is read to work with the new platform and the associated slaves. There are several tasks that you can do ahead of time to make it easier noted in the checklist below. Many of these involve IT, so open bugs accordingly.

Do you need a new master?

  • Do you have enough capacity on your master to accommodate the new slaves?
    • roughly, testing masters should have no more than 80 slaves (these days) (Todo: how to check what slaves are assigned to each master)
  • Does your master reside in the same data center as your new slaves?
    • If not, you should set up a new test master so both slaves and master reside in the same data center.

If so, open bugs for the new master

If the answer is no to any of the questions above, you'll need to setup a new master, unless there unused masters that are already provisioned. Open a bug with IT to bring up some VMs where you can install a new master (example: bug 782870. [ https://wiki.mozilla.org/ReleaseEngineering/Master_Setup Read this document for the steps to setup a new master. This document also describes some bugs that need to be opened with various teams when setting up the new master, so read it now.

Open bugs to establish network flows to the sql server from the new master

  • Open a bug for network flows from your new master(s) to the sql server to example bug 783055

Open a bug for graph server changes

  • testing machines and each type of build need graph server changes
    • graph server work needs to be run on staging and production graph server
    • need to land changes to 'sql/data.sql' on the 1.0 branch of http://hg.mozilla.org/graphs
    • If this is a new build platform, make sure that graph server knows about the build platform

Open a bug for tbpl changes

    • tbpl needs to be patched to reflect the new platform bug 782826 is an example of this change

Slavealloc changes and cnames for slaves

  • Open a bug with IT for the cnames for the slaves. Example bug 782870
  • Add the new slaves to slavealloc
  • Add the slave password to the slave_passwords table for the appropriate poolid and distro

On the client

  • disable screensaver
  • disable power savings
  • test that resolution meets requirements set forth by devs. This may require a dongle.
Retrieved from "https://wiki.allizom.org/index.php?title=ReferencePlatforms/How_To/Setup_a_New_Reference_Platform&oldid=461973"