| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I992dc0c1d40f563ade56a833162d409b02be90a0
|
|\
| |
| |
| |
| | |
Reviewed-By: James Thomas <james.thomas@codethink.co.uk>
Reviewed-By: Sam Thursfield <sam.thursfield@codethink.co.uk>
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Move some code to the '.check' extension to verify that the deployment
can happen *before* spending 5 minutes unpacking and configuring the
rootfs.
This is not a perfect solution yet because when multiple systems are
being deployed in a cluster, we do not check all systems and then
deploy them all. Instead, we check one, then deploy it, then check the
second, etc.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-s, or --protect-args prevents the file path components of destination
or source paths being interpreted by the remote shell.
This is for wildcards or other shell features, but it breaks when paths
have whitespace.
We tend to always use absolute paths, so all uses of rsync now pass -s.
kvm.write needs it, since the disk can be written to a path with spaces.
Nfsboot and ssh-rsync need it because version labels are used, which may
have spaces, and temporary directories are used, which could have spaces
in weird TMPDIR configurations.
|
|
|
|
|
|
|
|
|
| |
With this we'll have "default -> factory" instead of
"default-run" -> "factory/run".
Also change to use VERSION_LABEL instead of VERSION and
"factory" instead of "version1", to be more consistent with
other parts of the code.
|
| |
|
|
|
|
| |
If the version already exists on the device, deployment is aborted
|
| |
|
| |
|
|
|
|
|
| |
We only have written this this year, so it should be copyright
this year only.
|
|
|
|
| |
Reviewed-by: Lars Wirzenius <lars.wirzenius@codethink.co.uk>
|
|
The 'location' command-line argument refers to the hostname of the
'nfsboot server', a baserock system that has an nfs server, the
directory '/srv/nfsboot/nfs', and a tftp server that hosts files from
the directory '/srv/nfsboot/tftp'.
The write extension will read the hostname of the target system and copy
its root filesystem to /srv/nfsboot/nfs/<hostname> and its kernel to
/srv/nfsboot/tftp/<hostname>. It will then configure the nfs server to
export that nfs root.
|