ReleaseEngineering/PuppetAgain/Data: Difference between revisions

no edit summary
(details on mirrors)
No edit summary
Line 24: Line 24:
== .. add a data file ==
== .. add a data file ==


As root, login to the designated puppet master (currently releng-puppet1.srv.releng.scl3.mozilla.com) 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.
As root, login to the designated puppet master (currently releng-puppet1.srv.releng.scl3.mozilla.com) 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>puppetagain-fixperms</tt> to fix the permissions on those files (although this runs every half-hour anyway).


To accelerate the file-distribution process, run `puppetagain-sync`.  Note that this is run once an hour on a crontask, so this step is not required.  Whether you run it manually or from cron, a change-management email will be sent to indicate the changes you made.
To accelerate the file-distribution process, run `puppetagain-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 =
Line 46: Line 46:
</pre>
</pre>


The trees are synchronized, currently using rdist, although this is awful slow so we may look for another solution.
The trees are synchronized, using rsync (see {{bug|769071}}).
canmove, Confirmed users
1,394

edits