Actually, with BK it should be possible to have read only clones on
multiple servers, should it not? Not that I'm saying BK should foot
the bill to do that, but having read-only clones of the primary kernel
trees would avoid most downtime.
I suppose it would be difficult for two servers to do a merge with
conflicts by themselves so multiple write clones are probably not super
desirable, but read-only clones should be pretty easy to set up and
keep up-to-date via "bk pull" (or even "bk push" triggered by a commit
script).
You could allow writing on a single read-only clone while the primary
is down and then update the primary when you move back, if that was an
issue, although I'm guessing that the DNS updates would take longer to
propagate than most outages.
I wonder if any of the kernel.org mirror sites would be interested in
hosting a clone of one or more BK repositories.
Cheers, Andreas
-- Andreas Dilger http://sourceforge.net/projects/ext2resize/ http://www-mddsp.enel.ucalgary.ca/People/adilger/- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/