Confirmed users
391
edits
ReleaseEngineering/PuppetAgain/Data: Difference between revisions
Jump to navigation
Jump to search
m
ReleaseEngineering/PuppetAgain/Data (view source)
Revision as of 14:03, 2 August 2013
, 2 August 2013→.. add a data file
| Line 26: | Line 26: | ||
First, consider the implications. If something (e.g., pip without an explicit version) will magically "discover" the files you're about to add, then you're making a production change and you should tread carefully. In general, we want to avoid such magical discovery, but it happens sometimes anyway. | First, consider the implications. If something (e.g., pip without an explicit version) will magically "discover" the files you're about to add, then you're making a production change and you should tread carefully. In general, we want to avoid such magical discovery, but it happens sometimes anyway. | ||
As root, login to the designated puppet master (currently releng- | As root, login to the designated puppet master (currently <tt>releng-puppet2.srv.releng.scl3.mozilla.com</tt>) and add the file in the appropriate place under /data. In general, we try not to remove or overwrite files, but if you need to, do so. Run <tt>puppetmaster-fixperms</tt> to fix the permissions on those files (although this runs every half-hour anyway). | ||
To accelerate the file-distribution process, run ` | To accelerate the file-distribution process, run `puppetmaster-sync` on the other servers where you need the files. Note that this is run twice an hour on a crontask, so this step is not required if you've got time to spare. Whether you run it manually or from cron, a change-management email will be sent to indicate the changes you made. | ||
= How it works = | = How it works = | ||