On Thu, Jan 16, 2014 at 03:04:01AM +0100, Martin Bähr wrote: > what was the purpose of the copy? just backup/redundancy?
Well, in rPL land, the commits repository was in the office, and the mirror was in the colo, preserving office bandwidth. It also avoided contention between very different database use cases. When rPath hosted the foresight build infrastructure, it was set up with commits and mirror for the same reasons; we didn't want to take up all the rPath office bandwidth; that would have been rude. And again, there were two separate database instances. We preserved the setup when moving the infrastructure, even though there was no longer a low-bandwidth office and high-bandwidth colo situation. There were originally going to be two separate databases, but as we shuffled things around, they ended up being two nearly identical databases on the same postgresql cluster. So it ended up being not much redundancy, functionally, so there was no point in keeping it. Not sure why I didn't delete it earlier. After the change propagates, I'll be able to delete the mirror and use the space to move over all the rest of the preserved *.rpath.org repositories. Then I'll be able to decommission repostore.rpath.org and that will give me the storage we need to start the import process, while we get the additional storage deployed. (I had forgotten until recently that we also needed some additional network ports to actually hook it up.) _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
