ReferencePlatforms/How To/Setup a New Reference Platform: Difference between revisions

ReferencePlatforms/How To/Setup a New Reference Platform (view source)

787 bytes removed , 5 August 2015

Confirmed users

1,989

edits

@@ Line 23: / Line 23: @@
 This is a example {{bug|783455}}.  The  buildmaster-production.pp  (puppet-manifests) needs to have the new masters added to the nodes so you can puppetize the new masters.  The productionmasters.json (tools) needs to have the new masters listed.  I initially set them to disabled, they will be enabled when we are ready for production.  Before the reconfig to enable the new master occurs, you should add ssh keys and an updated authorized_keys file to the master.  Once the reconfig is complete, you'll need to start the new master.
-=== Are you able to send mail to the tinderbox server from the new master? ===
-{{bug|717808}} is an example.  Tested this tonight from bm37, think it works
-<pre>
-Aug 19 16:47:06 buildbot-master38 sendmail[17861]: q7JNl5wW017859: to=<dm-mail01@tinderbox.mozilla.org>, ctladdr=<root@buildbot-master38.srv.releng.scl3.mozilla.com> (0/0), delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=120434, relay=mx1.corp.phx1.mozilla.com. [63.245.216.69], dsn=5.1.1, stat=User unknown
-Aug 19 16:47:06 buildbot-master38 sendmail[17861]: q7JNl5wW017859: q7JNl6wW017861: DSN: User unknown
-Aug 19 16:47:06 buildbot-master38 sendmail[17861]: q7JNl6wW017861: to=<root@buildbot-master38.srv.releng.scl3.mozilla.com>, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=31748, dsn=2.0.0, stat=Sent
-</pre>
 == Open a bug for buildbot and puppet changes ==