ReleaseEngineering/How To/Setup buildbot masters in AWS: Difference between revisions

Jump to navigation Jump to search
tweaks for new processes
(update ACL request info)
(tweaks for new processes)
Line 30: Line 30:
Puppet will reboot the the master. You can follow the log in a different terminal:
Puppet will reboot the the master. You can follow the log in a different terminal:
  tail -F buildbot-master58.log
  tail -F buildbot-master58.log
* You can get the IP address of the master from the log or using AWS web console.
* You can get the IP address of the master from the log or using AWS web console.
* When master rebooted make sure to login as cltbld and '''stop the master''':
* When master rebooted make sure to login as cltbld and '''stop the master''':
  cd /build/buildbot/build1 && make stop
  cd /builds/buildbot/*1* && make stop


* For build/try masters, '''add master's ip to secrets::network::masterIPs''' on master-puppet1:/etc/puppet/manifests/secrets.pp. The signing instances will be automatically reloaded.
* For build/try masters, '''add master's ip to secrets::network::masterIPs''' on master-puppet1:/etc/puppet/manifests/secrets.pp. The signing instances will be automatically reloaded.
Line 64: Line 65:
** Mac Address: output of <tt>ip link show eth0 | tail -n -1 | awk '{print $2}'</tt> on the master
** Mac Address: output of <tt>ip link show eth0 | tail -n -1 | awk '{print $2}'</tt> on the master
** Adapter Name (nic0-99 or mgmt0-99): nic0
** Adapter Name (nic0-99 or mgmt0-99): nic0
** Host Name: fqdn
** Leave the rest as is
** Leave the rest as is
* Press "Create", then close box, to dismiss the adapter dialog
* Press "Save" to save the adapter (even though adapter may not show)


== 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]


== Add master's SSH key to know_hosts ==
== Add master's SSH key to known_hosts ==
* Add the master's ssh key to known_hosts (to make release-runner work):
* Add the master's ssh key to known_hosts (to make release-runner work):
** dump the key by running the following:
** dump the key by running the following:
  ssh-keyscan $master_name
  ssh-keyscan $master_name
** ad it to /N/production/home/cltbld/.ssh/known_hosts on master-puppet1.build.scl1.mozilla.com
** add it to /N/production/home/cltbld/.ssh/known_hosts on master-puppet1.build.scl1.mozilla.com
*** use the "fqdn,IP" when adding, to enable testing before host in DNS
** 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 (ssh to masters as cltbld from bm36)
  ssh -i .ssh/release-runner buildbot-master80.srv.releng.usw2.mozilla.com
  ssh -i .ssh/release-runner buildbot-master80.srv.releng.usw2.mozilla.com
Line 82: Line 87:
* Ask RelOps to add the master to DNS once you added it to inventory (for example, {{Bug|859524}})
* Ask RelOps to add the master to DNS once you added it to inventory (for example, {{Bug|859524}})
* Ask NetOps (ACL Requests) to add new hosts to the "Build Masters group" (for example {{Bug|859528}}, with [https://bugzil.la/812342#c13 update])
* Ask NetOps (ACL Requests) to add new hosts to the "Build Masters group" (for example {{Bug|859528}}, with [https://bugzil.la/812342#c13 update])
* Nagios ({{bug|861359}})
* Ask Server Ops to add the master to Nagios ({{bug|861359}})


== Lock a slave and let it take jobs ==
== Lock a slave and let it take jobs ==
Confirmed users
1,364

edits

Navigation menu