Confirmed users
1,989
edits
ReferencePlatforms/How To/Setup a New Reference Platform: Difference between revisions
Jump to navigation
Jump to search
ReferencePlatforms/How To/Setup a New Reference Platform (view source)
Revision as of 13:37, 14 December 2012
, 14 December 2012→Open bugs so you can puppetize the new master(s) and add them to productionmasters.json
| Line 20: | Line 20: | ||
=== Open bugs so you can puppetize the new master(s) and add them to productionmasters.json === | === Open bugs so you can puppetize the new master(s) and add them to productionmasters.json === | ||
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. | 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? === | === Are you able to send mail to the tinderbox server from the new master? === | ||