On 05/27/09 00:16, John Zolnowsky x69422/408-404-5064 wrote:
> 2) It doesn't extend to svcadm or svcprop. Users would likewise
> expect to use those commands for their effects in enabling,
> disabling, and querying services in an alternate repository.
Right. To come with a concrete example that would--sort of--work as an
administrator expects:
1. The admin creates a snapshot to run from, and boots off it
zfs snapshot rpool/ROOT/snv_115 at read-only
zpool set bootfs=rpool/ROOT/snv_115 at read-only rpool
reboot
2. after some time, the admin decides he/she doesn't want, e.g.,
apache running anymore. Two options would be: modify the original
filesystem and snapshot again, or clone the snapshot, modify the clone,
and snapshot the clone:
a. svcadm -R rpool/ROOT/snv_115 disable apache22
zfs snapshot rpool/ROOT/snv_115 at read-only-no-apache
zpool set bootfs=rpool/ROOT/snv_115 at read-only-no-apache rpool
reboot
b zfs clone rpool/ROOT/snv_115 at read-only rpool/ROOT/no-apache
svcadm -R rpool/ROOT/no-apache disable apache22
zfs snapshot rpool/ROOT/no-apache at read-only
zpool set bootfs=rpool/ROOT/no-apache at read-only
reboot
Apart from the administrative tasks of setting boot-FS'es, etc. this is
the sort of thing we were thinking about. Now I think svcadm always talks
to svc.configd/svc.startd which operate on the repository of the currently
booted environment, so we're looking for guidance as to how this could be
done/made to work.
Thanks,
Joep
