I've changed the plan a bit. The remaining plan, in case anyone is interested in what I'll be doing:
* Set up database dumps on foresight-commits (in addition to full backup from streaming mirror) [DONE] * Convert the filesystem that will hold the local foresight-commits content store from ext3 to ext4. [DONE] * Stop the mirror [DONE] * Modify the configuration to use the local content store [DONE] * Copy the NFS-mounted content store to the local content store [UNDERWAY] * Restart mirror The rest of this is unlikely to happen before next Tuesday: * Test email from fdev * Disable all non-mirror accounts on foresight.rpath.org * Wait for mirror to be complete * Reverse direction of mirror * Run mirror * Enable commitmail from foresight-commits * Disable commitmail from foresight.rpath.org * Enable developer accounts on foresight-commits * Send instructions on using foresight-commits to foresight-devel * Set up triggered as well as cron-based syncing for practically instantaneous public access on main foresight.rpath.org * Send instructions on how to use fdev and foresight-commits to foresight-devel I'll be trying to keep the amount of time when developers cannot commit anything to either repository to a minimum... _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
