Colin Walters 09238da065 admin: Add an unlock command, and libostree API ... I'm trying to improve the developer experience on OSTree-managed systems, and I had an epiphany the other day - there's no reason we have to be absolutely against mutating the current rootfs live. The key should be making it easy to rollback/reset to a known good state. I see this command as useful for two related but distinct workflows: - `ostree admin unlock` will assume you're doing "development". The semantics hare are that we mount an overlayfs on `/usr`, but the overlay data is in `/var/tmp`, and is thus discarded on reboot. - `ostree admin unlock --hotfix` first clones your current deployment, then creates an overlayfs over `/usr` persistent to this deployment. Persistent in that now the initramfs switchroot tool knows how to mount it as well. In this model, if you want to discard the hotfix, at the moment you roll back/reboot into the clone. Note originally, I tried using `rofiles-fuse` over `/usr` for this, but then everything immediately explodes because the default (at least CentOS 7) SELinux policy denies tons of things (including `sshd_t` access to `fusefs_t`). Sigh. So the switch to `overlayfs` came after experimentation. It still seems to have some issues...specifically `unix_chkpwd` is broken, possibly because it's setuid? Basically I can't ssh in anymore. But I *can* `rpm -Uvh strace.rpm` which is handy. NOTE: I haven't tested the hotfix path fully yet, specifically the initramfs bits.		2016-03-23 11:09:09 -04:00
..
glib-tap.mk	tests: Port to glib-tap.mk, make make check run all of the tests	2016-03-03 08:50:19 -05:00
glibtests.m4	tests: Port to glib-tap.mk, make make check run all of the tests	2016-03-03 08:50:19 -05:00
tap-driver.sh	tests: Port to glib-tap.mk, make make check run all of the tests	2016-03-03 08:50:19 -05:00
tap-test	admin: Add an unlock command, and libostree API	2016-03-23 11:09:09 -04:00