On Wed, 2009-06-03 at 14:05 -0500, Nicolas Williams wrote: > On Wed, Jun 03, 2009 at 03:01:45PM -0400, Sebastien Roy wrote: > > On Wed, 2009-06-03 at 18:29 +0100, Alan Maguire wrote: > > > If you just want a recipe for customers to revert config > > > to that which you ship in the manifest (while preserving > > > the enabled/disabled state of the instance) to cover > > > the rare cases where their configuration is unusable, > > > _and_ they don't want to repair it but start from scratch, > > > I believe "svccfg -s ilb:default revert last-import" > > > followed by a "svcadm refresh ilb:default" should do > > > it. > > > > I don't quite understand why this problem is specific to ILB. Why > > wouldn't anyone running into any non-recoverable and fatal problem with > > any subsystem not want to revert back to a working configuration? In > > that vein, why wouldn't a generic solution like zfs snapshots and/or > > alternate boot environments work without including ILB-specific > > solutions? > > I agree, mostly. This is just a matter of documentation. There's no > need to build an ILB-specific tool to do "svccfg -s ilb:default revert > last-import". > > (My one disagreement is that ZFS snapshots and BEs are too coarse for > backing out per-service configurations. You really need SMF's snapshots > instead.)
Agreed, I was going in that direction also. The general idea being that this is a general problem requiring a general-purpose solution. -Seb
