diff options
author | Sam Thursfield <sam.thursfield@codethink.co.uk> | 2015-04-13 12:31:46 +0000 |
---|---|---|
committer | Baserock Gerrit <gerrit@baserock.org> | 2015-04-21 18:25:12 +0000 |
commit | 9d2700755d616d66d49713cce77c48e1eb566cef (patch) | |
tree | a16cb198771ac4804b6eb4321f66e7358c9bd4cc /distbuild/sockserv.py | |
parent | 006096c5c8b8bdcf3fe89d9c4d7585aac5981d33 (diff) | |
download | morph-9d2700755d616d66d49713cce77c48e1eb566cef.tar.gz |
Add distbuild-trove-nfsboot.write
The nfsboot.write deployment extension has been deprecated for a while
because it's not generally useful. It's only used for deploying
distbuild nodes to a Trove, as far as I know.
We still need to support setting up a bunch of machines that boot over
NFS from a Trove. But we can do this in a special-purpose .write
extension.
The new distbuild-trove-nfsboot.write is much more efficient than
the more generic nfsboot.write: instead of treating each system
individually (thus copying an almost identical ~2GB rootfs to the Trove
once per node) it copies the system image to the Trove once, and /then/
sets up a rootfs per node.
Upgrades are now supported, although the code assumes distbuild nodes
are stateless (as they should be) so nothing special is done for
upgrades, other than checking that there is already a version of the
given system in existance. The new extension does not create an
orig/ and run/ version of each system, because there is no need when the
deployed system is stateless.
There could be further gains in efficiency, but I don't have time to do
them right now. This write extension is full of compromises, its goal is
to better support the existing users who have a Trove and a distbuild
network deployed via NFS. It is specifically not intended to be useful
for other purposes.
Change-Id: I9a50c58b714ed272212d1d6c55b289aaa96051b1
Diffstat (limited to 'distbuild/sockserv.py')
0 files changed, 0 insertions, 0 deletions