canmove, Confirmed users
1,394
edits
ReleaseEngineering/Applications/Slavealloc: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/Applications/Slavealloc (view source)
Revision as of 20:16, 25 March 2011
, 25 March 2011no edit summary
No edit summary |
|||
| Line 63: | Line 63: | ||
=== Slave Side === | === Slave Side === | ||
All slaves run [http://hg.mozilla.org/build/puppet-manifests/file/tip/modules/buildslave/files/runslave.py runslave.py] during startup. This file is distributed via puppet. The larger slave-startup process is described in [[ReleaseEngineering/Buildslave Startup Process]]. | All slaves run [http://hg.mozilla.org/build/puppet-manifests/file/tip/modules/buildslave/files/runslave.py runslave.py] during startup. This file is distributed via puppet. The larger slave-startup process is described in [[ReleaseEngineering/Buildslave Startup Process]]. | ||
== Staging == | |||
As described above, http://staging-slavealloc.build.mozilla.org/ points to a staging implementation of the slave allocator. This implementation has its own database runs from a distinct daemon, although it is served from the same nginx instance. | |||
'''NOTE:''' ''all'' slaves are configured use the production allocator. Allocations from the staging allocator will need to be simulated by hand (<tt>runslave.py</tt> has an command-line option to set the allocator URL). This is done to allow us, as a group, to move slaves between staging and production using a single slave allocator. | |||
== Development == | == Development == | ||