ReleaseEngineering/How To/Setup a buildbot master: Difference between revisions

Jump to navigation Jump to search
updated IT info for firewall changes
(updated IT info for firewall changes)
Line 69: Line 69:
== Add masters to slavealloc ==
== Add masters to slavealloc ==
See [https://wiki.mozilla.org/ReleaseEngineering/How_To/Setup_Personal_Development_Master#Adding_your_master_to_slavealloc Adding your master to slavealloc]
See [https://wiki.mozilla.org/ReleaseEngineering/How_To/Setup_Personal_Development_Master#Adding_your_master_to_slavealloc Adding your master to slavealloc]
== Lock a slave and let it take jobs ==
Locked through slavealloc a slave to the newly setup master.
Let it run for a couple of hours and check that the jobs worked well.
Check also in the #buildduty channel for possible nagios checks going off (e.g. [[ReleaseEngineering/Queue_directories|Queue directories]] checks)
If no issues are found then go ahead and enable the master on slavealloc.


== IT-related things ==
== IT-related things ==
File separate bugs for Nagios (eg: {{bug|717804}}), Mysql access (eg: {{bug|717806}})
Follow the steps for [[ReleaseEngineering/AWS_Master_Setup#IT|AWS masters]].
* Nagios
** PING
** Swap
** avg load
** buildbot
** disk - /
** disk - /builds
* Mysql access to the DB server
* Verify that master can send mail to tinderbox via dm-mail01. see e.g. {{bug|717808}}
 
== SSH Keys ==
== SSH Keys ==
* Copy production ssh keys (for ffxbld, trybld, xrbld and tbirdbld) and <tt>known_hosts</tt> to ~/.ssh.
* Copy production ssh keys (for ffxbld, trybld, xrbld and tbirdbld) and <tt>known_hosts</tt> to ~/.ssh.
Line 98: Line 81:
** add it to bm36:~cltbld/.ssh/known_hosts (puppet doesn't work here)
** add it to bm36:~cltbld/.ssh/known_hosts (puppet doesn't work here)
** TODO: add steps for puppetagain
** TODO: add steps for puppetagain
** verify the change (ssh to masters as cltbld from bm36)
** verify the change the same way as for [[ReleaseEngineering/AWS_Master_Setup#Add_master.27s_SSH_key_to_known_hosts|AWS masters]].
 
== Lock a slave and let it take jobs ==
Locked through slavealloc a slave to the newly setup master.
Let it run for a couple of hours and check that the jobs worked well.
Check also in the #buildduty channel for possible nagios checks going off (e.g. [[ReleaseEngineering/Queue_directories|Queue directories]] checks)
 
If no issues are found then go ahead and enable the master on slavealloc.


== Final Verification ==
== Final Verification ==
Confirmed users
1,364

edits

Navigation menu