> > A volatile policy might be a misnomer. One would hope that a consistent > > policy is enforced when dealing with things that sound like transient > > snapshots. :P > > Yes a consistent policy is enforced by allowing the default settings > to preside.
If that's the case, we should find a more appropriate and descriptive name for this policy. > > Would you please explain some more about what the libbe service does > > with these snapshots? I'm curious about this eventual removal. > > When does it take place, and under what cirumstances? What's the > > justification for introducing this type of snapshot? > > I couldn't explain it any better than section 3 in: > > http://opensolaris.org/os/project/caiman/Snap_Upgrade/snap-documents/snap-libbe-design-0.7.pdf The design document is a start, but it doesn't completely explain why things are the way they are. It's vague about what actually causes the snapshots to get deleted. Are you running a BE daemon that manages this in the background? If I've read the code review correctly, you're changing every snapshot pkg takes to be of type "volatile." Why is this the correct approach? I wouldn't hard code the name of the policy into the pkg client. I would stick with the static policy by default. It seems like it would make more sense to allow the administrator to choose the snapshot policy that is employed. Do you allow the administrator to create new dynamic management policies? If so, I wouldn't use a dynamic policy until the administrator has first configured one. At that point, the admin should choose which dynamic policy is the default. Hard coding the policy into the pkg client makes all of this impossible. -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
