Ethan Quach wrote: > > Dave Miner wrote: >> Tim S. Knitter wrote: >>> Please review and provide comments. Rev 0.2 Includes comments by >>> Dave, Mike, Ethan, Evan and Jason. >>> >>> http://www.opensolaris.org/os/project/caiman/Snap_Upgrade/snap-documents/snapBeUtilDesign-02.pdf >>> >>> >>> >> >> One thing which I forgot to comment on previously is that section 4.0 >> asserts that "Snapshots will be named and managed by beadm" but >> there's no specification of what operations will be available other >> than listing them in "beadm list". There are automatic snapshots >> taken prior to >> packaging transactions, but what about other snapshots I might desire >> to take? > > If you mean snapshots you take on your own, then there's no support > to do anything with those from the cli other than being listed... > >> And how do I destroy a snapshot, > > There isn't a need for an explicit destroy of a BE snapshot from > the cli since there's no option to create one. (Perhaps two things > we should consider adding.) >
That's what I'm suggesting - it's a missing feature in the design. > In the current design, the two types of snapshots that can exist are > the ones that get created as a result of generating a BE clone, and > the ones that get created using the be_create_snapshot() call from > libbe, which isn't used by the BE cli. > > The former type of snapshots are destroyed when the BE clones they > were used to create get destroyed. The latter type are destroyed > as specified by the caller of be_create_snapshot() by the defined > class of snapshot, see 3.1.1.1 of the libbe doc. > >> or revert a BE to a particular snapshot (including the "as-installed" >> snapshot we'll automatically take)? > > We don't have an option to create a new BE from some existing snapshot > of a BE. (another option we should probably support as well.) > Please. Dave
