One of my colleagues had a gate wiped on a disk crash (using ZFS, but only 1 disk). That got people wondering about our backup strategy. We have distributed developers, so we've banked on them having private copies. Oh, and we also push directly to OpenSolaris.

So now I'm looking at adding clones in two remote sites - on machines I don't own. And by that, I mean that I can't create a local gatekeeper user account. Which means that I'll have ssh trust issues. I.e., this will not work:

changegroup.2 = /usr/bin/hg push -R /pool/ws/nfs41-gate ssh://cistern.central//export/ws/th199096/nfs41-clone

I could have a cron job pull changes, but besides being gross, there is a slight chance it will not grab something. No, I want the push to the gate to still copy to the clones.

The answer is to mimic Dave Marker's code for updaing OpenSolaris (it is updateoso.py in the onnv-gk-tools repository seen at ssh://anon@hg.opensolaris.org/hg/scm-migration/onnv-gk-tools). Before I do that though, there is the issue that I'll need local copies of that repository as well. I could use the one that is in use for onnv, but then again, if I mess things up, Dave might recall that Oklahoma has a no helmet law and come over to visit. Much safer to create my own copy.

The biggest issue was making sure to add the new key to the two machines. I've got this set up and running.