tasket
Feature: multiple backup profiles (not just default?)
Hello there.
I see that everything wyng is under the default profile metadir (/var/lib/wyng.backup/default) and backup dirs (./wyng.backup/default) matching default profile name.
Is there a way to specify other profiles to arch-init and other operations? In what I try to accomplish, it would mean that a "local" (default) and remote (QubesOS/OEM maintained templates) could coexist under /var/lib/wyng.backup/ and permit restoration on local LVM from local/remote backups.
THAT, would be amazing.
Is QubesOS team aware of the possibilities of this tool to remove dependency on rpm to deploy templates post-install? (which doesn't respect rpm -V contract for verification post-install, anyway...). It would just be totally awesome to have QubesOS deploy those backups on a read-only ssh accessible server to users, so that users can actually restore their templates to latest releases ( with matching timestamps ) in emergency recovery situations (including root-snapshot that could be moved over root from recovery, once #18 is figured out so the user can reinject his QubesOS Machines configs inside of XML.)
Heads could even permit such deployments directly from the recovery shell if network wire was connected, offering similar detached signed digest validation upon QubesOS distribution gpg signature of a similar logic that is enforced here against user keypair, signed by QubesOS distribution key on the root of their offered ssh wyng-backup directory.
@marmarek? @tasket ?
There is no way to do it from wyng v0.2, although the dir structure anticipates this capability. Its already mentioned on the 'misc list' issue #25.
Swapping the default dirs manually could work, but only if wyng is not scheduled to run in the background (or if you put a lock on '/var/lock/wyng').
This is sort-of already supported via the --meta-dir option. However, the way its described here won't be possible for v0.3, so I expect it to land in v0.4 instead–and probably in a more elegant form that obviates the need for users to think about local metadata storage.
Work has begun on this. When it leaves the 04wip branch, the file format will change (not drastically) and we'll be in alpha3.