ReleaseEngineering:Sheriffing:HowTo: Difference between revisions

No edit summary
Line 79: Line 79:
** [[ReferencePlatforms/Test/WinXP#Installing_OPSI|Here]] is how you turn a Windows machine to talk to staging-opsi after being re-imaged
** [[ReferencePlatforms/Test/WinXP#Installing_OPSI|Here]] is how you turn a Windows machine to talk to staging-opsi after being re-imaged
* Read "[[ReferencePlatforms#Tracking_ref_images_being_refreshed|refreshing ref images]]" to know if you need to ask IT to refresh the images of the ref machines.
* Read "[[ReferencePlatforms#Tracking_ref_images_being_refreshed|refreshing ref images]]" to know if you need to ask IT to refresh the images of the ref machines.
Checklist:
* is the machine a staging machine that needs to be re-imaged?
** adjust the buildbot.tac accordingly
** check that it is talking with the right puppet master or opsi server
*** for Linux check '' '' and for Mac check '' /Library/LaunchDaemons/com.reductivelabs.puppet.plist''
* very important to verify [[PostImage]] after re-imaging minis
* clean and sign the puppet certificate
** on slave - puppetd --test --server ${puppet_master_hostname}.build.mozilla.org
** puppetca --clean ${hostname}.build.mozilla.org and puppetca --clean ${hostname}.build.mozilla.org
List of puppet masters:
* mv-production-puppet.build (for whatever is left at Castro)
* mpt-production-puppet.build (for most build VMs)
* scl-production-puppet.build (most HW machines)
I have also filed {{bug|601174}} to improve how the staging machines get re-imaged.


==Mobile==
==Mobile==
Confirmed users
3,990

edits